Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Chouette SaaS will provide first features to support Flexible Transport Service description in the coming Sprints.

Here is a preview of these features:

Booking Arrangements & Flexible Line

The user can manage Booking Arrangements which describes the booking rules of associated Flexible Services.

The user can associated a Flexible Line with a Booking Arrangements:

NeTEx Import/Export

The user can import and export a Line and its Booking Arrangement via a NeTex FlexibleLine:

<FlexibleLine id="line-1" version="any">
  <Name>Line Sample</Name>
  <FlexibleLineType>mixedFlexibleAndFixed</FlexibleLineType>

  <BookingContact>
    <Phone>+33 1 23 45 67 89</Phone>
    <Url>https://example.com/info</Url>
  </BookingContact>

  <BookingMethods>callOffice</BookingMethods>
  <BookingAccess>public</BookingAccess>
  <BookWhen>untilPreviousDay</BookWhen>
  <BuyWhen>beforeBoarding</BuyWhen>
  <LatestBookingTime>16:30:00</LatestBookingTime>
  <MinimumBookingPeriod>PT30M</MinimumBookingPeriod>
  <BookingUrl>https://example.com/booking</BookingUrl>
  <BookingNote>
    Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed ac elit
    suscipit, volutpat ipsum at, dignissim velit. Nullam feugiat, orci
    nec egestas placerat, ligula dolor tempus velit
  </BookingNote>
</FlexibleLine>

GTFS Import/Export

The user can import/export Booking Arrangements via GTFS Booking Rules.

In this first version, the GTFS import supports GTFS Trips with the same Booking Rules for a given GTFS Route.

See https://gtfs.org/documentation/schedule/reference/#booking_rulestxt

Flexible Stop Area

The user can define one or several Flexible Areas into a Stop Area:

image-20241105-144034.png

The user can associate one or several Stop Areas.

NeTEx import/export

The user can import and export a Stop Area and its Flexible Areas via a NeTex FlexibleStopPlace:

<FlexibleStopPlace id='zone-tad-1' version="any">
  <Name>FTS Zone 1</Name>
  <!-- Other standard attributes --<
  <areas>
    <FlexibleArea version="any" id="zone-tad-1-area">
      <members>
        <QuayRef ref="quay-1" version="any"/>
        <QuayRef ref="quay-2" version="any"/>
      </members>
    </FlexibleArea>
  </areas>
</FlexibleStopPlace>

GTFS import/export

The user can import and export Stop Area and its Flexible Areas via a GTFS Location Group.

See https://gtfs.org/documentation/schedule/reference/#location_groupstxt

Flexible Stop Point

The user can define a Route with a Flexible Stop Point.

NeTEx import/export

The user can import Route/Journey Pattern including Flexible Stop Points via NeTEx ServiceJourneyPatterns and FlexibleStopAssignments:

<ServiceJourneyPattern id="journeypattern-1" version="any">
  <Name>Journey Pattern Sample</Name>
  <RouteRef ref="route-1"/>
  <pointsInSequence>
    <!-- Normal Stop Point -->
    <StopPointInJourneyPattern id="stop-point-in-journey-pattern-1" order="1" version="any">
      <ScheduledStopPointRef ref="scheduled-stop-point-1" version="any"/>
    </StopPointInJourneyPattern>

    <!-- Flexible Stop Point -->
    <StopPointInJourneyPattern id="stop-point-in-journey-pattern-2" order="2" version="any">
      <ScheduledStopPointRef ref="scheduled-stop-point-zone-tad-1" version="any"/>

      <FlexiblePointProperties>
        <PointStandingForAZone>true</PointStandingForAZone>
        <ZoneContainingStops>true</ZoneContainingStops>
      </FlexiblePointProperties>
    </StopPointInJourneyPattern>
  </pointsInSequence>
</ServiceJourneyPattern>

<ScheduledStopPoint id="scheduled-stop-point-zone-tad-1" version="any"/>

<FlexibleStopAssignment id="flexible-stop-assignment-1" order="1" version="any">
  <ScheduledStopPointRef ref="scheduled-stop-point-zone-tad-1" version="any"/>
  <FlexibleStopPlaceRef ref="zone-tad-1"  version="any"/>
</FlexibleStopAssignment>

GTFS Import/Export

The GTFS format doesn’t support Route / Journey Pattern concepts. Chouette SaaS import/export manage them implicitely via GTFS Trips.

Flexible Passing Time

When associated to a Flexible Stop Point, the user can define a time window in place of the classic departure/arrival time.

vehicle_journeys - editor (4).png

NeTEx import/export

The user can import/export Vehicle Journeys with flexible Stop Points and associated time windows via NeTEx Service Journeys and LatestArrivalTime/EarliestDepartureTime attributes.

<ServiceJourney version="15" id="SKY:ServiceJourney:5979d025-1d5d-45a8-a9ec-b1af9ca0fa34">
  <Name>Service Journey Sample</Name>
  <dayTypes>
    <DayTypeRef ref="daytype-1"/>
  </dayTypes>
  <JourneyPatternRef ref="journeypattern-1" version="any"/>
  <passingTimes>
    <TimetabledPassingTime version="any" id="1">
      <StopPointInJourneyPatternRef ref="" version="13"/>
      <DepartureTime>16:00:00</DepartureTime>
    </TimetabledPassingTime>
    <TimetabledPassingTime version="any" id="2">
      <StopPointInJourneyPatternRef ref="scheduled-stop-point-zone-tad-1" version="any"/>
      <LatestArrivalTime>20:00:00</LatestArrivalTime>
      <EarliestDepartureTime>16:00:00</EarliestDepartureTime>
    </TimetabledPassingTime>
  </passingTimes>
</ServiceJourney>

GTFS Import/Export

The user can import and export GTFS Trips with Flex attributes:

  • location_group_id

  • start_pickup_drop_off_window/end_pickup_drop_off_window

  • pickup_booking_rule_id/drop_off_booking_rule_id

  • pickup_type/drop_off_type

See https://gtfs.org/documentation/schedule/reference/#stop_timestxt

  • No labels