logo separator

[mkgmap-dev] Wrong turn restriction warnings

From Gerd Petermann gpetermann_muenchen at hotmail.com on Sat Feb 22 07:49:10 GMT 2014

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 at orangecorreo.es
> To: mkgmap-dev at 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 at .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.
> 
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140222/0589c044/attachment.html>


More information about the mkgmap-dev mailing list