http://gpstracklog.com/2015/03/gps-leads-bus-on-400-mile-detour.html
Quote from: ArticleHowever, the bus driver accidentally selected the wrong destination on his GPS and ended up driving the opposite direction.
Clearly user-error in the above-case.
If there was any of us on that bus, he would've have gone a kilometer before we just took the wheel ourselves.
Quote from: jeffandnicole on March 12, 2015, 11:37:35 AM
If there was any of us on that bus, he would've have gone a kilometer before we just took the wheel ourselves.
Amen to that.
Quote from: PHLBOS on March 12, 2015, 11:46:24 AM
Quote from: jeffandnicole on March 12, 2015, 11:37:35 AM
If there was any of us on that bus, he would've have gone a kilometer before we just took the wheel ourselves.
Amen to that.
For sure. I sure can't tolerate people going the wrong way.
This topic is old, but the title being plural seems to be an invitation for other stories.
These are screen shots from a Snapchat video. According to the map, this is beside TX 137 north of Ozona. The first two have a text description. This driver was very determined to follow instructions.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.patternsandprinciples.com%2Fotherfiles%2Frs%2Fgps1.jpg&hash=bb31b4a8dc5edddc5b6fb4fefeba28863b0471c7)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.patternsandprinciples.com%2Fotherfiles%2Frs%2Fgps2.jpg&hash=4a90a53aefc2f47ea88129dfe66f28f5980e7297)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.patternsandprinciples.com%2Fotherfiles%2Frs%2Fgps3.jpg&hash=321c57a83b99893f42ac73db837c359bd943f08c)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.patternsandprinciples.com%2Fotherfiles%2Frs%2Fgps4.jpg&hash=ece69d051b49821bd5ef6cb3f53466e86c54218b)
Not really a horror story, but in fall 2015 I was driving to San Antonio. I had booked a Super 8 near the north I-35/410 junction. As I drew nearer the GPS destination, I saw a Super 8 off the frontage road and I said "is that it? well the GPS indicated no" so I kept going further to where my GPS told me to go thinking maybe there was another Super 8 nearby.
There was no Super 8 at the "destination", and the one I saw before was indeed the correct one. Where I got off of I-35 thiinking the hotel was off there was not the nicest part of San Antonio, either, but thank goodness it was only late afternoon.
Never put your GPS on avoid toll roads in the mountains just pay the toll and take the quicker way. About six years ago I was going to North Carolina from Michigan with my dad and a friend of ours. As we're traveling I'm noticing that the GPS is taking us a rather strange way. It took us up in the mountains of West Virginia to avoid the West Virginia Turnpike, after we got to North Carolina I told my dad that the GPS was on avoid toll roads and there was a toll road in West Virginia that it was avoiding. We were on this road that was switch backing all over the place and there was a curve on this road to avoid running into a house you could tell the curve was there just because the house was there as well. I was wondering why it didn't take us on the Ohio Turnpike to I-77 south instead it routed us to take I-75 to Findlay, Ohio then take US-68 and OH-15 to US-23 through Columbus and onto US-33 towards West Virginia then up into the mountains.
About four years ago I was in Texas and I set my GPS to take me to a Walmart. I ended up on a ranch in the middle of nowhere.
I was in Asheville and only used my GPS to let me know the quicker of two routes to a restaurant near the UNC-A campus, and it took me through a hotel parking lot. Now I know US 25 is the better route (and the restaurant sucked anyway).
The Magellan GPS my wife had in 2010 took us through a hospital parking lot in Morgantown, WV, while en route from the SE corner of PA to the Morgantown Courtyard by Marriot. Several weeks later, on the way back from Lake Michigan to Big Rapids, MI, Mr. Magellan took us on a "seasonal road" which was essentially a dirt path through a cornfield.
Quote from: kennyshark on October 15, 2018, 01:07:36 PM
The Magellan GPS my wife had in 2010 took us through a hospital parking lot in Morgantown, WV, while en route from the SE corner of PA to the Morgantown Courtyard by Marriot. Several weeks later, on the way back from Lake Michigan to Big Rapids, MI, Mr. Magellan took us on a "seasonal road" which was essentially a dirt path through a cornfield.
I got on a road like that in the thumb one time about 2-3 years ago. It said it was a seasonal road but I thought it was fine. I ended up going between two cornfields lol. I'm thinking it was somewhere in between Caseville and Port Austin.
Around 2011, my dad and now-stepmom were in Havre de Grace, Maryland to see sights, and then my now-stepmom wanted to see some point of interest in White Hall in Baltimore County. She followed the Mazda CX-9's GPS to I-95 from exit 89 in Harford County to the outer loop of the I-695 Beltway at Rosedale, then hit up I-83 at Timonium and exited at 31, Middletown Road. My dad was pissed: "You went at least half an hour out of our way! Turn off the GPS and get an idea of where you're going!" He showed her how to take MD-155 out of Havre de Grace to MD-22 at Churchville, follow that to Prospect Mill Road (a corner-cutter to MD-543), then 543 north to U.S. 1 south to the very next light at MD-23, then 23 to MD-165 and back to 23 at Jarrettsville, and finally left on White Hall Road into Baltimore County.
The Uber Driver app is forever trying to send me down alleys in Chicago.
Quote from: abefroman329 on October 16, 2018, 09:48:00 AM
The Uber Driver app is forever trying to send me down alleys in Chicago.
Is there a problem with that? If it's faster, legal (turn restrictions, etc.), and takes traffic off the main roads, it's better than a GPS that stays on the main roads.
Quote from: 1 on October 16, 2018, 10:03:35 AM
Quote from: abefroman329 on October 16, 2018, 09:48:00 AM
The Uber Driver app is forever trying to send me down alleys in Chicago.
Is there a problem with that? If it's faster, legal (turn restrictions, etc.), and takes traffic off the main roads, it's better than a GPS that stays on the main roads.
If the alleys in Chicago are anything like those in Philadelphia; potential crime element aside, they're narrow, not always paved & require a much slower speed to pass through.
Quote from: PHLBOS on October 16, 2018, 10:18:39 AMthey're narrow, not always paved & require a much slower speed to pass through.
This, plus they're frequently blocked by vehicles parked illegally and I don't really think they're intended for through traffic.
The closest I have to one of those was trying to find the Atlantic City Airport. It wasn't really a GPS-only situation as the signage was confusing and most of the locals had no idea how to get there or gave conflicting directions, but the GPS constantly led me to a road that wasn't there (or rather dead ended at an obstruction that wasn't shown). I finally made it 15 minutes before the flight was to depart. Lucky for me it's a small airport and there was no line through security, so I made it. That must have been ~10 years ago.
Now when I had to drop off and pick up my parents there last year, I had absolutely no issue finding it, possibly because I work in that general area now. Signage-wise, I think this is the problematic point:
https://www.google.com/maps/@39.4314719,-74.5785217,3a,75y,70.77h,77.81t/data=!3m7!1e1!3m5!1s7qB_nFST6rp3mCeIOvXHBA!2e0!5s20170701T000000!7i13312!8i6656!5m1!1e1
At all other exits off of the circle prior to this there are signs telling you which way the airport is. When you reach this point you don't know whether you missed your turn or not.
Quote from: PHLBOS on October 16, 2018, 10:18:39 AM
Quote from: 1 on October 16, 2018, 10:03:35 AM
Quote from: abefroman329 on October 16, 2018, 09:48:00 AM
The Uber Driver app is forever trying to send me down alleys in Chicago.
Is there a problem with that? If it's faster, legal (turn restrictions, etc.), and takes traffic off the main roads, it's better than a GPS that stays on the main roads.
If the alleys in Chicago are anything like those in Philadelphia; potential crime element aside, they're narrow, not always paved & require a much slower speed to pass through.
A lot of the alleys in Chicago are like that. Better to just stay on the main streets.
One time I was on a Greyhound between Philadelphia and NYC (on my way home to Hartford) and there were plenty of VMS warnings that the NJ Turnpike was closed north of Exit 8 (going back to Exit 6 or so).
What do you think the bus driver did?
Oh right, they stayed on the NJ Turnpike and made us sit in traffic for 90 minutes.
This was about four years ago, no clue how the driver was navigating or if it was GPS related.
Quote from: ipeters61 on October 16, 2018, 12:05:42 PM
One time I was on a Greyhound between Philadelphia and NYC (on my way home to Hartford) and there were plenty of VMS warnings that the NJ Turnpike was closed north of Exit 8 (going back to Exit 6 or so).
What do you think the bus driver did?
Oh right, they stayed on the NJ Turnpike and made us sit in traffic for 90 minutes.
This was about four years ago, no clue how the driver was navigating or if it was GPS related.
One has to wonder whether
that had more to do with either following a strict policy (if Greyhound has one) on not deviating from the main route for
any reason or the fact that the bus driver was completely unfamiliar with the area outside to the Turnpike.
That said, depending on where the incident that triggered the closure was located; the driver
could've used US 130 as an alternate route (to US 1 to I-287 if the Turnpike incident location was further north).
Quote from: jeffandnicole on March 12, 2015, 11:37:35 AM
If there was any of us on that bus, he would've have gone a kilometer before we just took the wheel ourselves.
Are you sure he would have made it a full kilometer? :-D
On a related note, I had some friends who were returning from Rochester to the Toronto area, and decided to take NY 104 home. Unfortunately for them, they got on the freeway headed east, and got nearly to I-81 before they realized they should have headed west! :-D :-D
They were commenting, though, on how scenic and high-quality of a road it was - I wonder what they would have thought had they followed it through Greece and the western suburbs as they intended to. :paranoid:
They never actually did it - they lost so much time that once they got back to Rochester 3 hours later they opted for the Thruway!
Quote from: PHLBOS on October 16, 2018, 12:16:31 PM
Quote from: ipeters61 on October 16, 2018, 12:05:42 PM
One time I was on a Greyhound between Philadelphia and NYC (on my way home to Hartford) and there were plenty of VMS warnings that the NJ Turnpike was closed north of Exit 8 (going back to Exit 6 or so).
What do you think the bus driver did?
Oh right, they stayed on the NJ Turnpike and made us sit in traffic for 90 minutes.
This was about four years ago, no clue how the driver was navigating or if it was GPS related.
One has to wonder whether that had more to do with either following a strict policy (if Greyhound has one) on not deviating from the main route for any reason or the fact that the bus driver was completely unfamiliar with the area outside to the Turnpike.
That said, depending on where the incident that triggered the closure was located; the driver could've used US 130 as an alternate route (to US 1 to I-287 if the Turnpike incident location was further north).
I've had a Greyhound driver shout over his shoulder to ask if anybody knew how to get to the Chicago bus terminal. I've also seen Greyhound buses enter Wichita from the same direction on more than one route. So I'm not so sure there's such a thing as "the main route" for Greyhound drivers to take.
Eureka Springs, AR, has several nonexistent streets that show up on GPS navigation systems. A local told me it's because the streets were surveyed and mapped but never actually constructed. I wasn't sure how much to believe it until my wife and I were walking to a restaurant the next day, and the street I intended to take after looking at Google Maps ... wasn't there. In a place where the ground is flat and the roads are wide, that wouldn't be such a problem. But Eureka Springs is not that kind of place.
Quote from: kphoger on October 16, 2018, 01:04:07 PM
Quote from: PHLBOS on October 16, 2018, 12:16:31 PM
Quote from: ipeters61 on October 16, 2018, 12:05:42 PM
One time I was on a Greyhound between Philadelphia and NYC (on my way home to Hartford) and there were plenty of VMS warnings that the NJ Turnpike was closed north of Exit 8 (going back to Exit 6 or so).
What do you think the bus driver did?
Oh right, they stayed on the NJ Turnpike and made us sit in traffic for 90 minutes.
This was about four years ago, no clue how the driver was navigating or if it was GPS related.
One has to wonder whether that had more to do with either following a strict policy (if Greyhound has one) on not deviating from the main route for any reason or the fact that the bus driver was completely unfamiliar with the area outside to the Turnpike.
That said, depending on where the incident that triggered the closure was located; the driver could've used US 130 as an alternate route (to US 1 to I-287 if the Turnpike incident location was further north).
I've had a Greyhound driver shout over his shoulder to ask if anybody knew how to get to the Chicago bus terminal. I've also seen Greyhound buses enter Wichita from the same direction on more than one route. So I'm not so sure there's such a thing as "the main route" for Greyhound drivers to take.
Now I'm going to talk about Peter Pan (pre-separation from Greyhound): going from Hartford to NYC it seemed like every driver would take a different route, likewise for NYC to Hartford (some would take the Lincoln Tunnel back to the NJ Turnpike to the GW Bridge, some would take local NYC roads up to I-95/I-278, I remember one took the Lincoln Tunnel to NJ-3 to the GS Parkway to the Tappan Zee, etc).
Quote from: PHLBOS on October 16, 2018, 12:16:31 PM
Quote from: ipeters61 on October 16, 2018, 12:05:42 PM
One time I was on a Greyhound between Philadelphia and NYC (on my way home to Hartford) and there were plenty of VMS warnings that the NJ Turnpike was closed north of Exit 8 (going back to Exit 6 or so).
What do you think the bus driver did?
Oh right, they stayed on the NJ Turnpike and made us sit in traffic for 90 minutes.
This was about four years ago, no clue how the driver was navigating or if it was GPS related.
One has to wonder whether that had more to do with either following a strict policy (if Greyhound has one) on not deviating from the main route for any reason or the fact that the bus driver was completely unfamiliar with the area outside to the Turnpike.
That said, depending on where the incident that triggered the closure was located; the driver could've used US 130 as an alternate route (to US 1 to I-287 if the Turnpike incident location was further north).
The Chinatown buses sure didn't have a policy that they had to follow a particular route no matter what. I was also on one that ran out of gas and had to stop at a service area on the Jersey Turnpike for more.
Quote from: ipeters61 on October 16, 2018, 01:43:45 PM
Quote from: kphoger on October 16, 2018, 01:04:07 PM
Quote from: PHLBOS on October 16, 2018, 12:16:31 PM
Quote from: ipeters61 on October 16, 2018, 12:05:42 PM
One time I was on a Greyhound between Philadelphia and NYC (on my way home to Hartford) and there were plenty of VMS warnings that the NJ Turnpike was closed north of Exit 8 (going back to Exit 6 or so).
What do you think the bus driver did?
Oh right, they stayed on the NJ Turnpike and made us sit in traffic for 90 minutes.
This was about four years ago, no clue how the driver was navigating or if it was GPS related.
One has to wonder whether that had more to do with either following a strict policy (if Greyhound has one) on not deviating from the main route for any reason or the fact that the bus driver was completely unfamiliar with the area outside to the Turnpike.
That said, depending on where the incident that triggered the closure was located; the driver could've used US 130 as an alternate route (to US 1 to I-287 if the Turnpike incident location was further north).
I've had a Greyhound driver shout over his shoulder to ask if anybody knew how to get to the Chicago bus terminal. I've also seen Greyhound buses enter Wichita from the same direction on more than one route. So I'm not so sure there's such a thing as "the main route" for Greyhound drivers to take.
Now I'm going to talk about Peter Pan (pre-separation from Greyhound): going from Hartford to NYC it seemed like every driver would take a different route, likewise for NYC to Hartford (some would take the Lincoln Tunnel back to the NJ Turnpike to the GW Bridge, some would take local NYC roads up to I-95/I-278, I remember one took the Lincoln Tunnel to NJ-3 to the GS Parkway to the Tappan Zee, etc).
It was either Megabus or Bolt I took from Boston to NYC (via Hartford), where the driver announced "we're going to do something we've never done before and go via Queens". I don't remember the exact way he accomplished this, presumably Throggs Neck Bridge and Queens Midtown Tunnel, but it worked reasonably well (the destination was Penn Station from where I continued by train into NJ)
Quote from: abefroman329 on October 16, 2018, 01:48:22 PM
Quote from: PHLBOS on October 16, 2018, 12:16:31 PM
Quote from: ipeters61 on October 16, 2018, 12:05:42 PM
One time I was on a Greyhound between Philadelphia and NYC (on my way home to Hartford) and there were plenty of VMS warnings that the NJ Turnpike was closed north of Exit 8 (going back to Exit 6 or so).
What do you think the bus driver did?
Oh right, they stayed on the NJ Turnpike and made us sit in traffic for 90 minutes.
This was about four years ago, no clue how the driver was navigating or if it was GPS related.
One has to wonder whether that had more to do with either following a strict policy (if Greyhound has one) on not deviating from the main route for any reason or the fact that the bus driver was completely unfamiliar with the area outside to the Turnpike.
That said, depending on where the incident that triggered the closure was located; the driver could've used US 130 as an alternate route (to US 1 to I-287 if the Turnpike incident location was further north).
The Chinatown buses sure didn't have a policy that they had to follow a particular route no matter what. I was also on one that ran out of gas and had to stop at a service area on the Jersey Turnpike for more.
To borrow from Frontier Airlines' slogan, those Chinatown busses (didn't the DOT recently & finally shut a few of them down for safety issues/reasons?) are a
whole different animal.
Quote from: kphoger on October 16, 2018, 01:04:07 PMI've had a Greyhound driver shout over his shoulder to ask if anybody knew how to get to the Chicago bus terminal. I've also seen Greyhound buses enter Wichita from the same direction on more than one route. So I'm not so sure there's such a thing as "the main route" for Greyhound drivers to take.
The so-called
main route I was referring to can vary from location to location but in the fore-mentioned Philly-to-NYC example; any
direct, all-highway routing between those two cities involves using a portion of the NJ Turnpike... particularly between Exits 7A (I-195) and 10 (I-287/NJ 440) to accomplish such. That would be considered as the
main route.
Quote from: PHLBOS on October 16, 2018, 03:08:22 PM(didn't the DOT recently & finally shut a few of them down for safety issues/reasons?)
One can only hope.
Quote from: abefroman329 on October 16, 2018, 03:52:28 PM
Quote from: PHLBOS on October 16, 2018, 03:08:22 PM
(didn't the DOT recently & finally shut a few of them down for safety issues/reasons?)
One can only hope.
Fixed your quote string.
I found it maddening to travel between DC and NYC for personal reasons (either pay through the nose to take Amtrak or sit in traffic on a Greyhound bus, only a fool would fly), and with a round trip ticket on Greyhound at around $75 in 2001 dollars versus $35 for a Chinatown bus, it's easy to see the appeal. However, my God did you ever get what you paid for. On the aforementioned trip, the "nonstop" bus stopped in Baltimore and Philly, took an unannounced detour through the New Jersey suburbs, and when we finally arrived in Manhattan three hours late, the passengers who were waiting to board were so agitated, I had to fight my way OFF the bus as they stormed it (I was sitting in the very back row).
I used to ride the bus home from college* my freshman year so I could work on the weekends. From time to time a few of us "regulars" had to tell the driver the route to get to the smaller stops.
* which implies this is a complete deviation from GPS Horror Stories since GPS wasn't even a gleam in any programmer's eye yet.
Quote from: 1 on October 16, 2018, 10:03:35 AM
Quote from: abefroman329 on October 16, 2018, 09:48:00 AM
The Uber Driver app is forever trying to send me down alleys in Chicago.
Is there a problem with that? If it's faster, legal (turn restrictions, etc.), and takes traffic off the main roads, it's better than a GPS that stays on the main roads.
My father did car repairs for a cab company in Boston, and used to pick up fares late at night if they let him. Let's just say before my birth in 1978 I almost didn't exist when my father went down an alley as his fare was setting him up to be robbed. His escape was only possible with a car from that era.
Here's a mass horror story.
https://www.cnn.com/2019/06/26/us/google-maps-detour-colorado-trnd/index.html (https://www.cnn.com/2019/06/26/us/google-maps-detour-colorado-trnd/index.html)
(https://cdn.cnn.com/cnnnext/dam/assets/190626124944-01-colorado-google-maps-drivers-stuck-trnd-exlarge-169.jpg)
Quote from: wxfree on June 26, 2019, 10:45:12 PM
Here's a mass horror story.
https://www.cnn.com/2019/06/26/us/google-maps-detour-colorado-trnd/index.html (https://www.cnn.com/2019/06/26/us/google-maps-detour-colorado-trnd/index.html)
(https://cdn.cnn.com/cnnnext/dam/assets/190626124944-01-colorado-google-maps-drivers-stuck-trnd-exlarge-169.jpg)
I saw this in a TV station's post on Facebook a few minutes ago. That is a lot of people..
Not GPS, but a former co-worker used to tell the story of one of his father's early experiences with mapping software. It was 1985, and they were preparing for a trip from the Boston area to New York City. He plugs in the origin and destination, gets a route and prints out the "step by step" directions, which routed him out of Boston via the Mass Pike, then onto I-86 at Sturbridge (Exit 9). So the family starts out on their journey, get on the Mass Pike, and focuses on looking for I-86. The only problem was that I-86 had been re-designated back to I-84 about six months prior, and all the signs on the Pike had already been changed. "Dad" finally realized something was wrong when they crossed the Connecticut River, at which point he gets off at Exit 4 and asks the toll taker for directions.
I heard something this morning about Google Maps in the Denver area rerouted several vehicles down a dirt road and all the cars ended up getting stuck in mud.
Quote from: Flint1979 on June 27, 2019, 02:46:01 PM
I heard something this morning about Google Maps in the Denver area rerouted several vehicles down a dirt road and all the cars ended up getting stuck in mud.
So... you heard something related to what was literally two posts before yours.
Quote from: roadman on June 27, 2019, 02:35:42 PM
Not GPS, but a former co-worker used to tell the story of one of his father's early experiences with mapping software. It was 1985, and they were preparing for a trip from the Boston area to New York City. He plugs in the origin and destination, gets a route and prints out the "step by step" directions, which routed him out of Boston via the Mass Pike, then onto I-86 at Sturbridge (Exit 9). So the family starts out on their journey, get on the Mass Pike, and focuses on looking for I-86. The only problem was that I-86 had been re-designated back to I-84 about six months prior, and all the signs on the Pike had already been changed. "Dad" finally realized something was wrong when they crossed the Connecticut River, at which point he gets off at Exit 4 and asks the toll taker for directions.
Were there no "Formerly I-86" signs installed on the Mass Pike? I actually had a time where I sent some family members directions from Philly (where they were) to Hartford (where I grew up) and they got confused when I said "take Exit 9 to I-684"...turns out they took Exit 9 immediately after the Tappan Zee Bridge (on the NY Thruway) instead of the Exit 9 in White Plains (on the Cross Westchester Expressway).
Also, your story vaguely reminds me of this video:
https://www.youtube.com/watch?v=jYfFTynCpZo
Quote from: ipeters61 on June 27, 2019, 10:59:11 PM
Quote from: roadman on June 27, 2019, 02:35:42 PM
Not GPS, but a former co-worker used to tell the story of one of his father's early experiences with mapping software. It was 1985, and they were preparing for a trip from the Boston area to New York City. He plugs in the origin and destination, gets a route and prints out the "step by step" directions, which routed him out of Boston via the Mass Pike, then onto I-86 at Sturbridge (Exit 9). So the family starts out on their journey, get on the Mass Pike, and focuses on looking for I-86. The only problem was that I-86 had been re-designated back to I-84 about six months prior, and all the signs on the Pike had already been changed. "Dad" finally realized something was wrong when they crossed the Connecticut River, at which point he gets off at Exit 4 and asks the toll taker for directions.
Were there no "Formerly I-86" signs installed on the Mass Pike? I actually had a time where I sent some family members directions from Philly (where they were) to Hartford (where I grew up) and they got confused when I said "take Exit 9 to I-684"...turns out they took Exit 9 immediately after the Tappan Zee Bridge (on the NY Thruway) instead of the Exit 9 in White Plains (on the Cross Westchester Expressway).
Also, your story vaguely reminds me of this video:
https://www.youtube.com/watch?v=jYfFTynCpZo
There were signs for a bit of a while stating something along the lines of "86 is now 84" for a couple of years.
The lack of common sense strikes again.
https://www.nbc12.com/2022/11/08/bus-driver-following-gps-takes-students-wrong-state/
Not a horror story, but still why you shouldn't 100% rely on a GPS.
On the way back home from Maine last summer, the Google Maps GPS thought the US 1 to I-295 SB ramp near Brunswick doesn't exist. At first, they wanted me to U-turn to stay on US 1 SB (that's what that intersection before the 295 ramps is like), and enter I-295 SB at Freeport. This is when I started smelling Google's bs. After passing that point, they wanted me to get on I-295 NB and take the next exit on NB to get to the SB side. I didn't see any "Road closed" signs for the 295 SB onramp, so just got onto it. Then the GPS spazzed out, rerouting me on various routings (including thinking I'm coming from 295 SB trying to use the loop ramp in that direction for US 1), before finally getting the memo that I'm on the correct ramp movement. The "time remaining" counter also dropped by a couple of minutes from not using their unneeded detours.
Quote from: plain on November 08, 2022, 09:49:25 AM
The lack of common sense strikes again.
https://www.nbc12.com/2022/11/08/bus-driver-following-gps-takes-students-wrong-state/
Too bad one of us wasn't on the bus, we could have tapped the driver and informed them of their error. :D
I always tell co-workers that those GPS things are only as good as the disinterested college interns who did the mapping and data entry. And, I sometimes seriously wonder if a time will come when a federal rule is imposed that would prohibit those things in the driver areas of vehicles that need commercial licenses to be operated on pubic roads.
Mike
Quote from: webny99 on November 08, 2022, 10:42:35 AM
Quote from: plain on November 08, 2022, 09:49:25 AM
The lack of common sense strikes again.
https://www.nbc12.com/2022/11/08/bus-driver-following-gps-takes-students-wrong-state/
Too bad one of us wasn't on the bus, we could have tapped the driver and informed them of their error. :D
It wouldn't surprise me if one of the students tried, and the bus driver ignored them.
Quote from: FrCorySticha on November 08, 2022, 11:08:06 AM
Quote from: webny99 on November 08, 2022, 10:42:35 AM
Quote from: plain on November 08, 2022, 09:49:25 AM
The lack of common sense strikes again.
https://www.nbc12.com/2022/11/08/bus-driver-following-gps-takes-students-wrong-state/
Too bad one of us wasn't on the bus, we could have tapped the driver and informed them of their error. :D
It wouldn't surprise me if one of the students tried, and the bus driver ignored them.
Or maybe the students just went with the flow, thinking they didn't want to go to their first hour class anyway.
Over 40 years ago I was on a Greyhound and the driver asked the passengers where to find the stop in a small town (had to turn off the highway). One of the other "regulars" answered before I could. It's a good thing that was pre-GPS. Who knows where we might have ended up if he was following the computer.
Quote from: GaryV on November 08, 2022, 11:13:24 AM
Over 40 years ago I was on a Greyhound and the driver asked the passengers where to find the stop in a small town (had to turn off the highway). One of the other "regulars" answered before I could. It's a good thing that was pre-GPS. Who knows where we might have ended up if he was following the computer.
Same here, except it was only about 20 years ago, and the driver was asking directions to the downtown Chicago station.
Quote from: webny99 on November 08, 2022, 10:42:35 AM
Quote from: plain on November 08, 2022, 09:49:25 AM
The lack of common sense strikes again.
https://www.nbc12.com/2022/11/08/bus-driver-following-gps-takes-students-wrong-state/
Too bad one of us wasn't on the bus, we could have tapped the driver and informed them of their error. :D
Unless it's a route they need to clinch. :-D
– Umm, driver, ma'am: I believe you just mixed the exit.
– I only have the I-44 Business Route clinched through Springfield in the eastbound direction, so I'm going to get off at Glenstone and then backtrack on Chestnut. That way I'll have it clinched westbound as well.
– But we're supposed to be arriving in four minutes. My wife is waiting for me, and she just texted to say that our toddler just threw up in the car and needs to get home ASAP.
– Don't worry, it'll only be a few extra minutes.
Side note: Huh, apparently Greyhound moved locations in Springfield last year. The station on Kearney was pretty nice, and it was fairly new too, but apparently Greyhound just didn't want to spend the money to keep it open. I'm kind of sad, personally, because that's the first place I ever saw my wife in person (we met online).
I've only had one epic GPS fail, but it only caused some minor aggravation, not a major issue.
Several years ago I had discovered and located my great-grandmother's grave in Lincoln County, WV. It's in a very rural area with no cell service, so I couldn't call up Google Maps for an aerial view of the roads, so I ended up using my Garmin with preloaded maps to try to navigate me out of that remote location and toward WV 3. It routed me along routes that I later verified are indeed on the map as "fractional" county routes, but the quality of one such route began deteriorating to the point that I was afraid my vehicle wouldn't make it out to the state highway. It was a very narrow gravel route that quickly became unimproved and forded a couple of creeks. I finally turned around and made that Garmin throw a "recalculating" fit until it realized I didn't want to go along that road. I got back to the paved road and continued along it until I came to a route that was fully striped with a center and edge lines. Turns out it was a whole number county route and it led me out to WV 3.
I was tracking the route on a couple of apps, and when I overlaid those tracks along available maps, I found that that those routes are, indeed, in WVDOH's system as county routes.
Here's a personal story that relates to this perfectly.
At the end of eighth grade, (if a student had raised enough money through fundraisers) they could go on a trip to Washington DC. I went on that trip, and the boneheadedness of relying solely on GPS quickly set in. First of all, the bus driver got from Cattaraugus to Salamanca... by going through Ellicottville. (In case you don't know, it is much faster to go through Little Valley). Then I thought, once on Route 17, "Oh, all is well, we will follow a somewhat normal routing now". I couldn't have been more wrong.
The driver took Exit 26 and drove right through Downtown Olean. (I can't imagine those tiny roundabouts were easy to navigate in a giant bus!). Then, south of Olean, turns down Cattaraugus County Road 29, crossing into PA. The driver then made umpteen turns, traversing the towns of Eldred, Port Allegany, Roulette, etc. I actually stopped paying attention at this point because the route was so miserably bad.
About 20 minutes later, I start looking around again, and saw we were in a forest. A few minutes later, the bus stops. We all wonder why. Apparently, the engine overheated and some belt broke, all because the driver was taking the giant bus up steep hills in the middle of a forest. (In case you are wondering, the road was PA 44 and this was in the depths of the Susquehanna Forest.) So we were all stranded in the middle of a forest. No cellphone service, and the nearest town was 20 miles away. We got out of the bus, and were all stranded for five and a half hours! By that time, mechanics came to fix the belt of the bus, a process that took about ten minutes.
Yet another story to prove you should never rely solely on GPS.
Quote from: mgk920 on November 08, 2022, 11:05:28 AMI sometimes seriously wonder if a time will come when a federal rule is imposed that would prohibit those things in the driver areas of vehicles that need commercial licenses to be operated on pubic roads.
Pubic road? eeewwwww.
I believe that the commercial GPS navigation units have additional map data to account for the vehicle/load weight, truck size, and problem curves that would not be an concern to automotive navigation. Of course, that type of unit costs over $300 (https://amzn.to/3twQh8N) while the Google Maps or Apple Maps is
FREE.
We had a 2009 Magellan GPS that took us thru some interesting areas in 2010:
The first was in Morgantown, WV. Our GPS took us thru the parking area of WVU's hospital.
Then on Labor Day weekend, somewhere in west-central Michigan, driving back to Big Rapids from Lake Michigan, we got directed onto a "seasonal road" (read: right on a path going thru a cornfield, something right out of "Twister).
Quote from: GaryV on November 08, 2022, 11:13:24 AM
Quote from: FrCorySticha on November 08, 2022, 11:08:06 AM
Quote from: webny99 on November 08, 2022, 10:42:35 AM
Quote from: plain on November 08, 2022, 09:49:25 AM
The lack of common sense strikes again.
https://www.nbc12.com/2022/11/08/bus-driver-following-gps-takes-students-wrong-state/
Too bad one of us wasn't on the bus, we could have tapped the driver and informed them of their error. :D
It wouldn't surprise me if one of the students tried, and the bus driver ignored them.
Or maybe the students just went with the flow, thinking they didn't want to go to their first hour class anyway.
It said in the article that several of the students were upset enough they were texting their parents about it. At least one parent intercepted the bus and demanded their child be let off, and the bus driver's response was to call the cops. Only when the
cops told the driver they were going to the wrong place did they turn around.
So I have no doubt that someone told the bus driver they were going the wrong way. And I'm guessing the driver just refused to believe that anyone else could possibly know where they were going better than the GPS did.
Quote from: Scott5114 on November 08, 2022, 05:46:47 PM
Quote from: GaryV on November 08, 2022, 11:13:24 AM
Quote from: FrCorySticha on November 08, 2022, 11:08:06 AM
Quote from: webny99 on November 08, 2022, 10:42:35 AM
Quote from: plain on November 08, 2022, 09:49:25 AM
The lack of common sense strikes again.
https://www.nbc12.com/2022/11/08/bus-driver-following-gps-takes-students-wrong-state/
Too bad one of us wasn't on the bus, we could have tapped the driver and informed them of their error. :D
It wouldn't surprise me if one of the students tried, and the bus driver ignored them.
Or maybe the students just went with the flow, thinking they didn't want to go to their first hour class anyway.
It said in the article that several of the students were upset enough they were texting their parents about it. At least one parent intercepted the bus and demanded their child be let off, and the bus driver's response was to call the cops. Only when the cops told the driver they were going to the wrong place did they turn around.
So I have no doubt that someone told the bus driver they were going the wrong way. And I'm guessing the driver just refused to believe that anyone else could possibly know where they were going better than the GPS did.
My thought was that while someone might have said "I think you're going the wrong way", a roadgeek may have figured out
why they were going the wrong way and said "We just entered Connecticut - I think you might be headed to the wrong Academy Avenue".
Then again, as others have said, you might as well take a chance to miss class and clinch some new roads instead, so why say anything? :biggrin:
Only in Rhode Island... A school bus driver took her students across the state line–on the other side of the state from the school's location–so one parent decided to just drive over there and speak with the driver.
Also, I found it interesting that, even though the bus was in Connecticut, a local officer from Scituate, RI, responded.
Quote from: kphoger on November 08, 2022, 06:11:16 PM
Only in Rhode Island... A school bus driver took her students across the state line–on the other side of the state from the school's location–so one parent decided to just drive over there and speak with the driver.
Also, I found it interesting that, even though the bus was in Connecticut, a local officer from Scituate, RI, responded.
Guess he was Scituated at the right place at the right time.
(sorry, couldn't resist)
Quote from: kennyshark64 on November 08, 2022, 04:07:51 PM
We had a 2009 Magellan GPS that took us thru some interesting areas in 2010:
The first was in Morgantown, WV. Our GPS took us thru the parking area of WVU's hospital.
Honestly, that's not a bad routing. It's common for locals to take the street that runs through the parking lot because it avoids a series of traffic lights along WV 705.
One time when I was younger, we were taking a vacation to Acadia in Maine, and we were trying to drive from our hotel in Ellsworth to a certain lobster pound on Mt. Desert Island. The thing is, though, we kept taking Route 1/3 south instead of Route 3 north, the right way towards Acadia and Mt. Desert Island. We somehow managed to drive all the way to Penobscot Narrows before the GPS said that we had arrived at our destination, despite there being no lobster pound there.
Below is an incident with tragic consequences that occurred in the Syracuse, New York area in 2010:
Megabus driver was using personal GPS in crash that killed four on Onondaga Lake Parkway (https://www.syracuse.com/news/2010/09/megabus_driver_suspended_witho.html)
Quote from: jmp367 on November 13, 2022, 09:36:05 AM
Below is an incident with tragic consequences that occurred in the Syracuse, New York area in 2010:
Megabus driver was using personal GPS in crash that killed four on Onondaga Lake Parkway (https://www.syracuse.com/news/2010/09/megabus_driver_suspended_witho.html)
The dreaded Onondaga Lake Parkway rail bridge wins again!
Then there are times when someone really should have trusted his GPS.
Back in 2013, a Boeing Dreamlifter (https://en.wikipedia.org/wiki/Boeing_Dreamlifter), operated by Atlas Air Cargo, was bound from JFK in New York to McConnell AFB here in Wichita. Before takeoff from New York, the captain entered McConnell runway 19L into the navigation system. As the aircraft later approached Wichita, McConnell AFB cleared the aircraft for landing while the Dreamlifter was about 12 miles out. The pilot and co-pilot then saw a lit runway in front of them, in the orientation they expected to see. The runway seemed easier to locate and came up faster than they expected (this was the captain's fourth landing at McConnell), but there it was, so the captain turned off the navigation system and began a steeper-than-planned manual descent–without verifying their location first. Shortly after the plane touched down, McConnell contacted the crew and advised them to "check wheels down"–upon which they replied that they were not, in fact, on approach anymore (and began to suspect something was, umm, rather amiss).
Oops. The runway they saw was actually Jabara, a small executive airport whose runway is half the length of McConnell's. The pilots realized they'd landed at the wrong airport but assumed they'd touched down at the nearby Beech factory instead. Their confusion was due in part to the fact that McConnell hadn't even appeared on the navigation system when the captain turned it off, because it was set for only a 5-mile range and they hadn't reached the 5-mile point yet.
Once everyone figured out what had happened, there was the big, looming question: was the runway even long enough for the plane to take off again? Egad! Maybe..? Hopefully! It's generally recommended that a 747 have a 9199-foot runway, and this one was only 6101 feet long. And at the bottom end of the runway was the K-96 freeway.
So they backed the plane up as far as they could, past the top end of the runway, with the wheels completely off the pavement. Then they closed off area roads, including K-96, just in case it didn't make it off the ground in time. And then, a little after 1 AM, it took off, successfully cleared the end of the runway, and landed at McConnell AFB 19 minutes later.
Investigations began.
Quote from: kphoger on November 14, 2022, 01:42:39 PM
Then there are times when someone really should have trusted his GPS.
Back in 2013, a Boeing Dreamlifter (https://en.wikipedia.org/wiki/Boeing_Dreamlifter), operated by Atlas Air Cargo, was bound from JFK in New York to McConnell AFB here in Wichita. Before takeoff from New York, the captain entered McConnell runway 19L into the navigation system. As the aircraft later approached Wichita, McConnell AFB cleared the aircraft for landing while the Dreamlifter was about 12 miles out. The pilot and co-pilot then saw a lit runway in front of them, in the orientation they expected to see. The runway seemed easier to locate and came up faster than they expected (this was the captain's fourth landing at McConnell), but there it was, so the captain turned off the navigation system and began a steeper-than-planned manual descent–without verifying their location first. Shortly after the plane touched down, McConnell contacted the crew and advised them to "check wheels down"–upon which they replied that they were not, in fact, on approach anymore (and began to suspect something was, umm, rather amiss).
Oops. The runway they saw was actually Jabara, a small executive airport whose runway is half the length of McConnell's. The pilots realized they'd landed at the wrong airport but assumed they'd touched down at the nearby Beech factory instead. Their confusion was due in part to the fact that McConnell hadn't even appeared on the navigation system when the captain turned it off, because it was set for only a 5-mile range and they hadn't reached the 5-mile point yet.
Once everyone figured out what had happened, there was the big, looming question: was the runway even long enough for the plane to take off again? Egad! Maybe..? Hopefully! It's generally recommended that a 747 have a 9199-foot runway, and this one was only 6101 feet long. And at the bottom end of the runway was the K-96 freeway.
So they backed the plane up as far as they could, past the top end of the runway, with the wheels completely off the pavement. Then they closed off area roads, including K-96, just in case it didn't make it off the ground in time. And then, a little after 1 AM, it took off, successfully cleared the end of the runway, and landed at McConnell AFB 19 minutes later.
Investigations began.
Sounds like egregious pilot error, unless their GPS/charts were incorrect.
Quote from: kphoger on November 14, 2022, 01:42:39 PM
Then there are times when someone really should have trusted his GPS.
Back in 2013, a Boeing Dreamlifter (https://en.wikipedia.org/wiki/Boeing_Dreamlifter), operated by Atlas Air Cargo, was bound from JFK in New York to McConnell AFB here in Wichita. Before takeoff from New York, the captain entered McConnell runway 19L into the navigation system. As the aircraft later approached Wichita, McConnell AFB cleared the aircraft for landing while the Dreamlifter was about 12 miles out. The pilot and co-pilot then saw a lit runway in front of them, in the orientation they expected to see. The runway seemed easier to locate and came up faster than they expected (this was the captain's fourth landing at McConnell), but there it was, so the captain turned off the navigation system and began a steeper-than-planned manual descent–without verifying their location first. Shortly after the plane touched down, McConnell contacted the crew and advised them to "check wheels down"–upon which they replied that they were not, in fact, on approach anymore (and began to suspect something was, umm, rather amiss).
Oops. The runway they saw was actually Jabara, a small executive airport whose runway is half the length of McConnell's. The pilots realized they'd landed at the wrong airport but assumed they'd touched down at the nearby Beech factory instead. Their confusion was due in part to the fact that McConnell hadn't even appeared on the navigation system when the captain turned it off, because it was set for only a 5-mile range and they hadn't reached the 5-mile point yet.
Once everyone figured out what had happened, there was the big, looming question: was the runway even long enough for the plane to take off again? Egad! Maybe..? Hopefully! It's generally recommended that a 747 have a 9199-foot runway, and this one was only 6101 feet long. And at the bottom end of the runway was the K-96 freeway.
So they backed the plane up as far as they could, past the top end of the runway, with the wheels completely off the pavement. Then they closed off area roads, including K-96, just in case it didn't make it off the ground in time. And then, a little after 1 AM, it took off, successfully cleared the end of the runway, and landed at McConnell AFB 19 minutes later.
Investigations began.
Quote from: Rothman on November 14, 2022, 02:00:54 PM
Sounds like egregious pilot error, unless their GPS/charts were incorrect.
Yes. Note the very first sentence in my post.
Quote from: kphoger on November 14, 2022, 03:24:36 PM
Quote from: kphoger on November 14, 2022, 01:42:39 PM
Then there are times when someone really should have trusted his GPS.
Back in 2013, a Boeing Dreamlifter (https://en.wikipedia.org/wiki/Boeing_Dreamlifter), operated by Atlas Air Cargo, was bound from JFK in New York to McConnell AFB here in Wichita. Before takeoff from New York, the captain entered McConnell runway 19L into the navigation system. As the aircraft later approached Wichita, McConnell AFB cleared the aircraft for landing while the Dreamlifter was about 12 miles out. The pilot and co-pilot then saw a lit runway in front of them, in the orientation they expected to see. The runway seemed easier to locate and came up faster than they expected (this was the captain's fourth landing at McConnell), but there it was, so the captain turned off the navigation system and began a steeper-than-planned manual descent–without verifying their location first. Shortly after the plane touched down, McConnell contacted the crew and advised them to "check wheels down"–upon which they replied that they were not, in fact, on approach anymore (and began to suspect something was, umm, rather amiss).
Oops. The runway they saw was actually Jabara, a small executive airport whose runway is half the length of McConnell's. The pilots realized they'd landed at the wrong airport but assumed they'd touched down at the nearby Beech factory instead. Their confusion was due in part to the fact that McConnell hadn't even appeared on the navigation system when the captain turned it off, because it was set for only a 5-mile range and they hadn't reached the 5-mile point yet.
Once everyone figured out what had happened, there was the big, looming question: was the runway even long enough for the plane to take off again? Egad! Maybe..? Hopefully! It's generally recommended that a 747 have a 9199-foot runway, and this one was only 6101 feet long. And at the bottom end of the runway was the K-96 freeway.
So they backed the plane up as far as they could, past the top end of the runway, with the wheels completely off the pavement. Then they closed off area roads, including K-96, just in case it didn't make it off the ground in time. And then, a little after 1 AM, it took off, successfully cleared the end of the runway, and landed at McConnell AFB 19 minutes later.
Investigations began.
Quote from: Rothman on November 14, 2022, 02:00:54 PM
Sounds like egregious pilot error, unless their GPS/charts were incorrect.
Yes. Note the very first sentence in my post.
I will not until you note the last half of mine.
Quote from: kirbykart on November 08, 2022, 02:54:30 PM
Here's a personal story that relates to this perfectly.
At the end of eighth grade, (if a student had raised enough money through fundraisers) they could go on a trip to Washington DC. I went on that trip, and the boneheadedness of relying solely on GPS quickly set in. First of all, the bus driver got from Cattaraugus to Salamanca... by going through Ellicottville. (In case you don't know, it is much faster to go through Little Valley). Then I thought, once on Route 17, "Oh, all is well, we will follow a somewhat normal routing now". I couldn't have been more wrong.
The driver took Exit 26 and drove right through Downtown Olean. (I can't imagine those tiny roundabouts were easy to navigate in a giant bus!). Then, south of Olean, turns down Cattaraugus County Road 29, crossing into PA. The driver then made umpteen turns, traversing the towns of Eldred, Port Allegany, Roulette, etc. I actually stopped paying attention at this point because the route was so miserably bad.
About 20 minutes later, I start looking around again, and saw we were in a forest. A few minutes later, the bus stops. We all wonder why. Apparently, the engine overheated and some belt broke, all because the driver was taking the giant bus up steep hills in the middle of a forest. (In case you are wondering, the road was PA 44 and this was in the depths of the Susquehanna Forest.) So we were all stranded in the middle of a forest. No cellphone service, and the nearest town was 20 miles away. We got out of the bus, and were all stranded for five and a half hours! By that time, mechanics came to fix the belt of the bus, a process that took about ten minutes.
Yet another story to prove you should never rely solely on GPS.
Wow! Did you make it to DC eventually?
WSDOT shifted a few miles of I-90 for a multi-year construction project near Snoqualmie Pass, so Apple Maps decided to reroute drivers onto a remote, unpaved forest road that would have become impassible after the first snow. Don't trust your GPS, especially if it's as awful as Apple Maps.
https://www.seattletimes.com/seattle-news/transportation/apple-maps-is-redirecting-drivers-off-i-90-onto-a-dirt-road/
Quote from: KCRoadFan on November 14, 2022, 06:53:19 PM
Quote from: kirbykart on November 08, 2022, 02:54:30 PM
Here's a personal story that relates to this perfectly.
At the end of eighth grade, (if a student had raised enough money through fundraisers) they could go on a trip to Washington DC. I went on that trip, and the boneheadedness of relying solely on GPS quickly set in. First of all, the bus driver got from Cattaraugus to Salamanca... by going through Ellicottville. (In case you don't know, it is much faster to go through Little Valley). Then I thought, once on Route 17, "Oh, all is well, we will follow a somewhat normal routing now". I couldn't have been more wrong.
The driver took Exit 26 and drove right through Downtown Olean. (I can't imagine those tiny roundabouts were easy to navigate in a giant bus!). Then, south of Olean, turns down Cattaraugus County Road 29, crossing into PA. The driver then made umpteen turns, traversing the towns of Eldred, Port Allegany, Roulette, etc. I actually stopped paying attention at this point because the route was so miserably bad.
About 20 minutes later, I start looking around again, and saw we were in a forest. A few minutes later, the bus stops. We all wonder why. Apparently, the engine overheated and some belt broke, all because the driver was taking the giant bus up steep hills in the middle of a forest. (In case you are wondering, the road was PA 44 and this was in the depths of the Susquehanna Forest.) So we were all stranded in the middle of a forest. No cellphone service, and the nearest town was 20 miles away. We got out of the bus, and were all stranded for five and a half hours! By that time, mechanics came to fix the belt of the bus, a process that took about ten minutes.
Yet another story to prove you should never rely solely on GPS.
Wow! Did you make it to DC eventually?
Yes, and we had a great time. But it was really quite the experience!
I once was on a bus trip returning from the NYC/Newark area, and when we got past Syracuse, the driver continued to follow NY 690 instead of exiting at the Thruway. We exited at NY 370 instead, followed NY 370 to NY 34, and then took NY 34 south to the Thruway to get on one exit further west. At that point, it would have been quicker to just stay on NY 370 and take NY 104 back into Rochester. It was night time and I remember it quite vividly - the only thing I don't remember is if the Thruway exit from I-690 was closed, or if the driver took an alternate route for some other unknown reason.
Quote from: kirbykart on November 14, 2022, 07:55:49 PM
Quote from: KCRoadFan on November 14, 2022, 06:53:19 PM
Quote from: kirbykart on November 08, 2022, 02:54:30 PM
Here's a personal story that relates to this perfectly.
...
About 20 minutes later, I start looking around again, and saw we were in a forest. A few minutes later, the bus stops. We all wonder why. Apparently, the engine overheated and some belt broke, all because the driver was taking the giant bus up steep hills in the middle of a forest. (In case you are wondering, the road was PA 44 and this was in the depths of the Susquehanna Forest.) So we were all stranded in the middle of a forest. No cellphone service, and the nearest town was 20 miles away. We got out of the bus, and were all stranded for five and a half hours! By that time, mechanics came to fix the belt of the bus, a process that took about ten minutes.
Yet another story to prove you should never rely solely on GPS.
Wow! Did you make it to DC eventually?
Yes, and we had a great time. But it was really quite the experience!
I can't help but wonder if the bus driver was following some sort of "fuel efficient" or shorter-mileage route. PA 44 could have been a shortcut to the US 15 corridor, but that would make more sense for the Baltimore area than DC. Near as I can tell, US 219 would still be shorter and faster for DC.
^I don't know. We did end up using US 15 down, but we should have just gone to Corning and followed it the whole way. Maybe PA 44 was technically shorter distance, but all those windy mountain roads couldn't have made it shorter time-wise.
Quote from: webny99 on November 14, 2022, 09:15:58 PM
the only thing I don't remember is if the Thruway exit from I-690 was closed, or if the driver took an alternate route for some other unknown reason.
Route clinching.
Quote from: kphoger on November 15, 2022, 09:25:26 AM
Quote from: webny99 on November 14, 2022, 09:15:58 PM
the only thing I don't remember is if the Thruway exit from I-690 was closed, or if the driver took an alternate route for some other unknown reason.
Route clinching.
Except that
no routes were clinched (https://www.google.com/maps/dir/43.1121392,-76.280399/43.0610852,-76.5660628/@43.0879719,-76.5307391,10.88z/data=!4m14!4m13!1m10!3m4!1m2!1d-76.4665781!2d43.1604551!3s0x89d75875f1a4438b:0xa93eb9fc178480ff!3m4!1m2!1d-76.5703295!2d43.157671!3s0x89d75a0d39640bdf:0xb42b7fb6a14eca82!1m0!3e0). We were already at the western terminus of I-690, exited before the end of NY 690, and traveled only partial segments of NY 370 and NY 34.
Quote from: webny99 on November 16, 2022, 12:56:09 PM
Quote from: kphoger on November 15, 2022, 09:25:26 AM
Quote from: webny99 on November 14, 2022, 09:15:58 PM
the only thing I don't remember is if the Thruway exit from I-690 was closed, or if the driver took an alternate route for some other unknown reason.
Route clinching.
Except that no routes were clinched (https://www.google.com/maps/dir/43.1121392,-76.280399/43.0610852,-76.5660628/@43.0879719,-76.5307391,10.88z/data=!4m14!4m13!1m10!3m4!1m2!1d-76.4665781!2d43.1604551!3s0x89d75875f1a4438b:0xa93eb9fc178480ff!3m4!1m2!1d-76.5703295!2d43.157671!3s0x89d75a0d39640bdf:0xb42b7fb6a14eca82!1m0!3e0). We were already at the western terminus of I-690, exited before the end of NY 690, and traveled only partial segments of NY 370 and NY 34.
Jokes are always funnier when you explain them.
Quote from: webny99 on November 16, 2022, 12:56:09 PM
Quote from: kphoger on November 15, 2022, 09:25:26 AM
Quote from: webny99 on November 14, 2022, 09:15:58 PM
the only thing I don't remember is if the Thruway exit from I-690 was closed, or if the driver took an alternate route for some other unknown reason.
Route clinching.
Except that no routes were clinched (https://www.google.com/maps/dir/43.1121392,-76.280399/43.0610852,-76.5660628/@43.0879719,-76.5307391,10.88z/data=!4m14!4m13!1m10!3m4!1m2!1d-76.4665781!2d43.1604551!3s0x89d75875f1a4438b:0xa93eb9fc178480ff!3m4!1m2!1d-76.5703295!2d43.157671!3s0x89d75a0d39640bdf:0xb42b7fb6a14eca82!1m0!3e0). We were already at the western terminus of I-690, exited before the end of NY 690, and traveled only partial segments of NY 370 and NY 34.
The driver was just looking to add some segments.
Quote from: JoePCool14 on November 16, 2022, 04:17:17 PM
Quote from: webny99 on November 16, 2022, 12:56:09 PM
Quote from: kphoger on November 15, 2022, 09:25:26 AM
Quote from: webny99 on November 14, 2022, 09:15:58 PM
the only thing I don't remember is if the Thruway exit from I-690 was closed, or if the driver took an alternate route for some other unknown reason.
Route clinching.
Except that no routes were clinched (https://www.google.com/maps/dir/43.1121392,-76.280399/43.0610852,-76.5660628/@43.0879719,-76.5307391,10.88z/data=!4m14!4m13!1m10!3m4!1m2!1d-76.4665781!2d43.1604551!3s0x89d75875f1a4438b:0xa93eb9fc178480ff!3m4!1m2!1d-76.5703295!2d43.157671!3s0x89d75a0d39640bdf:0xb42b7fb6a14eca82!1m0!3e0). We were already at the western terminus of I-690, exited before the end of NY 690, and traveled only partial segments of NY 370 and NY 34.
The driver was just looking to add some segments.
Precisely. They were the only segments remaining to clinch.
As I just posted in another topic, we just moved to Reno, NV. Last winter, already following Reno news, we were hearing all sorts of stories of people blindly following their GPS up impassable dirt roads during a period that both I-80 and US50 were closed due to a blizzard. Since the apps knew 80 and 50 were closed, it just found another not officially closed route and people just followed it rather than applying some common sense.
So fast forward to last Saturday night. I was on my way home from Sacramento to Reno and due to some snow, 80 was "chains or 4WD with snow tires." I wasn't concerned as I had 48 hours old new tires on my Subaru. Halfway up, the app pinged with "we found a faster route." I'm not sure but I think it was a piece of old US40 that's still extant Thank you but no - I'll just stick to 80. It was 1am and there was very little traffic - most of the trucks were stopped waiting it out rather than putting on chains. The traffic map had 80 as red as what traffic was moving was doing the 30mph speed limit when chain controls are in effect (and I suspect all the trucks that were stopping was also confusing "Google Central" as to what traffic was doing). In the end, I could hold road speed to the chain checkpoint where there was no waiting and not even an inspection (he saw I had a Subaru and said "you're good" and off I went).
EDIT: Rereading what I wrote, I realized the way I wrote it makes me sound like one of those overconfident idiots in snow. I'm not. And even though I said I just moved to Reno, not my first time in the Sierra Nevada in snow (used to live in the Bay Area).
Quote from: lstone19 on November 17, 2022, 09:49:03 PMAs I just posted in another topic, we just moved to Reno, NV. Last winter, already following Reno news, we were hearing all sorts of stories of people blindly following their GPS up impassable dirt roads during a period that both I-80 and US50 were closed due to a blizzard. Since the apps knew 80 and 50 were closed, it just found another not officially closed route and people just followed it rather than applying some common sense.
No joke. Too many people have attempted to bypass a I-80 closure utilizing the infamous "Dog Valley Road" starting in Verdi, NV despite this sign (https://www.google.com/maps/@39.5247058,-120.0018506,3a,75y,283.89h,75.42t/data=!3m6!1e1!3m4!1sU0uL-B9KuD1dfXMysgWwwg!2e0!7i16384!8i8192), this sign (https://www.google.com/maps/@39.5242937,-120.012701,3a,75y,301.39h,85.7t/data=!3m6!1e1!3m4!1sivJS4bU_pBZjZs5v8okl_A!2e0!7i16384!8i8192). or this sign (https://www.google.com/maps/@39.5245848,-120.0131621,3a,21.8y,328.5h,85.97t/data=!3m6!1e1!3m4!1sVOSsjNBACb5S_H4GIgrXtA!2e0!7i16384!8i8192). Because of the severe upward slope of the Sierra Nevada mountains, winter storms can be
very nasty, and I stayed home in Sacramento viewing the snow from the CalTrans Cameras (https://markholtz.info/quickmap).