AARoads Forum

National Boards => General Highway Talk => Topic started by: Molandfreak on April 28, 2013, 03:44:27 AM

Title: Streets and highways with similar names confusingly close to each other
Post by: Molandfreak on April 28, 2013, 03:44:27 AM
Anyone notice the same street names or highway numbers appearing close to each other?

Aside from first, second, third, I've noticed these duplicated names in Northfield and it's suburb Dundas, Minnesota.

Forest Avenue: This appears in Northfield where Third Street curves south of the grid pattern in town. A different Forest Avenue also appears on the west side of Dundas.

North St./Ave. In Northfield, North Avenue straddles the county line and is the road to the hospital. In Dundas, there is a minor road with the name North Street.

Another oddity is Northfield's league of Jeffersons. It contains Jefferson Parkway, Jefferson Road, Jefferson Drive, Jefferson Lane, and the forgotten Jefferson Place. At least two of these are a result of land annexations in the 1970s, where Northfield did not want to rename the roads.

Another oddity on different lines exists in the Lakeville, MN area, where Credit River Township is normally addressed to Lakeville. Credit River lies in eastern Scott County, whereas Lakeville is in western Dakota County. Thus, you have to travel west for an address of 185th Street East in Lakeville.

Near Redwood Falls, Minnesota state highway 19 and Redwood county road 19 intersect.

In Anoka county, MN, county road 10 replaced old U.S. 10 for part of it's length. The two roads confusingly intersect.

For all practical purposes, WV 7 and OH 7 also intersect near Hannibal, OH and New Martinsville, WV.

And who could forget that AZ-95 and U.S. 95 intersect in Quartzsite, AZ...

Also, the two I-395s that exist in Baltimore and D.C, the same CSA and virtually the same metro.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: dfilpus on April 28, 2013, 09:22:13 AM
US 360 and VA 360 intersect twice. At the eastern intersection, there are banners that say "US" and "State" above the shields.
US 74/I 74 in NC multiplex. NC 73 intersects with I 73.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: mgk920 on April 28, 2013, 10:31:31 AM
All of the 'Peachtrees' in the Atlanta area?

:meh:

Mike
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on April 28, 2013, 10:54:55 AM
There is a Virginia Avenue in the City of Falls Church, Virginia. Less than three miles away in Fairfax County there is an entirely different street also named Virginia Avenue. But to make it worse, the postal address for the one in the county is also "Falls Church, VA," even though it's outside the city limits (this is, as we all know, quite common).

I work with a guy who lives on the one in the county and he says even something as routine as getting a pizza delivered is a massive nuisance because the pizza guys are always going to the wrong Virginia Avenue.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: The High Plains Traveler on April 28, 2013, 11:42:17 AM
Minneapolis has four street quadrants, plus the downtown area that bends the streets just to mix things up. Each has numbered streets and avenues, distinguished only by the prefix or suffix (they can't even be consistent there). Streets on one side of the river go east-west, and north-south on the other side.

Phoenix has numbered streets on one side of downtown, numbered avenues on the other. They all go north-south.

In Colorado Springs, nearly every street is named Cheyenne.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: colinstu on April 28, 2013, 11:44:06 AM
There's "Moreland Blvd" and "Moorland Road" in Milwaukee/Waukesha. Heading west on I-94, Moreland is an entire 1 EXIT AFTER Moorland... can be quite confusing to describe to people at times. The Road and Blvd part is commonly dropped from the name too.

EDIT: There is also "Layton Blvd" that runs N-S through the southside (is basically 27th st) and there's "Layton Ave" which runs E-W even more south.

EDIT 2: A number of streets in the burbs of Chicago (Arlington heights anyways) are all named after trees. That's quite obnoxious.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Alps on April 28, 2013, 03:55:34 PM
Burnt Mill Rd. at Burnt Mills Rd.
Google: http://goo.gl/maps/yfI2V
Site: www.alpsroads.net/roads/nj/cr_641
(Note: zooming in, it seems that Burnt Mill (incorrectly labeled as another Mills) changes to Cowperthwaite. I have been there. That is a Google Mapsism.)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Brandon on April 28, 2013, 04:20:04 PM
Locally, Division Street.  There are three in easy driving distance and close to each other.

1. Division Street Lockport - on both sides of the Des Plaines River and goes by Stateville Road and 163rd Street.  Exists by the name "Division Street" in Lockport, Crest Hill, and Joliet.

2. Division Street Joliet - small east-west street near the Des Plaines River in Joliet, between Bridge Street and Ruby Street.  Turns into an alley west of Center Street (US-30).

3. Division Street Plainfield - Illinois 59 through Plainfield.  Crosses the latitude of Division Street Lockport, but Division Street Lockport ends two miles east.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: CentralCAroadgeek on April 28, 2013, 05:54:58 PM
I already made a thread like this months ago (with a similarly-long title), but I'll add some things from there...

Capitol Avenue and Capitol Expressway in San Jose.

Market Street and Market Way, & Tuscany Circle, Tuscany Avenue, and Tuscany Boulevard here in Salinas.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: signalman on April 28, 2013, 07:44:17 PM
In my town there's Mount Hope Road and Mount Hope Avenue.  Both are county maintained, but two completely different roadways.  People not from the area, often delivery truck drivers, think they're one and the same (ie. they are looking for an address located on Mount Hope Road, but traveling on Mount Hope Ave. looking for it).  As an added bonus to make it somewhat confusing for outsiders, Mount Hope Ave ends at Mount Hope Road.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: jp the roadgeek on April 28, 2013, 08:47:18 PM
In my town, there is a Flanders St, and a Flanders Rd.  Street runs E-W, and Road runs N-S.  Street's east end is at Road.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: tdindy88 on April 28, 2013, 09:20:22 PM
I pointed this out on the I-69 in Indiana thread, but southwest of Bloomington there is an intersection between "W." Leonard Springs Road and "S." Leonard Springs Road. Take out the direction and Leonard Springs Road has a three-way intersection with itself.

Here's a look at the intersection: https://maps.google.com/maps?q=Bloomington,+IN&hl=en&ll=39.121671,-86.591041&spn=0.004678,0.010568&sll=42.391009,-85.869141&sspn=9.118587,21.643066&oq=Bloomington,+IN&t=h&hnear=Bloomington,+Monroe,+Indiana&z=17

Also in Bloomington, there is a Rogers Street and a Rogers Road, though they don't intersect with each other.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: allniter89 on April 28, 2013, 10:01:14 PM
There are two Shady Lanes' within five miles in the Fort Walton Beach, FL. They do not intersect but they're both off the same major street (Beal Pkwy-Lewis Turner Blvd). I've also had the problem of delivery people going to the wrong Shady Lane  :banghead:
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: WNYroadgeek on April 29, 2013, 01:00:30 AM
US 15 and NY 15 in Corning/Painted Post, even though the latter is only signed there (it's southern terminus has always been at I-390 in Wayland, despite the aforementioned signage indicating otherwise).

It won't be like that for long, though, as NYSDOT is in the process of removing all NY 15 signage south of Wayland.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: mgk920 on April 29, 2013, 12:03:46 PM
In Madison, WI, there are two streets named 'King' that radiate outward from the Capitol Square, one block apart at the square.

The pizza guys really do have it tough here in the Appleton area, as there are multitudes of different munis that cover the area's relatively small population (about 230K), including three counties for some of the unincorporated parts, each with their own street naming and addressing grids and with numerous duplicating street names, many in close (as in just a few blocks) proximity to each other and some with duplicating valid address number ranges.

It is a real mess.

:banghead:

Mike
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: vdeane on April 29, 2013, 12:29:56 PM
Quote from: WNYroadgeek on April 29, 2013, 01:00:30 AM
US 15 and NY 15 in Corning/Painted Post, even though the latter is only signed there (it's southern terminus has always been at I-390 in Wayland, despite the aforementioned signage indicating otherwise).

It won't be like that for long, though, as NYSDOT is in the process of remove all NY 15 signage south of Wayland.
Plus NY 15 was the only example of a "state extension" of a US route (at least in NY, though I can't think of any other states that did such a thing).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Takumi on April 29, 2013, 12:56:14 PM
^ Virginia did and still has a few. VA 33 is the most notable, but there are/have been several others.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: agentsteel53 on April 29, 2013, 01:09:54 PM
north San Diego's road names all seem to be taken from the set of Carmel, Mira, Torrey, Sorrento, Mesa, and Valley.  on CA-56, there is a guide sign for the next three exits: Carmel Mountain, Carmel Valley, and Carmel Creek. 
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: NE2 on April 29, 2013, 01:27:26 PM
http://maps.google.com/maps?ll=28.669607,-81.330843&spn=0.008585,0.016512&gl=us&t=m&z=17&layer=c&cbll=28.669527,-81.330859&panoid=0xb_5cq2bKv7FazGNh2ghg&cbp=12,51.94,,2,1.9
If you turn 180 degrees you'll see another sign with the same name repeated. Officially two of them are North and South Triplet Lake (and that's written inside the arrow).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Henry on April 29, 2013, 02:10:34 PM
Quote from: mgk920 on April 28, 2013, 10:31:31 AM
All of the 'Peachtrees' in the Atlanta area?

:meh:

Mike
Or the Capitol Streets in Washington, DC?
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: briantroutman on April 29, 2013, 02:23:21 PM
I-283 and PA 283 in Harrisburg.

Trying to explain to people "you have to take the exit from Interstate 283 onto state route 283" was always an annoyance and led to a great deal of confusion. I always thought that the 283-283 interchange should be reconfigured to treat the Harrisburg-Lancaster route as continuous–and then renumber the entire length as I-383.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: NE2 on April 29, 2013, 03:46:06 PM
Quote from: briantroutman on April 29, 2013, 02:23:21 PM
I-283 and PA 283 in Harrisburg.

Trying to explain to people "you have to take the exit from Interstate 283 onto state route 283" was always an annoyance and led to a great deal of confusion.

How is it any different from "you have to take the exit from I-83 onto I-83"?
(https://www.aaroads.com/northeast/pennsylvania080/i-083_nb_exit_041a_01.jpg)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: briantroutman on April 29, 2013, 04:00:18 PM
Quote from: NE2 on April 29, 2013, 03:46:06 PM
How is it any different from "you have to take the exit from I-83 onto I-83"?

At least in that instance, the right lane is dedicated to I-83, so it functions more as a left lane exit for 581 (and it's signed that way).

But that interchange is also a terrible configuration and is in the process of being reconstructed.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: vdeane on April 30, 2013, 11:22:41 AM
Looking at that interchange, it is plain as day that I-83 to PA 581 is the intended through movement.  Also keep in mind with PA 283, that the interchange is right before the Turnpike, and as such there is no conflicting I-283 signage to speak of.  It's a simple TOTSO (for people who don't know about unsigned interstates, which is 99.9% of drivers), and those aren't uncommon in this part of the country.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: myosh_tino on April 30, 2013, 02:00:36 PM
Santa Barbara, CA...

* Castillo Street
* Carrillo Street
* Cabrillo Street

Interesting Notes
- All three roads have interchanges with US 101 (Cabrillo - Exit 94C, Castillo - Exit 97, Carrillo - Exit 98A) with Castillo and Carrillo being consecutive exits.
- Castillo and Carrillo intersect 1 block east of US 101
- Castillo and Cabrillo intersect down by the waterfront.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Mr_Northside on April 30, 2013, 03:51:53 PM
Quote from: vdeane on April 30, 2013, 11:22:41 AM
Looking at that interchange, it is plain as day that I-83 to PA 581 is the intended through movement. 

I'd say that's only half-right.  I'd think it's right for I-83 South to PA-581 West, where the Capitol Beltway is that roadway's thru movement, and I-83 exits itself.  I'd say there is no "intended thru movement" heading north on I-83 (as shown in the pic a couple posts above), since that roadway ends.  You simply figure out which way you want to go on the "Capitol Beltway", and choose the appropriate lane.
That's not to say that every highway ending at another highway follows that paradigm, some are engineered to clearly have an intended thru movement.  (IMO, the fairly recent interchange reconstruction of where US-15 ends @ I-86 in Painted Post, NY seems to favor the movement to I-86 westbound.... possibly for an extension of I-99 to Rochester sometime in the future). 
Though I think a lot of trumpets (especially old ones, like the I-83/PA-581 in question) simply end that road, with no intended  thru movement.  Even if one set of ramps continues a route, or gets the lions' share of the traffic.

-More on topic-
There are a handful of streets in Pittsburgh that have pretty close names. In just the Golden Triangle (downtown) there are seperate Streets & Avenues that use the same number.  (EX: A 6th St. in VERY close proximity, but not connecting to 6th Ave.).  Since downtown isn't a real grid, I'd have to imagine this trips a lot of people up.

Some of the consolidation / annexation has resulted in similar streets in the city as well; I'd imagine the biggest example is having Liberty Ave (A very prominent street from downtown to Bloomfield), and a West Liberty Ave, from the southern portals of the Liberty Tunnels, to (and through) the borough of Dormont (which carries Truck US-19).
There's a Main St. in Bloomfield & Lawrenceville neighborhoods, and a South Main St. near the West End Bridge.
There's a handful of smaller streets that are very close in names and potentially confusing as well throughout the city...

I'm not sure how much the average motorist (or even visiting driver) gets screwed up by these, but I know they want to do something about it for 911 purposes.  There have been some instances where emergency vehicles were sent to the wrong street.

*These are all just within the city limits of Pittsburgh.  The other 120+ municipalities in Allegheny County reuse many names found in the city.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Pete from Boston on April 30, 2013, 04:18:18 PM
Oh, Boston is notorious for duplicated street names.  It is part of the madness that passes for local color here.  There are several Washington Streets -- one in Brighton, one from Downtown to the Rhode Island line, one in Dorchester, one in Charlestown... and an unconnected North Washington St in the North End. 

There is Harvard St., which becomes Harvard Ave., which ends and picks up again some ways away as North Harvard St. 

There are several Broadways, and more of all of these once you start including adjoining municipalities.  I'm sure it's all been covered before.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: NE2 on April 30, 2013, 04:25:17 PM
Quote from: Pete from Boston on April 30, 2013, 04:18:18 PM
and an unconnected North Washington St in the North End. 
Which used to connect. It's presumably North Washington because they didn't want to redo the addresses on just plain Washington when they renamed Charlestown Street.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Pete from Boston on April 30, 2013, 04:26:42 PM
I once got rear-ended on a ramp from the Washington Bridge to I-95 in Manhattan.  Guess how many explanations of this did not result in someone thinking I was coming off the George Washington Bridge half a mile away (answer: zero).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: sdmichael on April 30, 2013, 04:45:30 PM
SR-125 has consecutive exits for Jamacha Road and Jamacha Blvd in Spring Valley, near San Diego.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: lordsutch on May 01, 2013, 04:00:17 AM
Memphis is pretty bad in this regard.  Notable examples:

Perkins Road and Perkins Extended (which parallel each other)
Kirby Road and Kirby Parkway (sometimes the same physical roadway, sometimes not); plus Kirby-Whitten Parkway, the logical extension of Kirby Parkway but with a two-mile gap through Shelby Farms.
Bartlett Road (which doesn't go to Bartlett) and Bartlett Boulevard (which is what Bartlett calls Sycamore View Road)
Old Brownsville Road and New Brownsville Road, neither of which seem to go to Brownsville
Brunswick Road and New Brunswick Road
Poplar Avenue and Poplar Pike
Union Avenue and Union Extended
Old Allen Road and New Allen Road
Covington Pike and New Covington Pike

They did fix one, about a decade ago: Germantown Road and Germantown Extended (now Riverdale Road).

Honorable mention: a rerouted section of Raleigh-Millington Road is Ramill Road. Someone in planning must have thought they were being really clever that day. Or, more likely, the computer wouldn't accept "New Raleigh-Millington Road" because it was too long and/or silly.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: elsmere241 on May 01, 2013, 08:44:47 AM
https://maps.google.com/maps?q=North+Antlers+Place,+Bear,+DE&hl=en&ll=39.606215,-75.721767&spn=0.002052,0.004128&sll=39.145251,-75.386656&sspn=4.229828,8.453979&oq=antlers+place&hnear=N+Antlers+Pl,+Bear,+New+Castle,+Delaware+19701&t=m&z=19
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on May 02, 2013, 11:02:36 AM
I'm sure we've had this conversation before, because I remember telling this story on here before....

I work in the dispatch office at a cable contractor company.  One day, we got a call from Cox (our "parent"), wondering why an install tech hadn't shown up for a customer's installation yet, something like two hours after their scheduled timeframe.  I looked at our WO tracking program, and it showed that he had already completed the installation.  So, yeah, I called the guy up to find out what was going on (he wasn't the most honest guy in the company).

For some reason, Wichita decided it would be a good idea to have Minnesota Street one block over from Minneapolis Street!  Did that not throw up a red flag in anyone's mind at the time?  (see http://goo.gl/maps/jYLLG (http://goo.gl/maps/jYLLG))

So our tech had arrived at the right house number on the wrong street.  The resident there then let him in her house and install Cox cable service.  Later, once we figured out what had happened, he had to go back out there, disconnect her service (while she was pissed off, yelling at him for unhooking it again), go over to the actual customer's house and hook her service up.

Won't make that mistake again!

I've also come across a Spanish-speaking customer who had called Cox to set up service.  He lived on Matthewson Street, but his order was set up for Madison Street.  Since he didn't speak English, I'm assuming he had talked to a Spanish-speaking customer service rep, who assumed he had said Madison with a Spanish accent (the letter d is pronounced similar to the English th).  Matthewson>Mathison>Madison.  Fortunately, those two streets are not as near each other.  It did make getting directions rather interesting, before I figured out what the problem was.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: elsmere241 on May 02, 2013, 11:08:24 AM
Quote from: lordsutch on May 01, 2013, 04:00:17 AM
Honorable mention: a rerouted section of Raleigh-Millington Road is Ramill Road. Someone in planning must have thought they were being really clever that day. Or, more likely, the computer wouldn't accept "New Raleigh-Millington Road" because it was too long and/or silly.

Our county police's CAD system is limited to eighteen characters for the core street name.  So we have several streets in our various systems with truncated names.  ("Elizabeth Sweetbriar Lane" is "ELIZABETH SWEETBRI LA".)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: jwolfer on May 03, 2013, 04:30:58 PM
Quote from: mgk920 on April 28, 2013, 10:31:31 AM
All of the 'Peachtrees' in the Atlanta area?

:meh:

Mike

Jacksonville has the "Baymeadows" 
The main one is Baymeadows Rd ( SR 152) which has exits from I-95 and I-295.

Baymeadows Road East, Baymeadows Way, Baymeadows Circle East, Baymeadows Circle West, Baymeadows Way West,  and I think there are more... not to mention Bayberry dr, Baypine rd all in the same area.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on May 03, 2013, 08:27:59 PM
Quote from: elsmere241 on May 02, 2013, 11:08:24 AM
Quote from: lordsutch on May 01, 2013, 04:00:17 AM
Honorable mention: a rerouted section of Raleigh-Millington Road is Ramill Road. Someone in planning must have thought they were being really clever that day. Or, more likely, the computer wouldn't accept "New Raleigh-Millington Road" because it was too long and/or silly.

Our county police's CAD system is limited to eighteen characters for the core street name.  So we have several streets in our various systems with truncated names.  ("Elizabeth Sweetbriar Lane" is "ELIZABETH SWEETBRI LA".)

The primary program I use at work truncates first names to ten letters.  When I first started, I wondered why so many people were named Christophe.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on May 03, 2013, 08:33:04 PM
kphoger, your cable account does sound familiar as to right number/wrong street. But I can't recall the thread either.




As to name truncation, any of you guys read Gordon Korman's Bruno & Boots books when you were growing up? Great stuff. In The War with Mr. Wizzle, Wizzle demands that Wilbur Hackenschleimer change his name to Wilbur Hacken because his name is too long for the computer.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: hm insulators on May 06, 2013, 03:52:19 PM
Verdugo Road and Verdugo Boulevard intersect in a small Los Angeles suburb called Montrose.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: txstateends on May 08, 2013, 06:31:39 PM
Quote from: mgk920 on April 28, 2013, 10:31:31 AM
All of the 'Peachtrees' in the Atlanta area?

:meh:

Mike

Was going to mention that, as well as the Ventura this, Ventura that, Ventura the other in the L.A. area.

Currently one of the few ubiquitous multiples locally is the many 'Preston' (or 'Preston'-influenced) roads or streets in north Dallas, Plano, and into Frisco.  Even though there are many, there seems to be little to no real confusion as to which is which.  The original Preston Road (the paved, modern version is signed TX 289 (which NONE of the locals call the road) from north Loop 12 up to the Lake Texoma area west of Sherman-Denison) actually pre-dates Dallas, as it has been an Indian path, cattle-driving trail, and important early road for settlers.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on May 08, 2013, 10:14:44 PM
While not exceedingly close to each other, Glen Ellyn and Lombard (Illinois) each have a north-south Main Street.  I remember there being the same brand of pizza place on both of them; people would frequently call in a pizza order at the one on, say, Main Street Glen Ellyn, then drive over to the one on Main Street Lombard and wonder why their order wasn't there.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Pete from Boston on May 09, 2013, 12:30:36 PM
Quote from: hm insulators on May 06, 2013, 03:52:19 PM
Verdugo Road and Verdugo Boulevard intersect in a small Los Angeles suburb called Montrose.

Wow, what an awful name.  Verdugo = executioner!
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: getemngo on May 09, 2013, 06:45:10 PM
Hastings, Michigan has a State Road and a State Street. They are parallel, 5 blocks apart, and west of Broadway, State Rd is old M-37 and State St is current M-37. Even worse, State Rd is the baseline for north-south Barry County addresses, but State St is the baseline for north-south City of Hastings addresses.

M-222 used to be numbered M-118. It's on 116th Ave, one mile from 118th Ave. MDOT wised up to this one, but usually they don't. There's US 24/M-24 confusion, and M-96 (not to be confused with I-96) right by I-94.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Molandfreak on May 09, 2013, 08:33:18 PM
Quote from: Pete from Boston on May 09, 2013, 12:30:36 PM
Quote from: hm insulators on May 06, 2013, 03:52:19 PM
Verdugo Road and Verdugo Boulevard intersect in a small Los Angeles suburb called Montrose.

Wow, what an awful name.  Verdugo = executioner!
:wow:
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on May 11, 2013, 12:24:37 PM
Quote from: getemngo on May 09, 2013, 06:45:10 PM
Hastings, Michigan has a State Road and a State Street. They are parallel, 5 blocks apart, and west of Broadway, State Rd is old M-37 and State St is current M-37. Even worse, State Rd is the baseline for north-south Barry County addresses, but State St is the baseline for north-south City of Hastings addresses.

Property values on those roads should be lower, due to the potential for emotional trauma.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cpzilliacus on May 11, 2013, 12:47:16 PM
Quote from: Henry on April 29, 2013, 02:10:34 PM
Quote from: mgk920 on April 28, 2013, 10:31:31 AM
All of the 'Peachtrees' in the Atlanta area?

:meh:

Mike
Or the Capitol Streets in Washington, DC?

At least the Capitol Streets are always referred to with a prefix - there's North Capitol Street, East Capitol Street and South Capitol Street. 

No West Capitol Street - had there been one, it would run down the middle of the National Mall.

But D.C. also duplicates street names in some instances, even though they are far from each other and have nothing to do with each other.

Three cases in point:

There's a Porter Street, N.W. (https://maps.google.com/maps?q=34th+street,+n.w.+%26+porter+street,+n.w.,+washington,+d.c.&hl=en&sll=38.934944,-77.060595&sspn=0.018661,0.038581&t=h&hnear=34th+St+NW+%26+Porter+St+NW,+Washington,+District+of+Columbia+20016&z=16), which is a relatively major street, since it provides access to Rock Creek Park, and to another street (Klingle Road) that crosses the park.  But inexplicably, there's a dead-end Porter Street, N.E. (https://maps.google.com/maps?q=florida+avenue,+n.e.+%26+porter+street,+n.e.,+washington,+d.c.&hl=en&ll=38.910871,-77.004805&spn=0.009333,0.01929&sll=38.937335,-77.066393&sspn=0.00933,0.01929&t=h&hnear=Florida+Ave+NE+%26+Porter+St+NE,+Washington,+District+of+Columbia+20002&z=16), which has nothing to do with the other Porter Street (as an aside, it happens to dead-end right at the SiriusXM complex).

These two have been identified more than once with incorrectly dispatched police/fire/EMS calls for service by D.C.'s 911 center (they are about as far apart as it is possible to be and still stay in D.C.):

Chesapeake Street, N.W. (https://maps.google.com/maps?q=Chesapeake+Street,+n.w.+and+Wisconsin+Avenue,+n.w.+washington,+d.c.&hl=en&sll=38.910871,-77.004805&sspn=0.009333,0.01929&t=h&hnear=Wisconsin+Ave+NW+%26+Chesapeake+St+NW,+Washington,+District+of+Columbia+20016&z=16) and Chesapeake Street, S.E./S.W. (https://maps.google.com/maps?q=Chesapeake+Street,+s.e.+and+South+Capitot+Street,+s.e..+washington,+d.c.&hl=en&sll=38.951054,-77.080767&sspn=0.009328,0.01929&t=h&hnear=South+Capitol+St+SW+%26+Chesapeake+St+SE,+Washington,+District+of+Columbia+20032&z=16)

Brandywine Street, N.W. (https://maps.google.com/maps?q=Brandywine+street,+n.w.+and+Wisconsin+Avenue,+n.w.+washington,+d.c.&hl=en&ll=38.949664,-77.080379&spn=0.009328,0.01929&sll=38.951054,-77.080767&sspn=0.009328,0.01929&t=h&hnear=Wisconsin+Ave+NW+%26+Brandywine+St+NW,+Washington,+District+of+Columbia+20016&z=16) and Brandywine Street, S.E./S.W. (https://maps.google.com/maps?q=Brandywine+street,+s.e.+and+south+capitol+street,+s.e.+washington,+d.c.&hl=en&sll=38.949664,-77.080379&sspn=0.009328,0.01929&t=h&hnear=South+Capitol+St+SW+%26+Brandywine+St+SE,+Washington,+District+of+Columbia+20032&z=16)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on May 11, 2013, 01:01:46 PM
Actually, I've seen references to "Capitol Street" without the "prefix" quite a few times, even in the Washington Post (an article referred to Nationals Park being located on "Capitol Street"). Some people must assume it's like a standard prefix that people usually omit (streets across the river in Alexandria are a good example or a place where people omit the prefix) when in fact the "prefix" is more an essential part of the name.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: andrewkbrown on May 11, 2013, 03:19:13 PM
Yes, Washington DC has many, several have been mentioned.

Just last week, my engine company was sent to Morris Road SE, when the incident was on Morse Street NE. Dispatch often mistakes locations if someone reports an incident at one of these similar sounding streets, without specifying (or themselves confusing) "Street", Road", etc. Same goes for Warder Street MW and Water Street NW/SW.

Many streets in DC have the same name, and are known as "Street", "Place", "Drive", or "Terrace". And they can be found in different sections of the city. Madison Drive NW runs along the northern part of the National Mall. Madison Place NW is approx. 5 miles north in the Brightwood neighborhood, and Madison Street NW is one block further north.

My company has been sent to 119 D Street NW (a homeless shelter) for a call once when the incident was actually at 119 D Street NE (U.S. Capitol Police Headquarters).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: roadman65 on May 12, 2013, 10:58:46 AM
I pointed this out years ago on another thread, but you have two different Springfield Avenues in the Township of Springfield, NJ.  In fact both Springfield Avenues have Meisel Avenue connecting between the two segments that should really all be named Springfield Avenue for one continuous street.

Then nearby in Summit, NJ you have a Morris Avenue that is partly CR 527 and in Springfield, NJ you again have Morris Avenue also on part of CR 527, but for some reason the City of Summit decides to call the remaining part of CR 527 near the Springfield Border  as Springfield Avenue as another Springfield Avenue (not related to the one in Springfield as previous) intersects CR 527 less than a mile from the Summit/ Springfield Line.  This discontinuous part is technically the continuation of it, even though Morris Avenue would be more logical as no turns are made going along CR 527 (at least NB anyway) between the two Morris Avenues.  In other words you must make a left turn heading east on Summit's Springfield Avenue to continue only to have it end in a very short distance to return to the name it took over at  the turning point.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cpzilliacus on May 12, 2013, 12:43:59 PM
Quote from: 1995hoo on May 11, 2013, 01:01:46 PM
Actually, I've seen references to "Capitol Street" without the "prefix" quite a few times, even in the Washington Post (an article referred to Nationals Park being located on "Capitol Street"). Some people must assume it's like a standard prefix that people usually omit (streets across the river in Alexandria are a good example or a place where people omit the prefix) when in fact the "prefix" is more an essential part of the name.

I know that when I was working on some new geographic information system software about 15 years ago (when the technology was very new), it could not handle an address on South Capitol Street, S.E. (for example), because it thought that was two prefixes (even thought S.E. is written after).

And there are folks from out-of-town that do not know (or have not learned).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cpzilliacus on May 12, 2013, 01:18:20 PM
Quote from: andrewkbrown on May 11, 2013, 03:19:13 PM
Yes, Washington DC has many, several have been mentioned.

Just last week, my engine company was sent to Morris Road SE, when the incident was on Morse Street NE. Dispatch often mistakes locations if someone reports an incident at one of these similar sounding streets, without specifying (or themselves confusing) "Street", Road", etc. Same goes for Warder Street MW and Water Street NW/SW.

That's a good example with potentially catastrophic consequences. 

Had not thought about Warder Street (https://maps.google.com/maps?q=Warder+Street,+n.w.+washington+dc&hl=en&sll=38.928868,-77.019224&sspn=0.018662,0.038581&t=h&gl=us&hnear=Warder+St+NW,+Washington,+District+of+Columbia&z=16) (which is one of those D.C. streets that does not follow the "normal" pattern of the D.C. street grid). 

Water Street is also a potential problem, as it extends in discontinuous segments from Southeast (https://maps.google.com/maps?q=Water+Street,+s.e.+%26+M+Street,+S.E.+washington+dc&hl=en&sll=38.876635,-76.980643&sspn=0.018676,0.038581&t=h&gl=us&hnear=M+St+SE+%26+Water+St+SE,+Washington,+District+of+Columbia+20003&z=16) (east of the I-695 11th  Street bridge), in at least two pieces along the Southwest waterfront (here (https://maps.google.com/maps?q=Water+Street,+s.w.+%26+T+Street+S.W.+washington+dc&hl=en&ll=38.867296,-77.010126&spn=0.009339,0.01929&sll=38.867213,-77.010427&sspn=0.009339,0.01929&t=h&gl=us&hnear=T+St+SW+%26+Water+St+SW,+Washington,+District+of+Columbia&z=16) and here (https://maps.google.com/maps?q=Water+Street,+s.w.+%26+6th+Street+S.W.+washington+dc&hl=en&ll=38.876935,-77.02167&spn=0.009338,0.01929&sll=38.867296,-77.010126&sspn=0.009339,0.01929&t=h&gl=us&hnear=6th+St+SW+%26+Water+St+SW,+Washington,+District+of+Columbia+20024&z=16)) and then that part along the Georgetown waterfront (https://maps.google.com/maps?q=Water+Street,+n.w.+%26+Potomac+Street+N.W.+washington+dc&hl=en&sll=38.903109,-77.065039&sspn=0.001167,0.002411&t=h&gl=us&hnear=Potomac+St+NW+%26+Water+St+NW,+Washington,+District+of+Columbia+20007&z=16) under U.S. 29 (Whitehurst Freeway).

And there's Potomac Street, N.W. (https://maps.google.com/maps?q=potomac+Street,+n.w.+washington+dc&hl=en&sll=38.932523,-77.020426&sspn=0.009331,0.01929&t=h&gl=us&hnear=Potomac+St+NW,+Washington,+District+of+Columbia+20007&z=16) which is far from Potomac Avenue, S.E. (https://maps.google.com/maps?q=potomac+Avenue,+s.e.+washington+dc&hl=en&ll=38.880944,-76.98369&spn=0.009337,0.01929&sll=38.905366,-77.065188&sspn=0.009334,0.01929&t=h&gl=us&hnear=Potomac+Ave+SE,+Washington,+District+of+Columbia+20003&z=16)

Quote from: andrewkbrown on May 11, 2013, 03:19:13 PM
Many streets in DC have the same name, and are known as "Street", "Place", "Drive", or "Terrace". And they can be found in different sections of the city. Madison Drive NW runs along the northern part of the National Mall. Madison Place NW is approx. 5 miles north in the Brightwood neighborhood, and Madison Street NW is one block further north.

My company has been sent to 119 D Street NW (a homeless shelter) for a call once when the incident was actually at 119 D Street NE (U.S. Capitol Police Headquarters).

A college buddy of mine was a cadet and dispatcher (yes, some cadets were asked to dispatch calls) for the Metropolitan Police Department (MPDC, D.C.'s municipal police force) back in the 1970's.  At the time, MPDC dispatcher training included a lot of indoctrination about the many duplications, exemptions and variations around the D.C. street network.  And it was generally not as much of a problem for city police dispatchers (as it was and is for fire/EMS dispatchers), since the police districts do not cover the entire city (and only the First District, or "1D," covers all four quadrants of the city). 
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on May 12, 2013, 01:47:47 PM
Quote from: cpzilliacus on May 12, 2013, 01:18:20 PM
....

And there's Potomac Street, N.W. (https://maps.google.com/maps?q=potomac+Street,+n.w.+washington+dc&hl=en&sll=38.932523,-77.020426&sspn=0.009331,0.01929&t=h&gl=us&hnear=Potomac+St+NW,+Washington,+District+of+Columbia+20007&z=16) which is far from Potomac Avenue, S.E. (https://maps.google.com/maps?q=potomac+Avenue,+s.e.+washington+dc&hl=en&ll=38.880944,-76.98369&spn=0.009337,0.01929&sll=38.905366,-77.065188&sspn=0.009334,0.01929&t=h&gl=us&hnear=Potomac+Ave+SE,+Washington,+District+of+Columbia+20003&z=16)

....

Then you have a street sign on Potomac Avenue across from Nationals Park that says it's Potomac Street, SW (sign was still there about a month ago the last time I went to a game)–to relate it further to this thread, it's at the intersection with South Capitol Street:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi31.photobucket.com%2Falbums%2Fc378%2F1995hoo%2FRoad%2520sign%2520pictures%2F18bba2d9.jpg&hash=990e4a976181e2bc5902e3505894352d79ebc5e7)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cpzilliacus on May 12, 2013, 05:58:28 PM
Quote from: 1995hoo on May 12, 2013, 01:47:47 PM
Then you have a street sign on Potomac Avenue across from Nationals Park that says it's Potomac Street, SW (sign was still there about a month ago the last time I went to a game)–to relate it further to this thread, it's at the intersection with South Capitol Street:

That is clearly incorrect - it should be Potomac Avenue, S.W.  (and S.E. too).

I even checked it against the District of Columbia's online GIS, confirming that the street sign is wrong.

I'll drop a note to a buddy of mine at DDOT, who I think can get it corrected.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on May 12, 2013, 08:11:08 PM
Quote from: cpzilliacus on May 12, 2013, 05:58:28 PM
Quote from: 1995hoo on May 12, 2013, 01:47:47 PM
Then you have a street sign on Potomac Avenue across from Nationals Park that says it's Potomac Street, SW (sign was still there about a month ago the last time I went to a game)–to relate it further to this thread, it's at the intersection with South Capitol Street:

That is clearly incorrect - it should be Potomac Avenue, S.W.  (and S.E. too).

I even checked it against the District of Columbia's online GIS, confirming that the street sign is wrong.

I'll drop a note to a buddy of mine at DDOT, who I think can get it corrected.

Indeed it is wrong. Until recently, a block away at 1st & Potomac SE (beyond the right field corner of the ballpark), the sign said "Potomac Ave St SE." Really! That was fixed last year.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cpzilliacus on May 13, 2013, 02:15:08 PM
Quote from: 1995hoo on May 12, 2013, 08:11:08 PM
Indeed it is wrong. Until recently, a block away at 1st & Potomac SE (beyond the right field corner of the ballpark), the sign said "Potomac Ave St SE." Really! That was fixed last year.

I had business in Southeast D.C. near there earlier today and snapped an image of that sign at Potomac Avenue, S.W. at South Capitol Street, which is still there (and still incorrect <smile>).

Just annotated that image and e-mailed it to a colleague of mine at DDOT, who will forward to the correct group within DDOT.

Thank you for pointing it out.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: apeman33 on May 16, 2013, 12:01:05 AM
Fort Scott, Kansas, has:
* Three National avenues. The original was just the north-south road curving east around 17th Street to go to National Cemetery No. 1 (thus it's name). However, the north-south route was extended south of 17th. Then when the U.S. 69 bypass was constructed, a diagonal was created beginning between 17th and 18th going southeast. This leaves you with National Avenue from the north city limits to South U.S. 69 where the bypass curves back to Main St., a National Avenue that extends from where the diagonal begins south to 19th St. that's really just a paved alley, and East National Ave., which leads from National at 17th to the National Cemetery.
* At least three Huntington Boulevards, none of which are actually a boulevard. I saw an old 1950s map once that made it appear as though Huntington Blvd. was intended to be a rectangle around the fairgrounds. All that ever came of it was the north-south stretch along the east side that goes from 19th to 23rd streets, a 1/2 block strip going east from the south National Ave. extension to the current National/U.S. 69 intersection, and another strip that goes west from Margrave St. a half block to dead end at the railroad tracks.

So not only are there all those confusing streets, but one of the Huntington Boulevards has its endpoints at TWO of the National Avenues.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Mark68 on May 16, 2013, 03:41:10 AM
The quadrants in Portland could lend to some confusion, especially to newcomers and tourists. The Willamette divides the eastern and western halves (as well as the northwest and north quadrants), and most of the N/S streets are numbered. So you have NE 1st Ave (there is no SE 1st Ave) and NW/SW 1st Ave on either side of the river.

The same quadrant system continues west into Washington County, and most of the county uses the NW & SW designations except Hillsboro. For instance, when traveling west on NW Cornell Rd, once you cross NW Cornelius Pass into the Beaverton numbering scheme, you are now on NE Cornell Rd.

This also happens to a lesser extent in Gresham, which has dual names for many of their arterial N/S streets. So, in Gresham, you have SE 212th Ave (using the Portland naming), which is also NW Wallula Ave (Gresham naming) cross paths with E/W NW 15th St (Gresham naming).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: jwolfer on May 17, 2013, 11:05:35 AM
I think that street grids like in Miami or Gainesville FL are really confusing for someone not familiar... is is   12th Ave or St is is NE, NW, SE or SW... especially for an out of towner or near the center of the grid... US 441 in Gainesville is 13th Street SW and NW... its a main road so locals might say "that place is over on 13th"  if you are from there you know its probably 441 but if you are unfamiliar... you might get lost... and then are are discontinuous streets... Gainesville has numbered Terraces and Courts in the grid  ( I know "Streets" in Gainesville are North-South and "Avenues" are East-West. "Terrace" and "Court" go with one of them but I'm not sure which way) 

I do like how you can tell how far away an address is from the center of the grid... you know that 615 SE 4th Ave is  6 blocks east of Main Street.  And the main roads out of town are "Roads" naming where they go to ( Waldo, Archer, Hawthorne, Williston, Newberry)

My mom grew up in Gainesville and they changed from named streets in the 1930s or 40s.  She lived on Roper St which is now SE 2nd Ave or St... then moved out to the NE Waldo Road... the center of Gainesville has historic street signs that have the old names in smaller type. 
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: NE2 on May 21, 2013, 02:17:26 AM
Back in about 1900, Orlando had both Deepdene and Deepolene. I suspect that one of them was a misreading of a handwritten subdivision plat.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: hm insulators on May 21, 2013, 02:44:05 PM
Quote from: Molandfreak on May 09, 2013, 08:33:18 PM
Quote from: Pete from Boston on May 09, 2013, 12:30:36 PM
Quote from: hm insulators on May 06, 2013, 03:52:19 PM
Verdugo Road and Verdugo Boulevard intersect in a small Los Angeles suburb called Montrose.

Wow, what an awful name.  Verdugo = executioner!
:wow:

The name dates back to when California was part of the Spanish Empire. In the 1700s, nearly two dozen missions were built, from San Diego up to somewhere north of San Francisco, I think near present-day Sonoma. The mission system didn't last very long and eventually giant cattle ranches ("ranchos") were established up and down California. One of the smaller ranchos in what is now the present-day Los Angeles metropolitan area was Rancho La Canada (pronounced Lah Can-YAH-dah--technically there's supposed to be a tilde ~ over the N, like jalapeno or pinata), which was granted by Spain to a fellow named Jose Maria Verdugo. Old Rancho La Canada encompassed the present-day communities of Glendale, Burbank, La Canada Flintridge (my home town), La Crescenta, Montrose and Tujunga (pronounced Tuh-HUN-gah).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: doorknob60 on May 21, 2013, 08:00:25 PM
Franklin Rd. and Franklin Blvd. near Nampa, ID. Franklin Rd. is an East-West road that goes from Nampa all the way to Boise, and Franklin Blvd. is North-South and goes from Nampa up to US-20. They don't connect with each other either (but they come within less than two miles of each other). Now that I look at it, Google seems to suggest that the Blvd. is also called Franklin Rd. once you get north of Nampa, although the freeway exit labels it as Blvd. The US-20 exit in Caldwell (Exit 29) is also labelled Franklin Rd, even though it does not connect to the Franklin Rd. in Nampa-Meridia-Boise!
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on May 21, 2013, 08:01:50 PM
Quote from: hm insulators on May 21, 2013, 02:44:05 PM
~ over the N

Alt+164 = ñ
Alt+165 = Ã'
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: hm insulators on May 24, 2013, 09:27:50 PM
Quote from: hm insulators on May 21, 2013, 02:44:05 PM
Quote from: Molandfreak on May 09, 2013, 08:33:18 PM
Quote from: Pete from Boston on May 09, 2013, 12:30:36 PM
Quote from: hm insulators on May 06, 2013, 03:52:19 PM
Verdugo Road and Verdugo Boulevard intersect in a small Los Angeles suburb called Montrose.

Wow, what an awful name.  Verdugo = executioner!
:wow:

The name dates back to when California was part of the Spanish Empire. In the 1700s, nearly two dozen missions were built, from San Diego up to somewhere north of San Francisco, I think near present-day Sonoma. The mission system didn't last very long and eventually giant cattle ranches ("ranchos") were established up and down California. One of the smaller ranchos in what is now the present-day Los Angeles metropolitan area was Rancho La Canada (pronounced Lah Can-YAH-dah--technically there's supposed to be a tilde ~ over the N, like jalapeno or pinata), which was granted by Spain to a fellow named Jose Maria Verdugo. Old Rancho La Canada encompassed the present-day communities of Glendale, Burbank, La Canada Flintridge (my home town), La Crescenta, Montrose and Tujunga (pronounced Tuh-HUN-gah).

That was interesting to learn that the term verdugo means executioner. The other day, I even talked to one of my neighbors (and even showed him a street map of the area in question), who's originally from Nogales, Mexico and he confirmed that's exactly what it means.

So maybe centuries ago, a Spaniard with the last name of Verdugo would in fact be an executioner. Very much like Anglo/Saxon surnames such as Carpenter, Miller, Draper, Taylor and so forth.

Anyway, in that part of the Los Angeles metropolitan area, Verdugo is a common name for at least one school, numerous businesses, and a hospital. Plus I forgot to mention a small community called Verdugo City, and finally, there's a small mountain range called the Verdugo Mountains which separate the San Fernando Valley from the Tujunga/La Crescenta/La Canada Flintridge area. 
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: apeman33 on May 31, 2013, 11:17:48 PM
Just looked over the copy of a county commission story. A person who lives just outside the city limits wants the name of the road he lives on changed from "235th St." to "235th Terrace." When the county first named the roads, they didn't account for the fact that 235th is broken up into several parts and on a couple of occasions, emergency vehicles ended up going to the wrong place.

(https://fbcdn-sphotos-g-a.akamaihd.net/hphotos-ak-ash4/424674_10152888048285331_1244453751_n.jpg)

The red dot and the blue dot would have the same address if there were properties at both locations. There's actually only some farmland where the red dot is located. The reason the county named both of them 235th St. is how they line up in the E911 grid system. Anyone looking for the petitioner's address ends up where the red dot is first, then has to double back to Maple Road and drive about a half mile east to get to the road he actually lives on.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: CentralCAroadgeek on June 20, 2013, 12:48:59 AM
While they are obviously not streets or highways at all, I'd like to mention how the Seattle-area cities of Renton and Redmond always confuse me. I always get them mixed up. To help me remember, I always tell myself Microsoft's in Redmond and 737s are built in Renton.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Thing 342 on July 01, 2013, 10:36:21 PM
There is a George Washington Highway in Chesapeake, and a George Washington Memorial Highway in Gloucester and York Counties. Even worse, both carry US 17.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: NE2 on July 01, 2013, 10:43:49 PM
Quote from: Thing 342 on July 01, 2013, 10:36:21 PM
There is a George Washington Highway in Chesapeake, and a George Washington Memorial Highway in Gloucester and York Counties. Even worse, both carry US 17.
So they're both part of the same long-distance road. What's the problem?
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on July 04, 2013, 04:30:56 PM
Quote from: cpzilliacus on May 13, 2013, 02:15:08 PM
Quote from: 1995hoo on May 12, 2013, 08:11:08 PM
Indeed it is wrong. Until recently, a block away at 1st & Potomac SE (beyond the right field corner of the ballpark), the sign said "Potomac Ave St SE." Really! That was fixed last year.

I had business in Southeast D.C. near there earlier today and snapped an image of that sign at Potomac Avenue, S.W. at South Capitol Street, which is still there (and still incorrect <smile>).

Just annotated that image and e-mailed it to a colleague of mine at DDOT, who will forward to the correct group within DDOT.

Thank you for pointing it out.

We just came home from Nationals Park. The sign has been fixed. Your colleague got the job done. Behold the power of the AARoads Forum!

The new sign is one of the new mixed-case signs. I didn't get a picture because we were on the far side of the street and my iPhone would have taken too grainy an image.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: TEG24601 on July 04, 2013, 07:45:44 PM
This is going to be good....

Throughout Washington County in Oregon, there are numerous N-S numbered avenues, however, if you have a street in-between the gridded roads, they will be the same as the more eastern number, then followed by Place or Drive, instead of Avenue.

Numerous locations in cities where they have avenues on one cardinal path and streets on another.  To mis-quote Kramer "1st St and 1st Ave, it is the center of the universe."

Flint, MI - Numbered streets run parallel to the Flint River.  However, rather than North on the North of the River, and South on the South side of the River, the Avenues run on the North of the River, and Streets run on the South Side.  It gets confusing when when you are talking to someone who has never been there before.

Again in Michigan... US-24, M-24, and Business US-24 all within a few miles of each other in and around Pontiac/Auburn Hills.

Frontage roads on Detroit Style freeways, both frontage roads have the same name, so you can't easily tell which one a business is really on, until you figure out the addressing.

My county used to have this problem quite frequently, however when they reorganized the emergency services they got rid of the duplications.  They now allow duplication within the county, but not within the same ZIP code, or within 15 miles, which because we are on two islands, makes them rare now.

It is also confusing when roads have huge gaps in them, but have the same name, simply because they fit the grid.  It makes it very difficult to navigate some Western cities, like Portland and Seattle (and their suburbs).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Tarkus on July 05, 2013, 04:01:08 AM
More on the Oregon front . . .

One real facepalm I can think of is with the Eugene-Springfield area.  Centennial Boulevard was/is a major east-west thoroughfare that runs through both Eugene and Springfield, and, once it arrives in Springfield, it has an intersection with Pioneer Parkway (part of which is OR-528). 

Sometime in the 1990s, Eugene decided to honor Martin Luther King Jr., by renaming their section of Centennial Boulevard to Martin Luther King Jr. Boulevard.  In the mid-00s, Springfield also decided to honor MLK, but rather than simply renaming their stretch of Centennial to follow suit with Eugene, they decided to name a new northern extension of Pioneer Parkway as Martin Luther King Jr. Parkway.  So, in effect, the Pioneer/Centennial intersection is between two roads that, just a short distance away, become MLK something.

Quote from: TEG24601 on July 04, 2013, 07:45:44 PM
Throughout Washington County in Oregon, there are numerous N-S numbered avenues, however, if you have a street in-between the gridded roads, they will be the same as the more eastern number, then followed by Place or Drive, instead of Avenue.

Don't forget Court and Terrace (and I seem to recall a numbered Lane, too).  And Hillsboro's strange fondness for "Street Drive" (e.g. NE 11th St Dr, which is especially peculiar, since Hillsboro uses Avenue as the standard for N-S numbered streets).  The Ct/Ter/Pl/Dr/Ln tendencies tend to apply to continuations of named streets, too (see SW Augusta Lane, Street, Drive, Court, and Place in Aloha).

Quote from: TEG24601 on July 04, 2013, 07:45:44 PM
It is also confusing when roads have huge gaps in them, but have the same name, simply because they fit the grid.  It makes it very difficult to navigate some Western cities, like Portland and Seattle (and their suburbs).

There's also 5 SW Jay Streets in Washington County--one from SW Cornelius Pass Road to SW 206th Avenue, another from SW 204th Avenue to SW 199th Court, one from SW 185th Avenue to SW 176th Terrace (and the Jay designation goes around the bend when it runs into a T at SW 179th Court), one that's a dead-end off of SW 175th Avenue, and another from SW 162nd Avenue to SW Jenkins Road (on the southwest edge of Nike HQ).  Confusingly enough, the one that ends at 206th on its east end continues further east as SW Keylock Lane, and runs into another SW 204th Avenue, which is not connected to the one from which the next SW Jay Street beings. :pan:

Additionally, the north-south divider at that point is supposedly Baseline Road, which often carries the designation of W Baseline Road, though sometimes becomes SW Baseline Road.  And even when it is marked as "W", some of the roads directly north of it are still marked as "SW" for a few blocks if in unincorporated Washington County (which actually seems to treat Beaverton Creek as the divider).  It gets to be an all-out fustercluck when Baseline runs into the east edge of the Hillsboro city limits at Cornelius Pass Road, and the stretch of Cornelius Pass within a few blocks of Baseline goes from being SW, to NE, to SW, to NW.  And W Baseline Road acts as the division between NE and SE streets in Hillsboro east of Brookwood Avenue/Parkway (which also manages go run the "tetrafecta" through SW, SE, NW and NE).  And don't get me started on how SW 229th Ave turns into SE 67th.

Also, Hillsboro happens to have two Alder Streets that are in completely different parts of town--SE Alder Street, and then NE Alder Street up in Orenco (which only became part of Hillsboro in the 1990s-era of Hillsboro and Beaverton's "manifest destiny"), Beaverton has SW Davis Road and SW Davies Road on the south end of town, and Tigard used to have both SW Frewing Lane (off SW 135th Ave) and SW Frewing Street (off OR-99W), not particularly close to one another, but seems to have mysteriously renamed Frewing Lane as Feiring Lane.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: TEG24601 on July 05, 2013, 11:29:51 AM
I forgot one that drove me nuts...

M-24 in Michigan is very often referred to as Lapeer Rd.  However, in a few towns, including the one I lived in, Lake Orion, this wasn't quite true.  Within the city limits, M-24 was originally named Broadway Street.  There is a Lapeer St. within the city limits, one block West of Broadway (I'm not sure if there was a cuplet or not).  Just South of downtown, M-24 veers off of broadway to bypass downtown, which is then called Park Blvd, until it reaches the Northern city limits, at which point it returns to Lapeer Rd.  So often I would be directed to something on Lapeer, and either go looking for it on M-24 or on Lapeer St., and it was on the other road named Lapeer.

This is of course not to be confused with Lapeer Rd. which is the former routing of M-21 between Flint and Lapeer.  M-24 and M-21 used to meet in Lapeer, now M-21 has been supplanted by I-69.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Avalanchez71 on July 05, 2013, 12:02:06 PM
How about Old Hickory Blvd in Nashville, TN? 
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: deathtopumpkins on July 05, 2013, 06:21:00 PM
Quote from: Avalanchez71 on July 05, 2013, 12:02:06 PM
How about Old Hickory Blvd in Nashville, TN?

How about it?
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: mjb2002 on July 07, 2013, 06:12:07 PM
Across the CSRA, Aiken County tends to do this quite a bit.

For example, there's SOUTH AIKEN LN and SOUTH AIKEN BLVD. Yes, near South Aiken High School.

UNIVERSITY PKWY & UNIVERSITY LN in Aiken 29801:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2F24.media.tumblr.com%2Fbb1b81756ad22fd03086754cf48a05cf%2Ftumblr_mpl4jmuX3Z1r2t3z9o1_500.jpg&hash=f7f5fa6cd1ddf0b52d37f82b6981eadb4a8e2730)

GREGG HY & GREGG ST in Graniteville:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2F24.media.tumblr.com%2F19caa40c607451a24cffc1bad4c09e00%2Ftumblr_mpl4jmuX3Z1r2t3z9o2_r1_400.jpg&hash=44e1c10f623701dee1f9f0dfdc222235087d8114)

STORM BRANCH RD & STORM BRANCH LEG near Beech Island
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: roadman65 on July 07, 2013, 06:36:53 PM
In Orlando we have two McGuires.  One called McGuire Boulevard on the east side of town and the other is McGuire Road on the west end.  Both roads respectively have intersections with Highway 50, and therefore on commercials and radio traffic reports you will here someone mention the intersection of 50 and McGuire.  That making you wonder which McGuire intersection they're talking about.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: DSS5 on July 07, 2013, 08:13:26 PM
Boone, NC has NC Highway 105, NC 105 Extension, and NC 105 Bypass.

There is also a University Circle, University Drive, and University Hall Drive, as well as Appalachian Street and Appalachian Drive. And more "Old US 421s" than you can shake a stick at.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: DSS5 on July 07, 2013, 08:24:25 PM
Also worth a mention is the entire city of Hickory, NC, which has wonders like "4th Avenue Drive" and "2nd Street Place." Here's a news report on the subject.

http://www.wcnc.com/news/neighborhood-news/hickory/Hickory-street-signs-confusing-to-residents-visitors-115931844.html
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cpzilliacus on July 07, 2013, 08:52:04 PM
Quote from: 1995hoo on July 04, 2013, 04:30:56 PM
We just came home from Nationals Park. The sign has been fixed. Your colleague got the job done. Behold the power of the AARoads Forum!

The new sign is one of the new mixed-case signs. I didn't get a picture because we were on the far side of the street and my iPhone would have taken too grainy an image.

That is great. 

Not so long ago (under the administration of former Mayor-for-Life Marion Shepilov Barry, Jr.) corrections to traffic control devices (except parking and NO  PARKING signs, related to the one thing his administrations did well - write parking tickets) was a very low priority for DCDPW (it was not DDOT until the administration of Tony Williams).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cpzilliacus on July 07, 2013, 08:56:52 PM
Quote from: Mark68 on May 16, 2013, 03:41:10 AM
The quadrants in Portland could lend to some confusion, especially to newcomers and tourists. The Willamette divides the eastern and western halves (as well as the northwest and north quadrants), and most of the N/S streets are numbered. So you have NE 1st Ave (there is no SE 1st Ave) and NW/SW 1st Ave on either side of the river.

The District of Columbia may have been the first municipality in the U.S. to use a quadrant system.

Unlike Portland, the quadrant on D.C. streets is always a suffix, and is supposed to be used for all street names and addresses, without exception.

Even the Capitol streets (North, East and South), which divide the quadrants along with the National Mall (no West Capitol Street) always have a quadrant associated with them - if you are going north on North Capitol Street, you are on North Capitol Street, N.E.  If you are headed south, you are on North Capitol Street, N.W.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: roadman65 on July 07, 2013, 09:18:09 PM
Quote from: cpzilliacus on July 07, 2013, 08:56:52 PM
Quote from: Mark68 on May 16, 2013, 03:41:10 AM
The quadrants in Portland could lend to some confusion, especially to newcomers and tourists. The Willamette divides the eastern and western halves (as well as the northwest and north quadrants), and most of the N/S streets are numbered. So you have NE 1st Ave (there is no SE 1st Ave) and NW/SW 1st Ave on either side of the river.

The District of Columbia may have been the first municipality in the U.S. to use a quadrant system.

Unlike Portland, the quadrant on D.C. streets is always a suffix, and is supposed to be used for all street names and addresses, without exception.

Even the Capitol streets (North, East and South), which divide the quadrants along with the National Mall (no West Capitol Street) always have a quadrant associated with them - if you are going north on North Capitol Street, you are on North Capitol Street, N.E.  If you are headed south, you are on North Capitol Street, N.W.
How come there is no Constitution Avenue N. W. or N. E. depending on what side of North Capitol Street?  Ditto for Independence Avenue as well.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: andrewkbrown on July 08, 2013, 02:18:48 AM
There is. Constitution Avenue west of North Capitol Street is Constitution Avenue NW, and east of it is Constitution Avenue NE. Likewise, Independence Avenue can be found as Independence Avenue SW and Independence Avenue SE, depending on if it is west or east of South Capitol Street.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on July 08, 2013, 01:34:24 PM
Quote from: TEG24601 on July 04, 2013, 07:45:44 PM
Throughout Washington County in Oregon, there are numerous N-S numbered avenues, however, if you have a street in-between the gridded roads, they will be the same as the more eastern number, then followed by Place or Drive, instead of Avenue.

Isn't this more or less what Kansas City does for east-west streets?
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: hm insulators on July 09, 2013, 03:33:18 PM
Quote from: DSS5 on July 07, 2013, 08:24:25 PM
Also worth a mention is the entire city of Hickory, NC, which has wonders like "4th Avenue Drive" and "2nd Street Place." Here's a news report on the subject.

http://www.wcnc.com/news/neighborhood-news/hickory/Hickory-street-signs-confusing-to-residents-visitors-115931844.html

"So who's on first?"

"That's right."

"What's the guy's name on first?"

"No, What's the guy's name on second."

"I'm not asking you who's on second!"

"Who's on first."
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: TEG24601 on July 09, 2013, 09:40:20 PM
I've remembered another couple...

In Everett Washington, there is the SR-526 Freeway, which was originally called the Casino Freeway, because it supplanted Casino Rd.  Today, it is usually called the Boeing freeway, but many long-time residents, like myself still call it Casino Freeway.  However, Casino Rd. still parallels the freeway for a large portion of the route.

Also, Washington has a large number of city streets called HWY 99, the former route of US-99/SR-99.  One of the most egregious uses of the name is in Vancouver, WA, which wouldn't be a problem, if many people didn't call OR-99E, Highway 99 as well, or that there were so many of the discontinuous HWY 99s, it is quite confusing.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: CentralCAroadgeek on July 27, 2013, 03:49:51 PM
Price Road and Price Canyon Road in Pismo Beach, CA.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: roadman65 on July 28, 2013, 06:32:47 PM
https://maps.google.com/maps?q=Bennington,+VT&hl=en&ll=42.907036,-73.219714&spn=0.005045,0.012274&sll=27.698638,-83.804601&sspn=12.394025,25.136719&oq=bennin&t=h&hnear=Bennington,+Vermont&z=17&layer=c&cbll=42.906878,-73.219605&panoid=fpTamgkFAPFECT5y4USbdg&cbp=12,179.92,,0,-0.09
Here is the way the State of Vermont prevents confusion between US 7 and NY Route 7 that are very close to each other and both major arteries for the region.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Thing 342 on September 05, 2013, 04:01:20 PM
Near my house, realignment has caused there to be a Menchville Rd, another Menchville Rd, an Old Menchville Rd, and a Menchville Ct, all within about a mile of each other. It doesn't help that there is also a Melville Rd close by, either.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on September 05, 2013, 04:59:22 PM
Quote from: roadman65 on July 28, 2013, 06:32:47 PM
https://maps.google.com/maps?q=Bennington,+VT&hl=en&ll=42.907036,-73.219714&spn=0.005045,0.012274&sll=27.698638,-83.804601&sspn=12.394025,25.136719&oq=bennin&t=h&hnear=Bennington,+Vermont&z=17&layer=c&cbll=42.906878,-73.219605&panoid=fpTamgkFAPFECT5y4USbdg&cbp=12,179.92,,0,-0.09
Here is the way the State of Vermont prevents confusion between US 7 and NY Route 7 that are very close to each other and both major arteries for the region.

Your comment reminds me of the sign on westbound I-70 near the exit for Clear Spring, Maryland (http://goo.gl/maps/sqlxO), which is served by MD-68. I-68 begins about 17 miles to the west. Evidently a lot of drivers must have gotten lost at Clear Spring when someone told them to take "68." (This sort of thing causes me to be very precise in always using a prefix prior to any route number when giving directions, along with trying to give additional detail as well such as "I-68 west towards Cumberland" or the like).

I can't help but think, though, that the people who get confused by this kind of thing might not be helped all that much by this sign, and I wonder if the sign would be clearer if it said "to Cumberland and Morgantown" next to the I-68 shield instead of using the gratuitous "National Freeway" (a name I've never heard anyone use in reference to that road).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Mr_Northside on September 06, 2013, 02:22:51 AM
Quote from: 1995hoo on September 05, 2013, 04:59:22 PM
I can't help but think, though, that the people who get confused by this kind of thing might not be helped all that much by this sign, and I wonder if the sign would be clearer if it said "to Cumberland and Morgantown" next to the I-68 shield instead of using the gratuitous "National Freeway" (a name I've never heard anyone use in reference to that road).

I agree that this might be the case for people who are not road-savvy. (Don't really know the difference between a state shield & Interstate shield).... and I also completely agree that actual destinations would be much more useful than "National Freeway" on those signs.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: DSS5 on October 26, 2013, 06:51:11 PM
Statesboro, GA has two stretches of road called Main Street. One signed as East/West Main, and another marked as North/South Main. The intersection between the two Mains is the center where the directions change.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: bzakharin on October 26, 2013, 09:10:42 PM
South Jersey has its fair share. Church Road and Church Street intersect in Marlton. Both cross NJ 38 not far from each other. Church Street goes on to be renamed to Church Road once it enters Cinnaminson. There are two Fellowship Roads crossing NJ 73 less than two miles from each other (Maple Shade and Mount Laurel). Ones is a handy shortcut to Church Road (not Street), which I use quite a bit, while the other is... not. Then there's Haddonfield-Berlin Road which loses that name in Haddonfield and splits into two roads, one of which eventually becomes Haddonfield Road, while the other eventually becomes Haddon Avenue. The Townships of Barrington and Haddon Heights have their own independent grids. They are separated by I 295, but one road connects them - 3rd ave. (Barrington) which becomes 9th ave. (Haddon Heights).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: dgolub on October 27, 2013, 10:36:58 AM
Long Island has both Merrick Road (Nassau CR 27) and Merrick Avenue (Nassau CR 4).  All of the county routes in Nassau are unsigned, so you can't use the route numbers to disambiguate.

Out in Suffolk County, where the county route numbers are signed, there's both CR 111 and NY 111.  A lot of people headed out to Montauk get off the expressway at the wrong exit because of this.

There's also two different streets called New Highway.  There's also Straight Path (Suffolk CR 2) and Carll's Straight Path.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: bugo on October 28, 2013, 03:07:08 AM
In Tulsa, there are often streets, places, courts, etc with the same name that parallel each other and sometimes intersect. 

There's also the situation of AR 59 and US 59 paralleling each other with just a few miles and a state line separating the two.  GA 27 and US 27 intersect, as do US 70 and TX 70.  US 25 ends at GA 25.  Not to mention the whole I-74/US 74 batshit insane clusterfuck.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Urban Prairie Schooner on October 28, 2013, 08:07:08 PM
In Baton Rouge the most obvious example of this would be North Street and North Boulevard, which are major arterial streets that begin in downtown and cross Mid-City, parallel to each other but separated by merely 5 blocks. This duplication doesn't confuse me anymore but I can imagine how someone unfamiliar with the area might fare.

There is an intersection of Canal Street and Carrollton Avenue in both New Orleans and Metairie.

Something I find irritating is when a subdivision developer creates a cul-de-sac off of another, well established street and gives the new street the same name (with a different suffix). Suffice it to say that the planning department will always require the developer to choose a new name before final plat approval...
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Ned Weasel on October 28, 2013, 09:46:20 PM
Here's one that I always found a bit odd but not terribly confusing: Olathe, Kansas and Overland Park, Kansas--two cities that border each other and are in the same county--both have a Santa Fe.  Olathe's is Santa Fe Street (although "Street" is often dropped from road signs), and Overland Park's is Santa Fe Drive.  To make things more interesting, both cities have their City Halls on their respective Santa Fe streets.  They don't intersect each other or any of the same streets, however.

Also:

Quote from: kphoger on July 08, 2013, 01:34:24 PM
Quote from: TEG24601 on July 04, 2013, 07:45:44 PM
Throughout Washington County in Oregon, there are numerous N-S numbered avenues, however, if you have a street in-between the gridded roads, they will be the same as the more eastern number, then followed by Place or Drive, instead of Avenue.

Isn't this more or less what Kansas City does for east-west streets?

In case you were expecting an answer (I didn't notice this post until now, but I see no one has answered it here): most of the Kansas City, Missouri grid system uses numbered Streets for east-west streets at eighth-mile intervals, and then it repeats the number as a Terrace, usually at a 16th-mile interval.  When a third iteration is needed, it's a Place.  There is one major exception, though: the street numbers are actually at 16th-mile intervals from 1st Street south through 23rd Street, and they then change to eighth-mile intervals at 24th Street.  It's also interesting to note that, not only does the Kansas City, MO grid system cover most of the area of the four counties in which the city lies (Jackson, Cass, Platte, and Clay), but Johnson and Miami Counties in Kansas also use a continuation of the same grid system.  Wyandotte County and Leavenworth Counties in Kansas, however, use a separate, distinct grid system (and Wyandotte County, KS is the county in which Kansas City, KS lies).

The Wyandotte and Leavenworth County, Lawrence, and Topeka/Shawnee County grid systems (all in Kansas) each use a similar Street and Terrace configuration, but the Wyandotte County and Topeka grid systems both have a similar situation to that of Kansas City, MO's grid system, in that the eighth-mile spacing of numbers doesn't start until several numbers away from the origin point.

(I had always assumed Wichita also used Terraces this way, simply because it has a rigid grid system with numbers for east-west Streets at eighth-mile intervals, but now that I look at a map, I see that Wichita seems to have named all of its inter-number streets.)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: PHLBOS on October 29, 2013, 01:12:20 PM
Although I-68 and MD-68 aren't exactly within close proximity to eachother, MDOT Md. SHA saw fit to place this supplemental BGS along I-70 Westbound approaching Exit 18 (for MD 68).

http://goo.gl/maps/6YQ5s (http://goo.gl/maps/6YQ5s)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: briantroutman on October 29, 2013, 01:50:50 PM
Quote from: PHLBOS on October 29, 2013, 01:12:20 PM
Although I-68 and MD-68 aren't exactly within close proximity to eachother, MDOT saw fit to place this supplemental BGS along I-70 Westbound approaching Exit 18 (for MD 68).

http://goo.gl/maps/6YQ5s (http://goo.gl/maps/6YQ5s)

I think that results not so much from the proximity of I-68 and MD 68 but because Md. SHA "advertises" I-68 as an alternate (and incidentally, toll-free vs. the PA Turnpike) nearly 60 miles east in Frederick. http://bit.ly/1dJnAd9 (http://bit.ly/1dJnAd9)

It comes across to me as one of the most overtly sales-y displays I've ever seen from a state DOT (on official guide signage).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: PHLBOS on October 29, 2013, 02:22:09 PM
Quote from: briantroutman on October 29, 2013, 01:50:50 PM
Quote from: PHLBOS on October 29, 2013, 01:12:20 PM
Although I-68 and MD-68 aren't exactly within close proximity to eachother, MDOT Md. SHA saw fit to place this supplemental BGS along I-70 Westbound approaching Exit 18 (for MD 68).

http://goo.gl/maps/6YQ5s (http://goo.gl/maps/6YQ5s)

I think that results not so much from the proximity of I-68 and MD 68 but because Md. SHA "advertises" I-68 as an alternate (and incidentally, toll-free vs. the PA Turnpike) nearly 60 miles east in Frederick. http://bit.ly/1dJnAd9 (http://bit.ly/1dJnAd9)
Yes, but if that was the case, then why is there a NEXT EXIT IS 68 (MD) on the BGS above the I-68/National Freeway listing? 

It's there because those unfamiliar with the area and only see a Route 68 exit sign, regardless of the shield shape, may inadvertently exit off I-70 West prematurely.

As far as the other BGS advertisements for I-68 signage is concerned (like the one you posted), that's on Md. SHA and not relevant to the thread topic at hand. 
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: briantroutman on October 29, 2013, 03:13:22 PM
Quote from: PHLBOS on October 29, 2013, 02:22:09 PM
Quote from: briantroutman on October 29, 2013, 01:50:50 PM
I think that results not so much from the proximity of I-68 and MD 68 but because Md. SHA "advertises" I-68 as an alternate (and incidentally, toll-free vs. the PA Turnpike) nearly 60 miles east in Frederick. http://bit.ly/1dJnAd9 (http://bit.ly/1dJnAd9)
Yes, but if that was the case, then why is there a NEXT EXIT IS 68 (MD) on the BGS above the I-68/National Freeway listing? 

It's there because those unfamiliar with the area and only see a Route 68 exit sign, regardless of the shield shape, may inadvertently exit off I-70 West prematurely.

What I was trying to say is that I believe Md. SHA posted the "NEXT EXIT IS [68]" sign because they had already promoted "68" earlier, and–I agree with you–the general public might confuse one "68" with the other, regardless of the shield shape.

But the larger point I was trying to make was that, if they hadn't posted those "advertisement" signs further to the east, I suspect they probably wouldn't have posted the other sign at MD 68.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: hotdogPi on November 10, 2013, 05:53:48 PM
Near Danvers MA, there are two streets called Endicott Street about a mile from each other. Both are relatively important streets.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: PHLBOS on November 11, 2013, 03:38:14 PM
Quote from: 1 on November 10, 2013, 05:53:48 PM
Near Danvers MA, there are two streets called Endicott Street about a mile from each other. Both are relatively important streets.
To clarify; if it's the two Endicott Streets that I'm thinking of; it's worth noting that one's in Danvers and the other is in Peabody.

The more familiar (to those outside the area) Endicott St. is Danvers one; Exit 24 off MA 128 & where the Liberty Tree Mall is located. 

The Peabody Endicott St. is a much shorter stretch of road that runs between MA 114 (Andover St.) and Lowell St.  It's worth noting that north of Andover St., road continues as Pulaski St. & MA 114; and south of Lowell St., the road continues as King St.

Truth be told, unless one's either from or familiar with the area; they're likely not to even know that that Endicott St. in Peabody even exists or is called that.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: agentsteel53 on November 11, 2013, 03:47:19 PM
according to an old GPS of mine, the frontage road to Pacific Highway in San Diego is Pacific Hwy.

good grief.

there's also two Morena Blvds, one of which is technically W. Morena Blvd, but it's signed as such with anything resembling consistency.  one is the bypass of the other - I believe both are 101 alignments from back in the day.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: NE2 on November 11, 2013, 06:14:03 PM
Quote from: agentsteel53 on November 11, 2013, 03:47:19 PM
according to an old GPS of mine, the frontage road to Pacific Highway in San Diego is Pacific Hwy.
What's wrong with this? Frontage roads are often named the same as the main lanes, since an address isn't going to exist on both in the same place.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: mrsman on December 22, 2013, 09:45:34 PM
Beverly Blvd is a main E-W thoroughfare in Los Angeles from the Downtown Area to Beverly Hills.  Beverly Drive is a N-S street through the heart of Beverly Hills and parts of Los Angeles.  Beverly Blvd ends about half a mile from Beverly Drive.

Another confusion is that there are two San Vicente Blvds in LA that are both major streets.  I beleive that they were connected long ago, but are now disjointed and might as well be separate streets, except that they share the same name.

Probably a worse confusion occurs in the Koreatown area of Los Angeles:  Normandie Avenue is a relatively important N-S street throughout Los Angeles.  North of Olympic, Irolo Street splits from Normandie on the west.  The major traffic follows Irolo, not Normandie.  Normandie is a relatively small street from Irolo until it ends at 7th Street, 4 blocks to the north.  Irolo then changes its name to Normandie just south of Wilshire.  So in other words, if you wanted to travel down the main N-S street between Vermont and Western, take Normandie.  But if you're traveling on 7th, 8th or 9th, don't take Normandie, take Irolo instead, which will then lead you to Normandie.

Crescent Heights Blvd does something similar (changing its name to Mc Carthy Vista and Carrillo between Olympic and Wilshire), but at least there is no parallel small Crescent Heights to further confuse the driving public.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: mrsman on December 22, 2013, 10:12:20 PM
Another confusion I note in the DC area is Beach Drive.  This is essentially the northern extension of the Rock Creek Parkway.  Its a major thoroughfare to head north from Downtown DC.  It is very twisty and its only one lane in each direction, but because it has few lights, it is a popular commuter corridor.  It is also closed on weekends to autos, so I very rarely get a chance to drive it.  (I take Metro to work on weekdays.) 

Beach Drive is very poorly marked.  It seems easy to exit on a side street too early.

The most confusing thing about Beach Drive is at its north end approaching Maryland.  There is a fork in the road where you can go NW to continue on Beach Drive or go NE to continue on West Beach Drive.  Yes, West Beach Drive is east of Beach Drive.  For Silver Spring, take West Beach Drive to Kalmia to East Beach Drive to Portal Drive to 16th Street.  For Lyttonsville, take West Beach Drive to Primrose which become Grubb Lane.  For Kensington continue on Beach Drive.

At East-West Highway, Beach Drive becomes Jones Mill Rd.  Jones Mill intersects Jones Bridge.  Most of the traffic from Jones Mill turns on Jones Bridge, but if you want Beach Drive continue on Jones Mill.  Jones Mill changes its name to Stoneybrook just before crossing under the Beltway.  Continue north on Stoneybrook to reach the Mormon Temple or make a quick left after the Beltway to continue on Beach Drive towards Garrett Park.

Its almost as difficult as following Sheridan Road in Chicago.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Eth on December 22, 2013, 11:23:42 PM
Quote from: mrsman on December 22, 2013, 10:12:20 PM
The most confusing thing about Beach Drive is at its north end approaching Maryland.  There is a fork in the road where you can go NW to continue on Beach Drive or go NE to continue on West Beach Drive.  Yes, West Beach Drive is east of Beach Drive.

This reminds me of a situation in Atlanta: Peachtree Street (which has likely been mentioned earlier in this thread) is paralleled a block or so to the west by West Peachtree Street. Past 14th Street going north, Peachtree turns to the west, and West Peachtree is absorbed into it around 19th. A short while later, Peachtree turns west again, and another short segment of West Peachtree appears - to the east of Peachtree. Looking at a map, you can easily see that both segments are on the same north-south line, but it's a little less than intuitive.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: US71 on December 23, 2013, 10:01:22 AM
Springfield, MO has Grant and Grand.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: bzakharin on December 23, 2013, 04:00:58 PM
Quote from: Eth on December 22, 2013, 11:23:42 PM
Quote from: mrsman on December 22, 2013, 10:12:20 PM
The most confusing thing about Beach Drive is at its north end approaching Maryland.  There is a fork in the road where you can go NW to continue on Beach Drive or go NE to continue on West Beach Drive.  Yes, West Beach Drive is east of Beach Drive.

This reminds me of a situation in Atlanta: Peachtree Street (which has likely been mentioned earlier in this thread) is paralleled a block or so to the west by West Peachtree Street. Past 14th Street going north, Peachtree turns to the west, and West Peachtree is absorbed into it around 19th. A short while later, Peachtree turns west again, and another short segment of West Peachtree appears - to the east of Peachtree. Looking at a map, you can easily see that both segments are on the same north-south line, but it's a little less than intuitive.

Having discontinuous segments of the same street on either side of continues streets is fairly common in cities with grid systems, although most of them are not named similarly. And sometimes continuous streets change their names very unintuitively to accommodate curves within the grid. In Philadelphia, Spruce Street becomes South street as you enter Center City from the West, while another Spruce Street appears north of it.

Even worse is 34th Street which, if you follow it from south to north manages to become 38th Street (there is a short portion in between under a different name) with another 34th Street eventually appearing 4 blocks away (the two intersect, but neither of them is 34th street at the point of intersection, so it's not like you would know to turn onto it).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: jbnv on June 17, 2014, 02:10:12 PM
Lafayette, LA:

* College Rd. and Coolidge Blvd., which intersect at an obtuse angle, making for an interesting street sign placement (http://goo.gl/maps/iFgdZ).

* Evangeline Thruway (a major road) and Evangeline St. (a minor neighborhood road).

* Plenty of cases of multiple cardinal directions, with duplicated address numbers, for the same road. University Avenue has East, West and North segments.

* A Martin Luther King Jr. Dr., and an arterial road that was designated the Martin Luther King Jr. Memorial Parkway because racial politics (http://www.lafayettepublicpolicy.com/lafayetteresolveskingissue.html).

The I-12 exit for LA 59 has trailblazers pointing the way to Interstate 59, which is several miles to the east.

On I-10 in Vidor, TX, near the exit for FM 105, there is an advance sign for TX-105, which is 10 miles further to the west.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: TheStranger on June 17, 2014, 02:51:39 PM
At the start of Point Lobos Avenue in San Francisco, there's a portion of road parallel to Geary Boulevard that should logically be part of Point Lobos, but is instead marked as part of Geary (alongside the main alignment)!

https://maps.google.com/maps?q=Point+Lobos+Avenue,+San+Francisco&hl=en&ll=37.779549,-122.502462&spn=0.001518,0.002004&sll=37.269174,-119.306607&sspn=12.440158,16.413574&hnear=Point+Lobos+Ave,+San+Francisco&t=m&z=19
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Road Hog on June 18, 2014, 02:15:30 AM
Plano, TX has three major east-west thoroughfares in order from north to south: Park, Parker, and Plano Parkway.

And there is the often-mentioned FM 121 that crosses US 75 just a few miles north of SH 121.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: MikeTheActuary on June 18, 2014, 08:14:57 AM
From my neighborhood (http://goo.gl/y9CRfL)

Note the name of the non-freeway portion of CT 20 and the arterial street to the south.

Title: Re: Streets and highways with similar names confusingly close to each other
Post by: bing101 on June 19, 2014, 10:38:11 AM
Alta Arden Expressway and Arden in Sacramento sound similar.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kurumi on June 19, 2014, 11:01:49 AM
Quote from: MikeTheActuary on June 18, 2014, 08:14:57 AM
From my neighborhood (http://goo.gl/y9CRfL)

Note the name of the non-freeway portion of CT 20 and the arterial street to the south.



(Derail: what's the deal with the roundabouts not at intersections? Saw one on [southern] Rainbow Road and International Drive.)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: agentsteel53 on June 19, 2014, 11:03:19 AM
Quote from: NE2 on November 11, 2013, 06:14:03 PM
Quote from: agentsteel53 on November 11, 2013, 03:47:19 PM
according to an old GPS of mine, the frontage road to Pacific Highway in San Diego is Pacific Hwy.
What's wrong with this? Frontage roads are often named the same as the main lanes, since an address isn't going to exist on both in the same place.

innately, nothing.  except the GPS was fussy, and attempting to search on Pacific Highway failed - one had to know that the GPS accepted Hwy, and only Hwy.

I think officially the frontage road is named "Pacific Highway Frontage Road".  in any case, the GPS failed gracelessly for sure.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: MikeTheActuary on June 19, 2014, 01:37:27 PM
Quote from: kurumi on June 19, 2014, 11:01:49 AM
Quote from: MikeTheActuary on June 18, 2014, 08:14:57 AM
From my neighborhood (http://goo.gl/y9CRfL)

Note the name of the non-freeway portion of CT 20 and the arterial street to the south.


(Derail: what's the deal with the roundabouts not at intersections? Saw one on [southern] Rainbow Road and International Drive.)

I think of them as "horizontal speed bumps".  :)

In all seriousness, International Drive is host to an industrial park that has a lot of truck traffic.  Before the roundabouts went in, there were many 18 wheelers traveling the southern Rainbow Rd. between Hamilton Rd. and International to access the south side of the industrial district.  East of the Rainbow Rd. roundabout, Rainbow becomes a residential arterial, with poor sightlines in places, no sidewalks or bike lanes, and quite a bit of pedestrian and bike traffic during daylight hours.  Speed limit is posted as 30; semis were blowing through at 45+, and even folks who don't have NIMBY knee-jerk syndrome (e.g., me -- I have a blind driveway on Rainbow) knew it was a tragedy waiting to happen.

The roundabouts were put in as part of a traffic-calming strategy, to create a barrier of a sort to suggest to truckers that Route 20 would be more appropriate to use.   The traffic calming by itself didn't really work (as evidenced by the number of tire tracks going through the roundabout centers, until posts and vegetation were installed), but it does seem to have tripped something in the logic of major nav systems; at least my GPS apps quit wanting to route down the residential arterial after the roundabout was picked up in updated maps.

I'm not positive, but I believe that the roundabout on International Drive, although framed as a traffic-calming item, has an additional purpose: the neighboring Town of East Granby required it as a condition to not fighting rezoning for one of the parcels in the industrial park.

If they were merely decorative or intended as speed-control obstructions, the roundabouts would be pretty annoying.  However, as devices to divert long-distance trucks away from residential streets, they seem to make sense and mostly work, and they were less intrusive or obnoxious and easier to implement than some of the alternatives my neighbors suggested.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: wisvishr0 on June 27, 2014, 12:19:51 AM
Not only does DC have a Quadrant system with repeating streets, but it also has repeating streets within quadrants. For example, Macomb St. NW connects MacArthur Blvd with Potomac Avenue (NW), but it also has an unrelated section that connects Wisconsin and Massachusetts Avenues, both in NW. It also has a section in the middle.

Actually, they seem to be related: if you see the map, the  Macombs have Cathedrals and Klingles below them, which are indeed "extensions" of the other over creeks or streams. I tried connecting the streets as though they were continuous with the dots.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fs11.postimg.org%2F9vpubc56b%2FScreen_Shot_2014_06_27_at_12_14_49_AM.png&hash=e0b1b83d95956a4954f2dc09e6013e2b3ec29deb)

But they are a source of confusion.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: PHLBOS on July 10, 2014, 01:14:03 PM
In both Peabody & Lynn, MA; there are two different roads both named Lynnfield St.; one of which crosses into Lynn and becomes Salem St.  Which, coincidentally, intersects with the other Lynnfield St. (MA 129) at Goodwin's Circle (http://goo.gl/maps/sRgTB).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on July 10, 2014, 03:05:18 PM
Quote from: wisvishr0 on June 27, 2014, 12:19:51 AM
Not only does DC have a Quadrant system with repeating streets, but it also has repeating streets within quadrants. For example, Macomb St. NW connects MacArthur Blvd with Potomac Avenue (NW), but it also has an unrelated section that connects Wisconsin and Massachusetts Avenues, both in NW. It also has a section in the middle.

Actually, they seem to be related: if you see the map, the  Macombs have Cathedrals and Klingles below them, which are indeed "extensions" of the other over creeks or streams. I tried connecting the streets as though they were continuous with the dots.

(image removed)

But they are a source of confusion.

Arlington County, Virginia, is similar. It doesn't use the quadrants but does have a "North" or "South" designator depending on which side of US-50 you're on. East—west streets are numbered, with the numbering ascending as you move away from Route 50 (so First Street North is close to Route 50). However, the numbered streets are often not thru streets and the same number will pick up again some distance away in order to maintain the same grid. However, sometimes an additional number is needed and they then re-use the same number as a "Road" (and then, if yet another is needed, as a "Place"). For example, Alex Ovechkin used to live on 16th Street North. The next block north of his old house is 16th Road North, and then after that you hit 17th Street North. Then you have the north—south streets. Those start at the Potomac and work west in alphabetical order–except for each letter of the alphabet there are only a very few names authorized per "alphabet," and the "alphabets" consist of one-syllable, two-syllable, three-syllable, and four-syllable words in sequence (although Arizona Street is the only four-syllable name and it's so microscopic it doesn't show up on most maps because the City of Falls Church, which surrounds Arlington on either side there, calls it Meridian Street–Google Maps won't recognize the name Arizona Street, for example). The use of minimal names per "alphabet" leads to confusing situations where there can be five or six different streets scattered around the county with the same name–I think I worked out once that there are six different Buchanan Streets and none of them connect to each other. This was a real problem prior to sat-navs and mapping software if you forgot to ask "which Buchanan Street" the hot girl in your dorm lived on.....
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cl94 on July 10, 2014, 05:54:45 PM
Buffalo, NY has 3 French Roads, all of which intersect NY 78/ Transit Rd within a 15 mile stretch. There's one in southern Cheektowaga, one in nkrthern Cheektowaga and Depew, and then there's (North) French Road in Amherst. Two of them have an almost identical assortment of stores at or near the intersection, adding to the confusion. There's also a William Street in Buffalo/Cheektowaga and one in Lancaster.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: right_said_ted on July 10, 2014, 08:31:46 PM
I humbly submit the corner of McMicken and McMillan in Cincinnati

http://goo.gl/maps/Ca6rq

They're both "West", and if that weren't confusing enough, at this corner they're both marked as Streets, even though McMicken is really an Avenue

Oh and I almost forgot, this intersection isn't too far from Central Avenue and Central Parkway, which run parallel about a block apart from each other
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: BakoCondors on July 12, 2014, 06:38:51 PM
A couple here in Bakersfield, CA:

Olive Drive and Olive Street. Olive Dr is a major E-W thoroughfare in northwest Bakersfield (CA-99 exit 28) that originated as a county road; Olive Street is a quaint little N-S drive (:biggrin:) in the downtown "tree" streets. Many of Bakersfield's oldest and most historic homes are located there.

Panama Lane and Panama Road: Panama Lane is another major city thoroughfare, running E-W through south and southwest Bako (CA-99 exit 18). Running parallel to and two miles south of Panama Lane is Panama Road. West of Union Avenue (old US-99), it's CA-119 Taft Highway (formerly US-399) so there's no conflict in the city but east of Union, the two Panama's coexist to confuse unsuspecting farm workers and truck drivers new to the area.

Stine Road and New Stine Road: City arterial Stine Road runs N-S then splits. New Stine is a sort-of 1960's western bypass of Stine, Stine becoming residential while New Stine continues Stine's arterial character. The kicker is, the arterial road changes from Stine to New Stine at a minor intersection and the residential remainder of Stine is discontinuous from the arterial.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Bruce on July 16, 2014, 02:17:37 AM
The exit numbering of I-5 and street grid of Shoreline nearly align at exits 175/176, the latter being NE 175th Street. Exit signs can be confusing at first glance (https://www.google.com/maps/@47.729732,-122.324121,3a,75y,1.13h,90.87t/data=!3m4!1e1!3m2!1sMB6mHkEfhIrfKNGAJUCEvw!2e0)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: mrsman on July 18, 2014, 09:27:27 AM
Quote from: wisvishr0 on June 27, 2014, 12:19:51 AM
Not only does DC have a Quadrant system with repeating streets, but it also has repeating streets within quadrants. For example, Macomb St. NW connects MacArthur Blvd with Potomac Avenue (NW), but it also has an unrelated section that connects Wisconsin and Massachusetts Avenues, both in NW. It also has a section in the middle.

Actually, they seem to be related: if you see the map, the  Macombs have Cathedrals and Klingles below them, which are indeed "extensions" of the other over creeks or streams. I tried connecting the streets as though they were continuous with the dots.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fs11.postimg.org%2F9vpubc56b%2FScreen_Shot_2014_06_27_at_12_14_49_AM.png&hash=e0b1b83d95956a4954f2dc09e6013e2b3ec29deb)

But they are a source of confusion.

It might be confusing for some people, but I don't consider it confusing, because there are many cities that have streets that start and stop, yet retain their same name throughout.  Chicago and Los Angeles come to mind immediately having many similar examples.  You're right though that if someone were driving Macomb Street, they might not find their address without having to detour off the street and coming back on because of the breaks in the street.  But the fact that DC streets are alphabetical is very helpful.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: doorknob60 on July 22, 2014, 10:17:58 PM
In the Nampa/Caldwell area, there are three North-South arterials within about 2 miles with these genius names (from West to East): Midway Rd, Middleton Rd, and Midland Blvd. It's like they were trying to confuse people. Take a look for yourself:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F8sWjpgq.png&hash=5fd5d77a76b92c7f94d5a90bef1cfeb3ba270358)

In Bend, when they built the Bend Parkway (current US-97), the parts of the former route (now Business US-97) that aren't considered 3rd St. are legally called "Highway 97". For example, the address of the Fred Meyer is "61535 S Hwy 97", even though it is not on the mainline US-97 at all. The two roads parallel each other within a half mile of each other the entire way through Bend. Also, long time Bend residents tend to call the old section "Highway 97" and the new section "The Parkway", while newer residents will call anything along Business 97 "3rd St." even if it's not technically 3rd St. in the grid. If you hear the phrase "Highway 97" in Bend, you have no idea what they're talking about without additional clarification or context clues.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Duke87 on July 22, 2014, 10:46:34 PM
This thread has gone surprisingly long without someone mentioning this infamous example (https://www.google.com/maps/@40.7156883,-73.9042503,17z).

60th Street, 60th Place, 60th Lane, 60th Avenue, 60th Road, 60th Drive, and 60th Court. Each intersects at least one of the others. "The corner of 60th and 60th" could mean any of nine different intersections.

This is Queens street numbering at its finest. :sombrero:
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: doorknob60 on July 23, 2014, 01:22:00 PM
To add to the mid mess in Nampa, I noticed this a couple days ago:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FwEW2Ocg.png&hash=b0eaf9bb9b954e1559fa7c9c627df046feb3eacc)

A building named Midway Plaza on Middleton Rd! Whoever named this building was either confused himself and thought it was on Midway, or he wanted to mess with people and confuse them (sounds like a bad business strategy).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: WNYroadgeek on August 30, 2015, 09:48:45 PM
How did I forget this one? Delaware Ave. (NY 384) and Delaware Rd. in Tonawanda: https://www.google.com/maps/@42.9772661,-78.8675241,15z?hl=en
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Bruce on August 31, 2015, 04:47:39 PM
The corner of Bellevue Avenue E, Bellevue Court E, and Bellevue Place E in Seattle, just a stone's throw from the city of Bellevue, Washington.

https://goo.gl/maps/zHgBr

(https://i.imgur.com/77C1jBL.jpg)

(Source (https://www.reddit.com/r/Seattle/comments/1g28ln/the_bellevue_bellevue_bellevue_triangle/))
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: tchafe1978 on September 02, 2015, 02:29:54 PM
In my little town of Belmont of about 900 people in southwest Wisconsin, there is a recurring theme that keeps popping up. The "main"  street (WI 126) is named Mound Ave. On the north end of town where a popular truck stop is located, in W. Mound View Ave.  A section of former US 151 before the new expressway was built is named Mound Avenue Rd. There are country roads in the same vicinity named East Mound Rd. and West Mound Rd. Then there is another Mound View Rd. Just outside of Platteville. Two guesses as to what these roads are all named after.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: steviep24 on September 06, 2015, 04:51:12 PM
In my area there's Elmgrove Dr., Elmgrove Park and Elmgrove Crossing. All are off of Elmgrove Rd. in Gates, NY

I'm surprised no one's mentioned the "Nexus of the Universe" which is First St. at First Ave. in Manhattan.  :sombrero:

https://www.youtube.com/watch?v=b5Z_AqaS3Ps
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: roadman65 on September 06, 2015, 05:14:50 PM
Osceola County, FL had two Boggy Creek Road's intersecting each other.  Now one of them was renamed Simpson Road with another short segment renamed Fortune Road (both of which existed previously on spur alignments of the old Boggy Creek Road).

In Springfield, NJ you have two different Springfield Avenues that are connected via Miesel Avenue, but often to locals the Miesel Avenue connection is erroneously called Springfield Avenue as well.  To avoid confusion from the post office, one of the segments is called South Springfield Avenue and the other just plain ole Springfield Avenue.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Chris19001 on September 08, 2015, 12:13:45 PM
Being lazy, I nominate the entire Salt Lake City street grid protruding from the Temple area.
The first time I was there I quickly realized how much attention you have to pay to the full address. :(
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Rothman on September 08, 2015, 12:45:35 PM
Quote from: Chris19001 on September 08, 2015, 12:13:45 PM
Being lazy, I nominate the entire Salt Lake City street grid protruding from the Temple area.
The first time I was there I quickly realized how much attention you have to pay to the full address. :(


I'd agree with you about the avenues and other areas north of Temple Square (e.g., Ensign Peak), but the rest of the grid is as intuitive as it gets.  As long as you've got the address, you essentially have grid coordinates -- you can get there pretty much any way you'd like.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: roadman65 on September 08, 2015, 01:06:53 PM
One thing that I like is that Scotch Plains, NJ has Martine Avenue change names to Park Avenue in its Downtown area.  That is because the Borough of Fanwood is between the two segments of the same street.  So if its Park Avenue you know to look Downtown, if its Martine Avenue you know to look south of Fanwood.  Martine keeps its name in Fanwood, but at the re-entry going NB to Scotch Plains it totally changes.  So you have Martine start at Lake Avenue near the Clark- Scotch Plains border and continue through the residential areas of the township before entering Fanwood and keeping its name, and then becoming Park when Martine finally approaches the Downtown area of Scotch Plains.  If it were to remain Martine Avenue in both parts, that would create more confusion.

However, Scotch Plains does have an East Second Street and a West Broad Street, but they are not part of a grid but extensions of neighboring towns.  So you have East Second Street west of West Broad Street.  It happens a lot with one particular city having a N-S-E-W descriptor that continues its directional header into the next community, so North Broad Street in Elizabeth keeps the North header even in Hillside when in many places it would revert to its plain name.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Chris19001 on September 09, 2015, 03:37:13 PM
Quote from: Rothman on September 08, 2015, 12:45:35 PM
[As long as you've got the address, you essentially have grid coordinates -- you can get there pretty much any way you'd like.
Well it tripped me up as I figured W 5th turned into E 5th..  Rather than W, N, E, & W all living and intersecting with each other seemingly all over the place...  (but then I wasn't prepared at all for it so it was my fault) 
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Mark68 on February 01, 2019, 01:59:22 PM
In Parker, CO, there are no less than 15 streets that start with some version of Pine:

https://geographic.org/streetview/usa/co/parker.html

I live on one of them, and when I first moved to my apartment (which was a new complex), we couldn't order pizza from most places because our address was not updated in their database.

Note the intersection of Pine & Pine, which is a fairly major intersection on the east ridge. Pine Ln ends at Pine Dr at a 3-way stop.

https://goo.gl/maps/C6W1N5fa3xF2

Also, there are two Parker Roads in the area. The main N/S road in Parker, which is also State Highway 83, is Parker Rd. Mainstreet (one word) is the "main" E/W street, but east of the town limits, it's known as E Parker Rd.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: US 89 on February 01, 2019, 04:59:03 PM
There are two Foothill Drives in Salt Lake City remarkably close to each other (https://www.google.com/maps/@40.7483212,-111.8335459,16z). The history, of course, is that they connected in the past. The main SW/NE Foothill Drive originally went directly northwest to end at Sunnyside, and there was no road to the north. When the connection to 500 South did open, it was viewed as an extension of Foothill Drive, and the name went along with it.

I think the city gets around this issue by designating the short N/S bit of the highway as 2100 East, so technically there is only one Foothill for a given latitude. But if you asked someone what that road was, I'd bet 99% of them would say Foothill. Also, the segment between Sunnyside and 500 South may officially be Foothill Boulevard, but I don't think anybody makes that distinction. In fact, the only signage on that segment using the "Boulevard" suffix is a sign at the entrance to the VA hospital (https://goo.gl/maps/vDQ9BLbHGDC2).




A similar situation exists with Coors Blvd in Albuquerque (https://www.google.com/maps/@35.0573118,-106.7056184,16z), except the old road in that case has been renamed to Old Coors Drive.

And just a few miles to the north, at the north end of Coors Blvd, it splits into Coors Road and Coors By-Pass (https://www.google.com/maps/@35.1938072,-106.6576096,17z). Both of those suffixes are included on all street blades, which is rare to non-existent for that type of signage in Albuquerque.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: DJ Particle on February 04, 2019, 05:04:54 AM
Not only do Minnehaha Ave and Minnehaha Pkwy intersect just north of Minnehaha Park in Minneapolis...but there's also a Minnehaha Ave in St. Paul!
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: djsekani on February 04, 2019, 01:52:02 PM
I'll add in an example close to home. In San Bernardino, Del Rosa Drive and Del Rosa Avenue are local roads that run parallel to each other with sometimes inconsistent signage. To make things more confusing, at one point Del Rosa Avenue actually turns into Del Rosa Drive.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: US71 on February 10, 2019, 12:35:47 PM
In Springfield, MO  Grant Ave crosses Grand St
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: ftballfan on February 12, 2019, 10:07:04 AM
Manistee and Eastlake have the following streets: 1st St, 2nd St, 3rd St, 4th St, 5th St, 6th St
Manistee and Stronach have the following streets: 1st Ave, 2nd Ave, 3rd Ave, 4th Ave, 5th Ave, 6th Ave

Manistee and Stronach share the same ZIP code (49660) while Eastlake is PO Box only (49626) and areas immediately outside the Eastlake village limits have the Manistee ZIP code. Stronach used to be 49681 years ago, but the Avenues in Stronach have higher house numbers than the Manistee Avenues.

Also:
Manistee proper has both Ramsdell St and Ramsdell Rd (however, they're on opposite sides of the city)
Manistee, Eastlake, and Stronach all have a street named Main St
Manistee and Eastlake both have a street named Division St
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on February 12, 2019, 01:23:28 PM
Quote from: ftballfan on February 12, 2019, 10:07:04 AM
Manistee and Eastlake have the following streets: 1st St, 2nd St, 3rd St, 4th St, 5th St, 6th St
Manistee and Stronach have the following streets: 1st Ave, 2nd Ave, 3rd Ave, 4th Ave, 5th Ave, 6th Ave

Common.  Check out Manhattan, New York.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Mark68 on February 12, 2019, 01:36:09 PM
Quote from: kphoger on February 12, 2019, 01:23:28 PM
Quote from: ftballfan on February 12, 2019, 10:07:04 AM
Manistee and Eastlake have the following streets: 1st St, 2nd St, 3rd St, 4th St, 5th St, 6th St
Manistee and Stronach have the following streets: 1st Ave, 2nd Ave, 3rd Ave, 4th Ave, 5th Ave, 6th Ave

Common.  Check out Manhattan, New York.

Or almost any town in Utah & southeastern Idaho.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: hotdogPi on February 12, 2019, 02:21:18 PM
Merrimack St. is the name of the street at the exit for both Exit 44 (in Lawrence) and Exit 46 (in Methuen; also Route 110) on I-495 in Massachusetts, although the Exit 46 sign does not contain the street name. People on the MVRTA bus system ask which bus goes to Merrimack St., and they usually mean the one in Lawrence, even though buses go to both. This is not a case of the one in Methuen exclusively being called "110", either; both the name and the number are used.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: skluth on February 12, 2019, 03:12:28 PM
Palm Springs has the grouping of West Palm Canyon Drive, East Palm Canyon Drive, and South Palm Canyon Drive. (https://www.google.com/maps/@33.8017704,-116.5452686,18z) The main traffic flow is from East Palm Canyon to South Palm Canyon. About one mile north, South Palm Canyon turns into North Palm Canyon and runs parallel to Indian Canyon. Palm Canyon and Indian Canyon are parallel one-way streets running north-south through downtown.

Going north on Indian Canyon, there is this collection  (https://www.google.com/maps/@33.8255171,-116.5456547,16z)within five blocks while going through downtown - Arenas, Andreas, Amado, Alejo.

There are two consecutive I-10 exits for Date Palm Drive and Palm Drive (https://www.google.com/maps/@33.8721059,-116.4775581,13.5z). Palm Drive is the main N-S road in Desert Hot Springs. Date Palm Drive is the main N-S road through Cathedral City.

Calling any cul-de-sac off a street by the same name here is so common it's not worth talking about.

I also find the habit of naming streets with the full name of famous locals humorous. My route to/from Costco frequently involves taking Gerald Ford to Bob Hope to Dinah Shore. People don't shorten them to Ford, Hope, or Shore.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: djsekani on February 12, 2019, 05:34:18 PM
Quote from: skluth on February 12, 2019, 03:12:28 PM
Palm Springs has the grouping of West Palm Canyon Drive, East Palm Canyon Drive, and South Palm Canyon Drive. (https://www.google.com/maps/@33.8017704,-116.5452686,18z) The main traffic flow is from East Palm Canyon to South Palm Canyon. About one mile north, South Palm Canyon turns into North Palm Canyon and runs parallel to Indian Canyon. Palm Canyon and Indian Canyon are parallel one-way streets running north-south through downtown.

Going north on Indian Canyon, there is this collection  (https://www.google.com/maps/@33.8255171,-116.5456547,16z)within five blocks while going through downtown - Arenas, Andreas, Amado, Alejo.

There are two consecutive I-10 exits for Date Palm Drive and Palm Drive (https://www.google.com/maps/@33.8721059,-116.4775581,13.5z). Palm Drive is the main N-S road in Desert Hot Springs. Date Palm Drive is the main N-S road through Cathedral City.

Calling any cul-de-sac off a street by the same name here is so common it's not worth talking about.

I also find the habit of naming streets with the full name of famous locals humorous. My route to/from Costco frequently involves taking Gerald Ford to Bob Hope to Dinah Shore. People don't shorten them to Ford, Hope, or Shore.

Lived in Palm Springs for 15 years and never found anything really confusing other than Amado and Alejo. Took me forever to remember which one came before the other.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Rothman on February 12, 2019, 05:47:42 PM
Quote from: Mark68 on February 12, 2019, 01:36:09 PM
Quote from: kphoger on February 12, 2019, 01:23:28 PM
Quote from: ftballfan on February 12, 2019, 10:07:04 AM
Manistee and Eastlake have the following streets: 1st St, 2nd St, 3rd St, 4th St, 5th St, 6th St
Manistee and Stronach have the following streets: 1st Ave, 2nd Ave, 3rd Ave, 4th Ave, 5th Ave, 6th Ave

Common.  Check out Manhattan, New York.

Or almost any town in Utah & southeastern Idaho.
Nah.  The difference is that in the "Mormon grids" people refer to "1st East," "2nd North," etc.  It is actually quite intuitive.

In Queens, you say "19th" without a suffix like New Yorkers do, it could pertain to all sorts of streets
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: US 89 on February 12, 2019, 06:39:42 PM
Quote from: Rothman on February 12, 2019, 05:47:42 PM
Quote from: Mark68 on February 12, 2019, 01:36:09 PM
Quote from: kphoger on February 12, 2019, 01:23:28 PM
Quote from: ftballfan on February 12, 2019, 10:07:04 AM
Manistee and Eastlake have the following streets: 1st St, 2nd St, 3rd St, 4th St, 5th St, 6th St
Manistee and Stronach have the following streets: 1st Ave, 2nd Ave, 3rd Ave, 4th Ave, 5th Ave, 6th Ave

Common.  Check out Manhattan, New York.

Or almost any town in Utah & southeastern Idaho.
Nah.  The difference is that in the "Mormon grids" people refer to "1st East," "2nd North," etc.  It is actually quite intuitive.

In Queens, you say "19th" without a suffix like New Yorkers do, it could pertain to all sorts of streets

Thing is, out-of-towners will come in and not realize that the directions actually mean something, and you really do need all four pieces of information in an address, in that order.

In Salt Lake at least (and probably elsewhere in the state, though other grids aren't usually big enough for this) locals will usually leave off the directional of nearby streets unless there's obvious ambiguity (like where 900 East and 900 South intersect). Plus, outside of any particular contexts, the directionals for major streets will often be left off. It's common to hear "7th", "114th", or "56th", and it's assumed they're talking about 700 East, 11400 South, 5600 West. Either the other streets with a matching coordinate number are relatively minor (like 700 W and 700 S), or they don't actually exist (there is no other 11400, for example).
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Flint1979 on February 12, 2019, 06:59:37 PM
US-24 and M-24 aren't too far apart in Michigan. The northern terminus of US-24 (yes northern since it curves in Toledo) is at exit 93 on I-75 and the southern terminus of M-24 is at exit 81 on I-75. M-75 and I-75 aren't real close to each other but not real far apart from each other either but aren't really confused with each other.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: GaryV on February 12, 2019, 07:31:14 PM
Quote from: Flint1979 on February 12, 2019, 06:59:37 PM
US-24 and M-24 aren't too far apart in Michigan. The northern terminus of US-24 (yes northern since it curves in Toledo) is at exit 93 on I-75 and the southern terminus of M-24 is at exit 81 on I-75.

They used to connect in Pontiac.  Michigan in the early years extended a few US highways with the same numbered state highway.  24, 25, 112 and 131.  Interestingly enough, M-131 became an extension of US-131 when it was decided that US-131 would end in Petosky, not Traverse City.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: skluth on February 12, 2019, 07:47:11 PM
Quote from: djsekani on February 12, 2019, 05:34:18 PM
Quote from: skluth on February 12, 2019, 03:12:28 PM
Palm Springs has the grouping of West Palm Canyon Drive, East Palm Canyon Drive, and South Palm Canyon Drive. (https://www.google.com/maps/@33.8017704,-116.5452686,18z) The main traffic flow is from East Palm Canyon to South Palm Canyon. About one mile north, South Palm Canyon turns into North Palm Canyon and runs parallel to Indian Canyon. Palm Canyon and Indian Canyon are parallel one-way streets running north-south through downtown.

Going north on Indian Canyon, there is this collection  (https://www.google.com/maps/@33.8255171,-116.5456547,16z)within five blocks while going through downtown - Arenas, Andreas, Amado, Alejo.

There are two consecutive I-10 exits for Date Palm Drive and Palm Drive (https://www.google.com/maps/@33.8721059,-116.4775581,13.5z). Palm Drive is the main N-S road in Desert Hot Springs. Date Palm Drive is the main N-S road through Cathedral City.

Calling any cul-de-sac off a street by the same name here is so common it's not worth talking about.

I also find the habit of naming streets with the full name of famous locals humorous. My route to/from Costco frequently involves taking Gerald Ford to Bob Hope to Dinah Shore. People don't shorten them to Ford, Hope, or Shore.

Lived in Palm Springs for 15 years and never found anything really confusing other than Amado and Alejo. Took me forever to remember which one came before the other.

I don't have any problems with Andreas. Probably because it's so short. But I get the other three mixed up frequently. Maybe because I just moved here last summer.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Rothman on February 13, 2019, 08:09:54 AM
Quote from: US 89 on February 12, 2019, 06:39:42 PM
Quote from: Rothman on February 12, 2019, 05:47:42 PM
Quote from: Mark68 on February 12, 2019, 01:36:09 PM
Quote from: kphoger on February 12, 2019, 01:23:28 PM
Quote from: ftballfan on February 12, 2019, 10:07:04 AM
Manistee and Eastlake have the following streets: 1st St, 2nd St, 3rd St, 4th St, 5th St, 6th St
Manistee and Stronach have the following streets: 1st Ave, 2nd Ave, 3rd Ave, 4th Ave, 5th Ave, 6th Ave

Common.  Check out Manhattan, New York.

Or almost any town in Utah & southeastern Idaho.
Nah.  The difference is that in the "Mormon grids" people refer to "1st East," "2nd North," etc.  It is actually quite intuitive.

In Queens, you say "19th" without a suffix like New Yorkers do, it could pertain to all sorts of streets

Thing is, out-of-towners will come in and not realize that the directions actually mean something, and you really do need all four pieces of information in an address, in that order.

In Salt Lake at least (and probably elsewhere in the state, though other grids aren't usually big enough for this) locals will usually leave off the directional of nearby streets unless there's obvious ambiguity (like where 900 East and 900 South intersect). Plus, outside of any particular contexts, the directionals for major streets will often be left off. It's common to hear "7th", "114th", or "56th", and it's assumed they're talking about 700 East, 11400 South, 5600 West. Either the other streets with a matching coordinate number are relatively minor (like 700 W and 700 S), or they don't actually exist (there is no other 11400, for example).
Or you can tell which street they're talking about due to context (e.g., there's little confusing 6th South with 6th North).  I have lived in the area myself.

It isn't half as confusing out there as in NYC (I live in the Northeast).  In fact, once you take the 30 seconds or so to learn the layout, you can get to nearly any address one way or another.  You may not take the fastest way, but you'll get there.

As a tangent, I am finding that in recent years Utahns have been adopting old jokes from the Midwest and East in an attempt to increase their originality.  They now joke about "if you don't like the weather, just wait a minute" or the old joke that their seasons are winter and construction.  It is very odd, especially when Utah Mormon culture has its own very unique quirks...and, of course, green Jell-O.  They should stick to joking about them.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: cwf1701 on February 20, 2019, 04:34:44 PM
Another Michigan example, in St. Clair Shores, there is a (Greater) Mack Ave and Little Mack Ave. Greater Mack Ends at 10 Mile and Little Mack goes from 9 Mile and Harper to 14 Mile and Gratiot. Greater Mack is a continuation of Mack Ave. in Detroit.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Flint1979 on February 20, 2019, 07:49:10 PM
Quote from: cwf1701 on February 20, 2019, 04:34:44 PM
Another Michigan example, in St. Clair Shores, there is a (Greater) Mack Ave and Little Mack Ave. Greater Mack Ends at 10 Mile and Little Mack goes from 9 Mile and Harper to 14 Mile and Gratiot. Greater Mack is a continuation of Mack Ave. in Detroit.
Both are discontinuous streets. North of 9 Mile though Greater Mack starts becoming a residential side street so it's importance decreases. Greater Mack actually picks up again several blocks south of 11 Mile then has another discontinuous part before it ends at 13 Mile (the actual street ends a little further north at Harper as Avon Blvd.).

Little Mack branches off of Harper 1/4 of a mile north of 9 Mile and starts out as a 5 lane street stops at Gratiot, then right away picks up at 14 Mile and curves into Nunneley Road ending just south of the intersection of 16 Mile and Gratiot. The entire stretch north of 14 Mile is residential.

As to why these two streets have similar names is beyond me. The title of Greater and Little Mack helps a little though but I can see where it might be confusing.

Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Flint1979 on February 20, 2019, 07:52:21 PM
I know this is the case in Manhattan as well with the Avenues and Streets. In Flint, Michigan there is a set of streets going north of downtown that are numbered as Streets such as 1st Street, 2nd Street and so on. South of downtown there is a set of streets that are numbered as Avenues such as 1st Avenue, 2nd Avenue and so on. I can also see where this could get confusing since the these Streets and Avenues run the same direction. At least in Manhattan they run in different directions.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: thspfc on March 30, 2019, 02:26:47 PM
How many Peachtrees does Atlanta have?
Yikes.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Verlanka on March 31, 2019, 06:44:12 AM
Quote from: thspfc on March 30, 2019, 02:26:47 PM
How many Peachtrees does Atlanta have?
Yikes.

Too many to count :spin:
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: mgk920 on March 31, 2019, 11:11:25 AM
How many people sometimes confuse Kingery Highway with the Kingery Expressway in Chicagoand?

Also, the story of how Chicago got its ridiculously easy to navigate addressing grid is truly amazing - an average guy (Edward P. Brennan) who's job entailed constantly finding addresses all day long as part of his regular duties (he was a bill collector), someone who in reality was no different than anyone in this forvm, got fed up with the city's previous addressing mess, a mess that was so bad that it was even crimping the Post Office's style, and did something about it.  I consider him to be an inspiration for us to keep playing around with ideas and making it a point to push the good ones towards fruition.

:nod:

(A lot of other midwestern cities, including my hometown City of Appleton, WI, were readdressed at about that time, too, that idea was that good.)

Mike
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on March 31, 2019, 03:35:31 PM
Quote from: mgk920 on March 31, 2019, 11:11:25 AM
How many people sometimes confuse Kingery Highway with the Kingery Expressway in Chicagoland?

I lived in the Chicago area for a total of 16 years, and I didn't know until your post that there was such a thing as the Kingery Expressway.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Flint1979 on April 01, 2019, 03:21:10 PM
Quote from: mgk920 on March 31, 2019, 11:11:25 AM
How many people sometimes confuse Kingery Highway with the Kingery Expressway in Chicagoand?

Also, the story of how Chicago got its ridiculously easy to navigate addressing grid is truly amazing - an average guy (Edward P. Brennan) who's job entailed constantly finding addresses all day long as part of his regular duties (he was a bill collector), someone who in reality was no different than anyone in this forvm, got fed up with the city's previous addressing mess, a mess that was so bad that it was even crimping the Post Office's style, and did something about it.  I consider him to be an inspiration for us to keep playing around with ideas and making it a point to push the good ones towards fruition.

:nod:

(A lot of other midwestern cities, including my hometown City of Appleton, WI, were readdressed at about that time, too, that idea was that good.)

Mike
I don't think many because the Kingery Expressway is usually called the Tri-State still and Kingery Highway is a state highway running north and south.

I do love how Chicago's address system is.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: roadman65 on April 02, 2019, 11:29:08 PM
Wibur Cross Parkway and Wilbur Cross Highway in CT?  I imagine no one calls the latter by name being its part of I-84.  I know the former is called by name as no one (according to Wiki) calls the Merit Parkway or that by its number Route 15.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: GreenLanternCorps on April 03, 2019, 03:28:14 PM
Beavercreek, Ohio has Colonial Drive and Colonial Parkway within a mile of each other in adjacent developments:

https://www.google.com/maps/@39.6984158,-84.0423557,15.58z

Colonial Drive is in the upper left and has been around for over 30 years.  Colonial Parkway is in he lower right and is around 20 years old.

Used to live in B-creek on Colonial Drive and the Colonial Parkway sign threw me off the first time I saw it going up Factory Road...
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: ipeters61 on April 03, 2019, 04:02:48 PM
In Dover DE, we have South Little Creek Road and North Little Creek Road (DE-8).  They are two distinct, parallel roads (two longish blocks apart) which enter Little Creek on the south and north ends of town.

In Newark DE, there's an Orchard Road and an Orchard Avenue.

In the area of Harrington/Milford DE, the "DuPont Highway" name switches from US-13 to US-113 (US-13 becomes Sussex Highway south of this point).  The problem, though, is that the name doesn't really transfer seamlessly (prior to the 1990s, US-113 ended at US-13, but about 20 miles north in Dover...now US-113 ends at DE-1 in Milford).

In South Windsor CT, there are two Ellington Roads (CT-30 and CT-74), which used to connect until about 1993.

Oh, and my favorite, US-13 Business is Salisbury Boulevard and US-50 Business is Salisbury Parkway in Salisbury MD.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: MikieTimT on April 03, 2019, 04:39:43 PM
Bentonville, AR has got to be one of the most confusing for out of towners.  At the downtown square, Main St. and Central Ave. intersect, making the center of the street grid in town.  The N/S streets are letters and the E/W streets are numbers.  The town is essentially divided into quadrants.  For example, the street to the SE of the square is SE 2nd St., which intersects SE A St.  Letters and numbers get progressively larger as you get further from the square, but within about a 3 block radius of the square, you have to be really careful to note the full address, else you'll be a few blocks from your destination.  So, in summary, there are 4 2nd streets, 4 A streets, 4 3rd streets, 4 B streets, etc. all with a very short walk from each other, but progressively further apart the further from the square you get.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on April 03, 2019, 04:48:06 PM
Quote from: MikieTimT on April 03, 2019, 04:39:43 PM
Bentonville, AR has got to be one of the most confusing for out of towners.  At the downtown square, Main St. and Central Ave. intersect, making the center of the street grid in town.  The N/S streets are letters and the E/W streets are numbers.  The town is essentially divided into quadrants.  For example, the street to the SE of the square is SE 2nd St., which intersects SE A St.  Letters and numbers get progressively larger as you get further from the square, but within about a 3 block radius of the square, you have to be really careful to note the full address, else you'll be a few blocks from your destination.  So, in summary, there are 4 2nd streets, 4 A streets, 4 3rd streets, 4 B streets, etc. all with a very short walk from each other, but progressively further apart the further from the square you get.

That sounds like an excellent system, actually.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: 1995hoo on April 03, 2019, 06:01:10 PM
The Bentonville system sounds largely similar to DC. The quadrant is the key in telling you which of four possible addresses it is.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: ftballfan on April 06, 2019, 12:34:19 PM
I-96 has consecutive exits with Alden Nash Ave (Exit 52) and Nash Hwy (Exit 59)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: US 89 on April 06, 2019, 06:41:05 PM
Reminds me of I-40 west of Albuquerque. There's an exit for Atrisco Vista Blvd, and then the very next exit to the east is Arroyo Vista Blvd.

The funny part is Atrisco Vista Blvd was renamed from Paseo del Volcan sometime in the early 2010s, to avoid confusion with a new-construction Paseo del Volcan to the north in Rio Rancho.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Terry Shea on April 06, 2019, 10:05:50 PM
https://www.google.com/maps/place/Aylesworth+St+SE+%26+Patterson+Ave+SE,+Grand+Rapids+Charter+Township,+MI+49546/@42.9445789,-85.552036,3a,90y,90h,90t/data=!3m6!1e1!3m4!1sMbclyi-9LROFCu8djXDpXA!2e0!7i13312!8i6656!4m5!3m4!1s0x8818526565650e03:0x364ccd612a22a7a1!8m2!3d42.9447009!4d-85.551526
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on April 08, 2019, 01:13:31 PM
Quote from: Terry Shea on April 06, 2019, 10:05:50 PM
https://www.google.com/maps/place/Aylesworth+St+SE+%26+Patterson+Ave+SE,+Grand+Rapids+Charter+Township,+MI+49546/@42.9445789,-85.552036,3a,90y,90h,90t/data=!3m6!1e1!3m4!1sMbclyi-9LROFCu8djXDpXA!2e0!7i13312!8i6656!4m5!3m4!1s0x8818526565650e03:0x364ccd612a22a7a1!8m2!3d42.9447009!4d-85.551526

Zooming out of street view, it looks like that's just a street that turns the corner.  Cutter Pkwy to the west and south, Aylesworth to the east.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: djsekani on April 09, 2019, 10:15:05 AM
Quote from: ftballfan on April 06, 2019, 12:34:19 PM
I-96 has consecutive exits with Alden Nash Ave (Exit 52) and Nash Hwy (Exit 59)

San Diego: "Hold my beer..." (https://goo.gl/maps/GASQ5gXAo832)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Kulerage on April 09, 2019, 08:52:17 PM
Does it count if it was once a complete road but a bunch of new construction have caused it to become fragmented into a bunch of pieces?
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: MikieTimT on April 09, 2019, 09:01:39 PM
Quote from: kphoger on April 03, 2019, 04:48:06 PM
Quote from: MikieTimT on April 03, 2019, 04:39:43 PM
Bentonville, AR has got to be one of the most confusing for out of towners.  At the downtown square, Main St. and Central Ave. intersect, making the center of the street grid in town.  The N/S streets are letters and the E/W streets are numbers.  The town is essentially divided into quadrants.  For example, the street to the SE of the square is SE 2nd St., which intersects SE A St.  Letters and numbers get progressively larger as you get further from the square, but within about a 3 block radius of the square, you have to be really careful to note the full address, else you'll be a few blocks from your destination.  So, in summary, there are 4 2nd streets, 4 A streets, 4 3rd streets, 4 B streets, etc. all with a very short walk from each other, but progressively further apart the further from the square you get.

That sounds like an excellent system, actually.

It's actually pretty handy once you've gotten your head around it.  I could be put in a car blindfolded and dropped off at pretty much any intersection and easily (assuming I wasn't dropped 28 blocks from the square) walk back to the square.  The issue becomes when someone from out of town comes by and wants to park in your driveway for a half-marathon on a Saturday and picks the wrong C St. to park in bright and early on race day to get around parking congestion.  He parked at NW C St. instead of SE C St., so was in a random stranger's driveway all morning.  Thankfully they weren't home, so he didn't block anyone in or get towed.  For the life of me, I can't understand the need to torture one's self by running 13.1 miles around town.  Makes my joints hurt to think about it.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on April 09, 2019, 09:58:15 PM
Quote from: djsekani on April 09, 2019, 10:15:05 AM
I could be put in a car blindfolded and dropped off at pretty much any intersection and easily (assuming I wasn't dropped 28 blocks from the square) walk back to the square. 

SE 28th Street (Tractor Supply) is only two miles from the square.  That's certainly not too far to walk.  I used to walk that far every day to work and then home again in the evening.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Terry Shea on April 10, 2019, 07:44:30 PM
Quote from: kphoger on April 08, 2019, 01:13:31 PM
Quote from: Terry Shea on April 06, 2019, 10:05:50 PM
https://www.google.com/maps/place/Aylesworth+St+SE+%26+Patterson+Ave+SE,+Grand+Rapids+Charter+Township,+MI+49546/@42.9445789,-85.552036,3a,90y,90h,90t/data=!3m6!1e1!3m4!1sMbclyi-9LROFCu8djXDpXA!2e0!7i13312!8i6656!4m5!3m4!1s0x8818526565650e03:0x364ccd612a22a7a1!8m2!3d42.9447009!4d-85.551526

Zooming out of street view, it looks like that's just a street that turns the corner.  Cutter Pkwy to the west and south, Aylesworth to the east.
Correct.  But the sign has read Cutter Parkway on both sides for most of the last 55 years, at least.  Several years ago they changed the sign to Cutter Parkway/Aylesworth, but then changed it back a few years ago.  I never did understand it.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: kphoger on April 11, 2019, 02:24:49 PM
Quote from: Terry Shea on April 10, 2019, 07:44:30 PM

Quote from: kphoger on April 08, 2019, 01:13:31 PM

Quote from: Terry Shea on April 06, 2019, 10:05:50 PM
https://www.google.com/maps/place/Aylesworth+St+SE+%26+Patterson+Ave+SE,+Grand+Rapids+Charter+Township,+MI+49546/@42.9445789,-85.552036,3a,90y,90h,90t/data=!3m6!1e1!3m4!1sMbclyi-9LROFCu8djXDpXA!2e0!7i13312!8i6656!4m5!3m4!1s0x8818526565650e03:0x364ccd612a22a7a1!8m2!3d42.9447009!4d-85.551526

Zooming out of street view, it looks like that's just a street that turns the corner.  Cutter Pkwy to the west and south, Aylesworth to the east.

Correct.  But the sign has read Cutter Parkway on both sides for most of the last 55 years, at least.  Several years ago they changed the sign to Cutter Parkway/Aylesworth, but then changed it back a few years ago.  I never did understand it.

I'm guessing the short connector between that corner and Patterson & Aylesworth is officially part of Cutter Pkwy, but there are no houses facing it so it doesn't matter.  If that's true, then I think changing the sign to Parkway/Aylesworth is better even if it's technically inaccurate.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: Elm on May 04, 2019, 01:44:56 PM
Colorado Springs has a bunch of streets with "Cheyenne"  names, mostly in the vicinity of the Broadmoor, which is near Cheyenne Mountain. According to a TV piece (https://www.fox21news.com/news/curious-colorado/curious-colorado-why-so-many-cheyenne-streets/837446110), there are sixteen of them across the city, at least as of 2017.

For someone that doesn't live in the immediate area, you'll most likely use or drive by several of those streets on the way to the Cheyenne Mountain Zoo (https://goo.gl/maps/HkrP2GHnnvk5oGhj8), with greater potential for wrong turns when coming from I-25 at Nevada/Tejon. Part of the route in is usually taking Cheyenne Blvd, which is mostly parallel to Cheyenne Rd a block or two to the south. (Note that, further west (https://www.google.com/maps/@?api=1&map_action=map&center=38.790807,-104.863487&zoom=18&basemap=satellite) than relevant to the zoo, they join, then split into North and South Cheyenne Canyon Rd). I think it's the return trip from the zoo that can be more confusing, though. You start out going down Cheyenne Mountain Zoo Road and pass Cheyenne Mountain Blvd (that one winds through the Broadmoor, occasionally with directional prefixes). Ideally, you'll get back to Cheyenne Blvd, but you need to pass Cheyenne Rd first. If you turn too early on "˜Rd,' you'll end up on Nevada Ave instead of Tejon St as they drift apart, which is fine (it heads to the same I-25 interchange), but unexpected if you're not from the area.

A fun feature of a couple of these roads is that after a brief break east of Nevada Ave, Cheyenne Rd reappears and arcs down to intersect Lake Ave (https://www.google.com/maps/@?api=1&map_action=map&center=38.795728,-104.802498&zoom=18&basemap=satellite) one block west of Cheyenne Mountain Blvd (which you passed the west end of way back by the zoo). Also, a few honorable "Cheyenne"  mentions also go to Cheyenne Meadows Rd, which at either end is the first intersection south of Cheyenne Mountain Blvd, and to the one block of Cheyenne Ave (https://www.google.com/maps/@?api=1&map_action=map&center=38.840124,-104.818710&zoom=19&basemap=satellite) in downtown Colorado Springs, which is completely unrelated to the Broadmoor shenanigans.

---

In contrast to wherever all the "Cheyennes"  came from, present-day Colorado Springs tends to be more particular about similar street names. A while ago, they wouldn't allow what's now Middle Creek Pkwy to be "Black Squirrel Pkwy," (after the creek in question) although the only "Black Squirrel"  road I see is on the opposite side of Black Forest. In the same area as the "Cheyenne"  roads, they're now requiring part of Mount Washington Ave to be renamed because a section in the middle is being vacated with some other roads to make way for an urban renewal project. On the flip side, both Briargate Pkwy and Briargate Blvd are notable roads in the city.
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: ErmineNotyours on May 05, 2019, 04:41:00 PM
Traffic reporters used to have to distinguish the Alaskan Way Viaduct with the Alaskan Way surface street, though this hasn't been a problem since a few months ago.  :)
Title: Re: Streets and highways with similar names confusingly close to each other
Post by: TheHighwayMan3561 on May 27, 2019, 11:26:55 AM
Milwaukee has "Kilbourn Ave"  and "Clybourn St"  a couple exits apart.