User:FredrikLindseth/NSR

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Import/Plan Outline
· Afrikaans · Alemannisch · aragonés · asturianu · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · Bân-lâm-gú · Basa Jawa · Basa Sunda · Baso Minangkabau · bosanski · brezhoneg · català · čeština · corsu · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · Kurdî · latviešu · Lëtzebuergesch · lietuvių · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk bokmål · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tagalog · Tiếng Việt · Türkçe · Vahcuengh · vèneto · Wolof · Yorùbá · Zazaki · српски / srpski · беларуская · български · қазақша · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · मराठी · हिन्दी · भोजपुरी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · བོད་ཡིག · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ ⵜⴰⵏⴰⵡⴰⵢⵜ‎ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 中文(繁體)‎ · 吴语 · 粵語 · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް
This is an import of NasjonalStoppestedRegister (National Stop Register in Norwegian) is a database with all stops of all public transports in Norway. The database contains ~60.000 stops place and ~100.000 stop areas.

The database is maintained by ENTUR and all public transport companies have to make sure this database is updated.

Goals

The goals of this import is to have a complete and updated coverage of public transport stop locations in Norway.

  • Separate stops on each side of the road
  • Stop area-relations with the stops
  • Offical names
  • Official ID of each stop, for This project currently has no time frame future updates

Schedule

Import Data

Background

Data source site: www.entur.org/dev/rutedata/
Data license:

Type of license (if applicable): no licence currently
Link to permission (if required):
OSM attribution (if required):
ODbL Compliance verified:

OSM Data Files

Link to your source data files that you have prepared for the import - e.g. the .osm files you have derived from the data sources.

Import Type

Identify if this is a one-time or recurring import and whether you'll be doing it with automated scripts, etc.

Identify what method will be used for entering the imported data into the OSM database - e.g. API, JOSM, upload.py, etc.

Data Preparation

Data Reduction & Simplification

Describe your plans, if any, to reduce the amount of data you'll need to import.

Examples of this include removing information that is already contained in OSM or simplifying shapefiles.

Tagging Plans

Describe your plan for mapping source attributes to OSM tags.

Changeset Tags

Describe how you'll use changeset tags in the import.

Data Transformation

Describe the transformations you'll need to conduct, the tools you're using, and any specific configurations or code that will be used in the transformation.

Data Transformation Results

Each stop looks like this

key value description OSM conversion
entityType Quay public_transport=platform
id NSR:Quay:51729 Unique ID of stop ref=*
description *
descriptionLang
privateCode
publicCode

Each stop is an entityType=Quay and has a each ID is unique.

One stop on each side of the road/stop area is associated with a StopPlace-node like this:

key possible values description OSM conversion
entityType StopPlace, Quay, Parking StopPlace, Quay or Parking
finalStopPlaceType Combination of parent modalities
hasParentSiteRef Is subordinate to a multimodal StopPlace
id * ENTURs unique ID for this stop-area
isParentStopPlace Is multimodal StopPlace with subordinate StopPlaces
name Official name of the stop
nameLang nor Language of name field
stopPlaceType onstreetBus Bus stops along a road
busStation Bus stations
airport Airports
harbourPort Passenger-only ferries
ferryStop Ferries that also take cars
railStation Railway stations
onstreetTram Bybanen og Trikken
liftStation Fløybanen i Bergen
metroStation Tbanen i Oslo
submode More specific modality subordinate to stopPlaceType
weighting not useful ignore
covered
parkingVehicleTypes
totalCapacity
There is no direct connection between the StopPlace and the Quay so to get the related Quays one has to use ENTURs API like this
{  stopPlace(id: "NSR:StopPlace:30085") {
    ... on StopPlace {
      quays {
        id
}}}}

Train

Tram / light rail

Ferry

Data Merge Workflow

Team Approach

Describe if you'll be doing this solo or as a team.

References

List all factors that will be evaluated in the import.

Workflow

Detail the steps you'll take during the actual import.

Information to include:

  • Open NSR.osm
  • Download data from OSM
  • Copy your stops to OSM-layer
  • Merge and validate the data
  • Upload the changeset with the comment TODO

Conflation

Identify your approach to conflation here.

QA

Add your QA plan here.