Kevin Kreiser

ok, as i surmised it was just a precision issue with boost... so they have a function `boost::geometry::wkt` and im not sure what rules it has built in but without...

if i had to bet, i would say that most folks are likley on forks that are significantly diverged from public master. this means that if they are taking functionality...

why would that bother python bindings? i should educate myself on the build system over there i guess? i thought it would be find with pybind

there are many embedded systems where that wont be an option. eg, inside car dashboards on special hardware, or on android or on ios. those types of embedded (read: non-server)...

also merry christmas everyone :smile:

there should be attributes in the response that will tell you that there is a "discontinuity" between the pieces, they arent meant to jump through the woods where there is...

see here for more info on discontinuity attributes: https://github.com/valhalla/valhalla/blob/master/docs/docs/api/map-matching/api-reference.md#matched-point-items

> and I may have huge (few kilometers) gaps set your `breakage_distance` in the valhalla.json config to be larger than your largest expected gap

we'll need to see the osm data near where you are to talk intelligently about the "cutting" part of the route. you are right cars cant take bike/ped paths. try...

> I tried adding "radius": 150 in each shape objects but it didn't impact the result for this particular request. there is a cap on the radius also set in...