Open BTollison opened 9 months ago
I wonder if this could be folded into #34, as a new type of location. There'd either need to be a way to put the max_kw/times into that file, or this file would still need to be separate (but referencing a child_location that represents this charger).
Why represent one charger with multiple stations, as opposed to many individual chargers? (I'm not familiar with electric vehicle operation, so I don't know how chargers are used or how this data would be used.)
At the planning / scheduling level, it becomes almost unmanageable to map every charging event to an individual charger, so it is preferred instead to group them. This reduces computation time but also allows for the day-to-day "what charger should I go to?" question to be offloaded to operations.
This is not to say that there aren't scenarios where we do map each charger.. but it's absolutely against best practices.
Does that make sense?
I understand the use case as many bus fleets transition to BEBs and can likewise see this being used for trains, but may I suggest we generalize this as power_stations.txt
to support additional fueling use cases?
i.e.
Add field power_type
Rename field number_of_chargers
to number_of_power_stands
or number_of_power_stations
Rename field max_kw
to max_output
power_type
= enum 1 (battery), gallons for power_type
= enum 2 (Diesel), etc.
This proposal seeks to provide a file describing the electric vehicle chargeing infrastructure within a network.
ops_location_id
stop_id
max_kw
number_of_chargers
start_time
end_time