Sprint 101
All our products have been updated on Nov 15, 2023 with the releases associated to this Sprint 101.
Chouette
Support GTFS file with subfolders
The user can now import an invalid GTFS file which uses subfolders to organise GTFS content files:
Chouette will ignore these subfolders and read GTFS resources.
This kind of GTFS files is now officially invalid: https://github.com/google/transit/issues/377. You can use Chouette to create valid GTFS files.
Filter GTFS Routes before Source import
The user can define the GTFS Route identifiers which must be kept into an Source file. Chouette will process the GTFS file to retain only information associated to the given GTFS Routes (aka Lines).
This feature can be used for example to retrieve local lines from a national open data provider .
Search Points of Interest
The user can search Points of Interest by:
name
zip code
city name
category
provider
Merge performance
Chouette now merges faster a dataset with huge numbers of Routes and Journey Patterns.
End of support - Import several datasets in imports
The user can no longer imports several datasets by a single import. This feature was only possible in unused configurations in some NeTEx profiles.
Ara
Request SIRI Vehicle Monitoring by filtering by Vehicle
The user can request the SIRI Vehicle Monitoring Ara Service by requesting a given Vehicle (aka VehicleRef)
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<sw:GetVehicleMonitoring xmlns:sw="http://wsdl.siri.org.uk" xmlns:siri="http://www.siri.org.uk/siri">
<ServiceRequestInfo>
<siri:RequestTimestamp>2023-11-10T13:49:29.175Z</siri:RequestTimestamp>
<siri:RequestorRef>user</siri:RequestorRef>
<siri:MessageIdentifier>539d38e2-9cb4-4bd3-8539-5779ab988f52</siri:MessageIdentifier>
</ServiceRequestInfo>
<Request version="2.0:FR-IDF-2.4">
<siri:RequestTimestamp>2023-11-10T13:49:29.175Z</siri:RequestTimestamp>
<siri:MessageIdentifier>539d38e2-9cb4-4bd3-8539-5779ab988f52</siri:MessageIdentifier>
<siri:VehicleRef>742</siri:VehicleRef>
</Request>
<RequestExtension />
</sw:GetVehicleMonitoring>
</soap:Body>
</soap:Envelope>Include RecordedCalls in SIRI Estimated Timetable responses
The user can use the Partner setting broadcast.recorded_calls.duration to define a default duration while passed Stop Visits are included in the SIRI Estimated TimeTable responses as RecordedCall elements.
The Estimated Timetable responses should look like:
<?xml version='1.0' encoding='utf-8'?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<sw:GetEstimatedTimetableResponse xmlns:sw="http://wsdl.siri.org.uk" xmlns:siri="http://www.siri.org.uk/siri">
<ServiceDeliveryInfo>
<siri:ResponseTimestamp>2017-01-01T12:00:00.000Z</siri:ResponseTimestamp>
<siri:ProducerRef>Ara</siri:ProducerRef>
<siri:ResponseMessageIdentifier>6ba7b814-9dad-11d1-c-00c04fd430c8</siri:ResponseMessageIdentifier>
<siri:RequestMessageRef>138852e0-8462-11ee-b013-bb5f2f680490</siri:RequestMessageRef>
</ServiceDeliveryInfo>
<Answer>
<siri:EstimatedTimetableDelivery>
<siri:ResponseTimestamp>2017-01-01T12:00:00.000Z</siri:ResponseTimestamp>
<siri:RequestMessageRef>138852e0-8462-11ee-b013-bb5f2f680490</siri:RequestMessageRef>
<siri:Status>true</siri:Status>
<siri:EstimatedJourneyVersionFrame>
<siri:RecordedAtTime>2017-01-01T12:00:00.000Z</siri:RecordedAtTime>
<siri:EstimatedVehicleJourney>
<siri:LineRef>3</siri:LineRef>
<siri:DirectionRef>Aller</siri:DirectionRef>
<siri:OperatorRef>410</siri:OperatorRef>
<siri:DatedVehicleJourneyRef>201</siri:DatedVehicleJourneyRef>
<siri:DestinationRef>1</siri:DestinationRef>
<siri:RecordedCalls>
<siri:RecordedCall>
<siri:StopPointRef>24</siri:StopPointRef>
<siri:Order>4</siri:Order>
<siri:StopPointName>Stop Point 4</siri:StopPointName>
<siri:VehicleAtStop>false</siri:VehicleAtStop>
<siri:DestinationDisplay>Destination Sample</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:RecordedCall>
<siri:RecordedCalls>
<siri:EstimatedCalls>
<siri:EstimatedCall>
<siri:StopPointRef>25</siri:StopPointRef>
<siri:Order>5</siri:Order>
<siri:StopPointName>Stop Point 5</siri:StopPointName>
<siri:VehicleAtStop>false</siri:VehicleAtStop>
<siri:AimedArrivalTime>2017-01-01T15:05:00.000Z</siri:AimedArrivalTime>
<siri:ExpectedArrivalTime>2017-01-01T15:06:00.000Z</siri:ExpectedArrivalTime>
<siri:ArrivalStatus>Delayed</siri:ArrivalStatus>
</siri:EstimatedCall>
</siri:EstimatedCalls>
</siri:EstimatedVehicleJourney>
</siri:EstimatedJourneyVersionFrame>
</siri:EstimatedTimetableDelivery>
</Answer>
<AnswerExtension/>
</sw:GetEstimatedTimetableResponse>
</soap:Body>
</soap:Envelope>Improve Exchange references
Ara SaaS stores all real-time exchanges with better references (associated Stop Areas, Lines, Vehicles, Vehicle Journeys, Subscriptions) in many cases (StopPointsDiscovery, SIRI Stop Monitoring notifications with multiple subscriptions, etc).
Display expected Partner slug format
The user can see the description of the expected format for Partner Short Name (only contains a-z, 0-9, - or _):
Chouette Convert
Support GTFS file with subfolders
The user can now convert an invalid GTFS file which uses subfolders to organise GTFS content files:
Chouette Convert will ignore these subfolders and converts GTFS resources.
This kind of GTFS files is now officially invalid: https://github.com/google/transit/issues/377. You can use Chouette to create valid GTFS files.
Performance improvement
The Chouette Convert production platform has been improved to provide an higher performance level (up to 250k requests per hour, 6000 conversions created per hour).