Highway Data Discussion > Completed Highway Systems Threads
usaar: Arkansas state highways
mapcat:
usaar was activated promoted to preview tonight. Ready for peer-review if anyone wants to tackle 787 routes (for now).
Here are some preliminary ideas and observations I made while compiling the set, adapted from the README.md file on GitHub:
Unsigned concurrencies are treated as gaps between separate routes unless the concurrency follows a single route between splits in the same county.
Instead of Alternate, Business, Truck, or Spur banners, auxiliary routes are posted with suffixes (i.e. AR 00 Business = "AR 00B"). Route names for these auxiliary routes follow the same convention (AR00B instead of AR00Bus, with or without city label). Signage for some spurs is "Spur AR 00S": this is treated as a bannerless AR00S (a similar situation exists with at least one truck route).
All 32 AR980 routes have a suffix so that renaming will not be necessary if any change length or are (de)commissioned in the future.
I'm not sure how to deal with AR43 in OK (specifically its westward bend along OK20): AR43 is concurrent with OK20 along state line, but bends west for some distance to be totally within OK, so it probably should have points where it crosses state line, but no corresponding state-line points exist in the OK20 file.
AR75S is signed "Truck AR 75S", but I've avoided using banners anywhere else. It behaves like a truck route (loop starting and ending on AR 75, bypassing a low bridge), but those are typically signed as AR 00T.
AR151 in usaar is longer than the AR151 in usansf and deserves to be free of a suffix, but is correcting this worth the trouble?
AR922-1A is signed AR722-1A on US165, which is the only signage viewable on GMSV.
Hard to believe that we haven't had a new US set since last August. Enjoy!
Jim:
--- Quote from: mapcat on June 15, 2018, 10:55:38 pm ---usaar was activated tonight. Ready for peer-review if anyone wants to tackle 787 routes (for now).
--- End quote ---
Just to clarify the terminology for everyone, the system was promoted to preview status, not active status.
rickmastfan67:
US-71 & US-62 are missing the point for AR-612 (I-49 Exit #77). Thus, those two routes are broken along I-49.
yakra:
--- Quote ---All 32 AR980 routes have a suffix so that renaming will not be necessary if any change length or are (de)commissioned in the future.
--- End quote ---
This seems appropriate for these airport roads, and I agree with this solution.
--- Quote ---I'm not sure how to deal with AR43 in OK (specifically its westward bend along OK20): AR43 is concurrent with OK20 along state line, but bends west for some distance to be totally within OK, so it probably should have points where it crosses state line, but no corresponding state-line points exist in the OK20 file.
--- End quote ---
OK20 on its own, if we ignore the concurrency, I'd think is comparabe to ME NH153. There's a bit that dips unambiguously into one state, and another bit that follows the state line, that we've got to include in one state or the other (See also: TX US71).
The state line portion is in the Okladot, but not AHTD shapefiles. (But OTOH, it *is* in the Benton county map -- even the clearly-within-OK portion. So, it's... something of importance, I guess?) I'd say then that this portion should be considered within OK, and thus the state line points are already included: OK OK20 AR43_S OK/AR.
Rather than include this section as part of AR AR43Sil, IMO it'd be better off as part of an OK AR43 route.
OTOH, there's no AR43 sign here, just a MO43 sign. Should we just consider AR43 an unsigned route here and leave it out?
On the 3rd hand, it's a bit early for Missouri, innit? It's not like MO43 continues anywhere south of here. Sign-o for AR43, perhaps? How close are we to craIG county?
I don't see any pressing need for shaping point(s) at the dip into OK, even if I did otherwise for AB17 along the SK border.
--- Quote ---AR75S is signed "Truck AR 75S", but I've avoided using banners anywhere else. It behaves like a truck route (loop starting and ending on AR 75, bypassing a low bridge), but those are typically signed as AR 00T.
--- End quote ---
Looks fine to me; I'd have handled this the same way.
--- Quote ---AR151 in usaar is longer than the AR151 in usansf and deserves to be free of a suffix, but is correcting this worth the trouble?
--- End quote ---
Not worth the trouble; we don't wanna break .list files. There's precedent in MO110 vs. MO110Han on the CKC corridor.
--- Quote ---AR922-1A is signed AR722-1A on US165, which is the only signage viewable on GMSV.
--- End quote ---
>:(
froggie:
--- Quote ---Unsigned concurrencies are treated as gaps between separate routes unless the concurrency follows a single route between splits in the same county.
--- End quote ---
Given how ARDOT has done things for decades, unless you have conclusive proof (whether the rare signage or it appears on maps or in route logs) that a concurrency exists, leave it out entirely.
Navigation
[0] Message Index
[#] Next page
Go to full version