On Fri, Mar 06, 2020 at 10:11:41AM +0100, Harry van der Wolf wrote: > Lots of data? I have created maps only consisisting of roads. They are > minimal compared to OsmAnds full maps. The growth of data is in "all the > rest": more detailed forests, lakes, ponds, POIs, etcetera. Also the > growing addresses in OSM create a lot of data, but there there it is not > applicable for the calculation. You select an address, which is then > "converted" to a coordinate. From that moment you don't need the address > data anymore for your calculation.
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. > Growing data? Yes, more roads get added every day. But this data is indexed > and is not really adding to the calculation time. This data is spatially indexed and you search from A to B through a graph. Adding more streets increases the amount of graph edges you may need to consider and thus the size of your working set. > Longer distances? Yes, you are absolutely right. This is really the > "killing" factor when using an hc=1.0. If you really need to explore every > "path" in your bidirectional A* route calculation, bigger distances > exponentially increase calculation time and necessary memory. That is why > other nav apps do use an hc>1. So use a different application - Where is the problem? Flo -- Florian Lohoff [email protected] UTF-8 Test: The 🐈 ran after a 🐁, but the 🐁 ran away -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/20200306102859.75hctbstmr4vsya7%40pax.zz.de.
signature.asc
Description: PGP signature
