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
As we've discussed, the package need not be restricted to OSM data alone, and can and hopefully will be used for any kind of graph data. I'd suggest this pretty much demands a new name that jettisons the OSM connotation and that also immediately indicates that it's a routing algorithm.
The text was updated successfully, but these errors were encountered:
That is true. Still, I'd definitely like to keep the osmdata functionality somewhere in the package, because I like the idea of just passing a bounding box and having the package take care of all the data acquisition/preprocessing stuff.
As for name, no idea right now. But to throw in a couple of words that come to mind: traffic flow, movement, vague.
As we've discussed, the package need not be restricted to OSM data alone, and can and hopefully will be used for any kind of graph data. I'd suggest this pretty much demands a new name that jettisons the OSM connotation and that also immediately indicates that it's a routing algorithm.
The text was updated successfully, but these errors were encountered: