--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/ec80f605-678f-4c66-ae52-a0a5e04efb8e%40googlegroups.com.
Osmand is doing all the calculations on your phone. Waze is using Google's datacenters. One has more computing power than the other.
On Thu, Mar 5, 2020 at 7:02 AM Episteme PROMENEUR <episteme...@gmail.com> wrote:
--Osmand routing calculation is very slow for long distance for many years.If you use for other app then no problem for example "waze"What is the problem ? No expert in Osmand team ? Not enough devs ? Something else ?If you use other app then no problem for example "waze"
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 osm...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/36863f4d-c0c1-4a8e-89a0-512b0e055697%40googlegroups.com.
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/86746d7f-f827-485f-bb9c-9af57f413c2c%40googlegroups.com.
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/86746d7f-f827-485f-bb9c-9af57f413c2c%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/77405db7-b42e-9a47-1a63-ece742ccf644%40gmail.com.
The issue is OsmAnd and its heuristic coefficient of 1.0. Not any other application is doing that.
Because the growth of OSM data has been faster than Moores law. So your
CPU <> Memory interface did not improve as fast as the OSM Data grew.
If you want to calculate a route you need to consider a LOT of data
and it grows exponentially by distance.
Other routers take short-cuts like OSRM with contracted hierarchies
etc. OSMAnd OTOH uses a more conservative approach which works pretty
well and i still like the amount of tags it supports and takes into
account for routing.
On Fri, Mar 06, 2020 at 10:11:41AM +0100, Harry van der Wolf wrote:
Comparing apples to peaches. You may integrated data for display and
routing, or you only consider routing. I use OSMAnd because it displays
lots of OSM data as i can visually verify completeness.
So use a different application - Where is the problem?
About long distance itinerary computing,for bike trekking what value for hc ?How to assign this value ?
I tried but no file in ..data/net.osmand/files/routingEither in memory nor in sdcard....
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/5e63daa0.1c69fb81.273fd.8022%40mx.google.com.
My sd card as the following
storage/8549-0EE7/android/data/net.osmand/files/routing
what I do not understand: I would expect the 1,5 to give the fastest route also, due to smaller rates of choice. but although the differences are close to non-existence that is not the case.
when I drive by car I am mostly not in a hurry and would like to be lead to small unknown roads that even shorten my way - so I mostly choose gas saving (in fact, that is what I love osmand the most for!). one problem here still remains: the time calculations become completely wrong the moment I switch for gas saving. they are more than 50% to high (while without they are pretty much exact). a trip which takes about 3hours20 may be displayed with 5hours10. that shure helps not starting too late - but arriving way too early doesn't help either ;-) how can I change that without getting into even bigger problems? thank you!
- the other aspect is the "averge cost factor", so the ratio of average versus minimal cost, which should be close to 1 and is e.g. about 1.05 for the "car eco" profile, 1.16 for "car fast". It's important to be close to 1 here to keep the search area small.
I don't believe at all in "unconditional surrender" when going away from 1.0. (And obviously neither do all those other navigation app builders.)
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/a624e0fa-fa7f-4faa-a302-90653a33ae7a%40googlegroups.com.
"'Arndt' via OsmAnd" <osm...@googlegroups.com> writes:
> So yes, if you know you "x" and are pretty sure the your hc stays well
> below, fine.
We don't know x, it seems.
I wonder if an algorithm that starts with hc sort of too high, but high
enough to be known to be adequately fast, perhaps 1.5, and then if the
computation finishes in a reasonable period of time, recompute with 1.4,
and so on. Perhaps this could be done more aggressively when on
external power, and less so on battery. (IMHO, navigating 500 km routes
on the phone's internal battery makes little sense anyway.)
Sorry. My stupid mistake. I said roads, but I meant routing (of course).When I said that the data is not so big, I meant the routing data.
Even better, post something of this quality (but a bit more elaborate) on your personal web space? That would make you king of the hill of A* !!! :-D
On Tuesday, March 10, 2020 at 12:13:28 AM UTC+1, Greg Troxel wrote:
>> And indeed: Simply copying the default profile and lowering the max speed
>> to 100 (what it will be in the Netherlands anyway after 16.03), does indeed
>> result in shorter computation times.
> Yes, but does it compute the same routes?No, if you set maxspeed=130 because you want to prefer the unlimited motorways AND if they actually exist, then you really need o keep maxspeed=130.With maxspeed=100 the unlimited highways will no longer be prefered.
superb, harry! was that done with setting FASTEST route or ENERGY SAVING? without being able to award you ANY price (besides a beer to be picked up here ;-) I would so very much like to see THESE very interesting differences. and to the above with the added setting AVOID HIGHWAYS - we all could learn so much!
already your statement of HC1.0 being wrong seems undoubtably proven.
up to 1 or 2 years ago "gas saving"/"kraftstoffsparend" was called "shortest" - I hope it actually is the same. I love it, not for gas saving, but to go along small roads I would never see else. I once travelled like that venice > berlin, very nice, if you take the time. or you quit the highway and take your way home avoiding highways ... almost impossible without a co-driver else ... on harry's list you see the time-miscalculations that way though ...
Dne 12. března 2020 5:14:34 A Thompson <thomp...@gmail.com> napsal:
Aaargh. I meant overestimates not underestimates. Wouldn't it be better if this were a google group where posts could be edited, rather than a mailing list archived as google group?
On Thursday, March 12, 2020 at 3:57:45 AM UTC, A Thompson wrote:As I understand it, the A* algorithm uses a heuristic that estimates the cost of the as-yet unexplored route from a point to the goal. If this function never underestimates the cost, then the optimal route is guaranteed to be found.
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/3b43ece4-e6dc-47bb-a731-7a4354c6c305%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/170cd38d210.2799.a291d67f9894f806060d35c996ca15e9%40gmail.com.
Just to add my 2-cents to the discussion. My use for OsmAnd's routing
(car) falls, primarially, into two major buckets:
1) to determine a route to get to a destination when I do not already
know how to navigate to that destination; and
2) to have an ETA indicator for long trips when I otherwise *do* know
how to navigate to the destination
Which led me to my opinion I stated above for #1. Yes, the chosen
route might be less optimal than what an 'insider' will pick, but it
will get me to my destination, and if I'm not an 'insider' in that
area, I'll never know the difference. And if I'm 'routing' via OsmAnd
in a location where I do have 'insider' knowledge, I'm simply going to
ignore the GPS's chosen route anyway.
Dne 13. března 2020 2:36:08 A Thompson <thomp...@gmail.com> napsal:
These are different. But it remains the case that the only absolute guarantee that the optimal route will be found is hc=1.0. I think I have created car and pedestrian profiles that use a customised routing.xml with hc=1.0 but I have yet to find a route that gives different results to OsmAnd 3.6.3's current values (1.5 for car, 1.2 for pedestrian).(Harry - had you noticed that the standard values are now this high?)
<routingProfile name="car" baseProfile="car" restrictionsAware="true" minSpeed="20.0" defaultSpeed="45.0" maxSpeed="130.0" leftTurn="5" rightTurn="5" roundaboutTurn="5" onewayAware="true"> <!--<attribute name="heuristicCoefficient" value="1.5" /> --> |
<routingProfile name="mycar13" baseProfile="car" restrictionsAware="true" minSpeed="20.0" defaultSpeed="45.0" maxSpeed="130.0" leftTurn="5" rightTurn="5" roundaboutTurn="5" onewayAware="true" heuristicCoefficient="1.3">
Dne 16. března 2020 9:34:33 Harry van der Wolf <hvd...@gmail.com> napsal:
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/170e3eb3700.2799.a291d67f9894f806060d35c996ca15e9%40gmail.com.
Dne 16. března 2020 18:57:52 Harry van der Wolf <hvd...@gmail.com> napsal:
Dne 16. března 2020 19:40:19 Poutnik Fornntp <poutni...@gmail.com> napsal:
Dne 16. března 2020 19:40:19 Poutnik Fornntp <poutni...@gmail.com> napsal:
Dne 16. března 2020 18:57:52 Harry van der Wolf <hvd...@gmail.com> napsal:
Osmand routing calculation is very slow for long distance for many years.If you use for other app then no problem for example "waze"What is the problem ? No expert in Osmand team ? Not enough devs ? Something else ?If you use other app then no problem for example "waze"
Dne 22. března 2020 7:54:19 Lodro Gyamtso <lodrog...@gmail.com> napsal:
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/4856016d-04c8-4515-938d-5b4358145e03%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to osm...@googlegroups.com.
after the answer of user "Poutnik", we have another proof that the OSMAnd and BRoute use slow (bad) technology.
Software like Here WeGO, Sygic, Tomtom Go, iGO, navigon, navitel, route 66, copilot, mireo, etc , are far away from this low level apps (OSMAnd and BRout). And all of this top companies has offline navigation apps. So, the user "Episteme PROMENEUR" has right into his first post.
My opinion is - don't use osmand, locus, orux, brouter, for city navigation. They are only for mountain use.
Dne 24. března 2020 7:32:45 Lodro Gyamtso <lodrog...@gmail.com> napsal:
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/726a6a04-bedf-40dd-b1ec-ef384563f713%40googlegroups.com.
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/jwvsghx99g3.fsf-monnier%2BInbox%40gnu.org.
this post is special for user "Harry van der Wolf"
who do you think that you are ? who gave you the right to say to other people - Please test yourself before posting these "theories".
Is your ego and arrogance ? That's why i suggest to you "don't say to other people what to do into their personal lives"
i am writing a post having experience of my devices or reading posts from other users. I did exactly what you made, i write my thoughts as you did, without judging other people. I use only what the others say, just to found answers.
Using my old smartphone for a route inside the city of 60 Km, the results time is over 1 minute for calculation. With my new smartphone for the same route needs less of 20secs to draw the route. With all the navigation apps i have mentions before, the route results is 1sec (instantaneously) for both of my devices.
p.s
sorry for my english
--
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/9455b432-a528-44ab-9949-8b31ba934569%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to osm...@googlegroups.com.
Dne 25. března 2020 22:06:52 Lodro Gyamtso <lodrog...@gmail.com> napsal:
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/07444c14-65bb-484b-b02e-3d56fac4f4e8%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/17114aea8b8.2799.a291d67f9894f806060d35c996ca15e9%40gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to osm...@googlegroups.com.
Dne 26. března 2020 7:35:10 Harry van der Wolf <hvd...@gmail.com> napsal:
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAGARPpu5ZS9L7%3DK%3DZR%2B6iqvqk8q9eLiMGrM8n8oTwxuTEMxE1Q%40mail.gmail.com.
Route calculation is slowi have found this text is from 24-04-2016. This situation is well known to the company.
Please be aware that there are 2 offline routing engines in the app: a Java based approach and a "Native" (C++) routing. The Java based approach is used in 'Safe Mode', it is 10 times slower than native mode and it has strict memory limitations. If you experience it and you see messages 'Not enough memory to compute', please go to Settings — 'General' — 'Safe mode' and make sure the option is disabled.
For native routing there are different limitations for different phones, depending on memory & processor. In general, native routing should handle < 300 km routes nicely. The route calculation should take between 15 sec and 4 minutes. It is prudent to not wait much longer than 4 minutes, because most likely the program will crash.
The only known workaround to compute long routes is to insert intermediate destinations. Two additional intermediate destinations should be enough even for very long routes.
How to calculate routes longer than 250km?
Many long routes (> 200-250km) cannot not be calculated by OsmAnd's offline routing engine today. If the app does not show a route after 7-8 minutes of calculation time, consider placing waypoints (pick e.g. places on motorways). 3-4 waypoints will be enough to calculate even 1000km routes.
there are different limitations for different phones, depending on memory & processor
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/40b29374-2daf-42b2-8c59-14796c995c71%40googlegroups.com.
Netherlands, Amstelveen Logger 41, 1186 RM
Victor Shcherb - Founder and CEO, Product Lead.
Alexey Kulish - Technical Lead, Android/iOS developer.
Eugene Kizevich - Marketing Lead.
Dmitriy Prodchenko - Product Lead, UI/UX designer.
Dr. Hardy Mueller - Map appearance concept and base renderers, international consistency and testing, usability, app scoping, concepts, documentation, wiki, market research.
Max (Zahnstocher) - Java contributor, active forum participant.
Leonid (xmd5a) - Co-author of main OsmAnd rendering, author of UniRS, LightRS styles.
Pavel Stetsenko - Key Android / IOS developer.
Vitaliy Golinko - Key Android developer.
Dne 26. března 2020 18:47:06 Lodro Gyamtso <lodrog...@gmail.com> napsal:
--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/09bee5c6-3b9e-4b3d-9468-1eb39f2a0aac%40googlegroups.com.
Each group is superior to the other in what it is focused to. Speed is both strength and weakness.