-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add Vehicles.txt #30
Comments
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 |
Which of these fields would be used to match what's in VehicleDescriptor in GTFS-RT? |
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. |
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 |
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). |
I propose:
Edit: the 0 or empty - Unknown |
Re: Fuel types:
|
@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 |
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. |
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. |
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.
The text was updated successfully, but these errors were encountered: