1,345
edits
Import/Catalogue/Bus stop import Norway: Difference between revisions
Jump to navigation
Jump to search
m
Import/Catalogue/Bus stop import Norway (view source)
Revision as of 04:50, 22 June 2019
, 5 years agoFixes
(Update link to NSR files) |
m (Fixes) |
||
|
When extracting data, NSR should primarily be accessed through [https://developer.entur.org/content/national-stop-register its API] or the derivative [https://developer.entur.org/content/geocoder Geocoder], but it may also be viewed through its web interface at [https://stoppested.entur.org stoppested.entur.org] using the guest account.
For bulk data from NSR, files are made available [https://developer.entur.org/files here] through daily updated XML files in the [http://netex-cen.eu NeTEx] format. This format has been chosen by the European Commission as its standard format for exchanging public transport information. The python program [https://github.com/osmno/nsr2osm nsr2osm_dump] reads the files and produces OSM/XML files which can be opened in JOSM. The program [https://github.com/osmno/nsr2osm nsr2osm] is used for later updates after the initial import.
The generated OSM file ''nsr_current.osm'' is available [https://drive.google.com/drive/folders/1pkHcNvmHoRWHHTrnrIWpC--cCFmPbkXL?usp=sharing here]. Please disregard train, tram and ferry stops - only bus stops and bus stations will be imported. Attributes with keys in capital letters will not be imported. A file containing ''all'' Norwegian bus stops and stations currently in OSM is also available in the folder
=== Data reduction and simplification ===
The NeTEx files contains a lot more information than needed for OSM import. The [https://github.com/osmno/nsr2osm nsr2osm_dump] program extracts all attributes necessary for tagging. The update program [https://github.com/osmno/nsr2osm nsr2osm]
=== Source data structure ===
| |||