And THAT,
I think, just about wraps it up for Operation Arkansas Cleanup.
Some final notes...
Banners vs. suffixes:Routes (EG, business, truck, spur) that may be signed as bannered routes in other jurisdictions are signed with a letter suffix in Arkansas. A small minority of routes did have banner plates above the shields, but even these, as in all cases, contained a letter suffix after the route number in the shield.
Thus I standardized state highway waypoint labels to use letter suffixes instead of banners.
The only exception was, I left
AR US412BusHun AR23Cit as-is -- it's signed for vanilla AR23 at its north end, and TO AR74 at its south end. Thus, I didn't see any example of a route signed with a 'C' for City suffix in the field. I'm open to changing this.
There may be other state highway City routes I've not come across on my cleanup of the US routes etc. I'll search thru the shapefiles and see what I can come up with, if there's anything I can check out in GMSV.
High-numbered routes:I didn't do another pass to add in high-numbered routes, such as the signed AR9xx routes mapcat & I discussed via PM. I figure this task would be more easily handled as part of usaar development.
Odd Y legs:For example,
AR US165 AR1_S in Back Gate officially connects to AR1Y; AR1 proper is the east-west leg that connects
here. However, AR1Y is not signed as such: at the south end there's just signage for each direction of US165; at the north end there's signage for vanilla AR1, which is the more sensible route for thru traffic to take.
(Looking at satellite view, the left turn onto actual-AR1-proper isn't even all that feasible...) As this is what thru travelers following signs for AR1 would be doing, I just went with the "no-build" option here. So yeah, however you may wanna handle this when the time for usaar comes...
ISTR there may have been another case where I did something similar, but I can't remember where/what it was.
