# Schema reference

The schema provides the authoritative definition of the structure of Risk Data Library Standard (RDLS) data, the meaning of each field, and the rules that must be followed to publish RDLS data. It is used to validate the structure and format of RDLS data.

For this version of RDLS, the canonical URL of the schema is [https://docs.riskdatalibrary.org/en/0\_\_2\_\_0/rdls_schema.json](https://docs.riskdatalibrary.org/en/0__2__0/rdls_schema.json). Use the canonical URL to make sure that your software, documentation or other resources refer to the specific version of the schema with which they were tested.

This page presents the schema in tables with additional information in paragraphs. You can also [view the schema in an interactive browser](browser.md) or [download it as JSON Schema](../../docs/_readthedocs/html/rdls_schema.json).

```{note}
   If any conflicts are found between the text on this page and the text within the schema, the text within the schema takes precedence.
```

The RDLS schema covers [dataset fields](#dataset), [resource fields](#resource) and four risk-specific components to describe risk datasets:

- [Hazard](#hazard-metadata): Metadata that is specific to datasets that describe processes or phenomena that may cause loss of life, injury or other health impacts, property damage, social and economic disruption or environmental degradation. For example, a classification of the type of the hazard, the units in which the intensity of the hazard is measured, and the frequency at which the hazard occurs.
- [Exposure](#exposure-metadata): Metadata that is specific to datasets that describe the location and demographic information of people, and the location, characteristics and value of assets in the built and natural environment. For example, the type of building and the cost to replace it if it suffered damage.
- [Vulnerability](#vulnerability-metadata): Metadata that is specific to datasets that describe the vulnerability and fragility relationships and indexes used in risk analysis. This includes the type of exposure, hazard intensity and impact the relationship describes, and information on how the relationship was developed. This component uses attributes consistent with the hazard, exposure and loss components.
- [Loss](#loss-metadata): Metadata that is specific to datasets that contain the simulated (modeled) risk and impact estimates produced in a risk assessment, including explicit links to the hazard, exposure, and vulnerability datasets used in the analysis.

For general definitions of hazard, exposure, vulnerability and loss, please see the [Glossary](../glossary.md).

For fields that reference [sub-schemas](#sub-schemas), a link is provided to a table with details of the sub-schema. To see how the fields and sub-schemas fit together, consult the [schema browser](browser.md).

## Dataset

The top-level object in the RDLS schema is a risk dataset. A risk dataset is described as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /description
---
```

The general attributes of a dataset are described by fields based on the [Data Catalog Vocabulary](https://www.w3.org/TR/vocab-dcat-3/) and the [Dublin Core Metadata Initiative Metadata Terms](https://www.dublincore.org/specifications/dublin-core/dcmi-terms).

The following diagram shows key dataset-level fields, with required fields highlighted in blue:

```{eval-rst}
.. uml::

  @startjson
  <style>
    jsonDiagram {
      BackGroundColor transparent
    }
    .required {
      BackGroundColor #239ce8
    }
  </style>
  #highlight "title" <<required>>
  #highlight "risk_data_type" <<required>>
  #highlight "publisher" <<required>>
  #highlight "publisher" / "name" <<required>>
  #highlight "spatial" <<required>>
  #highlight "license" <<required>>
  {
    "title": "",
    "description": "",
    "risk_data_type": "",
    "publisher": {
      "name": "",
      "email": "",
      "url": ""
    },
    "version": "",
    "purpose": "",
    "project": "",
    "details": "",
    "spatial": {
      "countries": "",
      "bbox": ""
    },
    "license": ""
  }
  @endjson

```

The following table lists all dataset-level fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
collapse: 
  publisher,spatial,resources,referenced_by,contact_point,creator,attributions,sources,links,hazard,exposure,vulnerability,loss
addtargets:
---
```

## Resource

A `Resource` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Resource/description
---
```

Each dataset can have many associated resources.

The following table lists all resource-level fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Resource
collapse: temporal
addtargets:
---
```

## Hazard metadata

The `hazard` component is described as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /properties/hazard/description
---
```

The hazard component describes metadata about modeled natural hazards data, including hazard intensity footprints of historical or hypothetical events, return period hazard maps, hazard or susceptibility index, and stochastic event sets. The metadata defines the hazard type, physical process and intensity measures used in the dataset. Multiple hazards and processes (including cascading events) can be defined for each hazard, enabling users to describe dataset that contain, for example, earthquake ground shaking and liquefaction, and tsunami inundation triggered by the earthquake.

The hazard component uses hazard_type, process_type and intensity_measure consistent with the vulnerability and loss components of this standard. Spatial reference and location information are described using existing external standards. Temporal information can include date and duration of events or year of scenario, and is defined using the Dublin Core standards.

The following diagram shows key hazard component fields, with required fields highlighted in blue. The ![array](../img/array.png) icon indicates that a field is an array.

```{eval-rst}
.. uml::

  @startjson
  <style>
    jsonDiagram {
      BackGroundColor transparent
    }
    .required {
      BackGroundColor #239ce8
    }
  </style>
  #highlight "event_sets" <<required>>
  #highlight "event_sets" / 0 / "analysis_type" <<required>>
  #highlight "event_sets" / 0 / "events" / 0 / "calculation_method" <<required>>
  #highlight "event_sets" / 0 / "events" / 0 / "hazard" <<required>>
  #highlight "event_sets" / 0 / "events" / 0 / "hazard" / "type" <<required>>
  #highlight "event_sets" / 0 / "events" / 0 / "hazard" / "processes" <<required>>
  #highlight "event_sets" / 0 / "events" / 0 / "occurrence" <<required>>
  #highlight "event_sets" / 0 / "events" / 0 / "footprints" / 0 / "intensity_measure" <<required>>
  {
    "event_sets": [
      {
        "analysis_type": "",
        "frequency_distribution": "",
        "seasonality": "",
        "event_count": "",
        "occurrence_range": "",
        "spatial": "",
        "temporal": "",
        "events": [
          {
            "disaster_identifiers": "",
            "calculation_method": "",
            "description": "",
            "hazard": {
              "type": "",
              "processes": "",
              "intensity_measure": "",
              "trigger": ""
            },
            "occurrence": "",
            "footprints": [
              {
                "intensity_measure": "",
                "data_uncertainty": ""
              }
            ]
          }
        ]
      }
    ]
  }
  @endjson

```

The following table lists all hazard component fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /properties/hazard
collapse: 
  event_sets/0/hazards,event_sets/0/spatial,event_sets/0/temporal,event_sets/0/events
addtargets:
---
```

``````{dropdown} Example: Fathom Global Flood Map
---
open:
---
The following example shows RDLS metadata for the [Fathom Global Flood Map](https://www.fathom.global/product/global-flood-map/) in tabular format and JSON format.

`````{tab-set}

````{tab-item} Figure

```{figure} ../../examples/hazard/fathom/figure.png
```

````

````{tab-item} Metadata (tabular)

In tabular format, the metadata consists of several tables. To aid comprehension, the metadata is presented column wise using field titles.

```{csv-table-no-translate} Datasets
---
stub-columns: 1
widths: auto
file: ../../examples/hazard/fathom/datasets.csv
---

```

```{csv-table-no-translate} Resources
---
stub-columns: 1
widths: auto
file: ../../examples/hazard/fathom/Resources.csv
---

```

```{csv-table-no-translate} Event sets
---
stub-columns: 1
widths: auto
file: ../../examples/hazard/fathom/Hazard metadata_Event sets.csv
---

```

```{csv-table-no-translate} Event set hazards
---
stub-columns: 1
widths: auto
file: ../../examples/hazard/fathom/Hazard metadata_Event sets_Hazards.csv
---

```

````

````{tab-item} Metadata (JSON)

```{eval-rst}
.. jsoninclude:: ../../examples/hazard/fathom/example.json
   :jsonpointer: /datasets/0
   :title: Example
```

`````

``````

``````{dropdown} Example: Aqueduct Floods Hazard Maps

The following example shows RDLS metadata for the [Aqueduct Floods Hazard Maps](https://www.wri.org/data/aqueduct-floods-hazard-maps) in tabular format and JSON format.

`````{tab-set}

````{tab-item} Figure

```{figure} ../../examples/hazard/aqueduct/figure.png
```

````

````{tab-item} Metadata (tabular)

In tabular format, the metadata consists of several tables. To aid comprehension, the metadata is presented column wise using field titles.

```{csv-table-no-translate} Datasets
---
stub-columns: 1
widths: auto
file: ../../examples/hazard/aqueduct/datasets.csv
---

```

```{csv-table-no-translate} Resources
---
stub-columns: 1
widths: auto
file: ../../examples/hazard/aqueduct/Resources.csv
---

```

```{csv-table-no-translate} Event sets
---
stub-columns: 1
widths: auto
file: ../../examples/hazard/aqueduct/Hazard metadata_Event sets.csv
---

```

```{csv-table-no-translate} Event set hazards
---
stub-columns: 1
widths: auto
file: ../../examples/hazard/aqueduct/Hazard metadata_Event sets_Hazards.csv
---

```

````

````{tab-item} Metadata (JSON)

```{eval-rst}
.. jsoninclude:: ../../examples/hazard/aqueduct/example.json
   :jsonpointer: /datasets/0
   :title: Example
```

````

`````
``````

## Exposure metadata

The `exposure` component is described as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /properties/exposure/description
---
```

The exposure component describes metadata for datasets containing information on the distribution and characteristics of built environment assets (buildings and infrastructure) and natural assets and population, that are used in risk assessment. The exposure component provides codelists to describe the type of assets and costs, and the taxonomy scheme that is used to describe construction and demographic information contained in the dataset. For more information, see [exposure standards](../rdl/other-standards.md#exposure-standards).

The exposure component uses exposure categories consistent with the vulnerability and loss components of this standard. Spatial reference and location information are described using existing external standards. Temporal information can include date and duration of events or year of scenario, and is defined using the Dublin Core standards.

The following diagram shows key exposure component fields, with required fields highlighted in blue. The ![array](../img/array.png) icon indicates that a field is an array.

```{eval-rst}
.. uml::

  @startjson
  <style>
    jsonDiagram {
      BackGroundColor transparent
    }
    .required {
      BackGroundColor #239ce8
    }
  </style>
  #highlight "exposure" / "category" <<required>>
  #highlight "exposure" / "metrics" / 0 / "quantity_kind" <<required>>
  {
    "exposure": {
      "category": "",
      "taxonomy": "",
      "metrics": [
        {
          "dimension": "",
          "quantity_kind": ""
        }
      ]
    }
  }
  @endjson

```

The following table lists all exposure component fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /properties/exposure
collapse: metrics
addtargets:
---
```

``````{dropdown} Example: Central Asia projected residential exposure dataset

The following example shows RDLS metadata for the [Central Asia projected residential exposure dataset](https://datacatalog.worldbank.org/search/dataset/0064254/Central-Asia-exposure-dataset---Projected-residential-exposure) in tabular format and JSON format.

`````{tab-set}

````{tab-item} Metadata (tabular)
hazard

```{csv-table-no-translate} Datasets
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_projected/datasets.csv
---

```

```{csv-table-no-translate} Resources
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_projected/Resources.csv
---

```

```{csv-table-no-translate} Attributions
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_projected/Attributions.csv
---

```

```{csv-table-no-translate} Referenced by
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_projected/Referenced by.csv
---

```

```{csv-table-no-translate} Sources
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_projected/Sources.csv
---

```

```{csv-table-no-translate} Gazetteer entries (spatial coverage)
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_projected/Spatial coverage_Gazetteer entries.csv
---

```

```{csv-table-no-translate} Exposure metrics
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_projected/Exposure metadata_Exposure metrics.csv
---

```

````

````{tab-item} Metadata (JSON)

```{eval-rst}
.. jsoninclude:: ../../examples/exposure/central_asia_residential_projected/example.json
   :jsonpointer: /datasets/0
   :title: Example
```

`````
``````

``````{dropdown} Example: Central Asia current residential exposure dataset

The following example shows RDLS metadata for the [Central Asia current residential exposure dataset](https://datacatalog.worldbank.org/search/dataset/0064251/Central-Asia-exposure-dataset---Residential-buildings) in tabular format and JSON format.

`````{tab-set}

````{tab-item} Metadata (tabular)

In tabular format, the metadata consists of several tables. To aid comprehension, the metadata is presented column wise using field titles.

```{csv-table-no-translate} Datasets
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_current/datasets.csv
---

```

```{csv-table-no-translate} Resources
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_current/Resources.csv
---

```

```{csv-table-no-translate} Attributions
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_current/Attributions.csv
---

```

```{csv-table-no-translate} Referenced by
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_current/Referenced by.csv
---

```

```{csv-table-no-translate} Sources
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_current/Sources.csv
---

```

```{csv-table-no-translate} Gazetteer entries (spatial coverage)
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_current/Spatial coverage_Gazetteer entries.csv
---

```

```{csv-table-no-translate} Exposure metrics
---
stub-columns: 1
widths: auto
file: ../../examples/exposure/central_asia_residential_current/Exposure metadata_Exposure metrics.csv
---

```

````

````{tab-item} Metadata (JSON)

```{eval-rst}
.. jsoninclude:: ../../examples/exposure/central_asia_residential_current/example.json
   :jsonpointer: /datasets/0
   :title: Example
```

````

`````
``````

## Vulnerability metadata

The `vulnerability` component is described as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /properties/vulnerability/description
---
```

The vulnerability component describes metadata for datasets that detail fragility, damage-to-loss and vulnerability relationships and indexes for physical damage and social vulnerability that are used in risk analysis. It contains key information including the type of function, intensity and impact metrics used, which asset types or population groups it applies to, how it was developed and for what locations.

The vulnerability component uses hazard_type, process_type and intensity_measure consistent with the hazard and loss components, exposure information consistent with the exposure and loss components. Spatial reference and location information are described using existing external standards.

The following diagram shows key vulnerability component fields, with required fields highlighted in blue:

```{eval-rst}
.. uml::

  @startjson
  <style>
    jsonDiagram {
      BackGroundColor transparent
    }
    .required {
      BackGroundColor #239ce8
    }
  </style>
  #highlight "hazard_primary" <<required>>
  #highlight "intensity" <<required>>
  #highlight "category" <<required>>
  #highlight "impact" <<required>>
  #highlight "functions" <<required>>
  {
    "hazard_primary": "",
    "hazard_secondary": "",
    "intensity": "",
    "category": "",
    "impact": {
      "type": "",
      "metric": "",
      "unit": ""
    },
    "functions": {
      "vulnerability": "",
      "fragility": "",
      "damage_to_loss": "",
      "engineering_demand": ""
    },
    "se_category": ""
  }
  @endjson

```

The following table lists all vulnerability component fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /properties/vulnerability
collapse: cost,impact,spatial,se_category
addtargets:
---
```

``````{dropdown} Example: Global flood depth-damage functions
---
open:
---
The following example shows RDLS metadata for the [Global flood depth-damage functions](https://publications.jrc.ec.europa.eu/repository/handle/JRC105688) in tabular format and JSON format.

`````{tab-set}

````{tab-item} Figure

```{figure} ../../examples/vulnerability/flood_jrc/figure.png
```
````

````{tab-item} Metadata (tabular)

In tabular format, the metadata consists of several tables. To aid comprehension, the metadata is presented column wise using field titles.

```{csv-table-no-translate} Datasets
---
stub-columns: 1
widths: auto
file: ../../examples/vulnerability/flood_jrc/datasets.csv
---

```

```{csv-table-no-translate} Resources
---
stub-columns: 1
widths: auto
file: ../../examples/vulnerability/flood_jrc/Resources.csv
---

```

```{csv-table-no-translate} Attributions
---
stub-columns: 1
widths: auto
file: ../../examples/vulnerability/flood_jrc/Attributions.csv
---

```

```{csv-table-no-translate} Referenced by
---
stub-columns: 1
widths: auto
file: ../../examples/vulnerability/flood_jrc/Referenced by.csv
---

```

```{csv-table-no-translate} Asset costs
---
stub-columns: 1
widths: auto
file: ../../examples/vulnerability/flood_jrc/Vulnerability metadata_Asset cost.csv
---

```

````

````{tab-item} Metadata (JSON)

```{eval-rst}
.. jsoninclude:: ../../examples/vulnerability/flood_jrc/example.json
   :jsonpointer: /datasets/0
   :title: Example
```

````

`````
``````

## Loss metadata

The `loss` component is described as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /properties/loss/description
---
```

The loss component provides metadata describing data generated in risk assessments, i.e., modelled impacts and losses for single historical events or hypothetical scenarios and risk estimates from analysis of large event sets. The data can include monetary and non-monetary, and direct or indirect, impacts and losses.
Loss datasets can be explicitly linked to the exposure, hazard, and vulnerability datasets used in the analysis. This component uses descriptions of assets, hazards and impact types consistent with all other components of this standard. Spatial reference and location information are described using existing external standards. Temporal information can include date and duration of events or year of scenario, and is defined using the Dublin Core standards.

The following diagram shows key loss component fields, with required fields highlighted in blue.  The ![array](../img/array.png) icon indicates that a field is an array.

```{eval-rst}
.. uml::

  @startjson
  <style>
    jsonDiagram {
      BackGroundColor transparent
    }
    .required {
      BackGroundColor #239ce8
    }
  </style>
  #highlight "losses" / "0" / "hazard_type" <<required>>
  #highlight "losses" / "0" / "cost" <<required>>
  #highlight "losses" / "0" / "cost" / "type" <<required>>
  #highlight "losses" / "0" / "cost" / "unit" <<required>>
  {
    "losses": [
      {
        "hazard_type": "",
        "hazard_process": "",
        "category": "",
        "type": "",
        "impact": {
          "type": "",
          "metric": "",
          "unit": ""
        },
        "approach": "",
        "cost": {
          "type": "",
          "unit": ""
        }
      }
    ]
  }
  @endjson

```

The following table lists all loss component fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /properties/loss
collapse: losses/0/cost,losses/0/impact
addtargets:
---
```

## Sub-schemas

### Entity

`Entity` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Entity/description
---
```

This sub-schema is referenced by the following properties:

- [`publisher`](rdls_schema.json,,publisher)
- [`contact_point`](rdls_schema.json,,contact_point)
- [`creator`](rdls_schema.json,,creator)
- [`Attribution/entity`](rdls_schema.json,/$defs/Attribution,entity)

Each `Entity` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Entity
collapse:
addtargets:
---
```

### Attribution

`Attribution` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Attribution/description
---
```

This sub-schema is referenced by the following properties:

- [`attributions`](rdls_schema.json,,attributions)

Each `Attribution` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Attribution
collapse: entity
addtargets:
---
```

### Related_resource

`Related_resource` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Related_resource/description
---
```

This sub-schema is referenced by the following properties:

- [`referenced_by`](rdls_schema.json,,referenced_by)

Each `Related_resource` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Related_resource
collapse:
addtargets:
---
```

### Source

`Source` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Source/description
---
```

This sub-schema is referenced by the following properties:

- [`sources`](rdls_schema.json,,sources)

Each `Source` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Source
collapse:
addtargets:
---
```

### Period

`Period` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Period/description
---
```

This sub-schema is referenced by the following properties:

- [`Resource/temporal`](rdls_schema.json,/$defs/Resource,temporal)
- [`Event_set/temporal`](rdls_schema.json,/$defs/Event_set,temporal)
- [`Event/occurrence/empirical/temporal`](rdls_schema.json,/$defs/Event,occurrence/empirical/temporal)

Each `Period` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Period
collapse:
addtargets:
---
```

### Location

`Location` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Location/description
---
```

This sub-schema is referenced by the following properties:

- [`spatial`](rdls_schema.json,,spatial)
- [`vulnerability/spatial`](rdls_schema.json,/properties/vulnerability,spatial)
- [`Event_set/spatial`](rdls_schema.json,/$defs/Event_set,spatial)

Each `Location` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Location
collapse: geometry
addtargets:
---
```

### Gazetteer_entry

`Gazetteer_entry` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Gazetteer_entry/description
---
```

This sub-schema is referenced by the following properties:

- [`Location/gazetteer_entries`](rdls_schema.json,/$defs/Location,gazetteer_entries)

Each `Gazetteer_entry` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Gazetteer_entry
collapse:
addtargets:
---
```

### Geometry

`Geometry` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Geometry/description
---
```

This sub-schema is referenced by the following properties:

- [`Location/geometry`](rdls_schema.json,/$defs/Location,geometry)

Each `Geometry` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Geometry
collapse:
addtargets:
---
```

### Hazard

`Hazard` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Hazard/description
---
```

This sub-schema is referenced by the following properties:

- [`Event_set/hazards`](rdls_schema.json,/$defs/Event_set,hazards)
- [`Event/hazard`](rdls_schema.json,/$defs/Event,hazard)

Each `Hazard` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Hazard
collapse: trigger
addtargets:
---
```

### Trigger

`Trigger` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Trigger/description
---
```

This sub-schema is referenced by the following properties:

- [`Hazard/trigger`](rdls_schema.json,/$defs/Hazard,trigger)

Each `Trigger` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Trigger
collapse:
addtargets:
---
```

### Event_set

`Event_set` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Event_set/description
---
```

This sub-schema is referenced by the following properties:

- [`hazard/event_sets`](rdls_schema.json,/properties/hazard,event_sets)

Each `Event_set` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Event_set
collapse: spatial,temporal
addtargets:
---
```

### Event

`Event` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Event/description
---
```

This sub-schema is referenced by the following properties:

- [`Event_set/events`](rdls_schema.json,/$defs/Event_set,events)

Each `Event` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Event
collapse: hazard
addtargets:
---
```

### Footprint

`Footprint` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Footprint/description
---
```

This sub-schema is referenced by the following properties:

- [`Event/footprints`](rdls_schema.json,/$defs/Event,footprints)

Each `Footprint` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Footprint
collapse:
addtargets:
---
```

### Metric

`Metric` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Metric/description
---
```

This sub-schema is referenced by the following properties:

- [`exposure/metrics`](rdls_schema.json,/properties/exposure,metrics)

Each `Metric` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Metric
collapse:
addtargets:
---
```

### Cost

`Cost` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Cost/description
---
```

This sub-schema is referenced by the following properties:

- [`vulnerability/cost`](rdls_schema.json,/properties/vulnerability,cost)
- [`Losses/cost`](rdls_schema.json,/$defs/Losses,cost)

Each `Cost` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Cost
collapse:
addtargets:
---
```

### Probabilistic

`Probabilistic` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Probabilistic/description
---
```

This sub-schema is referenced by the following properties:

- [`Event/occurrence/probabilistic`](rdls_schema.json,/$defs/Event,occurrence/probabilistic)

Each `Probabilistic` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Probabilistic
collapse:
addtargets:
---
```

### Impact

`Impact` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Impact/description
---
```

This sub-schema is referenced by the following properties:

- [`vulnerability/impact`](rdls_schema.json,/properties/vulnerability,impact)
- [`Losses/impact`](rdls_schema.json,/$defs/Losses,impact)

Each `Impact` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Impact
collapse:
addtargets:
---
```

### Classification

`Classification` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Classification/description
---
```

This sub-schema is referenced by the following properties:

- [`vulnerability/se_category`](rdls_schema.json,/properties/vulnerability,se_category)
- [`Event/disaster_identifiers`](rdls_schema.json,/$defs/Event,disaster_identifiers)

Each `Classification` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Classification
collapse:
addtargets:
---
```

### Link

`Link` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Link/description
---
```

This sub-schema is referenced by the following properties:

- [`links`](rdls_schema.json,,links)

Each `Link` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Link
collapse:
addtargets:
---
```

### Losses

`Losses` is defined as:

```{jsoninclude-quote} ../../docs/_readthedocs/html/rdls_schema.json
---
jsonpointer: /$defs/Losses/description
---
```

This sub-schema is referenced by the following properties:

- [`loss/losses`](rdls_schema.json,/properties/loss,losses)

Each `Losses` has the following fields:

```{jsonschema} ../../docs/_readthedocs/html/rdls_schema.json
---
pointer: /$defs/Losses
collapse: cost,impact
addtargets:
---
```