logo separator

[mkgmap-dev] question about ignored no_u_turn restriction

From Ben Konrath ben at bagu.org on Mon Jul 6 12:34:12 BST 2015

Just to follow up ... Does anybody know concretely that the Garmin format
cannot handle and u-turn restriction with the same from and two way?

Thanks, Ben

On Sun, Jul 5, 2015 at 9:20 PM, Ben Konrath <ben at bagu.org> wrote:

> Hi Anor,
>
> Thanks for the tip but it seems that your suggestion breaks the OSM rule
> of manipulating the map for specific renderers (the renderer here being
> mkgmap). If the Garmin format truly doesn't support the u-turn restriction
> with the same to and from way at an intersection, we should come up with
> another solution.
>
> Ben
>
> On Sun, Jul 5, 2015 at 4:01 PM, A. Carlos <anorcarlos at hotmail.com> wrote:
>
>>
>>  Ben
>>
>> There I draw two routes, one in each direction, since there is a false
>> median, then with 2-way, it's easy for a restriction
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *_______________________________________________________________________________________________________*
>>
>>  *Anor                                                              Co*
>> *ncórdia SC *
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ------------------------------
>> Date: Sun, 5 Jul 2015 15:53:50 +0200
>> From: ben at bagu.org
>> To: mkgmap-dev at lists.mkgmap.org.uk
>> Subject: Re: [mkgmap-dev] question about ignored no_u_turn restriction
>>
>>
>> Hi Thorsten,
>>
>> Thanks for your reply. This type of restriction is probably a country
>> specific thing. In Ontario Canada, you can make u-turns at intersections
>> (regardless of the road is separation) if there is no sign indicating that
>> you can't make the u-turn. Here's the information directly from the Ontario
>> Ministry of Transportation:
>>
>> http://www.mto.gov.on.ca/english/dandv/driver/handbook/section2.6.11.shtml
>>
>> I realize that the link I sent previously is in the US but I suspect that
>> it's the same policy there which is why the restriction is tagged like it
>> is.
>>
>> Since the tagging seems to be valid, does the Garmin format support this
>> type of restriction? If not then it's probably a good idea to indicate this
>> in the warning message. Maybe the message should also be changed to an info
>> message if there's no problem with the data. Does anybody have other
>> insights?
>>
>> Thanks, Ben
>>
>> On Sun, Jul 5, 2015 at 2:47 PM, Thorsten Kukuk <kukuk at suse.de> wrote:
>>
>> On Sun, Jul 05, Ben Konrath wrote:
>>
>> > Does anybody know why this particular restriction is being ignored?
>>
>> Beside that this particular type of restrictions doesn't make
>> any sense to me, I would guess the GARMIN format does not support it.
>>
>> If the to and from ways are the same, I have never seen a sign forbidding
>> u-turns. Only, if you have two ways, structural seperated. But then I
>> should tag the street that way and the restriction will not be ignored.
>>
>>   Thorsten
>>
>> --
>> Thorsten Kukuk, Senior Architect SLES & Common Code Base
>> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
>> GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB
>> 21284 (AG Nürnberg)
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>>
>>
>> _______________________________________________ mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>> _______________________________________________
>> 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/20150706/d181b1aa/attachment.html>


More information about the mkgmap-dev mailing list