The user can export without period limit a given dataset. In this case, the exported file will include any vehicle journey with a not empty timetable.
With this option, the user can export data associated with past timetables.
Export only a subset of lines
The user can export from a given dataset only scheduled data associated to a subset of lines. In this case, the exported file will include only vehicle journeys associated to one of the selected lines (and obviously all required resources like timetables, stop places, etc).
The user can select lines by either:
a predefined line set
a company set: selected lines are lines associated to the given companies
a line provider set: selected lines are lines associated to the given line providers
By default, the export will include all available lines in the dataset.
Publish via new export options
The user can use the export options to publish:
without time duration
by including a subset of lines
When your Workgroup dataset contains neighboring / complementary data (like the local rails / bus provider lines), you can publish only our company lines.
You can use several Publications to provide several subsets of our Workgroup dataset: scholar lines, local airport transports, sub area lines, etc
Publish per line
The user can choose to publish a dataset with “a file” for each line.
In this case, for each line, an export is performed with the given options (format, etc). Each exported file contains only the required data (stop places, etc) to describe the line services.
All resulted files are managed automatically by the Publication. Each created file is managed by each destination defined in the publication. In the Publication API, each file can be retrieve with a dedicated URL.
When you’re administrating a Workgroup which publish a very large dataset (several hundred of lines), the Publication by line provides a smart way for consumers who only require few lines to process small datasets.
Export flexible lines in GTFS
When the user defines a Line as "On demand transportation, the GTFS export uses the GTFS pick type 2 - Must phone agency to arrange pickup for all associated Vehicle Journeys.
GTFS import improvements
When the user defines the agency_phone GTFS agency attribute, the Line default contact phone number is defined / updated.
When the user defines GTFS route colors by using low case value (like abcdef), the Line colors are defined / updated as expected (with upcase color values),
Collect only discovered Stop Areas
When the user uses a collector which allows to discover Stop Areas (like the SIRI Stop Points Discovery collector), the setting collect.use_discovered_stop_areas can be used to setup this Partner to only collect the discovered Stop Areas. All other Stop Area collect requests will be ignored by this Partner.
Other collect options like priority or include / exclude filters can be used with this setting to tune the collect logic.
When you’re collecting several systems (like a bus SIRI server and a tram SIRI server) in the same Ara referential, this option will automatically setup our Partners to collect the correct Stop Areas.
Select an alternative code space to broadcast GTFS-RT Vehicle Positions
When the user broadcasts Ara realtime data with a given code space (objectid kind) which isn’t available on Vehicles, the setting is gtfs-rt-vehicle-positions-broadcaster.vehicle_remote_objectid_kind can be used to use an alterne code space.
On this case, the GTFS-RT vehicle will use this code associated of the specific cope space while Line or Vehicle Journey identifiers still use the Partner’s default code space.
A Partner with:
a remote_objectid_kind public
a gtfs-rt-vehicle-positions-broadcaster.vehicle_remote_objectid_kind internal
will broadcast the Vehicle as a GTFS vehicle with: