So I've been doing some editing in OpenStreetMap lately to tag expressway=yes routes, and I've come across the very strange alignments of MS 57 and 63.
These two routes are 4 lane divided highways in their most important parts, filling in a gap in the state's network between Meridian and the coast right where US 45 leaves the state for Alabama.
The thing is, they meet in the middle, become concurrent through Leakesville, then split off in their respective directions.
(https://media.discordapp.net/attachments/413070502580453387/994322041824104568/unknown.png)
So that makes me wonder, do any of your states have really strange state route alignments?
VA 165
MA 80, which makes a 3/4 circle to nowhere. A bit unusual since Massachusetts is usually pretty good with route coherence.
MA 31 leaves the road it's on and comes back to it in Charlton, but I've been told that there's good reason for that (not that I can really see it).
MA 129 could easily parallel I-95/MA 128 in Lynnfield instead of going to downtown Wakefield and then overlapping with US 1, but then downtown Wakefield would be without a numbered route.
Am I the only one who's failing to see what's weird about the OP's example? It's just a concurrency, right? Maybe wrong-way signed(?), but still, not all that unusual. Am I missing something?
MA 145 in Winthrop is basically just a loop that exists just so Winthrop can have a numbered route.
I nominate CO Highway 30 (https://www.google.com/maps/dir/39.6529751,-104.9178733/39.6384669,-104.7167979/@39.6792078,-104.8647306,12.5z/data=!4m19!4m18!1m15!3m4!1m2!1d-104.8659222!2d39.7240871!3s0x876c7cc2d58f1843:0x3e60ab5c9dcb5b5d!3m4!1m2!1d-104.7466876!2d39.7202159!3s0x876c6186ff9a009f:0xb7bbd293e3252602!3m4!1m2!1d-104.7161583!2d39.6750311!3s0x876c8a660eda4637:0x556fee3d83f7cd46!1m0!3e0), which begins at I-25/US 285 (Hampden Avenue) and ends at Gun Club Road/Quincy Avenue near the E-470 toll road. While the termini are approximately 12 miles apart as the crow flies, the route begins going due east on Hampden, then it curves north on Havana Street for 5 miles, then turns east on 6th Avenue, then curves back south about 6 miles to the end for a total of over 20 miles for the route.
Quote from: JayhawkCO on July 07, 2022, 10:58:29 AM
Am I the only one who's failing to see what's weird about the OP's example? It's just a concurrency, right? Maybe wrong-way signed(?), but still, not all that unusual. Am I missing something?
I suggest that the reason is it's a continuous 4-lane expressway where the primary travel is through but the route numbers switch on the expressway and split apart to follow their original paths.
QC 132 and QC 169 are both loops that end at themselves, and QC 368 is a loop that never ends.
Quote from: JayhawkCO on July 07, 2022, 10:58:29 AM
Am I the only one who's failing to see what's weird about the OP's example? It's just a concurrency, right? Maybe wrong-way signed(?), but still, not all that unusual. Am I missing something?
IMO it's both about the concurrency but with the expressway switching highway numbers at the interchange with both highways going off the freeway onto a concurrency. It's relatively common for a highway to change numbers at an interchange but usually one number ends at that point; both going off in the same direction as a concurrency is the difference here. It's similar to the I-74/80 interchange SE of the Quad Cities (https://www.google.com/maps/@41.4435657,-90.3330325,3210m/data=!3m1!1e3?hl=en) but with both highways going off in the same direction rather than opposite directions.
Similar to what the OP showed, the WV 9/WV 45 routing along the south side of Martinsburg.
Quote from: WillWeaverRVA on July 07, 2022, 11:10:34 AM
Quote from: froggie on July 07, 2022, 10:33:07 AM
VA 165
I think VA 156 would qualify as well.
156 at least made sense in its original configuration, connecting a bunch of Civil War sites east of Richmond. It was when it was extended south of the James and took over VA 154 that it became a bit more odd. I don't think 165 ever made sense though.
Some candidates in Utah, leaving out institutional routes which are their whole own beast.
SR 68 (https://goo.gl/maps/cKRuzMpJq9jiC1H97) at the north end in Bountiful. The route travels 67 miles almost due north along Redwood Rd through three counties, then turns east on 500 South in Bountiful, then back south on 200 West and then southwest to an interchange at US 89 - which it just crossed a mile or two back.
SR 147 (https://goo.gl/maps/mfP3e7JhKyByf1Vz7) in Utah County, which stair steps along section line roads and goes east through Spanish Fork, crosses US 89 into Mapleton, then turns north and west and hooks back to 89. There is really no reason this all should be one route, and the designations around Benjamin are especially dumb. 147 and 115 "bump" at Benjamin, and that north-south road through Benjamin changes from 115 to 147 to 77 in the span of a mile.
It used to be even worse - the southwest end of 147 used to extend back east on 10400 South into Payson. That got removed from the state system in the early 2000s, but they didn't combine 147 and 141 at the same time, so now those routes just end at each other for no particular reason.
CA 77 and it's over abundance of reassurance shields on Route despite a true freeway to freeway connection with I-880:
https://www.gribblenation.org/2019/02/california-state-route-77-real-shortest.html?m=1
Quote from: skluth on July 07, 2022, 11:50:16 AM
Quote from: JayhawkCO on July 07, 2022, 10:58:29 AM
Am I the only one who's failing to see what's weird about the OP's example? It's just a concurrency, right? Maybe wrong-way signed(?), but still, not all that unusual. Am I missing something?
IMO it's both about the concurrency but with the expressway switching highway numbers at the interchange with both highways going off the freeway onto a concurrency. It's relatively common for a highway to change numbers at an interchange but usually one number ends at that point; both going off in the same direction as a concurrency is the difference here. It's similar to the I-74/80 interchange SE of the Quad Cities (https://www.google.com/maps/@41.4435657,-90.3330325,3210m/data=!3m1!1e3?hl=en) but with both highways going off in the same direction rather than opposite directions.
A more extreme version like the Mississippi example is the expressway from Columbus OH to Newcomerstown OH which are the following designations without ever having to make a turn:
OH 161, OH 37, OH 16 and US 36
The weirdest alignment has to be the AR-43 OK-20 cosign. Besides the fact that two different state highways are cosigned, I don't even understand why OK-20 needed to be cosigned there since it ends at eh Missouri state line.
Routes that run a significant distance one set of cardinal directions, then flip to the other set (examples: MN 95, WIS 23)
^
And M-123
Quote from: ethanhopkin14 on July 07, 2022, 02:16:23 PM
The weirdest alignment has to be the AR-43 OK-20 cosign. Besides the fact that two different state highways are cosigned, I don't even understand why OK-20 needed to be cosigned there since it ends at eh Missouri state line.
Isn't the road maintained by ODOT?
M-43 now that it doesn't go through downtown Kalamazoo.
Quote from: Takumi on July 07, 2022, 12:27:45 PM
Quote from: WillWeaverRVA on July 07, 2022, 11:10:34 AM
Quote from: froggie on July 07, 2022, 10:33:07 AM
VA 165
I think VA 156 would qualify as well.
156 at least made sense in its original configuration, connecting a bunch of Civil War sites east of Richmond. It was when it was extended south of the James and took over VA 154 that it became a bit more odd. I don't think 165 ever made sense though.
Honestly I think VA 156 made more sense south of the James River than north of it. Though this is probably due to personal bias as I grew up along this route in Prince George County.
OH 37 - Alignment looks more like 3 or 4 separate routes than a single route
OH 15 - Same as above. Easternmost 19 miles also happen to be an expressway that's part of the Columbus-Toledo corridor
Quote from: US 89 on July 07, 2022, 04:55:16 PM
Quote from: ethanhopkin14 on July 07, 2022, 02:16:23 PM
The weirdest alignment has to be the AR-43 OK-20 cosign. Besides the fact that two different state highways are cosigned, I don't even understand why OK-20 needed to be cosigned there since it ends at eh Missouri state line.
Isn't the road maintained by ODOT?
Yep, it's part of Control Section 20-21-22.
It being concurrent routes from both states makes a lot of sense to me. Oklahoma maintains the road, but it does veer fully into Arkansas at points. Arkansas wants to maintain continuity between AR-43 and MO-43.
Oklahoma could "fix" the situation by designating the north-south road as OK-43, but that designation is already in use in southeast Oklahoma, and besides it would lead to two OK highways that end at each other, which is always awkward. And if Arkansas is kicking Oklahoma any money to help maintain the road, then Arkansas deserves to have their shield up too. Really, the concurrency is the best way of handling the situation.
Quote from: 74/171FAN on July 07, 2022, 06:26:41 PM
Quote from: Takumi on July 07, 2022, 12:27:45 PM
Quote from: WillWeaverRVA on July 07, 2022, 11:10:34 AM
Quote from: froggie on July 07, 2022, 10:33:07 AM
VA 165
I think VA 156 would qualify as well.
156 at least made sense in its original configuration, connecting a bunch of Civil War sites east of Richmond. It was when it was extended south of the James and took over VA 154 that it became a bit more odd. I don't think 165 ever made sense though.
Honestly I think VA 156 made more sense south of the James River than north of it. Though this is probably due to personal bias as I grew up along this route in Prince George County.
You could argue it would make more sense as two separate routes: one from Templeton to Hopewell, and the battlefield tour route for the other one. The parts between them can stay 5, 10, and 106.
M-185 makes a complete car-free circuit along the shoreline of Mackinac Island (https://www.google.com/maps/@45.8693326,-84.6292149,13.67z?hl=en)
Quote from: skluth on July 07, 2022, 08:49:04 PM
M-185 makes a complete car-free circuit along the shoreline of Mackinac Island (https://www.google.com/maps/@45.8693326,-84.6292149,13.67z?hl=en)
Excepting emergency vehicles of course. Close to car free, but not completely.
Quote from: Flint1979 on July 07, 2022, 05:27:10 PM
M-43 now that it doesn't go through downtown Kalamazoo.
What exactly does it do now? Reading the link below doesn't really help much, except to make me think that the City of Kalamazoo is run by a bunch of crazies!
http://www.michiganhighways.org/listings/M-043.html
Instead of continuing sw from Richland into Kalamazoo, M-43 now turns nw following M-89 to Plainwell, then s on US-131, before rejoining the route w on West Main St toward South Haven. The portion of M-43 from Richland sw through Comstock was renumbered as M-343.
Quote from: TheHighwayMan394 on July 07, 2022, 03:27:41 PM
Routes that run a significant distance one set of cardinal directions, then flip to the other set (examples: MN 95, WIS 23)
You can add Iowa 136 to that list
WV 55. This route was originally only from Moorefield running east from US 220 to Wardensville, and then into Virginia as a continuation of VA 55. The road number designation has been extended westward along a bunch of concurrencies. Now, the only independent segments are the glorified exit ramp/access road from Corridor H (US 48) to US 220, and a short segment from Craigsville to US 19.
Quote from: JayhawkCO on July 07, 2022, 10:58:29 AM
Am I the only one who's failing to see what's weird about the OP's example? It's just a concurrency, right? Maybe wrong-way signed(?), but still, not all that unusual. Am I missing something?
Others have pointed out the situation overall... it's a lot of weird things coming together.
Also, because each half uses a different state highway up until the concurrency, the concurrency ends up being a wrong-way concurrency.
(https://i.imgur.com/IaoZ2FK.jpeg)
Edit: Also, here's the relation on OpenStreetMap for each route so you can see it yourself.
MS 57: https://www.openstreetmap.org/relation/1527073
MS 63: https://www.openstreetmap.org/relation/1527071
WA 96 takes a winding route instead of a more direct one (built later by the county): https://goo.gl/maps/9LAuD6BMzne7C22r5
WA 99's gap in Tukwila, created in 2004, which means that its northern segment just suddenly transitions into WA 599.
WA 509 between Fife and Des Moines, born of a few decades of not building a connection in between. Once the Puget Sound Gateway is complete, there will have to be some more realigning to prevent a long I-5 concurrency.
Quote from: JayhawkCO on July 07, 2022, 10:58:29 AM
Am I the only one who's failing to see what's weird about the OP's example? It's just a concurrency, right? Maybe wrong-way signed(?), but still, not all that unusual. Am I missing something?
Quote from: MoiraPrime on July 08, 2022, 03:35:45 PM
Others have pointed out the situation overall... it's a lot of weird things coming together.
Also, because each half uses a different state highway up until the concurrency, the concurrency ends up being a wrong-way concurrency.
(https://i.imgur.com/IaoZ2FK.jpeg)
Interesting take. I presumed that the "weird alignment" was that the bypass had two separate route numbers heading towards each other until they met, then both routes exited onto a multiplex.
WV 62. Before, WV 62 went from Charleston to Point Pleasant. With the realignment of US 33, WV 62 was extended over the old US 33 routing and now ends near Ripley. 100 mile road to drive from end to end, approximately 35 miles between its termini.
Quote from: amroad17 on July 08, 2022, 09:51:06 PM
WV 62. Before, WV 62 went from Charleston to Point Pleasant. With the realignment of US 33, WV 62 was extended over the old US 33 routing and now ends near Ripley. 100 mile road to drive from end to end, approximately 35 miles between its termini.
WV 62 does have a weird history: (http://www.vahighways.com/wvannex/route-log/wv062.htm)
1922-30 Huntington to Point Pleasant to Mason
1931 Point Pleasant to Mason to Mt Alto
1932-37 Point Pleasant to Mason to Evans
1937-70 Point Pleasant to Mason
1970-2004 Charleston to Point Pleasant to Mason
since 2004 Charleston to Point Pleasant to Mason to Ripley
M-96 and BL I-94 in Battle Creek. They have a same-way concurrency on the east side of town and a separate wrong-way concurrency on the west side.
Routes that make a 180-degree turn and reverse the cardinal directions, like M-123 and M-22 in Michigan. That makes for interesting signage:
(https://i.imgur.com/nubVFWS.jpg)
(https://i.imgur.com/TmtFyxq.jpg)
(both posted previously)
Quote from: wanderer2575 on July 09, 2022, 02:26:29 PM
M-96 and BL I-94 in Battle Creek. They have a same-way concurrency on the east side of town and a separate wrong-way concurrency on the west side.
Routes that make a 180-degree turn and reverse the cardinal directions, like M-123 and M-22 in Michigan. That makes for interesting signage:
(https://i.imgur.com/nubVFWS.jpg)
(https://i.imgur.com/TmtFyxq.jpg)
(both posted previously)
The M-22 sign should at least have control cities on them so you know what city you are heading towards. If you saw a sign that said Traverse City and Empire you would know where you're going. But the route does head south either way you go.
So there is a sign in between the two assemblies pictured that indicates you go straight for Traverse City and right for Frankfort.
Quote from: NWI_Irish96 on July 11, 2022, 08:46:42 AM
So there is a sign in between the two assemblies pictured that indicates you go straight for Traverse City and right for Frankfort.
Yep so there isn't any confusion, M-22 heads south in both directions from this interchange so the signs are right as well.
^Similar to the way US 321 is signed SOUTH both ways from Elizabethtown, TN--except at the point where the switchover occurs. Probably to avoid "motorist confusion".
Another one is OH 211 in Dover. The alignment itself is not weird--it is the cardinal directions. Here SOUTH is north and NORTH is south. The "southern" terminus is north of its "northern" terminus. I believe that this is a holdover of when OH 211 used to be routed down current OH 39 west of Dover and New Philadelphia. This iteration of OH 211 is the second one that Ohio DOT decided to use for a state maintained road in Dover and kept the same cardinal directions. Of course, the DOT could have changed the cardinal directions around or even used EAST-WEST, just like the Kentucky Transportation Cabinet did with KY 1017 (Turfway Road in Florence, KY). When KY 1017 was rerouted from Turfway onto the new Aero Parkway, which runs from near Turfway Park to KY 18 between Florence and Burlington, the cardinal directions were changed from NORTH-SOUTH to WEST-EAST.
New York Route 28 has a weird "C"-shape. It starts heading west and northwest, then north, then northeast, then southeast. It always struck me as weird that this is one contiguous route designation.
https://en.wikipedia.org/wiki/New_York_State_Route_28
TN SR 99
This route runs E-W, N-S, E-W, N-S, E-W. This thing winds around for almost no apparent reason.
Quote from: Avalanchez71 on July 16, 2022, 03:40:49 AM
TN SR 99
This route runs E-W, N-S, E-W, N-S, E-W. This thing winds around for almost no apparent reason.
Is it strange that one end of this highway is at US-64 and the other end is at SR-64?
Quote from: Mapmikey on July 09, 2022, 01:55:02 PM
Quote from: amroad17 on July 08, 2022, 09:51:06 PM
WV 62. Before, WV 62 went from Charleston to Point Pleasant. With the realignment of US 33, WV 62 was extended over the old US 33 routing and now ends near Ripley. 100 mile road to drive from end to end, approximately 35 miles between its termini.
WV 62 does have a weird history: (http://www.vahighways.com/wvannex/route-log/wv062.htm)
1922-30 Huntington to Point Pleasant to Mason
1931 Point Pleasant to Mason to Mt Alto
1932-37 Point Pleasant to Mason to Evans
1937-70 Point Pleasant to Mason
1970-2004 Charleston to Point Pleasant to Mason
since 2004 Charleston to Point Pleasant to Mason to Ripley
That last extension was poorly planned. WV 62 is signed as north/south, which makes sense on its pre-2004 alignment. The problem is now that the first 29 miles of "southbound" WV 62 heading out from Ripley actually go northwest. It would have made more sense if WVDOH followed ODOT's lead and numbered old US 33 as WV 833, leaving WV 62 as it was.
PA 53, PA 153, and PA 253 have weird alignments around Houtzdale, PA. PA 53 is the main road. It takes a longer but more heavily traveled alignment between Van Ormer and Houtzdale, which sort of makes sense. PA 253 also travels between these two points.
The strange bit is the relationship between PA 153 and PA 253. PA 253's northern end is at PA 53 two blocks from PA 153 in Houtzdale. It heads southwest out of town, picking up PA 453 for a 5-mile multiplex. Near the end of the multiplex, it intersects PA 153's southern end after that route took a more direct route south out of Houtzdale. PA 253 then breaks off to head southwest to its end at PA 53.
It seems like a more reasonable routing would be to cut PA 253 back so it just goes from PA 53 at Houtzdale to PA 453 at Ramey, unwinding the PA 453 multiplex. You can extend PA 153 south over PA 253's old alignment to PA 53.
Quote from: paulthemapguy on July 11, 2022, 11:37:20 PM
New York Route 28 has a weird "C"-shape. It starts heading west and northwest, then north, then northeast, then southeast. It always struck me as weird that this is one contiguous route designation.
https://en.wikipedia.org/wiki/New_York_State_Route_28
Similarly, WA 28 is like a stretched-out "W" that could easily be chopped up into several shorter routes.
https://en.wikipedia.org/wiki/Washington_State_Route_28
I'd suggest adding WV 92 to this list. From 1933 to the about 1950, this road has a fairly reasonable alignment - WV 7 at Reedsville to US 250 at Belington.
Around 1950, the pointless extensions began. First, it was multiplexed north along WV 7 into Morgantown, then across the Star City Bridge, up what is now US 19 to WV 100 (then US 19) just short of the PA line. This was eventually cut back to a pointless multiplex into downtown Morgantown, and in the 1980s, it was reverted to its 1933 endpoint at WV 7 in Reedsville.
On the southern end of things, in 1970, WV 92 gained a 55-mile multiplex with US 250 from Belington to Bartow, then a 33-mile multiplex with WV 28 from Bartow to WV 39 at Minnehaha Springs, followed by a 4-mile WV 39 multiplex, before heading south on its own for 31 miles to US 60 at White Sulphur Springs.
Later, WV 28 was relocated between Dunmore and WV 39 cutting the WV 28/WV 92 multiplex back to 15 miles. US 250 and US 33 were relocated onto a partial bypass of Elkins in 2001, leaving WV 92 on its own for 4 miles on the west side of town. Basically, you have 9-mile multiplex, a 4-mile independent segment, then 56 miles of multiplexes before striking out on its own for 53 miles.
Personally, I'd cut WV 92 back to the 1933 routing between Reedsville and Belington. Move US 33 and US 250 back to their former alignment coming into Elkins since the bypass is of little benefit to their traffic, eliminating this standalone segment of WV 92. You could move WV 28 onto WV 92's routing south of Dunmore and renumber the portion of WV 28 between Dunmore and Huntersville something like WV 428.
Quote from: Flint1979 on July 16, 2022, 07:42:20 AM
Quote from: Avalanchez71 on July 16, 2022, 03:40:49 AM
TN SR 99
This route runs E-W, N-S, E-W, N-S, E-W. This thing winds around for almost no apparent reason.
Is it strange that one end of this highway is at US-64 and the other end is at SR-64?
That is correct. I am sure there are a whole lot of folks that want to travel from Waynesboro to unincorporated Bradyville. It looks like the designation was slapped on a bunch of local roads to be added to the State Road system.
Quote from: Avalanchez71 on July 17, 2022, 10:28:22 AM
Quote from: Flint1979 on July 16, 2022, 07:42:20 AM
Quote from: Avalanchez71 on July 16, 2022, 03:40:49 AM
TN SR 99
This route runs E-W, N-S, E-W, N-S, E-W. This thing winds around for almost no apparent reason.
Is it strange that one end of this highway is at US-64 and the other end is at SR-64?
That is correct. I am sure there are a whole lot of folks that want to travel from Waynesboro to unincorporated Bradyville. It looks like the designation was slapped on a bunch of local roads to be added to the State Road system.
Even if there was I wouldn't take TN-99 to get between the two.
Quote from: Bitmapped on July 16, 2022, 07:04:54 PM
I'd suggest adding WV 92 to this list. From 1933 to the about 1950, this road has a fairly reasonable alignment - WV 7 at Reedsville to US 250 at Belington.
Around 1950, the pointless extensions began. First, it was multiplexed north along WV 7 into Morgantown, then across the Star City Bridge, up what is now US 19 to WV 100 (then US 19) just short of the PA line. This was eventually cut back to a pointless multiplex into downtown Morgantown, and in the 1980s, it was reverted to its 1933 endpoint at WV 7 in Reedsville.
On the southern end of things, in 1970, WV 92 gained a 55-mile multiplex with US 250 from Belington to Bartow, then a 33-mile multiplex with WV 28 from Bartow to WV 39 at Minnehaha Springs, followed by a 4-mile WV 39 multiplex, before heading south on its own for 31 miles to US 60 at White Sulphur Springs.
Later, WV 28 was relocated between Dunmore and WV 39 cutting the WV 28/WV 92 multiplex back to 15 miles. US 250 and US 33 were relocated onto a partial bypass of Elkins in 2001, leaving WV 92 on its own for 4 miles on the west side of town. Basically, you have 9-mile multiplex, a 4-mile independent segment, then 56 miles of multiplexes before striking out on its own for 53 miles.
Personally, I'd cut WV 92 back to the 1933 routing between Reedsville and Belington. Move US 33 and US 250 back to their former alignment coming into Elkins since the bypass is of little benefit to their traffic, eliminating this standalone segment of WV 92. You could move WV 28 onto WV 92's routing south of Dunmore and renumber the portion of WV 28 between Dunmore and Huntersville something like WV 428.
I have an old WV map from around 1972 or so that shows the segment of WV 28 running from WV 92 down to WV 39 as a county road. The concurrency with WV 92 came later. At the time of that map, WV 92 was a solo route from US 250 down to White Sulphur Springs (not including the short WV 39 concurrency).
Quote from: hbelkins on July 17, 2022, 03:00:41 PM
I have an old WV map from around 1972 or so that shows the segment of WV 28 running from WV 92 down to WV 39 as a county road. The concurrency with WV 92 came later. At the time of that map, WV 92 was a solo route from US 250 down to White Sulphur Springs (not including the short WV 39 concurrency).
I don't believe WV 92 was ever by itself between US 250 at Bartow and Dunmore. This route was WV 28 before WV 92 got extended and the WVDOH maps I have from 1970-1976 show both routes multiplexed to WV 39 at Minnehaha Springs, where WV 28 then ended.
The 1980 WVDOH map shows WV 28 moved onto what had been CR 11 between Dunmore and WV 39 near Huntersville. WV 92 stayed on WV 28's prior alignment through Minnehaha Springs.
Quote from: Bitmapped on July 17, 2022, 03:32:48 PM
Quote from: hbelkins on July 17, 2022, 03:00:41 PM
I have an old WV map from around 1972 or so that shows the segment of WV 28 running from WV 92 down to WV 39 as a county road. The concurrency with WV 92 came later. At the time of that map, WV 92 was a solo route from US 250 down to White Sulphur Springs (not including the short WV 39 concurrency).
I don't believe WV 92 was ever by itself between US 250 at Bartow and Dunmore. This route was WV 28 before WV 92 got extended and the WVDOH maps I have from 1970-1976 show both routes multiplexed to WV 39 at Minnehaha Springs, where WV 28 then ended.
The 1980 WVDOH map shows WV 28 moved onto what had been CR 11 between Dunmore and WV 39 near Huntersville. WV 92 stayed on WV 28's prior alignment through Minnehaha Springs.
WV 28 was extended south of US 250 in 1935 following today's WV 92 path to WV 39 (plus went west to Marlinton.
http://www.vahighways.com/wvannex/route-log/wv028.htm
Incidentally, WV 92 once went west of US 250 Belington.
http://www.vahighways.com/wvannex/route-log/wv092.htm