...
The id attribute must follow the pattern: [codespace]:[type]:[id] or [countrycode]:[codespace]:[type]:[id] . Examples:
253:Authority:9010005000000000orSE:253:Authority:9010005000000000.
Be consistent with your choice throughout all of the files.The version must be a positive whole number (integer) or “any”.
The version number must be increased in such a way that the latest version of the object always has the highest number.
We recommend using the pattern YYYYMMDDHHmmSS as version if your non-netex objects are already version controlled with "exists from"-dates.
The Xmlns value of the Codespace-element is provided by Samtrafiken.
ServiceCalendar and DayTypeAssignment
You must use the <Date> element in the DayTypeAssignment when specifying operating days.
We do not support the use of the OperatingPeriodRef and OperatingDayRef elements.
Example:
| Code Block | ||
|---|---|---|
| ||
<DayTypeAssignment order="1" version="any" id="SE:253:DayTypeAssignment:1-20191125">
<!-- Choices OperatingPeriodRef and OperatingDayRef are ignored -->
<Date>2019-11-25</Date>
<DayTypeRef ref="SE:253:DayType:1" version="any"/>
</DayTypeAssignment> |
_shared_data.xml
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<PublicationDelivery xmlns="http://www.netex.org.uk/netex" xmlns:ns2="http://www.opengis.net/gml/3.2">
<PublicationTimestamp>2019-11-27T12:50:21</PublicationTimestamp> <!-- Required Timestamp of export. -->
<ParticipantRef>SAM</ParticipantRef> <!-- Required Codespace for data submitter, participant identifier. We currently don't use this value for anything, so it's not important for our import. -->
<dataObjects>
<CompositeFrame created="2019-11-27T12:50:21" version="20191127125021" id="SE:253:CompositeFrame:1">
<ValidBetween>
<FromDate>2002-01-01T00:00:00</FromDate>
<!-- ToDate is omitted since if there are elements within the frame that have indefinite validity, the frame must also have that. -->
</ValidBetween>
<codespaces>
<Codespace id="253"> <!-- id is the same as Xmlns below -->
<Xmlns>253</Xmlns> <!-- From Samtrafiken's registry of producer numbers, provided by Samtrafiken -->
<XmlnsUrl>http://www.samtrafiken.se/ns/Östgötatrafiken</XmlnsUrl> <!-- "Östgötatrafiken" is based on data source and ensures that the url is unique, but is otherwise ignored during import -->
</Codespace>
</codespaces>
<!-- Recommended defaults used to define common values. -->
<FrameDefaults>
<DefaultLocale>
<TimeZone>Europe/Stockholm</TimeZone>
<DefaultLanguage>se</DefaultLanguage>
</DefaultLocale>
<DefaultLocationSystem>4326</DefaultLocationSystem> <!-- All coordinates are EPSG:4326 WGS84 -->
</FrameDefaults>
<frames>
<ResourceFrame version="20191127125021" id="SE:253:ResourceFrame:1">
<organisations>
<Authority version="20131206" id="SE:253:Authority:9010005000000000">
<CompanyNumber>5560388950</CompanyNumber> <!-- Required -->
<Name>Östgötatrafiken</Name> <!-- Required -->
<LegalName>Östgötatrafiken</LegalName> <!-- Required -->
<OrganisationType>authority</OrganisationType> <!-- Always "authority" -->
</Authority>
<!-- More Authority elements -->
<Operator version="20131211" id="SE:253:Operator:9013005918200000">
<Name>eBuss Motala</Name> <!-- Required -->
<LegalName>eBuss i Sverige AB</LegalName> <!-- Required -->
<OrganisationType>operator</OrganisationType> <!-- Always "operator" -->
</Operator>
<!-- More Operator elements -->
</organisations>
</ResourceFrame>
<ServiceFrame version="20191127125021" id="SE:253:ServiceFrame:1">
<!-- Network elements are refered to from Line elements (in the line-files) and provide common information of the Lines, like their Authority. -->
<Network version="20131206" id="SE:253:Network:9010005000000000">
<Name>Östgötatrafiken</Name> <!-- Required -->
<AuthorityRef ref="SE:253:Authority:9010005000000000" version="20131206"/>
</Network>
<additionalNetworks>
<!-- More Network elements -->
</additionalNetworks>
<routePoints>
<!-- A point that is a stop place in a route. -->
<RoutePoint version="20190426" id="SE:253:RoutePoint:9022005000001001">
<projections>
<PointProjection version="20190426" id="SE:253:PointProjection:9022005000001001">
<ProjectedPointRef ref="SE:253:ScheduledStopPoint:9022005000001001" version="20190426"/>
</PointProjection>
</projections>
</RoutePoint>
<RoutePoint version="20190426" id="SE:253:RoutePoint:9022005000050016">
<projections>
<PointProjection version="20190426" id="SE:253:PointProjection:9022005000001002">
<ProjectedPointRef ref="SE:253:ScheduledStopPoint:9022005000001001" version="20190426"/>
</PointProjection>
</projections>
</RoutePoint>
<!-- More RoutePoint elements -->
</routePoints>
<destinationDisplays>
<!-- The displayed destination for a vehicle, commonly above the front window or onboard information screens, describing the vehicles final (or intermediary) destination. -->
<!-- -->
<DestinationDisplay version="any" id="SE:253:DestinationDisplay:via_55700000037211691">
<FrontText>Västerlösa</FrontText> <!-- Required -->
<PublicCode>573</PublicCode> <!-- Optional Line Designation/number -->
<!-- SideText is ignored -->
</DestinationDisplay>
<DestinationDisplay version="any" id="SE:253:DestinationDisplay:55700000037211691">
<FrontText>Malmslätt</FrontText>
<PublicCode>573</PublicCode>
<vias>
<!-- max 1 via -->
<Via>
<DestinationDisplayRef ref="SE:253:DestinationDisplay:via_55700000037211691" version="any"/>
</Via>
</vias>
</DestinationDisplay>
<!-- More DestinationDisplay elements -->
</destinationDisplays>
<scheduledStopPoints>
<!-- Point for planned disembarking and/or boarding.
All ScheduledStopPoint must be mapped to a corresponding Quay, through PassengerStopAssignment further down the file. -->
<ScheduledStopPoint version="20190426" id="SE:253:ScheduledStopPoint:9022005000001001">
<Name>Norr Tull</Name> <!-- Name is ignored, but useful for human readability -->
</ScheduledStopPoint>
<ScheduledStopPoint version="20190426" id="SE:253:ScheduledStopPoint:9022005001364002">
<Name>Söder Tull</Name>
</ScheduledStopPoint>
<ScheduledStopPoint version="20190426" id="SE:253:ScheduledStopPoint:9022005000057002">
<Name>Öster Tull</Name>
</ScheduledStopPoint>
<!-- More ScheduledStopPoint elements -->
</scheduledStopPoints>
<serviceLinks> <!-- Optional, omit if empty -->
<!-- A ServiceLink describes the actual path a vehicle travels between two stop points. In GTFS this is called Shapes. -->
<ServiceLink version="20190213" id="SE:253:ServiceLink:BUS_9025005000136402_9025005000005702">
<ValidBetween>
<FromDate>2019-02-13T00:00:00</FromDate>
</ValidBetween>
<Distance>338</Distance> <!-- Optional distance in meters (decimals are ignored) defaults to 0 -->
<projections>
<LinkSequenceProjection version="20190213" id="SE:253:LinkSequenceProjection:BUS_9025005000136402_9025005000005702">
<!-- Geometric representation of Link. The LineString is a sequential list of coordinate pairs. -->
<ns2:LineString srsName="4326" ns2:id="LS_BUS_9025005000136402_9025005000005702">
<!-- Coordinate pairs -->
<ns2:posList count="30" srsDimension="2">58.666991 16.180848 58.666982 16.180848 58.66691 16.180899 58.666703 16.181034 58.666325 16.181358 58.666109 16.181545 58.665821 16.1818 58.665749 16.181834 58.665651 16.181833 58.665624 16.181833 58.665328 16.181743 58.664978 16.18155 58.664593 16.181253 58.664494 16.181166 58.664154 16.180869</ns2:posList>
</ns2:LineString>
</LinkSequenceProjection>
</projections>
<FromPointRef ref="SE:253:ScheduledStopPoint:9022005001364002" version="20190426"/> <!-- Required -->
<ToPointRef ref="SE:253:ScheduledStopPoint:9022005000057002" version="20190426"/> <!-- Required -->
<!-- VehicleMode is ignored during import, it is extracted from ServiceJourneys that travel this ServceLink instead -->
</ServiceLink>
<!-- More ServiceLink elements -->
</serviceLinks>
<stopAssignments>
<!-- Mapping between ScheduledStopPoint and Quay -->
<PassengerStopAssignment order="1" version="20190426" id="SE:253:PassengerStopAssignment:9022005000001001">
<ScheduledStopPointRef ref="SE:253:ScheduledStopPoint:9022005000001001" version="20190426"/>
<QuayRef ref="SE:253:Quay:9022005000001001"/>
</PassengerStopAssignment>
<PassengerStopAssignment order="2" version="20190426" id="SE:253:PassengerStopAssignment:9022005000001002">
<ScheduledStopPointRef ref="SE:253:ScheduledStopPoint:9022005001364002" version="20190426"/>
<QuayRef ref="SE:253:Quay:9022005000100216"/>
</PassengerStopAssignment>
<PassengerStopAssignment order="3" version="20190426" id="SE:253:PassengerStopAssignment:9022005000001003">
<ScheduledStopPointRef ref="SE:253:ScheduledStopPoint:9022005000057002" version="20190426"/>
<QuayRef ref="SE:253:Quay:9022005000102017"/>
</PassengerStopAssignment>
<!-- More PassengerStopAssignment elements -->
</stopAssignments>
<notices>
<!-- Text-based notes describing circumstances which cannot be modelled as structured data.
These are mapped to ServiceJourneys in the line-files through NoticeAssignment.
(Note: the example text below should actually be provided as a BookingArrangement (WIP for us))-->
<Notice version="any" id="SE:253:Notice:55700000050931583">
<Text>Turen måste förbeställas på 0771 - 71 10 20 senast 2 timmar före avresa från turens starthållplats.</Text> <!-- Required-->
</Notice>
<!-- More Notice elements -->
</notices>
</ServiceFrame>
<ServiceCalendarFrame version="20191127125021" id="SE:253:ServiceCalendarFrame:1">
<!-- Each unique combination of operating days will create one DayType. -->
<!-- The DayType contains each operating date as a DayTypeAssignment. -->
<dayTypes>
<DayType version="any" id="SE:253:DayType:1"/>
<DayType version="any" id="SE:253:DayType:2"/>
<DayType version="any" id="SE:253:DayType:3"/>
<DayType version="any" id="SE:253:DayType:4"/>
<DayType version="any" id="SE:253:DayType:5"/>
<DayType version="any" id="SE:253:DayType:6"/>
<DayType version="any" id="SE:253:DayType:7"/>
<DayType version="any" id="SE:253:DayType:8"/>
<DayType version="any" id="SE:253:DayType:9"/>
<DayType version="any" id="SE:253:DayType:10"/>
<DayType version="any" id="SE:253:DayType:11"/>
<DayType version="any" id="SE:253:DayType:12"/>
<DayType version="any" id="SE:253:DayType:13"/>
</dayTypes>
<dayTypeAssignments>
<!-- Each DayTypeAssignments maps one operating Date to a DayType -->
<DayTypeAssignment order="1" version="any" id="SE:253:DayTypeAssignment:1-20191125">
<!-- Choices OperatingPeriodRef and OperatingDayRef are ignored -->
<Date>2019-11-25</Date>
<DayTypeRef ref="SE:253:DayType:1" version="any"/>
</DayTypeAssignment>
<DayTypeAssignment order="2" version="any" id="SE:253:DayTypeAssignment:1-20191126">
<Date>2019-11-26</Date>
<DayTypeRef ref="SE:253:DayType:1" version="any"/>
</DayTypeAssignment>
<DayTypeAssignment order="3" version="any" id="SE:253:DayTypeAssignment:1-20191127">
<Date>2019-11-27</Date>
<DayTypeRef ref="SE:253:DayType:1" version="any"/>
</DayTypeAssignment>
<!-- More DayTypeAssignment elements -->
</dayTypeAssignments>
</ServiceCalendarFrame>
</frames>
</CompositeFrame>
</dataObjects>
</PublicationDelivery> |
...