All our products have been updated on Jul 22, 2024 with the releases associated to this Sprint 113.

Chouette

Retrieve a file via an SFTP URL

The user can define a Source with a Downloader type “SFTP” and specify an SFTP URL:

screenshot-chouette-core-test_enroute_mobi-2024_10_02-16_32_15.png

Ara

Broadcast Occupancy in SIRI EstimatedTimetable

When an EstimatedCall is broadcasted in SIRI Estimated Timetable, Ara includes the Vehicle occupancy when the associated Stop Visit is the next Stop Visit of this Vehicle (same logic than Occupancy is broadcasted into the StopMonitoringDelivery).

<siri:EstimatedCall>
  <siri:StopPointRef>NINOXE:StopPoint:SP:24:LOC</siri:StopPointRef>
  <siri:VisitNumber>4</siri:VisitNumber>
  <siri:StopPointName>Tutute</siri:StopPointName>
  <siri:Occupancy>seatsAvailable</siri:Occupancy>
  <siri:VehicleAtStop>false</siri:VehicleAtStop> <!-- VehicleAtStop here seems invalid -->
  <siri:DestinationDisplay>Pouet-pouet</siri:DestinationDisplay>
  <siri:AimedArrivalTime>2017-01-01T15:00:00.000Z</siri:AimedArrivalTime>
  <siri:ExpectedArrivalTime>2017-01-01T15:01:00.000Z</siri:ExpectedArrivalTime>
  <siri:ArrivalStatus>Delayed</siri:ArrivalStatus>
  <siri:AimedDepartureTime>2017-01-01T15:01:00.000Z</siri:AimedDepartureTime>
  <siri:ExpectedDepartureTime>2017-01-01T15:02:00.000Z</siri:ExpectedDepartureTime>
  <siri:DepartureStatus>Delayed</siri:DepartureStatus>
</siri:EstimatedCall>

Support Situation Consequence Condition attribute

Ara can collect and broadcast Situation Consequences with an attribute Condition:

<Consequence>
  <Period>
    <StartTime>2030-01-01T12:00:00.000Z</StartTime>
    <EndTime>2030-01-01T16:00:00.000Z</EndTime>
  </Period>

  <Condition>delay</Condition>
  <Severity>severe</Severity>

  <Affects>
    <Networks>
      <AffectedNetwork>
        <AffectedLine>
          <LineRef>Line:3</LineRef>
          <Sections>
            <AffectedSection>
              <IndirectSectionRef>
                <FirstStopPointRef>StopPoint:24</FirstStopPointRef>
                <LastStopPointRef>StopPoint:25</LastStopPointRef>
              </IndirectSectionRef>
            </AffectedSection>
          </Sections>
        </AffectedLine>
      </AffectedNetwork>
    </Networks>
  </Affects>

  <Blocking>
    <JourneyPlanner>true</JourneyPlanner>
    <RealTime>true</RealTime>
  </Blocking>
</Consequence>

All values defined by SIRI are supported.

Collect Situations using GTFS-RT Service Alert

When the user uses a GTFS-RT Collector, if the read GTFS-RT feed contains Service Alerts, they are collected as Situations.

These Situations can be broadcasted (as any other Situations) using SIRI Situation Exchange or GTFS-RT Broadcaster (see below).

Broadcast Situations using GTFS-RT Service Alert

When the user uses a GTFS-RT Broadcaster, existing Situations are included in the GTFS-RT feed as Service Alerts.

Improve Referents support in SIRI StopPointDiscovery broadcast

When several particular Stop Areas have a same referent Stop Area (with expected code space), the referent Stop Area is used. The Referent Stop Area name is used. All lines associated with the referent and particulars are listed .

For a given Stop Area, when several particular Lines have a same referent Line (with expected code space), only the referent Line should be used.

<StopPointsDiscoveryResponse xmlns:sw='http://wsdl.siri.org.uk' xmlns:siri='http://www.siri.org.uk/siri'>
  <Answer>
    <ResponseTimestamp>2030-01-01T12:00:00.000Z</ResponseTimestamp>
    <Status>true</Status>
    <AnnotatedStopPointRef>
      <StopPointRef>particular-stop</StopPointRef>
      <Monitored>true</Monitored>
      <StopName>Particular Stop</StopName>
      <Lines>
        <LineRef>particular-line-1</LineRef>
        <LineRef>referent-line-1</LineRef>
      </Lines>
    </AnnotatedStopPointRef>
    <AnnotatedStopPointRef>
      <StopPointRef>referent-stop</StopPointRef>
      <Monitored>true</Monitored>
      <StopName>Referent Stop</StopName>
      <Lines>
        <LineRef>particular-line-1</LineRef>
        <LineRef>referent-line-1</LineRef>
        <LineRef>referent-line-2</LineRef>
      </Lines>
    </AnnotatedStopPointRef>
  </Answer>
  <AnswerExtension/>
</StopPointsDiscoveryResponse>

Define Maximum MonitoredStopVisit + MonitoredStopVisitCancellation broadcasted in the same notification

When the setting broadcast.siri.stop_monitoring.maximum_resources_per_delivery is used, the total number of MonitoredStopVisit + MonitoredStopVisitCancellation on a StopMonitoringDelivery is limited to this value.

This setting can ensure that StopMonitoring notifications can be consume by SIRI implementations with an hard coded limit.