Skip to content

Processing Profiles

Jump to bottom
Stefan de Konink edited this page Aug 29, 2025 · 2 revisions

Swiss Profile

The Swiss profile consists of a zip delivery having the following filename patterns:

  1. RESOURCE (ResponsibilitySet, ValueSet, Operator, VehicleType)
  2. SITE (TopographicPlace, StopPlace)
  3. SERVICECALENDAR (AvailabilityCondition)
  4. SERVICE (Direction, Line, DestinationDisplay, ScheduledStopPoint, DefaultConnection)
  5. TIMETABLE (ServiceJourney)
  6. COMMON (ServiceFacilitySet, TypeOfService, JourneyMeeting, InterchangeRule)

When inserted in this order it can be guaranteed that the most possible resolved entities are present upon the moment of insertion. As potential optimisation the insertion of TIMETABLE may occur in parallel. COMMON must follow as last file, due to its excessive number of JourneyMeeting. It would have been a better situation if COMMON would be split between COMMON and JOURNEYMEETING, or the ServiceFacilitySets and TypesOfService being added to the RESOURCE file.

Clone this wiki locally