The original question referenced the OSM wiki about "complex intersections"
at
https://wiki.openstreetmap.org/wiki/Tag:highway%3Dtraffic_signals#Complex_intersections
My much preferred tagging, not for any specific data consumer like OsmAnd,
is to "tag all incoming ways" as illustrated
at
A while back I submitting a change to make directions while hiking better:
Basically allow a "avoid roads" option to the foot routing. It was rejected
for a couple of reasons, the biggest one in my opinion was that the
developers did not see a use for it. I guess they never hike in areas where
Nice video. I have this version of OsmAnd and current maps but was unaware
that I could see the elevation profiles. Your methods work perfectly on my
phone.
On Thursday, May 4, 2017 at 12:08:41 PM UTC-7, Bart Eisenberg wrote:
>
> I've posted an instructional video on using the new elevation
Walking routes work on my Moto G4 Play which also lacks a compass. Once you
are moving OsmAnd can detect your direction and shows the location as an
arrow/triangle. If stationary, it shows a dot.
On Friday, May 5, 2017 at 10:58:43 AM UTC-7, Eric Voncken wrote:
>
> Does Osmand work for walking
1. You can see what roads have speed limits using one of the maps
provided by ITO.
See http://product.itoworld.com/map/124?lon=-122.03736=37.37416=13
2. You can use OsmTracker to record speed limits while you are driving.
Two ways on that: Press the voice record button and
The address search in Osmand has never been good and recent versions are so
much worse that I gave up. I've installed AddressToGPS and Acastus (both
available on F-Droid) and use them for address lookups then open the
resulting lat/lon in Osmand. AddressToGPS uses Google for its backend while
.
On Tuesday, February 7, 2017 at 9:42:21 AM UTC-8, Torben Vandborg wrote:
>
>
> Hi stf
>
> I have same version as you 2.5.4, but the APK is 2.5.3.345 and Osmand
> chrash with that version of the file. I have also tried the version on
> github with same result (crash). I tried
Careful with getting routing.xml from github: Sometimes there are changes
in it that are not finalized or compatible with the release of OsmAnd you
are running.
Case in point: I am running v2.5.4 and the version of routing.xml that was
on GitHub late last week would crash my version of OsmAnd.
