Re: [Talk-us] cycle.travel US bike routing, and unreviewed rural TIGER
Harald Kliems wrote: > Until then you could consider a user setting to avoid/not avoid > unpaved roads. Unfortunately contraction hierarchies - the routing algorithm used by OSRM - don't really allow user settings. For each distinct routing profile, you need to regenerate the routing graph, which takes (many) hours and requires (many) GB of RAM both to route and to host. cycle.travel penalises surface types variably: surface=mud gets a big penalty, surface=gravel not so much. cheers Richard -- View this message in context: http://gis.19327.n5.nabble.com/cycle-travel-US-bike-routing-and-unreviewed-rural-TIGER-tp5848084p5848600.html Sent from the USA mailing list archive at Nabble.com. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] cycle.travel US bike routing, and unreviewed rural TIGER
Richard, I would somewhat caution against penalizing unpaved roads too much. In many areas of the US they actually make wonderful cycling routes, whereas the paved alternatives are high traffic and unpleasant to ride on. Of course, proper smoothness tagging would help but that will be a long way coming. Until then you could consider a user setting to avoid/not avoid unpaved roads. Harald. On Fri, Jun 19, 2015 at 2:48 PM Richard Fairhurst wrote: > Just as a postscript to this discussion I thought I'd cite an example area. > If you look here, in Georgia: > >http://cycle.travel/map?lat=31.9023&lon=-84.0398&zoom=14 > > you'll see that most of the roads are unreviewed TIGER residentials. Of > those, these are adjacent to each other: > > http://www.openstreetmap.org/way/9359782 - good tarmac, should be > highway=tertiary > http://www.openstreetmap.org/way/9359913 - unpaved road; > highway=unclassified, surface=unpaved > http://www.openstreetmap.org/way/9359784 - probably tertiary, but lousy > geometry at the S > http://www.openstreetmap.org/way/9359783 - whoops, where did the > connectivity go? > > All of this is trivially fixable but right now there's no way of using them > for routing or sensible cartography. Do dive in - the cycle.travel > rendering > makes it obvious which bits need fixing, and you learn to identify the > roads > which are likely to be paved through roads and therefore targets to fix. > It's quite good fun. :) > > cheers > Richard > > > > > > -- > View this message in context: > http://gis.19327.n5.nabble.com/cycle-travel-US-bike-routing-and-unreviewed-rural-TIGER-tp5848084p5848589.html > Sent from the USA mailing list archive at Nabble.com. > > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] cycle.travel US bike routing, and unreviewed rural TIGER
Just as a postscript to this discussion I thought I'd cite an example area. If you look here, in Georgia: http://cycle.travel/map?lat=31.9023&lon=-84.0398&zoom=14 you'll see that most of the roads are unreviewed TIGER residentials. Of those, these are adjacent to each other: http://www.openstreetmap.org/way/9359782 - good tarmac, should be highway=tertiary http://www.openstreetmap.org/way/9359913 - unpaved road; highway=unclassified, surface=unpaved http://www.openstreetmap.org/way/9359784 - probably tertiary, but lousy geometry at the S http://www.openstreetmap.org/way/9359783 - whoops, where did the connectivity go? All of this is trivially fixable but right now there's no way of using them for routing or sensible cartography. Do dive in - the cycle.travel rendering makes it obvious which bits need fixing, and you learn to identify the roads which are likely to be paved through roads and therefore targets to fix. It's quite good fun. :) cheers Richard -- View this message in context: http://gis.19327.n5.nabble.com/cycle-travel-US-bike-routing-and-unreviewed-rural-TIGER-tp5848084p5848589.html Sent from the USA mailing list archive at Nabble.com. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
