Hi Bernd,
this happens right before the data is written to the img file,
and I don't see a simple change to print any useful info.
Please post the data so that we can try to reproduce the
problem.
Gerd
Bernd Weigelt wrote
HOUSE NUMBER RANGE: Difference too large
I got this message, when
Am 18.06.2013 08:18, schrieb GerdP:
Please post the data so that we can try to reproduce the
problem.
I've two files to http://files.mkgmap.org.uk/, i can't find anything in
the log, but the O5M is the right one.
mapname: 65000105
description: DE-Duisburg
input-file: 65000105.o5m
Bernd
Many Thanks - that fixed the problem with the tile in Black Sea area, but I found another tile which cannot be rendered.
I have uploaded the PBF to http://files.mkgmap.org.uk/download/140/70010283.osm.pbf
mkgmap - the one you proposed to use http://files.mkgmap.org.uk/download/136/mkgmap.jar
Hi Chris,
mkgmaps current algorithm uses the addr:street tag to assign housenumber
to road segment. I don't see that assigning housenumbers to roads with
no road name is a good idea. I guess the rate of mistakes is too high.
So you problem could only be solved either by assigning a name to the
Hi,
the problem is similar. I guess we have more places were a string is
converted to an
array with split() and there is no check if the result has a length of 0.
I have to analyze all places were split() is used. This might take a
while...
Gerd
thesurveyor wrote
Many Thanks - that fixed the
Hi,
thanks for the info.
I suspected something like that.
As I understand there is a rule within the style and there is at least an OSM object in the map which must come together that mkgmap will fail.
So from my point it is not clear where it must be fixed. You can fix it in the code of
Version 2650 was committed by gerd on Wed, 19 Jun 2013
squashSpaces() return null for an empty string, as this seems to be the
expected value in the calling routines
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Gerd,
thesurveyor wrote
As I understand there is a rule within the style and there is at least an
OSM object in the map which must come together that mkgmap will fail.
So from my point it is not clear where it must be fixed. You can fix it in
the code of mkgmap, of course that is the
Version 2651 was committed by gerd on Wed, 19 Jun 2013
- add log message for invalid housenumbers
- handle case that java.util.regex.Pattern.split() can return an array with
length 0
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Bernd,
the problem is caused by this highway:
http://www.openstreetmap.org/browse/way/44174652
and the building
http://www.openstreetmap.org/browse/way/225876050
with addr:housenumber=231235.
I guess it was meant to be 231-235, and it should be just 231.
The img format doesn't seem to allow
10 matches
Mail list logo
