An osm contributor who usually downloads the errors files I serve with my maps has reported that since a long time there are no "oneway errors" for the whole Spain, which is certainly estrange. I checked the map generation log and it seems mkgmap is not reporting dead ends. I have tried with a very simple osm file, containing just two oneway residential ways joined like this ---><---- and mkgmap doesn't report anything, neither with --report-dead-ends=1 nor =2 What am I doing wrong?
Hi Carlos, the last big change was in r2944: The check was moved to StyledConverter. I think I tested it then, but maybe something else changed after that. I'll try to reproduce the problem tomorrow. Gerd Carlos Dávila-2 wrote
An osm contributor who usually downloads the errors files I serve with my maps has reported that since a long time there are no "oneway errors" for the whole Spain, which is certainly estrange. I checked the map generation log and it seems mkgmap is not reporting dead ends. I have tried with a very simple osm file, containing just two oneway residential ways joined like this ---><---- and mkgmap doesn't report anything, neither with --report-dead-ends=1 nor =2 What am I doing wrong? _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/report-dead-ends-not-working-tp5802812p580281... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Carlos, I think the check works. Please check how you produce your list. Maybe you have to change the logging properties file or you have to grep for a different string. The check produces a warning message like Oneway road nnn with tags ... comes from nowhere at .. or Oneway road nnn with tags ... goes to nowhere at .. Gerd GerdP wrote
Hi Carlos,
the last big change was in r2944: The check was moved to StyledConverter. I think I tested it then, but maybe something else changed after that. I'll try to reproduce the problem tomorrow.
Gerd Carlos Dávila-2 wrote
An osm contributor who usually downloads the errors files I serve with my maps has reported that since a long time there are no "oneway errors" for the whole Spain, which is certainly estrange. I checked the map generation log and it seems mkgmap is not reporting dead ends. I have tried with a very simple osm file, containing just two oneway residential ways joined like this ---><---- and mkgmap doesn't report anything, neither with --report-dead-ends=1 nor =2 What am I doing wrong? _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/report-dead-ends-not-working-tp5802812p580282... Sent from the Mkgmap Development mailing list archive at Nabble.com.
I think the line in the logging.properties that should affect is uk.me.parabola.mkgmap.osmstyle.StyledConverter.level=SEVERE I have already changed it to INFO, but didn't work. There is no Oneway... line in the log El 09/04/14 22:12, GerdP escribió:
Hi Carlos,
I think the check works. Please check how you produce your list. Maybe you have to change the logging properties file or you have to grep for a different string. The check produces a warning message like Oneway road nnn with tags ... comes from nowhere at .. or Oneway road nnn with tags ... goes to nowhere at ..
Gerd
GerdP wrote
Hi Carlos,
the last big change was in r2944: The check was moved to StyledConverter. I think I tested it then, but maybe something else changed after that. I'll try to reproduce the problem tomorrow.
Gerd Carlos Dávila-2 wrote
An osm contributor who usually downloads the errors files I serve with my maps has reported that since a long time there are no "oneway errors" for the whole Spain, which is certainly estrange. I checked the map generation log and it seems mkgmap is not reporting dead ends. I have tried with a very simple osm file, containing just two oneway residential ways joined like this ---><---- and mkgmap doesn't report anything, neither with --report-dead-ends=1 nor =2 What am I doing wrong?
Hi Carlos, I tested it with these files deadend.osm <http://gis.19327.n5.nabble.com/file/n5802823/deadend.osm> logging.properties <http://gis.19327.n5.nabble.com/file/n5802823/logging.properties> and this command: java -Dlog.config=logging.properties -jar dist\mkgmap.jar --route --report-dead-ends=2 c:\temp\deadend.osm result: mkgmap.log <http://gis.19327.n5.nabble.com/file/n5802823/mkgmap.log> Gerd -- View this message in context: http://gis.19327.n5.nabble.com/report-dead-ends-not-working-tp5802812p580282... Sent from the Mkgmap Development mailing list archive at Nabble.com.
El 09/04/14 22:37, GerdP escribió:
Hi Carlos,
I tested it with these files deadend.osm <http://gis.19327.n5.nabble.com/file/n5802823/deadend.osm> logging.properties <http://gis.19327.n5.nabble.com/file/n5802823/logging.properties>
and this command: java -Dlog.config=logging.properties -jar dist\mkgmap.jar --route --report-dead-ends=2 c:\temp\deadend.osm
result: mkgmap.log <http://gis.19327.n5.nabble.com/file/n5802823/mkgmap.log>
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/report-dead-ends-not-working-tp5802812p580282... 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
Thanks for your files. I'm afraid I have been looking at the wrong mkgmap.log.X file, because now changing StyledConverter level in logging.properties to WARNING did the trick.
participants (2)
-
Carlos Dávila -
GerdP