Revise Vs30 options
This is placeholder issue because these problems are visible in nshm-apps, they stem from underlying service metadata and can probably be fixed in nshmp-haz and various model repositories.
- Models report out of range VSs30 options in drop down menus: These presets come from
model-info.jsonfiles and need to be updated in the model repositories - The valid range (min max for vs30 numeric field) is coming from the service usage
- This is ok, but note currently the min max are hard coded (150 and 1500) and should instead be retrieved from the
SourceModel - Swagger docs are also hardcoded into annotations but need to use dynamic schema update like IMTs
- This is ok, but note currently the min max are hard coded (150 and 1500) and should instead be retrieved from the