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.
I opened that box on a map with a magnifying glass icon, and uncovered five importers, three microservices, and hundreds of Node modules. I was in awe.
Pestering fruit with flashlights may not sound related to mapping, but when you work with mapping software for a while, everything starts to look like a map.
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.