StopPlace - simple
- Copy Page Tree
- Johan Wiklund
- Hans Inge Letnes
- Johan Wiklund (Unlicensed)
Content
- 1 Bryn skole, Oslo
- 1.1 Monomodal StopPlace with two Quays
- 1.1.1 Link
- 1.2 Elements
- 1.2.1 PublicationDelivery
- 1.2.2 Validity
- 1.2.2.1 ValidityConditions
- 1.2.3 Organization
- 1.2.3.1 Codespace
- 1.2.4 Site Frame
- 1.2.4.1 Stop Place
- 1.2.4.2 Quay
- 1.1 Monomodal StopPlace with two Quays
Bryn skole, Oslo
Monomodal StopPlace with two Quays
Bryn skole (at Ole Deviks vei) is modelled as a monomodal stop place (a stop place for one single type of transport) with two quays, and serves as an example of a stop place which is served only by bus. All stop places that are served by only one type of transport, such as tram, metro, train or boat, are modelled in this manner.
The stop place for Bryn skole has no facilities beyond a sign showing that there is a bus stop, with information board for the bus route, with a timetable.
Link
The XML example in it its entirety can be found in the GitHub repository: https://github.com/entur/profile-norway-examples/blob/master/netex/stops/BasicStopPlace-two-quays_example.xml
Elements
The following is a more detailed description of the most important elements that must be included in the data transfer to the stop place registry:
PublicationDelivery
All XML files according to the Norwegian NeTEx-profile should be of type PublicationDelivery containing relevant Frames. (See GitHub for a complete example.)
Validity
Describes the validity criteria for the dataset. In this example, an open-ended validity period, from a specific date, without an end date.
ValidityConditions
<validityConditions>
<AvailabilityCondition version="any" id="NSR:AvailabilityCondition:1">
<FromDate>2017-03-08T12:12:00.0Z</FromDate>
</AvailabilityCondition>
</validityConditions>Organization
Each operator, as well as other authorities, has its own "namespace" - Xmlns - (cf. Administration Code) which guarantees the uniqueness of the contents of the dataset.
In Norway, these codes are set by the national stop place registry.
Codespace
<codespaces>
<Codespace id="NRS">
<Xmlns>NSR</Xmlns>
<XmlnsUrl>http://www.entur.org/ns/nsr</XmlnsUrl>
</Codespace>
</codespaces>Site Frame
This block contains the information relevant for describing "physical" objects, including StopPlace, Quay and Facilities/Equipment found on them.
<SiteFrame version="any" id="NSR:SiteFrame:1">
<!-- ===StopPlaces=== -->
<!-- Details for StopPlace and Quay can be found further down in the example -->
<stopPlaces>
<StopPlace>
[...]
<quays>
<Quay>[...]</Quay>
</quays>
</StopPlace>
</stopPlaces>
<siteFacilitySets>
<SiteFacilitySet id="NSR:SiteFacilitySet:timetablePoster" version="any">
<PassengerInformationEquipmentList>timetablePoster</PassengerInformationEquipmentList>
</SiteFacilitySet>
<SiteFacilitySet id="NSR:SiteFacilitySet:lineNetworkPlan" version="any">
<PassengerInformationEquipmentList>lineNetworkPlan</PassengerInformationEquipmentList>
</SiteFacilitySet>
<SiteFacilitySet id="NSR:SiteFacilitySet:fareInformation" version="any">
<PassengerInformationEquipmentList>fareInformation</PassengerInformationEquipmentList>
</SiteFacilitySet>
</siteFacilitySets>
</SiteFrame>Stop Place
The stop place is generally described with name, transport mode, and location, and should have accessibility information defined to satisfy universal design requirements. (Accessibility can also be modelled as NavigationPaths if relevant.)
Quay
An individual (and exact) position for boarding/alighting is defined as a Quay. It can have references to nearby roads, facilities, compass bearing etc. Its most prominent features are coordinate and PublicCode (platform identifier). The Quay always inherits name from its parent StopPlace.