Wrong turn restriction warnings
Some of the turn restriction warnings reported by mkgmap are correctly mapped in OSM. They all seem to be near tile borders. Shouldn't keep-complete option of splitter take care of these relations? If you want to check some of these relations, here is the list I currently get processing a customized spain.osm.pbf file (I can supply the file if necessary) (max-nodes=2100000): Turn restriction http://www.openstreetmap.org/browse/relation/1610018 Turn restriction http://www.openstreetmap.org/browse/relation/2556829 Turn restriction http://www.openstreetmap.org/browse/relation/2556828 Turn restriction http://www.openstreetmap.org/browse/relation/1619758 Turn restriction http://www.openstreetmap.org/browse/relation/1619754 Turn restriction http://www.openstreetmap.org/browse/relation/1619760 Turn restriction http://www.openstreetmap.org/browse/relation/1874949 Turn restriction http://www.openstreetmap.org/browse/relation/1471323 Turn restriction http://www.openstreetmap.org/browse/relation/2733411 Turn restriction http://www.openstreetmap.org/browse/relation/1553991 Turn restriction http://www.openstreetmap.org/browse/relation/1553985 Turn restriction http://www.openstreetmap.org/browse/relation/1554001 Turn restriction http://www.openstreetmap.org/browse/relation/3499015 Turn restriction http://www.openstreetmap.org/browse/relation/1874952 Turn restriction http://www.openstreetmap.org/browse/relation/1874950 Turn restriction http://www.openstreetmap.org/browse/relation/3121764 Turn restriction http://www.openstreetmap.org/browse/relation/2512039 Turn restriction http://www.openstreetmap.org/browse/relation/3328204 Turn restriction http://www.openstreetmap.org/browse/relation/3395687 Turn restriction http://www.openstreetmap.org/browse/relation/3395691 Turn restriction http://www.openstreetmap.org/browse/relation/3395685 Turn restriction http://www.openstreetmap.org/browse/relation/3009483 Turn restriction http://www.openstreetmap.org/browse/relation/3009481 Turn restriction http://www.openstreetmap.org/browse/relation/3497275 Turn restriction http://www.openstreetmap.org/browse/relation/2074869 Turn restriction http://www.openstreetmap.org/browse/relation/3103660 Turn restriction http://www.openstreetmap.org/browse/relation/1694535 Turn restriction http://www.openstreetmap.org/browse/relation/1694528 Turn restriction http://www.openstreetmap.org/browse/relation/1694526 Turn restriction http://www.openstreetmap.org/browse/relation/1694533 Turn restriction http://www.openstreetmap.org/browse/relation/3526934
Hi Carlos, is the via point within the tile border? If not, it should be ignored. Gerd Carlos Dávila-2 wrote
Some of the turn restriction warnings reported by mkgmap are correctly mapped in OSM. They all seem to be near tile borders. Shouldn't keep-complete option of splitter take care of these relations? If you want to check some of these relations, here is the list I currently get processing a customized spain.osm.pbf file (I can supply the file if necessary) (max-nodes=2100000): Turn restriction http://www.openstreetmap.org/browse/relation/1610018 Turn restriction http://www.openstreetmap.org/browse/relation/2556829 Turn restriction http://www.openstreetmap.org/browse/relation/2556828 Turn restriction http://www.openstreetmap.org/browse/relation/1619758 Turn restriction http://www.openstreetmap.org/browse/relation/1619754 Turn restriction http://www.openstreetmap.org/browse/relation/1619760 Turn restriction http://www.openstreetmap.org/browse/relation/1874949 Turn restriction http://www.openstreetmap.org/browse/relation/1471323 Turn restriction http://www.openstreetmap.org/browse/relation/2733411 Turn restriction http://www.openstreetmap.org/browse/relation/1553991 Turn restriction http://www.openstreetmap.org/browse/relation/1553985 Turn restriction http://www.openstreetmap.org/browse/relation/1554001 Turn restriction http://www.openstreetmap.org/browse/relation/3499015 Turn restriction http://www.openstreetmap.org/browse/relation/1874952 Turn restriction http://www.openstreetmap.org/browse/relation/1874950 Turn restriction http://www.openstreetmap.org/browse/relation/3121764 Turn restriction http://www.openstreetmap.org/browse/relation/2512039 Turn restriction http://www.openstreetmap.org/browse/relation/3328204 Turn restriction http://www.openstreetmap.org/browse/relation/3395687 Turn restriction http://www.openstreetmap.org/browse/relation/3395691 Turn restriction http://www.openstreetmap.org/browse/relation/3395685 Turn restriction http://www.openstreetmap.org/browse/relation/3009483 Turn restriction http://www.openstreetmap.org/browse/relation/3009481 Turn restriction http://www.openstreetmap.org/browse/relation/3497275 Turn restriction http://www.openstreetmap.org/browse/relation/2074869 Turn restriction http://www.openstreetmap.org/browse/relation/3103660 Turn restriction http://www.openstreetmap.org/browse/relation/1694535 Turn restriction http://www.openstreetmap.org/browse/relation/1694528 Turn restriction http://www.openstreetmap.org/browse/relation/1694526 Turn restriction http://www.openstreetmap.org/browse/relation/1694533 Turn restriction http://www.openstreetmap.org/browse/relation/3526934 _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Not sure what you mean. See attached screenshot for relation 1610018. It's placed on the crossing below label "CL-501". Tile border is the vertical gray line on the left, so some 800 meters. overlap=auto El 21/02/14 19:31, GerdP escribió:
Hi Carlos,
is the via point within the tile border? If not, it should be ignored.
Gerd
Carlos Dávila-2 wrote
Some of the turn restriction warnings reported by mkgmap are correctly mapped in OSM. They all seem to be near tile borders. Shouldn't keep-complete option of splitter take care of these relations? If you want to check some of these relations, here is the list I currently get processing a customized spain.osm.pbf file (I can supply the file if necessary) (max-nodes=2100000): Turn restriction http://www.openstreetmap.org/browse/relation/1610018 Turn restriction http://www.openstreetmap.org/browse/relation/2556829 Turn restriction http://www.openstreetmap.org/browse/relation/2556828 Turn restriction http://www.openstreetmap.org/browse/relation/1619758 Turn restriction http://www.openstreetmap.org/browse/relation/1619754 Turn restriction http://www.openstreetmap.org/browse/relation/1619760 Turn restriction http://www.openstreetmap.org/browse/relation/1874949 Turn restriction http://www.openstreetmap.org/browse/relation/1471323 Turn restriction http://www.openstreetmap.org/browse/relation/2733411 Turn restriction http://www.openstreetmap.org/browse/relation/1553991 Turn restriction http://www.openstreetmap.org/browse/relation/1553985 Turn restriction http://www.openstreetmap.org/browse/relation/1554001 Turn restriction http://www.openstreetmap.org/browse/relation/3499015 Turn restriction http://www.openstreetmap.org/browse/relation/1874952 Turn restriction http://www.openstreetmap.org/browse/relation/1874950 Turn restriction http://www.openstreetmap.org/browse/relation/3121764 Turn restriction http://www.openstreetmap.org/browse/relation/2512039 Turn restriction http://www.openstreetmap.org/browse/relation/3328204 Turn restriction http://www.openstreetmap.org/browse/relation/3395687 Turn restriction http://www.openstreetmap.org/browse/relation/3395691 Turn restriction http://www.openstreetmap.org/browse/relation/3395685 Turn restriction http://www.openstreetmap.org/browse/relation/3009483 Turn restriction http://www.openstreetmap.org/browse/relation/3009481 Turn restriction http://www.openstreetmap.org/browse/relation/3497275 Turn restriction http://www.openstreetmap.org/browse/relation/2074869 Turn restriction http://www.openstreetmap.org/browse/relation/3103660 Turn restriction http://www.openstreetmap.org/browse/relation/1694535 Turn restriction http://www.openstreetmap.org/browse/relation/1694528 Turn restriction http://www.openstreetmap.org/browse/relation/1694526 Turn restriction http://www.openstreetmap.org/browse/relation/1694533 Turn restriction http://www.openstreetmap.org/browse/relation/3526934 _______________________________________________
Hi Carlos, you say that you see the message for the turn restriction in mkgmap. If one of the ways of relation 1610018 crosses the tile border, splitter will write all members of the relation to both tiles, but it is only usable in the tile that contains the via point. Gerd Carlos Dávila-2 wrote
Not sure what you mean. See attached screenshot for relation 1610018. It's placed on the crossing below label "CL-501". Tile border is the vertical gray line on the left, so some 800 meters. overlap=auto
El 21/02/14 19:31, GerdP escribió:
Hi Carlos,
is the via point within the tile border? If not, it should be ignored.
Gerd
Carlos Dávila-2 wrote
Some of the turn restriction warnings reported by mkgmap are correctly mapped in OSM. They all seem to be near tile borders. Shouldn't keep-complete option of splitter take care of these relations? If you want to check some of these relations, here is the list I currently get processing a customized spain.osm.pbf file (I can supply the file if necessary) (max-nodes=2100000): Turn restriction http://www.openstreetmap.org/browse/relation/1610018 Turn restriction http://www.openstreetmap.org/browse/relation/2556829 Turn restriction http://www.openstreetmap.org/browse/relation/2556828 Turn restriction http://www.openstreetmap.org/browse/relation/1619758 Turn restriction http://www.openstreetmap.org/browse/relation/1619754 Turn restriction http://www.openstreetmap.org/browse/relation/1619760 Turn restriction http://www.openstreetmap.org/browse/relation/1874949 Turn restriction http://www.openstreetmap.org/browse/relation/1471323 Turn restriction http://www.openstreetmap.org/browse/relation/2733411 Turn restriction http://www.openstreetmap.org/browse/relation/1553991 Turn restriction http://www.openstreetmap.org/browse/relation/1553985 Turn restriction http://www.openstreetmap.org/browse/relation/1554001 Turn restriction http://www.openstreetmap.org/browse/relation/3499015 Turn restriction http://www.openstreetmap.org/browse/relation/1874952 Turn restriction http://www.openstreetmap.org/browse/relation/1874950 Turn restriction http://www.openstreetmap.org/browse/relation/3121764 Turn restriction http://www.openstreetmap.org/browse/relation/2512039 Turn restriction http://www.openstreetmap.org/browse/relation/3328204 Turn restriction http://www.openstreetmap.org/browse/relation/3395687 Turn restriction http://www.openstreetmap.org/browse/relation/3395691 Turn restriction http://www.openstreetmap.org/browse/relation/3395685 Turn restriction http://www.openstreetmap.org/browse/relation/3009483 Turn restriction http://www.openstreetmap.org/browse/relation/3009481 Turn restriction http://www.openstreetmap.org/browse/relation/3497275 Turn restriction http://www.openstreetmap.org/browse/relation/2074869 Turn restriction http://www.openstreetmap.org/browse/relation/3103660 Turn restriction http://www.openstreetmap.org/browse/relation/1694535 Turn restriction http://www.openstreetmap.org/browse/relation/1694528 Turn restriction http://www.openstreetmap.org/browse/relation/1694526 Turn restriction http://www.openstreetmap.org/browse/relation/1694533 Turn restriction http://www.openstreetmap.org/browse/relation/3526934 _______________________________________________
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
MapSource.png (7K) <http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png>;
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
El 21/02/14 20:57, GerdP escribió:
Hi Carlos,
you say that you see the message for the turn restriction in mkgmap. Right If one of the ways of relation 1610018 crosses the tile border, splitter will write all members of the relation to both tiles, but it is only usable in the tile that contains the via point. Restrictions are correctly processed when a route is calculated, no problem there. The warning is not reported for the tile that contains the restriction (or the via point), but for the neighbor one. Would it be possible to detect that a restriction is fully contained in given tile and avoid such warnings in the neighbor one? The main concerns are the waste of time trying to fix restrictions reported by mkgmap that are correct in OSM and the bad experience of people who download errors files from my site and faces a list full of false errors, which for sure will dis encourage them to continue working on their fix. Carlos
Gerd
Carlos Dávila-2 wrote
Not sure what you mean. See attached screenshot for relation 1610018. It's placed on the crossing below label "CL-501". Tile border is the vertical gray line on the left, so some 800 meters. overlap=auto
El 21/02/14 19:31, GerdP escribió:
Hi Carlos,
is the via point within the tile border? If not, it should be ignored.
Gerd
Carlos Dávila-2 wrote
Some of the turn restriction warnings reported by mkgmap are correctly mapped in OSM. They all seem to be near tile borders. Shouldn't keep-complete option of splitter take care of these relations? If you want to check some of these relations, here is the list I currently get processing a customized spain.osm.pbf file (I can supply the file if necessary) (max-nodes=2100000): Turn restriction http://www.openstreetmap.org/browse/relation/1610018 Turn restriction http://www.openstreetmap.org/browse/relation/2556829 Turn restriction http://www.openstreetmap.org/browse/relation/2556828 Turn restriction http://www.openstreetmap.org/browse/relation/1619758 Turn restriction http://www.openstreetmap.org/browse/relation/1619754 Turn restriction http://www.openstreetmap.org/browse/relation/1619760 Turn restriction http://www.openstreetmap.org/browse/relation/1874949 Turn restriction http://www.openstreetmap.org/browse/relation/1471323 Turn restriction http://www.openstreetmap.org/browse/relation/2733411 Turn restriction http://www.openstreetmap.org/browse/relation/1553991 Turn restriction http://www.openstreetmap.org/browse/relation/1553985 Turn restriction http://www.openstreetmap.org/browse/relation/1554001 Turn restriction http://www.openstreetmap.org/browse/relation/3499015 Turn restriction http://www.openstreetmap.org/browse/relation/1874952 Turn restriction http://www.openstreetmap.org/browse/relation/1874950 Turn restriction http://www.openstreetmap.org/browse/relation/3121764 Turn restriction http://www.openstreetmap.org/browse/relation/2512039 Turn restriction http://www.openstreetmap.org/browse/relation/3328204 Turn restriction http://www.openstreetmap.org/browse/relation/3395687 Turn restriction http://www.openstreetmap.org/browse/relation/3395691 Turn restriction http://www.openstreetmap.org/browse/relation/3395685 Turn restriction http://www.openstreetmap.org/browse/relation/3009483 Turn restriction http://www.openstreetmap.org/browse/relation/3009481 Turn restriction http://www.openstreetmap.org/browse/relation/3497275 Turn restriction http://www.openstreetmap.org/browse/relation/2074869 Turn restriction http://www.openstreetmap.org/browse/relation/3103660 Turn restriction http://www.openstreetmap.org/browse/relation/1694535 Turn restriction http://www.openstreetmap.org/browse/relation/1694528 Turn restriction http://www.openstreetmap.org/browse/relation/1694526 Turn restriction http://www.openstreetmap.org/browse/relation/1694533 Turn restriction http://www.openstreetmap.org/browse/relation/3526934 _______________________________________________
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
MapSource.png (7K) <http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png>;
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Carlos, I was not able to reproduce the problem. Please post a link to a tile for that mkgmap produces wrong messages. Gerd
Date: Fri, 21 Feb 2014 22:31:19 +0100 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Wrong turn restriction warnings
El 21/02/14 20:57, GerdP escribió:
Hi Carlos,
you say that you see the message for the turn restriction in mkgmap. Right If one of the ways of relation 1610018 crosses the tile border, splitter will write all members of the relation to both tiles, but it is only usable in the tile that contains the via point. Restrictions are correctly processed when a route is calculated, no problem there. The warning is not reported for the tile that contains the restriction (or the via point), but for the neighbor one. Would it be possible to detect that a restriction is fully contained in given tile and avoid such warnings in the neighbor one? The main concerns are the waste of time trying to fix restrictions reported by mkgmap that are correct in OSM and the bad experience of people who download errors files from my site and faces a list full of false errors, which for sure will dis encourage them to continue working on their fix. Carlos
Gerd
Carlos Dávila-2 wrote
Not sure what you mean. See attached screenshot for relation 1610018. It's placed on the crossing below label "CL-501". Tile border is the vertical gray line on the left, so some 800 meters. overlap=auto
El 21/02/14 19:31, GerdP escribió:
Hi Carlos,
is the via point within the tile border? If not, it should be ignored.
Gerd
Carlos Dávila-2 wrote
Some of the turn restriction warnings reported by mkgmap are correctly mapped in OSM. They all seem to be near tile borders. Shouldn't keep-complete option of splitter take care of these relations? If you want to check some of these relations, here is the list I currently get processing a customized spain.osm.pbf file (I can supply the file if necessary) (max-nodes=2100000): Turn restriction http://www.openstreetmap.org/browse/relation/1610018 Turn restriction http://www.openstreetmap.org/browse/relation/2556829 Turn restriction http://www.openstreetmap.org/browse/relation/2556828 Turn restriction http://www.openstreetmap.org/browse/relation/1619758 Turn restriction http://www.openstreetmap.org/browse/relation/1619754 Turn restriction http://www.openstreetmap.org/browse/relation/1619760 Turn restriction http://www.openstreetmap.org/browse/relation/1874949 Turn restriction http://www.openstreetmap.org/browse/relation/1471323 Turn restriction http://www.openstreetmap.org/browse/relation/2733411 Turn restriction http://www.openstreetmap.org/browse/relation/1553991 Turn restriction http://www.openstreetmap.org/browse/relation/1553985 Turn restriction http://www.openstreetmap.org/browse/relation/1554001 Turn restriction http://www.openstreetmap.org/browse/relation/3499015 Turn restriction http://www.openstreetmap.org/browse/relation/1874952 Turn restriction http://www.openstreetmap.org/browse/relation/1874950 Turn restriction http://www.openstreetmap.org/browse/relation/3121764 Turn restriction http://www.openstreetmap.org/browse/relation/2512039 Turn restriction http://www.openstreetmap.org/browse/relation/3328204 Turn restriction http://www.openstreetmap.org/browse/relation/3395687 Turn restriction http://www.openstreetmap.org/browse/relation/3395691 Turn restriction http://www.openstreetmap.org/browse/relation/3395685 Turn restriction http://www.openstreetmap.org/browse/relation/3009483 Turn restriction http://www.openstreetmap.org/browse/relation/3009481 Turn restriction http://www.openstreetmap.org/browse/relation/3497275 Turn restriction http://www.openstreetmap.org/browse/relation/2074869 Turn restriction http://www.openstreetmap.org/browse/relation/3103660 Turn restriction http://www.openstreetmap.org/browse/relation/1694535 Turn restriction http://www.openstreetmap.org/browse/relation/1694528 Turn restriction http://www.openstreetmap.org/browse/relation/1694526 Turn restriction http://www.openstreetmap.org/browse/relation/1694533 Turn restriction http://www.openstreetmap.org/browse/relation/3526934 _______________________________________________
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
MapSource.png (7K) <http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png>;
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Relation 1610018 is reported to lack "to" way for tile http://mapas.alternativaslibres.es/55114002.img while it is fully contained in tile http://mapas.alternativaslibres.es/55114011.img Source files are available at http://mapas.alternativaslibres.es/55114002.osm.pbf and http://mapas.alternativaslibres.es/55114011.osm.pbf El 22/02/14 08:49, Gerd Petermann escribió:
Hi Carlos,
I was not able to reproduce the problem. Please post a link to a tile for that mkgmap produces wrong messages.
Gerd
Date: Fri, 21 Feb 2014 22:31:19 +0100 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Wrong turn restriction warnings
El 21/02/14 20:57, GerdP escribió:
Hi Carlos,
you say that you see the message for the turn restriction in mkgmap. Right If one of the ways of relation 1610018 crosses the tile border, splitter will write all members of the relation to both tiles, but it is only usable in the tile that contains the via point. Restrictions are correctly processed when a route is calculated, no problem there. The warning is not reported for the tile that contains the restriction (or the via point), but for the neighbor one. Would it be possible to detect that a restriction is fully contained in given tile and avoid such warnings in the neighbor one? The main concerns are the waste of time trying to fix restrictions reported by mkgmap that are correct in OSM and the bad experience of people who download errors files from my site and faces a list full of false errors, which for sure will dis encourage them to continue working on their fix. Carlos
Gerd
Carlos Dávila-2 wrote
Not sure what you mean. See attached screenshot for relation 1610018. It's placed on the crossing below label "CL-501". Tile border is the vertical gray line on the left, so some 800 meters. overlap=auto
El 21/02/14 19:31, GerdP escribió:
Hi Carlos,
is the via point within the tile border? If not, it should be ignored.
Gerd
Carlos Dávila-2 wrote
Some of the turn restriction warnings reported by mkgmap are correctly mapped in OSM. They all seem to be near tile borders. Shouldn't keep-complete option of splitter take care of these relations? If you want to check some of these relations, here is the list I currently get processing a customized spain.osm.pbf file (I can supply the file if necessary) (max-nodes=2100000): Turn restriction http://www.openstreetmap.org/browse/relation/1610018 Turn restriction http://www.openstreetmap.org/browse/relation/2556829 Turn restriction http://www.openstreetmap.org/browse/relation/2556828 Turn restriction http://www.openstreetmap.org/browse/relation/1619758 Turn restriction http://www.openstreetmap.org/browse/relation/1619754 Turn restriction http://www.openstreetmap.org/browse/relation/1619760 Turn restriction http://www.openstreetmap.org/browse/relation/1874949 Turn restriction http://www.openstreetmap.org/browse/relation/1471323 Turn restriction http://www.openstreetmap.org/browse/relation/2733411 Turn restriction http://www.openstreetmap.org/browse/relation/1553991 Turn restriction http://www.openstreetmap.org/browse/relation/1553985 Turn restriction http://www.openstreetmap.org/browse/relation/1554001 Turn restriction http://www.openstreetmap.org/browse/relation/3499015 Turn restriction http://www.openstreetmap.org/browse/relation/1874952 Turn restriction http://www.openstreetmap.org/browse/relation/1874950 Turn restriction http://www.openstreetmap.org/browse/relation/3121764 Turn restriction http://www.openstreetmap.org/browse/relation/2512039 Turn restriction http://www.openstreetmap.org/browse/relation/3328204 Turn restriction http://www.openstreetmap.org/browse/relation/3395687 Turn restriction http://www.openstreetmap.org/browse/relation/3395691 Turn restriction http://www.openstreetmap.org/browse/relation/3395685 Turn restriction http://www.openstreetmap.org/browse/relation/3009483 Turn restriction http://www.openstreetmap.org/browse/relation/3009481 Turn restriction http://www.openstreetmap.org/browse/relation/3497275 Turn restriction http://www.openstreetmap.org/browse/relation/2074869 Turn restriction http://www.openstreetmap.org/browse/relation/3103660 Turn restriction http://www.openstreetmap.org/browse/relation/1694535 Turn restriction http://www.openstreetmap.org/browse/relation/1694528 Turn restriction http://www.openstreetmap.org/browse/relation/1694526 Turn restriction http://www.openstreetmap.org/browse/relation/1694533 Turn restriction http://www.openstreetmap.org/browse/relation/3526934 _______________________________________________
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
MapSource.png (7K)
<http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png>;
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
-- 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 problem seems to be in splitter, as the to-way is really missing in the file 55114002.osm.pbf. I'll try to reproduce that. Please post your splitter log file. Gerd Carlos Dávila-2 wrote
Relation 1610018 is reported to lack "to" way for tile http://mapas.alternativaslibres.es/55114002.img while it is fully contained in tile http://mapas.alternativaslibres.es/55114011.img Source files are available at http://mapas.alternativaslibres.es/55114002.osm.pbf and http://mapas.alternativaslibres.es/55114011.osm.pbf
El 22/02/14 08:49, Gerd Petermann escribió:
Hi Carlos,
I was not able to reproduce the problem. Please post a link to a tile for that mkgmap produces wrong messages.
Gerd
Date: Fri, 21 Feb 2014 22:31:19 +0100 From:
cdavilam@
To:
mkgmap-dev@.org
Subject: Re: [mkgmap-dev] Wrong turn restriction warnings
El 21/02/14 20:57, GerdP escribió:
Hi Carlos,
you say that you see the message for the turn restriction in mkgmap. Right If one of the ways of relation 1610018 crosses the tile border, splitter will write all members of the relation to both tiles, but it is only usable in the tile that contains the via point. Restrictions are correctly processed when a route is calculated, no problem there. The warning is not reported for the tile that contains the restriction (or the via point), but for the neighbor one. Would it be possible to detect that a restriction is fully contained in given tile and avoid such warnings in the neighbor one? The main concerns are the waste of time trying to fix restrictions reported by mkgmap that are correct in OSM and the bad experience of people who download errors files from my site and faces a list full of false errors, which for sure will dis encourage them to continue working on their fix. Carlos
Gerd
Carlos Dávila-2 wrote
Not sure what you mean. See attached screenshot for relation
It's placed on the crossing below label "CL-501". Tile border is the vertical gray line on the left, so some 800 meters. overlap=auto
El 21/02/14 19:31, GerdP escribió:
Hi Carlos,
is the via point within the tile border? If not, it should be ignored.
Gerd
Carlos Dávila-2 wrote > Some of the turn restriction warnings reported by mkgmap are correctly > mapped in OSM. They all seem to be near tile borders. Shouldn't > keep-complete option of splitter take care of these relations? > If you want to check some of these relations, here is the list I > currently get processing a customized spain.osm.pbf file (I can supply > the file if necessary) (max-nodes=2100000): > Turn restriction http://www.openstreetmap.org/browse/relation/1610018 > Turn restriction http://www.openstreetmap.org/browse/relation/2556829 > Turn restriction http://www.openstreetmap.org/browse/relation/2556828 > Turn restriction http://www.openstreetmap.org/browse/relation/1619758 > Turn restriction http://www.openstreetmap.org/browse/relation/1619754 > Turn restriction http://www.openstreetmap.org/browse/relation/1619760 > Turn restriction http://www.openstreetmap.org/browse/relation/1874949 > Turn restriction http://www.openstreetmap.org/browse/relation/1471323 > Turn restriction http://www.openstreetmap.org/browse/relation/2733411 > Turn restriction http://www.openstreetmap.org/browse/relation/1553991 > Turn restriction http://www.openstreetmap.org/browse/relation/1553985 > Turn restriction http://www.openstreetmap.org/browse/relation/1554001 > Turn restriction http://www.openstreetmap.org/browse/relation/3499015 > Turn restriction http://www.openstreetmap.org/browse/relation/1874952 > Turn restriction http://www.openstreetmap.org/browse/relation/1874950 > Turn restriction http://www.openstreetmap.org/browse/relation/3121764 > Turn restriction http://www.openstreetmap.org/browse/relation/2512039 > Turn restriction http://www.openstreetmap.org/browse/relation/3328204 > Turn restriction http://www.openstreetmap.org/browse/relation/3395687 > Turn restriction http://www.openstreetmap.org/browse/relation/3395691 > Turn restriction http://www.openstreetmap.org/browse/relation/3395685 > Turn restriction http://www.openstreetmap.org/browse/relation/3009483 > Turn restriction http://www.openstreetmap.org/browse/relation/3009481 > Turn restriction http://www.openstreetmap.org/browse/relation/3497275 > Turn restriction http://www.openstreetmap.org/browse/relation/2074869 > Turn restriction http://www.openstreetmap.org/browse/relation/3103660 > Turn restriction http://www.openstreetmap.org/browse/relation/1694535 > Turn restriction http://www.openstreetmap.org/browse/relation/1694528 > Turn restriction http://www.openstreetmap.org/browse/relation/1694526 > Turn restriction http://www.openstreetmap.org/browse/relation/1694533 > Turn restriction http://www.openstreetmap.org/browse/relation/3526934 > _______________________________________________ >
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
MapSource.png (7K)
<http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png>;
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
-- 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@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
http://mapas.alternativaslibres.es/splitter.log El 22/02/14 11:33, GerdP escribió:
Hi Carlos,
the problem seems to be in splitter, as the to-way is really missing in the file 55114002.osm.pbf. I'll try to reproduce that. Please post your splitter log file.
Gerd
Carlos Dávila-2 wrote
Relation 1610018 is reported to lack "to" way for tile http://mapas.alternativaslibres.es/55114002.img while it is fully contained in tile http://mapas.alternativaslibres.es/55114011.img Source files are available at http://mapas.alternativaslibres.es/55114002.osm.pbf and http://mapas.alternativaslibres.es/55114011.osm.pbf
El 22/02/14 08:49, Gerd Petermann escribió:
Hi Carlos,
I was not able to reproduce the problem. Please post a link to a tile for that mkgmap produces wrong messages.
Gerd
Date: Fri, 21 Feb 2014 22:31:19 +0100 From: cdavilam@ To: mkgmap-dev@.org Subject: Re: [mkgmap-dev] Wrong turn restriction warnings
El 21/02/14 20:57, GerdP escribió:
Hi Carlos,
you say that you see the message for the turn restriction in mkgmap. Right If one of the ways of relation 1610018 crosses the tile border, splitter will write all members of the relation to both tiles, but it is only usable in the tile that contains the via point. Restrictions are correctly processed when a route is calculated, no problem there. The warning is not reported for the tile that contains the restriction (or the via point), but for the neighbor one. Would it be possible to detect that a restriction is fully contained in given tile and avoid such warnings in the neighbor one? The main concerns are the waste of time trying to fix restrictions reported by mkgmap that are correct in OSM and the bad experience of people who download errors files from my site and faces a list full of false errors, which for sure will dis encourage them to continue working on their fix. Carlos Gerd
Carlos Dávila-2 wrote
Not sure what you mean. See attached screenshot for relation
It's placed on the crossing below label "CL-501". Tile border is the vertical gray line on the left, so some 800 meters. overlap=auto
El 21/02/14 19:31, GerdP escribió: > Hi Carlos, > > is the via point within the tile border? If not, it should be ignored. > Gerd > > > Carlos Dávila-2 wrote >> Some of the turn restriction warnings reported by mkgmap are correctly >> mapped in OSM. They all seem to be near tile borders. Shouldn't >> keep-complete option of splitter take care of these relations? >> If you want to check some of these relations, here is the list I >> currently get processing a customized spain.osm.pbf file (I can supply >> the file if necessary) (max-nodes=2100000): >> Turn restriction http://www.openstreetmap.org/browse/relation/1610018 >> Turn restriction http://www.openstreetmap.org/browse/relation/2556829 >> Turn restriction http://www.openstreetmap.org/browse/relation/2556828 >> Turn restriction http://www.openstreetmap.org/browse/relation/1619758 >> Turn restriction http://www.openstreetmap.org/browse/relation/1619754 >> Turn restriction http://www.openstreetmap.org/browse/relation/1619760 >> Turn restriction http://www.openstreetmap.org/browse/relation/1874949 >> Turn restriction http://www.openstreetmap.org/browse/relation/1471323 >> Turn restriction http://www.openstreetmap.org/browse/relation/2733411 >> Turn restriction http://www.openstreetmap.org/browse/relation/1553991 >> Turn restriction http://www.openstreetmap.org/browse/relation/1553985 >> Turn restriction http://www.openstreetmap.org/browse/relation/1554001 >> Turn restriction http://www.openstreetmap.org/browse/relation/3499015 >> Turn restriction http://www.openstreetmap.org/browse/relation/1874952 >> Turn restriction http://www.openstreetmap.org/browse/relation/1874950 >> Turn restriction http://www.openstreetmap.org/browse/relation/3121764 >> Turn restriction http://www.openstreetmap.org/browse/relation/2512039 >> Turn restriction http://www.openstreetmap.org/browse/relation/3328204 >> Turn restriction http://www.openstreetmap.org/browse/relation/3395687 >> Turn restriction http://www.openstreetmap.org/browse/relation/3395691 >> Turn restriction http://www.openstreetmap.org/browse/relation/3395685 >> Turn restriction http://www.openstreetmap.org/browse/relation/3009483 >> Turn restriction http://www.openstreetmap.org/browse/relation/3009481 >> Turn restriction http://www.openstreetmap.org/browse/relation/3497275 >> Turn restriction http://www.openstreetmap.org/browse/relation/2074869 >> Turn restriction http://www.openstreetmap.org/browse/relation/3103660 >> Turn restriction http://www.openstreetmap.org/browse/relation/1694535 >> Turn restriction http://www.openstreetmap.org/browse/relation/1694528 >> Turn restriction http://www.openstreetmap.org/browse/relation/1694526 >> Turn restriction http://www.openstreetmap.org/browse/relation/1694533 >> Turn restriction http://www.openstreetmap.org/browse/relation/3526934 >> _______________________________________________ >> _______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
MapSource.png (7K)
<http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png>;
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Carlos, thanks for reporting this. I fixed a bug in splitter with r316, see http://www.mkgmap.org.uk/websvn/listing.php?repname=splitter You might still see warnings from mkgmap for lacking ways in restriction relations if you style doesn't assign a routable type for the to-way or from-way. See point 4 in this post: http://gis.19327.n5.nabble.com/Problem-with-turn-restriction-tp5795049p57952... Gerd Carlos Dávila-2 wrote
http://mapas.alternativaslibres.es/splitter.log
El 22/02/14 11:33, GerdP escribió:
Hi Carlos,
the problem seems to be in splitter, as the to-way is really missing in the file 55114002.osm.pbf. I'll try to reproduce that. Please post your splitter log file.
Gerd
Carlos Dávila-2 wrote
Relation 1610018 is reported to lack "to" way for tile http://mapas.alternativaslibres.es/55114002.img while it is fully contained in tile http://mapas.alternativaslibres.es/55114011.img Source files are available at http://mapas.alternativaslibres.es/55114002.osm.pbf and http://mapas.alternativaslibres.es/55114011.osm.pbf
El 22/02/14 08:49, Gerd Petermann escribió:
Hi Carlos,
I was not able to reproduce the problem. Please post a link to a tile for that mkgmap produces wrong messages.
Gerd
Date: Fri, 21 Feb 2014 22:31:19 +0100 From: cdavilam@ To: mkgmap-dev@.org Subject: Re: [mkgmap-dev] Wrong turn restriction warnings
El 21/02/14 20:57, GerdP escribió:
Hi Carlos,
you say that you see the message for the turn restriction in mkgmap. Right If one of the ways of relation 1610018 crosses the tile border, splitter will write all members of the relation to both tiles, but it is only usable in the tile that contains the via point. Restrictions are correctly processed when a route is calculated, no problem there. The warning is not reported for the tile that contains the restriction (or the via point), but for the neighbor one. Would it be possible to detect that a restriction is fully contained in given tile and avoid such warnings in the neighbor one? The main concerns are the waste of time trying to fix restrictions reported by mkgmap that are correct in OSM and the bad experience of people who download errors files from my site and faces a list full of false errors, which for sure will dis encourage them to continue working on their fix. Carlos Gerd
Carlos Dávila-2 wrote > Not sure what you mean. See attached screenshot for relation
> It's placed on the crossing below label "CL-501". Tile border is the > vertical gray line on the left, so some 800 meters. overlap=auto > > El 21/02/14 19:31, GerdP escribió: >> Hi Carlos, >> >> is the via point within the tile border? If not, it should be ignored. >> Gerd >> >> >> Carlos Dávila-2 wrote >>> Some of the turn restriction warnings reported by mkgmap are correctly >>> mapped in OSM. They all seem to be near tile borders. Shouldn't >>> keep-complete option of splitter take care of these relations? >>> If you want to check some of these relations, here is the list I >>> currently get processing a customized spain.osm.pbf file (I can supply >>> the file if necessary) (max-nodes=2100000): >>> Turn restriction http://www.openstreetmap.org/browse/relation/1610018 >>> Turn restriction http://www.openstreetmap.org/browse/relation/2556829 >>> Turn restriction http://www.openstreetmap.org/browse/relation/2556828 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1619758 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1619754 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1619760 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1874949 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1471323 >>> Turn restriction http://www.openstreetmap.org/browse/relation/2733411 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1553991 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1553985 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1554001 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3499015 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1874952 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1874950 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3121764 >>> Turn restriction http://www.openstreetmap.org/browse/relation/2512039 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3328204 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3395687 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3395691 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3395685 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3009483 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3009481 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3497275 >>> Turn restriction http://www.openstreetmap.org/browse/relation/2074869 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3103660 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1694535 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1694528 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1694526 >>> Turn restriction http://www.openstreetmap.org/browse/relation/1694533 >>> Turn restriction http://www.openstreetmap.org/browse/relation/3526934 >>> _______________________________________________ >>> > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev@.org > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > MapSource.png (7K) > <http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png>;
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p579... Sent from the Mkgmap Development mailing list archive at Nabble.com.
El 23/02/14 08:06, GerdP escribió: > Hi Carlos, > > thanks for reporting this. I fixed a bug in splitter with r316, see > http://www.mkgmap.org.uk/websvn/listing.php?repname=splitter Thank you for fixing it. > > You might still see warnings from mkgmap for lacking ways in restriction > relations > if you style doesn't assign a routable type for the to-way or from-way. > See point 4 in this post: > http://gis.19327.n5.nabble.com/Problem-with-turn-restriction-tp5795049p5795209.html I think processing turn restrictions for non routable ways doesn't make much sense. If the problem is that the ways have not tags of incomplete tags, as those mentioned in the post above, it's good to get the warning, so that data can be fixed. > > Gerd > > > Carlos Dávila-2 wrote >> http://mapas.alternativaslibres.es/splitter.log >> >> El 22/02/14 11:33, GerdP escribió: >>> Hi Carlos, >>> >>> the problem seems to be in splitter, as the to-way is really missing in >>> the >>> file >>> 55114002.osm.pbf. I'll try to reproduce that. >>> Please post your splitter log file. >>> >>> Gerd >>> >>> >>> Carlos Dávila-2 wrote >>>> Relation 1610018 is reported to lack "to" way for tile >>>> http://mapas.alternativaslibres.es/55114002.img while it is fully >>>> contained in tile http://mapas.alternativaslibres.es/55114011.img >>>> Source files are available at >>>> http://mapas.alternativaslibres.es/55114002.osm.pbf and >>>> http://mapas.alternativaslibres.es/55114011.osm.pbf >>>> >>>> El 22/02/14 08:49, Gerd Petermann escribió: >>>>> Hi Carlos, >>>>> >>>>> I was not able to reproduce the problem. >>>>> Please post a link to a tile for that mkgmap produces wrong messages. >>>>> >>>>> Gerd >>>>> >>>>>> Date: Fri, 21 Feb 2014 22:31:19 +0100 >>>>>> From: >>>> cdavilam@ >>>>>> To: >>>> mkgmap-dev@.org >>>>>> Subject: Re: [mkgmap-dev] Wrong turn restriction warnings >>>>>> >>>>>> >>>>>> El 21/02/14 20:57, GerdP escribió: >>>>>>> Hi Carlos, >>>>>>> >>>>>>> you say that you see the message for the turn restriction in mkgmap. >>>>>> Right >>>>>>> If one of the ways of relation 1610018 crosses the tile border, >>>>>>> splitter will write all members of the relation to both tiles, but it >>>>>>> is only usable in the tile that contains the via point. >>>>>> Restrictions are correctly processed when a route is calculated, no >>>>>> problem there. The warning is not reported for the tile that contains >>>>>> the restriction (or the via point), but for the neighbor one. Would it >>>>>> be possible to detect that a restriction is fully contained in given >>>>>> tile and avoid such warnings in the neighbor one? >>>>>> The main concerns are the waste of time trying to fix restrictions >>>>>> reported by mkgmap that are correct in OSM and the bad experience of >>>>>> people who download errors files from my site and faces a list full of >>>>>> false errors, which for sure will dis encourage them to continue >>>>> working >>>>>> on their fix. >>>>>> Carlos >>>>>>> Gerd >>>>>>> >>>>>>> >>>>>>> Carlos Dávila-2 wrote >>>>>>>> Not sure what you mean. See attached screenshot for relation >>>>> 1610018. >>>>>>>> It's placed on the crossing below label "CL-501". Tile border is the >>>>>>>> vertical gray line on the left, so some 800 meters. overlap=auto >>>>>>>> >>>>>>>> El 21/02/14 19:31, GerdP escribió: >>>>>>>>> Hi Carlos, >>>>>>>>> >>>>>>>>> is the via point within the tile border? If not, it should be >>>>> ignored. >>>>>>>>> Gerd >>>>>>>>> >>>>>>>>> >>>>>>>>> Carlos Dávila-2 wrote >>>>>>>>>> Some of the turn restriction warnings reported by mkgmap are >>>>> correctly >>>>>>>>>> mapped in OSM. They all seem to be near tile borders. Shouldn't >>>>>>>>>> keep-complete option of splitter take care of these relations? >>>>>>>>>> If you want to check some of these relations, here is the list I >>>>>>>>>> currently get processing a customized spain.osm.pbf file (I can >>>>> supply >>>>>>>>>> the file if necessary) (max-nodes=2100000): >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1610018 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/2556829 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/2556828 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1619758 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1619754 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1619760 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1874949 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1471323 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/2733411 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1553991 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1553985 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1554001 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3499015 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1874952 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1874950 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3121764 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/2512039 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3328204 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3395687 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3395691 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3395685 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3009483 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3009481 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3497275 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/2074869 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3103660 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1694535 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1694528 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1694526 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/1694533 >>>>>>>>>> Turn restriction >>>>> http://www.openstreetmap.org/browse/relation/3526934 >>>>>>>>>> _______________________________________________ >>>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> mkgmap-dev mailing list >>>>>>>> mkgmap-dev@.org >>>>>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >>>>>>>> >>>>>>>> MapSource.png (7K) >>>>>>>> >>>>> <http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> View this message in context: >>>>> http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p5797041.html >>>>>>> Sent from the Mkgmap Development mailing list archive at Nabble.com. >>>>>>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p5797097.html >>> Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, splitter r306 crashes, while r304 does the same task correctly. See log: Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 552 at uk.me.parabola.splitter.SplitProcessor.addToWorkingQueue(SplitProcessor.java:364) at uk.me.parabola.splitter.SplitProcessor.writeRelation(SplitProcessor.java:355) at uk.me.parabola.splitter.SplitProcessor.processRelation(SplitProcessor.java:208) at uk.me.parabola.splitter.BinaryMapParser.parseRelations(BinaryMapParser.java:204) at crosby.binary.BinaryParser.parse(BinaryParser.java:122) at crosby.binary.BinaryParser.handleBlock(BinaryParser.java:68) at crosby.binary.file.FileBlock.process(FileBlock.java:135) at crosby.binary.file.BlockInputStream.process(BlockInputStream.java:34) at uk.me.parabola.splitter.Main.processMap(Main.java:828) at uk.me.parabola.splitter.Main.writeAreas(Main.java:780) at uk.me.parabola.splitter.Main.split(Main.java:284) at uk.me.parabola.splitter.Main.start(Main.java:165) at uk.me.parabola.splitter.Main.main(Main.java:149) -- Best regards, Andrzej
Hi Andrzej, think you meant r316 and r314. arg, forgot to test the splitting of large files which require multiple passes. Fixed with r317. A hint for you: Try to use a higher max-areas value to avoid the multiple passes. See also http://wiki.openstreetmap.org/wiki/Mkgmap/help/splitter#Tuning_for_best_perf... Gerd
Date: Wed, 26 Feb 2014 23:17:47 +0100 From: popej@poczta.onet.pl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Wrong turn restriction warnings
Hi Gerd,
splitter r306 crashes, while r304 does the same task correctly. See log:
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 552 at uk.me.parabola.splitter.SplitProcessor.addToWorkingQueue(SplitProcessor.java:364) at uk.me.parabola.splitter.SplitProcessor.writeRelation(SplitProcessor.java:355) at uk.me.parabola.splitter.SplitProcessor.processRelation(SplitProcessor.java:208) at uk.me.parabola.splitter.BinaryMapParser.parseRelations(BinaryMapParser.java:204) at crosby.binary.BinaryParser.parse(BinaryParser.java:122) at crosby.binary.BinaryParser.handleBlock(BinaryParser.java:68) at crosby.binary.file.FileBlock.process(FileBlock.java:135) at crosby.binary.file.BlockInputStream.process(BlockInputStream.java:34) at uk.me.parabola.splitter.Main.processMap(Main.java:828) at uk.me.parabola.splitter.Main.writeAreas(Main.java:780) at uk.me.parabola.splitter.Main.split(Main.java:284) at uk.me.parabola.splitter.Main.start(Main.java:165) at uk.me.parabola.splitter.Main.main(Main.java:149)
-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd,
think you meant r316 and r314
Yes, sorry for mistake.
Try to use a higher max-areas value to avoid the multiple passes
I tested max-areas at the time, when I had problems with PC crashing and I left this option at default value. Now I have checked, that splitter r317 can process Europe in single pass, thanks for a good advice. -- Best regards, Andrzej
participants (4)
-
Andrzej Popowski -
Carlos Dávila -
Gerd Petermann -
GerdP