Registered wells near the address
Registered wells near the address from NGU's GRANADA borehole registry: counts of groundwater and energy wells and the distance to the nearest of each. Zero does not prove there is none.
Status right now
Measured 22 Nov 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.
Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing
Source terms and reuse
These are declarations from the catalogue contract, not a new rights approval. Customer access, source agreements and privacy need separate assessment. A licence label does not establish coverage or reviewed content.
- Declared licence or terms
- unverified
- Declared redistribution
- Not established
- Catalogue basis
- Unverified
API warnings
The API returns these notes in warnings.
- Counts and nearest distances from the NGU GRANADA borehole registry within 2 km. Registration is mandatory for drillers so modern coverage is good, but historic wells are under-registered — zero is not proof of no well.
- A nearby groundwater well can indicate private (non-municipal) water supply; energy wells indicate geothermal heating. This is registry proximity, not confirmation of this property's own supply.
Provider-contract fields
5 of 5 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| wells_within_500m | integer | null | value | open |
| groundwater_wells_within_500m | integer | null | value | open |
| energy_wells_within_500m | integer | null | value | open |
| nearest_groundwater_well_m | integer | null | value | open |
| nearest_energy_well_m | integer | null | value | open |
Fetch this section
Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
-H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
'https://api.approach.no/api/v1/addresses/285717643?include=wells'
# paginated, one section at a time
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
-H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
'https://api.approach.no/api/v1/addresses/285717643/sections/wells?limit=25'Try it now
This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.