Skip to main content
Beta! Dokumentasjonen er automatisk generert. Informasjonen kan være ufullstendig og inneholde feil, spesielt skjermbilder og videoer. Se Om hjelpesidene. Vi vil veldig gjerne ha innspill: Kontakt oss via «Fant du det du lette etter?» nederst, i chatten nede til høyre eller på support@placepoint.no – vi svarer så fort vi kan!

Catchment - methodology

This page brings together the definitions and assumptions behind catchment calculations in Placepoint. The travel distance tool (isochrones) is not available in Placepoint Fusion yet. This page will be updated when the feature launches.

Definitions​

  • Catchment (Norwegian: nedslagsfelt) is the combined area treated as reachable from a starting point, bounded by an isochrone.
  • Isochrone is the polygon that encloses every point you can reach within a given travel time using a given travel mode. The shape follows the road network and timetable data, not a circle.
  • Radius is a circle with a fixed length from the starting point, independent of the road network. Use it when you want to compare on geographical distance instead of travel time.

Travel modes and speed assumptions​

The isochrone calculation is based on actual road data, not a constant speed. A 15 minute car isochrone reaches further along a motorway than along a minor road with a 50 km/h speed limit.

Supported travel modes (once travel distance is available):

  • Car
  • Bicycle
  • Walking (5 km/h, set by an external data provider)
  • Public transport, based on Entur's national timetable for the selected arrival time

Minutes, not kilometres​

Isochrones are configured in minutes. There is no toggle to switch the calculation itself to kilometres. To compare on distance alone, place a radius measurement next to the isochrone.

Estimated grocery turnover​

The catchment layer can show estimated grocery turnover for the area the isochrone covers.

  • The estimate covers total grocery retail within the bounded area.
  • The underlying data is usually updated once a year.
  • The estimate does not distinguish between shops at the edge of the isochrone and shops further inside it.

When an isochrone or an estimate looks unexpected​

Common causes:

  • A sparse road network around the starting point. A car based isochrone comes out smaller than expected.
  • An arrival time outside rush hour. Travel times are shorter, so the isochrone is larger.
  • Public transport in the middle of the night. Services run rarely or not at all, so the isochrone is small.
  • A point near a motorway with a short time budget. The isochrone comes out unexpectedly elongated.

If it still looks wrong, contact support with the matrikkel or coordinate, the configuration, and the expected value against the actual one.

See also​

Sist oppdatert
Beta! Dokumentasjonen er automatisk generert. Informasjonen kan være ufullstendig og inneholde feil, spesielt skjermbilder og videoer. Se Om hjelpesidene. Vi vil veldig gjerne ha innspill: Kontakt oss via «Fant du det du lette etter?» nederst, i chatten nede til høyre eller på support@placepoint.no – vi svarer så fort vi kan!