Colorado GIS Well Location Reconciliation Study 2026: Research question and scope
A well marker on a public map is useful, but its meaning depends on the layer, geometry role, coordinate system, and time observed. This study provides a reconciliation method for Colorado permit coordinates, legal descriptions, downloadable attributes, imaged documents, and GIS points. It is built for map-support workflows that prepare exceptions for a land or survey professional rather than make boundary conclusions.
The unit of analysis is one public source observation at one access time. Facts are limited to what an official route or artifact displays. Analysis compares those facts. Inferences are labeled and state the evidence that would confirm them. Uncertainty includes missing images, unclear versions, conflicting identifiers, unavailable fields, and undocumented intervals. This study does not decide title, ownership, boundaries, regulatory compliance, engineering questions, or legal effect.
Name the geometry before comparing it
Classify each location as proposed surface, approved surface, as-drilled surface, bottom-hole, path or lateral, facility, parcel reference, or another source-defined role. Two coordinates can both be accurate while representing different physical or administrative objects. A distance calculation is meaningless until geometry roles are compatible.
Capture the official layer name, feature identifier, displayed attributes, access time, and any metadata or legend that explains the layer. A screenshot can aid review but should not replace the underlying values and query record. Preserve the map scale and visible context when the visual relationship is material.
Retain coordinate reference and precision
Store coordinates as published, including sign, decimal precision, direction labels, and stated datum or coordinate reference system. If the datum is not stated, mark it unknown. Do not infer it from the numerical range. Any transformation into a working map system should record the source CRS, target CRS, transformation method, software, and output precision.
Avoid reporting calculated distance more precisely than the inputs support. Rounding can create apparent movement, and an unknown datum can produce a systematic shift. The reconciliation table should display original values beside transformed values so a reviewer can distinguish source differences from processing differences.
Link legal descriptions cautiously
Legal descriptions, survey references, section-township-range fields, parcel layers, and coordinates are related evidence, not automatic substitutes. Transcribe the source wording and page locator. If a legal description is parsed into components, retain the original and document the parser or manual rule.
A point falling within a mapped polygon does not prove title, lease inclusion, surveyed boundary, or regulatory compliance. Parcel and survey layers may have their own vintages and accuracy limits. The administrative output can identify consistency or a potential exception, while a qualified land or survey professional determines significance.
Use a reconciliation matrix
Build one row per source observation and columns for identifier, location role, source role, legal description, native coordinates, datum, transformed coordinates, precision, stated date, access time, and locator. Compare only like roles first. Then describe cross-role relationships explicitly, such as a proposed surface point versus a later displayed surface point.
Classify results as consistent within stated precision, explainable role difference, unresolved datum difference, identifier conflict, or material unexplained variance. Set thresholds according to the client's review criteria; this study does not prescribe a universal tolerance.
Escalation and review controls
Escalate when source roles are unclear, identifiers compete, datum is absent and the difference matters, a bottom-hole point is presented as surface, legal descriptions conflict, or the map relationship could affect a professional decision. Include the original artifacts, map observation, calculations, and assumptions.
A second researcher should reproduce the feature query and transformation from saved inputs. This public-source study did not test survey-grade accuracy, private parcel data, field measurements, or agency back-office geometry. Its purpose is to make GIS support transparent enough that spatial uncertainty is visible before a decision is made.
Operational worksheet
The following fields form a minimum worksheet for this study. They are intentionally observation-centered: a later value creates another row instead of overwriting the earlier evidence.
- feature identifier: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning. Keep any cleaned or derived value in a separate column.
- geometry role: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning.
- layer name: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning.
- legal description: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning. Keep any cleaned or derived value in a separate column.
- native coordinate: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning.
- stated datum: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning.
- transformation rule: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning. Keep any cleaned or derived value in a separate column.
- display precision: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning.
- calculated variance: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning.
- review class: Record the literal source value, the artifact or interface that supplied it, and the event date or access time that gives the observation its temporal meaning. Keep any cleaned or derived value in a separate column.
At handoff, sort the worksheet by source event rather than by the order in which files happened to be found. Attach an exception owner and next action to every material conflict. If a field is unavailable, record the attempted source and query instead of filling the gap from assumption.
Methodology and limitations
We reviewed the official Colorado and federal source routes listed below on October 6, 2026. For each route, the method records the publisher, interface, query or document role, source-native identifiers, displayed values, event-specific dates, access time, and a reproducible locator. Material files should be preserved with byte counts and SHA-256 hashes. Derived fields and normalized keys remain separate from source strings.
This was a source-architecture and workflow study, not a statistical sample of Colorado wells, filings, orders, or database errors. It did not test authenticated features, agency back-office systems, every query combination, physical records, subscription sources, client files, or later changes to the interfaces. A negative result means only that the documented query returned no match at the recorded time.
Niche-specific conclusion
For Colorado GIS well-location reconciliation, remote land support creates value by preserving and organizing evidence, not by collapsing uncertainty. A defensible packet lets the authorized professional see each source in its proper role, reproduce the material joins, identify changes across time, and focus judgment on a short exception list. That directly supports title research, data entry, GIS coordination, and document preparation while keeping professional decisions with the responsible reviewer.
Sources
- ECMC Home and Public Records Directory — Colorado Energy & Carbon Management Commission. Official entry point for Commission programs, public records, data, maps, permits, and regulation. Checked October 6, 2026.
- ECMC COGIS Data Search — Colorado Energy & Carbon Management Commission. Official COGIS search entry point for well, facility, production, and inspection records. Checked October 6, 2026.
- ECMC Data Downloads — Colorado Energy & Carbon Management Commission. Official entry point for downloadable Colorado oil and gas datasets. Checked October 6, 2026.
- ECMC Imaged Document Search — Colorado Energy & Carbon Management Commission. Official public route for imaged well and regulatory documents. Checked October 6, 2026.
- ECMC GIS Online — Colorado Energy & Carbon Management Commission. Official map entry point for spatial research. Checked October 6, 2026.
- Colorado Department of Natural Resources — Colorado Department of Natural Resources. Official department entry point used to confirm agency and program context. Checked October 6, 2026.
- Code of Colorado Regulations — Colorado Secretary of State. Official state rules publication and search system. Checked October 6, 2026.
- Colorado Information Marketplace — State of Colorado. Official state open-data catalog used to distinguish catalog records from regulator records. Checked October 6, 2026.
- Federal Oil and Gas Program — Bureau of Land Management. Official federal program source used to separate federal and Colorado jurisdiction. Checked October 6, 2026.
- Oil and Gas Data — U.S. Energy Information Administration. Official federal statistical-data directory used to distinguish aggregates from asset records. Checked October 6, 2026.
Frequently asked questions
Is a current ECMC screen the complete historical record?
No. It is a dated public observation. Earlier applications, images, orders, corrections, downloads, or archived material may be needed to reconstruct history.
Can a support team make the final professional determination?
Support staff can locate, preserve, transcribe, compare, and route authorized evidence. Qualified reviewers remain responsible for title, legal, survey, engineering, regulatory, and other professional conclusions.
What should happen when official sources conflict?
Keep both observations, describe the field-level difference, record each locator and date, and open a focused exception. Do not overwrite one source or invent a reason for the variance.
If your team needs a review-ready Colorado GIS well-location reconciliation packet, Book a free consultation.
