All our SaaS products are about to be updated with the releases associated with this Sprint 135.
Chouette
Export Flexible Services with GTFS
Export Line Booking arrangement as GTFS Booking Rules
For each Booking Arrangement in Chouette, the GTFS export creates a GTFS Booking Rule.
The GTFS Booking Rule is created with the following information:
Booking Arrangement Attribute | GTFS Attribute | GTFS Value | Description |
|---|---|---|---|
Code | booking_rule_id |
| Identifies a rule. |
Book When
| booking_type | Time Of Travel Only: 0 Other value: no value | Indicates how far in advance booking can be made. Valid options are: 0 - Real time booking |
MinimumBookingPeriod (in minutes) | prior_notice_duration_min |
| Minimum number of minutes before travel to make the request. Conditionally Required:
|
Latest Booking Time | prior_notice_last_time |
| Last time on the last day before travel to make the booking request. Example: “Ride must be booked 1 day in advance before 5PM” will be encoded as prior_notice_last_time=17:00:00. Conditionally Required:
|
| prior_notice_last_day | 1 (if Latest Booking Time is defined) |
|
Booking Notes | message |
| Message to riders utilizing service at a stop_time when booking on-demand pickup and drop off. Meant to provide minimal information to be transmitted within a user interface about the action a rider must take in order to utilize the service. |
Contact / Phone Number | phone_number |
| Phone number to call to make the booking request. |
Contact / URL | info_url |
| URL providing information about the booking rule. |
Booking URL | booking_url |
| URL to an online interface or app where the booking request can be made. |
Export Stop Area Flexible Area as GTFS location groups
Each Flexible Stop Area (in the export scope) should be exported as a GTFS Location Group.
Export Flexible Vehicle Journeys with GTFS Flexible Stop Times
For each Vehicle Journey passing time associated to a Flexible Stop Point, Chouette exports a GTFS Stop Time with:
start_pickup_drop_off_window/end_pickup_drop_off_window with Vehcile Journey At Stop EarliestDepartureTime/LatestArrivalTime values
pickup_type/drop_off_type
with value 2 if the associated Stop Point ForBoarding/ForAligthing is Normal
else with value 1
location_group_id when the associated Stop Area is a flexible one
Imports have a new interface
Imports have a more complete and clearer interface featuring:
the detailed list of imported resources in GTFS or NeTEx, with status, number of test results, and a download link for each resource,
the list of macro runs, with status, name, start date, duration, and operator name,
the list of control lists, with status, name, start date, duration, and operator name.
Include or exclude tags from workbench processing rules
Processing rules in a workbench can be defined with required tags and excluded tags.
Only an operation with all the required tags and none of the excluded tags will be processed by this rule.
Export/Publish a selected group of lines
Users can now select one or several groups of lines to be included in an Export or a Publication.
Control sets: Create a Context by selecting a saved search
When users create a control set, they can create a context by selecting a saved search.
New GraphQL Retrieval Options
Retrieve line codes
The user can select codes in Line GraphQL model.
For example, the GraphQL query:
{ line(registrationNumber: "sample") { codes } }
would return:
{ "other": "third", "test": ["first","second"] }
Retrieve line referent
The user can select referent in Line GraphQL model.
For example, the GraphQL query:
{ line(registrationNumber: "sample") { referent { name, registrationNumber } } }
would return:
{ "referent": { "name": "Referent", "registrationNumber": "REFERENT" } }
Retrieve a Stoparea or a Line by code
The user can retrieve a StopArea or a Line by code in GraphQL API:
{ stopArea(code: { value: "TEST", code_space: "test" }) { name, codes } } { line(code: { value: "TEST", code_space: "test" }) { name, codes } }
Retrieve model documents
The user can retrieve the documents associated to a Line and Stop Area model in a GraphQL query. The following attributes can be retrieve for each document:
uuid
name
documentType
description
validityPeriod
codes
createdAt
updatedAt
The user can also retrieve the metadatas of all documents for all lines.