Content
| Table of Contents |
|---|
Geographical location indications (for Line 109, Oslo)
...
A JourneyPattern can be defined as pointsInSequence (a sorted list of points, detailed in other examples) and/or linksInSequence (a sorted list of links between two points).
According to The Norwegian Nordic NeTEx Profile, the actual route must be defined as at the highest possible level in the XML structure, and in most cases, it is recommended that this be done as a set of 637370789 Projeksjon#serviceLinks with Link projections describing the points it follows. These should unambiguously describe the path using sufficient GML coordinates (gml:pos) so that the line's JourneyPattern is correctly displayed on maps.
In some cases (e.g. air routes), this may be done using the line's RoutePoints, since it will suffice to display the route as a straight line between these two locations.
| Info |
|---|
See also official NeTex White Papers, in particular 06.NeTEx-Network-WhitePaper, where this aspect is described in detail. |
Link
The entire XML sample file is located XML example in it its entirety can be found in the GitHub repository below : https://github.com/entur/profile-norway-examples/blob/master/netex/Full_PublicationDelivery_109_Oslo_morningbus_example.xml
...
| Info |
|---|
Because other relevant data structures in the example have already been described in Simple rhythm based bus line / Simple bus line, only the definition of serviceLinks and their use in linksInSequence (in JourneyPattern) are described in this document. |
Service Frame
serviceLinks
637370789Projeksjon#serviceLinks with Link projections describes additional geographical points between StopPoints/TimingPoints .
...