Nearby listed security-company offices

Listed offices ranked by straight-line distance among uniquely geocoded entries. Offices are not verified dispatch bases; neither proximity nor optional road travel is guard response time.

nearby_security_offices23 fieldsNot in the demo

Source: Securitas public office directory; Kartverket address geocoding
Geography: Around the address
Reported stale after: 30 days
Access: Requires an approved pilot customer and named section access
Contract version: 2
In packages: safety

Read about this data source →

Status right now

State: Not measured yet
There is no age measurement for this section yet, or it is measured when requested.
Last loaded: not measured
Data freshness evidence: Not measured yet
Unverified: only collection time is known.
Newest record: not measured

Measured 12 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: approved pilot customer and named section access

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.

Securitas public directory factual office snapshot; exact customer redistribution terms not yet adjudicated. Kartverket geocoding does not license the publisher directory. No dispatch coverage or response-time data supplied. Pending legal review.

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.

Only Securitas is included: 41 published directory entries, 29 uniquely geocoded and 12 excluded from proximity ranking. This is not a complete security-provider or patrol network.
Coordinates identify the matched official address point, not a verified office entrance or vehicle access point.
Unresolved/conflicting directory addresses are excluded from proximity ranking; nearest means nearest among the geocoded subset, not the complete published directory.
Technical offices may share premises with another office entry. Entries are not counts of patrols, bases or available guards.
Response time, service coverage and dispatch-base status are unverified. Do not infer an Alarmly/Securitas agreement or service availability.
Publisher source-as-of is unknown; collection time is not a publisher update time. Redistribution terms remain unreviewed.
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 23 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.

Field	Type	Role
office_id	string	context
provider	string	context
office_name	string	value
office_kind	string	context
street_address	string	context
postal_code	string	context
postal_place	string	context
address_id	string	context
lat	number	context
lon	number	context
geocode_status	string	context
source_url	string	context
collected_at	string	context
source_as_of	string \| null	context
straight_line_distance_m	number	context
distance_method	string	context
response_time_seconds	number \| null	value
response_time_status	string	context
dispatch_base_status	string	context
coverage_status	string	context
route	object	context
walk_route	object	context
cycle_route	object	context

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_security_offices'

# 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_security_offices?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.