Hi Paul, The the most correct way is to provide for the affected ways the explicit surface= tag in suitable OSM editor, e.g. the online editor ID, invocable from the OSM site. you need the OSM account for that.
Another way is to tweak the OSMAnd routing.xml to explicitly address the "3rd state" of surface tag, depending of the tag highway=. There is need to extract the file from the OSMAnd application package http://download.osmand.net/releases/ modify it and place it in the base OSMand data folder. The disadvantage is, this is only for you, and you need keep updating the file with updating the OSMAnd, especially for major OSMAnd updates. As this external file takes precedence of the default internal file version. Yet another way is to use BRouter routing and a profile explicitly addressing the surfaces On 05/02/2017 02:17 PM, 'P Wat' via Osmand wrote:
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
-- Poutnik ( The Pilgrim, Der Wanderer ) 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]. For more options, visit https://groups.google.com/d/optout.
