HOUSE NUMBER RANGE: Difference too large
HOUSE NUMBER RANGE: Difference too large I got this message, when i build a map with my DACH-poly, but i can't find the object. Is it possible, to get the object-ID? Logging is enabled with loglevel 'WARNING' Bernd
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 i build a map with my DACH-poly, but i can't find the object.
Is it possible, to get the object-ID? Logging is enabled with loglevel 'WARNING'
Bernd
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
signature.asc (271 bytes) <http://gis.19327.n5.nabble.com/attachment/5765720/0/signature.asc>;
-- View this message in context: http://gis.19327.n5.nabble.com/HOUSE-NUMBER-RANGE-Difference-too-large-tp576... Sent from the Mkgmap Development mailing list archive at Nabble.com.
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
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 one road segment with housenumbers in a large range, I can't say exactly the allowed values. I've committed r2561 to print a warning containing the OSM id when mkgmap is not able to convert the housenumber information into a valid bit string. Ciao, Gerd Bernd Weigelt wrote
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
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
signature.asc (271 bytes) <http://gis.19327.n5.nabble.com/attachment/5765944/0/signature.asc>;
-- View this message in context: http://gis.19327.n5.nabble.com/HOUSE-NUMBER-RANGE-Difference-too-large-tp576... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Am 19.06.2013 05:59, schrieb GerdP: Hi Gerd thank you I've fixed the housenumber. 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 one road segment with housenumbers in a large range, I can't say exactly the allowed values.
I've committed r2561 to print a warning containing the OSM id when mkgmap is not able to convert the housenumber information into a valid bit string.
participants (2)
-
Bernd Weigelt -
GerdP