usatr: United States select tourist routes

[the_spui_ninja]

The route on the other side of the Missouri has been turned around, seen by border labels being the wrong way around, giving an east to west route. That's the one that needs fixing.
https://travelmapping.net/hb/showroute.php?r=ia.lctrl&cr

IA,SD,MT: flip point order, keep border labels
ND: flip point order, SD/ND -> ND/SD, MT/ND stays as-is.

So I set that up so the Lewis and Clark trail heading up the river (east/north bank roughly) would be paralleling the outbound journey (St. Louis to Astoria) and heading down the river (west/south bank roughly) would be paralleling the return journey (Astoria to St. Louis with branches in Montana). I was inspired by the ND/SD "River Roads", where 1804 is on the east bank (for the outbound journey, the stretch north of Bismarck should be ND 1805 to be technically correct but whatever) and 1806 is on the west bank, as well as watching too many Lewis and Clark documentaries. That's also why the additional names for the Montana routes (that I added) aren't based off of cities, but off of features that were important to the expedition.

Why does Lewis & Clark Auto Trail (Dakotas-Nebraska) run north-to-south?

Typically routes in the US are done west to east and south to north, we all know that. While that connected segment is somewhat N-S, the whole trail is an W-E route and therefore this connected route should run from its western end just east of the Montana border (where the two routes either side of the Missouri River merge into one route) to its eastern one at the Kansas border (where the signed routes don't line up).

As I look at it, the trail is both an east-to-west and a west-to-east route, since Lewis and Clark went out and came back.

[yakra]

Fair enough, makes sense.

In that case my issue becomes about the waypoint labels at borders; many would need to be reversed to 1stRgn/2ndRgn.

I bring all this up because a datacheck for border labels is in development. I expect to post about it in the forum shortly.

[the_spui_ninja]

In that case my issue becomes about the waypoint labels at borders; many would need to be reversed to 1stRgn/2ndRgn.

Yeah I noticed that when I was looking at the files again, just kind of threw it together the first time. I'll adjust it so it makes sense.

[the_spui_ninja]

Also, I noticed that the Lincoln Highway in the NE panhandle (https://travelmapping.net/hb/showroute.php?units=miles&u=the_spui_ninja&r=ne.linhwy) has a bunch of points where it jumps on and off US 30 that aren't in the US 30 file.

[si404]

When I said west-east I didn't mean west to east, but not north-south.

Later this evening I'll sort out a proposal to 'dakotarize' the routes (so one bank westwards the other eastwards where the route is either side of a river.

I've found signs in Kentucky, but not a huge number (similar to Montana). Ohio and West Virginia seem to have some signs and I have a map of Pennsylvania's route.

[si404]

Right, so using the 1804 and 1806 designations in the Dakotas, the westbound ('outbound') uses the north/east banks of rivers and the eastbound return (inbound') uses the south/west banks of rivers. Montana and Idaho are a bit different as its where they split up on the way back, and because they don't follow a river over the mountains.

'OUTBOUND'
Ohio River
in.lctrl

Missouri River
mo.lctrl
ia.lctrl,sd.lctrl,nd.lctrl

Colombia River
wa.lctrl

INBOUND
Colombia River
or.lctrl
or.lctrlher

Missouri River
nd.lctrlwes,sd.lctrlwes,ne.lctrl
ks.lctrl,mo.lctrlsou

Ohio River
ky.lctrl (not yet finished making wpt)

COULD GO EITHER WAY
id.lctrl - links to wa.lctrl (which is 'outbound') and mt.lctrlbla (which is mostly inbound-only in terms of route)

SPURS/CONNECTORS
nd.lctrlkee
nd.lctrlnew
nd.lctrlpic
nd.lctrlwas
nd.lctrlbis
nd.lctrlsbi
sd.lctrlmob
sd.lctrlpie
mo.lctrlwes

MONTANA - these routes may need reforming (and are really terribly signed, though I've not checked it that thoroughly yet)
mt.lctrlmis (Missouri River Downstream) - at least the bit east of 'Forks of the Yellow' is unsigned. Runs on northside, so outbound.
mt.lctrlfor (Forks of the Yellowstone) - outbound, unsigned, is really part of 'Missouri River Downstream' (with the bit on US2 north of it some sort of bypass/truck route leg)
mt.lctrl (Missouri Headwaters) - eastern bit south of the river so inbound (Lewis), western bit outbound, far western bit inbound (Clark) as well as outbound. Some signs at Dillon
mt.lctrlyel (Yellowstone River) - inbound (Clark), some signs in Billings area
mt.lctrlbla (Blackfeet) - from Bitterroot Mountains section eastward is inbound (Lewis), westward to Idaho border is both
mt.lctrlbit (Bitterroot Mountains) - outbound and inbound (Clark)

[yakra]

On nd.lctrl.wpt, SD/ND was already right, but got reversed in yesterday's pull request.

[the_spui_ninja]

MONTANA - these routes may need reforming (and are really terribly signed, though I've not checked it that thoroughly yet)
mt.lctrlmis (Missouri River Downstream) - at least the bit east of 'Forks of the Yellow' is unsigned. Runs on northside, so outbound.
mt.lctrlfor (Forks of the Yellowstone) - outbound, unsigned, is really part of 'Missouri River Downstream' (with the bit on US2 north of it some sort of bypass/truck route leg)
mt.lctrl (Missouri Headwaters) - eastern bit south of the river so inbound (Lewis), western bit outbound, far western bit inbound (Clark) as well as outbound. Some signs at Dillon
mt.lctrlyel (Yellowstone River) - inbound (Clark), some signs in Billings area
mt.lctrlbla (Blackfeet) - from Bitterroot Mountains section eastward is inbound (Lewis), westward to Idaho border is both
mt.lctrlbit (Bitterroot Mountains) - outbound and inbound (Clark)

So with those most of it is on existing routes, so I was fine with adding duplicate badly signed routes based off the official NPS routing. I broke them up based on what made sense to me at the time. For mt.lctrl, I wanted to get a cohesive route from North Dakota to Lemhi Pass, and so kind of gave up on the river sides convention since sometimes there isn't a route on both sides of the river.

The only place I added "new" mileage was east of Billings, where there is signage along Old Hwy 312.

[si404]

I've found a lot more signs in Montana than I thought - after changes in route rather than a more useful before.

[shiggins]

There's a misplaced or missing point on the LC Trail in Ashland, KY. At the point US60_W, we have the LC Trail following Winchester Ave (US 23 Business), but by the next point east, it's jumped one block northeast to Greenup Ave (mainline US 23). Either one of these points is incorrect, or there is at least one point missing wherever the LC Trail jumps from Winchester to Greenup.