All our SaaS products have been be updated with the releases associated to this Sprint 128.

Chouette

The last step https://enroute.atlassian.net/wiki/spaces/PUBLIC/pages/2595913729 is now completed. Chouette users can manage Flexible Transport Service by using both GTFS and NeTEx.

The latest features are provided in this Sprint 128 release.

Export Stop Area Flexible Area in NeTEx

When the user exports a Flexible Stop Area, a FlexibleStopPlace should be exported in the NeTEx file:

<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>

Export Flexible Vehicle Journey with LatestArrivalTime/EarliestDepartureTime NeTEx attributes

When the user exports a Route where a Stop Point is flexible, the Chouette NeTEx export contains a NeTEx StopPointInJourneyPattern with FlexiblePointProperties.

<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>

Import flexible NeTEx StopPointInJourneyPattern as Flexible Stop Point

The user can import NeTEx StopPointInJourneyPattern with ScheduledStopPoint associated to FlexibleStopAssignment. In this case, the created Chouette Stop Point is flexible.

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

<ScheduledStopPoint id="scheduled-stop-point-2" version="any"/>

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

Import Flexible Vehicle Journey with EarliestDepartureTime/LatestArrivalTime NeTEx attributes

The user can import a ServiceJourney associated to a ServiceJourneyPattern with a flexible StopPoint with EarliestDepartureTime and LatestArrivalTime. In this case, the both attributes are mandatory (for the moment). If DepartureTime/ArrivalTime are specified, the values are ignored.

<ServiceJourney id="vehicleJourney-1" version="any">
  <Name>Vehicle Journey Sample</Name>
  <dayTypes>
    <DayTypeRef ref="daytype-1" version="any"/>
  </dayTypes>
  <JourneyPatternRef ref="journeypattern-1" version="any"/>
  <passingTimes>
    <TimetabledPassingTime version="any">
      <DepartureTime>06:30:00</DepartureTime>
    </TimetabledPassingTime>
    <TimetabledPassingTime version="any">
      <EarliestDepartureTime>06:35:00</EarliestDepartureTime>
      <LatestArrivalTime>07:00:00</LatestArrivalTime>
    </TimetabledPassingTime>
  </passingTimes>
</ServiceJourney>

Associate Booking Arrangement with Journey Pattern

The user can associate each Journey Pattern (with flexible Stops) with a Booking Arrangement:

In this case, the Booking Arrangement associated is exported/imported in the NeTEx ServiceJourneyPattern:

<ServiceJourneyPattern id="journeypattern-1" version="any">
  <Name>Journey Pattern Sample</Name>
  <RouteRef ref="route-1"/>
  <bookingArrangements>
    <BookingArrangementRef ref="sample"/>
  </bookingArrangements>
  
  <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>

This NeTEx syntax is only by using the next XML schema under validation: https://github.com/NeTEx-CEN/NeTEx/tree/next

Export Booking Arrangement in ServiceJourneyPattern with IDFM IBOO Producer NeTEx Profile

When the user exports a Dataset by using the IDFM IBOO Producer NeTEx Profile, the BookingArrangement associations are only exported into the ServiceJourneyPattern NeTEx resource.

The user can associated BookingArrangement with the Line or the with the Journey Pattern. In the both cases, the NeTEx export contains a BookingArrangementRef in each ServiceJourneyPattern:

<ServiceJourneyPattern id="journeypattern-1" version="any">
  <Name>Journey Pattern Sample</Name>
  <RouteRef ref="route-1"/>
  <bookingArrangements>
    <BookingArrangementRef ref="sample"/>
  </bookingArrangements>
  <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>

Create Document with validity period via Chouette client

The user can create a Document using the Chouette Client by specifying a (partial) validity period:

chouette-client create document --valid-from="2030-01-01" ...
chouette-client create document --valid-from="2030-01-01" --valid-until="2030-01-31" ...

Documentation

The Chouette SaaS documentation has been improved, especially these topics:

The IBOO documentation has been improved :

https://enroute.atlassian.net/wiki/spaces/IBOO/pages/305758223/Import#Cadre-de-version-%E2%80%98NETEX_HORAIRE%E2%80%99