Addition of vehicles.txt to GTFS static about transit HOT 6 OPEN

@met then include regular wall outlets too...

from transit.

I have added AirConditioned, AC_Plugs and USB_Plugs to the proposal. Is it too soon to add USB type-C plugs.

from transit.

Related : #200

from transit.

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.

from transit.

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:

• boolean property airConditioned (if the vehicle is airconditioned - it is being very impotant in Summer months) and
• boolean property usbChargers (if the vehicle contains USB charges for passengers).

from transit.

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.

from transit.