Separate names with a comma.
Discussion in 'Mapping & Navigation' started by EmmEff, Jul 28, 2014.
I just did a 234 miler. It took about that much to calculate. I think it's your phone.
I'm not using any "avoid" points in the settings. the routing typically starts in a residential area and goes out through the city, on to interstate, breaks off into small towns, across FS roads, then stops at whichever campground was close by. basically just drop the start/intermediate/final waypoints to build the route around. this time I ended up with about 142 miles, but it took maybe six seconds to plot it.
my phone isn't a powerhouse compared to today's models , but the 3gb ram seems to help. on my older still phone it would probably take thirty seconds to plot.
I used brouter as the rendering engine.
note, if you didn't know this already, brouter just works in the back ground, you don't interact with it at all.
I could probably do it a lot faster with locus, just because I'm better with its interface, but the rendering time is similar since it's just an application waiting on the route to be handed to it from brouter or graph hopper. some people could likely do it faster with Google maps or basecamp, but I'm trying to stay away from lugging a laptop on my bike.
oops, added screen shots
OK part of the difference is definition.
My 3 point route has a start, 3 shaping points and the finish.
Either way I am still seeing at least 1 min of chugging for each point I add and/or each time I re-organize the points.
That route would still take me a couple of minutes.
4 points on this route. Each point is added as a "subsequent destination". Each time it takes approximately 10 seconds to calculate.
Using a MotoZ Force.
I suspect it is heresy to bring this up in a smartphone/Osmand thread, but I do this all the time on my PC using Mapsource or Basecamp when creating a new trip. It rarely takes more than one second per intermediate point. I then convert that to a track and send the track to my navigation device.
It is a bit unfair to compare a phone to a pc as far as speed.
But, why don't you do the same thing with osmand? Create the route on your pc and send it to the device?
I am adding points as intermediate destinations as that is how I typiclay work.
I did try using subsequent destinations and the recalc times where closer to 30 secs so that does seem to make a difference.
While that is faster, I typiclay don't work my routes like that.
I will say as far as routing on the PC vs device, I know my garmins will route exactly how I do it in basecamp, but that took me awhile to get it right.
Is there a PC program that will absolutely route the same as this app?
For clarification I want a turn by turn route, not a track.
How deep into the back roads are you getting? I've had good luck with co-pilot doing what you are doing. It's just that in some of the out of the way places the maps aren't always completely accurate. The specialty of co-pilot is turn by turn routing.
So you want a route that behaves like a track?
I don't get it, there are no shaping point restrictions in OsmAnd, if you want exact you can lay it out as such, they aren't even that big. I had a track that was 3300km and VERY specifically constructed. OsmAnd had no issues with either long calculation or display, and that was being interrupted because I would power the device down to charge. Not even a new hotness type device either I was using a older Experia Z ultra as a primary nav device on that trip.
That was literally designing the track in Furkot and then dumping it down to the phone.
However, if you route, you aren't going to get identical behavior out of disparate devices and planners, they are going to calculate differently. Its usually not that big of a deal, but I do notice it when I am using routes generated by Garmin users.
Yep. i tried to do it your way and it took forever.
So I don't.
I'm not sure what you gain by putting point A and D and then inputting B and C. Just put them in chronological order and call it a day.
yuuup. basecamp takes about ten seconds to do a thousand mile plot on my old Mac mini dual core. on the quad core server it is much faster. honestly though I don't use it enough to figure out how to speed it up, or what features might bog it down. I only use it when I'm sharing tracks to other folks that I know will be using Garmin devices, and I don't want basecamp to spz out when they start trying to do stuff with the tracks
I know that in general the comparison might be unfair. But there are lots of things where the phone is far faster than the PC. So I don't think the slowness is endemic to the phone.
I think the problem with Osmand is just bad coding.
To be honest I am mainly a Garmin Montana user. But I have been transferring my tracks to Osmand as a backup. The worst issue is that Osmand will not break up a file
with multiple tracks. It shows them all and kind of treats them all as one at least in the fact that they are all the same color. So if I have a trip with 20 tracks, I have to break it up into 20 separate files and send each one individually to get Osmand to work the way I would like. Not good folks.
See the track thing I'd rather use locus for this. It's track management and database is fantastic. But for turn by turn routing I'll use copilot for longer trips and osmand for shorter trips.
yup, track managing is not great in Osmand
For tracks use Locus
I am not sure anything else comes close.
No I just want a route that gives me turn by turn and unless I deviate significantly from it, it does not change if I build it on a PC then put it on a device.
I have been doing just that for years, so that is my expectations.
I dont mind adding points to get a route that I want, but dont want to have to add more than are necessary.
I know many folks like tracks because they dont change and I do use those too as a back up/reference for if I do end up WAY off my planned route, but I prefer to use a route for navigation.
I assume when I make a route on osmand on the device it will run the way it is planned but on the 2 android devices I have this is a pretty slow process.
It does not sound like you have found a PC program that routes the same.
See that is a trick with OsmAnd if you get WAY off track, just stop and restart Navigation, it'll calculate back to the nearest point. This is useful in road closure/reroute type situations, stop nav and just map it, then when you are close restart...otherwise it tries to put you back exactly where you left the route and will drive you nuts with the rerouting messages.
...and it avoids recalculating more than a few kilometers
Well when I am building a route I dont know exactly where I want to go.
I tend to know where I want to end up, but then like to hunt around for the most interesting way between points and then shape my route to pick them up. Sorry it does not sound logical, but its how I have been doing it.
I agree for the most part. Thing is that OsmAnds map rendering is more clear and the voice is less aggravating.
Of course I have also been known to use locus on guidance with OsmAnd running nav under it for the voice commands.
Huh, that sounds like more of a flaw than a feature.
My buddies Zumo does something like that when we get off route.
Its a pain to have to stop so he can shut it down and restart the the route.
Mine might route funky for a bit trying to bring you back but quickly re-routes to the next point on its own.