-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Proposal] Add guidance to docs to instruct users to include key non-metadata in datasets themselves #56
Comments
Noting that we should instruct users to include these fields in the data files, not assume they will. |
Some of these are now being kept and incorporated into |
The fields listed in the initial description have all been removed. Renamed this issue to reflect the remaining task. |
@stufraser1 do the individual fields need to be listed somewhere? If so, we can add a new "what to include in risk datasets" page under how to publish risk datasets. Otherwise, the sentence added in #234 should be sufficient. |
@stufraser1 @matamadio to draft content. |
@stufraser1 draft content for review What to include in risk datasets (What is not included in metadata)?There is an important distinction between data content, data structure and the metadata schema. The RDLS provides a metadata standard but does not impose any specific data structure. HazardA hazard dataset contains, as a minimum, the intensity value at a particular location for the event or scenario represented. Aside from the hazard value and location, most information about the data is metadata, therefore part of the RDLS metadata schema. ExposureThe RDLS metadata schema can describe the main category of exposure, associated quantities and cost units, and taxonomy standard. Other attributes such as the taxonomy code or the quantity variable associated to each feature (e.g. replacement cost or number of people for a goven location) are part of the data itself. VulnerabilityThe RDLS metadata schema covers a fairly large amount of attributes and parameters to describe vulnerability datasets (models). The actual parameter values from a vulnerability relationship would be part of the data. LossThe RDLS metadata schema can accomodate attributes describing both geospatial and tabular loss data. Key metatada include the type of hazard and exposure considered, the type and unit of impact considered and related economic cost units. Impact and loss values are part of the data content. |
What is your proposed change?
Proposal to remove fields which are not consistent across the entire data file being described. This also includes fields which can be found within the data itself. Spreadsheet
Can you provide an example?
Fields suggested for removal:
anyOf.exposure.model.occupancy
anyOf.exposure.model.occupancy_time
anyOf.exposure.model.taxonomy_code
anyOf.exposure.model_add_attributes
anyOf.vulnerability.model.taxonomy_code
anyOf.vulnerability.specifics.par_names
anyOf.vulnerability.specifics.im_name
anyOf.vulnerability.specifics.im_units
anyOf.vulnerability.specifics.n_events
anyOf.vulnerability.specifics.n_assets
anyOf.vulnerability.specifics.is_fit_good
anyOf.vulnerability.specifics.is_edp_thre
anyOf.vulnerability.specifics.is_dm_factor
anyOf.vulnerability.specifics.is_casualties
anyOf.vulnerability.specifics.is_downtime
The text was updated successfully, but these errors were encountered: