Skip to content
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] Hazard event location #71

Closed
odscrachel opened this issue May 24, 2023 · 4 comments
Closed

[Proposal] Hazard event location #71

odscrachel opened this issue May 24, 2023 · 4 comments
Labels
hazard Issues related to Hazard data proposal New feature or request

Comments

@odscrachel
Copy link
Contributor

What is your proposed change?

To create a new event.geographic_coverage field within the event object that sits within the hazard component. The field will have the following attributes

Title Field name Description Type
Event location event.geographic_coverage The names of the geographic areas covered by the event in the modelled scenario(s). array of strings

What is the context or reason for the change?

This replaces event_set.geo_area from rdl-schema_0_1.json. It was reasoned that this should be at event level e.g. for the same event_set, multiple locations (events) can be modelled. Spreadsheet link

@odscrachel odscrachel added the proposal New feature or request label May 24, 2023
@matamadio
Copy link
Contributor

This would be different from top-level subnational_coverage, which gives the summary of all locations (as list).

  • subnational_coverage (Location1_name, Location2_name)
    • hazard.event_set.event1.geographic_coverage (Location1_name)
    • hazard.event_set.event2.geographic_coverage (Location2_name)

@duncandewhurst
Copy link
Contributor

I think that our modelling and naming conventions for spatial/geographic coverage at the event level should be consistent with our approach at the dataset level. Suggest that we agree the dataset modelling first in #52 and then update this issue.

@odscrachel odscrachel added the hazard Issues related to Hazard data label May 30, 2023
@stufraser1
Copy link
Member

Proposal agreed in #52, so moving to agreed and ready.

@odscjen
Copy link
Contributor

odscjen commented Jul 11, 2023

updated in schema by #121

@odscjen odscjen closed this as completed Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hazard Issues related to Hazard data proposal New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants