# Danger rating card

> Canonical HTML: https://screenrig.ai/docs/cards/danger-rating/

Staff-issued hazard ratings with the guidance that goes with them.

Fire, avalanche, beach, water or heat ratings appear with their issuing source and guidance. The highest supplied severity leads, while expired, future-dated and old reports are clearly marked. Primetime uses a crisp entrance and slow outlines while keeping every warning readable.

## Live card

This card is drawn in your browser by the same code the Players run, with sample data.

Category: Weather. Tags: Weather and environment, Alerts and status, Lobbies and reception.

## Layouts

This fullscreen card fills the whole screen in landscape or portrait and is not placed as a corner, chip, or strip.

Layouts: full. Forms: landscape, portrait.

[Card layouts, themes and publishing](/docs/cards/). [Browse the cards](/apps/#cards).

## Data and privacy

This card uses its configured properties and live card data.

Operational ratings and issuing sources; no personal data.

## Properties

For theme, background, accent and position, see [Common properties](/docs/cards/#common-properties).

Set static properties in `params`. Bind `data` to a project card data key for live values; that document holds only dynamic properties. Without a data key, put the complete configuration in `params`. Nested rows describe the contents of their parent property.

### Static properties

| Name | Type | Default | Values and limits | Description |
| --- | --- | --- | --- | --- |
| `title` | string | `"Danger ratings"` | maxLength: `100` |  |
| `staleMinutes` | integer | `1440` | minimum: `1`; maximum: `10080` |  |
| `pageSeconds` | integer | `12` | minimum: `8`; maximum: `120` |  |

### Dynamic properties

| Name | Type | Default | Values and limits | Description |
| --- | --- | --- | --- | --- |
| `site` | string | `""` | maxLength: `120` |  |
| `ratings` | array | `[]` | maxItems: `32` | Staff-issued ratings, labels and guidance; the card does not derive a hazard assessment. Missing, future, expired or old issue times never imply a current low rating. |
| `ratings[].name` | string |  | minLength: `1`; maxLength: `80`; Required |  |
| `ratings[].level` | string |  | `"low"`, `"moderate"`, `"high"`, `"extreme"`, `"unknown"`; Required |  |
| `ratings[].label` | string | `""` | maxLength: `80` |  |
| `ratings[].guidance` | string | `""` | maxLength: `300` |  |
| `ratings[].source` | string | `""` | maxLength: `120` |  |
| `ratings[].issuedAt` | string |  | maxLength: `64`; Required |  |
| `ratings[].expiresAt` | string | `""` | maxLength: `64` |  |

## Canvas example

Add this item to a playlist page’s `primitives`. [Publish the playlist and assign a screen](/docs/cards/#publish-a-card-canvas).

```json
{
  "id": "danger-rating",
  "primitive": "card",
  "card": "danger-rating",
  "major": 1,
  "params": {
    "theme": "neomustard"
  },
  "rect": {
    "x": 0,
    "y": 0,
    "width": 1920,
    "height": 1080
  },
  "layer": 0,
  "content_fit": "fill",
  "data": "example-key"
}
```

## Write live data

The canvas example binds its `data` field to `example-key`. That value is a data key: a name this canvas item chooses, not the name of the card. Give each canvas item its own key when items should show different data, or share one key when they should show the same data. Keys are scoped to the project, follow the K/V key grammar, and cannot start with `feed:`.

Create this document before showing the card, then replace it to update the screen without republishing. Writes to a key that live canvas items bind are checked against each bound card’s dynamic properties. Use the same project as the playlist.

Save the document as `card-data.json`. The CLI reads the document itself, with no wrapper:

```json
{
  "site": "",
  "ratings": []
}
```

```console
screenrig card-data put example-key --file card-data.json
```

Or call the API directly. The API wraps the same document in a `document` field. An agent token already names its project, so no project header is sent; if you send `ScreenRig-Project`, it must match the token’s project. Supply your API authorization through the environment; see [API authentication](/docs/authentication/).

```console
curl --request PUT "https://api.screenrig.ai/api/card-data/example-key" \
  --header "Authorization: Bearer $SCREENRIG_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"document":{"site":"","ratings":[]}}'
```