Behind flexible services, structured data

A scheduled transport line is relatively simple to describe:

Identified stops 🚏
Precise schedules ⏰
A predefined route 🛤️

DRT (Demand-Responsive Transport), as we have seen, does not follow this logic.

It can operate:

By a set of served stop areas
With time slots for schedules,
With booking rules and conditions, 📝
With routes that are only truly defined at the time of booking.

For a DRT service to be known to travellers, it must be correctly consumed by passenger information systems 📲 and then it should appear:

In a trip planner
On open data
On regional or national passenger information systems
Etc.

For this, DRT services must be described in a structured manner. 📤

Visualize the offer with Chouette SaaS

This is precisely the advantage of using a tool like Chouette SaaS: allowing a DRT service to be described and visualized. 👀

In Chouette SaaS, it is possible to define and create each element of your DRT offer:

Flexible stop areas
Time slots for the trips
Booking conditions

Chouette_BookingRules

Completing and controlling the data is even more accessible with our user interface. 🖥️

And the challenge is not only to describe a DRT service, but to integrate it into the rest of the network or territory’s offer. 🔗

The success of a DRT service also depends on its ability to be disseminated and exploited in the various information flows, leveraging structure data that is of good quality and interoperable. ✨

With Chouette SaaS, it is possible to visualize and manipulate your DRT data, then publish it within your classic offer in standard GTFS and NeTEx formats.

They can thus be shared in third-party tools. 🌐