Sprint 131
- 1 Chouette
- 1.1 Manage codes on Networks
- 1.2 Prefer Documents of Referent models in Publication API
- 1.3 Export GTFS Stop Time with stop sequence from 1
- 1.4 Specify file type when creating an Import with chouette-client
- 1.5 Add BookingArrangement model to Create code macros
- 1.6 Define Referent Stop Area transport mode from particulars
- 1.7 Accept NeTEx files with non-xml entries
- 1.8 Documentation
- 2 Ara
All our SaaS products have been updated with the releases associated with this Sprint 131.
Chouette
Manage codes on Networks
The user can associate codes with a Network:
The user can import/export a Network via a NeTex import using alternate identifiers:
<Network id="sample">
<keyList>
<KeyValue typeOfKey="ALTERNATE_IDENTIFIER">
<Key>test</Key>
<Value>other</Value>
</KeyValue>
</keyList>
<Name>Network Sample</Name>
</Network>Prefer Documents of Referent models in Publication API
When the user enables the option “Prefer Referent Documents” in the Pubilcation API, a document request should try to find first a Referent model with the given code.
If a such Referent model exists, the associated Documents are used to select the returned Document.
Export GTFS Stop Time with stop sequence from 1
When the user selects the option “Use Stop Sequence from 1” in a GTFS export, the exported GTFS file should contain GTFS Stop Time using a stop sequence from 1 (instead of 0).
The GTFS format only expect non-negative integer. A GTFS consumer should support GTFS Stop Time stop sequence with zero value.
Specify file type when creating an Import with chouette-client
The user can create a Chouette Import via Chouette CLI client with a specifc file type:
chouette-client -name "Stop Area addresses" -file-type netex sample.xmlThe new (optionnal) option allows to import a NeTEx XML file in a script for example.
Add BookingArrangement model to Create code macros
The user can create codes on the new BookingArrangement model to improve flexible data:
See the Managing Codes with Chouette Guide for more details.
Define Referent Stop Area transport mode from particulars
The user can use the macro “Define Attribute from Particulars” to define Referent Stop Area transport mode.
Accept NeTEx files with non-xml entries
The user can import a NeTEx Zip file which contains non-XML entries. The non-XML entries are ignored.
Chouette previously rejected this kind of NeTEx file (for security reasons) but many NeTEx producers include non-XML entries in their archive.
Documentation
The Chouette SaaS documentation has been improved, especially these topics:
New Type Macros: https://enroute.atlassian.net/wiki/spaces/PUBLIC/pages/2011922433/Macro+lists#Type-of-Macros
https://enroute.atlassian.net/wiki/spaces/PUBLIC/pages/2991259651
Ara
Manage static HTTP header(s) used in requests
The user can define in the Partner HTTP headers that will be included in every HTTP request associated to this Partner (both SIRI and GTFS-RT).
The associated setting should be http.custom_headers , and the value should have the form key=value separated by a comma. For example:
Producer=acmee,SecondHeader=value The user doesn’t need to use this feature to secure SIRI requests performed by Ara. Ara already uses an HTTP X-Siri-Requestor with Partner remote credential. See https://github.com/etalab/transport-profil-siri-fr/issues/25 for more details.
Historize GraphQL exchanges
When the user performs requests on GraphQL connector, these exchanges are stored into an Event with “GraphQL Request” type. The request and response bodies are stored.
Facility Support
This Ara release includes the first steps of Facility Support features.
Facilities are are pieces of equipment at a station, stop or vehicle, for example: elevators, escalators, information desks, bike parkings.
SIRI FacilityMonitoring allows users to monitor the status of these pieces of equipments: available, not available, etc …
Collect Facility through SIRI FacilityMonitoring Request
The user can collect Facility information with a SIRI FacilityMonitoring Request by using the associated Connector into the dedicated Partner:
For example, the user can use this connector to request a simple SIRI endpoint. See https://enroute.atlassian.net/wiki/spaces/PUBLIC/pages/2641854465/Collect+via+Pseudo+SIRI#Facility-Monitoring for more details.
Broadcast Facility through SIRI FacilityMonitoring Request
The user can broadcast Facility information by using SIRI FacilityMonitoring Request by using the associated Connector into the dedicated Partner.
The SIRI FacilityMonitoring Subscription support will be available in a future release.
Import Facility from CSV
The user can import Facility models by using Ara File Format.
Support SIRI “raw” Discovery Request broadcaster
The user can use StopPointsDiscovery and LinesDiscovery SIRI Request Broadcasters with the SIRI envelope “raw”: