This is all good information and it should be in OSM. I'm just saying it
doesn't need to be in there twice.
> On Sep 2, 2016, at 3:47 PM, Jack Burke wrote:
>
> Tagging maxspeed is purely for a router. So are turn restrictions
> As for turn:lanes meant for complex
Tagging maxspeed is purely for a router. So are turn restrictions.
As for turn:lanes meant for complex intersectionsthe examples in the
wiki show very simple uses. I can't see anything in it, or the discussion
page, indicating that it is only for complex intersections. Certainly
there is a
On Fri, Sep 2, 2016 at 12:18 PM, David Mease wrote:
> I thing my reservations about this type of tagging is that this may be
> "tagging for the router".
>
On some level, all of it is.
> I still view the turn:lanes scheme as a (probably incomplete) way of
> describing
I thing my reservations about this type of tagging is that this may be "tagging
for the router". I still view the turn:lanes scheme as a (probably incomplete)
way of describing complex intersections. Tagging simple intersections with this
scheme just to get a routing engine to display the
Would love to compare notes on that, but it'll have to be later next week.
If you want to look at what I do for exits, feel free to examine pretty
much all of them on I 75 south of Atlanta, as well as through downtown.
--jack
On Mon, Aug 29, 2016 at 4:25 PM, Paul Johnson
On Mon, Aug 29, 2016 at 2:05 PM, Jack Burke wrote:
> > This exit has no turn lane. There is no staging lane prior to the exit
> where tags could be placed, one should not be created just so that there is
> a place to put tags.
> > This freeway should not be split. You said
I've given it a little minor tag-completion update if anybody wants to
compare notes.
On Mon, Aug 29, 2016 at 11:00 AM, Duane Gearhart wrote:
> FYI - the exit 78 interchange information has been updated. The Mapzen
> directions are calling out the exit as you expected
>
> This exit has no turn lane. There is no staging lane prior to the exit
where tags could be placed, one should not be created just so that there is
a place to put tags.
> This freeway should not be split. You said yourself that the exit is not
part of the freeway itself, so tags should not be
So it sounds like the general consensus is that I should probably be using
"through;right" at places like shown in my original pic, instead of
"none;right", based on the usage rather than the signage (presuming, of
course, my tagging doesn't conflict with a sign, which shouldn't happen
since
Where I live (San Francisco, CA, USA), lane arrows are generally added
for one of two reasons:
1) It isn't obvious what the authorized use of a lane is, when there is
e.g. a right, slight right, and through option with various lanes for
each - especially when there are multiple slight_rights as
On Thu, Aug 25, 2016 at 11:06 PM, David Mease wrote:
> Road markings are both beneficial and useful for navigation. Cities and
> governments have paid a lot of money installing them all over globe
> precisely for these reasons. OSM would be well served to include them
>
On Thu, Aug 25, 2016 at 4:28 PM, Rihards wrote:
> On 2016.08.26. 00:15, Jack Burke wrote:
>
>> Freeway exit tagging
>>
>>
>> I am totally confused.
>>
>> What is the proper method to use turn:lanes to tag freeway lanes
>> approaching an exit, where the exit branches directly
> mapping the road markings seems extremely strange - what if they are very
> faded, when do we map them ? is there a threshold of % of the paint left ?
> what is there are no road markings but there are signs ?
I encouraged MapBox to add some of their workflow information to the
wiki page.[1]
My interpretation:
What is the proper method to use turn:lanes to tag freeway lanes
>> approaching an exit, where the exit branches directly from an edge lane
>> without being part of the freeway itself, but the freeway lanes are not
>> signed with an arrow, such as this one?
>>
On 2016.08.26. 00:15, Jack Burke wrote:
Freeway exit tagging
I am totally confused.
What is the proper method to use turn:lanes to tag freeway lanes
approaching an exit, where the exit branches directly from an edge lane
without being part of the freeway itself, but the freeway lanes are not
Freeway exit tagging
I am totally confused.
What is the proper method to use turn:lanes to tag freeway lanes
approaching an exit, where the exit branches directly from an edge lane
without being part of the freeway itself, but the freeway lanes are not
signed with an arrow, such as this one?
16 matches
Mail list logo