turn restrictions relations are lost when using `--remove-short-arcs`
Reported here: https://github.com/maning/osmphgps/issues/48 Apparently, relation information on turn-restrictions were lost when using `--remove-short-arcs`. Compiling without the `--remove-short-arcs` directive solves the issue. My assumption is that the `remove-short-arcs` directive is processed after routing creation, it seems to be the other way around. Another separate but related issue on turn_restrictions. Does current version of mkgmap support turn_restriction relation where via is a way and not a point? Full args list below for reference: code-page=1252 tdbfile latin1 country-abbr=PHL country-name=PHILIPPINES remove-short-arcs=5 route add-pois-to-areas family-id=639 family-name=OSM_PHIL overview-mapname=40000001 series-name=OSM_PHIL description=OSM Philippines style-file=/home/maning/osm/routable_garmin/git/osmphgps/styles/default generate-sea=polygons,extend-sea-sectors,close-gaps=1000 index adjust-turn-headings check-roundabouts drive-on-right check-roundabout-flares report-dead-ends ignore-maxspeeds link-pois-to-ways location-autofill=0 -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------
On Tue, May 15, 2012 at 10:19:48AM +0800, maning sambale wrote:
Another separate but related issue on turn_restrictions. Does current version of mkgmap support turn_restriction relation where via is a way and not a point?
Mkgmap does parse them, but does not support them. There was some talk maybe a year ago that via ways might be possible to support in the Garmin format. I made the parser modification a couple of years ago. It is not perfect. I think that you could legitimately have a sequence of multiple via ways in the relation (in case the via way needs to be split because of a bus route relation or such). The current parser would complain if there are more than one via way. Marko
Hi. On Tue, May 15, 2012 04:19, maning sambale wrote:
Reported here: https://github.com/maning/osmphgps/issues/48
Apparently, relation information on turn-restrictions were lost when using `--remove-short-arcs`. Compiling without the `--remove-short-arcs` directive solves the issue. My assumption is that the `remove-short-arcs` directive is processed after routing creation, it seems to be the other way around.
I guess this is caused by the quite large minimum arc length of 5 meters. Essentially this means that all points not further away then 5 meters are one point and it would be quite difficult and time consuming to adapt all turn restrictions accordingly. With the default value of 0 (--remove-short-arcs) you should be fine though.
Another separate but related issue on turn_restrictions. Does current version of mkgmap support turn_restriction relation where via is a way and not a point?
AFAIK this is not yet supported. Most probably its still unclear how this would have to be represented within the Garmin format.
Full args list below for reference:
code-page=1252 tdbfile latin1 country-abbr=PHL country-name=PHILIPPINES remove-short-arcs=5 route add-pois-to-areas family-id=639 family-name=OSM_PHIL overview-mapname=40000001 series-name=OSM_PHIL description=OSM Philippines style-file=/home/maning/osm/routable_garmin/git/osmphgps/styles/default generate-sea=polygons,extend-sea-sectors,close-gaps=1000 index adjust-turn-headings check-roundabouts drive-on-right check-roundabout-flares report-dead-ends ignore-maxspeeds link-pois-to-ways location-autofill=0
Regards, Michael
On Tue, May 15, "Michael Günnewig" wrote:
Hi.
On Tue, May 15, 2012 04:19, maning sambale wrote:
Reported here: https://github.com/maning/osmphgps/issues/48
Apparently, relation information on turn-restrictions were lost when using `--remove-short-arcs`. Compiling without the `--remove-short-arcs` directive solves the issue. My assumption is that the `remove-short-arcs` directive is processed after routing creation, it seems to be the other way around.
I guess this is caused by the quite large minimum arc length of 5 meters. Essentially this means that all points not further away then 5 meters are one point and it would be quite difficult and time consuming to adapt all turn restrictions accordingly. With the default value of 0 (--remove-short-arcs) you should be fine though.
I run into the same issue with ignored turn restrictions myself some time ago, but was never able to track that somehow down. I'm using --remove-short-arcs only. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
participants (4)
-
"Michael Günnewig" -
maning sambale -
Marko Mäkelä -
Thorsten Kukuk