Versions Compared

Old Version 16

changes.mady.by.user Johan Wiklund

Saved on

compared with

New Version Current

changes.mady.by.user Johan Wiklund

Saved on

Key

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

InnholdContent

Table of Contents

Line 61A, Oslo

Infonote

According to the Norwegian NeTEx-profile, each Line must be defined in its own separate XML-file.

...

Line 61A is a circular bus line passing the following stops:

  • Tveita T

  • Tveita bedriftsområde

  • Solfjellet

  • Larsbråten

  • Tveita bedriftsområde

  • Tveita

  • Tveita T

Departures are fixed to leave 15 minutes past every whole hour between 0915 and 1415, Monday through Saturday. The Line is modelled with a Route, where Timetable is modelled as Periodical Journeys (TemplateServiceJourney) based on RhythmicalJourneyGroup.

...

Defines the contents of the submitted file 

Frameset
Code Block
languagexml
titleFrameset
<?xml version="1.0" encoding="UTF-8"?>
<PublicationDelivery 
    version="1.0" 
    xmlns="http://www.netex.org.uk/netex" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.netex.org.uk/netex ../../xsd/NeTEx_publication.xsd">
    [...]
    <dataObjects>
        <CompositeFrame version="1" created="2015-12-13T00:00:00Z" id="RUT:Norway:CompositeFrame:0061">
            [...]
            <frames>
                <ResourceFrame version="any" id="RUT:ResourceFrame:RF1"> 
                [...]
                </ResourceFrame>
                
                <SiteFrame version="any" id="RUT:SiteFrame:SF01">
                [...]
                </SiteFrame>
                
                <ServiceFrame version="any" id="RUT:ServiceFrame:0061">
                [...]
                </ServiceFrame>
                
                <ServiceCalendarFrame version="any" id="RUT:ServiceCalendarFrame:SCF01">
                [...]
                </ServiceCalendarFrame>
                
                <TimetableFrame version="any" id="RUT:TimetableFrame:TF02">
                [...]
                </TimetableFrame>
            </frames>
        </CompositeFrame>
    </dataObjects>
</PublicationDelivery>

...

Info

Each operator, as well as other authorities, has its own unique namespace, allocated by Entur.

Codespace

Code Block
languagexml
titleCodespace
collapsetrue
<codespaces>
    <!-- Codespace for Ruter -->
    <Codespace id="ruter">
        <Xmlns>RUT</Xmlns>
        <XmlnsUrl>http://www.ruter.no/</XmlnsUrl>
    </Codespace>
    <!-- Codespace for national stop place registry-->
    <Codespace id="nhr">
        <Xmlns>NHR</Xmlns>
        <XmlnsUrl>http://stoppested.entur.org</XmlnsUrl>
    </Codespace>
</codespaces>

ResourceFrame

Organisation

organisations
Code Block
languagexml
titleorganisations
collapsetrue
<organisations>
	<!-- Owner of line -->
    <Authority version="1" id="RUT:Company:0">
        <CompanyNumber>991609407</CompanyNumber>
        <!-- Organisasjonsnummer -->
        <Name>Ruter</Name>
        <LegalName>RUTER AS</LegalName>
        <OrganisationType>authority</OrganisationType>
    </Authority>
    <!-- Operator of line -->
    <Operator version="1" id="RUT:Company:1">
        <CompanyNumber>985615616</CompanyNumber>
        <Name>Unibuss</Name>
        <LegalName>UNIBUSS AS</LegalName>
        <CustomerServiceContactDetails>
            <Phone>0047 177</Phone>
            <Url>http://www.ruter.no</Url>
            <FurtherDetails>Kontaktskjema på websider</FurtherDetails>
        </CustomerServiceContactDetails>
    </Operator>
</organisations>

...

Description of a stop place can be found in more detail under Stop place - Simple. Other files should only contain simplified references to the stop places with IDs from the stop place registry. 

SiteFrame
Code Block
collapse
languagexml
titleSiteFrame
true
<SiteFrame version="any" id="RUT:SiteFrame:SF01">
    <stopPlaces>
        <!-- The stops have been given ficticious ID's -->
        <StopPlace version="1" id="NHR:StopArea:03011537">
            <Name>Larsbr&#229;ten</Name>
            <quays>
                <Quay version="1" id="NHR:StopArea:0301153701"/>
            </quays>
        </StopPlace>
        <StopPlace version="1" id="NHR:StopArea:03011525">
            <Name>Tveita bedriftsomr&#229;de</Name>
            <quays>
                <Quay version="1" id="NHR:StopArea:0301152501"/>
                <Quay version="1" id="NHR:StopArea:0301152502"/>
            </quays>
        </StopPlace>
        <StopPlace version="1" id="NHR:StopArea:03011536">
            <Name>Solfjellet</Name>
            <quays>
                <Quay version="1" id="NHR:StopArea:0301153601"/>
            </quays>
        </StopPlace>
        <StopPlace version="1" id="NHR:StopArea:03011522">
            <Name>Tveita</Name>
            <quays>
                <Quay version="1" id="NHR:StopArea:0301152202"/>
            </quays>
        </StopPlace>
        <StopPlace version="1" id="NHR:StopArea:03011521">
            <Name>Tveita T</Name>
            <quays>
                <Quay version="1" id="NHR:StopArea:0301152101"/>
                <Quay version="1" id="NHR:StopArea:0301152102"/>
            </quays>
        </StopPlace>
    </stopPlaces>
</SiteFrame>

...

Defines data for a Route, such as Networks, Lines stops, etc.

General concepts

Network

  • Lines under a common "umbrella", e.g. the bus lines owned by Ruter.

Line

  • A group of Routes known by the same marketed name, e.g. Metro Line 2.

Direction

  • Defines the direction of a line. Line 61A is a clockwise roundtrip.

DestinationDisplay

...

  • Specifies the destination information for the Line (commonly matching the text displayed on the front of the bus).

...

...

Network | Line | Direction | Destination
collapse
Code Block
languagetruexml
<Network version="1" changed="2015-12-13T00:00:00Z" id="RUT:GroupOfLine:RuterBuss">
    <Name>Ruter</Name>
</Network>
[...]
<Line version="any" id="RUT:Line:0061">
    <Name>Tveita Solfjellet</Name>
    <TransportMode>bus</TransportMode>
    <PublicCode>61A</PublicCode>
    <routes>
        <!-- The line has no return direction, as it is circular -->
        <RouteRef version="1" ref="RUT:Route:0061101"/>
    </routes>
</Line>
[...]
<Direction version="any" id="RUT:Route:0061101:Direction">
    <Name>Round trip</Name>
    <DirectionType>clockwise</DirectionType>
</Direction>
[...]
<destinationDisplays>
    <DestinationDisplay version="any" id="RUT:DestinationDisplay:DST_Solfjellet">
        <FrontText>Solfjellet</FrontText>
    </DestinationDisplay>
    <DestinationDisplay version="any" id="RUT:DestinationDisplay:DST_TveitaT">
        <FrontText>Tveita T</FrontText>
    </DestinationDisplay>
</destinationDisplays>

...

Linking of a ScheduledStopPoint to a defined StopPlace/Quay is done through a PassengerStopAssignment. (All StopPlaces and Quays belong to the NSR codespace.)

StopAssignment
Code Block
languagexml
titleStopAssignment
collapsetrue
<stopAssignments>
	<PassengerStopAssignment version="any" order="1" id="RUT:PassengerStopAssignment:0061101001">
		<!-- Hvilket ScheduledStopPoint som mappes til ... -->
		<ScheduledStopPointRef version="1" ref="RUT:StopPoint:0061101001"/>
		<!-- .. hvilket stopPlace ... og hvis mulig -->
		<StopPlaceRef version="1" ref="NSR:StopPlace:03011521"/>
		<!-- hvilken quay kjøretøyet stopper ved -->
		<QuayRef version="1" ref="NSR:Quay:0301152101"/>
	</PassengerStopAssignment>
	<PassengerStopAssignment version="any" order="2" id="RUT:PassengerStopAssignment:0061101002">
		<ScheduledStopPointRef version="1" ref="RUT:StopPoint:0061101002"/>
		<StopPlaceRef version="1" ref="NSR:StopPlace:03011525"/>
		<QuayRef version="1" ref="NSR:Quay:0301152501"/>
	</PassengerStopAssignment>
	<PassengerStopAssignment version="any" order="3" id="RUT:PassengerStopAssignment:0061101003">
		<ScheduledStopPointRef version="1" ref="RUT:StopPoint:0061101003"/>
		<StopPlaceRef version="1" ref="NSR:StopPlace:03011536"/>
		<QuayRef version="1" ref="NSR:Quay:0301153601"/>
	</PassengerStopAssignment>
	<PassengerStopAssignment version="any" order="4" id="RUT:PassengerStopAssignment:0061101004">
		<ScheduledStopPointRef version="1" ref="RUT:StopPoint:0061101004"/>
		<StopPlaceRef version="1" ref="NSR:StopPlace:03011537"/>
		<QuayRef version="1" ref="NSR:Quay:0301153701"/>
	</PassengerStopAssignment>
	<PassengerStopAssignment version="any" order="5" id="RUT:PassengerStopAssignment:0061101005">
		<ScheduledStopPointRef version="1" ref="RUT:StopPoint:0061101005"/>
		<StopPlaceRef version="1" ref="NSR:StopPlace:03011525"/>
		<QuayRef version="1" ref="NSR:Quay:0301152502"/>
	</PassengerStopAssignment>
	<PassengerStopAssignment version="any" order="6" id="RUT:PassengerStopAssignment:0061101006">
		<ScheduledStopPointRef version="1" ref="RUT:StopPoint:0061101006"/>
		<StopPlaceRef version="1" ref="NSR:StopPlace:03011522"/>
		<QuayRef version="1" ref="NSR:Quay:0301152202"/>
	</PassengerStopAssignment>
	<PassengerStopAssignment version="any" order="7" id="RUT:PassengerStopAssignment:0061101007">
		<ScheduledStopPointRef version="1" ref="RUT:StopPoint:0061101007"/>
		<StopPlaceRef version="1" ref="NSR:StopPlace:03011521"/>
		<QuayRef version="1" ref="NSR:Quay:0301152102"/>
	</PassengerStopAssignment>
</stopAssignments>

...

Notices (Free text fields, sometimes referred to as footnotes) referring to the entire Line, are modelled in the ServiceFrame.

Specific noticeAssignmens for a JourneyPattern is specified/referenced under PointInJourneyPattern and correspondingly for a VehicleJourney under Call.

Code Block
languagexml
<notices>
	<Notice version="any" id="RUT:Notice:1">
		<Text>On residential roads, bus 61A can make additional stops besides the regular stops. Remember to hail the vehicle!</Text>
	</Notice>
</notices>

Service Calendar Frame

Defines data for time, days, periods, and other calendar items.

...

Validity period for the timetable is indicated by AvailabilityCondition.

validityConditions
Code Block
languagexml
titlevalidityConditions
collapsetrue
<validityConditions>
	<ValidBetween>
		<FromDate>2016-01-10T00:00:00</FromDate>
		<ToDate>2016-12-20T00:00:00</ToDate>
	</ValidBetween>
</validityConditions>

...

A specific trip with passengers for a given day type can be specified in the following ways:

For a line like 61A, which has a recurring departure time (Simple route - Bus (rhythm based departure)#Timeband) and follows the same route (pattern) every day, a TemplateServiceJourney with a RhythmicalJourneyGroup describing the departure pattern can be used.

...