What you can ask
- “What does UT Division of Oil, Gas and Mining have for the area or asset I'm working on?”
- “Pull the most recent UT Division of Oil, Gas and Mining records and put them in a table.”
- “What does UT Division of Oil, Gas and Mining cover, and how fresh is the data?”
About this source
Utah DOGM — O&G regulator. Uinta Basin operator side (Crescent / Ovintiv / KODA). - searchWells ⭐ ~40K surface wells with operator/county/status/cumulative - searchBottomHoles ⭐ ~33K bottomhole locations (deviated wells) - searchWellPaths ~12.5K directional drilling polylines - getWellByApi single-well lookup by 10-digit API upstream quirks: AGOL services.arcgis.com/ZzrwjTRez6FJiOq4 owner OGMGIS_utahDNR. Surf County is UPPERCASE STRING ('DUCHESNE'); BottomHole County is INTEGER code (Duchesne=7 / Uintah=24 / San Juan=19). Paths layer has only API + ConstructStatus (no operator/county). O&G permits are NOT a Feature Service — searchPermits dropped; APD-status wells (1772) are the substitute via searchWells.
Connector ID ut-dogm
Provenance
Freshness & coverage
› Methods (5)
Technical detail for developers: parameters, pagination, units, and freshness per method.
searchWells
readUT surface wells (~40K). Filter operator/county/wellStatus/wellType/bbox/near.
EntitieswellCounty any case. wellStatus/wellType take a code (P, OW) or label (Producing).
getWellByApi
readSingle-well lookup by 10-digit API. Returns the surface-well record.
Required paramsapiEntitieswellsearchBottomHoles
readUT bottomhole locations (~33K). Deviated wells. Filter constructType/county/deviatedOnly.
Entitiestrajectory, wellCounty is integer code on this layer; handler translates from county name.
searchWellPaths
readUT directional well-path polylines (~12.5K). Filter api/constructStatus/bbox/near.
Entitiestrajectory, wellNo county/operator/wellName upstream — join via API to searchWells.
getServiceInfo
readSchema + record counts for any of 3 services (UT Division of Oil, Gas and Mining).
Entitiesmetadata
