[mkgmap-dev] bugreport for new splitter
From Steve Ratcliffe steve at parabola.me.uk on Mon Aug 10 12:45:00 BST 2009
Hi On 10/08/09 10:52, Chris Miller wrote: > Given that it's only when a relatively low number is given for --max-nodes > that we run into any trouble, maybe it's best to leave at 2000 for now. Is > there a reason why people would want to use such a low number? Smaller tiles > so more flexibility about exactly what they upload to their Garmin perhaps? Well I'm just saying that there was no particular thought in choosing 2000 in the first place. For really old devices that have limited memory you may only be able to load a few tiles at a time and then it would be more flexible to have smaller tiles. But this is really from before OSM was started, I've never had anyone complain that tiles were too big, in fact quite the opposite. So ideally you want to be able to make the tiles as large as possible. However if you only look at the number of nodes then you find that you have to have it quite low to cope with one particular area when a higher value would have been fine everywhere else. ..Steve
- Previous message: [mkgmap-dev] bugreport for new splitter
- Next message: [mkgmap-dev] bugreport for new splitter
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list