vignettes/data_packs.Rmd
data_packs.RmdThis vignette covers the recategorisation of OpenStreetMap (OSM)
infrastructure data into the openinfra transport infrastructure data
packs.
To view the current publication of our data packs,
please see the Openinfra GitHub repository releases page here.
The transport infrastructure data packs contain OSM infrastructure data
for a given Local Authority District (LAD), as defined by the following
polygons for UK
LADs.
Whilst these LADs are currently being used to define
the spatial area covered by each infrastructure data pack, any new set
of updated boundaries (as a geojson file) can also be used to create the
transport infrastructure data packs.
The LADs can be seen below:
This sections visualises the data pack outputs generated by
the openinfra functions that are described in detail below.
The current example data pack outputs for a 2km circular radius about
“Leeds” City Centre:
– Cleaned road descriptions
– Legally
cyclable network
– Legally walkable network
– Presence of
lighting network
– Cleaned maximum speed values
– Presence of
cycle crossings
– Presence of cycle parking
– Recategorised
road names
Please note that a 2Km circular buffer has been applied to the data
so that the map can be hosted on this website. (max size 25Mb)
As
can be seen, the default network has a variety of highway
values and is rather confusing to the uninitiated OSM user.
The recategorised road descriptions are more interpenetrate and meaningful than the default OSM highway values.
As can be seen - the OSM highways recategorised to road descriptions
are much easier to visualise and insightful than all OSM highway values.
This visualisation shows the ways that cyclist legally have a right
to access and use - note that this does not imply a “friendly” or “super
safe” route, more that cyclists can use such ways if required.
An example application of this dataset could be highlighting the most
likely roads that will be used by cyclists when switching from
(intermittent) dedicated cycling infrastructure.
Much like the cyclable ways visualisation above, this visualisation
shows ways that pedestrians legally have a right of way on. It does not
assess or indicate any “friendliness” or “scenic-ness” of a way.
Note that a value of maybe implies the lack of data to
distinguish between "yes" or "no".
Such information may be utilised to assess routes for safe active travel
after dark. Likewise, complimented with Origin Destination (OD) data,
one may identify active travel routes along high active travel traffic
ways and implement lighting (if not present) to increase the safety of
such routes after dark.
Recategorised UK maximum road speed values. Based on the official UK speed limits.
Note that the potential lack of coverage for the maxspeed tag is due to
the fact that this tag is usually not explicitly adeed, except where it
is an exceptional value. See #147 for
more context.
Recategorises OSM to provide more descriptive road names useful for
discussion and targeted analysis.
For example, osm_id:23200835
is less useful as a name than, Lovell Park Road
This function identifies the type of cycling infrastructure, with respect to the level of separation from carriageways, from OSM data. Such infrastructure consists of on carriageway infrastructure (cycling lanes, mixed traffic, shared busway/lanes) and protected infrastructure (cycle tracks and ways, stepped cycleways, kerb separated cycleways) where protected implies some form of physical separation from the carriageway.
This section defines the column names contained within each LAD data pack added by the openinfra functions.
| column name | column description |
|---|---|
| openinfra_cycle | Indicates if an OSM way is legally usable by cyclists Note: this does not assess any “qualities” of a way (such as quietness, traffic flows etc.) |
| openinfra_walk | Indicates if an OSM way is legally usable by pedestrians Note: this does not assess any “qualities” of a way (such as quietness, traffic flows etc.) |
| openinfra_cycle_parking | Identifies bicycle parking places from OSM data amenity
tag |
| openinfra_maxspeed | Reclassified default OSM maxspeed column values to be
compliant with current UK
speed limits
|
| openinfra_cycle_crossings | Identifies OSM ways used specifically for cycles to cross carriageways |
| openinfra_cycle_infra | Reclassifies default OSM data to identify the ‘high-level’ type of
protection provided by dedicated cycling infrastructure, such as:
Mixed Traffic (=< 20 mph) - no protection, Cycle Lanes (mandatory & advisory) - legal protection, Protected Cycling Spaces - physical protection, including: stepped cycleways, kerb separated cycleways, cycle tracks, etc. |
| openinfra_is_lit | Identifies if an OSM way has lighting present or not, or if there is a lack of data to accurately assess (“maybe”) |
| openinfra_road_class | Reclassifies default OSM highway values to relevant UK
highway classifications, with modifications used by Chan and
Cooper
|
| openinfra_road_names | Identifies the road name and reference (where available) of OSM ways
and combines these to be more informative. i.e. osm_id=4004413 –> Headingly Lane, A660 |
For further information and documentation, including an example data pack production for Leeds, see the data pack documentation vignette.