
- Interstate-intersections-
- 11-27-2010
![]() Re: Interstate intersections ??
| Howard Lester | 11-27-2010 |
![]() ![]() ![]() Re: Interstate intersections ??
| Howard Lester | 11-27-2010 |
![]() ![]() ![]() ![]() Re: Interstate intersections ??
| Peter H. Coffin | 11-28-2010 |
![]() Re: Interstate intersections ??
| Fred McKenzie | 11-27-2010 |
![]() Re: Interstate intersections ??
| Ed Pawlowski | 11-27-2010 |
![]() Re: Interstate intersections ??
| Thibaud Taudin ... | 11-28-2010 |
![]() ![]() Re: Interstate intersections ??
| Howard Lester | 11-28-2010 |
![]() ![]() ![]() ![]() Re: Interstate intersections ??
| Howard Lester | 11-28-2010 |
![]() ![]() Re: Interstate intersections ??
| Howard Lester | 11-29-2010 |
![]() ![]() ![]() ![]() ![]() Re: Interstate intersections ??
| Gene E. Bloch | 11-29-2010 |
![]() ![]() ![]() ![]() ![]() ![]() Re: Interstate intersections ??
| Howard Lester | 11-29-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Interstate intersections ??
| Howard Lester | 11-30-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Interstate intersections ??
| Gene E. Bloch | 11-30-2010 |
![]() ![]() Re: Interstate intersections ??
| Gene E. Bloch | 11-30-2010 |
![]() ![]() Re: Interstate intersections ??
| Ed Pawlowski | 11-28-2010 |
If you were Registered and logged in, you could reply and use other advanced thread options
265T going from FLA to MA and want to go via I77 , I81 etc rather than
straight up the coast. SO I chose "where to": "intersection" and entered
I77 = bad
i-77 = bad ( 5 minutes of screaming at it didn't help)
YET if I pick a city like Bethel, PA, the directions tell me to " take I-77"
to "I-81 " to "I-78" ..
Can someone PLEASE tell me the correct syntax to use ?
I wanted to go from FL to MA but not via I-95 ( on a Monday) , but up 77 to
81... over to I-84 ...
Yeah 100 miles longer, but driving 80mph to keep up with traffic vs. 'stop
and go' from DC to CT border.
This the route I took but had to keep picking cities along the way because I
couldn't get the syntax for " Interstate intersections". ( As I got close to
the target city it would route me via secondary highways ... so to stay ON
the hwy I had to select another town.
http://tinyurl.com/2ebf78a
straight up the coast. SO I chose "where to": "intersection" and entered
I77 = bad
i-77 = bad ( 5 minutes of screaming at it didn't help)
YET if I pick a city like Bethel, PA, the directions tell me to " take I-77"
to "I-81 " to "I-78" ..
Can someone PLEASE tell me the correct syntax to use ?
I wanted to go from FL to MA but not via I-95 ( on a Monday) , but up 77 to
81... over to I-84 ...
Yeah 100 miles longer, but driving 80mph to keep up with traffic vs. 'stop
and go' from DC to CT border.
This the route I took but had to keep picking cities along the way because I
couldn't get the syntax for " Interstate intersections". ( As I got close to
the target city it would route me via secondary highways ... so to stay ON
the hwy I had to select another town.
http://tinyurl.com/2ebf78a
"- Bobb -" wrote
I find GPS intersection finding as confusing as you. Try entering just the
number, such as 77 and 81. Let it figure out the rest. (This sort of thing
works well when entering numbered streets.)
I find GPS intersection finding as confusing as you. Try entering just the
number, such as 77 and 81. Let it figure out the rest. (This sort of thing
works well when entering numbered streets.)
> "- Bobb -" wrote
>> 265T going from FLA to MA and want to go via I77 , I81 etc rather than
>> straight up the coast. SO I chose "where to": "intersection" and entered
>> I77 = bad
>> i-77 = bad ( 5 minutes of screaming at it didn't help)
>> YET if I pick a city like Bethel, PA, the directions tell me to " take
>> I-77" to "I-81 " to "I-78" ..
>> Can someone PLEASE tell me the correct syntax to use ?
>> straight up the coast. SO I chose "where to": "intersection" and entered
>> I77 = bad
>> i-77 = bad ( 5 minutes of screaming at it didn't help)
>> YET if I pick a city like Bethel, PA, the directions tell me to " take
>> I-77" to "I-81 " to "I-78" ..
>> Can someone PLEASE tell me the correct syntax to use ?
> I find GPS intersection finding as confusing as you. Try entering just the
> number, such as 77 and 81. Let it figure out the rest. (This sort of thing
> works well when entering numbered streets.)
> number, such as 77 and 81. Let it figure out the rest. (This sort of thing
> works well when entering numbered streets.)
I tried that - didn't work
It came back with options for Street, road, avenue etc
Interstate not listed as an option.
"- Bobb -" wrote
Could it be that an interstate highway is never part of an intersection, as
would be 12th Street and Vine? "I'm gonna... stand on the corner -- 12th
street and Vine!"
>> I find GPS intersection finding as confusing as you. Try entering just
>> the number, such as 77 and 81. Let it figure out the rest. (This sort of
>> thing works well when entering numbered streets.)
>> the number, such as 77 and 81. Let it figure out the rest. (This sort of
>> thing works well when entering numbered streets.)
> I tried that - didn't work
> It came back with options for Street, road, avenue etc
> Interstate not listed as an option.
> It came back with options for Street, road, avenue etc
> Interstate not listed as an option.
Could it be that an interstate highway is never part of an intersection, as
would be 12th Street and Vine? "I'm gonna... stand on the corner -- 12th
street and Vine!"
On Sat, 27 Nov 2010 18:34:47 -0500, Howard Lester wrote:
As far as I know, this is the case. Interstates are connected by ramps
on all but the crudest of base maps, not to each other. The best thing
to do in these circumstances is to find a place you'd like to vist
someplace in the general vicinity of the intersection (often within like
15% of the OVERALL difference is good enough, which may be a hundred
miles) and route to (or via if your unit supports vias) it. Then the GPS
will likely pick up the other interstate as the sensible path for the
next leg.
(I also don't really advise trying to route through a point ON the
interstate itself, as there's middling odds that one will end up
actually selecting a frontage road, the wrong ramp, something running
in the opposite direction or other things that will cause completely
idiotic routing, which will then be complained about on the newsgroup
when it's the fault of the user anyway. Just pick a good restaurant
someplace near the intersection and take a nice break. You've probably
been driving too long anyway, right? (; )
--
The pig is nothing but a giant dish which walks while waiting to be
served.
--Grimod de La Reynière
> "- Bobb -" wrote
>>> I find GPS intersection finding as confusing as you. Try entering just
>>> the number, such as 77 and 81. Let it figure out the rest. (This sort of
>>> thing works well when entering numbered streets.)
>>> the number, such as 77 and 81. Let it figure out the rest. (This sort of
>>> thing works well when entering numbered streets.)
>> I tried that - didn't work
>> It came back with options for Street, road, avenue etc
>> Interstate not listed as an option.
>> It came back with options for Street, road, avenue etc
>> Interstate not listed as an option.
> Could it be that an interstate highway is never part of an intersection, as
> would be 12th Street and Vine? "I'm gonna... stand on the corner -- 12th
> street and Vine!"
> would be 12th Street and Vine? "I'm gonna... stand on the corner -- 12th
> street and Vine!"
As far as I know, this is the case. Interstates are connected by ramps
on all but the crudest of base maps, not to each other. The best thing
to do in these circumstances is to find a place you'd like to vist
someplace in the general vicinity of the intersection (often within like
15% of the OVERALL difference is good enough, which may be a hundred
miles) and route to (or via if your unit supports vias) it. Then the GPS
will likely pick up the other interstate as the sensible path for the
next leg.
(I also don't really advise trying to route through a point ON the
interstate itself, as there's middling odds that one will end up
actually selecting a frontage road, the wrong ramp, something running
in the opposite direction or other things that will cause completely
idiotic routing, which will then be complained about on the newsgroup
when it's the fault of the user anyway. Just pick a good restaurant
someplace near the intersection and take a nice break. You've probably
been driving too long anyway, right? (; )
--
The pig is nothing but a giant dish which walks while waiting to be
served.
--Grimod de La Reynière
- Interstate Rest Areas
- Garmin GPS
- 2010-12-05
- food stops along interstate
- Garmin GPS
- 2010-12-01
- Finding intersection of 2 interstates
- Garmin GPS
- 2006-08-27
- Multilane intersections
- Garmin GPS
- 2007-06-29
- Finding highway intersections
- Garmin GPS
- 2006-11-09
- Map Update Time Delay
- Tomtom GPS
- 2010-05-10









> straight up the coast. SO I chose "where to": "intersection" and entered
> I77 = bad
> i-77 = bad ( 5 minutes of screaming at it didn't help)
> YET if I pick a city like Bethel, PA, the directions tell me to " take
> I-77" to "I-81 " to "I-78" ..
> Can someone PLEASE tell me the correct syntax to use ?