Hi Poutnik. Thanks for your very swift feedback. So is the only solution to amend all such cases discovered existing on OSM? If so, what are the optimum and/or minimum amendments required? Paul W
On Tuesday, May 2, 2017 at 12:54:52 PM UTC+1, Poutnik wrote: > > Real status of the way is irrelevant. > > The only thing that matters is if it is recorded in Osm data, respectively > reflected in osmand obf maps. > > In this case it clearly is not, as for what you have provided there is no > tag hint for being unpaved. > > The only way to fix it is to correct Osm data. > > On 2 May 2017 13:43:37 "'P Wat' via Osmand" <[email protected] > <javascript:>> wrote: > >> A case of "Unpaved road not avoided in Bike profile" exists at 51.524592, >> -0.991479. >> Navigatrion was set to "Osmand" & "Avoid unpaved roads". >> I was approaching from North-East and was directed to turn left onto the >> footpath running south east from the paved road >> The path is clearly unpaved. See attached pic. or street view. The OSM >> data seems to be adequate "designation >> <http://wiki.openstreetmap.org/wiki/Key:designation?uselang=en-US> >> public_footpath - foot >> <http://wiki.openstreetmap.org/wiki/Key:foot?uselang=en-US> designated >> <http://wiki.openstreetmap.org/wiki/Tag:foot=designated?uselang=en-US> - >> highway <http://wiki.openstreetmap.org/wiki/Key:highway?uselang=en-US> >> footway >> <http://wiki.openstreetmap.org/wiki/Tag:highway=footway?uselang=en-US>." >> Why does this happen. >> What should one do to prevent it? >> Paul W >> >> >> >> On Friday, April 7, 2017 at 7:25:00 AM UTC+1, Poutnik wrote: >>> >>> Have you checked, if OSM data provides explicit unpaved tag hints for >>> affected ways ? >>> As many ways have no surface= tag, or quality is provided indirectly via >>> tag tracktype=, >>> or not at all. >>> >>> Note that incoming upgrade of OSMAnd provide huge upgrade of the >>> routing.xml >>> <https://raw.githubusercontent.com/osmandapp/OsmAnd-resources/master/routing/routing.xml> >>> >>> file, >>> so I would try to download and install not yet released new OSMAnd 2.6.1 >>> <http://download.osmand.net/releases/?C=M;O=D> . >>> >>> You can easily examine a/o share the current OSM tagging* of affected >>> ways >>> e.g. via providing a link to the particular provided route on >>> Brouter-web server. >>> <http://brouter.de/brouter-web/#zoom=15&lat=49.23127&lon=16.47919&layer=OpenStreetMap&lonlats=16.465673,49.2329%7C16.467519,49.236907%7C16.475844,49.238673%7C16.480823,49.242147&nogos=&profile=trekking&alternativeidx=0&format=geojson> >>> >>> If you go on the desktop to the left on DATA tab, >>> you can see table of routing related way segment tags. >>> >>> Such a table is downloadable also as a CSV download. >>> >>> * with some 7-10 day delay wrt primary OSM data >>> >>> Dne 07/04/2017 v 07:54 Nick Payne napsal(a): >>> >>> I have OsmAnd+ 2.5.4 installed on a Google Pixel running the latest >>> 7.1.2 Android update. In OsmAnd navigation settings for bicycle, I have >>> "Avoid" set to avoid toll roads and unpaved, but when I ask the app to >>> provide bicycle directions, if the directions take me to rural areas it >>> quite frequently routes me onto unpaved roads, even though the app is set >>> to avoid them. >>> >>> -- >>> >>> Poutnik ( The Wanderer ) >>> >>> My Brouter profiles https://github.com/poutnikl/Brouter-profiles/wiki >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Osmand" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
