Conversation
…ow to use, showing/hiding form fields as a consequence (WIP)
…sponding radio button
… corresponding radio button is selected
…d (set to 'UserProvided' by default)
…ata' button in the states 'initial' and 'running'
…also to get the preferred finite fault
…e of the available nodal planes and populating rake, dip and strike subsequently
…hes use_pnt_rup_from_usgs and build_rup_from_usgs
…t actually selectable and use the chosen value in the calculation)
…d the magnitude saling relationships
… reading data from finite fault
| ffs = products['finite-fault'] | ||
| ff = _get_preferred_item(ffs) | ||
| p = ff['properties'] | ||
| # TODO: we probably need to get the rupture coordinates from shakemap_polygon.txt |
There was a problem hiding this comment.
Anirudh says
the downloadable rupture polygon files are not very reliable or consistent in format. For instance, the finite fault polygon file for the 2024 Hualien earthquake does contain the rupture coordinates: https://earthquake.usgs.gov/product/finite-fault/us7000m9g4_1/us/1712690873099/shakemap_polygon.txt, but the 2023 Kahramanmaraş finite fault polygon files are empty: https://earthquake.usgs.gov/product/finite-fault/us6000jllz_1/us/1676951251912/shakemap_polygon.txt and https://earthquake.usgs.gov/product/finite-fault/us6000jlqa_1/us/1676676771092/shakemap_polygon.txt
On the other hand, the rupture.json file from the ShakeMap downloads page is reliable and consistent
so we should never read the polygon and you can remove the commented code below.
….xml to the temporary file
2 participants
No description provided.