NeTEx will be transfered as files.

We will have three different file types:

  • STOP_OFFER: stops, quays, transfer times and accessiblity related to sites at some point
  • NETWORK_OFFER:lines, routes, timetables
  • INTERCHANGE: interchange, “Durchbindungen”

The first two are valid according to the XSD. INTERCHANGE only as far as we use versionRef intead of version.

NETWORK_OFFER is per operator and in some cases per area.

This distinction leads to some redundancy.However, the files can still be transfered efficiently.

Content of each file

classDiagram
class STOP_OFFER{
    SiteFrame: SiteFrame
    TopographicPlaces: TopographicPlace
    StopPlaces StopPlace
    Quays: Quay
    ServiceFrame: ServiceFrame
    DefaultConnections: DefaultConnection
    SiteConnections: SiteConnections
} 

class NETWORK_OFFER{
    ResourceFrame: ResourceFrame
    Operators: Operators
    ResponsibilitySets: ResponsibilitySets
    TypesOfNotice: TypeOfNotice
    TypesOfProductCategory:TypesOfProductCategory
    TypesOfNotice: TypeOfNotice
    ServoceCalendarFrame: ServiceCalendarFrame
    VehicleTypes: VehicleType
    DayTypes: DayType 
    ServiceCalendar: ServiceCalendar
    DaytypeAssignments: DaytypeAssignment
    DetinationDisplays: DestinationDisplay
    ServiceFrame: ServiceFrame
    Lines: Line
    ServiceJourneyPatterns: ServiceJourneyPattern
    ScheduledStopPoint: ScheduldedStopPoint
    PassengerStopAssignments: PassengerStopAssignment
    Notices: Notice
    TimetableFrame: TimetableFrame
    ServiceJourneys: ServiceJourneyPattern
    ServiceFacilitySets: ServiceFacilitySet
    TrainNumbers : TrainNumber
}
class INTERCHANGE {
    ServiceJourneyInterchanges : ServiceJourneyInterchange
}

STOP_OFFER:

  • Contains everything related to stops
  • Later accessibility

NETWORK_OFFER:

  • By operator (legal) and sometimes region (e.g. canton)
  • Contains the ResourceFrame, CalendarFrame, ServiceFrame, TimetableFrame
  • Is self-sufficient from ref/id side
  • Eventually a reduced StopPlace, Quay could be added, but for the time being we won’t do this.

INTERCHANGE

  • Contains interchanges, Spliting, joining and “Durchbindungen”.
  • ref/id can’t be checked by the schema. Therefore we use the attribute versionRef instead of version.

Swiss operators deliver NETWORK_OFFER and INTERCHANGE to INFO+. STOP_OFFER is only needed for data not stored in ATLAS. INFO+ will deliver a completed STOP_OFFER.

Naming conventions

IT-Environments:

  • Development: dev
  • Test: test
  • Integration_ int
  • Production: prod

The name of each XML file is composed of the following information:

Content Example Description
IT-Environment TEST DEV,TEST,INT,PROD
Format of the file NETEX (Describe the format (NETEX)
Content of the file TT Timetable
Version 2.0 Number of the version of the NeTEx .xsd schema
Country CHE ISO code of the country for which the file was produced
Provider SKI Name of the provider
Time table year 2026 period of he data (always a year for now)
Name of Export oev-schweiz Defines the scope of the timetable data (e.g. bernmobilor for the whole of Switzerland oev-schweiz
Type of file STOP_OFFER, NETWORK_OFFER, INTERCHANGE Describes the content
Date and Time 202606101200 Datum und Zeit der Produktion des Files Format : YYYYMMDDHHMM

Example: TEST_NETEX_TT_2.0_CHE_SKI_2026_OEV-SCHWEIZ_STOP_OFFER_202301250401.xml

All Files are embedded in a zip-File. The name of the zip-file is composed of the following in-formation:

Content Example Description
IT-Environment DEV,TEST,INT In the production environment, the prefix PROD is not written in the name
Format of the file NETEX Describe the format (NETEX)
Content of the file TT Describe the content (TimeTable)
Version 2.0 Number of the version of the NeTEx .xsd schema
Country CHE ISO code of the country for which the file was produced
Provider SKI Name of the provider
Time period 2026 Time period of he data
Name of Export oev-schweiz Defines the scope of the timetable data (e.g. bernmobilor for the whole of Switzerland oev-schweiz
Date and Time 202606131500 Datum und Zeit der Produktion des Files Format : YYYYMMDDHHMM

Example :TEST_NETEX_TT_2.0_CHE_SKI_2026_OEV-SCHWEIZ__202602010402.zip

Zip structure

All files in a delivery are zipped into a single one according to the name structure above.

Encoding

All data is encoded as UTF-8 without BOM.

Data transfer

The data transfer will be defined by INFO+. A version of the full swiss data will be available on https://opentransportdata.swiss/ for download.

File sent by data provider to SKI

We suggest that the partner name consists of the short name of the partner and necessary additions to identify the system. In addition, the number of the timetable period is to be indicated in the name, as well as the date and time of creation of the file

Examples.: test_zvv_2024_20231112_095217.zip, prod_tl_2024_20231114_152836.zip

The file name must be agreed on between the data provider and SKI. Generally it is agreed that delivery can be on network, operator or line base.

TODO handling of partial deliveries and mixed lines will be added later.

File sent by SKI to data receivers

As the quantity of data is very large for a single XML-file, SKI provides the data a list of XML files. In addition to the XML files, SKI provides a README file listing the contents of each XML file.