Advanced Searches

[stdavis]

• [x] county
• [x] city
• [x] zip
• [x] street address
• [x] name (not sure how to implement this)
• [x] id (ditto)
• [x] shape
• [x] nhd stream name
• [x] coordinates

[nathankota]

Seeing some different results for identical queries b/t prod and dev.

Layers searched

DDW: GWPZ DAQ: Oil & Gas Wells and Air Monitoring by Station DERR: Water Rights POD DAQ: Air Monitoring Stations

County Test

Juab

Prod app results

Dev app results

Beaver

Prod

Dev

City test

Price

Prod

Dev

Zip test

84106

Prod

Dev

Street address

4315 S 2700 W, Taylorsville; buffer = 3 miles

Prod

Dev

ID

4304530005 (Oil and Gas Wells)

Results were the same, but the dev app zoomed way father in than prod, and I had to zoom out to see where the point was. Matching the zoom level for single returned points with prod might be worth a try.

Prod

Dev

06009WS001 (Groundwater Protection Zones)

Prod

Dev

NO RESULTS

Shape

Polygon (in about the same area)

Results were different

Other Shape search comments

• Is it correct that only polygon search areas can be created?
• Not sure what the purpose of the arrow (Select feature) or the back and forward arrows are on the toolbar. They don't seem to do anything, and the back/forward arrows are never activated on the toolbar.
• Can't draw a point or line and buffer, like prod

NHD Stream Name

Results were different for each test query, but the searched stream names went to the same location, which is good.

Little Cottonwood Creek (Salt Lake)

Prod

Dev

Coordinates

• The coordinate zoom/search worked the same in both apps for UTM and Decimal Degrees, but the results continued to be different.
• DMS did not zoom to the same location in prod and dev (see below)
• I like how the prod app assumes negative for longitude, rather than having to enter the negate operator on the dev app
• I also like how the dev app calculates the location as you type, rather than having to click Zoom, like in prod

UTM 463089.1, 4195327.42, 1 mile buffer

Prod

Dev

Degrees minutes seconds

• The dev app did not zoom to the same location as prod, and prod was correct (confirmed via Atlas)
• Tested DMS coordinates:
  • -112, 22, 36.19 / 37, 44, 59.6
  • -109, 33, 20.3 / 37, 17, 3.26

[stdavis]

@nathankota This issue is ready for another look in staging.

I focusing on getting the results in the new app to match what Pro showed me for the same data. I didn't spend time trying to figure out why the old app differed.

This feedback was invaluable as it pointed me to some bad assumptions in how I was searching in the new app. I feel far more confident in the results now.

Points of Diversion

Search: Juab County (9/8/2023) New App: 5454 Old App: 3603

Queries in Pro:

New App after bb0a992498bb4cc9ab8c9869cdd4f235ef9b23f3: 5457

Ground Water Protection Zones

Search: Juab County (9/19/2023) New App: 99 Old App: 144

Queries in Pro:

New App after 88303030c54ff3f234f7347cf29e8f24c4e9b103: 149

Shape

Is it correct that only polygon search areas can be created?

Yes, for now. This was an oversight on my part. Let me know if you want me to add the missing functionality or wait for them to ask for it.

Not sure what the purpose of the arrow (Select feature) or the back and forward arrows are on the toolbar. They don't seem to do anything, and the back/forward arrows are never activated on the toolbar.

These are default controls for undo/redo during drawing. They seem to be working for me. Let me know if you think that we should just remove them.

Zoom Levels

Results were the same, but the dev app zoomed way father in than prod, and I had to zoom out to see where the point was. Matching the zoom level for single returned points with prod might be worth a try.

I set the max zoom level to 17 which should prevent a blank map. This is zoomed in a little further than prod but I think that it will be useful for features that are not in the middle of the Great Salt Lake. :)

Address Buffer

I didn't have a great way of testing this since I couldn't reproduce the exact same buffer in Pro.

This is the buffer function that I'm using in the app after projecting the point to UTM: https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-geometryEngine.html#buffer

Coordinates

DMS did not zoom to the same location in prod and dev (see below)

This was a bug that I fixed.

I like how the prod app assumes negative for longitude, rather than having to enter the negate operator on the dev app

I updated the app to assume negative for longitude and also added the suffix symbols similar to the old app.

[nathankota]

I've done some additional testing and I'm ready to close this down as it is, and we can accumulate feedback from the DEQ testing team for any new issues.