Sprint 117
All our products have been updated with the releases associated to this Sprint 117
Ara has been updated on Oct 16, 2024
Chouette has been updated on Oct 21, 2024
- 1 Chouette
- 1.1 Search Vehicle Journeys by "code"
- 1.2 Ignore Referent Stop Areas in NeTEx export
- 1.3 Import all standard GTFS Route Types
- 1.4 Improve large NeTEx Publications via a cache
- 1.5 Search Line Notices with new interface
- 1.6 New syntax for Chouette CLI
- 1.7 Create Documents with Chouette CLI
- 1.8 End of Life: Vehicle Journey ignored Routing Constraints
- 2 Ara
Chouette
Search Vehicle Journeys by "code"
When the user searches Vehicle Journeys by text, the result includes any Vehicle Journey which matches (even partially):
by Published Name
by Published Identifier
by Chouette internal identifier
by code with code space external
If the used syntax is the <code_space>:<value>
, the search is performed on codes of the specified code space and the given partial value.
Ignore Referent Stop Areas in NeTEx export
The user can select the option “Ignore Referent Stop Areas” for an NeTEx Export/Publication. In this case, referent Stop Areas won’t be present into the exported file.
Without this option:
<Quay id="PARTICULAR" created="2024-10-18T06:49:17Z" changed="2024-10-18T06:49:29Z" version="any" derivedFromObjectRef="REFERENT">
<Name>North Ave / D Ave N (Demo)</Name>
<PrivateCode>NADAV</PrivateCode>
<Centroid version="any">
<Location>
<Longitude>-116.76821</Longitude>
<Latitude>36.914893</Latitude>
</Location>
</Centroid>
</Quay>
<Quay id="REFERENT" created="2024-10-18T06:49:24Z" changed="2024-10-18T06:49:24Z" version="any">
<Name>Referent</Name>
<PrivateCode>REFERENT</PrivateCode>
</Quay>
With this option:
<Quay id="PARTICULAR" created="2024-10-18T06:49:17Z" changed="2024-10-18T06:49:29Z" version="any">
<Name>North Ave / D Ave N (Demo)</Name>
<PrivateCode>NADAV</PrivateCode>
<Centroid version="any">
<Location>
<Longitude>-116.76821</Longitude>
<Latitude>36.914893</Latitude>
</Location>
</Centroid>
</Quay>
Import all standard GTFS Route Types
When the user imports a GTFS file, Chouette manages all standard GTFS Route Types:
GTFS Route | Chouette Transport Mode |
---|---|
0 | Tramway |
1 | Metro |
2 | Rail |
3 | Bus |
4 | Water |
5 | Funicalr / Street Cable Car |
6 | Telecabin |
7 | Funicular |
11 | TrolleyBus |
12 | Rail / Monorail |
Improve large NeTEx Publications via a cache
The user can use the Publication option “Optimise with a cache”. With this option, a Publication export can reuse the Service Journey XML payload exported for a Chouette Vehicle Journey in the last 30 days.
On very large NeTEx Publication, the performance impact is very important. A Dataset containing 500 000 Vehicle Journeys which is exported by 9 GB of XML can be performed in less than 20 minutes.
This feature is experimental for the moment. Please use it for test purpose.
Search Line Notices with new interface
The user can use the new search interface to find Line Notice:
New syntax for Chouette CLI
The user can create an Import via the new syntax:
chouette-client create import --name=Test /path/to/file
The user can create a batch of imports with this new syntax:
Create Documents with Chouette CLI
The user can create Documents by using the https://bitbucket.org/enroute-mobi/chouette-client/ command line client:
A new guide is available (in French) to describe documents import and code management: https://enroute.atlassian.net/wiki/spaces/PUBLIC/pages/2524676099/Import+et+association+automatique+des+documents#Import.
End of Life: Vehicle Journey ignored Routing Constraints
The user can no longer selects ignored Routing Constraint Zones for a given Vehicle Journey.
Ara
Display and edit Situation Affects with All lines
The user can edit a Situation and define the Affected Lines as “All Lines”:
In this case, the Line selection is disabled.
This kind of affects can collect and broadcasted in SIRI Situation Exchange: https://enroute.atlassian.net/wiki/spaces/PUBLIC/pages/2534014977/Sprint+116#Collect-%26-Broadcast-Situation-with-AllLines-affect
Collect & Broadcast Situation InfoLinks in SIRI Situation Exchange
Ara can collect and broadcast via SIRI Situation Exchange Situations with one or several InfoLink(s).
Each InfoLink is defined with:
an
Uri
(mandatory)a translated string
Label
(optional)an Image uri (optional)
Display & Edit Situation InfoLinks
The user can see InfoLinks associated to a Situation:
the InfoLink URI is a clickable link
the Label is displayed if present
the Image link (when present) is clickable via a small icon
When a Situation is created, the user can define an InfoLink:
All attributes are optional. If no URI is specified, no InfoLink is defined.
Broadcast SIRI Vehicle Monitoring when a Referent Line is requested
When the user requests the SIRI Vehicle Monitoring connectors with a Referent Line, all the Vehicles associated to the Referent Line and its particular Lines are included into the response.
Both the SIRI Vehicle Monitoring Request Broadcaster and SIRI Lite Vehicle Monitoring Request Broadcaster include this mechanism.