Slow does not mean bad. Open projects with low budget do not have
computation power to preprocess the maps of the World.
OSMAnd and BRouter ( not BRoute nor BRout ) are fast enough for city
navigation. Plus their maps have superior details.
Advantage of contraction hierarchy comes rather for long distances, but it
may be disadvantage in rural areas, as their road network is a subset of
OSMAnd/BRouter.
Dne 24. března 2020 7:32:45 Lodro Gyamtso <lodrogyam...@gmail.com> napsal:
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.
On Sunday, March 22, 2020 at 9:23:18 AM UTC+2, Poutnik wrote:
Time needed to calculate the route grows in average quadratically with
distance , for both OSMAnd and BRouter. Brouter may use more resource
serving algorithm and data.
Online routing services use very different algorithms.
OSMAnd and BRouter use modifications of A-star algorithm, which is slow on
end device, but resource friendly for creation navigation data.
Online car routers usually contraction hierarchy or similar algorithm, that
is fast for end device, but is extremely demanding for preprocessing of the
server navigation data.
Dne 22. března 2020 7:54:19 Lodro Gyamtso <lodrog...@gmail.com> napsal:
from my experience with navigation, i have some information to share with you
- brouter says ... for every 1Km of travel distance, the time is 1sec to
design the route
- the osm maps is one open community and the users "draw" the maps into
computers
- maps from big companies like google or Here or tomtom, etc, has special
cars to collect data from the field
the results are ...
when the big cartographic companies collect data, they include info like
traffic data for 24/7 of time (365days per year). Those data is also
embedded into offline maps. The route algorithm use this info and during
the calculation rejects probably over the 95% of roads. So, the design time
into one trip will be very fast, 2-3 secs.
On Thursday, March 5, 2020 at 3:02:23 PM UTC+2, Episteme PROMENEUR 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 view this discussion on the web visit
https://groups.google.com/d/msgid/osmand/4856016d-04c8-4515-938d-5b4358145e03%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+unsubscr...@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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/osmand/1710c377408.2799.a291d67f9894f806060d35c996ca15e9%40gmail.com.
