You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HIVE should be able to support turn and signal costs of the form Edge => Edge => (0, infinity] to describe turn penalties and signal delays.
our primary network data source, OSM, already stores some data on this. in order to design a solution for HIVE, we need to review how OSM stores this data and if/how osmnx retrieves it. this impacts our conventional network download script (should be ported to github.com/nrel/hive/) but also our path search function which needs to incorporate the Edge => Edge => Cost lookup. if networkx does not expose a shortest path variant with this scope, we may need to roll our own or look for alternatives.
a solution that matches our OSM inputs needs to be checked against the requirement of working with our internal speeds data as well.
this task is to come up with a design and to produce an issue describing the implementation.
The text was updated successfully, but these errors were encountered:
HIVE should be able to support turn and signal costs of the form
Edge => Edge => (0, infinity]
to describe turn penalties and signal delays.our primary network data source, OSM, already stores some data on this. in order to design a solution for HIVE, we need to review how OSM stores this data and if/how osmnx retrieves it. this impacts our conventional network download script (should be ported to github.com/nrel/hive/) but also our path search function which needs to incorporate the
Edge => Edge => Cost
lookup. if networkx does not expose a shortest path variant with this scope, we may need to roll our own or look for alternatives.a solution that matches our OSM inputs needs to be checked against the requirement of working with our internal speeds data as well.
this task is to come up with a design and to produce an issue describing the implementation.
The text was updated successfully, but these errors were encountered: