cal-itp / operational-data-standard

The Transit Operational Data Standard is an open standard for representing the transit schedules used by drivers, dispatchers, and planners to carry out transit operations.
https://ods.calitp.org
Apache License 2.0
28 stars 6 forks source link

add Vehicles.txt #30

Open BTollison opened 12 months ago

BTollison commented 12 months ago

In an effort to make ODS more compatible with electric fleets, I am proposing the following addition of Vehicles.txt

Vehicle_type_id Used to identify a specific vehicle type within a fleet.

vehicle_long_name For the purpose of describing a vehicle type in length

vehicle_short_name For the purpose of briefly describing a vehicle.

useable_kwh Described the amount of useable battery capacity. This should not be the total capacity of the battery as stated by a manufacture, but rather the total allowed consumable and rechargeable kwh. This is a decimal value.

total_kwh This represents the full size of the battery as decimal value. It should change over time as batteries degrade.

charge_curve_id Reference to the proposed charge_curves.txt. Connects the appropriate charging curve to the vehicle_type_id.

min_kwh Minimum kwh allowed to remain in the battery while the vehicle is in operation.

hodb commented 12 months ago

Adding to the vehicles.txt file concept, additional attributes that relate to the vehicle itself (non-EV related) such as -

These attributes can assist in maintaining fleet information to be consumed by the AVL provider

skyqrose commented 12 months ago

Which of these fields would be used to match what's in VehicleDescriptor in GTFS-RT?

BTollison commented 12 months ago

The intention of this is actually not to be a database of individual vehicles, but of groups of vehicle types so that up and downstream systems have the information necessary to understand the EV context. I admit the "vehicles.txt" name is a bit misleading in this way.

hodb commented 11 months ago

It could be it can be separated into two separated files, connected by a foreign key. My intention was to have communication between the dispatching software and the AVL provider regarding what vehicles are being operated

BTollison commented 11 months ago

For sure my intention is that in the future I would like a real-time component of ODS to be created that would expand on GTFS-RT. Right now this proposal though is focused on EV's (and some more proposals to come).

safrazier17 commented 11 months ago

I propose:

Edit: the fuel_type field was proposed as an enum with the following values

0 or empty - Unknown 1 - Gasoline 2 - Diesel 3 - Natural gas 4 - Diesel-electric hybrid 5 - Natural gas hybrid 6 - Battery electric 7 - Fuel cell 8 - Hydrogen

skyqrose commented 11 months ago

Re: Fuel types:

safrazier17 commented 11 months ago

@skyqrose I think there are non-hydrogen fuel cells that could be represented there, although they are certainly a minority... and for our purposes, there may be no particular advantage to separating (8) hydrogen out from (7) fuel cell. I'd be fine with dropping it

BTollison commented 11 months ago

We think it would be good to add trolley bus, but we consider trolley bus with a battery to be just an electric bus that can charge while driving. So we don't feel an addition of this is necessary.

skyqrose commented 3 months ago

I know this proposal is mostly about battery buses rather than trains, but if representing trains in this file, will this file list the types of cars or the types of trainsets.