Versions Compared

Version Old Version 1 New Version 2
Changes made by

Copy Page Tree

Hans Inge Letnes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

InnholdContent

Table of Contents

...

Geographical location indications (for

...

Line 109, Oslo)

...

Journeypattern

Et JourneyPattern kan defineres som A JourneyPattern can be defined as pointsInSequence (en sortert liste av punkter, vist nærmere i annet eksempel) og/eller linksInSequence (en sortert liste av lenker mellom to punkter).

Faktisk kjørerute skal i henhold til NeTEx NORWEGIAN PROFILE defineres så høynivå som mulig, og i de fleste tilfeller anbefales det derfor at dette gjøres som et sett av 637370789 med Link projections som beskriver punktene denne følger. Disse bør ved hjelp av tilstrekkelige GML-koordinater (gml:pos) beskrive traseen entydig, slik at linjens JourneyPattern vises korrekt i karttjenester.

I noen tilfeller (f.eks. flyruter) kan dette alternativt gjøres overordnet ved hjelp av linjens RoutePoints, siden det vil være tilstrekkelig å vise trasèen i kart som en rett linje mellom disse to stedene.

...

a sorted list of points, detailed in other example) and / or linksInSequence (a sorted list of links between two points).

According to The Norwegian NeTEx Profile, the actual route must be defined as high as possible, and in most cases it is recommended that this be done as a set of 637370789 with  Link projections describing the points this follows. These should describe the path unambiguously using sufficient GML coordinates (gml: pos) so that the line's  JourneyPattern is correctly displayed in map services.

In some cases (eg, flight routes), this may alternatively be done by the line's RoutePoints, since it will suffice to display the route in maps as a straight line between these two locations.


Info

See also officialNeTex White Papers, in particular 06.NeTEx-Network-WhitePaper, hvor dette aspektet er beskrevet nærmerewhere this aspect is described in detail.

...

Hele XML eksempelfilen ligger på prosjektets GitHub-repository under The entire XML sample file is located on the project's GitHub repository below https://github.com/entur/profile-norway-examples/blob/master/netex/Full_PublicationDelivery_109_Oslo_morningbus_example.xml

PublicationDelivery

Info

Fordi andre relevante datastrukturer i eksempelet allerede er gjennomgått i Because other relevant datastructures in the example have already been reviewed in Simple route - Bus (rhytmbased departure) (i arbeid) / Simple route - Bus (i arbeid),  blir kun definisjon av serviceLinks samt bruk av disse i linksInSequence (i JourneyPattern) gjennomgått i dette dokumentetonly definition of serviceLinks and their use in linksInSequence (in JourneyPattern) are reviewed in this document.

Service Frame

637370789 med  with Link projections beskriver ytterligere geografiske punkter mellom  describes furterh geographical points between  StopPoints / TimingPoints .

Code Block
languagexml
<serviceLinks>
	<ServiceLink version="any" id="unibuss:sl:helsfyr_to_brynseng">
		<projections>
			<LinkSequenceProjection version="any" id="unibuss:lsp:109:helsfyr_to_brynseng">
				<gml:LineString srsName="WGS84" gml:id="helsfyr_to_brynseng">
					<gml:pos>59.911925 10.807198</gml:pos>
					<gml:pos>59.910395 10.813012</gml:pos>
				</gml:LineString>
			</LinkSequenceProjection>
		</projections>
		<FromPointRef version="any" ref="unibuss:ssp:helfyr_t"/>
		<ToPointRef version="any" ref="unibuss:ssp:brynseng_t"/>
	</ServiceLink>
[...]	
	<ServiceLink version="any" id="unibuss:sl:ryen_to_holtet">
		<projections>
			<LinkSequenceProjection version="any" id="unibuss:lsp:109:ryen_to_holtet">
				<gml:LineString srsName="WGS84" gml:id="ryen_to_holtet">
					<gml:pos>59.894780 10.804309</gml:pos>
					<gml:pos>59.892531 10.804000</gml:pos>
					<gml:pos>59.888996 10.805961</gml:pos>
					<gml:pos>59.887608 10.806368</gml:pos>
					<gml:pos>59.886410 10.800586</gml:pos>
					<gml:pos>59.885832 10.792943</gml:pos>
					<gml:pos>59.885392 10.788938</gml:pos>
					<gml:pos>59.885630 10.784435</gml:pos>
					<gml:pos>59.883864 10.783759</gml:pos>
					<gml:pos>59.881872 10.783770</gml:pos>
				</gml:LineString>
			</LinkSequenceProjection>
		</projections>
		<FromPointRef version="any" ref="unibuss:ssp:ryen_t"/>
		<ToPointRef version="any" ref="unibuss:ssp:holtet"/>
	</ServiceLink>
</serviceLinks>

linksInSequence

Lenkene som beskriver hvordan linjens kjøremønster skal projiseres på kart brukes sammen med stoppestedene (evt. timing-punkter) for å nøyaktig angi linjens The links describing how the line's journeypattern is to be projected onto maps are used in conjunction with the stops (possibly timing points) to accurately specify the line's JourneyPattern.

Code Block
languagexml
<journeyPatterns>
	<JourneyPattern version="any" id="unibuss:jp:109">
		<RouteRef ref="unibuss:rt:109"/>
		<DestinationDisplayRef ref="unibuss:dd:holtet"/>
		<pointsInSequence>
		[...]
		</pointsInSequence>
		<linksInSequence>
			<ServiceLinkInJourneyPattern version="any" id="unibuss:slijp:helsfyr_to_brynseng" order="1">
				<ServiceLinkRef version="any" ref="unibuss:sl:helsfyr_to_brynseng"/>
			</ServiceLinkInJourneyPattern>
			<ServiceLinkInJourneyPattern version="any" id="unibuss:slijp:brynseng_to_hoyenhall" order="2">
				<ServiceLinkRef version="any" ref="unibuss:sl:brynseng_to_hoyenhall"/>
			</ServiceLinkInJourneyPattern>
			<ServiceLinkInJourneyPattern version="any" id="unibuss:slijp:hoyenhall_to_manglerud" order="3">
				<ServiceLinkRef version="any" ref="unibuss:sl:hoyenhall_to_manglerud"/>
			</ServiceLinkInJourneyPattern>
			<ServiceLinkInJourneyPattern version="any" id="unibuss:slijp:manglerud_to_ryen" order="4">
				<ServiceLinkRef version="any" ref="unibuss:sl:manglerud_to_ryen"/>
			</ServiceLinkInJourneyPattern>
			<ServiceLinkInJourneyPattern version="any" id="unibuss:slijp:ryen_to_holtet" order="5">
				<ServiceLinkRef version="any" ref="unibuss:sl:ryen_to_holtet"/>
			</ServiceLinkInJourneyPattern>
		</linksInSequence>
	</JourneyPattern>
</journeyPatterns>

...