addr:street and street name matching for house number searchs
HousenumberRoad throws a warning when addr:street from a node and name of the street the node is next to are not equal, even if they differ only in the capitalization. See for example nodes http://www.openstreetmap.org/node/2486105470 and http://www.openstreetmap.org/node/2486105464 (addr:street=carrer del Montseny) which are next to way http://www.openstreetmap.org/way/8590864 with name=Carrer del Montseny. One of the names is more correct than the other but, having in mind that Garmin changes capitalization arbitrarily, I'm not sure if we should keep these warnings. Another case to discuss is when one of addr:street or way name contains special letters and the other one not (eg. Asturies vs Astúries). Here one of the names is wrongly written and should be corrected in OSM data, so may be worth keeping the warning.
Hi Carlos, not sure what to do here. See first this discussion: http://gis.19327.n5.nabble.com/address-search-and-case-significance-of-stree... My problem reg. suppression of certain messages is that current code in mkgmap is not able to find a nearly matching road name, so it has no way to say "differs only in capitalization" or maybe "differs only slightly", it just doesn't find a road. Gerd
Date: Wed, 12 Aug 2015 13:54:51 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] addr:street and street name matching for house number searchs
HousenumberRoad throws a warning when addr:street from a node and name of the street the node is next to are not equal, even if they differ only in the capitalization. See for example nodes http://www.openstreetmap.org/node/2486105470 and http://www.openstreetmap.org/node/2486105464 (addr:street=carrer del Montseny) which are next to way http://www.openstreetmap.org/way/8590864 with name=Carrer del Montseny. One of the names is more correct than the other but, having in mind that Garmin changes capitalization arbitrarily, I'm not sure if we should keep these warnings. Another case to discuss is when one of addr:street or way name contains special letters and the other one not (eg. Asturies vs Astúries). Here one of the names is wrongly written and should be corrected in OSM data, so may be worth keeping the warning. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
OK, I see, not an easy matter. I will then have to deal with the nearly 90.000 lines of this type in my log for Spain;-) El 13/08/15 a las 08:10, Gerd Petermann escribió:
Hi Carlos,
not sure what to do here. See first this discussion: http://gis.19327.n5.nabble.com/address-search-and-case-significance-of-stree...
My problem reg. suppression of certain messages is that current code in mkgmap is not able to find a nearly matching road name, so it has no way to say "differs only in capitalization" or maybe "differs only slightly", it just doesn't find a road.
Gerd
Date: Wed, 12 Aug 2015 13:54:51 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] addr:street and street name matching for house number searchs
HousenumberRoad throws a warning when addr:street from a node and name of the street the node is next to are not equal, even if they differ only in the capitalization. See for example nodes http://www.openstreetmap.org/node/2486105470 and http://www.openstreetmap.org/node/2486105464 (addr:street=carrer del Montseny) which are next to way http://www.openstreetmap.org/way/8590864 with name=Carrer del Montseny. One of the names is more correct than the other but, having in mind that Garmin changes capitalization arbitrarily, I'm not sure if we should keep these warnings. Another case to discuss is when one of addr:street or way name contains special letters and the other one not (eg. Asturies vs Astúries). Here one of the names is wrongly written and should be corrected in OSM data, so may be worth keeping the warning.
-- Por favor, no me envíe documentos con extensiones .doc, .docx, .xls, .xlsx, .ppt, .pptx, .mdb, mdbx Instale LibreOffice desde http://es.libreoffice.org/descarga/ LibreOffice es libre: se puede copiar, modificar y redistribuir libremente. Gratis y totalmente legal. LibreOffice está en continuo desarrollo y no tendrá que pagar por las nuevas versiones.
Hi Carlos, the best solution would be to correct errors in OSM data. Polish mappers got a site, which shows all addresses, that needs to be corrected. Maybe you can ask Spanish community to do something similar? See: http://v3.mrowka.org/adresy/#7/52.298/19.199 -- Best regards, Andrzej
Hi Carlos, today I revieved the source and found that my statement was no longer true, mkgmap "knows" the roads and can ignore the capitalization. My argument was based on a previous version in the housenumber2 branch. The attached patch will solve many, but probably not all cases. Instead of WARN: uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberRoad e:\osm_out_work\niedersachsen\20150810_082633\63240021.o5m: found no plausible road for address Am kleinen Esch 1D(0) http://www.openstreetmap.org/node/1601720743 it will now print WARN: uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator e:\osm_out_work\niedersachsen\20150810_082633\63240021.o5m: accepting match in spite of different capitalization Am Kleinen Esch 1D (http://www.openstreetmap.org/browse/way/43561741) house: http://www.openstreetmap.org/node/1601720743 and it will use the address. I did not check special cases, e.g. when there are multiple close roads with different spelling. Also, addr:interpolation ways with different spelling may not yet fully work, but it should help in most cases. A binary is here: http://files.mkgmap.org.uk/download/275/mkgmap.jar Gerd
Date: Sun, 16 Aug 2015 17:20:38 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] addr:street and street name matching for house number searchs
OK, I see, not an easy matter. I will then have to deal with the nearly 90.000 lines of this type in my log for Spain;-)
El 13/08/15 a las 08:10, Gerd Petermann escribió:
Hi Carlos,
not sure what to do here. See first this discussion: http://gis.19327.n5.nabble.com/address-search-and-case-significance-of-stree...
My problem reg. suppression of certain messages is that current code in mkgmap is not able to find a nearly matching road name, so it has no way to say "differs only in capitalization" or maybe "differs only slightly", it just doesn't find a road.
Gerd
Date: Wed, 12 Aug 2015 13:54:51 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] addr:street and street name matching for house number searchs
HousenumberRoad throws a warning when addr:street from a node and name of the street the node is next to are not equal, even if they differ only in the capitalization. See for example nodes http://www.openstreetmap.org/node/2486105470 and http://www.openstreetmap.org/node/2486105464 (addr:street=carrer del Montseny) which are next to way http://www.openstreetmap.org/way/8590864 with name=Carrer del Montseny. One of the names is more correct than the other but, having in mind that Garmin changes capitalization arbitrarily, I'm not sure if we should keep these warnings. Another case to discuss is when one of addr:street or way name contains special letters and the other one not (eg. Asturies vs Astúries). Here one of the names is wrongly written and should be corrected in OSM data, so may be worth keeping the warning.
-- Por favor, no me envíe documentos con extensiones .doc, .docx, .xls, .xlsx, .ppt, .pptx, .mdb, mdbx Instale LibreOffice desde http://es.libreoffice.org/descarga/ LibreOffice es libre: se puede copiar, modificar y redistribuir libremente. Gratis y totalmente legal. LibreOffice está en continuo desarrollo y no tendrá que pagar por las nuevas versiones.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Your patch caught 19293 lines of my log. Although those cases must also be corrected in OSM data, they can now be put in a second priority level, so +1 from me to commit the patch. Have you thought about including alt_name in the match search when matching with name fails? I have found some cases where it can help. El 17/08/15 a las 10:42, Gerd Petermann escribió:
Hi Carlos,
today I revieved the source and found that my statement was no longer true, mkgmap "knows" the roads and can ignore the capitalization. My argument was based on a previous version in the housenumber2 branch. The attached patch will solve many, but probably not all cases. Instead of WARN: uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberRoad e:\osm_out_work\niedersachsen\20150810_082633\63240021.o5m: found no plausible road for address Am kleinen Esch 1D(0) http://www.openstreetmap.org/node/1601720743
it will now print WARN: uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator e:\osm_out_work\niedersachsen\20150810_082633\63240021.o5m: accepting match in spite of different capitalization Am Kleinen Esch 1D (http://www.openstreetmap.org/browse/way/43561741) house: http://www.openstreetmap.org/node/1601720743 and it will use the address.
I did not check special cases, e.g. when there are multiple close roads with different spelling. Also, addr:interpolation ways with different spelling may not yet fully work, but it should help in most cases.
A binary is here: |http://files.mkgmap.org.uk/download/275/mkgmap.jar
|Gerd
Date: Sun, 16 Aug 2015 17:20:38 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] addr:street and street name matching for house number searchs
OK, I see, not an easy matter. I will then have to deal with the nearly 90.000 lines of this type in my log for Spain;-)
El 13/08/15 a las 08:10, Gerd Petermann escribió:
Hi Carlos,
not sure what to do here. See first this discussion:
http://gis.19327.n5.nabble.com/address-search-and-case-significance-of-stree...
My problem reg. suppression of certain messages is that current code in mkgmap is not able to find a nearly matching road name, so it has no way
to say
"differs only in capitalization" or maybe "differs only slightly", it just doesn't find a road.
Gerd
Date: Wed, 12 Aug 2015 13:54:51 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] addr:street and street name matching for house number searchs
HousenumberRoad throws a warning when addr:street from a node and name of the street the node is next to are not equal, even if they differ only in the capitalization. See for example nodes http://www.openstreetmap.org/node/2486105470 and http://www.openstreetmap.org/node/2486105464 (addr:street=carrer del Montseny) which are next to way http://www.openstreetmap.org/way/8590864 with name=Carrer del Montseny. One of the names is more correct than the other but, having in mind that Garmin changes capitalization arbitrarily, I'm not sure if we should keep these warnings. Another case to discuss is when one of addr:street or way name contains special letters and the other one not (eg. Asturies vs Astúries). Here one of the names is wrongly written and should be corrected in OSM data, so may be worth keeping the warning.
Hi Carlos, okay, thanks for the quick feedback. I'll try to find out more about the possible special cases. Gerd
Date: Mon, 17 Aug 2015 17:12:16 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] addr:street and street name matching for house number searchs
Your patch caught 19293 lines of my log. Although those cases must also be corrected in OSM data, they can now be put in a second priority level, so +1 from me to commit the patch. Have you thought about including alt_name in the match search when matching with name fails? I have found some cases where it can help.
El 17/08/15 a las 10:42, Gerd Petermann escribió:
Hi Carlos,
today I revieved the source and found that my statement was no longer true, mkgmap "knows" the roads and can ignore the capitalization. My argument was based on a previous version in the housenumber2 branch. The attached patch will solve many, but probably not all cases. Instead of WARN: uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberRoad e:\osm_out_work\niedersachsen\20150810_082633\63240021.o5m: found no plausible road for address Am kleinen Esch 1D(0) http://www.openstreetmap.org/node/1601720743
it will now print WARN: uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator e:\osm_out_work\niedersachsen\20150810_082633\63240021.o5m: accepting match in spite of different capitalization Am Kleinen Esch 1D (http://www.openstreetmap.org/browse/way/43561741) house: http://www.openstreetmap.org/node/1601720743 and it will use the address.
I did not check special cases, e.g. when there are multiple close roads with different spelling. Also, addr:interpolation ways with different spelling may not yet fully work, but it should help in most cases.
A binary is here: |http://files.mkgmap.org.uk/download/275/mkgmap.jar
|Gerd
Date: Sun, 16 Aug 2015 17:20:38 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] addr:street and street name matching for house number searchs
OK, I see, not an easy matter. I will then have to deal with the nearly 90.000 lines of this type in my log for Spain;-)
El 13/08/15 a las 08:10, Gerd Petermann escribió:
Hi Carlos,
not sure what to do here. See first this discussion:
http://gis.19327.n5.nabble.com/address-search-and-case-significance-of-stree...
My problem reg. suppression of certain messages is that current code in mkgmap is not able to find a nearly matching road name, so it has no way
to say
"differs only in capitalization" or maybe "differs only slightly", it just doesn't find a road.
Gerd
Date: Wed, 12 Aug 2015 13:54:51 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] addr:street and street name matching for house number searchs
HousenumberRoad throws a warning when addr:street from a node and name of the street the node is next to are not equal, even if they differ only in the capitalization. See for example nodes http://www.openstreetmap.org/node/2486105470 and http://www.openstreetmap.org/node/2486105464 (addr:street=carrer del Montseny) which are next to way http://www.openstreetmap.org/way/8590864 with name=Carrer del Montseny. One of the names is more correct than the other but, having in mind that Garmin changes capitalization arbitrarily, I'm not sure if we should keep these warnings. Another case to discuss is when one of addr:street or way name contains special letters and the other one not (eg. Asturies vs Astúries). Here one of the names is wrongly written and should be corrected in OSM data, so may be worth keeping the warning.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Andrzej Popowski -
Carlos Dávila -
Gerd Petermann