Introduction
Like all AVM solutions, Pysae requires the prior configuration of a transport plan. Theoretical offer data, such as :
stops
lines
routes
timetables
and schedules
are described in the transport plan.
The data structure in Pysae is largely based on the GTFS standard.
A transport plan is a global file containing all elements.
In Pysae, you can store, consult, edit, import, export and put a transport plan into production. The Editor tool, accessible via a web browser from the Op operating platform, facilitates these operations.
Important rules
Only one transport plan can be published at a time.
A published transport plan becomes immutable, and modifications are no longer possible. To make changes, duplicate the published transport plan.
A transport plan with errors cannot be published.
GTFS elements managed by Pysae
Description: Transit agencies with a service represented in the dataset.
Type : Mandatory
Field name
| Type | Format | Managed by Pysae |
agency_id | Mandatory (subject to conditions) | ID | YES |
agency_name | Mandatory | Text | YES |
agency_URL | Mandatory | URL | YES |
agency_timezone | Mandatory | Time zone | YES |
agency_lang | Optional | Language code | YES |
angency_phone | Optional | Phone number | YES |
agency_fare_url | Optional | URL | NO |
agency_email | Optional | E-mail adress | YES |
Description: Stops where users can get on and off. Also defines stations and their entrances.
Type : Mandatory
Field name | Type | Format | Managed by Pysae |
stop_id | Mandatory | ID | YES |
stop_code | Optional | Text | YES |
stop_name | Mandatory (subject to conditions) | Text | YES |
stop_desc | Optional | Text | YES |
stop_lat | Mandatory (subject to conditions) | Latitude | YES |
stop_lon | Mandatory (subject to conditions) | Longitude | YES |
zone_id | Mandatory subject to conditions) | ID | YES |
stop_url | Optional | URL | YES |
location_type | Optional | Listing | YES |
parent_station | Mandatory (subject to conditions) | ID | YES |
stop_timezone | Optional | Time zone | YES |
wheelchair_boarding | Optional | Listing | YES |
level_id | Optional | ID | NO |
platform_code | Optional | Text | NO |
Description: Public transport routes. A route is a set of journeys presented to users as belonging to the same service.
Type : Mandatory
Field name | Type | Format | Managed by Pysae |
route_id | Mandatory | ID | YES |
agency_id | Mandatory (subject to conditions) | ID | YES |
route_short_name | Mandatory (subject to conditions) | Text | YES |
route_long_name | Mandatory (subject to conditions) | Text | YES |
route_desc | Optional | Text | YES |
route_type | Mandatory | Listing | YES |
route_url | Optional | URL | YES |
route_color | Optional | Color | YES |
route_text_color | Optional | Color | YES |
route_sort_order | Optional | Number | NO |
continuous_pickup | Optional | Listing | NO |
continuous_drop_off | Optional | Listing | NO |
Description: Trips for each route. A trip is a series of at least two stops served at specific times.
Type : Mandatory
Field name | Type | Format | Managed by Pysae |
route_id | Mandatory | ID | YES |
service_id | Mandatory | ID | YES |
trip_id | Mandatory | ID | YES |
trip_headsign | Optional | Text | YES |
trip_short_name | Optional | Text | YES |
direction_id | Optional | Listing | YES |
block_id | Optional | ID | YES |
shape_id | Mandatory (subject to conditions) | ID | YES |
wheelchair_accessible | Optional | Listing | YES |
bikes_allowed | Optional | Listing | YES |
Description: Vehicle arrival and departure times from specific stops, for each route.
Type: Mandatory
Field name | Type | Format | Managed by Pysae |
trip_id | Mandatory | ID | YES |
arrival_time | Mandatory (subject to conditions) | Hour | YES |
departure_time | Mandatory (subject to conditions) | Hour | YES |
stop_id | Mandatory | ID | YES |
stop_sequence | Mandatory | Whole number | YES |
stop_headsign | Optional | Text | NO |
pickup_type | Optional | Listing | YES |
drop_off_type | Optional | Listing | YES |
continuous_pickup | Optional | Listing | NO |
continuous_drop_off | Optional | Listing | NO |
shape_dist_traveled | Optional | Floating number | YES |
timepoint | Optional | Listing | NO |
Description: Service dates indicated using a weekly schedule with start and end dates. This file is mandatory, unless all service dates are defined in calendar_dates.txt.
Type : Mandatory
Field name | Type | Format | Managed by Pysae |
service_id | Mandatory | ID | YES |
monday | Mandatory | Listing | YES |
tuesday | Mandatory | Listing | YES |
wednesday | Mandatory | Listing | YES |
thursday | Mandatory | Listing | YES |
friday | Mandatory | Listing | YES |
saturday | Mandatory | Listing | YES |
sunday | Mandatory | Listing | YES |
start_date | Mandatory | Date | YES |
end_date | Mandatory | Date | YES |
Description: Exceptions for services defined in calendar.txt. If calendar.txt is omitted, then calendar_dates.txt is mandatory and must contain all service dates.
Type: Mandatory (under conditions).
Field name | Type | Format | Managed by Pysae |
service_id | Mandatory | ID | YES |
date | Mandatory | Date | YES |
exception_type | Mandatory | Listing | YES |
Description: Cartographic rules for vehicle routes (sometimes called route alignments).
Type: Optional.
Field name | Type | Format | Managed by Pysae |
shape_id | Mandatory | ID | YES |
shape_pt_lat | Mandatory | Latitude | YES |
shape_pt_lon | Mandatory | Longitude | YES |
shape_pt_sequence | Mandatory | Whole number | YES |
shape_dist_traveled | Optional | Floating number | NO |
Quality control of the GTFS stream before import
Before importing your transport plan into Pysae, we strongly recommend that you check the quality of the GTFS file to avoid any complications such as alerts or missing information.
Remember: orange alerts do not prevent the transport plan from working, but it is advisable to resolve them. Red errors, on the other hand, prevent your plan from working properly.
To do this, you can use the Ministry of Transport's online tool.
1. Go to this link
2. Import your ZIP file containing your GTFS data.
This file can also be downloaded from your "Transport plan" interface in your Pysae operating area. Hover over the line corresponding to the plan in question and click on "download".
3. Run the analysis
4. Observe the results
"Warnings" are errors that must be corrected for your plan to be usable. "Information" represents items that need to be rectified to make your transportation plan work optimally.
Click on each category to discover the details of the items to be modified, which appear as a list below the interactive map.