Skip to content

← All sections

Waterworks serving the address's municipality (Mattilsynet)

water_supply22 fieldsNot in the demo
Source
Mattilsynet vannverk open data (vannforsyningssystem, vanntransportsystem, inntakspunkt, analyse)
Geography
Municipality
Reported stale after
21 days
Access
Requires an API key granted this section
Contract version
1

Available with: bought bundle or agreed plan (all fields) · Pricing

What this does not say

Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.

  • NOT address-specific: this is the list of waterworks Mattilsynet registers in, or that distribute in, the address's kommune (match_basis, address_specific=false). Mattilsynet publishes no supply-area polygons and no address-level connection, so which of these serves the address cannot be told from open data; ask the kommune or the water utility. Systems that serve 50 people or more and every municipally owned system are included; private small waterworks and private wells are not. match_basis says why a system is listed: distribution_system_in_municipality (Mattilsynet records a distribution system in this kommune), registered_in_municipality (the system's own kommune number), or owner_municipality_unplaced, the weakest: the extract gives the system no kommune at all (this is true of about half of the active systems, including most large municipal utilities such as Oslo's, Bergen's and Trondheim's) and it is listed because its municipal owner is this kommune. A municipal owner can also supply neighbouring kommuner, and a system with no kommune and a non-municipal owner cannot be placed, so the list can be incomplete.
  • persons_connected_in_municipality is the permanent residents Mattilsynet records on the system's own network in this kommune (null when not reported); persons_permanent, persons_max, households and cabins are the owner's annual report for the whole system, which can span several kommuner. source_types lists the intake source types (innsjø, borebrønn, elv/bekk, ...) and main_source_types those marked as the main source; intake positions are not published.
  • quality is the annual summary of drinking-water analyses reported for quality_year: samples required, samples taken and samples over the limit per parameter, with the median and maximum value in the parameter's own unit (E. coli per 100 ml, turbidity in FNU, pH, metals in mg/l or ug/l, per Mattilsynet's field documentation). A zero or a missing exceedance count is as reported by the owner; it is not a certificate of quality. No boil-water notice (kokevarsel), incident or outage is published as open data, so their absence here says nothing about whether one is in force: check the kommune and the utility.
  • For sole traders (organisasjonsform ENK) the system and owner names are the owner's own and are withheld (name_withheld=true); the people counts remain. last_inspection_date is Mattilsynet's last inspection or audit of the system. data_as_of is the extract date Mattilsynet states; the files are regenerated daily and owners report once a year.
  • Licence: NLOD 2.0 (Norsk lisens for offentlige data), as listed for Mattilsynet's "Vannverk - vannforsyningssystem" datasets on data.norge.no (files at https://data.mattilsynet.no/vannverk/). Attribution: Mattilsynet.

Fields

9 of 22 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.

FieldTypeRole
system_idstring | nullcontext
system_namestring | nullcontext
name_withheldboolean | nullcontext
supply_area_namestring | nullcontext
owner_namestring | nullcontext
organization_formstring | nullcontext
vreg_numberstring | nullcontext
match_basisstring | nullcontext
address_specificboolean | nullcontext
persons_connected_in_municipalityinteger | nullvalue
persons_permanentinteger | nullvalue
persons_maxinteger | nullvalue
householdsinteger | nullvalue
cabinsinteger | nullvalue
source_typesarray<string> | nullvalue
main_source_typesarray<string> | nullvalue
last_inspection_datedate | nullvalue
report_yearinteger | null (årstall)context
quality_yearinteger | null (årstall)context
qualityarray<object> | nullvalue
data_as_ofdate | nullcontext
fetched_attimestamp | nullcontext

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 --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643?include=water_supply'

# paginated, one section at a time
curl --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/water_supply?limit=25'

Why it cannot be tried here

This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.