Posts tagged: routing
A "data-driven" approach to improving map-matching: Part IV — Map-Matching and the Built Environment
The final part of a series on how Mapzen validates, fine tunes, and deploys our map-matching, in support of the Open Traffic platform and other applications.
In part three of how Mapzen validates, fine tunes, and deploys our map-matching, we'll describe how we ensure that only the best-quality matches make their way into the Open Traffic datastore.
In part two of how Mapzen validates, fine tunes, and deploys our map-matching, we'll dive a bit deeper into the internals of the algorithm itself to see how we can use our validation metrics to fine-tune the map-matching parameters.
This summer, we have enhanced bicycle costing. Not only is overall routing improved, but `use_roads'` and `use_hills` are now much more versatile.
We wanted to take some time to explain exactly how map matching works, and how we use it. This will be the first in a series of three blog posts on how Mapzen validates, fine tunes, and deploys our map-matching services to meet the needs of our users.
We're excited to release Mapzen Map Matching, the latest addition to the Mapzen Mobility services. Our Map Matching service takes in a trajectory of latitude/longitude coordinates and returns back a route line that is snapped to the OpenStreetMap road network and enriched with attributes, like speed limits and freeway exit signs.