Open doconnoronca opened 4 months ago
I reviewed the GTFS-Vehicles proposal. I added a few things inspired by that. My proposal is close to what @mgilligan and @botanize suggested.
This is a much simpler. It just has a list of vehicles and describes them. I have suggested one row per vehicle. The largest agencies would have thousands of rows, which isn't a lot these days, but I would be open to having ranges of Ids and Labels instead.
It does not add vehicle_category_id, to routes.txt or trips.txt because it is dependant on the real time data to provide the vehicle label. I addition to GTFS real-time, other real time formats like the BusTime and NextBus (Umo) API, also provide the vehicle number. I would be open to a feature so the that an expected vehicle class could be added to routes or trips, for systems that do not support real time data.
Hi, I like this approach. Will there be any discussion about parameters included in vehicles.txt?
In Prague we would like to have there also:
@met then include regular wall outlets too...
I have added AirConditioned, AC_Plugs and USB_Plugs to the proposal. Is it too soon to add USB type-C plugs.
I have added the ability to have ranges for the id and label (which will make is easier to include before GTFS generators support this), note fields for text description of different features, WiFi information, next stop announcements and displays and special decoration fields to indicate vehicles seasonal wraps, like Pride or Christmas buses.
vehicle_type
being redundant of route_type
doesn't make sense to me. I'd want more detail, like at least at the level provided to NTD and used in transit asset management.
Sometimes instead of year manufactured, you want to know the general quality of the vehicle: is it falling apart and scary (likely in some places) or pristine. The TERM scale used by BTS could be a useful here:
The APTA Vehicle Inventory DB might also be useful for standardizing some attributes around. For example, there are some useful attributes like "wifi available" and there are a lot more fuel types:
@e-lo The new version I've been working on used the Vehicle Type and Fuel Type from the National Transit Database. I could add the TERM scale, if agencies where willing to publicize it.
Is fare depending on the vehicle currently supported in GTFS? For example, the fare for a bus route is higher if it is an air conditioned bus.
Describe the problem
Real time prediction tools could use additional information to describe what type of vehicle is approaching and its capacity and accessibility features.
Use cases
Real-time data usually includes the vehicle number which could be used to look up more details about the vehicle then it would be practical to include with the real-time data feed. Capacity would be used to indicate how busy a vehicle is if the real-time passenger load is provided. The vehicle type would be useful to indicate when a rail vehicle has been replaced by a bus.
This could also be used for reporting fleet information in a standard format for analyses by other levels of government and the public.
Proposed solution
A new vehicles.txt file in the GTFS static file to describe the capacity, accessibility and features of individual vehicles or vehicle ranges. It would apply to buses, LRT, subway cars, rail cars and even ferries.
Fields could include:
Additional information
No response