![]() ![]() When traveling long distances we always use highways (or similar fast roads *). I wonder why long-distance trips are so slow to calculate. Maybe this old-school routing mechanism, that cgogolin mentioned and that I described above, could be a solution for Osmand's "long distance problem": connect the starting point and the destination by a straight line, then look for the best paved roads and fastest lanes along side this line, and off you go! And once you're within 50km of the final destination, Osmand can calculate the exact route. And I highly appreciate that and all the work that is being put into this project! I really love it! :)īut on the other hand: do you really need a navigation software, Osmand or other, to calculate a trip that consists of 490km on a highway and 10 km city traffic? I'd say: no! And, no offence meant, but any one who can't drive from edge of a country to the other without the use of a navigation software, should ask themselves, if taking a train wouldn't be the better solution. Osmand is unbeatable when it comes to finding addresses and guiding you through a city that is not your home town. No one in those days would have started a trip of more than 200km by writing down each and every single street and little dirt road, that would have summed up to the shortest way, needing 10 different detailed maps and taking 5 hours to calculate that route. And just before you left or passed the last way stop, you took a look at a detailed city map and only then you would have looked up the proper way to your destination. #AUTOMAPA WINCE 4.2 HOW TO#Then you memorized all the places along that road that you had to parse by or drive through, and then your trip started! Once on the road, you just followed the signs that told you how to drive from one way stop to the next. In those "pre-electronic age", when you had to make a trip from A to B, you took a look at a large scaled map, you mentally connected the places by a straight line, and you simply looked for the most convenient and fastest roads that were the closest to this line. #AUTOMAPA WINCE 4.2 DRIVER#I am a driver who has passed a certain age, and I can tell you, this is exactly the way how long distance trips were "calculated" back in "the good old days", when maps were made out of paper and electronic guidance was something that only the army used for their tanks and rockets. I will try other application, AutoMapa, which is alternative (not free) to check how it will work on Sony Xperia M.Ĭan long distance calculations not be done on a much simplified graph of just motorways and their rough intersections? So I am in fact driving without any navigation. And when calculation is over then it appears that new route still differs from my route and then calculation start again for next 4-5 minutes. ![]() But the navigation is still unusable - older version may calculate route faster but if i choose the other way than navigation proposed, OsmAnd starts to recalculating route again and it takes next 4-5 minutes. Returning to my previous post, I was happy that older 2.3.5 was able to calculate 250-300km distance in about 5 minutes, much short than 2.8.2. I would need to check this again because it was quite long ago (yes, versions 2.2 and 2.3).īesides, i didn't put any results from my latest tests which might put support in wrong here. On short routes, for example 30-50kms the calculation is quite fast, as far as i remember. Don't think so that this is the same issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |