Ā key factor here is the nature of the data. The data that systems like Tom Tom are built on is notionally complete. That is to say all significant features of a type which are in existence are in the data set when it is created. This means the data files for systems like Tom Tom change relatively slowly. But, it is only feasible commercially for limited data sets; roads, rail, geographic data, postcodes etc.
The data set for OSM is quite different. For one, it is FAR richer and more diverse. Tom Tom will not provide info on cafes with associated opening times, wheelchair access and WiFi availability information. In this regard OSM data is also far less complete. My point is that in terms of comparison to the functionality of commercial GPS I'd say the OSM data is complete nowadays. If you are using OSMAnd as an alternative to Tom Tom, then monthly updates which come out a month behind are fine. But, if you use OSMAnd for the far richer data, it is not such a good situtation. Or at least, you have to accept you could be missing out on a LOT of detail created in the interim 8 weeks. The problem for me, is that it is this richer data that I want for trips. When, as is often the case, there is a lot of useful data missing i will mai it a part of my trip research. That way everyone gets to benefit in the long run. But I don't plan every trip far enough ahead that all the research is complete 2 months in advance. Hence the delay between updating the database and receiving that information in OSMAnd can be a problem. Now I've sussed the map creator I can compile and download a new New Zealand map in 90 minutes of so. -- 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/75532a1b-f019-40f1-86c5-b887f7e5340e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
