Content

Complex stop place area "Oslo S - Jernbanetorget"

Please note that this example doesn't represent the actual modelling in the national stop place registry.

Group of StopPlaces with multiple multimodal- and monomodal StopPlaces

Jernbanetorget and Oslo S constitutes a public transport hub which can be modelled as a Group of Stop Places, where each part of the stop place area is modelled as a multimodal stop place or a monomodal stop place.

Stop places are served by several transport modes, such as trains, metros, trams and buses, where some stop places connected to the area serve more than one transport mode. Some of the stops are indoors, or underground, while others can be found on the street level, connected to the road network. This means that the stops have different facilities depending on transport modality and location and that the area has some services that apply across the various stop places.

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/OsloS_station_example.xml

Modelling

All StopPlaces for trains, buses, trams and taxis are logically linked into one stop area. In this stop area, there are 19 train tracks, two metro tracks, two tram stops, two bus stops and a taxi stop.

The model can look like this:

Train
- ~~One Parent Quay for each platform with two Quays (one for each side of the platform) which each contain several BoardingPositions.~~ (Nesting of Quays is outdated and the example will be remodelled in the next version of Norwegian NeTEx Profile)
- ~~Parent quays are gathered in a single StopPlace representing the train station.~~ (Nesting of Quays is outdated and the example will be remodelled in the next version of Norwegian NeTEx Profile)
Metro
- Two Quay objects (one in each direction) gathered in one StopPlace
Bus/Tram just outside Oslo S (bus and Tram do not share a platform)
- Two Quays under a StopPlace for bus
- Two Quays under a StopPlace for the tram
- One Parent StopPlace (multimodal) to above the bus and tram stop places
Bus (between Byporten and Oslo City)
- One StopPlace with two Quays
Tram (in front of Clarion Hotel)
- One StopPlace with two Quays
One GroupOfStopPlaces to gather all the parent StopPlace objects

Model

Illustration

Alternativt modelleringseksempel

Flyplass (Gardermoen)

Another example of a complex stop is an airport, in this case Oslo Airport, Gardermoen. It has several bus and taxi stop places in front of the main terminal, plus the train platforms below them. The airport consists of various airport terminals with their gates:

Aircraft related
- Each gate is a Quay
- ~~Gates can be grouped for "Domestic", "Schengen", "Rest-of-the-world"~~ (Nesting of Quays is outdated and the example will be remodeled in the next version of Norwegian NeTEx Profile)
- All Quays are collected in one StopPlace which describes the terminal.
- ~~A StopPlace with two Quays for Flytog~~ (Dividing airport trains and regular trains into separate stop places is outdated and the example will be remodeled in the next version of Norwegian NeTEx Profile)
- A StopPlace with two Quays for regular trains (Dividing airport trains and regular trains into separate stop places is outdated and the example will be remodeled in the next version of Norwegian NeTEx Profile)
- a parent StopPlace for rail transport (Dividing airport trains and regular trains into separate stop places is outdated and the example will be remodeled in the next version of Norwegian NeTEx Profile)
Road-based
- Quays for each bus stop.
- Quays for each taxi stop.
- One StopPlace for buses and one StopPlace for taxis.
- A parent StopPlace (multimodal) for bus/taxi.
A GroupOfStopPlaces to gather all multimodal StopPlaces.

Model

Illustration

Elements

Many of the basic elements are described in more detail in the examples for minimalistic stop place and single stop place, and will therefore not be covered more closely in this example document. Below is an overview of (some of) the most important elements that should be modeled for a multimodal stop area with multiple StopPlaces:

GroupOfStopPlaces

No XML model available. Will be described here in the next version of the handbook. Contact Entur for examples.

Please be aware, due to developments after the publication of these examples, the usage of GroupOfStopPlace has been changed from a top-level StopPlace element to something more akin to an "alias" which refers to StopPlaces seen as central/important hub stops (usually the GroupOfStopPlaces is equal to a city/town).

StopPlace

For a larger building connected to a stop place area, it will normally be expedient to describe the stop in more detail with geographical location, its facilities, and public entrances.

In this example the railway station "Oslo S" is modelled with a higher degree of detail, (for more examples of StopPlace modelling, see: minimalistic stop place and single stop place).

<StopPlace id="NHR:StopPlace:8" version="any">
	<Name lang="no-NO">Oslo S</Name>
	<Centroid>
		<Location>
			<!-- Note: Generalized coordinate representing the whole station -->
			<Longitude>59.910921</Longitude>
			<Latitude>10.753284</Latitude>
		</Location>
	</Centroid>
	<placeTypes>
		<TypeOfPlaceRef ref="monomodalStopPlace"/>
	</placeTypes>
	<AccessibilityAssessment id="NHR:AccessibilityAssessment:6" version="any">
		<MobilityImpairedAccess>true</MobilityImpairedAccess>
		<limitations>
			<AccessibilityLimitation>
				<WheelchairAccess>true</WheelchairAccess>
				<StepFreeAccess>true</StepFreeAccess>
				<AudibleSignalsAvailable>true</AudibleSignalsAvailable>
			</AccessibilityLimitation>
		</limitations>
	</AccessibilityAssessment>
	<Covered>indoors</Covered>
	<Gated>openArea</Gated>
	<facilities>
		<SiteFacilitySetRef ref="sfs:1"/>
	</facilities>
	<entrances>
		<!-- Main entrance towards Jernbanetorget -->
		<StopPlaceEntrance id="NHR:Entrance:1" version="any">
			<EntranceType>automaticDoor</EntranceType>
			<Width>1.5</Width>
			<Height>2.2</Height>
		</StopPlaceEntrance>
	</entrances>
	<TransportMode>rail</TransportMode>
	<StopPlaceType>railStation</StopPlaceType>
	
	[...]
	
</StopPlace>

boardingPositions

For trains, a Quay can be subdivided into BoardingPositions, which specifies positions or zones at the along the platform. This can be used, for example, to specify where different carriage types will be relative to the length of a train, or where one may find boarding facilities for travellers with special needs.

<boardingPositions>
	<BoardingPosition id="NHR:BoardingPosition:1" version="any">
		<Label>A</Label>
		<BoardingPositionType>positionOnRailPlatform</BoardingPositionType>
	</BoardingPosition>
	<BoardingPosition id="NHR:BoardingPosition:2" version="any">
		<Label>B</Label>
		<BoardingPositionType>positionOnRailPlatform</BoardingPositionType>
	</BoardingPosition>
	[...]
</boardingPositions>

AccessSpace

Areas, often indoors, associated with a stop place or groups of stop places, are modelled as AccessSpace. This includes, among other things, map position(s), a reference to relevant public entrances, information on general accessibility for wheelchair users and information about ticketing equipment.

For larger stop place areas, several AccessSpace can be defined, in this example, the main hall for "Oslo Central Station" (Oslo S) has been modelled.

<AccessSpace id="NHR:AccessSpace:1" version="any">
	<gml:Polygon gml:id="OsloS">
		<!-- Perimeter of the inner public space. The main hall and the various corridors -->
		<gml:interior>
			<gml:LinearRing>
				<gml:pos>59.91160529142 10.75148462981</gml:pos>
				<gml:pos>59.91127987568 10.75117885798</gml:pos>
				<gml:pos>59.91115750777 10.75204521149</gml:pos>
				<gml:pos>59.91109699601 10.75230002135</gml:pos>
				<gml:pos>59.91093159661 10.75214177102</gml:pos>
				<gml:pos>59.91074871503 10.75290620059</gml:pos>
				<gml:pos>59.9115004057 10.75361698598</gml:pos>
				<gml:pos>59.91164966605 10.75296252698</gml:pos>
				<gml:pos>59.91131214845 10.75265407294</gml:pos>
			</gml:LinearRing>
		</gml:interior>
	</gml:Polygon>
	<PublicUse>all</PublicUse>
	<Covered>indoors</Covered>
	<Lighting>wellLit</Lighting>
	<AllAreasWheelchairAccessible>true</AllAreasWheelchairAccessible>
	<equipmentPlaces>
		<EquipmentPlace id="NHR:EquipmentPlace:1" version="any">
			<Centroid>
				<Location>
					<Longitude>59.911213</Longitude>
					<Latitude>10.752860</Latitude>
				</Location>
			</Centroid>
			<placeEquipments>
				<TicketingEquipment id="NHR:TicketingEquipment:1" version="any">
					<VehicleModes>rail bus</VehicleModes>
					<NumberOfMachines>4</NumberOfMachines>
					<TicketingFacilityList>ticketOffice mobileTicketing
						ticketMachines</TicketingFacilityList>
					<TicketingServiceFacilityList>reservations purchase</TicketingServiceFacilityList>
				</TicketingEquipment>
			</placeEquipments>
		</EquipmentPlace>
	</equipmentPlaces>
	<entrances>
		<StopPlaceEntranceRef ref="NHR:Entrance:1"/>
	</entrances>
	<AccessSpaceType>concourse</AccessSpaceType>
</AccessSpace>

NavigationPath

To describe how to get from one location of a stop place area to another (usually on foot), for example, to indicate the expected walking time for interchanges between two transport modes within a transportation hub, a NavigationPath can be modelled.

<!-- Path between Entrance to Oslo S and platform 1 (spor 1) -->
<NavigationPath id="np:1" version="any">
	<Distance>12.3</Distance>
	<From>
		<!-- From Entrance to Oslo S train stop (sp:osl:7) -->
		<PlaceRef ref="sp:osl:7:entr:1"/>
	</From>
	<To>
		<!-- Train platform - spor 1 -->
		<PlaceRef ref="q:sp:osl:7:spor1"/>
	</To>
	<TransferDuration>
		<DefaultDuration>PT15M0S</DefaultDuration>
		<FrequentTravellerDuration>PT4M0S</FrequentTravellerDuration>
		<OccasionalTravellerDuration>PT6M0S</OccasionalTravellerDuration>
		<MobilityRestrictedTravellerDuration>PT10M0S</MobilityRestrictedTravellerDuration>
	</TransferDuration>
	<AccessFeatureList>escalator concourse travelator</AccessFeatureList>
	<NavigationType>streetToQuay</NavigationType>
</NavigationPath>

SiteFacilitySet

Public facilities and services at-, or associated with a stop place, such as information boards, are described with the explicit type of FacilitySet specifically defined for, and associated with a SiteElement.

<SiteFacilitySet id="sfs:1" version="any">
	<AccessibilityInfoFacilityList>largePrintTimetables audioForHearingImpaired audioInformation
		displaysForVisuallyImpaired</AccessibilityInfoFacilityList>
	<PassengerInformationEquipmentList>timetablePoster</PassengerInformationEquipmentList>
	<PassengerInformationFacilityList>passengerInformationDisplay
		realTimeConnections</PassengerInformationFacilityList>
</SiteFacilitySet>

Håndbok N801 (SIRI/NeTEX)

StopPlace - complex