Open matamadio opened 10 months ago
Sounds good to me, suggest adding this content to a new 'What's not in scope?' page at the end of the introduction.
Any Base data from the OpenDRI Index:
I believe there is a grey zone for ALL exposure data, no? and maybe value in describing raw data that was used in the case there is no pre-existing exposure ready dataset?
From @stufraser1 on today's check-in call - these are not risk datasets, but they can be listed in the sources
section of RDLS metadata for datasets that use these as sources. The suggested page can include an explanation of the use of sources
and an example in JSON/tabular format showing the risk dataset title and description and the sources field.
@stufraser1, @matamadio and @pzwsk to agree on content.
Draft text to be included in the page, for revision (@stufraser1):
Risk analytics often require ancillary data to develop hazard, exposure and vulnerability data and to provide context for mapping and visualization. These may be geospatial or non-geospatial data.
The following list of data are commonly part of the data package produced within a risk assessment project, but are not themselves considered risk data. As such, these elements are not meant to be described using the RDLS, but by using the source
object, they can be included as a source for the risk data produced from them.
These elements include:
There's already some non-risk data in the RDL collection, such as https://datacatalog.worldbank.org/int/search/dataset/0064179/Central-Asia-river-network--MERIT-Hydro-data-
What is the context or reason for the change?
After discussion with fellows, we recognize the need to specify which kind of data are not directly risk-related and as such are not meant for the RDLS - and on the other side, the schema might be unable to represent them properly.
The following is a list of common items that might be present in risk analytics as ancillary data (e.g. for visualisation), but are not strictly risk data:
Please add any I might forget.
What is your proposed change?
Add a section in the documentation or in the website to explain which data are not meant for the RDL.