OSM Network Reader Defaults
All defaults in OSM are either country specific or not. This is why each OSM reader requires a country of origin to be provided upon creation. If no country is provided all country specific defaults will fall back to the “Global” defaults.
The following defaults are country specific:
The following defaults are not country specific:
- Lane configuration defaults
- Activated mode defaults
- Activated OSM highway type defaults
- Activated OSM railway type defaults
- Activated OSM waterway type defaults
Speed limit defaults
The speed limit on an OSM way in this OSM reader is based on three components:
- OSM way type (e.g., highway=primary)
- Country where the road resides in (e.g., Australia)
- Is the OSM way in an urban area or not
the OSM way type is collected from the road being parsed, the country is available from the OSM reader upon creation and whether the OSM way is in an urban area or not, is currently a global setting configurable via the OSM reader’s highway settings.
Presently, defaults for the following countries are available out-of-the-box:
- Australia
- The Netherlands
- Global (default fall back option)
The Global default is applied when the country is not yet supported.
More countries will be added in due time
The default speed limits for road infrastructure are directly based on the defaults as proposed by OSM itself on the following Wiki pages:
- https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Maxspeed
- https://wiki.openstreetmap.org/wiki/Default_speed_limits
These values are not always complete for all OSM way types and therefore have a look at the Planit JavaDoc if you want to know the defaults adopted for those OSM ways that are not listed. Also, in some very rare cases Planit deviates from the OSM defaults in case they are known to be incorrect or very unlikely.
The global defaults per OSM highway type (urban and non-urban) are provided below for the reader’s convenience:
| OSM highway type | Urban speed limit (km/h) | Non-urban speed limit (km/h) |
|---|---|---|
motorway |
100 | 120 |
motorway_link |
100 | 120 |
trunk |
80 | 100 |
trunk_link |
80 | 100 |
primary |
60 | 100 |
primary_link |
60 | 100 |
secondary |
50 | 80 |
secondary_link |
50 | 80 |
tertiary |
50 | 80 |
tertiary_link |
50 | 80 |
unclassified |
50 | 80 |
residential |
40 | 80 |
living_street |
20 | 20 |
pedestrian |
20 | 20 |
track |
20 | 40 |
road |
20 | 40 |
service |
20 | 40 |
footway |
20 | 20 |
path |
20 | 20 |
cycleway |
20 | 20 |
steps |
10 | 10 |
bridleway |
20 | 20 |
The global defaults per OSM railway are not differentiated by urban location or not. The adopted global defaults are provided below:
| OSM railway type | Speed limit (km/h) |
|---|---|
funicular |
70 |
light_rail |
70 |
monorail |
70 |
narrow_gauge |
70 |
rail |
70 |
subway |
70 |
tram |
70 |
For waterways we currently apply a single global default speed limit of
| OSM waterway type | Speed limit (km/h) |
|---|---|
| N/A | 20 |
It is worth noting that despite the physical speed limits set here, each mode using the OSM way also receives its own maximum speed in PLANit. Therefore, if any modelling is conducted, the minimum of the physical speed limit and the mode’s maximum speed is applied in such cases.
PLANit will log the percentages of explicitly tagged and untagged roads regarding speed limits
OSM specifies defaults for specific countries, as well as a non-country specific default.
PLANit follows those guidelines when specifying the country specific defaults and adopts the non-country specific defaults for its "Global" default.
Information on the OSM proposed defaults can be found on the following wiki page and need no repeating here:
Note that for some OSM way types no defaults are proposed by OSM, in which case we refer the reader to our Javadoc pages or the source code to unearth the adopted defaults.
Further, OSM makes a distinction between various types of access:
- yes: mode is allowed
- permissive: generally allowed by owner unless otherwise indicated, practically accessible
- designated: preferred for a particular mode (mainly used for routing of for example trucks)
- destination: only allowed for destination traffic
- private: private road, no public access
- no: mode is not allowed
PLANit has no such distinction, a road/rail is accessible to a mode or not. Therefore, the following mapping is applied, also when creating the mode access defaults based on the OSM wiki:
- yes (OSM) = yes (PLANit)
- permissive (OSM) = yes (PLANit)
- designated (OSM) = yes (PLANit)
- destination (OSM) = no (PLANit)
- private (OSM) = no (PLANit)
- no (OSM) = no (PLANit)
Lane configuration defaults
The lane configuration defaults specify the number of lanes (or tracks) for OSM ways per direction, in case no explicit number of lanes (or tracks) is set. The adopted defaults are OSM way type (highway/railway) dependent and follow the OSM guidelines as per
- Default lanes for OSM highway types (header assumptions): https://wiki.openstreetmap.org/wiki/Key:lanes
- Information on OSM railway types: https://wiki.openstreetmap.org/wiki/Key:railway#Tracks
Note that for rail the default is always 1, assuming that the track can be used by one direction at the time, but
both directions are viable (unless indicated otherwise). The same holds for waterways, e.g., route=ferry.
The defaults for lanes are generally 2 lanes per direction for larger roads (motorway, trunk), and 1 per direction for all other roads. It is encouraged to explicitly tag the number of lanes always on larger roads, whereas for smaller roads that adhere to the default it is fine to not tag explicitly.
PLANit will log the percentages of explicitly tagged and untagged roads regarding lane numbers
Activated mode defaults
By default, the OSM network reader activates a number of OSM modes for parsing by mapping them to (predefined) PLANit modes. Activating a mode does not necessarily mean that all infrastructure for that mode is parsed, because this also depends on what OSM highway, railway, waterway types are activated. Currently, the following default mapping is used and activated upon creation of the reader:
| Default activated OSM road mode | Mapped PLANit mode |
|---|---|
foot |
PredefinedModeType.PEDESTRIAN |
bicycle |
PredefinedModeType.BICYCLE |
motorcycle |
PredefinedModeType.MOTOR_BIKE |
motorcar |
PredefinedModeType.CAR |
goods |
PredefinedModeType.GOODS_VEHICLE |
hgv |
PredefinedModeType.HEAVY_GOODS_VEHICLE |
hgv_articulated |
PredefinedModeType.LARGE_HEAVY_GOODS_VEHICLE |
bus |
PredefinedModeType.BUS |
In case the railway parser is activated, the following rail based modes are activated by default
| Default activated OSM rail mode | Mapped PLANit mode |
|---|---|
light_rail |
PredefinedModeType.LIGHTRAIL |
rail |
PredefinedModeType.TRAIN |
subway |
PredefinedModeType.SUBWAY |
tram |
PredefinedModeType.TRAM |
In case the waterway parser is activated, the following water based modes are activated by default
| Default activated OSM water mode | Mapped PLANit mode |
|---|---|
ferry |
PredefinedModeType.FERRY |
(route=ferry |
PredefinedModeType.FERRY) |
Activated highway type defaults
By default the Osm network reader activates a number of OSM highway types to parse (as long as the highway parser is active). Below we list all the OSM highway types that are currently supported, whether or not they are activated by default and their default values regarding number of lanes, capacity and max density, the latter two are not based on OSM guidelines since OSM has no objective with respect to modelling or aggregate metrics tracking. These particular defaults are proposed by Planit.
The default activated types assume the most common use will be around motorised road traffic, but of course the user can override these defaults if desired.
| OSM highway types | Default activated | Number of lanes | Capacity (pcu/h/lane) | Max density (pcu/km/lane) |
|---|---|---|---|---|
motorway |
YES | 2 | 2000 | 180 |
motorway_link |
YES | 2 | 1800 | 180 |
trunk |
YES | 2 | 2000 | 180 |
trunk_link |
YES | 2 | 1700 | 180 |
primary |
YES | 1 | 1600 | 180 |
primary_link |
YES | 1 | 1400 | 180 |
secondary |
YES | 1 | 1200 | 180 |
secondary_link |
YES | 1 | 1000 | 180 |
tertiary |
YES | 1 | 1000 | 180 |
tertiary_link |
YES | 1 | 800 | 180 |
unclassified |
YES | 1 | 600 | 180 |
residential |
YES | 1 | 600 | 180 |
living_street |
YES | 1 | 600 | 180 |
service |
YES | 1 | 600 | 180 |
pedestrian |
YES | 1 | 600 | 180 |
path |
NO | 1 | 600 | 180 |
steps |
NO | 1 | 600 | 180 |
footway |
NO | 1 | 600 | 180 |
cycleway |
NO | 1 | 600 | 180 |
bridleway |
NO | 1 | 600 | 180 |
track |
YES | 1 | 600 | 180 |
road |
YES | 1 | 600 | 180 |
Activated railway type defaults
By default, the OSM network reader activates a number of OSM railway types whenever the railway parser is activated. Below we list all the OSM railway types that are currently supported, whether they are activated by default and their default values regarding number of tracks, capacity and max density, the latter two are not based on OSM guidelines since OSM has no objective with respect to modelling or aggregate metrics tracking. These particular defaults are proposed by Planit (and in case of rail are unlikely to ever be considered, but they are provided for transparancy)
| OSM railway types | Default activated | Number of tracks | Capacity (pcu/h/lane) | Max density (pcu/km/lane) |
|---|---|---|---|---|
funicular |
NO | 1 | 10000 | 180 |
light_rail |
YES | 1 | 10000 | 180 |
monorail |
NO | 1 | 10000 | 180 |
narrow_gauge |
NO | 1 | 10000 | 180 |
rail |
YES | 1 | 10000 | 180 |
subway |
YES | 1 | 10000 | 180 |
tram |
YES | 1 | 10000 | 180 |
Activated waterway type defaults
Be default the OSM network reader activates two types of waterways, namely all route=ferry OSM ways, as these represent the equivalent of links on bodies of water used by
water modes. In addition, the reader also activates all ferry crossings that are marked using OSM hghway types via ferry=<osm_highway_type, e.g., if the user has
activated highway=trunk but not highway=motorway, then all ferry crossings marked as ferry=trunk will be included, whereas the ferry=motorway will be excluded.