AARoads Forum

Non-Road Boards => Off-Topic => Topic started by: index on June 22, 2022, 08:20:32 PM

Title: Things non-roadgeeks get wrong about roads that bother you
Post by: index on June 22, 2022, 08:20:32 PM
My biggest pet peeve is when they call any old road an Interstate. No, you're not on the Interstate when you're on a two lane city street infested with traffic lights or any long distance highway. Too many people I know do that.

Of course, I don't actually interrupt and correct them because nobody wants to be that person. I just seethe inside.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: skluth on June 22, 2022, 08:30:11 PM
That's strange. When I lived in the Midwest, most people just referred to them as "Highway (insert number here)," both in Wisconsin and in St Louis. In California, it's just "The (insert number)" for most highways. Unnumbered streets were just "the street" or "the road," though I have heard busy streets called highways on occasion. Never heard anything but an interstate called an interstate.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: SkyPesos on June 22, 2022, 08:31:51 PM
Calling interstates and US routes "state routes".
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: jeffandnicole on June 22, 2022, 08:35:30 PM
Quote from: SkyPesos on June 22, 2022, 08:31:51 PM
Calling interstates and US routes "state routes".

I find a lot of people around here thinking state roads are county roads.

Last winter, someone took to their community's Facebook page to complain the State DOT trucks weren't plowing business parking lots!  (That person was corrected by a whole lot of people)
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Max Rockatansky on June 22, 2022, 09:00:45 PM
Not knowing the difference between US, Interstate and State routes.  Not having a good general sense of direction.  Not understanding how driving can be fun and why someone wouldn't take the most direct route to places.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: NWI_Irish96 on June 22, 2022, 09:07:56 PM
Quote from: SkyPesos on June 22, 2022, 08:31:51 PM
Calling interstates and US routes "state routes".

What I get a lot more is people confusing US and state highways. Interstates are freeways and have blue/red shields. US and state highways (around here) are almost always non-freeways and have black and white shields.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: formulanone on June 22, 2022, 09:19:43 PM
Quote from: Max Rockatansky on June 22, 2022, 09:00:45 PM
Not understanding how driving can be fun and why someone wouldn't take the most direct route to places.

Pretty much this.

99% of the time, the distinction between route types is essentially minutiae to everyone else.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Bruce on June 22, 2022, 09:28:36 PM
Being 100% reliant on the GPS screen, even when it doesn't make sense.

For example: a recent ride in the Tesla with friends was made a bit more perilous when the in-car GPS navigated us down a gravel road with giant potholes instead of the nice paved state highway nearby, but we didn't realize until it was too late.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Max Rockatansky on June 22, 2022, 09:33:22 PM
Quote from: Bruce on June 22, 2022, 09:28:36 PM
Being 100% reliant on the GPS screen, even when it doesn't make sense.

For example: a recent ride in the Tesla with friends was made a bit more perilous when the in-car GPS navigated us down a gravel road with giant potholes instead of the nice paved state highway nearby, but we didn't realize until it was too late.

Did you end up on Bald Hills Road?
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Bruce on June 22, 2022, 10:05:49 PM
Quote from: Max Rockatansky on June 22, 2022, 09:33:22 PM
Quote from: Bruce on June 22, 2022, 09:28:36 PM
Being 100% reliant on the GPS screen, even when it doesn't make sense.

For example: a recent ride in the Tesla with friends was made a bit more perilous when the in-car GPS navigated us down a gravel road with giant potholes instead of the nice paved state highway nearby, but we didn't realize until it was too late.

Did you end up on Bald Hills Road?

This was over near Mount Hood, actually. Never got that far south in Redwoods Country.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: hbelkins on June 22, 2022, 10:26:03 PM
"Federal routes"

No, this isn't another gratuitous swipe at Calrog, although there's nothing wrong with that. Very few routes are actually owned or maintained by the federal government.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Max Rockatansky on June 22, 2022, 10:26:21 PM
Quote from: Bruce on June 22, 2022, 10:05:49 PM
Quote from: Max Rockatansky on June 22, 2022, 09:33:22 PM
Quote from: Bruce on June 22, 2022, 09:28:36 PM
Being 100% reliant on the GPS screen, even when it doesn't make sense.

For example: a recent ride in the Tesla with friends was made a bit more perilous when the in-car GPS navigated us down a gravel road with giant potholes instead of the nice paved state highway nearby, but we didn't realize until it was too late.

Did you end up on Bald Hills Road?

This was over near Mount Hood, actually. Never got that far south in Redwoods Country.

The one I'm referring to connects US 101 to eastern CA 169 and CA 96 via the Lady Bird Johnson Trail.  It wouldn't surprise me if a GPS recommended it over CA 299 given it is mostly a quality gravel road through Redwood National Park. 
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Rothman on June 22, 2022, 11:40:05 PM
Quote from: hbelkins on June 22, 2022, 10:26:03 PM
"Federal routes"

No, this isn't another gratuitous swipe at Calrog, although there's nothing wrong with that. Very few routes are actually owned or maintained by the federal government.
They pay for a heckuva lot of it, though.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: hotdogPi on June 23, 2022, 12:28:03 AM
Quote from: hbelkins on June 22, 2022, 10:26:03 PM
"Federal routes"

No, this isn't another gratuitous swipe at Calrog, although there's nothing wrong with that. Very few routes are actually owned or maintained by the federal government.

Unless you're in Mexico, where they're actually called that.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: J N Winkler on June 23, 2022, 01:11:50 AM
I've actually seen the "federal route" terminology on the title sheets of state DOT construction plans sets.

I don't say anything unless it cannot be avoided, but it bothers me when civilians use the term highway as a synonym for freeway in a way that suggests they think non-freeways cannot be highways.  "I-135 or US 77?  I'll take the highway."
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: roadman65 on June 23, 2022, 03:24:54 AM
Calling US 17, 92, and 441 in the Orlando area just by US 441 or four forty-one.

Most people think that US 17 & 92 terminate at FL 50 in Orlando including the signing contractor for the I-4 ultimate who signs the Colonial Drive exit solely as FL SR 50 despite the original signs had both US 17 & 92 on them and the fact contractors or engineers like to copy verbatim wording on guidesigns.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: SSOWorld on June 23, 2022, 04:26:59 AM
Quote from: skluth on June 22, 2022, 08:30:11 PM
That's strange. When I lived in the Midwest, most people just referred to them as "Highway (insert number here)," both in Wisconsin and in St Louis. In California, it's just "The (insert number)" for most highways. Unnumbered streets were just "the street" or "the road," though I have heard busy streets called highways on occasion. Never heard anything but an interstate called an interstate.
It's pronounced "Hwy"! :bigass:
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Rothman on June 23, 2022, 06:46:41 AM
Quote from: J N Winkler on June 23, 2022, 01:11:50 AM
I've actually seen the "federal route" terminology on the title sheets of state DOT construction plans sets.

What?  Where?

I can see "federal-aid route" or "federal-aid eligible" or something along those lines, but "federal route"?  That's just weird.

In NY, we mainly just refer to "Rt 13" or "I-81" and the very old state highway designations.  For some reason, we're frustratingly inconsistent with U.S. highways.  You'll mostly see just references to "Rt 20" rather than "US 20," as an example.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: kphoger on June 23, 2022, 09:44:42 AM
Quote from: SkyPesos on June 22, 2022, 08:31:51 PM
Calling interstates and US routes "state routes".

They are state highways.  They just aren't "state routes".  Think about that.  Now who's not being sensible?

Quote from: J N Winkler on June 23, 2022, 01:11:50 AM
it bothers me when civilians use the term highway as a synonym for freeway in a way that suggests they think non-freeways cannot be highways.

Don't go over to the Skyscrapercity road forums, then.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: jeffandnicole on June 23, 2022, 10:00:45 AM
Quote from: kphoger on June 23, 2022, 09:44:42 AM
Quote from: SkyPesos on June 22, 2022, 08:31:51 PM
Calling interstates and US routes "state routes".

They are state highways.  They just aren't "state routes".  Think about that.  Now who's not being sensible?

They're state *maintained*. Still not a state route.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: zzcarp on June 23, 2022, 10:01:07 AM
Quote from: Max Rockatansky on June 22, 2022, 09:00:45 PM
Not knowing the difference between US, Interstate and State routes (or highways).  Not having a good general sense of direction.  Not understanding how driving can be fun and why someone wouldn't take the most direct route to places.

Not knowing the difference between the route types bugs me. A Facebook friend this morning posted she got into an accident on "I-36" (referring to the US 36 Boulder Turnpike freeway). And, no, I didn't correct her.

Even worse is when CDOT's media people screw up the highway classifications. They recently referred to construction on CO 285 when it really is US 285. I did comment on that one and CDOT said they'd change the release.

And, as an engineer, I always notice when surveys and plans mischaracterize a route type. It seems like if we're in the industry, we should work to distinguish between the highway classifications.

Quote from: kphoger on June 23, 2022, 09:44:42 AM
Quote from: SkyPesos on June 22, 2022, 08:31:51 PM
Calling interstates and US routes "state routes".

They are state highways.  They just aren't "state routes".  Think about that.  Now who's not being sensible?


It depends where you are. I grew up in Ohio, and we called them US Routes (like US Route 20) or State Routes (State Route 60). Here in Colorado, we colloquially refer to them as highways (like US Highway 36 or State Highway 2). Either way, unless it's written down, laypeople tend to just drop the US/State distinction and just say Route 20 (in Ohio) or Highway 6 (in Colorado).
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: US 89 on June 23, 2022, 10:14:06 AM
The news stations in Salt Lake will often report on events that occurred on "SR-6"  or "SR-40"  or "SR-89" . Those are US highways. Drives me up the wall. KSL is especially guilty of this but I've seen it on all of them.

At least I've never seen a UDOT media release mess that up. That said, the state does have its share of US/SR sign errors, which are not numerous by any means but also not too hard to come across.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: webny99 on June 23, 2022, 10:23:19 AM
Quote from: Max Rockatansky on June 22, 2022, 09:00:45 PMNot having a good general sense of direction.  Not understanding how driving can be fun and why someone wouldn't take the most direct route to places.

Interestingly, those two things often oppose each other. People might not take the most direct route precisely because they don't have a good sense of direction. So they could understand why you might not take the most direct route, but their understanding would be very different than a roadgeek's understanding.

Ironically, this creates a bit of a dilemma sometimes when I don't want to take the fastest way, since everyone assumes I'm always looking for the shortest/fastest route and know the best way to get pretty much anywhere. That doesn't leave much opportunity to take different routes since people don't seem to understand intentionally taking a longer route. If you're just bad at directions and don't know your way around, you can take a longer route and nobody complains, but I can't use that excuse!
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: kphoger on June 23, 2022, 10:34:55 AM
Quote from: jeffandnicole on June 23, 2022, 10:00:45 AM

Quote from: kphoger on June 23, 2022, 09:44:42 AM

Quote from: SkyPesos on June 22, 2022, 08:31:51 PM
Calling interstates and US routes "state routes".

They are state highways.  They just aren't "state routes".  Think about that.  Now who's not being sensible?

They're state *maintained*. Still not a state route.

And state owned and operated.

Quote from: FHWA:  Interstate Frequently Asked Questions
Who owns it?

The States own and operate the Interstate highways.

https://www.fhwa.dot.gov/interstate/faq.cfm
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: webny99 on June 23, 2022, 10:57:09 AM
A big one for me is avoidance of freeways because they're slightly longer mileage.

The two default routes on my roughly 11-mile commute are (1) about 50% local roads, 50% freeway, and (2) about 70% local roads, 30% freeway. There's also a third route that's 15 miles, but only about 10% local roads, 10% expressway, and 80% freeway. Time-wise, it's basically a toss-up between all three routes, and I find the majority freeway route more relaxing since you can cruise at 65-70 mph most of the way instead of poking along underposted local roads and invariably ending up stuck behind someone going below my preferred speed and missing most of the lights. So oftentimes, especially in the afternoon, I'll take the majority freeway route. And yet, many people wouldn't even consider that route because it "seems" so much longer and because you have to backtrack to get to/from the freeway. To each their own, but I regard all three routes as perfectly good options even though one is a few miles longer.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: kphoger on June 23, 2022, 11:09:46 AM
Quote from: webny99 on June 23, 2022, 10:57:09 AM
A big one for me is avoidance of freeways because they're slightly longer mileage.

The two default routes on my roughly 11-mile commute are (1) about 50% local roads, 50% freeway, and (2) about 70% local roads, 30% freeway. There's also a third route that's 15 miles, but only about 10% local roads, 10% expressway, and 80% freeway. Time-wise, it's basically a toss-up between all three routes, and I find the majority freeway route more relaxing since you can cruise at 65-70 mph most of the way instead of poking along underposted local roads and invariably ending up stuck behind someone going below my preferred speed and missing most of the lights. So oftentimes, especially in the afternoon, I'll take the majority freeway route. And yet, many people wouldn't even consider that route because it "seems" so much longer and because you have to backtrack to get to/from the freeway. To each their own, but I regard all three routes as perfectly good options even though one is a few miles longer.

Mine is the opposite:  avoidance of non-freeways even if they're shorter mileage.

For example, take a Wichita—Nashville trip.

Option #1:
I-35 → I-435 → I-470 → I-70 → I-64 → I-57 → I-24
748 miles / 10h 45m

Option #2:
US-400 → KS/MO-171 → MO-96 → I-49 → I-44 → US-60 → US-51 → KY-121 → KY-286 → US-62 → I-24
681 miles / 10h 45m

I would prefer Option #2, but most people would choose Option #1.

(I've actually done both routes, #1 eastbound and #2 westbound.  The only reason I chose #1 eastbound was to avoid US-62 and KY-286 because of winter weather.)
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: 1995hoo on June 23, 2022, 11:12:12 AM
Quote from: J N Winkler on June 23, 2022, 01:11:50 AM
....

I don't say anything unless it cannot be avoided, but it bothers me when civilians use the term highway as a synonym for freeway in a way that suggests they think non-freeways cannot be highways.  "I-135 or US 77?  I'll take the highway."

Ehhh, that doesn't bother me at all because I think it's in the nature of a regionalism, much like the "expressway" versus "freeway" issue that annoys some people on this forum. I'm sure part of my view of that is because "freeway" is not a term we generally use in this part of the country unless it's part of a road's name (e.g., the Whitehurst Freeway in DC). I once saw one of those polls on regionalisms–you know, the sort of poll that asks whether you say "soda," "pop," or "Coke," whether you say "water fountain," "drinking fountain," or "bubbler," whether it's a "shopping cart" or a "buggy," etc.–and the poll asked something like, "What do you call the type of road with no traffic lights and no intersections where you go to drive faster than you can on other roads?" I think the choices were "highway," "freeway," "expressway," and maybe "turnpike" (or perhaps "something else" instead of "turnpike"). Around here, the term "highway" is definitely the term normally used for that sort of thing. Not just here, either; I recall in 1996 when Hurricane Fran did a number on North Carolina, one of my classmates was griping that "751 was blocked by downed trees, so I had to take the highway this morning" ("the highway" referring to US-15/501, which was and is what some people call a "freeway" from the area where she lived–near where South Square Mall used to be–up to, and beyond, the area where Duke is).

Now, with all that said, I find it somewhat annoying when people who are not from this area use out-of-area regionalisms to refer to roads around here and expect us to know what they mean. I once saw something where someone referred simply to "the Tollway." That's not a term we use here and it wasn't clear what he meant; it turned out he was referring to the Dulles Toll Road. Similarly, I saw someone referring to the "HP" being out on a given road. People asked what in the world he meant and it turned out he meant "Highway Patrol," which is also not a term we use.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Max Rockatansky on June 23, 2022, 11:13:50 AM
I usually opt for the surface highway if the drive time via a freeway is a near wash.  An example of this would be how I would usually take a series of US Routes (mostly US 27) between Brooksville and Key West versus the absolute bore that was I-75.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Dirt Roads on June 23, 2022, 11:23:23 AM
Quote from: webny99 on June 23, 2022, 10:57:09 AM
A big one for me is avoidance of freeways because they're slightly longer mileage.

The two default routes on my roughly 11-mile commute are (1) about 50% local roads, 50% freeway, and (2) about 70% local roads, 30% freeway. There's also a third route that's 15 miles, but only about 10% local roads, 10% expressway, and 80% freeway. Time-wise, it's basically a toss-up between all three routes, and I find the majority freeway route more relaxing since you can cruise at 65-70 mph most of the way instead of poking along underposted local roads and invariably ending up stuck behind someone going below my preferred speed and missing most of the lights. So oftentimes, especially in the afternoon, I'll take the majority freeway route. And yet, many people wouldn't even consider that route because it "seems" so much longer and because you have to backtrack to get to/from the freeway. To each their own, but I regard all three routes as perfectly good options even though one is a few miles longer.

Quote from: kphoger on June 23, 2022, 11:09:46 AM
Mine is the opposite:  avoidance of non-freeways even if they're shorter mileage.

For example, take a Wichita—Nashville trip.

Option #1:
I-35 → I-435 → I-470 → I-70 → I-64 → I-57 → I-24
748 miles / 10h 45m

Option #2:
US-400 → KS/MO-171 → MO-96 → I-49 → I-44 → US-60 → US-51 → KY-121 → KY-286 → US-62 → I-24
681 miles / 10h 45m

I would prefer Option #2, but most people would choose Option #1.

(I've actually done both routes, #1 eastbound and #2 westbound.  The only reason I chose #1 eastbound was to avoid US-62 and KY-286 because of winter weather.)

I understand why folks stick to the Interstates and other freeways nowadays with the higher speed limits.  But I could never understand this during the NMSL (National Minimum Speed Limit) days. 
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: kphoger on June 23, 2022, 11:25:08 AM
I've always had the idea that "freeway" was a California regionalism.  I think I only started using the term after getting into the online roadgeek community.

When I lived in the Chicago suburbs, I started referring to State Routes as "Route ##", US Routes as "Highway ##", and Interstates as "I ##", because that seemed to be the way people talked.  For example, I heard people refer to Ogden Avenue as "Highway 34" but the road to Morris as "Route 47".  Maybe that was just the result of a small sample size, but it's something I noticed and adopted into my own verbiage.  I still occasionally make that distinction even today.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: J N Winkler on June 23, 2022, 12:18:37 PM
Quote from: Rothman on June 23, 2022, 06:46:41 AM
Quote from: J N Winkler on June 23, 2022, 01:11:50 AMI've actually seen the "federal route" terminology on the title sheets of state DOT construction plans sets.

What?  Where?

I can see "federal-aid route" or "federal-aid eligible" or something along those lines, but "federal route"?  That's just weird.

I remember seeing it on the title sheet of at least one Georgia DOT plans set from the 1970's or early 1980's (probably long before Calrog was born).  Georgia is one of the states where every US route is a state route overlap, so I suspect it had to do with that.

I ran across this during the time of peak viatology, which is why I noticed it, but I said nothing so as to avoid pouring gasoline on the flames.

Quote from: 1995hoo on June 23, 2022, 11:12:12 AM
Quote from: J N Winkler on June 23, 2022, 01:11:50 AMI don't say anything unless it cannot be avoided, but it bothers me when civilians use the term highway as a synonym for freeway in a way that suggests they think non-freeways cannot be highways.  "I-135 or US 77?  I'll take the highway."

Ehhh, that doesn't bother me at all because I think it's in the nature of a regionalism, much like the "expressway" versus "freeway" issue that annoys some people on this forum. I'm sure part of my view of that is because "freeway" is not a term we generally use in this part of the country unless it's part of a road's name (e.g., the Whitehurst Freeway in DC). I once saw one of those polls on regionalisms–you know, the sort of poll that asks whether you say "soda," "pop," or "Coke," whether you say "water fountain," "drinking fountain," or "bubbler," whether it's a "shopping cart" or a "buggy," etc.–and the poll asked something like, "What do you call the type of road with no traffic lights and no intersections where you go to drive faster than you can on other roads?" I think the choices were "highway," "freeway," "expressway," and maybe "turnpike" (or perhaps "something else" instead of "turnpike"). Around here, the term "highway" is definitely the term normally used for that sort of thing. Not just here, either; I recall in 1996 when Hurricane Fran did a number on North Carolina, one of my classmates was griping that "751 was blocked by downed trees, so I had to take the highway this morning" ("the highway" referring to US-15/501, which was and is what some people call a "freeway" from the area where she lived–near where South Square Mall used to be–up to, and beyond, the area where Duke is).

Yes--it's very much a regional usage.  I don't really object to others, such as urban freeways being described as "expressways" in areas where that has traditionally been part of their names, or "the [route number]" in reference to freeways in southern California.  I think what pushes on me is the (admittedly remote) possibility of blowback if I use the term highway in reference to roads that are not freeways and my interlocutors then think I did them an injury by pointing them to facilities of inferior standard.

Quote from: 1995hoo on June 23, 2022, 11:12:12 AMNow, with all that said, I find it somewhat annoying when people who are not from this area use out-of-area regionalisms to refer to roads around here and expect us to know what they mean. I once saw something where someone referred simply to "the Tollway." That's not a term we use here and it wasn't clear what he meant; it turned out he was referring to the Dulles Toll Road. Similarly, I saw someone referring to the "HP" being out on a given road. People asked what in the world he meant and it turned out he meant "Highway Patrol," which is also not a term we use.

I've often wondered if the Highway Patrol/State Police divide has to do with whether a state police agency was originally founded specifically to patrol the state highway system.  This distinction would seem to hold for the Kansas Highway Patrol, Oklahoma Highway Patrol, Ohio State Highway Patrol (all founded during the Depression as motor patrol agencies), as well as the Massachusetts State Police (predecessor agency was founded 1865) and the Michigan State Police (founded 1917 to maintain internal order during World War I), with the Virginia State Police (originally a DMV constabulary) being somewhat of an exception.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: 1995hoo on June 23, 2022, 12:22:36 PM
Quote from: J N Winkler on June 23, 2022, 12:18:37 PM
....

Yes--it's very much a regional usage.  I don't really object to others, such as urban freeways being described as "expressways" in areas where that has traditionally been part of their names, or "the [route number]" in reference to freeways in southern California.  I think what pushes on me is the (admittedly remote) possibility of blowback if I use the term highway in reference to roads that are not freeways and my interlocutors then think I did them an injury by pointing them to facilities of inferior standard.

....

I can understand that. I once had to explain to someone that a state statute that used the word "highway" was not referring to Interstates or even to major routes like US-29 between DC and Charlottesville, but to roads generally.


Edited to add: I realized where that discussion was and a search found it. The first link is to the first post in the thread, the second link is to where someone misunderstood what "highway" meant, and the third link is to my response to him on that issue. The discussion had to do with whether you're obligated to stop for a school bus when you're on a street with a median but the school bus stop is located at an intersection.

https://virginia.sportswar.com/mid/11957344/board/general/

https://virginia.sportswar.com/mid/11958342/board/general/

https://virginia.sportswar.com/mid/11958800/board/general/
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: formulanone on June 23, 2022, 12:30:49 PM
Quote from: kphoger on June 23, 2022, 10:34:55 AM
Quote from: jeffandnicole on June 23, 2022, 10:00:45 AM

Quote from: kphoger on June 23, 2022, 09:44:42 AM

Quote from: SkyPesos on June 22, 2022, 08:31:51 PM
Calling interstates and US routes "state routes".

They are state highways.  They just aren't "state routes".  Think about that.  Now who's not being sensible?

They're state *maintained*. Still not a state route.

And state owned and operated.

Quote from: FHWA:  Interstate Frequently Asked Questions
Who owns it?

The States own and operate the Interstate highways.

https://www.fhwa.dot.gov/interstate/faq.cfm

...again, this is why the public at large doesn't really care about the precise terminology and classification. To them, it's just "the government" who slaps down gray pavement, puts up signs, and lighting. The locals in the area are going to call it what it is, but terms are effectively interchangeable.

To the public, it only really matters when they:
[1] have a complaint (missing sign, traffic light, pothole, repaving et al) for a specific agency
[2] need it plowed
[3] driving in a place where there's nearby route number duplication

The rest is just details not worth arguing about unless you have a lot of time together trapped in an elevator.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: webny99 on June 23, 2022, 12:46:19 PM
Quote from: kphoger on June 23, 2022, 11:09:46 AM
Quote from: webny99 on June 23, 2022, 10:57:09 AM
A big one for me is avoidance of freeways because they're slightly longer mileage.

Mine is the opposite:  avoidance of non-freeways even if they're shorter mileage.

For example, take a Wichita—Nashville trip.

...

I can see that as well, and I think it's probably the trip length that makes the difference.

On shorter trips, people tend to gravitate towards the shorter, more local routes, since that's what they're comfortable with and going "out of the way" seems like a bigger deal than it actually is. On longer trips, people tend to gravitate towards the all-freeway routes, since that's what they're comfortable with and taking "shortcuts" seems less predictable, more prone to slowdowns, and increases the likelihood of getting lost. In both cases, the basis for that decision-making is all about perception, and one's perceptions tend to be very different for a daily commute than they do for a full-on road trip.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: webny99 on June 23, 2022, 01:07:32 PM
To weigh in on the "highway" debate, I would ask: is this (https://goo.gl/maps/vjSb139kBwnsR5x3A) (a generic county route in rural North Dakota) a "highway"?
My family that grew up in the area would say Yes. I would say No.

A "highway" is generically defined as "a main road, especially one connecting major towns or cities". So to me, it's just a matter of perception. As someone who grew up in a NY suburb of about 35k in a county of 750k, my idea of "major towns and cities" is very different from that of someone who grew up in a "city" of 500 in a county of 7000 (in an entire state that only just surpassed 750k in the most recent census).


Quote from: J N Winkler on June 23, 2022, 12:18:37 PM
I think what pushes on me is the (admittedly remote) possibility of blowback if I use the term highway in reference to roads that are not freeways and my interlocutors then think I did them an injury by pointing them to facilities of inferior standard.

As I've just described above, I've had this come up firsthand in the context of whether or not something counts as a "highway". I don't necessarily take issue with a two-lane road being called a highway, but for most county routes, I would consider "highway" at least slightly misleading unless given additional context. To me, most county routes -- and indeed many state routes -- are more effectively described as "backroads". But again, it's all about perception, since for some people, especially in rural, remote areas, what I'd call "backroads" are their highways - their connection to other towns and cities. 
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: triplemultiplex on June 23, 2022, 03:07:30 PM
Quote from: Bruce on June 22, 2022, 09:28:36 PM
Being 100% reliant on the GPS screen, even when it doesn't make sense.

Seconded.
What's more, the inability to navigate the city one has lived in for years without the damn GPS.  Like seriously?  You need the GPS to tell you how to get to the airport you've been to 10 times this year? WTF?
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: vdeane on June 23, 2022, 09:15:20 PM
Quote from: webny99 on June 23, 2022, 01:07:32 PM
To weigh in on the "highway" debate, I would ask: is this (https://goo.gl/maps/vjSb139kBwnsR5x3A) (a generic county route in rural North Dakota) a "highway"?
My family that grew up in the area would say Yes. I would say No.
It would have been called one when my Driver's Ed class did our "highway driving" lesson.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: thspfc on June 23, 2022, 10:37:12 PM
Quote from: vdeane on June 23, 2022, 09:15:20 PM
Quote from: webny99 on June 23, 2022, 01:07:32 PM
To weigh in on the "highway" debate, I would ask: is this (https://goo.gl/maps/vjSb139kBwnsR5x3A) (a generic county route in rural North Dakota) a "highway"?
My family that grew up in the area would say Yes. I would say No.
It would have been called one when my Driver's Ed class did our "highway driving" lesson.
I'd consider it just a road. For county routes my general rule is that if it looks like it could be a state highway then it's a highway. That one does not.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: US 89 on June 24, 2022, 01:08:00 AM
Quote from: thspfc on June 23, 2022, 10:37:12 PM
Quote from: vdeane on June 23, 2022, 09:15:20 PM
Quote from: webny99 on June 23, 2022, 01:07:32 PM
To weigh in on the "highway" debate, I would ask: is this (https://goo.gl/maps/vjSb139kBwnsR5x3A) (a generic county route in rural North Dakota) a "highway"?
My family that grew up in the area would say Yes. I would say No.
It would have been called one when my Driver's Ed class did our "highway driving" lesson.
I'd consider it just a road. For county routes my general rule is that if it looks like it could be a state highway then it's a highway. That one does not.

I've seen plenty of state highways that look worse than that.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: kphoger on June 24, 2022, 02:40:38 PM
Quote from: vdeane on June 23, 2022, 09:15:20 PM
It would have been called one when my Driver's Ed class did our "highway driving" lesson.

When my drivers ed class did the "highway driving" lesson, we drove 31 miles to I-70 in Colby, drove 8 miles to the next exit, and then took US-24 back to town.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: thspfc on June 24, 2022, 07:04:12 PM
Quote from: kphoger on June 24, 2022, 02:40:38 PM
Quote from: vdeane on June 23, 2022, 09:15:20 PM
It would have been called one when my Driver's Ed class did our "highway driving" lesson.

When my drivers ed class did the "highway driving" lesson, we drove 31 miles to I-70 in Colby, drove 8 miles to the next exit, and then took US-24 back to town.
To be fair, those are highways.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: I-55 on June 24, 2022, 11:47:51 PM
I'm interning with City of Fort Wayne this summer. If I had a dollar for every time someone asked if we have plans for Lima Rd (SR 3) or I-69 I would be able to take a paid day off. Just because the road is in city limits doesn't mean we maintain it. Sure we call it different names but it's still a state maintained route, so we have little at all to do with them (this also applies to city vs county roads).
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: KCRoadFan on June 25, 2022, 08:00:01 PM
It bothers me whenever people say that toll roads can't be freeways - the "free"  refers to "free flow of traffic"  (i.e. limited access) rather than "free of charge" .

Also, those who say that interstates entirely within one state (e.g. I-16 in Georgia or I-45 in Texas) aren't actually interstates - again, the word "interstate"  refers to a classification of highway, not the path that highway actually travels.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: Flint1979 on June 26, 2022, 10:34:42 PM
In Michigan all the state highways are called M-(whatever the number is) so on Google Maps M-46 in the Saginaw area for some reason gets called State Route 46 and everything else gets called Michigan instead of State Route and I'm thinking you stupid idiot it's M-46 we don't call it State Route.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: kphoger on June 27, 2022, 03:03:38 PM
Quote from: thspfc on June 24, 2022, 07:04:12 PM

Quote from: kphoger on June 24, 2022, 02:40:38 PM

Quote from: vdeane on June 23, 2022, 09:15:20 PM
It would have been called one when my Driver's Ed class did our "highway driving" lesson.

When my drivers ed class did the "highway driving" lesson, we drove 31 miles to I-70 in Colby, drove 8 miles to the next exit, and then took US-24 back to town.

To be fair, those are highways.

To be fair, so was the 30 miles of K-25 we used to get to Colby.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: bwana39 on June 28, 2022, 01:18:10 PM
Quote from: webny99 on June 23, 2022, 10:57:09 AM
A big one for me is avoidance of freeways because they're slightly longer mileage.

The two default routes on my roughly 11-mile commute are (1) about 50% local roads, 50% freeway, and (2) about 70% local roads, 30% freeway. There's also a third route that's 15 miles, but only about 10% local roads, 10% expressway, and 80% freeway. Time-wise, it's basically a toss-up between all three routes, and I find the majority freeway route more relaxing since you can cruise at 65-70 mph most of the way instead of poking along underposted local roads and invariably ending up stuck behind someone going below my preferred speed and missing most of the lights. So oftentimes, especially in the afternoon, I'll take the majority freeway route. And yet, many people wouldn't even consider that route because it "seems" so much longer and because you have to backtrack to get to/from the freeway. To each their own, but I regard all three routes as perfectly good options even though one is a few miles longer.

If I can get to the same place in the same time, I will bypass the freeway EVERY time.
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: bwana39 on June 28, 2022, 01:20:09 PM
Quote from: Dirt Roads on June 23, 2022, 11:23:23 AM


I understand why folks stick to the Interstates and other freeways nowadays with the higher speed limits.  But I could never understand this during the NMSL (National Minimum Speed Limit) days.

Minimum LMAO
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: bwana39 on June 28, 2022, 01:52:25 PM
Quote from: webny99 on June 23, 2022, 01:07:32 PM
To weigh in on the "highway" debate, I would ask: is this (https://goo.gl/maps/vjSb139kBwnsR5x3A) (a generic county route in rural North Dakota) a "highway"?
My family that grew up in the area would say Yes. I would say No.

A "highway" is generically defined as "a main road, especially one connecting major towns or cities". So to me, it's just a matter of perception. As someone who grew up in a NY suburb of about 35k in a county of 750k, my idea of "major towns and cities" is very different from that of someone who grew up in a "city" of 500 in a county of 7000 (in an entire state that only just surpassed 750k in the most recent census).


Quote from: J N Winkler on June 23, 2022, 12:18:37 PM
I think what pushes on me is the (admittedly remote) possibility of blowback if I use the term highway in reference to roads that are not freeways and my interlocutors then think I did them an injury by pointing them to facilities of inferior standard.

As I've just described above, I've had this come up firsthand in the context of whether or not something counts as a "highway". I don't necessarily take issue with a two-lane road being called a highway, but for most county routes, I would consider "highway" at least slightly misleading unless given additional context. To me, most county routes -- and indeed many state routes -- are more effectively described as "backroads". But again, it's all about perception, since for some people, especially in rural, remote areas, what I'd call "backroads" are their highways - their connection to other towns and cities.

I had an in-law of a relative talk about the HIGHWAY near his house. Describe FM-196 as "the highway" and SH-37 (two lanes) as the "Big Highway".

I guess US-271 (still two lanes) would have been the "REALLY BIG HIGHWAY"

For us if it has painted stripes, it probably would be called highway IF it is outside of town. In town everything that isn't freeway is "street. "

Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: ethanhopkin14 on June 28, 2022, 05:00:05 PM
Quote from: J N Winkler on June 23, 2022, 12:18:37 PM
Quote from: Rothman on June 23, 2022, 06:46:41 AM
Quote from: J N Winkler on June 23, 2022, 01:11:50 AMI've actually seen the "federal route" terminology on the title sheets of state DOT construction plans sets.

What?  Where?

I can see "federal-aid route" or "federal-aid eligible" or something along those lines, but "federal route"?  That's just weird.

I remember seeing it on the title sheet of at least one Georgia DOT plans set from the 1970's or early 1980's (probably long before Calrog was born).  Georgia is one of the states where every US route is a state route overlap, so I suspect it had to do with that.

I ran across this during the time of peak viatology, which is why I noticed it, but I said nothing so as to avoid pouring gasoline on the flames.

Quote from: 1995hoo on June 23, 2022, 11:12:12 AM
Quote from: J N Winkler on June 23, 2022, 01:11:50 AMI don't say anything unless it cannot be avoided, but it bothers me when civilians use the term highway as a synonym for freeway in a way that suggests they think non-freeways cannot be highways.  "I-135 or US 77?  I'll take the highway."

Ehhh, that doesn't bother me at all because I think it's in the nature of a regionalism, much like the "expressway" versus "freeway" issue that annoys some people on this forum. I'm sure part of my view of that is because "freeway" is not a term we generally use in this part of the country unless it's part of a road's name (e.g., the Whitehurst Freeway in DC). I once saw one of those polls on regionalisms–you know, the sort of poll that asks whether you say "soda," "pop," or "Coke," whether you say "water fountain," "drinking fountain," or "bubbler," whether it's a "shopping cart" or a "buggy," etc.–and the poll asked something like, "What do you call the type of road with no traffic lights and no intersections where you go to drive faster than you can on other roads?" I think the choices were "highway," "freeway," "expressway," and maybe "turnpike" (or perhaps "something else" instead of "turnpike"). Around here, the term "highway" is definitely the term normally used for that sort of thing. Not just here, either; I recall in 1996 when Hurricane Fran did a number on North Carolina, one of my classmates was griping that "751 was blocked by downed trees, so I had to take the highway this morning" ("the highway" referring to US-15/501, which was and is what some people call a "freeway" from the area where she lived–near where South Square Mall used to be–up to, and beyond, the area where Duke is).

Yes--it's very much a regional usage.  I don't really object to others, such as urban freeways being described as "expressways" in areas where that has traditionally been part of their names, or "the [route number]" in reference to freeways in southern California.  I think what pushes on me is the (admittedly remote) possibility of blowback if I use the term highway in reference to roads that are not freeways and my interlocutors then think I did them an injury by pointing them to facilities of inferior standard.

Quote from: 1995hoo on June 23, 2022, 11:12:12 AMNow, with all that said, I find it somewhat annoying when people who are not from this area use out-of-area regionalisms to refer to roads around here and expect us to know what they mean. I once saw something where someone referred simply to "the Tollway." That's not a term we use here and it wasn't clear what he meant; it turned out he was referring to the Dulles Toll Road. Similarly, I saw someone referring to the "HP" being out on a given road. People asked what in the world he meant and it turned out he meant "Highway Patrol," which is also not a term we use.

I've often wondered if the Highway Patrol/State Police divide has to do with whether a state police agency was originally founded specifically to patrol the state highway system.  This distinction would seem to hold for the Kansas Highway Patrol, Oklahoma Highway Patrol, Ohio State Highway Patrol (all founded during the Depression as motor patrol agencies), as well as the Massachusetts State Police (predecessor agency was founded 1865) and the Michigan State Police (founded 1917 to maintain internal order during World War I), with the Virginia State Police (originally a DMV constabulary) being somewhat of an exception.

To throw in one more wrinkle, in Texas it is the State Troopers (I am sure the term is not exclusive to Texas). 
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: ethanhopkin14 on June 28, 2022, 05:11:01 PM
I also hate it when people use interstate in place of a US highway or for a any type of freeway.  I have actually heard it multiple times.  US-59 (pre I-69 days) was I-59 in Houston despite the real I-59 terminating a state over. Just this past year I was at a field visit north of Amarillo for a site for work and one of the people running the meeting crested the hill of the project where you could see US-87/287 in the distance said" see, look, there is the interstate" despite the fact he called it US-87 not five minutes earlier. 


I have had arguments with my dad about I-37 in Texas.  He says since it doesn't leave Texas, it shouldn't be called interstate and I say its a classifications describing the system.  That is never good enough. 


To the regional terminology thing (expressway vs. freeway) I never knew until about ten years ago that an expressway had traffic lights and at grade intersections on it.  All the expressways I knew my whole life were freeways and even some being interstate highways so they never were anything less than a freeway.  Central Expressway in Dallas, MoPac Expressway in Austin and Pan Am Expressway in San Antonio were the only expressways I knew for the longest time and they all were full freeways (I know Central Expressway has a surface street section south of I-345, but no one has ever cared about that stretch; when you say Central Expressway you are talking about the part from Woodall Rodgers to the Oklahoma State Line.)
Title: Re: Things non-roadgeeks get wrong about roads that bother you
Post by: kphoger on June 28, 2022, 05:17:40 PM
I've actually heard the opposite before.

My wife and I got married in Branson, but we lived in the Chicago suburbs before that and were moving to southern Illinois.  A couple of weeks before the wedding, we got a moving truck and hauled our stuff down into our house in southern Illinois.  Then she went on to Branson to get things ready for the wedding, while I caught Greyhound back to the Chicago area so I could work for another 1½ weeks, living out of a backpack.  After I was done working, I hitchhiked back down to southern Illinois, where my wife met me.  We stayed the night at our new house before heading over to Branson together.  (Confused yet?)

Anyway, the hitchhiking sign I'd made had the shape of a big thumb sticking up at one end.  I drew a "hitchhiking thumb" there, then added an I-57 shield in the rectangle part, and wrote "Getting Married" as the main text.

My wife's sister rode with her out to meet me in southern Illinois.  My last ride dropped me off at the nearest Interstate exit, where my wife and her sister were waiting for me.  I later heard my sister-in-law describe my hitchhiking sign to someone, and she talked about how I had drawn a "US Route 57 sign" on it.

I didn't correct her.