Thanks for investigating it. I've been using those two rules for several years, it's strange the problem didn't arise till now.

El 26/2/21 a las 15:36, Gerd Petermann escribió:
Hi Carlos,


I didn't find a fix for the problem so far. I see what's going wrong but not 
why it only happens in this special situation.
Your points file contains these two rules:
highway=traffic_signals { add mkgmap:road-speed = '-1'; add 
mkgmap:road-speed-min = '1' }
highway=crossing { add mkgmap:road-speed = '-1'; add mkgmap:road-speed-min = 
'1' }

When I copy them to the default style I see the same error. Because of the 
extra rules and --link-poi-to-ways the OSM way 573320541 is split into smaller 
parts and somehow mkgmap fails to find the right part for the numbers generated 
by the addr:interpolation way.

Gerd

________________________________________
Von: mkgmap-dev <[email protected]> im Auftrag von Gerd 
Petermann <[email protected]>
Gesendet: Freitag, 26. Februar 2021 08:00
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] internal error: found no housenumber road

Hi Carlos,

OK, I can now reproduce with
java -Xmx4G -ea -jar d:\mkgmap\dist\mkgmap.jar --route --housenumbers  
--link-pois-to-ways  --style-option=language=non_latin --style-file=..\mio 
51690125.o5m

Also with a smaller extract. It seems your style in combination with 
--link-pois-to-ways triggers this...

Gerd

________________________________________
Von: mkgmap-dev <[email protected]> im Auftrag von Carlos Dávila 
<[email protected]>
Gesendet: Donnerstag, 25. Februar 2021 23:06
An: [email protected]
Betreff: Re: [mkgmap-dev] internal error: found no housenumber road

Removing --road-name-config didn't fix the problem. Error can be
reproduced with command:

java -Xmx27G -ea -jar mkgmap.jar -c opciones_comunes -c opciones_teselas
--latin1 --family-id=51169 --overview-mapname=OCE1169
--overview-mapnumber=51169000 --name-tag-list=int_name,name:en,name
--report-similar-arcs --report-dead-ends=2 --drive-on=detect,right
--check-roundabouts --check-roundabout-flares --license-file=license_OSM
--copyright-file=copyright  --style-option=language=non_latin
--style=mio 51690125.o5m

You can get all (I hope) needed files at
https://alternativaslibres.org/tmp/no_housenumber.zip

El 25/2/21 a las 22:34, Carlos Dávila escribió:
According to your comment, I think it may be caused by the line below
passed by  --road-name-config parameter. Testing now...

suffix:en = " Avenue", " Close", " Court", " Crescent", " Drive", "
Gate", " Grove", " Lane", " Mews", " Parade", " Place", " Road", "
Square", " Street", " Terrace", " View", " Way"


El 25/2/21 a las 20:53, Gerd Petermann escribió:
Hi Carlos,

I cannot reproduce this with the default style. The error message
means that mkgmap found a matching road at some time and later it
didn't. This should not happen, but maybe it depends on the style or
other options. I downloaded the small area and tried with
java -jar dist\mkgmap.jar --bounds=bounds.zip --route --housenumbers
--index d:\OSM\addr-inter.osm

Please let me know how to reproduce.

Gerd


________________________________________
Von: mkgmap-dev <[email protected]> im Auftrag
von Carlos Dávila <[email protected]>
Gesendet: Donnerstag, 25. Februar 2021 20:33
An: Development list for mkgmap
Betreff: [mkgmap-dev] internal error: found no housenumber road

While processing Australia I get several warnings of the form:

SEVERE (HousenumberGenerator): 51690125.o5m: internal error: found no
housenumber road for interpolated house
http://www.openstreetmap.org/?mlat=-37.782001&mlon=144.959382&zoom=17

Looking at that area in JOSM, I see addr:interpolation lines next to a
footway without a name, connecting houses with addr:street=Royal Parede,
and a primary road named Royal Parede some 20 m away from the
addr:interpolation lines. I guess mkgmap searches for street name in the
footway (which doesn't have a name) instead of in the Royal Parade road,
and thus it fails to assign housenumbers.

_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to