GFDRR / rdl-standard

The Risk Data Library Standard (RDLS) is an open data standard to make it easier to work with disaster and climate risk data. It provides a common description of the data used and produced in risk assessments, including hazard, exposure, vulnerability, and modelled loss, or impact, data.

https://docs.riskdatalibrary.org/

GFDRR/rdl-standard Issues

[DATA] Critical infrastructure VULNERABILITY
Updated 10 days ago
[DATA] Standard administrative boundaries for risk processing and presentation
Closed 8 days ago2
[Proposal] Add project_url field.
Updated 2 months ago
[Proposal] Listing multiple exposure category for one dataset
Updated 2 months ago
[Proposal] Add more IMT
Updated 2 months ago
Metadata translator .json into .md
Closed 8 days ago1
[DATA] Push for UR24
Closed 19 days ago1
[Proposal] Attribution object information optional
Updated 8 days ago1
[Proposal] Forecast data - label H, E, L datasets as forecasts
Updated 4 months ago2
[Docs update] Make a reference to Exposure taxonomies in Schema reference Exposure taxonomy scheme
Updated 4 months ago1
[Docs update] additional details into developer_docs.md
Updated 10 months ago
[DATA] GEM 2023 - Hazard, Exposure, Vulnerability, Risk
Closed 8 days ago1
[Proposal] Add details to source attributes
Updated 10 months ago2
[DATA] Flood urban/national scale analyses
Updated 8 days ago1
Specs > CSV code-lists
Updated a year ago2
[Website] Transition to CMS
Closed 8 days ago4
[Docs update] guidance on deliberate use of additional fields
Updated a year ago
Branch setup after 0.2 release
Closed a year ago5
0.2.0 release and follow ups
Closed a year ago1
Review loss metadata modelling
Updated 9 months ago3
Add test to check all links in schema, codelists and documentation
Updated 10 months ago2
[Proposal] Socio-Economic Vulnerability layers are not hazard-related
Updated a year ago5
[Docs update] Specify off-topic: what is NOT risk data
Updated a year ago6
Tests: Add a check to validate required properties
Updated a year ago
Tests: Add a test to check that example JSON files are valid and do not contain additional fields
Updated a year ago1
Update schema URLs
Closed a year ago
[Website] Links, URLS and redirects
Closed 10 months ago11
[Schema] Declare different schemes for disaster id
Closed a year ago4
[Docs update] Change contact information
Closed a year ago
[Schema] Loss: Should hazard_id, exposure_id and vulnerability_id be optional?
Closed a year ago1
Tests: Add a test to check that diagram JSON is valid
Updated a year ago1
[Docs update] Schema reference introduction
Closed a year ago1
[Schema] url for a resource option and split into 2, one for access details and one for download
Closed a year ago1
[Schema] should taxonomy be optional in vulnerability?
Closed a year ago6
Specify the coordinate reference system to be used in the Location object
Closed a year ago2
Add a metadata package schema
Closed a year ago3
[Schema] Update `.coordinate_system` to recommend either EPSG or ESRI codes
Closed a year ago8
[Schema] review for camelCase field names that should be snake_case
Closed a year ago5
[Schema] Spatial coordinates format
Closed 4 months ago11
[DATA] Make RDL sharepoint folder public access (read)
Closed a year ago1
[Schema] Exposure costs and metrics
Closed a year ago12
[Schema] Hazard object (i.e. hazard type and process) required in both event_set and event?
Closed a year ago3
[schema/documentation] Clarify the purpose of links
Closed a year ago6
[Schema] add generalized_extreme_values to frequency_distribution codelist
Closed a year ago3
[Schema] add ISO 3166-1 alpha-3 to location_gazetteers.csv
Closed a year ago
[Schema] update dataset identifier description
Closed a year ago6
[Schema] Commercial licenses?
Closed a year ago2
[Docs update] Duplicated "probabilistic frequency" in the schema browser
Closed a year ago2
[Schema] Temporal object / period
Closed 10 months ago3
[Docs update] Update or remove mermaid flowcharts
Closed a year ago7