Sprint 137

Sprint 137

Chouette

Ara Export/Publication for Vehicle Journey Stop Visit count

When Chouette exports a Vehicle Journey, the number of associated stops (aka Vehicle Journey At Stops) is added to the Ara::File::VehicleJourney as aimed_stop_visit_count.

 

Ara Export/Publication for StopArea Groups and Line Groups

Ara Export/Publication exports only StopArea groups and Line groups that have a short_name. For information, short_name is mandatory for Ara but not inside Chouette.

 

Ara Export/Publication should include all Stop Area Groups in Ara export

Ara Export/Publication now includes all Stop Area Groups because they are used in Ara to collect external Stop Areas.

 

Gtfs and NeTEx Export/Publication for Booking Arrangements

In the NeTEx or GTFS export, a BookingArrangement is now exported only when it’s linked to the dataset.

Updated import layout

The user can see the code space used to perform the import, and import options are displayed into a dedicated options block.

Chouette-sample-feed-2030.png

Custom ICAR API publication destination

A user can now manually set the ICAR API publication destination if their organisation has the feature.

Chouette-Ajouter-une-Publication-Automatique.png

 

Ara

Visualise real-time VehicleJourneys and Vehicles

VehiclesJourneys and Vehicles can be displayed on the user interface. The user can have acess to the details of each types.

Example for VehicleJourneys:

image-20251216-121813.png

The details of a VehicleJourney:

image-20251216-121831.png

 

Limit Stop Monitoring subscriptions per request

Ara can limit the number of StopmonitoringSubscriptionRequest per subscription request using the setting collect.siri.stop_monitoring.maximum_subscriptions_per_request

refer to Ara Partner Parameters for more details.

 

Remove default onTime for Arrival & Departure status

When Ara receives a SIRI StopMonitoring, if the ArrivalStatus or DepartureStatus is not provided in the SIRI xml, then Ara will not consider that the StopVisit is onTime anymore.

 

Flamingo

Initialize IDFM NeTEx ruleset

A ruleset has been created to check IDFM rules.

An excerpt is available below :

[ { "rule_context": "resource/kind_of", "resource_classes": ["CompositeFrame"], "rules": [ { "rule_context": "attribute/match", "name": "id", "value": "FR1:CompositeFrame:NETEX_FRANCE-[A-Z,0-9]*:LOC/", "rules": [ { "rule": "resource/mandatory" }, { "rule": "attribute/value", "name": "type_of_frame", "value": "FR1:TypeOfFrame:NETEX_FRANCE:", "criticity": "error", "code": "commun_frame_france", "message": "Le fichier doit respecter l'organisation en Frames défini par le profil IDFM." }, { "rule": "tag/match", "name": "filename", "value": "commun.xml", "criticity": "error", "code": "commun_nomfichier", "message": "Le fichier doit porter le nom de 'commun'." } ] } ] }, { "rule_context": "resource/kind_of", "resource_classes": ["GeneralFrame"], "rules": [ { "rule_context": "attribute/match", "name": "id", "value": "/FR1:GeneralFrame:NETEX_COMMUN-[A-Z,0-9]*:LOC/", "rules": [ { "rule": "resource/mandatory" }, { "rule": "attribute/value", "name": "type_of_frame", "value": "FR1:TypeOfFrame:NETEX_COMMUN:", "criticity": "error", "code": "commun_frame_commun", "message": "Le fichier doit respecter l'organisation en Frames défini par le profil IDFM." }, { "rule": "tag/match", "name": "filename", "value": "commun.xml", "criticity": "error", "code": "commun_nomfichier", "message": "Le fichier doit porter le nom de 'commun'." } ] } ] },

 

Documentation

Tags

 

Imports

  • Updated all screenshots for import pages

 

Lignes

Add NeTEx description of each flexible line type :