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
Based on my interpretation, this matcher handles GPS traces and matches (via routing) them to OSM references. I can extrapolate logic and guess at how the same algo could be used to match traffic counts (e.g. 10,298 annual average daily traffic), which are attributed to links on a city-maintained GIS road network, to OSM-based SharedStreets reference IDs.
I am considering forking this repo to attempt to handle this case. We have a real-world set of data to work with from the MPO in Philadephia and modeled traffic volumes in the same area from CityCast (see also this blog), which can run with either an OSM network or a HERE network.
What do you think of this? Am I missing something from the get-go? Is there a better place to try to implement this kind of matching?
The text was updated successfully, but these errors were encountered:
Based on my interpretation, this matcher handles GPS traces and matches (via routing) them to OSM references. I can extrapolate logic and guess at how the same algo could be used to match traffic counts (e.g. 10,298 annual average daily traffic), which are attributed to links on a city-maintained GIS road network, to OSM-based SharedStreets reference IDs.
I am considering forking this repo to attempt to handle this case. We have a real-world set of data to work with from the MPO in Philadephia and modeled traffic volumes in the same area from CityCast (see also this blog), which can run with either an OSM network or a HERE network.
What do you think of this? Am I missing something from the get-go? Is there a better place to try to implement this kind of matching?
The text was updated successfully, but these errors were encountered: