Skip to content

← All sections

Walkability (15-minute city) score

Modelled walkability score for the address, from counts of groceries, transit stops, schools, cafes, pharmacies and other destinations within walking bands. A banded heuristic, and a zero count also reflects how well the underlying data covers the place.

walk_score17 fields17 of these fields open in the demo
Source
Approach walk-score model over OpenStreetMap (ODbL) and public registers
Geography
The address point
Reported stale after
60 days
Access
Requires an approved pilot customer and named section access
Contract version
1
In packages
neighbourhood_life, calculations

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
10 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured

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

Model and method

How much is within walking distance?

This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.

Result type
Calculation
Method
Index
Declared maturity
Marked stable in the catalogue
Reference comparison
No qualified comparison declared
Contract version
1
Model artifact and runtime version
Not established by this catalogue description
Inputs, headline fields and comparison basis

Declared inputs

  • OpenStreetMap
  • BRREG
  • schools
  • kindergartens
  • public-transport stops

Headline output fields

score

Declared comparison basis

none: a weighted count

Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.

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.

Computed over OpenStreetMap places (ODbL): whether the score is a derived database under ODbL share-alike is not settled. Pending legal review.

API warnings

The API returns these notes in warnings.

  • Counts within straight-line bands over the POI layers listed in coverage; the score is a banded heuristic, and a zero count reflects our POI coverage as much as the neighbourhood.
  • Licence: derived in part from OpenStreetMap (ODbL 1.0, share-alike). The score is a produced work and needs the attribution "© OpenStreetMap contributors" where it is shown; the per-address counts are database extracts, and passing them on in bulk can bring ODbL's share-alike terms with it. Approach has not cleared them for bulk redistribution under other terms, so treat the section as ODbL-encumbered. The other inputs are public registers under their own terms.
  • 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.

Provider-contract fields

1 of 17 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 | nullcontextopen
municipality_codestring | nullcontextopen
updated_atstring | nullcontextopen
scoreinteger | nullvalueopen
methodstring | nullcontextopen
grocery_within_500minteger | nullcontextopen
transit_stops_within_500minteger | nullcontextopen
playgrounds_within_500minteger | nullcontextopen
schools_within_1000minteger | nullcontextopen
kindergartens_within_1000minteger | nullcontextopen
cafes_within_1000minteger | nullcontextopen
pharmacies_within_1000minteger | nullcontextopen
libraries_within_1500minteger | nullcontextopen
sports_within_1500minteger | nullcontextopen
attractions_within_1500minteger | nullcontextopen
coveragearray<string> | nullcontextopen

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

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