|
Cellular forums Home > Archive > Garmin GPS > June 2007 > Multilane intersections
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Multilane intersections
|
|
| Bruce. 2007-06-26, 10:33 pm |
| There is an intersection near me (in Aurora, IL). To the east is E New
York. To the west is W New York. To the north is N Eola. To the south is
S Eola. Both roads are 4 lane divided roads.
If I ask for the intersection of New York and Eola, I get these 4 choices:
E New York St(E) & N Eola Rd(N)
E New York St(E) & N Eola Rd(S)
N Eola Rd(N) & E New York(W)
N Eola Rd(S) & E New York(W)
If I look at the map for each one, all 4 describe the exact same
intersection.
If I zoom in, I can tell the (x) describes the direction of the lanes. In
other words, (E) means the eastbound lanes and (W) means the west bound
lanes of the same road. The Nuvi treats this intersection as 4
intersections (2 N/S bound lanes with 2 E/W bound lanes) instead of just 1
intersection, and so all 4 are listed in the search results.
Weird.
Bruce.
| |
| Bruce. 2007-06-26, 10:33 pm |
| "Bruce." <noone@nowhere.com> wrote in message
news:ZAigi.53$eY.40@newssvr13.news.prodigy.net...
> There is an intersection near me (in Aurora, IL). To the east is E New
> York. To the west is W New York. To the north is N Eola. To the south
> is S Eola. Both roads are 4 lane divided roads.
Sorry, this part is wrong. There is only E New York and N Eola. The rest
is correct.
Bruce.
| |
| Non Toxic 2007-06-29, 4:33 am |
|
"Bruce." <noone@nowhere.com> wrote in message
news:ZAigi.53$eY.40@newssvr13.news.prodigy.net...
> There is an intersection near me (in Aurora, IL). To the east is E New
> York. To the west is W New York. To the north is N Eola. To the south
> is S Eola. Both roads are 4 lane divided roads.
>
> If I ask for the intersection of New York and Eola, I get these 4 choices:
>
> E New York St(E) & N Eola Rd(N)
> E New York St(E) & N Eola Rd(S)
> N Eola Rd(N) & E New York(W)
> N Eola Rd(S) & E New York(W)
>
> If I look at the map for each one, all 4 describe the exact same
> intersection.
>
> If I zoom in, I can tell the (x) describes the direction of the lanes. In
> other words, (E) means the eastbound lanes and (W) means the west bound
> lanes of the same road. The Nuvi treats this intersection as 4
> intersections (2 N/S bound lanes with 2 E/W bound lanes) instead of just 1
> intersection, and so all 4 are listed in the search results.
>
> Weird.
>
> Bruce.
>
>
If you zoom into that intersection you will see the two East/Westbound lanes
and the two North/Southbound lanes form a square at the intersection. Since
each corner is a separate intersection, they appear separately in the
intersection search.
| |
| Bruce. 2007-06-29, 10:33 am |
| "Non Toxic" <nt@reba.com.au> wrote in message
news:4684af23$0$6743
9$c30e37c6@lon-reader.news.telstra.net...
> If you zoom into that intersection you will see the two East/Westbound
> lanes and the two North/Southbound lanes form a square at the
> intersection. Since each corner is a separate intersection, they appear
> separately in the intersection search.
Understood, but I don't think any driver would consider it to be 4
intersections and so I would much prefer than the Nuvi search feature treat
it as a single intersection instead of filling the search results with
redundant and duplicate entries all pointing to the same feature.
Bruce.
| |
| peter 2007-06-29, 10:33 am |
| On Jun 29, 6:07 am, "Bruce." <n...@nowhere.com> wrote:
> Understood, but I don't think any driver would consider it to be 4
> intersections and so I would much prefer than the Nuvi search feature treat
> it as a single intersection instead of filling the search results with
> redundant and duplicate entries all pointing to the same feature.
Depends on why you're doing the search. If you just want to see where
that intersection is on the map then a single point is enough. But if
you want to place an intermediate via point there for a route then it
would be important to place it on the proper corner to avoid any
backtracking.
| |
|
| Bruce. <noone@nowhere.com> wrote:
>"Non Toxic" <nt@reba.com.au> wrote:
>
>Understood, but I don't think any driver would consider it to be 4
>intersections and so I would much prefer than the Nuvi search feature treat
>it as a single intersection instead of filling the search results with
>redundant and duplicate entries all pointing to the same feature.
When considered as a single location that makes sense. When
considered as junction of four differently named roads (an
East/West and a North/South junction), I can see where having
them as separate entries makes as much or more sense.
I don't know how mapping algorithms work, but I know when I
use online maps I frequently get weird roundabout directions when
using locations like highway intersections because the software
assumes I'm on "the other" roadway. Also, I sometimes enter
road names without the directional modifier, and get a clarification
query, e.g., did I mean North Broadway or South Broadway?
--
Joel Plutchak "They're not people, they're HIPPIES!"
$LASTNAME at VERYWARMmail.com - Eric Cartman
| |
| Bruce. 2007-06-29, 10:33 am |
| "peter" <prathman@comcast.net> wrote in message
news:1183122990.368804.237850@j4g2000prf.googlegroups.com...
> Depends on why you're doing the search. If you just want to see where
> that intersection is on the map then a single point is enough. But if
> you want to place an intermediate via point there for a route then it
> would be important to place it on the proper corner to avoid any
> backtracking.
Yes, I just tried that and confirmed that the gps is not smart enough to
treat the intersection as a single feature for routing purposes. Placing
the via point on the wrong one of the 4 possibilities yields very
undesirable routes.
I wish it was smarter, not just searching, but routing as well.
Bruce.
| |
| Bruce. 2007-06-29, 10:33 am |
| "Joel" <plutchak@see.headers> wrote in message
news:f632s7$hqk$1@ba
dger.ncsa.uiuc.edu...
> I don't know how mapping algorithms work, but I know when I
> use online maps I frequently get weird roundabout directions when
> using locations like highway intersections because the software
> assumes I'm on "the other" roadway. Also, I sometimes enter
> road names without the directional modifier, and get a clarification
> query, e.g., did I mean North Broadway or South Broadway?
When I say go from point A to point B, the gps is generally smart enough to
route using the proper side of the roads and the proper sides of
intersections.
All I'm suggesting it the gps be equally as smart when I set intersection C
as a via point, or display intersection search results.
Bruce.
|
|
|
|
|