SGID-based Query Layer Candidates for AGOL Migration

[stdavis]

There are many more layers that we should be asking DEQ about moving to AGOL. The layers that are currently being pushed to SGID (and consequently AGOL) via the DEQ forklift pallet may be candidates for moving to AGOL directly. These aren't as high of a priority since they are currently being updated in AGOL via forklift, but at some point, we may want to ask about them as well. I'm guessing that some of them won't be able to be moved since they are managed in non-spatial databases that require ETL. But there may be others that would be easy to move. Here is a list of them:

• Irrigated Crop Consumptive Use Zones
• Assessed Lakes
• Assessed Waters 2022
• Groundwater Permits
• Mercury in Fish Tissue
• Monitoring Locations
• UPDES Dischargers
• UPDES Storm Water
• Underground Injection Control
• Point Source Emissions
• Oil and Gas - Wells
• Permitting and Compliance - Approval Orders/NSR
• Permitting and Compliance - Operating Permits/Title V Permits
• Brownfields Other
• Brownfields Targeted
• CERCLA - CERCLIS List
• CERCLA - National Priorities List
• Enforceable Written Assurances
• Environmental Incidents
• Formerly Used Defense
• Military Munition Response Program
• TIER2
• Toxic Release Inventory
• Petroleum Storage Tanks
• Voluntary Cleanup Program
• Solid Waste Facilities
• Hazardous Waste and Used Oil
• Low Level Waste Disposal and Uranium Mills
• Air Monitoring by Station
• Hydrologic Units (HUC8)
• Pre-1978 Residential Structures

web services on mapserv

There are a few query layers that are still being reference by the mapserve service since they are not pushed to AGOL as part of SGID. I'll need to figure this out before deleting the map service.

• Dry Clean Facilities (Michelle is working on migrating this one to AGOL and said it would be done by 8/23/24)
• Municipal Separate Storm Sewer System (MS4) Permits

They can be easily called out from the config spreadsheet if they have a feature service URL that starts with:
https://services1.arcgis.com/99lidPhWCzftIe9K/ArcGIS/rest/services/

Note that these are SGID datasets so they would have to be deprecated in favor of the newly created DEQ AGOL datasets via porter.

[nathankota]

What is the right timing/sequence for asking about this? It may be another large effort/project along with the app rebuild. Would we want to consider easing them into a change like this, such that we offer to keep Forklift in place, but load the data into their AGOL? Or start introducing the full gamut of possibilities for some layers to be ETL'd, others managed directly in AGOL, and so forth?

[stdavis]

I'm sure that forklift will stay in place to some extent for the foreseeable future. I don't think that it would be bad to take a look at these and see which ones we think could easily be moved to AGOL. For example, the ones that the source is just a file geodatabase on a network share. I do think that for others, we will need to keep some sort of ETL process. But maybe it becomes palletjack rather than the full forklift stuff. I don't think that it is an emergency. Once I get the app rebuilt, I'll start digging into the backend/forklift stuff.

[stdavis]

I think that this means that we can shut down the enviro map service on mapserv! 🍾 I'll have to do some looking to make sure.

[stdavis]

/remind me to delete the map service in two weeks

I shut it down today.

[github-actions]

@stdavis set a reminder for 9/5/2024

[github-actions]

👋 @stdavis, delete the map service