Skip to content

Restrict events, event sets and triggers to a single hazard process type #356

@duncandewhurst

Description

@duncandewhurst

@matamadio @stufraser1 in the proposed 0.3 schema, the array-type Event.processes, Event_set.processes and Trigger.processes properties have been replaced by string .hazard_process properties, i.e. restricting events, event sets and triggers to a single hazard process type.

I can't see this change discussed anywhere in the issues. Please could you clarify the reason for the change?

For reference, the decision to make the properties arrays was originally taken in #91 based on input from @stufraser1 in #91 (comment):

(...) yes one hazard type can include >1 process type eg flood can include pluvial and fluvial data

There's no technical problem with the change to strings, but it wouldn't be possible to model the scenario described above under the proposed schema.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Changes needed

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions