Related to #22 and #4 and of possible interest to @tordans. Previously, the only built-in way to create a graph for the route-snapper was to use OpenStreetMap data, ignoring one-ways and using distance as the cost function. Now there's a second tool to turn a GeoJSON file with LineStrings and custom costs into a graph. A demo with custom costs that heavily penalize non-residential roads, causing the routes to zig-zag and avoid arterial roads in Seattle:
(Click to see video, GH isn't embedding webm)
clipped.webm
Related to #22 and #4 and of possible interest to @tordans. Previously, the only built-in way to create a graph for the route-snapper was to use OpenStreetMap data, ignoring one-ways and using distance as the cost function. Now there's a second tool to turn a GeoJSON file with LineStrings and custom costs into a graph. A demo with custom costs that heavily penalize non-residential roads, causing the routes to zig-zag and avoid arterial roads in Seattle:
(Click to see video, GH isn't embedding webm) clipped.webm