Closed marshallrobinson closed 3 years ago
The following email from Emily will influence the naming convention, but for right now, make sure that the fault zone/name/section/strand syntax matches what is found in the qFaults app: https://geology.utah.gov/apps/qfaults/index.html
---------- Forwarded message ---------
From: Emily Kleber <ekleber@utah.gov>
Date: Mon, Apr 27, 2020 at 5:53 PM
Subject: Re: fault comments
To: Jessica Castleton <jessicacastleton@utah.gov>
#1 Fault Name is empty when Faults are part of Fault Zone (WFZ)There are 4 fields that comprise the overall fault name in the Q-fault database. This is inherited from the USGS version of the Q-faults database, and cannot be avoided. It is a cumbersome standard we need to use. I suggest asking Gordon about the "label" field that he uses to label the q-faults database as a work-around.Q-faults schema document- https://docs.google.com/document/d/ 1yyhlG1Q9Ic2S2IQeOFhvuxYfozq0q w5x6QnO3D2mQ5U/edit?usp= sharing FaultZone(Text data type)
Fault zone name, applied to faults comprising two or more named sections.
Example: Wasatch fault zone, East Cache fault zone
FaultName(Text data type)
Fault name, applied to faults that are not subdivided into named sections (equivalent to faults in the Q fault database that have an assigned fault number, but no letter).
SectionName (Text data type)
Fault zone section name, applied to named subdivisions of a fault zone (equivalent to faults in the Q fault database that have a letter appended to the fault number).
StrandName(Text data type)
Named subdivision of a section of a fault zone, formal or informal.
On Mon, Apr 27, 2020 at 5:17 PM Jessica Castleton <jessicacastleton@utah.gov> wrote:#1 Fault Name is empty when Faults are part of Fault Zone (WFZ)#2 Hide Fault Name category in those cases#3 Nothing gets highlighted when clicking on segments#4 Fault Zone names need to be clickable and longer descriptions should show up (like on qfaults app)#5 Search capabilities from qFaults app need transferred into this app--Jessica J. Castleton, P.G.GeologistHazards MappingUtah Geological Survey1594 W. North Temple, Suite 3110Salt Lake City, Utah 84114-6100O: 801.537.3381F: 801.537-3400M: 801-390-3665--Emily KleberHazards GeologistUtah Geological Survey(801) 537-3380c. (530) 204-8923
1594 West North Temple
Salt Lake City, Utah 84114-6100
I do not understand what is wrong withe faults in the app Here is the results in the current app Here are the results from the new app
For the same fault
Also the service for searching faults is here:
https://webmaps.geology.utah.gov/arcgis/rest/services/Hazards/Faults_Quaternary/MapServer
Hazards App:
qFaults App:
So I think the current app is pulling the info in the header from the Label field. Whst field is the new app pulling the header info from?
On Tue, Apr 28, 2020 at 3:48 PM marshallrobinson notifications@github.com wrote:
Hazards App: [image: image] https://user-images.githubusercontent.com/5225390/80540924-78d3ba80-8967-11ea-80d4-6b10b805cfcd.png
qFaults App: [image: image] https://user-images.githubusercontent.com/5225390/80541000-9bfe6a00-8967-11ea-905b-1a6818e957df.png
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/geohaz/issues/13#issuecomment-620873161, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANNUAU75ZTNC3G6OREC2SQ3RO5FJZANCNFSM4MTCKDKA .
-- Gordon Douglass, B.A., M.S. GIS Manager Utah Geological Survey Lead GIS Analyst Utah Geological Survey - Geologic Hazards
gdoug gdouglass@utah.govlass@ gdouglass@utah.govutah.gov gdouglass@utah.gov Office: 801-538-4810 Mobile: 801-657-6981 1594 West North Temple Salt Lake City, Utah 84114
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.
I've been in a conversation today w/ @mikehylland, and @emkleb about whether or not we were going to maintain both the qFaults app and Hazards Portal simultaneously. I mentioned that this Github issue tracks the last couple of things that the qFaults does that the Portal does not yet do.
Closing this issue is one of my team's priorities; however, I know that the way the qFaults data is put together for the Hazards Portal may not allow for an exact transfer of functionality (specifically search functionality). Do we want to transfer over the "search by parcel" functionality?
I think that highlighting segments and bringing back fault zone summaries is a must though. I'm okay with getting those specific things done before retiring the qFaults app, but I would really prefer not massage any future qFaults data additions for both apps.
@jjhi11 Looks good overall, the search functions have gotten better, but in order to match what was done before will be much more time-intensive and can be moved to its own issue (will have to be saved for a later).
A couple things before we close this:
-please add Fault Strand under Fault Section in qFaults popup -add following CSS - "cursor: pointer" to the underlined fault zones in qFaults popup -remove top: 314px from .help-tip img CSS property
Looks good @jjhi11, go ahead and make this the live version.
Legend/Popups
Hazardous Faults