Skip to main content
All Collections📌 Transport plan editorGeneral operation
Error and alert management
Error and alert management
A
Written by Antoine Marin
Updated over a week ago

Introduction

The proper functioning of an AEIV type solution requires an accurate database.

The aim is to prevent the theoretical transport offer from containing inconsistent data that could lead to :

  • Giving wrong driving instructions to drivers;

  • Providing incorrect alerts and indicators;

  • Disseminate the wrong information to passengers;

  • Create malfunctions in the Pysae system.

In response, your Pysae platform's transport plan editing interface includes a data verification module. Around fifty consistency rules are automatically checked during your imports, and the verification module provides you with two types of feedback:

  • Errors: these prevent the system from working properly and your transport plan from being published.

  • Alerts: these do not prevent your plan from being published, but they do slow down the system. They are designed to improve the quality of data distribution.

A number of the rules verified by Pysae are based on the recommendations of the GTFS standard (to find out more, click here).

Errors

Plan components

Error list

Agency

  • Required fields missing (agency_name)

  • Missing required fields (agency_url)

  • Missing required fields (agency_timezone)

  • Invalid field format (agency_url)

  • Invalid field format (agency_timezone)

Stop

  • Invalid field format (stipulat)

  • Invalid field format (stop_lon)

  • Invalid field format (date)

  • Required fields missing (stop_lat)

  • Missing required fields (stop_lon)

  • Missing required fields (stop_name)

Line

  • Required fields missing (route_id)

  • Missing required fields (route_short_name)

  • Required fields missing (route_type)

Trip

  • Invalid reference (service_id)

  • Invalid reference (stop_id)

  • Missing required fields (service_id)

  • Required fields missing (route_id)

  • Invalid format (arrival_time & departure_time)

  • Arrival time descending

Calendar

  • Missing required field (day of week)

  • Missing required field (start_date)

  • Missing required field (end_date)

  • Missing required field (service_id)

  • Invalid field format (date)

  • Invalid date order

Calendar_dates

  • Missing required field (date)

  • Missing required field (service_id)

  • Missing required field (exception_type)

  • Invalid field format (date)

As long as the transport plan contains at least one of these errors, you will be unable to publish it.

Alerts

Plan components

Error list

Agency

  • Stop not in use

  • Station not used

  • Invalid stop coordinates

Line

  • Line not used

  • Short line name too long (more than 6 characters)

Trips

  • Theoretical distance missing

  • Invalid reference (shape_id)

  • Equal consecutive times

Tracks

  • Route not used

  • No distance

Calendar

  • Unused calendar

View errors and alerts

You can consult the list of errors and alerts in your transportation plan by accessing its view. (Please refer to the article "Guided tour of the transportation plan editor" and then to the section "Accessing your "Transportation plan editor" to find out how to do this)

Once your transport plan view is open, you can view errors and alerts:

  • From the "Home" tab, opposite each component;

  • From the "Verification" tab, at the bottom of the left-hand side menu.

A red icon represents an error, an orange icon represents an alert.

From the "Verification" view, alerts and errors are grouped by :

  • Transport plan components concerned (stop, line, etc.) ;

  • Type of error or alert

By clicking on the type of error or alert, you can display a detailed list of the transport plan components concerned.

Did this answer your question?