Re: 3.4.0 I'm very disappointed
Great! Thank you so much. -- 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 osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/be23deac-6ffd-48da-b420-cc27d5a6300a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: calculating route is acting strange
Have you considered letting Osmand calculate the route? (Instead of creating in on other software). See https://groups.google.com/d/topic/osmand/ycufpFjzAP8/discussion from July 4th? Paul W On Friday, July 5, 2019 at 2:34:26 PM UTC+1, Peer wrote: > > Today I imported a track (from myrouteapp.com. This track has a length of > 410 km and contains 53 routepoints. I choose this track for navigation with > the option 'calculate route between points'. > > I took my motorola e4plus more then two whole minutes to calculate the > route. > > The starting point of the route was by my house. After the start OsmAnd > let me four time take a right turn and then I am back at my home again. > Then OsmAnd continues with the route. The option 'calculate route til first > and last point' is disabled. It looks as if OsmAnd recognises the first > point after it is passed so it wil find the shortest route to this point > and therefore creates the loop. > The calculated route is almost the same as the track. There are a few > points where the route is different from the track. I tried some navigation > option in OsmAnd but I always got the same result. So I think this has > something to do with the map. > > I will not navigate this route. I allready noticed that recalculating can > give strange behaviour on shorter tracks (100km). Therefor I can expect > problems with this 400km track. > > I like the feature 'Calculate the route between points' very much but at > this moment I think that the route calculation should be improved. I hope > to see an improved version in a coming version of OsmAnd. > > Op maandag 1 juli 2019 13:43:39 UTC+2 schreef Peer: >> >> I created a track with waypoints on MyRouteApp.com and saved it to the >> tracks directory of OsmAnd. >> I choosed the track for navigating with the option 'Calculate route >> between Points'. >> >> At first the navigating was fine. After approximately one hour OsmAnd was >> starting to act strange when it should recalculate a route. The >> recalculated as not logical. >> example 1: >> I should take a turn right into a side street. But OsmAnd wants me to go >> straight ahead, make a u-turn on a roundabout 200 meters further and then >> make a left turn into the side straat. >> example 2: I have to drive straight ahead. But Osmand wants me to turn >> right into a side street, make a uturn after 100meters and then turn right >> again to follow the orginal route. >> >> This happened several times, always when recalculating a route. I do not >> know if this is problem in OsmAnd (version 3.3.8) or that my phone (Samsung >> trend, 6 years old) is just not strong enough for performing this >> calculations. >> > -- 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 osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/f536c8d7-416e-4d46-921e-1bd27095b19f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Free version or Osmand+
FWIW. Last year we cycled every day for 14 days touring in Netherlands. We used an Android phone with OsmAnd+ all the way. Each night it was re-charged on mains at B You can also top up at cafes etc en-route if necessary. On longer days, and if the phone was used for other purposes during the day (email, web browsing, phone calls, etc.) we were able to keep it running with a power pack which is combined with a solar panel. This unit is about the same size as the phone. I hang it on the cross-bar or handlebars, facing the (usually by then) setting sun. Power is saved by switching the screen off most of the time, ie using the vocal turn-by-turn instructions. Last summer "Screen auto-on-off" was available on Osmand. It is currently not available but we understand it will soon be available again. It is (was/will-be) a system which turns the screen on for just a few seconds each time there is a turn to do, then off again - An excellent benefit in terms of power-saving! Note, you can select (in settings) Flat/Less hilly/Hilly, and various categories of things to avoid (eg unpaved/stairs/etc), and other things in "Driving style". As a further extension, you can combine OsmAnd with Brouter which has several profiles from which to choose, though I often just stick to Osmand's own routing. As for Free version Vs OsmAnd+ (paid). What does it cost? A couple of beers? Good value for money, a VERY small proportion of your holiday cost, and it supports the valuable work done for us users. Good luck Paul W On Wednesday, July 3, 2019 at 3:36:28 PM UTC+1, Lukas wrote: > > Hey guys > > I'm a cyclist and currently looking for the perfect route planer AND > navigator while on the road. I'm planning on doing big tours for up to 10 > days on my road bike. Some people recommended Osmand so I'm looking into > that now. First of all: Do you guys think this is the BEST application for > my needs on the market right now? What other do you recommend? > > Then I figured that there's a free app and a paid one. The only big > difference I saw until now was that there's unlimited map downloads in the > paid version. What are the other differences? Do you think it's worth it to > buy the full one? > > Any other hints how to get started etc. are highly appreciated. > > Thank you so much for your support. > > Cheers, > Lukas > -- 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 osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/fafd36f7-2f9d-4e0d-b1ae-114a7f3b55d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: calculating route is acting strange
Today I imported a track (from myrouteapp.com. This track has a length of 410 km and contains 53 routepoints. I choose this track for navigation with the option 'calculate route between points'. I took my motorola e4plus more then two whole minutes to calculate the route. The starting point of the route was by my house. After the start OsmAnd let me four time take a right turn and then I am back at my home again. Then OsmAnd continues with the route. The option 'calculate route til first and last point' is disabled. It looks as if OsmAnd recognises the first point after it is passed so it wil find the shortest route to this point and therefore creates the loop. The calculated route is almost the same as the track. There are a few points where the route is different from the track. I tried some navigation option in OsmAnd but I always got the same result. So I think this has something to do with the map. I will not navigate this route. I allready noticed that recalculating can give strange behaviour on shorter tracks (100km). Therefor I can expect problems with this 400km track. I like the feature 'Calculate the route between points' very much but at this moment I think that the route calculation should be improved. I hope to see an improved version in a coming version of OsmAnd. Op maandag 1 juli 2019 13:43:39 UTC+2 schreef Peer: > > I created a track with waypoints on MyRouteApp.com and saved it to the > tracks directory of OsmAnd. > I choosed the track for navigating with the option 'Calculate route > between Points'. > > At first the navigating was fine. After approximately one hour OsmAnd was > starting to act strange when it should recalculate a route. The > recalculated as not logical. > example 1: > I should take a turn right into a side street. But OsmAnd wants me to go > straight ahead, make a u-turn on a roundabout 200 meters further and then > make a left turn into the side straat. > example 2: I have to drive straight ahead. But Osmand wants me to turn > right into a side street, make a uturn after 100meters and then turn right > again to follow the orginal route. > > This happened several times, always when recalculating a route. I do not > know if this is problem in OsmAnd (version 3.3.8) or that my phone (Samsung > trend, 6 years old) is just not strong enough for performing this > calculations. > -- 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 osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/f128ae3f-709f-4b36-bf9f-df080cb50f1b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: What's up with map updates?
Are there any ongoing efforts to rewrite the software to create the maps in C++? I would expect a significant speedup on multicore processors. 'Xavier' via Osmand schrieb am Do., 4. Juli 2019, 20:56: > On Thu, Jul 04, 2019 at 02:14:21PM -0400, Greg Troxel wrote: > > > >I also don't understand why people are so upset about monthly updates > >being 10-20 days behind the end of the month. Yes, the next day would > >be better, but 1) it's so much faster than any non-OSM approach > > If I remember correctly, back when I had a TomTom, the map updates from > TomTom were available either on a 6 month cycle or yearly cycle. > > OsmAnd monthly updates, even if they don't arrive until the 10th of the > month, are already either six or twelve times more frequent than what > TomTom provided. > > I don't know what cycle TomTom is on now, as I switched to OsmAnd when > TomTom decided to drop support for my old navigator. > > > and 2) with osmand live, it matters very little. Even without > >osmandlive, having map data that's between 20 and 50 days old at any > >point isn't much worse than having data that's between 5 and 35. > > 20-50 days old seems better than 180 or 365 days old (and of course > with TomTom one had to pay per update or 'subscribe' to a limited > number of updates). > > -- > 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 osmand+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/osmand/20190704185647.GN1375%40d820.dp100.com > . > 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 osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CA%2BCgGZRsKdoZwQrBth1okp1WxXsD4bqnTrDk72X5CUXQvXbmCQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
