enav.com; talk-us@openstreetmap.org
>
>> Subject: Re: [Talk-us] Complex intersection mapping
>>
>> James,
>>
>> Thanks for the feedback. This is of course not good. I will make sure
>> we will be more careful with both the lane counts and the relations
>> not ge
> From: marti...@telenav.com
> Date: Sat, 9 Nov 2013 11:31:55 -0500
> To: rickmastfa...@hotmail.com
> CC: ste...@telenav.com; krist...@telenav.com; robe...@telenav.com;
> chr...@telenav.com; talk-us@openstreetmap.org
> Subject: Re: [Talk-us] Complex intersection mapping
>
t;
>> From: marti...@telenav.com
>> Date: Mon, 14 Oct 2013 11:42:53 -0600
>> To: talk-us@openstreetmap.org
>> CC: ste...@telenav.com; krist...@telenav.com; robe...@telenav.com;
>> chr...@telenav.com
>> Subject: [Talk-us] Complex intersection mapping
>
>&g
PM
To: Martijn van Exel; OSM US Talk
Cc: ste...@telenav.com; krist...@telenav.com; Stack, Robert;
chr...@telenav.com
Subject: Re: [Talk-us] Complex intersection mapping
Martijn (and other telenav workers),
I just happened to see some intersections in my area tweaked today. If
you're going to b
need to
be fixed again. :)
-James (rickmastfan67)
> From: marti...@telenav.com
> Date: Mon, 14 Oct 2013 11:42:53 -0600
> To: talk-us@openstreetmap.org
> CC: ste...@telenav.com; krist...@telenav.com; robe...@telenav.com;
> chr...@telenav.com
> Subject: [Talk-us] Complex intersection mapp
> From: marti...@telenav.com
> Date: Mon, 21 Oct 2013 17:40:11 -0600
> To: nel...@crynwr.com
> CC: talk-us@openstreetmap.org
> Subject: Re: [Talk-us] Complex intersection mapping
>
>
> One followup question I do have is about one of the other examples of
> elaborat
On Tue, Oct 15, 2013 at 10:52 PM, Russ Nelson wrote:
> It *is* incorrect to map in contravention to the description in the
> Wiki.
> It *is* incorrect to map without the wiki containing an explanation of
> how you map.
>
> If there are a dozen different ways to enter a stop sign into OSM, and
> th
Tod Fitch writes:
> People will map as they see fit and, as pointed out elsewhere in
> this thread, it is not possible to "correct" all instances of all
> variations.
It's *not* incorrect to map as you see fit.
It *is* incorrect to map in contravention to the description in the
Wiki.
It *is* in
It would be tagged as described at
http://wiki.openstreetmaps.org/wiki/Tag:highway%3Dtraffic_signals#Tag_all_incoming_ways
Tod
--
Sent from my mobile device. Please excuse my brevity.
Saikrishna Arcot wrote:
>Just to check, in the case of number 3, if a traffic signal was present
>
>at the ab
Just to check, in the case of number 3, if a traffic signal was present
at the above direction, would there have to be two traffic signal for
the up-and-down two-way road?
Saikrishna Arcot
On Tue 15 Oct 2013 03:14:13 PM EDT, Tod Fitch wrote:
> People will map as they see fit and, as pointed out
People will map as they see fit and, as pointed out elsewhere in this thread,
it is not possible to "correct" all instances of all variations.
That said, the wiki is replete with guidance on preferred tagging for various
features so it is not out of line to work toward a preferred method of mapp
I just want to emphasize that there are (at least) two separate but
related issues here:
1) Whether the "before" or "after" style is preferred or more correct,
2) What a routing algorithm (potentially yet-to-be-coded or
now-actually coded) does with either or both.
Regarding 1), it appears
On 2013-10-15 4:12 PM, Martijn van Exel wrote:
I apologize for the confusion around the term 'braiding' - we used
this term internally for a while (and it ended up in some changeset
comments) not realizing that this had a different meaning that traces
back to the TIGER source data.
To me, the "b
Hi Minh -
Thanks for clarifying the more specific cases. I realize that my
example would not cover all the possible permutations. Thank you for
bringing more specific cases to the table. My colleague Kristen also
has some more specific examples I know she intends to share here. Your
specific cases
James Mast wrote:
> After hands down. That's how I do intersections like that with one minor
> difference. If the road on the "right" (as in the example) doesn't have a
> divider, I merge the ways before leaving the intersection so I would have
> 3 traffic light nodes instead of 4.
>
> -James
2013/10/15 Minh Nguyen
> ** Example A **
>
> Ryans Way and Sycamore Grove Ln. meet Fields Ertel Rd. at the same
> intersection. Fields Ertel is undivided. Ryans Way is briefly divided at
> the subdivision entrance, a very common configuration in newer
> subdivisions, but Sycamore Grove is not.
>
On 2013-10-14 10:42 AM, Martijn van Exel wrote:
So what are we talking about? Intersections like this one, where one
or more dual carriageways come together at an at-grade intersection:
https://www.evernote.com/shard/s9/sh/6438c196-bb92-4f66-81dc-9b75186286ba/0e8f07ff527c6a85c0dec426b9b79f1e
On
After hands down. That's how I do intersections like that with one minor
difference. If the road on the "right" (as in the example) doesn't have a
divider, I merge the ways before leaving the intersection so I would have 3
traffic light nodes instead of 4.
-James
Richard Welty wrote:
> On 10/14/13 1:52 PM, Ian Dees wrote:
> >
> >
> >
> > On Mon, Oct 14, 2013 at 12:42 PM, Martijn van Exel
> > mailto:marti...@telenav.com>> wrote:
> >
> > Hi all,
> >
> > Here at Telenav we have been looking at complex intersections
> and we
> > have set about edit
I too prefer the after pattern since it is easier to do, especially when
you are making a road be dual-carriageway by using the "parallel way"
feature in Potlatch 2. Also, it matches the way it is on the ground better.
Since there seems to be unanimous agreement to map intersections this way,
then
I prefer, and always use, the "after" pattern.
/Stellan
On 2013-10-14 7:42 PM, Martijn van Exel wrote:
Hi all,
Here at Telenav we have been looking at complex intersections and we
have set about editing some of these intersections in a way we feel
represents the situation on the ground better
The latter (after) version matches the traffic signal wiki
http://wiki.openstreetmaps.org/wiki/Tag:highway%3Dtraffic_signals#Tag_all_incoming_ways
It makes sense to me and is the way I prefer.
Tod
--
Sent from my mobile device. Please excuse my brevity.
Martijn van Exel wrote:
>Hi all,
>
>He
To expand on the point of having both methods used, starting with the
multiple intersection points method, what if all four intersection
points were under a relation of a group of intersections, and the
number of lanes on each way was marked? That way, routing algorithms
could convert from the
2013/10/14 stevea
> Hi Martijn: one thing "wrong" I do see at this particular intersection
> are extraneous nodes with highway=crossing tags: two extra ones on the
> (northerly) east-west ped-path and one extra one each of the (westerly and
> easterly) north-south ped-paths. A fairly minor err
So what are we talking about? Intersections like this one, where one
or more dual carriageways come together at an at-grade intersection:
https://www.evernote.com/shard/s9/sh/6438c196-bb92-4f66-81dc-9b75186286ba/0e8f07ff527c6a85c0dec426b9b79f1e
One of my colleagues at Telenav has remapped this i
2013/10/14 Martijn van Exel
> So what are we talking about? Intersections like this one, where one
> or more dual carriageways come together at an at-grade intersection:
>
>
> https://www.evernote.com/shard/s9/sh/6438c196-bb92-4f66-81dc-9b75186286ba/0e8f07ff527c6a85c0dec426b9b79f1e
>
>
I think i
On 10/14/13 1:52 PM, Ian Dees wrote:
>
>
>
> On Mon, Oct 14, 2013 at 12:42 PM, Martijn van Exel
> mailto:marti...@telenav.com>> wrote:
>
> Hi all,
>
> Here at Telenav we have been looking at complex intersections and we
> have set about editing some of these intersections in a way we fe
On Mon, Oct 14, 2013 at 12:42 PM, Martijn van Exel wrote:
> Hi all,
>
> Here at Telenav we have been looking at complex intersections and we
> have set about editing some of these intersections in a way we feel
> represents the situation on the ground better than their original
> state, and becaus
Hi all,
Here at Telenav we have been looking at complex intersections and we
have set about editing some of these intersections in a way we feel
represents the situation on the ground better than their original
state, and because of that, works better for us. We have received some
feedback on our
29 matches
Mail list logo