Hi Gerd
Thanks a lot; will test it when the .jar file is available.
I haven't investigated if the FIDs and PIDs also need to be checked for
an invalid input.
Nick
On 01/11/2019 21:18, Gerd Petermann wrote:
Hi Nick,
reg. --mapname=:
The attached patch stops mkgmap before computing
Hi Nick,
reg. --mapname=:
The attached patch stops mkgmap before computing any tile when it calculates
an invalid mapid for any tile.
I tested special cases like
java -jar mkgmap.jar d:\osm\9.osm d:\osm\sample.osm
or
java -jar mkgmap.jar d:\osm\sample.osm --mapname=
Hi,
first, many thanks to all of you who are supporting this great tool.
The last days I decided to upgrade to the newest version of mkgmap and to the newest bounds and sea files. I downloaded all files (mkgmap, bounds, sea). But then I had to stop for some reasons. And today I started
Hi Nick,
NET3 is just a list of offsets into NET in a particular order. The problem is
not the order itself but the de-duplication that happens before.
My current understanding is that the list should contain all roads which have
numbers or more than one city. This is not always the case.
BTW:
Hi Gerd
No rush
What you are finding out about NET3 is really fascinating. Hope you are
able to uncover how identical treet names are linked to their coordinates.
Nick
On 01/11/2019 08:42, Gerd Petermann wrote:
Hi Nick,
okay, I'll have a look later. I am now working on problems with the
Hi Nick,
okay, I'll have a look later. I am now working on problems with the address
search in trunk version. I've noticed that some house numbers are not found in
Mapsource, reason are missing entries in NET3. So far I've learned that NET3
must contain all roads with numbers. There is also
