WellLookupPublic well record intelligence Check an address →
Original source-field audit

What can you learn from a public well index?

A reproducible check of 300 domestic-classified entries across six indexes. This is a bounded field-availability audit, not a statewide study of well performance.

Published by WellLookup · Updated · Editorial standards and corrections

The question and the result

We asked whether a reader can obtain a numerical construction depth, reported rate and static-water field from specific public index queries. The table separates a missing value in a requested field from a measurement that was not part of that query. Neither implies the underlying paper or scanned file has no additional information.

Numerical values in the retained source rows, with exact field names
IndexRowsPositive depthNon-negative reported rateNon-negative static value
Maine5050/50WELL_DEPTH_FT32/50WELL_YIELD_GPM2/50WELL_STATIC_LEVEL_FT
Pennsylvania5041/50Well_Depth32/50Well_Yield_GPMNot in audited query
Colorado5017/50well_depth6/50yield16/50static_water_level
New Hampshire5050/50TOTD50/50YTQ29/50SWL; 1 source zero(s), verify meaning
Texas5050/50BoreholeDepthFtNot in audited queryNot in audited query
Minnesota5050/50depth_drllNot in audited query47/50swlavgmeas

Download all 300 audit rows (CSV)

A numerical value passes only a parsing and sign check. It is not validated against a physical well. In particular, source zeros require their original meaning to be checked; a numeric zero is retained separately from blank or unparseable data.

How to reproduce the audit

  1. Select the first 50 rows explicitly classified domestic in each index, ordered by that service's object identifier. These are convenience samples with no randomization or geographic balancing.
  2. Request only the documented allowlisted fields, without geometry, owner names or street addresses. Retain the exact IDs, query URL and UTC retrieval time.
  3. Count finite positive numbers for the selected depth field, and finite non-negative numbers for the rate and static fields. Keep absent, blank, negative and unparseable values out of those counts.
  4. Do not fill a missing drilled-depth value from a different field: Minnesota's drilled and completed depths are separate. Do not replace an unrequested yield field with another measurement.
  5. Use the retained-ID query to recheck those entries. A later first-50 selection can differ if an agency changes its inventory or identifiers.

What this sample cannot tell you

Low object identifiers can cluster in particular places, periods or source batches. The samples do not estimate statewide completeness, compare states' well quality, represent all households or prove that a record belongs to a parcel. We have not audited every source field, accessed every scanned log, inspected any well or tested any water. No independent professional review has been completed for this audit.

Texas's table uses BoreholeDepthFt, not a verified completed-well depth. Its filtered query does not retain yield or static level. Minnesota's table uses depth_drll and swlavgmeas, an average-measurement field, not a fresh water-level reading. Pennsylvania's selected query does not contain a static field. Numerical rates in the other indexes preserve each source's historical meaning and test context; they are not interchangeable measures of present household supply.

Use the gaps to ask a better question

If a needed field is absent, trace the identifier to the full filing or ask the agency. If a nearby point has the wrong use or uncertain location, resolve relevance before comparing measurements. The annotated log guide and property document checklist show the next steps.

Prepared and published by WellLookup. Corrections: evidence and corrections policy. Retained-state-data SHA-256: 95e97cd6fbba4817437d7e0c1bb8fbe8d50f00c186b3d858a83f372a6ff9a3c8. This checksum identifies this release's stored state data; it is not a certification of source accuracy.