i agree that the usage of pre-compiled bounds could be clearer, especially to "outsiders" who don't/can't read whole threads in the archives and distill their conclusions from there... How do I use mkgmap to make a perfectly up-to-date map, including a similarly up-to-date index? One "obvious" way is to simply use the downloaded pbf file, without pre-compiled bounds. The pre-compiled bounds which are available for download are updated rather infrequently, and I have been doing a lot of work on boundaries recently. Do I *have* to create my own bounds files from the downloaded PBF and then use them as "pre-compiled"? Is using "pre-compiled bounds" merely a performance enhancement, or is there a functional difference between the maps obtained with and without their usage? I can imagine similar questions arise about the use of pre-compiled sea. Colin On 02/12/2012 12:50, WanMil wrote:
> --index \ 5 and 6. I'd be inclined not to make it the default
I don't understand if the index code is stable enough, but I thought that generally people should want this. If that's off, though, it makes sense to default to off until such time as it's stable.
Another usability comment is that I find the precompiled bounds situation a bit confusing. But maybe I haven't tried hard enough.
What do you think is confusing? Do you have a better idea? What do you expect and what do you think is useful? I would like to make it easier if possible.
WanMil
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev