search

UGS-GIO / geohaz

UGS Geologic Hazards Portal web application that compiles a large data set of geologic hazards data and displays it on an interactive web map
https://geology.utah.gov/apps/hazards
2 stars 0 forks source link

Add fault mapping and special study zones to hazards app #66

Closed emkleb closed 3 years ago

emkleb commented 3 years ago

Description of data you're adding to an existing layer/database As part of our contract deliverable, fault mapping and special study zones (SSZ) need to be added to the hazards database.

Faults Fault attributes and geometry should be copied from UGHP.UGHPADMIN.Qfaults_UBOT based on the fault numbers. The fault numbers in the app version should be completely deleted and replaced with the data from the SDE version.

Fault Numbers

Buffers Buffers should be added to the app from the SDE version "UGHP.UGHPADMIN.WFZ_Buffers." Note that these buffers need to be updated for the "SSZ" layer and "mapped areas" layer

Once you submit this issue, your data will be reviewed and checked off by the following people (using Github): -Product Manager -Data Manager -Technical Reviewer (only the text within the database/app: if it's in full sentence format) -Web Services Manager

marthajensen commented 3 years ago

@gordondouglass added a gdb for me to the following location: G:\Shared drives\UGS_Hazards\Fault Mapping\UBOT - Bear Lake-Oquirrh Fault Mapping

BUT I can't access that location. Should it be moved or would you rather I have access to the main UGS_Hazards folder?

I can access this folder: G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data

marthajensen commented 3 years ago

the faults have been moved to : "G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Working and editing geodatabase\Qfaults_Update_20210324.gdb"

Thanks @gordondouglass!

marthajensen commented 3 years ago

@emkleb

I will work on getting the qfaults ready for review. In the meantime, @gordondouglass is going to move the buffers into the review (working/editing gdb at "G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Working and editing geodatabase\Geologic_Hazards_Geodatabase_Review_Version.gdb") I'm not familiar enough with that dataset to do so.

Once both datasets are ready for review, I will post back on here to have you review them

emkleb commented 3 years ago

Martha-

We need to add "Hiscock and others, 2021" to the citation field for all of the fault numbers listed above.

marthajensen commented 3 years ago

@emkleb We are ready for a review! Please review the following mxd/datasets and table:

Open one of these two MXD's depending on your version of Arc (first one is 10.8, second is 10.7)

"G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Working and editing geodatabase\GeologicHazards_Final.mxd"

"G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Working and editing geodatabase\GeologicHazards_Final_10_7.mxd"

datasets/attributes to review in MXD: Quaternary Faults Project Areas Surface Fault Rupture Hazard Special Study Zone

review table at (scroll down for new Qfault data): "G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Final_Report_Tables\HazardUnitTextTable.csv"

emkleb commented 3 years ago

Based on a google meet conversation around noon, we need to re-review the SDE version of UBOT, and re-start the GIS review process.

I have completed another review of the UBOT SDE (UGHP.UGHPADMIN.Qfaults_UBOT).

Here are the fault numbers that need updating: Geometry: 2405 Attributes: 2545

We also discussed issues with ArcPro not selecting all of the faults when we are working on attributes. I also updated this github ticket with the number of entries that should be associated with each fault numbers.

marthajensen commented 3 years ago

@emkleb Gordon and I have implemented the changes to the Quaternary Faults dataset and HazardUnitTextTable and are now ready for another review.

Please review the following mxd/datasets and table:

Open one of these two MXD's depending on your version of Arc (first one is 10.8, second is 10.7)

"G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Working and editing geodatabase\GeologicHazards_Final.mxd"

"G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Working and editing geodatabase\GeologicHazards_Final_10_7.mxd"

datasets/attributes to review in MXD: Quaternary Faults Project Areas Surface Fault Rupture Hazard Special Study Zone

review table at (scroll down for new Qfault data): "G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Final_Report_Tables\HazardUnitTextTable.csv"

Thanks!

emkleb commented 3 years ago

Quaternary faults- Still doesn't have a link to the UGS report with it, but I am reluctant to change the "USGS_Link" field. I have added a new feature to be added to the app in github. Users will still be able to find the report in the app, just not from the Q-faults layer.

Checked:

Issues:

-Table issues: Faults with the 2399 fault number at the beginning of their "Hazard Unit" number have an issue with how the name is reported out. Most of the faults with 2399 name have a two part name, AND . Right now, only the OR the is showing up. -The table will also need to be updated once the attributes are updated for faults 2405, 2406 and 2396. -I'm a little concerned about 2406694qff (line 802) and 2406695qff (line 803). I don't see this issue in the attribute table (FaultNum 2406 being connected to "Toplif Hill fault zone" when it should be 2407). I was under the impression that the QFF hazard unit number for q-faults started with the fault number. If that is the case, then the QFF codes do not match all of the descriptions. I saw this issue for a few other faults. I've saved a version of the table "HazardUnitTextTable_ejk.xls" with some of these field highlighted.

For reference, if you ever want to check the fault number with the fault name, you can search this database (by using the "faultID" field: https://earthquake.usgs.gov/cfusion/qfault/query_main_AB.cfm?CFID=1983788&CFTOKEN=379a468fd6c7e623-5D4BD099-E73F-1F80-AA9B19054C3A818C

marthajensen commented 3 years ago

@emkleb

We are ready for another review

emkleb commented 3 years ago

Adam M and I have reviewed. There are some outstanding issues that Adam M identified, which will take more time to work through. To satisfy the contract deliverable, we should push this data up ASAP, and I will work on sorting out the other issues.

We are ready to move onto the next stage of review. Thanks!

marthajensen commented 3 years ago

@JCastleton Your turn for the qfaults data.

Please review the following mxd/datasets and table:

Open one of these two MXD's depending on your version of Arc (first one is 10.8, second is 10.7)

"G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Working and editing geodatabase\GeologicHazards_Final.mxd"

"G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Working and editing geodatabase\GeologicHazards_Final_10_7.mxd"

datasets/attributes to review in MXD: Quaternary Faults Project Areas Surface Fault Rupture Hazard Special Study Zone

review table at (scroll down for new Qfault data): "G:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Final_Report_Tables\HazardUnitTextTable.csv"

Once you are done, please post here and let us know! Thanks!

JCastleton commented 3 years ago

@marthajensen @emkleb I have reviewed the GIS and not found any issues just one question will the URL for the Bear Lake report come later? The table is good as well.

@marthajensen will having the volcanic data in the table affect the publishing?

I will send this to Steph for a quick review. I will comment here when Steph is done.

JCastleton commented 3 years ago

@emkleb please delete duplicate table when appropriate

emkleb commented 3 years ago

Deleted duplicate table from M:\Shared drives\UGS_Hazards_Geotech\Geologic Hazards Online Data\Final_Report_Tables

gordondouglass commented 3 years ago

URL is in there now.

On Tue, Apr 6, 2021 at 12:17 PM JCastleton @.***> wrote:

@emkleb https://github.com/emkleb please delete duplicate table when appropriate

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/geohaz/issues/66#issuecomment-814336645, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANNUAU3KNLTA664DCPYJD2DTHNF45ANCNFSM4ZZ3HTYQ .

-- Gordon Douglass, B.A., M.S. GIS Manager Utah Geological Survey Lead GIS Analyst Utah Geological Survey - Geologic Hazards

gdoug @.>lass@ @.>utah.gov @.***> Office: 801-538-4810 Mobile: 801-657-6981 1594 West North Temple Salt Lake City, Utah 84114

http://geology.utah.gov/

CONFIDENTIALITY NOTICE: This e-mail message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient but do not wish to receive communications through this medium, please so advise the sender immediately.

marthajensen commented 3 years ago

I talked to @JCastleton and the entire SSZ and project areas feature class can moved over to the LIVE gdb. I will do that, along with the qfaults feature class and the HazardUnitTextTable.

@emkleb do you want to take one last glance at the data in the mxd before it disappears and gets added to the app?

emkleb commented 3 years ago

I'm happy pushing it up as is. It's been reviewed thoroughly. I will be doing another update soon.

marthajensen commented 3 years ago

Ok - I'll move the version over to the publishing gdb and send it up to the app soon. I'll comment on here when its done

marthajensen commented 3 years ago

@emkleb @JCastleton the data is now live in the app. Popups, reporting tool, and relationships all are working. The only thing that is not working has to do with the link to Report_ID G19AP00072 in the mapped areas ( feature class - study_areas).

We need to have a conversation with @jjhi11 and @marshallrobinson to fix that. Please have a look at the app when you have time.

marthajensen commented 3 years ago

@emkleb @JCastleton. All the new data should be working now. The problem listed above - the report_id - is fixed . To make it work, we changed the mapped areas Report_ID field data from G19AP00072 to 65364 because the URL of the report references 65364, not the GP#

URL of report: https://geodata.geology.utah.gov/pages/view.php?ref=65364

I have changed the Report ID to 65364 in the review and live mapped areas to match what is on the web