Open emkleb opened 3 years ago
Thanks for the heads up. In my opinion, further discussion may be necessary about the direction we're taking this web application. Paleoseismic trenches are not geologic hazards (which is the current scope of this web app), but that does not mean we can't expand the scope of the application if that is a priority for the application's users.
I'm going to open up a separate conversation here (https://github.com/UGS-GIO/geohaz/discussions/73) so we can discuss this more fully outside of this specific issue.
Adam is working on the data for this right now - it is also discussed here: https://github.com/UGS-GIO/geohaz/discussions/73
All - Furter discussion has occured between myself, Mike, Steve, and Jessica and we've decide to add the paleoseismic trench data to the hazards portal. I'm updating our feature class containing this data (currently on the Hazards SDE). This data will just be a simple point feature class with some basic attributes about each trench location. For now, it only contains research-level trenches, NO consultant trenches, but we may explore adding that data in the future.
A couple things we'd like to have available in the pop-up in the hazards portal:
I am working on making sure all the locations are updated and correct on the haz SDE right now. I will be done with that shortly, and then I can start working on how to link sites to data in the geochron DB.
chatted with Adam about this and he will add project name and project id fields to the data in order to link them
Why do you feel this application needs what you're requesting? Steve is requesting an additional layer to the "Earthquake Hazards" group of layers. This would be point layer with attributes related to paleoseismic trenches in Utah.
Describe the solution you'd like and why it builds value This feature will help people identify where trenching data are, and access it quickly.
Additional context Working on finalizing the data and getting it through review.