Re: [mkgmap-dev] Problem with splitter

Hi Teo, I tried to reproduce the problem with mkgmap trunk version r2248, but I get different results, esp. I don't see this flooding. I am using coastlines_europe-120128.osm.pbf, maybe your file is older? Gerd Matteo Gottardi-2 wrote Hi, I noticed a problem splitting the geofabrik pbf

Re: [mkgmap-dev] Problem with splitter

On Mon, Mar 12, GerdP wrote: Hi Teo, I tried to reproduce the problem with mkgmap trunk version r2248, but I get different results, esp. I don't see this flooding. I am using coastlines_europe-120128.osm.pbf, maybe your file is older? You need the exact same tiles, else you will not see

Re: [mkgmap-dev] Problem with splitter

Hi Thorsten, I tried with his *.cfg and his 63240018.osm.pbf With splitter r200 I produced an identical 63240018.osm.pbf Why do you think that I should use his areas.list ? Gerd Date: Mon, 12 Mar 2012 10:03:21 +0100 From: ku...@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re:

Re: [mkgmap-dev] [Patch] Error in BoundaryUtil

Hi WanMil, I don't see a need for the length field in the header, and I don't see how I could use it (I found no way to calculate how many bytes were removed from a stream) So I've coded this: Format type: String: BND Timestamp: long | Record format: String: (RAW, QUADTREE) | Record layout:

Re: [mkgmap-dev] using short_name tag of a boundary

thanks! I will try this method. But what if I want to use short_name only for boundaries and name for all other objects? I've seen .bnd files under hex editor and data from all tags is there so theoretically it is possible :). best regards Michal Rogala 2012/3/12 Gerd Petermann

Re: [mkgmap-dev] using short_name tag of a boundary

Hi Michal, Date: Mon, 12 Mar 2012 10:26:21 +0100 From: michal.rog...@gmail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] using short_name tag of a boundary thanks! I will try this method. But what if I want to use short_name only for boundaries and name for all other

Re: [mkgmap-dev] using short_name tag of a boundary

This isn't a problem. Just add afer addresspart of style-file: short_name=* { delete short_name } Henning Am 12.03.2012 10:26, schrieb Micha? Rogala: thanks! I will try this method. But what if I want to use short_name only for boundaries and name for all other objects? I've seen .bnd files

Re: [mkgmap-dev] using short_name tag of a boundary

great! Thank you very much :) 2012/3/12 aighes o...@aighes.de: This isn't a problem. Just add afer addresspart of style-file: short_name=* { delete short_name } Henning Am 12.03.2012 10:26, schrieb Michał Rogala: thanks! I will try this method. But what if I want to use short_name

Re: [mkgmap-dev] Problem with splitter

2012/3/12 GerdP gpetermann_muenc...@hotmail.com: Hi Teo, I tried to reproduce the problem with mkgmap trunk version r2248, but I get different results, esp. I don't see this flooding. I am using coastlines_europe-120128.osm.pbf, maybe your file is older? Hi Gerd, my coastlines file was the

Re: [mkgmap-dev] Problem with splitter

Hi Matteo, okay, I am able to reproduce the problem (also without the coastfile parameter). The log shows some warnings for relation 541757 (the Lago di Como) , so I should be able to understand what's happening and why it fails. Gerd Matteo Gottardi wrote 2012/3/12 GerdP

Re: [mkgmap-dev] [Patch] Error in BoundaryUtil

Hi Gerd, the length field is required to be able to add more fields to the header in the future. Example (please don't nail me with the given length of the fields - it's just an example): Header: Format type: String: BND Timestamp: long | Header length: int: 8+4+10+4 = 26 bytes | Record

Re: [mkgmap-dev] [Patch] Error in BoundaryUtil

Hi WanMil, the length field will only help when we want to allow an old mkgmap version to read a newer bnd format. I don't think that we need that. Any (incompatible) change in the record layout should increase the record id, so that a newer version can decide what fields are available. Gerd

[mkgmap-dev] BoundaryCoverageUtil

Hi, I have commited a new tool BoundaryCoverageUtil to the performance branch. Thanks to Gerd who ported it to the new boundary format. I have tested it with freshly compiled boundaries of africa and found some mysteries. http://files.mkgmap.org.uk/detail/60 contains a zip file with the

Re: [mkgmap-dev] [Patch] Error in BoundaryUtil

Gerd, I have commited your patch plus the header length implementation. The int for the record layout should give the format of the records not the header. So I don't see a reason to change the record layout id if I just want to add a field to the header and therefore I need the header length.

Re: [mkgmap-dev] Problem with splitter

Hi Gerd, when I had the problem some time ago, I did some rough checking on splitters output. What I know so far is, that splitter removes all the ways from a certain tile that have no node inside this tile. The problem arises when a tile boundary divides a multipolyon that consist of normally

Re: [mkgmap-dev] Problem with splitter

Hi Wolfgang, yes, that' s exactly what happens. I see three ways to solve this problem: 1) Enhance the logic in mkgmap that guesses how the missing ways completed the multipolygon, e.g. by adding a backtracking algorithmn (this is already suggested in the code). 2) Enhance splitter so that it