User guide: National StopPlace Registry
Table of contents
- 1.1 Table of contents
- 1.2 Further reading
- 2 Change history of the guide
- 3 Introduction
- 4 Basic rules for usage
- 5 User interface
- 5.1 Menu and settings
- 5.1.1 Toggling displayed elements
- 5.1.2 Language
- 5.1.3 Map backgrounds
- 5.2 Searching for stops
- 5.3 Edit mode
- 5.4 Tools in the map view
- 5.5 The report view
- 5.1 Menu and settings
- 6 Editing Tariff zones
Further reading
Change history of the guide
Version | Date | Change |
|---|---|---|
1.0 | 30.06.2017 | First version https://enturas.atlassian.net/wiki/spaces/ROR/pages/637370663 |
2.0 | 25.05.2020 | Re-written English user guide replaces old Norwegian user guide. |
Introduction
The purpose of the national stop place registry (NSR) is to provide a single source of information for all public transport stops in Norway. All stops are assigned a national ID to which public transport providers can link their own data. NSR is to be considered the master database for stop places in Norway.
It is absolutely critical to the quality of the national stop place registry that the users have a clear understanding of the tools available in the editor, and the guidelines for how stops are structured.
Guidelines for stop place structuring can be found in Håndbok N801
Registered users log in with their personal accounts and may edit any element to which they have been given access. Guest users may view the data without logging in but will not be able to make edits.
Access the service here: https://stoppested.entur.org/
Basic rules for usage
User access is given on a person to person basis. Never share your account with another person. Contact the administrator (Entur) to create accounts for new users.
Only make changes where you are absolutely sure of the implications of that change. If something is unclear, return to this guide, try it out in the test environment, or contact the administrators (Entur).
Stops can not be permanently deleted by a user but can be temporarily deactivated or permanently deactivated (archived). If mistakes are made where erroneous stops are created, contact an administrator (Entur) for permanent deletion.
User interface
The user interface is an open-source ReactJS component and can be freely used, copied and modified by anyone. For more information and installation, please visit Github - Abzu.
Menu and settings
Toggling displayed elements
Menu item | Explanation |
|---|---|
Settings > Public and private codes on stop places | By default, the usage of public- and private codes on the stop place level is not promoted, it may, however, be used in appropriate situations. |
Map preferences > Show path links | Toggle to show path links. |
Map preferences > Show compass bearing | Toggle to show compass bearing arrows on quays, used to indicate the driving direction out of a quay. |
Map preferences > Show expired stop places | Toggles expired stops being displayed on the map. |
Map preferences > Show multimodal internal connections | Toggles a green line linking the member stops of a multimodal stop place. |
Map preferences > Quay marker label | Select whether to display the public- or private code on the Quay icons. |
Language
The language menu allows you the change the language of the user interface. Additional languages may be submitted through GitHub.
Map backgrounds
With the map layer menu, an appropriate map background is selected. Additional map players may be submitted through GitHub.
For Norway, the map layers for accurate positioning are:
Kartverket flyfotoKartverket topografisk
Searching for stops
Find stops by typing in part of the name you are looking for in the search field.
If there are too many results the results can be filtered:
By selecting specific modes by clicking the transport mode icons at the top of the box
By selecting a geographical area by clicking “More filters” and searching for a municipality or county.
Find expired- or future stops by opening “More filters” and checking the “Show expired, future and permanently deleted” checkbox.
Use “lookup coordinates” to find a position on the map by adding a coordinate.
“Save search” allows you to save searches to the favourites list.
For the button “New Stop Place”, see Creating new stops.
Preview of stops
After searching and selecting a stop from the list, a quick preview box of the stop will be displayed showing a summary of the most important information about it.
From here you may access the stop in edit (or view) mode by clicking the “Edit” (or “View”) button.
Finding stops directly on the map
If searching for a stop name is not an option, or your workflow better suits it, you can find stops directly on the map and start editing from there. Use the previously mentioned “Lookup coordinate” from the stop search box, or zoom in on the map (due to restrictions on data usage a certain zoom level is required to see stops) and find your stop geographically.
Once a stop has been located, click on the stop icon and then the stop name to enter edit mode.
Edit mode
There is no difference between “edit mode” and “view mode” except that a user may or may not have permission to make and save changes to that particular stop. Permissions are governed by modality and/or topographic places (geographical borders) and are created by the administrator.
Key-values and private codes
The StopPlace and Quay levels can have key-values added to them. This allows the registration of non-standard data which can be used by third-party- or data creator users to match NSR-stops with external systems.
Private codes for StopPlace and Quay are likewise used for correlation with external systems, but may not be used for non-standard purposes.
For both StopPlace and Quay the key-value editor is accessed by clicking the key icon on the respective element. Please note the difference between StopPlace and Quay-key-values.
The key-values are essentially free text fields where a key and a value are combined. Add new keys by clicking the “plus” button, or edit values of existing keys by clicking the “pen” icon.
Please note that both key and value may be case sensitive and mistakes may render them unusable.
Communication between users
A user may leave a note, very much like a post-it note”, on a stop place. These are meant to act as reminders and searchable data for the data maintainers. The tagging system has a tag and a comment field. New tags can be created by all users at any time - or previously used tags can be re-used.
The comment is optional but can be used to describe the issue with each stop tagged.
It is highly recommended that each data maintainer creates a unique tagging scheme - for example by prefixing the tag with a codespace - in order to avoid data collision with other users of the system.
Entur has created a tagging scheme based around a prefix and a theme, for example:
adm_gruppering- indicating a problem with how stops are grouped.adm_koordinat- indicating a problem with the position of the stop.
The data maintainer “Kolumbus” has a tagging scheme with the prefix kol_.
The tags are not included in the StopPlaces' version history and can be created, updated and deleted independently from the stop to which they belong.
Tools in the map view
The map view has a number of tools for editing and viewing information. These can be accessed by clicking on StopPlaces or Quays.
To open a stop in edit mode, click the StopPlace icon, then its name. When clicking certain things in Edit mode, the context in the editor box may also change, such as when clicking on Quay- or parking-markers.
The function and operation of these tools are described in further detail under processes.
To add new features on the map to a StopPlace, three icons at the top of the page can be dragged down onto the map. This concerns creating a Quay, bicycle- or car parking.
The report view
Go to the top right corner menu and click “Reports” to launch the report view which can generate lists based on search criteria.
Much like the regular stop search, the user can filter stops on modality and geography. In this example, the search is limited to bus stops, car ferry ports, and subway stations in the county ‘Vestland’.
Further filters can be applied, such as “only stops with a certain tag” or “stops without coordinates”. In this example, only stops with the tag adm_koordinat and a name containing the string “Bryn” will be shown in the results. In addition to this, the stop has been permitted to also include expired-, future- and permanently deleted stops. These filterings come in addition to the above-mentioned filters of modality and geography.
The resulting view, which is limited to 300 results (to avoid overloading the API), displays the results as a list of StopPlaces. Quays may be viewed by expanding a StopPlace. Which columns to display can be modified using the two menus “Columns for Stop Place” and “Columns for Quays”.
At the bottom of the report is the page navigator, and an option to export the results as a CSV file.
Editing Tariff zones
Tariff zones (Tariff zones / Tariff Zones) can not be edited in the interface of the stop register, but the association of stops to a zone can be controlled via positioning. TariffZones are updated by submitting polygon data to Entur. This can be done in OSM XML formats, or NeTEx XML (Contact Entur for other formats).
Submitted zone polygons must contain the following information:
Codespace
Name of the zone
Reference (zone ID)
Polygonal geometry with closed rings and no inner/outer rings.
It is possible to change a stop zone association in the interface of the stop register by moving the stop icon (the blue circle with the transport icon) into another zone, and then save the stop point, but this requires that zone polygons are correctly submitted in advance. When the TariffZone polygons are updated, all stops are automatically checked and if necessary updated with new zone associations.
Submitted zones can be viewed as a map background layer in NSR by selecting the background map "TariffZones" The zone connections of the stops can be viewed by clicking the Tz icon when editing/viewing a stop.