...
| Info |
|---|
The Nordic NeTEx profile allows for more elements to be added to stop places. This guide covers only the most fundamental data points. |
Element | What it does | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Quay | Marks the exact position where a vehicle stops, and its equipment. |
| ||||||||||||||||
StopPlace | Connects nearby Quays into a single stop with a common name, and sometimes common facilities or equipment. | |||||||||||||||||
Multimodal StopPlace (or | Makes it possible to have two StopPlaces with different modalities connected as a single element. |
A fundamental principle
The structure of a stop should always reflect the actual conditions and physical reality of the stop. Any fictitious data is disallowed in order to keep the data generic, sustainable and predictable. This means the stops must be placed where they actually are rather than making adjustments to suit external needs.
...
The use of the description field differs between StopPlace and Quay. For StopPlace it should be seen as an extension of the name field. So if the stop name is “Main Street” the description field can be “by the harbor”harbour”. For this reason, it is advised to begin this field in lowercase letters.
...
It is possible to add alternative names to stops which can assist the customer to find the stop they are looking for. Since the alternative name is usually not displayed to the customer it is important that the names are closely linked.
Examples
Quality | Name of stop place | Alternative name | Comment |
|---|---|---|---|
Good | Nationaltheatret | Nasjonalteatret | The unusual spelling of the stop is assisted by the often presumed spelling. |
Uneccesary | Fjellveien | Fjellvegen | The geocoder is flexible enough that small variations in spelling can be overlooked. |
Bad | Fjellveien | Dalsveien | Applying a completely different name will cause confusion as for why the name Fjellveien would appear when searching for Dalsveien. Remember that the customer can’t know what you were thinking of when adding the name. |
It is advisable to use alternative names as sparsely as possible, and only when it adds value for the end user.
Label
For airports, the location portion of the airport name is added as the type: Label.
...
All alternative names added, regardless of type or translation will be searchable in the Entur geocoder which will return the name of the stop place.
...
Quay
The Quay element has three fields, public code, private code and Description.
PublicCode | Must be a code (not words) | Used when a position (quay) is marked with a code. See more below. |
PrivateCode | Used freely by the local authority for any purpose. This field is not communicated to the public. | |
Description | Should start with a lowercase word which describes the location of the quay. Only use when extra information is needed. | Used to extend the StopPlace name. See naming rules above. |
Private code
This field should only be filled out when the Quay has a clearly visible (from a distance) code (number or letter) marked on the infrastructure of the platform which is distinct from the other platforms. If several platforms cohabit on the same code this should be clearly visible to the customer.
When the Quay has no clearly visible coding the PrivateCode field must be left empty. Inot sufficient to have a code indicated in small print on the timetable board. |  |
A large print letter or number is concidered sufficient but not optimal. The reason is that a time table board is specific to the owner of that board. When multiple operator serve the stop this may cause confusion. |  |
Clear large print markings on the wall or roof of the shelter is in full complience. |  |
A free standing large print sign on the platform is in full complience. |  |