Skip to content
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

Open
BTollison opened this issue Nov 16, 2023 · 10 comments
Open

add Vehicles.txt #30

BTollison opened this issue Nov 16, 2023 · 10 comments

Comments

@BTollison
Copy link
Collaborator

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.

  • Required (Primary Key)

vehicle_long_name
For the purpose of describing a vehicle type in length

  • Example: Where vehicle_type_id could be 1234, a vehicle_description could say "Noord-Holland 10 meter VDL Citea Electric"

vehicle_short_name
For the purpose of briefly describing a vehicle.

  • Example: vehicle_type_id ias 1234, and vehicle_short_name is "H10e."

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.

  • Example: A manufacture states that your battery is 200kwh total, but that you may only use 80% of that value. Then you are left with 160.00.
  • Example 2: Your total battery capacity has degraded from 200kwh to 180kwh, but you are still only allowed to use 80%. Then your useable_kwh should be 144.00.
  • This is the primary field for any energy consumption calculation.

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.

  • Used to set a bottom threshold of acceptable battery charge level
@hodb
Copy link

hodb commented Nov 19, 2023

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

  • make
  • model
  • license_plate

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

@skyqrose
Copy link
Contributor

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

@BTollison
Copy link
Collaborator Author

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
Copy link

hodb commented Nov 21, 2023

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
Copy link
Collaborator Author

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
Copy link
Contributor

safrazier17 commented Dec 4, 2023

I propose:

  • Naming this vehicle_categories.txt as it covers substantially the same material as the file from the proposed GTFS vehicles extension. This also avoids the confusion that vehicles.txt sounds as though it were going to provide individual vehicle data for the fleet
  • Rename vehicle_type_id to vehicle_category_id
  • Adding vehicle_category_name and fuel_type from the same proposal

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
Copy link
Contributor

skyqrose commented Dec 4, 2023

Re: Fuel types:

  • What's the difference between 7 - Fuel Cell and 8 - Hydrogen?
  • Does there need to be a distinction between electric trolley buses that are capable of in motion charging via trolley poles, vs battery-only buses that need to sit at a charger?

@safrazier17
Copy link
Contributor

@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
Copy link
Collaborator Author

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
Copy link
Contributor

skyqrose commented Jul 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants