Nearest geocoded police premises
The ten nearest known police premises by straight-line distance, with name, address and optional car, walking and cycling routes. Most matches rest on registered names, so a premises is not a verified public service.
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
Attribution and note
Shown from the contract in its original language.
Combines several publishers named in source; each one's terms apply.
API warnings
The API returns these notes in warnings.
- Ten nearest known premises by straight-line UTM33 distance; incomplete coverage, no opening-hours or emergency response guarantee. Most matches use registered names, not verified public services. Reviewed identity/address exceptions include Grønland (Oslo district office), checked against Politiet on 2026-09-27; fetched_at is the register retrieval time, not a renewed operational verification.
- 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 12 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 |
|---|---|---|---|
| id | integer | null | context | open |
| org_nr | string | null | context | open |
| station_name | string | null | value | open |
| address | string | null | context | open |
| lat | number | null | context | open |
| lon | number | null | context | open |
| geocode_status | string | null | context | open |
| straight_line_distance_m | number | null (m) | value | open |
| fetched_at | string | null | context | open |
| route | object | context | open |
| walk_route | object | context | open |
| cycle_route | object | context | 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=nearby_police_stations'
# 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/nearby_police_stations?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.