Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-28 Thread Dominik Röttsches
Hi Adrian, I came across a similar problem last year. The trouble was with the merge function of osmosis. It takes the bounding box of the output file, from the first input file, regardless of the bounding boxes of the other input files. But the data from all the input files is in the merged

Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-28 Thread Charlie Ferrero
On 28/04/2011 14:32, Dominik Röttsches wrote: [snip] I have a vague recollection that it is also possible to get the splitter to ignore the bounds in the input file. Any more thoughts on this coming back in the meantime? Dominik It's definitely possible in mkgmap using --ignore-osm-bounds,

Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-27 Thread Dominik Röttsches
Areas only cover Finland :-( http://maps.google.com/maps?q=roettsches.de%2Fdominik%2Fareas.kml Sorry, that link didn't work, here's the right one: http://maps.google.com/maps?q=http%3A%2F%2Froettsches.de%2Fdominik%2Fareas.kml d ___ mkgmap-dev

Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-27 Thread Marko Mäkelä
On Wed, Apr 27, 2011 at 10:14:14AM +0300, Dominik Röttsches wrote: Can I tell the splitter to ignore the map's bounding box altogether and find its own? Any other ideas how to make it take into account the whole merged map? Can you split each extract separately and then tell mkgmap to produce a

Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-27 Thread Dominik Röttsches
Hi Marko, Can you split each extract separately and then tell mkgmap to produce a map from the tiles generated by the three splitter runs? Good idea, thanks. Generation seems to have worked, at least combining Finland and Germany. When adding US, it complained map area too small to split.

Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-27 Thread Adrian
I came across a similar problem last year. The trouble was with the merge function of osmosis. It takes the bounding box of the output file, from the first input file, regardless of the bounding boxes of the other input files. But the data from all the input files is in the merged file. I

Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-27 Thread Marko Mäkelä
On Wed, Apr 27, 2011 at 02:48:03PM +0100, Adrian wrote: I worked around this problem, but it is not at all convenient. You create the output file in uncompressed .osm format. This can result in a large file. Then you edit the file with a hexadecimal editor, because it will be too large to edit

[mkgmap-dev] Tile splitter and merged maps?

2011-04-26 Thread Dominik Röttsches
Hi, I created a merged map using osmosis: $ ./osmosis --rb finland.osm.pbf --rb germany.osm.pbf --rb us-west.osm.pbf --merge --merge --wx DE_FI_USW.osm which results in an uncompressed XML output map DE_FI_USW.osm of ~36G in size. So this maps contains three different countries which do not

Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-26 Thread Marko Mäkelä
On Tue, Apr 26, 2011 at 08:00:27PM +0300, Dominik Röttsches wrote: I created a merged map using osmosis: $ ./osmosis --rb finland.osm.pbf --rb germany.osm.pbf --rb us-west.osm.pbf --merge --merge --wx DE_FI_USW.osm which results in an uncompressed XML output map DE_FI_USW.osm of ~36G in size.

Re: [mkgmap-dev] Tile splitter and merged maps?

2011-04-26 Thread Charlie Ferrero
On 26/04/2011 21:00, Dominik Röttsches wrote: Hi, I created a merged map using osmosis: $ ./osmosis --rb finland.osm.pbf --rb germany.osm.pbf --rb us-west.osm.pbf --merge --merge --wx DE_FI_USW.osm which results in an uncompressed XML output map DE_FI_USW.osm of ~36G in size. So this maps