Content

Bryn

...

skole, Oslo

Monomodal StopPlace with two Quays

Bryn skole (at Ole Deviks vei) is modeled modelled as a monomodal stop place (stopplace a stop place for one single type of transport type) with two quays, and serves as an example of a stopplace that stop place which is served only operated by bus. Stopplaces All stop places that are served by only operated by one type of transport, such as tram, metro, train or boat, must be modeled in a similar are modelled in this manner.

The stopplace stop place for Bryn Skole skole has no facilities beyond a sign showing that there is a bus stop, with information board showing the busroute and for the bus route, with a timetable.

Link

The entire XML example file is located on the projects's GitHub-repository at 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 stopplaceregisterstop place registry:

PublicationDelivery

All XML files according to the  Norwegian NeTEx-profile should profile should be of type PublicationDelivery containing relevant Frames. (See GitHub for a complete example.)

Validity

Describes the validity criteria for the data set, in the example validity from a given date (without end date).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 uniquely defines the submitter guarantees the uniqueness of the contents of the dataset.

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 to for describing "physical" objects, including StopPlace, Quay and Facilities/Equipment found on them.

<SiteFrame version="any" id="NSR:SiteFrame:1">
	<!-- ===StoppestederStopPlaces=== -->
	<!-- DetaljeneDetails for StopPlace ogand Quay vises lenger ned i eksempelet 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 stopplace stop place is generally described by with name, short nametransport mode, and location, and should as a minimum have defined overall accessibility information defined to satisfy universal design requirements. (Note that for the more complicated stopplace, this should be modeled as NavigationPaths when relevant.)

Stoppestedet beskrives overordnet med navn, kortnavn, lokasjon og skal som minimum ha definert overordnet tilgjenelighetsinformasjon for å tilfredsstille krav om universell utforming. (Merk at for mer kompliserte stoppestedet bør dette modeleres som NavigationPaths når relevant.)

The stopplace must also define the type of transport and the stopplace type.Accessibility can also be modelled as NavigationPaths if relevant.)

<!-- MerkNote: HoldeplassStopPlace-ID vil komme fra Holdeplassregisteretmust be generated by the stop place registry -->
<StopPlace version="any" id="NSR:StopPlace:12345678">
	<Centroid>
		<Location srsName="WGS84" id="NSR:Location:1">
			<Longitude>10.824609</Longitude>
			<Latitude>59.913915</Latitude>
		</Location>
	</Centroid>
	<AccessibilityAssessment version="any" id="NSR:AccessibilityAssessment:1">
		<MobilityImpairedAccess>true</MobilityImpairedAccess>
		<limitations>
			<AccessibilityLimitation>
				<WheelchairAccess>true</WheelchairAccess>
				<StepFreeAccess>true</StepFreeAccess>
			</AccessibilityLimitation>
		</limitations>
	</AccessibilityAssessment>

	<placeEquipments>
		<GeneralSign id="NSR:GeneralSign:1" version="any">
			<PrivateCode>512</PrivateCode>
			<SignContentType>transportMode</SignContentType>
		</GeneralSign>
	</placeEquipments>

	<TransportMode>bus</TransportMode>
	<StopPlaceType>onstreetBus</StopPlaceType>

	<quays>
		[...]
	</quays>
</StopPlace>

Quay

The individual stopplace for disembarking/ boarding An individual (and exact) position for boarding/alighting is defined as a Quay with connection description, for example relevant . It can have references to nearby roads, direction and relevant info to be presented to the publicfacilities, compass bearing etc. Its most prominent features are coordinate and PublicCode (platform identifier). The Quay always inherits name from its parent StopPlace.

<Quay version="any" id="NSR:Quay:12345679">
	<Centroid>
		<Location>
			<Longitude>59.9139819</Longitude>
			<Latitude>10.8247039</Latitude>
		</Location>
	</Centroid>
	<Lighting>poorlyLit</Lighting>
	<facilities>
		<SiteFacilitySetRef ref="NSR:SiteFacilitySet:timetablePoster"/>
		<SiteFacilitySetRef ref="NSR:SiteFacilitySet:fareInformation"/>
	</facilities>
	<PublicCode>Sør<<PublicCode>A</PublicCode>
	<CompassBearing>200</CompassBearing>
</Quay>

...