Hi Ralf,
you got it wrong, it is about mkgmap because the problem is in this stage. The
subject might be misleading ;-)
Gerd
Von: mkgmap-dev im Auftrag von Ralf
Kleineisel
Gesendet: Freitag, 2. November 2018 21:48
An: Development list for mkgmap
Betre
On 11/02/2018 07:31 PM, Gerd Petermann wrote:
> just a guess: If you use option --add-pois-to-lines and you have a rule in
> the points file which processes ele to add a POI
> you may see something like that.
I may have understood this wrong, but wasn't the file size comparison
after the splitte
Hi Bernhard,
just a guess: If you use option --add-pois-to-lines and you have a rule in the
points file which processes ele to add a POI
you may see something like that.
Gerd
Von: mkgmap-dev im Auftrag von Gerd
Petermann
Gesendet: Freitag, 2. November
Hi Bernhard,
what are your rules for the contour lines?
Gerd
Von: mkgmap-dev im Auftrag von
Bernhard Hiller
Gesendet: Freitag, 2. November 2018 19:18
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
Hi all,
still struggling with that strange issue. But I guess I found some hint
to the cause: inconsistent file sizes.
- extracted OSM data: 400 MB pbf
- elevation contour lines: 600 MB pbf
- merged file: 1 GB pbf
So far, sizes are consistent.
When I run splitter on the OSM data only file, it p
