Skip to content

← All sections

Nearest fire hydrants

Nearest fire hydrants mapped in OpenStreetMap, with distance. Community-mapped: presence and position are unverified, and absence means unmapped, not absent.

fire_hydrants13 fields13 of these fields open in the demo
Source
OpenStreetMap
Geography
Around the address
Reported stale after
47 days
Access
Requires an API key granted this section
Contract version
2
In packages
fire, civil_protection, fire_and_damage

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
6 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 6 Nov 2026
Newest record
6 Nov 2026
Municipalities with data
1

Measured 16 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
Open Database License 1.0
Declared redistribution
Share alike
Catalogue basis
Stated in catalogue evidence
Read the publisher terms →
Attribution and note

Shown from the contract in its original language.

© OpenStreetMap contributors

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.

  • Straight-line EPSG:25833 distances from the address point to the feature; not travel distance. Source features are imported as published, with their own accuracy and update cadence; updated_at is our import time.
  • © OpenStreetMap contributors, ODbL 1.0. Community-mapped; presence, name and position are unverified and absence means unmapped, not absent. Licence limits: ODbL is share-alike. Showing these records needs the attribution "© OpenStreetMap contributors" beside them, and a database you build from them and pass on or publish must itself be offered under ODbL, so the records cannot be folded into a proprietary dataset or resold under different terms. NLOD and CC BY terms elsewhere in this API do not apply to them.
  • Routes follow the car profile, from the address to the feature; ranking remains straight-line. Static modelled travel time excludes live traffic and emergency response. Road snapping is limited to 250 m at each end. Ferries may be included without timetable/wait guarantees. Graph source date is unverified unless supplied. © OpenStreetMap contributors, ODbL: https://www.openstreetmap.org/copyright
  • walk_route and cycle_route follow OSRM's foot and bicycle profiles on the same OpenStreetMap data: paths and stairs allowed on foot, road rules for bicycles; modelled times at profile default speeds, not measured.

Provider-contract fields

2 of 13 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.

FieldTypeRoleDemo
feature_idstring | nullcontextopen
labelstring | nullvalueopen
categorystring | nullcontextopen
municipality_codestring | nullcontextopen
updated_atstring | nullcontextopen
osm_typestring | nullcontextopen
osm_idinteger | nullcontextopen
straight_line_distance_minteger | null (m)valueopen
lonnumber | nullcontextopen
latnumber | nullcontextopen
routeobjectcontextopen
walk_routeobjectcontextopen
cycle_routeobjectcontextopen

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=fire_hydrants'

# 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/fire_hydrants?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.