Travel Mapping

Highway Data Discussion => In-progress Highway Systems & Work => Completed Highway Systems Threads => Topic started by: mapcat on June 15, 2018, 10:55:38 pm

Title: usaar: Arkansas state highways
Post by: mapcat on June 15, 2018, 10:55:38 pm
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!
Title: Re: usaar: Arkansas state highways
Post by: Jim on June 15, 2018, 11:07:58 pm
usaar was activated tonight. Ready for peer-review if anyone wants to tackle 787 routes (for now).

Just to clarify the terminology for everyone, the system was promoted to preview status, not active status.
Title: Re: usaar: Arkansas state highways
Post by: rickmastfan67 on June 16, 2018, 01:23:26 am
US-71 & US-62 are missing the point for AR-612 (I-49 Exit #77).  Thus, those two routes are broken along I-49.
Title: Re: usaar: Arkansas state highways
Post by: yakra on June 16, 2018, 02:08:21 am
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.
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.
OK20 on its own, if we ignore the concurrency, I'd think is comparabe to ME NH153 (http://travelmapping.net/hb/index.php?r=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 (http://travelmapping.net/hb/index.php?r=tx.us071)).
The state line portion is in the Okladot, but not AHTD shapefiles. (But OTOH, it *is* in the Benton county map (https://www.arkansashighways.com/maps/Counties/County%20PDFs/BentonCounty.pdf) -- 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 (https://www.google.com/maps/@36.4224379,-94.6055818,3a,15y,48.12h,88.41t/data=!3m9!1e1!3m7!1soBswUPuxaNzq9jVeMwNIMA!2e0!7i3328!8i1664!9m2!1b1!2i41), 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.
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?
Not worth the trouble; we don't wanna break .list files. There's precedent in MO110 (http://travelmapping.net/hb/index.php?r=mo.mo110) vs. MO110Han (http://travelmapping.net/hb/index.php?r=mo.mo110han) on the CKC corridor.

Quote
AR922-1A is signed AR722-1A on US165, which is the only signage viewable on GMSV.
>:(
Title: Re: usaar: Arkansas state highways
Post by: froggie on June 16, 2018, 07:57:38 am
Quote
Unsigned concurrencies are treated as gaps between separate routes unless the concurrency follows a single route between splits in the same county.

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.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on June 16, 2018, 09:46:37 am
Quote
Unsigned concurrencies are treated as gaps between separate routes unless the concurrency follows a single route between splits in the same county.

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.

Do that, and the number of routes included would probably increase by 50%.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on June 16, 2018, 09:48:26 am
US-71 & US-62 are missing the point for AR-612 (I-49 Exit #77).  Thus, those two routes are broken along I-49.

Thanks. Fixed in my copy.
Title: Re: usaar: Arkansas state highways
Post by: froggie on June 16, 2018, 10:20:56 am
Quote
Unsigned concurrencies are treated as gaps between separate routes unless the concurrency follows a single route between splits in the same county.

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.

Do that, and the number of routes included would probably increase by 50%.

Wouldn't be the first region with lots of route lists.  And since ARDOT doesn't actually consider these concurrencies, it would also be the proper/correct way to do it.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on June 16, 2018, 10:49:05 am
Wouldn't be the first region with lots of route lists.  And since ARDOT doesn't actually consider these concurrencies, it would also be the proper/correct way to do it.
True, but all they would all be suffixed routes, making it much less user-friendly than usaky or usapr, whose route numbers are almost all unique.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on June 16, 2018, 11:27:51 am
They're obviously intended to be one continuous route. Except 159. F that route.

edit: obviously a few others are separate routes too.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on June 16, 2018, 12:02:49 pm
They're obviously intended to be one continuous route. Except 159. F that route.
Yeah, that one was my personal unfavorite.

43 makes very little sense as a continuous route. There has to be a story behind it.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on June 16, 2018, 08:38:24 pm
43 makes very little sense as a continuous route. There has to be a story behind it.
The west piece was designated in 1971 (replacing AR 99) to match Missouri, but the east piece was not renumbered. A similar thing happened with AR 37 in 1976 (replacing AR 47).
Title: usaar: Arkansas
Post by: neroute2 on November 02, 2019, 06:52:44 pm
Should 130 be truncated to 1B? That's where the official end is (https://www.arkansashighways.com/maps/Counties/County%20RAS/RAS%20Maps%20PDF/marka2_ras.pdf), and the supposed overlap is only signed north/westbound (sometimes with to plates above west 130). Eastbound on 130, you get to 1B and 130 signage just ends. This would affect the files for 130, 1BDew (AR130_N -> AR130), and 1 (AR1B/130 -> AR1BDew_S - or AR1BDeW_S?).

1: AR1BDew_N -> AR1BDeW_N?
1: AR243 -> AR243Mar?
1: US64Bus/284 -> US64B/284
1: US64/64Spr -> US64/64S
1: LawRd -> CR407/428 (https://www.google.com/maps/@35.7525891,-90.690304,3a,15y,358.89h,84.84t/data=!3m6!1e1!3m4!1sqvX6RWkhNwDCMUz-hpGqAg!2e0!7i13312!8i6656)?
1/US 49: WhiRd -> CR701/902 (https://www.google.com/maps/@35.8645382,-90.6136887,3a,75y,222.06h,71.47t/data=!3m6!1e1!3m4!1sBH90FcKbG2Q1ggxP1KgvNA!2e0!7i13312!8i6656)?
1/US 49: US49Bus* -> US49B*
1/US 49: US49Spr -> US49Y
1/US 49: ClaySt -> CR542 (https://www.google.com/maps/@36.3384981,-90.2205088,3a,15y,53.67h,84.19t/data=!3m6!1e1!3m4!1srUL4Zk2QhgaRmRqOjvD3Tg!2e0!7i13312!8i6656)?
1McG: US165 is a wye junction; maybe move the point to the center or the south intersection (which has right of way where the two branches meet)
1BDeW: AR130_N -> AR130_W (or just AR130 - see above)
1BVan/364: CR358 -> CR358/362 (https://www.google.com/maps/@35.3136519,-90.7733469,3a,15y,129.49h,85.01t/data=!3m6!1e1!3m4!1sneORqriY1E_MDTl5a4P55A!2e0!7i13312!8i6656)
4: AR4SSpr -> AR4S
5: 5MiRd -> 5MileRd
5: CR46 -> StaCemRd (https://www.google.com/maps/@36.1547804,-92.1647186,3a,15y,49.55h,83.06t/data=!3m7!1e1!3m5!1sdd6df78wIe4POgW9NYGidw!2e0!5s20151201T000000!7i13312!8i6656) (Staggs Cemetery Road (https://arkansasgravestones.org/view.php?id=296247))
5: MocCreRd -> CR227 (https://www.google.com/maps/@36.1580608,-92.2162799,3a,15y,162.45h,83.3t/data=!3m6!1e1!3m4!1sqnVCdeNkJRrZK2_ybdQXtQ!2e0!7i13312!8i6656)?
5: US62Bus_W -> US62B_W, US62Bus_E -> US62B_E
5: the block of Main Street is one-way northbound, so move US62B_W southwest a block to the main intersection?
5: AR178_E -> AR178_S?
5Lit: BalGate -> BalGateEnt (https://www.google.com/maps/@34.6168343,-92.9059267,3a,24.1y,298.79h,89.77t/data=!3m6!1e1!3m4!1sgifPo8RI7v4I0_PcyqqmbA!2e0!7i13312!8i6656)
5Lit: NBJamRd has been realigned east
5Lit: I-30SerRd_E -> I-30_E (just as the west split is I-30/35, not just AR35)
5Lit: add SprRd and BryPkwy (access to I-30; the latter is what OSM and the Goog call Echo Lake Blvd)
5Lit: US70Bus -> US70B
Title: Re: usaar: Arkansas
Post by: mapcat on November 02, 2019, 08:06:14 pm
Thanks for doing the review.

Re 130, I'm inclined to leave it since it is signed in one direction but welcome input from anyone else with an opinion on this. It won't be the only instance where signage and official ends disagree.

Re the names for points at usausb routes, I followed the convention established by yakra when he did Operation Arkansas Cleanup (http://forum.travelmapping.net/index.php?topic=8.0) prior to handing the state over to me. Compare New York and Ohio, which use US20Alt point labels for intersections with routes signed US 20A. I didn't use the same convention for points at routes such as AR4B on purpose.

I'll address the others next week when I get some more editing time.
Title: Re: usaar: Arkansas
Post by: neroute2 on November 02, 2019, 09:49:46 pm
I disagree with but understand using Bus/Spr etc. But surely at least "49Y" in a shield should be US49Y, not US49Spr?

7: US167Bus_S -> US167(15), US63_N -> US167(16), ChaRd -> US167(17)
7: US79B_N -> US79Bus_N (ouch)
7: AR128_S -> AR128_E, AR128_N -> AR128_W
7/8: CR340 -> CR311/340
7: NavTrl intersects farther south (opposite Fargo Lane)
7: Ar88_W -> AR88_S, AR88_E -> AR88_N?
5 has DeSotoBlvd and 7 has DesBlvd for the same road. I don't know which is correct, since the name isn't signed in public areas.
7: USFS11 -> FR11? (street sign says Forest Rd 11)
7: USFS36110 -> FR86 or Trl86 (street sign says Trail 86, but shield is the same as FR11)
7/16: LurLp -> ToAR123_N? (name is unposted)
7/16: OldAR7 -> CR7120 (https://www.google.com/maps/@35.8201171,-93.1627911,3a,18.7y,251.38h,95.78t/data=!3m6!1e1!3m4!1ss8_OGnKqMeGHd7wCsdtkUg!2e0!7i13312!8i6656)
7: GumSprRd -> CR8675? (https://www.google.com/maps/@35.9397143,-93.1660162,3a,15y,215.69h,89.31t/data=!3m6!1e1!3m4!1s2lPPPlvMhO0JZMCLoe5wGw!2e0!7i13312!8i6656)
7: CR80 -> CR2890 (https://www.google.com/maps/@36.0622203,-93.1373757,3a,15.8y,320.32h,90.86t/data=!3m6!1e1!3m4!1sdNmELy2y6ZQnoxNqXQR88A!2e0!7i13312!8i6656)
7: AR7SSpr -> AR7SMar
7B: Bro -> BroSt (https://www.google.com/maps/@33.3649174,-92.725302,3a,17y,132.57h,86.17t/data=!3m6!1e1!3m4!1sni1zAtqKdF6Rl_tKyfbTUg!2e0!7i13312!8i6656)
7SMar: SkiLoopDr -> CR3353 (https://www.google.com/maps/@36.1132561,-93.1231655,3a,35.9y,243.96h,90.76t/data=!3m6!1e1!3m4!1s4qzX4orvtvIReIQ4UCrQ6Q!2e0!7i13312!8i6656)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 03, 2019, 06:32:31 pm
8: AR375_E -> AR375_S
8: USFS38 -> CanCreWMA (https://www.google.com/maps/@34.4690288,-93.9552642,3a,15y,226.5h,87.89t/data=!3m6!1e1!3m4!1skL6eKvnqAhePaqtfHsBogg!2e0!7i13312!8i6656)?
8: CR334 -> CR334/336
8: BanRd -> CR17 (https://www.google.com/maps/@33.7576514,-92.2389975,3a,17.8y,165h,85.46t/data=!3m6!1e1!3m4!1snB07oaeE5OrwoMTAIbtUuw!2e0!7i13312!8i6656)?
8: AR189 -> AR189Kin, AR189_N -> AR189Ham_N? (both are signed north)
8: AR209_W -> AR209Par, AR209_E -> AR209Rea
8S: AR8/27 -> AR8 (standard for suffixed routes)
9: BaiCutRd -> BaiCut (https://www.google.com/maps/@34.6312646,-92.7663874,3a,15y,51.34h,90.06t/data=!3m6!1e1!3m4!1sFLN2NQMUT_LFjSzX6QWIOQ!2e0!7i16384!8i8192)
9: AR92_N -> AR92_E
9/16: AR16Lp_W -> Hwy16Lp_W (https://www.google.com/maps/@35.6332595,-92.3643155,3a,57.7y,312.07h,79.52t/data=!3m6!1e1!3m4!1szK5grllnmb_rqO3hFOFLAg!2e0!7i3328!8i1664)
9: AR5_S -> AR5/14_S, AR5/14 -> AR5/14_N
10/309: move LakeCutRd east to the other intersection
10: AR324_N -> AR324Ado, AR324_W -> AR324Lak
10: missing point at US70Bus
10: add CumSt_S?
11: StiLetRd -> LetRd (https://www.google.com/maps/@34.9202229,-91.5641934,3a,15y,66.38h,89.24t/data=!3m6!1e1!3m4!1spfZi90uLgb6Ll-torxc7qA!2e0!7i13312!8i6656)?
11Sta: AR293_S -> AR293Sta, AR293_N -> AR293Sel (both are signed south)

How sure are we that 12 doesn't use 71B to 94 in Rogers? This sign (https://www.google.com/maps/@36.3551327,-94.122447,3a,15y,292.49h,90.03t/data=!3m6!1e1!3m4!1sCQRa-mFW3DPKI9gmD5s_5w!2e0!7i13312!8i6656) points westbound traffic left on 94, and there are some to 12 signs at the 71B/94 intersection. On the other hand, eastbound signs exist on I-49 north showing the routing we have. Some discussion on AARoads. (https://www.aaroads.com/forum/index.php?topic=3390.msg117481#msg117481)

12: CR8615 -> CR8240/8615
13: US79 -> US63/79
13sea: GSJ at MainSt
14: OldUS65 -> RidRd?
14: move AR281_N west to the cutoff; AR281_N -> ToAR281_N
14: AR268_W -> AR268Lea, AR268_E -> AR268Mul
14: SprCreRd -> CR135 (https://www.google.com/maps/@36.006195,-92.4043591,3a,75y,340.96h,77.4t/data=!3m6!1e1!3m4!1sUhD-2wRPS6sZMAgYgE2R1Q!2e0!7i3328!8i1664)?
14: LinHillRd -> LinHillLn? OSM shows both names and the Goog shows the latter
14/140: DickKingRd is closed (https://www.google.com/maps/@35.6142156,-90.3907633,3a,38.3y,276.83h,90.8t/data=!3m6!1e1!3m4!1sYEP7Yq5RPg0gqFLAe3cTHw!2e0!7i13312!8i6656)
14: CRS449 -> CRS449/W1020
Title: Re: usaar: Arkansas state highways
Post by: yakra on November 04, 2019, 12:39:02 pm
I disagree with but understand using Bus/Spr etc. But surely at least "49Y" in a shield should be US49Y, not US49Spr?
If that were the case, US1A & US1B would be such as well though.
Quote from: http://travelmapping.net/devel/manual/wayptlabels.php
For the US Highways, local conventions of using suffixes instead of banners are ignored. Use banners here. NY US 20A is US20Alt here.

7: AR128_S -> AR128_E, AR128_N -> AR128_W
7: Ar88_W -> AR88_S, AR88_E -> AR88_N?
This appears to be on "direction letter refers to the relative position of the intersection along the route whose file is being made (http://travelmapping.net/devel/manual/wayptlabels.php)" grounds.

5 has DeSotoBlvd and 7 has DesBlvd for the same road. I don't know which is correct, since the name isn't signed in public areas.
FWIW, shapefiles have "De Soto", 2 words (thus DeSoto), at AR7, and "DeSoto" & "Desoto" (DeS / Des) N & S respectively of AR5. Heh.

7: USFS11 -> FR11? (street sign says Forest Rd 11)
7: USFS36110 -> FR86 or Trl86 (street sign says Trail 86, but shield is the same as FR11)
'FR[0-9]\+' (http://forum.travelmapping.net/index.php?topic=3245) style labels seem pretty common nation(world?)wide (566 examples in AK AL AR AZ CA CO ESP-AS ID KY LA MB MI MN MO MT NM NV OR PA TX UT VA WI WY). There are 4 'ForRd[0-9]\+' examples; incl. 2 in TX I could change if appropriate.
@neroute2 has found all the AR 'USFS[0-9]\+' examples. There are 6 in LA & 1 in MI.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 04, 2019, 08:30:07 pm
I disagree with but understand using Bus/Spr etc. But surely at least "49Y" in a shield should be US49Y, not US49Spr?
If that were the case, US1A & US1B would be such as well though.
Quote from: http://travelmapping.net/devel/manual/wayptlabels.php
For the US Highways, local conventions of using suffixes instead of banners are ignored. Use banners here. NY US 20A is US20Alt here.
This (https://www.google.com/maps/@36.3777562,-93.5844523,3a,28.7y,100.08h,84.73t/data=!3m6!1e1!3m4!1ssdHTM0kl1tuWl6bBZ3jL4A!2e0!7i13312!8i6656) is US 62S, AKA US 62 Spur.
This (https://www.google.com/maps/@36.0566869,-90.5044213,3a,15y,242.76h,88.39t/data=!3m6!1e1!3m4!1svEm4qLxKn4LXzymq02TjsA!2e0!7i13312!8i6656) is US 49Y, not AKA anything bannered.

7: AR128_S -> AR128_E, AR128_N -> AR128_W
7: Ar88_W -> AR88_S, AR88_E -> AR88_N?
This appears to be on "direction letter refers to the relative position of the intersection along the route whose file is being made (http://travelmapping.net/devel/manual/wayptlabels.php)" grounds.
But this falls under "The direction letter should match the signed direction the concurrent route is splitting toward."
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 04, 2019, 09:25:12 pm
15eld: TramRd -> CR51 (https://www.google.com/maps/@33.0943736,-92.8540817,3a,35.9y,315.32h,80.66t/data=!3m6!1e1!3m4!1sOkLXBU1-NbuiC40szQwatg!2e0!7i13312!8i6656)?
16: US412 -> US412/59 (to match the 16S file)
16: DraRd -> CR662 (https://www.google.com/maps/@36.0804559,-94.3173953,3a,18.3y,267.57h,88.34t/data=!3m6!1e1!3m4!1svUkWgOUm5BiiWXyXbkXjog!2e0!7i13312!8i6656)? (maybe realigned west to the main intersection)
16: DouSprRd -> CR880 (https://www.google.com/maps/@36.0792843,-94.2545701,3a,75y,111.44h,80.43t/data=!3m6!1e1!3m4!1sWuTrb3zDP_4DhlLaPOX9vg!2e0!7i13312!8i6656)?
16: LkSeqDr -> CR50 (https://www.google.com/maps/@36.0466026,-94.0756836,3a,30.2y,111.18h,83.41t/data=!3m6!1e1!3m4!1s3L9qqOlbQve0B2HhMV_fpg!2e0!7i13312!8i6656)?
16: 1stAve -> CR44 (https://www.google.com/maps/@36.0016876,-94.0088124,3a,17.3y,185.34h,85.53t/data=!3m6!1e1!3m4!1sB_IrZGivw-tnSZgqZOApBw!2e0!7i13312!8i6656)?
16: BlaOakRd -> CR57 (https://www.google.com/maps/@35.9730261,-94.0048072,3a,43.9y,6.01h,81.84t/data=!3m6!1e1!3m4!1s3phKghkXxAUMxI7GS-7d5g!2e0!7i3328!8i1664)?
16: CR314 -> CR5201 (https://www.google.com/maps/@35.8427348,-93.8835171,3a,41y,26.81h,80.36t/data=!3m7!1e1!3m5!1sNPP0hSoCy43e7j8YVtSIxg!2e0!5s20071201T000000!7i3328!8i1664) and another route that I can't make out
16: CR3 -> something else that I can't read (https://www.google.com/maps/@35.7816178,-93.5016014,3a,46.5y,315.82h,85.94t/data=!3m6!1e1!3m4!1sanfDof_rRlgr-wVNQ0KHjQ!2e0!7i3328!8i1664)
16: OldAR27 -> OldHwy27?
16: LoGapRd -> CR9 (https://www.google.com/maps/@35.6327909,-92.68003,3a,46.2y,129.45h,81.89t/data=!3m6!1e1!3m4!1sK1paFSM_JNMhJaRC4_CoVA!2e0!7i3328!8i1664)?
16: AR110_W -> AR110Shi, AR110_E -> AR110Heb
17: 3ForRd -> CR43 (https://www.google.com/maps/@35.0984059,-91.2338289,3a,36.5y,19.14h,81.63t/data=!3m6!1e1!3m4!1sbItnrJOLLXrymEdwGYSNFg!2e0!7i3328!8i1664)?
17: US64Bus -> US64Bus_E (https://www.google.com/maps/@35.2703769,-91.2352796,3a,15.9y,138.1h,85.06t/data=!3m6!1e1!3m4!1swnhA9r6d0wBey-d-y5x3Qw!2e0!7i13312!8i6656) (and US64BusMcC should extend back to US 64)
17: move WasSt south to CR22 (https://www.google.com/maps/@35.4456504,-91.2306245,3a,41.8y,63.25h,73.26t/data=!3m6!1e1!3m4!1s3dOG0RGoDsHs78otvptAfA!2e0!7i13312!8i6656)?
17dia still overlaps 18 east to MainSt_S (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mjack_ras.pdf)
18: AR17 -> AR17_N
18: CR276 -> CR276/278
18: AR91_W -> AR91_N
18: *(63) -> US63(*)
18/135: CotSt -> CotWoodSt (https://www.google.com/maps/@35.8201789,-90.4347633,3a,16.5y,108.41h,90.94t/data=!3m6!1e1!3m4!1sAP_0R8BgEptr2dnNY3GStg!2e0!7i13312!8i6656)
18: new Monette bypass; AR139_N simply moves north (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mcrai_ras.pdf)
18: AR18B_W -> AR18B (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mmiss2_ras.pdf), move AR77_S south, delete AR18B_E
18/151bly/239: maybe add a point at ElmSt in Blytheville to make the alignment clear
18: the east end is way too far east; it needs to be moved here (https://www.google.com/maps/@35.9072817,-89.7704944,3a,50.7y,109.59h,81.11t/data=!3m6!1e1!3m4!1su0Rg-AeYsMW6UDim02pFVA!2e0!7i13312!8i6656) and renamed either End or CRE234 (the section map (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mmiss2_ras.pdf) matches the mileage to here)
18B: east end is now at AR77 (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mmiss2_ras.pdf)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 05, 2019, 09:46:33 pm
20: CR501 -> CR272? (the more major road)
20S: CR422 -> CR418? 422 is shown on maps as the levee road, which 20S doesn't quite reach
21/74: CR1300 -> CR1300/3260 (https://www.google.com/maps/@36.0122335,-93.4423132,3a,18y,292.97h,79.74t/data=!3m6!1e1!3m4!1s6ohPdPx1Pk0CSZgwmtkwVA!2e0!7i13312!8i6656)
21: FreAve -> FreSt (https://www.google.com/maps/@36.370509,-93.5672696,3a,15.5y,38.33h,86.77t/data=!3m6!1e1!3m4!1sW0164sPGO836uo8A2R3xxg!2e0!7i13312!8i6656)
21: move CR435 southwest to the intersection with the mainline of 435?
22: add a point near the west end at RogAve_W (unsigned 22Y) and a corresponding point on US 71B
22: FreeFryRd -> OldGreRd? (probably more important)
22: AR197_W -> AR197Sub, AR197_E -> AR197New
23: AR116_S -> AR116Boo, AR116_N -> AR116
23: OzaHigTr -> CheBend? the actual trail crosses to the north
23: AR127_S -> AR127Aur, AR127_N -> AR127Ala
23: WitSprSP -> WitSprSP_S, add WitSprSP_N just south of AR127Ala (this is unsigned 23W)
23: move SprSt south a bit
23: GraAve -> HilAve (based on the intersection where they split; no sign at 23)
23: CR222 -> CR222/266
24: CR25 -> CR25/56 (or move east to the other intersection, which doesn't have a yield where the two forks join?)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 06, 2019, 09:37:30 pm
25/US 65: AR285_S -> AR285Woo (which is missing a file)
25: AR107 -> AR107Qui, AR107_S -> AR107Heb_S, AR107_N -> AR107Heb_N
25: AR233_S -> AR233Bat_S, AR233_N -> AR233Bat_N, AR233 -> AR233Moo
25SHeb stays east of the park (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mcleb_ras.pdf), ending at or near http://www.openstreetmap.org/?lat=35.534330&lon=-92.014280
27: AR27B -> AR27B_S (it may not return at the north end but it comes damn close)
27: ChuRd -> FR2 (https://www.google.com/maps/@34.7908735,-93.4863248,3a,15y,314.88h,83.57t/data=!3m6!1e1!3m4!1sF5dNujwTn1aMRwy8xPaQRQ!2e0!7i13312!8i6656)?
27: FSR83 -> FR83
27: AR7 -> AR7_S (or is the signage gap long enough to split 27 in two?)
27: AR164_N -> AR164Sco
27: OldAR27 -> OldHwy27
27: SmyRd -> CR73 (https://www.google.com/maps/@35.6402828,-92.8788558,3a,15y,293.52h,87.83t/data=!3m6!1e1!3m4!1soScBnuMFoXojHStJJDUWIw!2e0!7i13312!8i6656)
27B: MainSt -> MainSt_N
28: US71Bus_N -> US71Bus_W, US71Bus_S -> US71Bus_E
28: OldCouRd -> RaiAve (https://www.google.com/maps/@34.997405,-93.2948521,3a,15y,252.02h,83.37t/data=!3m6!1e1!3m4!1sCLDhC15d-2GBHpiYNNiSmQ!2e0!7i13312!8i6656)
29: 23rdSt_E -> 23rdSt (https://www.google.com/maps/@33.6462368,-93.5871274,3a,15y,342.26h,97.66t/data=!3m6!1e1!3m4!1swxBLagjEm4GnAPDCChlKsQ!2e0!7i13312!8i6656)
29: ExpStaRd -> CR4 (https://www.google.com/maps/@33.686163,-93.5779677,3a,22.1y,330.06h,83.97t/data=!3m6!1e1!3m4!1sbkE0H-9qLKOpGwbJi52GjQ!2e0!7i13312!8i6656)?
Title: Re: usaar: Arkansas state highways
Post by: yakra on November 07, 2019, 12:04:02 pm
Quote from: http://travelmapping.net/devel/manual/wayptlabels.php
For the US Highways, local conventions of using suffixes instead of banners are ignored. Use banners here. NY US 20A is US20Alt here.
This (https://www.google.com/maps/@36.3777562,-93.5844523,3a,28.7y,100.08h,84.73t/data=!3m6!1e1!3m4!1ssdHTM0kl1tuWl6bBZ3jL4A!2e0!7i13312!8i6656) is US 62S, AKA US 62 Spur.
This (https://www.google.com/maps/@36.0566869,-90.5044213,3a,15y,242.76h,88.39t/data=!3m6!1e1!3m4!1svEm4qLxKn4LXzymq02TjsA!2e0!7i13312!8i6656) is US 49Y, not AKA anything bannered.
I would argue "AKA also a spur", still falling under "local conventions of using suffixes instead of banners".
Quote from: ROAD_INVENTORY_AHTD.shp.xml
<edomv>Y</edomv>
<edomvd>Y leg</edomvd>
<edomvds>Y leg of a route</edomvds>
Operationally, sounds pretty much like a a form of spur to me.
Child US routes have always become bannered routes; all we have for letter suffixes in the main usaus system are the big regional mainline splits, that in an alternate universe would be 3dUSes.
US6N US9W US11E US11W US19E US19W US25E US25W US31E US31W US45E US45W US49E US49W US70N US70S

7: AR128_S -> AR128_E, AR128_N -> AR128_W
7: Ar88_W -> AR88_S, AR88_E -> AR88_N?
This appears to be on "direction letter refers to the relative position of the intersection along the route whose file is being made (http://travelmapping.net/devel/manual/wayptlabels.php)" grounds.
But this falls under "The direction letter should match the signed direction the concurrent route is splitting toward."
Fair enough; I can see the argument for that.
FWIW, these are not concurrent routes, but separate segments of a route that got split.
Thus I'll see your "signed direction" and raise you a "Distinguish two different same-bannered same-numbered routes as needed with the 3-letter city abbreviations."
22: AR197_W -> AR197Sub, AR197_E -> AR197New
Like this. Also perfectly fine.
As the "no build" of the three options, I was fine with what mapcat already had.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 07, 2019, 12:26:12 pm
I would argue "AKA also a spur", still falling under "local conventions of using suffixes instead of banners".
Quote from: ROAD_INVENTORY_AHTD.shp.xml
<edomv>Y</edomv>
<edomvd>Y leg</edomvd>
<edomvds>Y leg of a route</edomvds>
Operationally, sounds pretty much like a a form of spur to me.
Operationally it's a form of spur, just as bypasses and business routes are a form of loop. But we don't lie and use LOOP banners, and we shouldn't lie and use a SPUR banner for a Y suffix.

7: AR128_S -> AR128_E, AR128_N -> AR128_W
7: Ar88_W -> AR88_S, AR88_E -> AR88_N?
This appears to be on "direction letter refers to the relative position of the intersection along the route whose file is being made (http://travelmapping.net/devel/manual/wayptlabels.php)" grounds.
But this falls under "The direction letter should match the signed direction the concurrent route is splitting toward."
Fair enough; I can see the argument for that.
FWIW, these are not concurrent routes, but separate segments of a route that got split.
Ah, I think we both got confused here. AR88 (http://travelmapping.net/hb/?r=ar.ar088hot) is a clear case of N/S, being an east-west signed loop off a north-south signed highway.

As for 128, I thought we were treating it as an overlap through Dalark. But I guess it's two separate routes due to length of possible overlap. So AR128Spa and AR128Joa?
Title: Re: usaar: Arkansas state highways
Post by: yakra on November 07, 2019, 01:44:43 pm
Ah, I think we both got confused here. AR88 (http://travelmapping.net/hb/?r=ar.ar088hot) is a clear case of N/S, being an east-west signed loop off a north-south signed highway.
Oh! Yes, agreed.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 07, 2019, 09:49:22 pm
31: AR321S -> AR321SOak
31: AR267_S -> AR267Bee, AR267_N -> AR267Sea
31: US67/167 -> US64/67?
32: CR180 -> CR143/180 (https://www.google.com/maps/@33.6674877,-94.3241343,3a,15.3y,68.62h,83.06t/data=!3m6!1e1!3m4!1s8sNkPkPyKzirfXWz6z4_MQ!2e0!7i13312!8i6656)
33/38: where does the GraMilRd name come from?
33: AR33B -> AR33B_S? (even though it's not signed back to 33 at the north end)
34: US67Spr -> US67Y
35 is mileposted from north to south; should it be reversed?
35: OldAR13 -> OldHwy13 (https://www.google.com/maps/@33.704655,-91.8075429,3a,21.7y,239.48h,85.1t/data=!3m6!1e1!3m4!1sQ5MHMMEj8LZM_R2zwiWx6Q!2e0!7i13312!8i6656)
35: CR56 -> RyeCutRd (https://www.google.com/maps/@33.8280859,-92.0780026,3a,21.1y,68.38h,83.71t/data=!3m6!1e1!3m4!1sGbBqew75yp3tJ7Pw9Xf26Q!2e0!7i13312!8i6656)?
35: move SouSt east to 35 (there's no one-way pair)
37: AR145_S -> AR145Lit, AR145_N -> AR145Bla
37: CR68 -> CR68/84 (https://www.google.com/maps/@35.7488322,-91.2452652,3a,46.8y,24.07h,82.4t/data=!3m6!1e1!3m4!1sGE3eJ1HATbARnQAaC5OG8w!2e0!7i13312!8i6656)
39 is mileposted from north to south; should it be reversed?
39: CR637 -> CR637/654
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 08, 2019, 02:26:16 pm
41 is mileposted from north to south; should it be reversed?
41bra: VestSt -> VestSt_S? (it returns at AR22_E)
43sil is mileposted from north to south; should it be reversed?
43sil's south end was truncated to 264 (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mbent_ras.pdf) upon completion of the railroad overpass (https://www.arkansashighways.com/minute_orders/2014/110514_minute%20orders.pdf) (it was still signed in 2018, with construction ongoing)
43sil/OK20: E0390 -> E390 (https://www.google.com/maps/@36.4526474,-94.6103037,3a,75y,223.47h,83.72t/data=!3m6!1e1!3m4!1sTNQhDx6iy80FMhj6cVNxTw!2e0!7i13312!8i6656)
44: MicRd -> LacCir? only OSM shows the former, but the latter is on Google and OSM
44: CR518 -> CR518/524
44mar is mileposted from east to west; should it be reversed?
44tic: JackBayRd -> JacBayRd? Google says it's Jacks Bay, as does OSM on the north-south portion
45: AR253_S -> AR253Mid, AR253_N -> AR253For
45fay: SasHillRd -> CR355 (https://www.google.com/maps/@36.1042543,-94.0738999,3a,23.8y,113.96h,81.14t/data=!3m6!1e1!3m4!1sfV_q--EAcJ5lH-DXTHsrfQ!2e0!7i13312!8i6656)?
45fay: TutRd -> CR70/79 (https://www.google.com/maps/@36.0999331,-93.9932459,3a,29.4y,75.29h,86.2t/data=!3m6!1e1!3m4!1sQRBg-OfVu6NQkJdTYoRlJw!2e0!7i13312!8i6656)?
45fay: CR8340 -> CR8225/8340 (https://www.google.com/maps/@36.2137245,-93.8591094,3a,29.1y,259.91h,83.02t/data=!3m6!1e1!3m4!1s6FgfB7KJKeBCo45OFzUHCg!2e0!7i13312!8i6656)
50cra: move SmoAllRd southwest
51: GurRd -> OldGurHwy_W (https://www.google.com/maps/@33.8883524,-93.2054082,3a,42.6y,157.79h,94.45t/data=!3m6!1e1!3m4!1sabQJmpiFaH5Vig0YgPNGow!2e0!7i3328!8i1664) (confirmed by sign on US 70 (https://www.google.com/maps/@33.8896945,-93.2632006,3a,15y,135.65h,85.12t/data=!3m6!1e1!3m4!1sW5mlIGScj114x707jfqgqA!2e0!7i13312!8i6656))
51: US67_S <-> US67_N
51: US67_ArkN -> US67/7?
51roc is the wrong direction; US270_W -> US270_N and US270_E -> US270_S
52: US82/425_E -> US82_E? I'm not sure that it makes sense to use the E direction if we list 425
53 is mileposted from north to south; should it be reversed?
53: CR81 -> CR36/81
54 is mileposted from east to west; should it be reversed?
56: WidRd -> CR36? I can't find signs for either, and neither OSM nor Google lists a name
56: SprHillRd -> CR25 (https://www.google.com/maps/@36.154035,-91.8411893,3a,16.5y,305.05h,78.82t/data=!3m6!1e1!3m4!1sG4OaYkv0YVdOhVlABDAYQw!2e0!7i13312!8i6656)?
57 is mileposted from north to south; should it be reversed?
58: add ToAR69_S (this connection is officially 58, with 58Y on what's signed as 58)
59 is mileposted from north to south; should it be reversed?
59: move RigDr south to the I-540 overpass?
59: US64/71Bus_W -> US64_W, US64/71Bus_E -> US64_E? (seems weird to use E/W with 71B)
59: DanRd -> OakRd (https://www.google.com/maps/@35.7070106,-94.4831807,3a,16.2y,201.11h,87.99t/data=!3m6!1e1!3m4!1s8gEBgnwHwf5O0VZ5ICUmmQ!2e0!7i13312!8i6656)
59: AR244_S -> AR244Eva, AR244_N -> AR244Wed
59: AR43 -> CheWhiDr
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 10, 2019, 11:32:28 am
60 is mileposted from east to west; should it be reversed?
60: AR9/10_S -> AR9_S, AR9/10_N -> AR9_N? I'm not sure N/S makes sense with 10
60: add DonAve in Conway (former 60S)
66: OakSt_N -> OakSt_E, WalSt_S -> WalSt_W?
69 (main segment only) is mileposted from north to south; should it be reversed?
69: AR69BNew -> AR69BNew_N?
69: AR394_E -> AR394_S, AR394_W -> AR394_N
69: AR233_S -> AR233Moo, AR233_N -> AR233Bat
69: add ToAR58_E (which is officially 58, with signed 58 being 58Y)
69tru: CR626 -> CR626/691
69Smel: MelArpt -> MelMunArpt (https://www.google.com/maps/@36.073171,-91.8313315,3a,26.7y,141.6h,83.27t/data=!3m6!1e1!3m4!1s__chIkgQSNtZev3nKGlZWw!2e0!7i13312!8i6656)
72: SchRd -> SchHouRd (https://www.google.com/maps/@36.4212674,-94.5659405,3a,15y,290.19h,87.79t/data=!3m6!1e1!3m4!1s40jOfn6ixyXkZ-DmQm9-cg!2e0!7i13312!8i6656)
73 is mileposted from north to south; should it be reversed?
74: GosTutRd -> CR79 (https://www.google.com/maps/@36.0332,-93.9735601,3a,21.6y,72.9h,81.62t/data=!3m6!1e1!3m4!1sJxbkNTUzY0jnI086dbD1gQ!2e0!7i13312!8i6656)?
74: are you sure about CR3180? I can't make out the number on GSV and Google and OSM both (from TIGER) label it 3655
74: presumably CR3850 and CR4500 are on street signs?
74mar, 74sno: ditto for these street names
74win/170: Based on reassurance, the end is a bit to the north at this sign (https://www.google.com/maps/@35.7813178,-94.2503818,3a,75y,240.97h,84.08t/data=!3m6!1e1!3m4!1sx3-orz8XduqP8k7vJGb86w!2e0!7i13312!8i6656) (pan left for the back of the first 170 reassurance).
74win: BreMtnRd -> CR39 (https://www.google.com/maps/@35.8233894,-94.1470612,3a,43.2y,184.97h,78.53t/data=!3m6!1e1!3m4!1sjeMtMqLQXD4CyryFge1qBQ!2e0!7i3328!8i1664)?
75: AR50 -> AR38/50
75/US 64: why is there a point at FroSt?
75: where does the name of LockDamRd come from?
75S: where does the name of IndParkRd come from?

A second piece of 76 (Waterloo) is missing:
US371 http://www.openstreetmap.org/?lat=33.552697&lon=-93.283110
CR162 http://www.openstreetmap.org/?lat=33.543800&lon=-93.269516
CR173 http://www.openstreetmap.org/?lat=33.544055&lon=-93.213952
US278 http://www.openstreetmap.org/?lat=33.556166&lon=-93.167238

77 is mileposted from north to south; should it be reversed?
77: US61 -> US61_N
77/18: CosDr -> CRW314 (https://www.google.com/maps/@35.8728754,-90.1775776,3a,75y,171.59h,67.98t/data=!3m6!1e1!3m4!1s5-h3Pf9hJzDyyQ81MvlQ4g!2e0!7i13312!8i6656)?
77: AR18_E has been moved south and the old location is torn up
78aub is mileposted from east to west; should it be reversed?
78aub: CR132 -> CR132/173?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 10, 2019, 07:14:12 pm
80: AR28_W -> AR28, since 28 isn't signed at the other intersection (US71)?
80: FS18 -> FR18? (I know the sign says FS 18, but we change e.g. MC 40 to CR 40)
81S may be one of the only unsigned sub-400 routes :(
83: JefAve_W -> JefSt_W (https://www.google.com/maps/@33.6366324,-91.7873255,3a,19.1y,240.22h,91.04t/data=!3m6!1e1!3m4!1sTA6uGk-rIBoEI9DCGhkSbw!2e0!7i13312!8i6656)
84: US70/27_E -> US70_E, US70/27_W -> US70_W?
84bog: CR14 -> End?
85 is mileposted from north to south; should it be reversed?
86: OldAR11 -> OldHwy11?
86hay: where does the HolRd name come from?
86hay: CroRd -> HalRd (https://www.google.com/maps/@34.8172661,-91.6748428,3a,48.7y,76.6h,79.33t/data=!3m6!1e1!3m4!1seyYIgXxQADxzavm5KyFhLg!2e0!7i3328!8i1664)
87 is mileposted from south to north (as it should be), and the main segment and 87mou should definitely be reversed
87: OldUS167_S -> OldHwy167_S?
87eli: US62 -> US62/412
87ken: CenSt -> CenAve (https://www.google.com/maps/@35.229159,-91.6768835,3a,39.3y,258.5h,77.83t/data=!3m6!1e1!3m4!1sRm620l7aMSDfpazdMNIv2g!2e0!7i3328!8i1664)
88hot: AR7_S -> AR7_W, AR7_N -> AR7_E
88lon: the west end is probably a bit farther west, where the pavement changes; this also matches 0.64 mi (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mgarl_ras.pdf) from the bridge
88alt: CorRd -> MorRd (https://www.google.com/maps/@34.2304044,-91.7449748,3a,18.8y,213h,87.92t/data=!3m6!1e1!3m4!1stHzmqSrNAO8Qn6rIkb6Zhg!2e0!7i13312!8i6656)?
88alt: LockDamRd -> HarLockDam (https://www.google.com/maps/@34.176984,-91.6709286,3a,75y,153.54h,82.25t/data=!3m6!1e1!3m4!1smjW6Rttpk-FmACLhlPEp2g!2e0!7i13312!8i6656)?
89may is mileposted from east to west; should it be reversed?
Title: Re: usaar: Arkansas state highways
Post by: mapcat on November 11, 2019, 09:14:39 pm
Continued thanks for the updates and suggestions. It will probably be December before I have time to properly address them. As for routes mileposted E->W or N->S, I intend to keep with the convention of W->E or S->N whenever I can. Feel free to continue to point these out (as well as any N->S that I actually did enter N->S, etc) in case others would like to weigh in.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 11, 2019, 10:16:21 pm
90 is mileposted from east to west; should it be reversed?
90 continues south from US 63 in Ravenden (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mlawr_ras.pdf), but it's unsigned except for a 'state maintenance begins' northbound at Main Street. So no change there.
90: US63 -> US62/63
90/115: Bro_W -> BroSt_W (https://www.google.com/maps/@36.260628,-90.9694461,3a,35.3y,192.72h,95.36t/data=!3m6!1e1!3m4!1sLBjTcj2Bepjl5d1Ei1p9Zw!2e0!7i13312!8i6656)
90/US 67: AirLn -> PocMunAir (https://www.google.com/maps/@36.2452935,-90.9580535,3a,15y,60.99h,86.57t/data=!3m6!1e1!3m4!1swjbzpuKyE01FKmiL5VFoag!2e0!7i13312!8i6656) (no street sign posted)
91 is mileposted from north to south; should it be reversed?
91: US49 -> US49/1?
91: US63/18 -> US63(49), since 18 begins along 91 - also this needs relocation
92 is missing a point at I-40
92: AR16_W <-> AR16_E
92: AR25 -> AR5/25
94 is mileposted from east to west; should it be reversed?
94 continues north from AR340
94: McNelRd -> McNRd?
95: CR389 -> Hwy389 (https://www.google.com/maps/@35.5256497,-92.6136006,3a,18.1y,207.71h,89.86t/data=!3m6!1e1!3m4!1sauvPtlmYThETrM1SUZoLFA!2e0!7i13312!8i6656) (no evidence that it's a county route rather than just a street named "Highway 389" for its former state designation)

The piece of 95 from Clinton east to Greers Ferry Lake (95Gre?) is missing:
US65/9 http://www.openstreetmap.org/?lat=35.561732&lon=-92.450638
CR23 http://www.openstreetmap.org/?lat=35.552349&lon=-92.426788
CR330E http://www.openstreetmap.org/?lat=35.529616&lon=-92.407207
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 14, 2019, 10:39:52 am
101 is mileposted from north to south; should it be reversed?
101: US62 -> US62/412
101fli: US62 -> US62/412
102: I-49 -> I-49/62?
103: Where does the CR1800 name come from? There's a street sign (https://www.google.com/maps/@36.0795147,-93.4005191,3a,44.2y,292.86h,86.66t/data=!3m6!1e1!3m4!1sq6kwUYIzFA_2N0gsVZLeeQ!2e0!7i3328!8i1664) that might say George Rd.
103cla: RivRd -> RivPoiRd (https://www.google.com/maps/@35.4353745,-93.4613042,3a,15y,283.3h,85.02t/data=!3m6!1e1!3m4!1s6VrJhgdIoRe_KTfFHrtgMA!2e0!7i13312!8i6656)
103cla: CR3350 -> CR3350/3361 (https://www.google.com/maps/@35.5169247,-93.5131284,3a,17.8y,2h,86.02t/data=!3m6!1e1!3m4!1siuFeVupbUHNzkSL1WchJTg!2e0!7i13312!8i6656)
105 is mileposted from north to south; should it be reversed?
107: are there any signs between PerBlvd and I-40?
107: ArnDr -> LitRockAFB (https://www.google.com/maps/@34.8980041,-92.1713545,3a,33.9y,163.45h,87.91t/data=!3m6!1e1!3m4!1sZ1MI653EugUUGZipHwuspg!2e0!7i16384!8i8192)?
107: add a point at CR89 (https://www.google.com/maps/@34.9399625,-92.1648643,3a,46.6y,41.52h,89.12t/data=!3m6!1e1!3m4!1s2QO6opT4pUFW5sNr5cUOvg!2e0!7i16384!8i8192)
107heb: AR25_N -> AR16/25
108: CR345 -> CR153/345 (https://www.google.com/maps/@33.7466914,-94.3299505,3a,15y,202.61h,77.15t/data=!3m6!1e1!3m4!1sSmNlvmhTpfWilPPk_LgK5w!2e0!7i13312!8i6656)
108S: AR41 -> AR32/41
109: OldAR109 -> OldSH109?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 17, 2019, 02:23:46 pm
110: AR25_N -> AR25B_N
111 is mileposted from north to south; should it be reversed?
112S: I-49 -> I-49/16?
113mor is signed north-south (https://www.google.com/maps/@35.2154802,-92.8321356,3a,15y,163.86h,85.94t/data=!3m6!1e1!3m4!1sO7ULOGGkBdjEkhlQ_IsJkw!2e0!7i13312!8i6656) and needs to be reversed; also US64_W -> US64_N
114 has a brief overlap with US 63
11B overlaps 114 at its north end (https://www.google.com/maps/@33.9425526,-91.8423313,3a,44.5y,304.86h,84.79t/data=!3m6!1e1!3m4!1s28mmsp2bfFw81auWTvryzw!2e0!7i13312!8i6656), so extend its file and 114: AR11B -> AR11B_S, also maybe 11: US425/114 -> US425/11B
115 is mileposted from north to south; should it be reversed?
115: CR134 -> CR134/214 (https://www.google.com/maps/@36.1553076,-91.240543,3a,38.1y,54.58h,86.54t/data=!3m6!1e1!3m4!1sDEPaaCn_-opwrjjwSNEwrA!2e0!7i13312!8i6656)
117: US63/412_W -> US412_W, US63/412_E -> US412_E? (since 63 is north-south)
118 is mileposted from north to south; should it be reversed?
118/US 64: OldUS64 -> OldHwy64
118/US 64: SprRd -> SprHillRd (https://www.google.com/maps/@35.271331,-90.3975307,3a,75y,326.71h,78.52t/data=!3m6!1e1!3m4!1spYiazdAoBW0vSmWrsGG2Ag!2e0!7i3328!8i1664)
118: CR1116 -> CRW1116? (as with other routes in the county)
118: CR495 -> CRS495? The nearby CR 495 is signed as CR S495
119: CRS447 -> CRS447_S (https://www.google.com/maps/@35.6251395,-90.0486391,3a,24.4y,315.73h,87.23t/data=!3m6!1e1!3m4!1suMl_ylxRAwdoNpT5XrJb7Q!2e0!7i13312!8i6656)
119mar is inventoried as two sections, both ending at US 61. The west piece (section 0) is signed north-south (from 14 to US 61), while I can't find any directional signs on the east piece (section 1). Suggest separating and reversing the east piece as 119But.
120: CRN759_N -> CRE474/N759?
121 is mileposted from north to south; should it be reversed?
121lon is signed north-south and should definitely be reversed
123 is mileposted from north to south; should it be reversed?
123: LurLp -> ToAR7_N
123: CR3551 -> CR3510 (https://www.google.com/maps/@36.0936471,-92.9716644,3a,18.1y,273.92h,90.72t/data=!3m6!1e1!3m4!1s8e09Kk7SAguSUAnOckOmJw!2e0!7i13312!8i6656)
124: OldAR124 -> OldHwy124 (https://www.google.com/maps/@35.3009082,-93.1017909,3a,15.1y,238.34h,86.16t/data=!3m6!1e1!3m4!1sy8d_hQ_1P1WvjyfWS_TBFA!2e0!7i16384!8i8192)
124: ForRd -> CR32 (https://www.google.com/maps/@35.4047948,-92.8171988,3a,17.6y,20.16h,85.51t/data=!3m6!1e1!3m4!1sTMjN23DuR_ehC5Fgrxi85Q!2e0!7i13312!8i6656)?
124: GraCutRd -> CR33 (https://www.google.com/maps/@35.3889889,-92.3493096,3a,35.5y,104.83h,83.44t/data=!3m6!1e1!3m4!1sWakh09tn9CYbdO03RtTIxQ!2e0!7i3328!8i1664)?
125: MarDr -> Hwy125Park (https://www.google.com/maps/@36.4896464,-92.778125,3a,43.1y,37.86h,79.31t/data=!3m6!1e1!3m4!1sMaKndNEDUmRbFpq8jlSGeA!2e0!7i13312!8i6656)
126: WhiBufTr -> CR641 (https://www.google.com/maps/@36.1674283,-92.4436055,3a,55.2y,204.34h,70.78t/data=!3m6!1e1!3m4!1srtokZBme9R62-D2DHEh7qA!2e0!7i3328!8i1664)?
126: CR57 -> CR57/59?
127 is signed north-south, so reverse the direction of the main segment and AR12_W -> AR12_N, AR12_E -> AR12_S
127los has no signed direction, but is inventoried from south to north, so reverse direction
127s: MarRd -> LosBriPark (https://www.google.com/maps/@36.4013598,-93.9042823,3a,44.5y,45.82h,80.51t/data=!3m6!1e1!3m4!1sh3b5UkI8UCMLTla5thnIhw!2e0!7i3328!8i1664)? (there is a street sign but it looks too long for Marina Road)
128fou is mileposted from east to west; should it be reversed?
128spa is mileposted from east to west; should it be reversed?
128spa: move CR263 east to CR205?
129 is signed to continue north with 275 to US 82
129law: CR185 -> CR55/185 (https://www.google.com/maps/@33.1962765,-92.48298,3a,53.4y,113.67h,78.01t/data=!3m6!1e1!3m4!1sQY9n-suGlezg1Gg68VPV9A!2e0!7i13312!8i6656)?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 17, 2019, 05:39:09 pm
130: AR1/1B -> AR1 (1B ends concurrent, so you can't turn onto 1B)
131edm: EubRd -> MudRd, move east
133: AR133T -> AR133T_S
133T: US82/133 -> AR133_N
combine 135 and 135par (https://www.google.com/maps/@36.0525846,-90.4404382,3a,19.1y,338.93h,88.5t/data=!3m6!1e1!3m4!1sEglnabf_6juPzNzr04qOWg!2e0!7i13312!8i6656)
135: OakSt -> OakSt_W
139: US62_E -> US62/1, US49 -> US49/1?
139mon: move AR18_W north to the new bypass
140: the piece east of US 61 doesn't make much sense as part of the same segment, and it's mileposted from south to north, with signs both north (south end) and east (north end); maybe split as 140Osc
141: remove UniSt (it's unsigned south of AR91)
141: CR652 -> CR652/654 (https://www.google.com/maps/@36.0975204,-90.6627638,3a,75y,158.07h,75.5t/data=!3m6!1e1!3m4!1sK4-RMeQUUvjieKhqNOjDow!2e0!7i13312!8i6656)
143: move PigCoopRd west to CR219_S?
143: CR219 -> CR219/226 (https://www.google.com/maps/@36.4817383,-93.6440924,3a,17.4y,165.3h,84.62t/data=!3m6!1e1!3m4!1sKoq1d0OZET_4xSaT3apECg!2e0!7i13312!8i6656)
144: US65/278_N -> US65_N? (since 278 is east-west)
144gil: FurRd -> FarRd (https://www.google.com/maps/@34.0832599,-91.4401351,3a,75y,121.92h,68.49t/data=!3m6!1e1!3m4!1sAAgPHCM1cislq25Q2j8uIw!2e0!7i3328!8i1664)
145 is mileposted from north to south; should it be reversed?
145: CR675 -> CR42/679??
145: CR635 -> CR626/635 (https://www.google.com/maps/@35.2245082,-91.1981116,3a,15.3y,304.4h,81.75t/data=!3m6!1e1!3m4!1sMZW1NliMsWBiuN1n4ge-BQ!2e0!7i13312!8i6656)
145bla: move CR33 northwest
145lit: CR56 -> CR36?
148 is mileposted from east to west; should it be reversed?
148cle: CRE328 -> CRE328/E330 (https://www.google.com/maps/@35.863247,-89.8098788,3a,17.8y,190.36h,83.08t/data=!3m6!1e1!3m4!1sP_zLg2jg8wIByvyNg0yhLw!2e0!7i13312!8i6656)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 17, 2019, 08:28:17 pm
151: TX/AR -> StaLineAve?
154 is mileposted from east to west; should it be reversed?
155 is mileposted from north to south; should it (all segments but 155dar) be reversed?
156fay: MorDr -> End (https://www.google.com/maps/@36.0414813,-94.1495672,3a,75y,65.12h,73.91t/data=!3m6!1e1!3m4!1sD9CfzxhtkgjcUgdwRQIQNg!2e0!7i13312!8i6656)
157: US67/167 -> US64/67?
157dia may be mileposted from north to south
157dia: AR18 -> AR17/18
158 is mileposted from east to west; should it (all segments but 158otw) be reversed?
158: CRN49 -> CRN49/W522 (https://www.google.com/maps/@35.7792303,-90.2588192,3a,15.5y,240.01h,86.59t/data=!3m6!1e1!3m4!1sOpYt-XIRErA81FbNWSN-IA!2e0!7i13312!8i6656)
158: US61_S -> US61_W, US61_N -> US61_E
158bay: MainSt_S -> CR623 (https://www.google.com/maps/@35.7416684,-90.56096,3a,75y,116.09h,86.9t/data=!3m6!1e1!3m4!1sGu7ZujZbgT7zC0gSRsgjuA!2e0!7i13312!8i6656)?
159: US65 -> US65/8?
159dum: OldUS65 -> MainSt_N?
159lak: JenRd -> JenCutRd (https://www.google.com/maps/@33.2568587,-91.2863541,3a,17.6y,36.19h,87.73t/data=!3m6!1e1!3m4!1sod-iZinDGN7Om2iRT-AaPQ!2e0!7i13312!8i6656)
159lak: US65/82_N -> US65_N, US65/82_S -> US65_S? (82 is east-west)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 19, 2019, 04:39:29 pm
161 is mileposted from north to south; should it be reversed?
161nor: move TraRd north to the intersection
162: the intersections near the east end appear to be a bit off; extend west and north to I-40/US 71 (https://www.google.com/maps/@35.4880416,-94.2262138,3a,75y,214.24h,77.4t/data=!3m6!1e1!3m4!1s2obQ8yKxjY8P2_5RgyvpUQ!2e0!7i13312!8i6656) (this isn't a remnant sign; it's still inventoried that way (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mcraw_ras.pdf); note that 11.023 is too high to be the US 64 intersection)
163: AR158_S -> AR158_W, AR158_N -> AR158_E
169: move ThuRd south
169: MillRd -> HanRd_N? (since sources disagree on the former name)
170 (main segment) is mileposted from east to west; should it be reversed?
170far: SunLn -> CR256 (https://www.google.com/maps/@36.0107883,-94.2517882,3a,49.1y,117.03h,83.77t/data=!3m6!1e1!3m4!1s_Iht2_8X3XnWQjj1shXibg!2e0!7i13312!8i6656)
171gif is signed north-south, but it's mileposted from north to south
175 is mileposted from north to south; should it be reversed?
177: JorRd -> CR64/70 (https://www.google.com/maps/@36.2335301,-92.1840064,3a,29.4y,154.17h,77.86t/data=!3m6!1e1!3m4!1syuvB-HYXIwqCYO3K4KnYVg!2e0!7i3328!8i1664)?
179 is mileposted from north to south; should it be reversed?
181 is mileposted from "north" (US61) to "south" (I-55); should it be reversed?
183: 4thSt -> MilParkRd?
185mar is mileposted from north to south; should it be reversed?
185mar: CR230 -> CR216/230
186: extend south to NorRd
187: BeaParkRd -> DamLakeCamp (https://www.google.com/maps/@36.4185,-93.8499065,3a,52.7y,24.41h,75.09t/data=!3m6!1e1!3m4!1sMsB_luY_gbdjgAF_yfiRcg!2e0!7i16384!8i8192)?
189 is mileposted from north to south; should it be reversed?
189: PraRd has a county road number on the sign, but I can't make it out
189ham: HamLim -> CR17 (https://www.google.com/maps/@33.2137018,-91.8092565,3a,43.3y,244.22h,78.89t/data=!3m6!1e1!3m4!1stOo8AsLDd7kZh72oQK5HuA!2e0!7i13312!8i6656)?
189ham: US82/425_W -> US425_S, US82/425_E -> US425_N?
190: End -> ComCorCen (https://www.google.com/maps/@34.2155872,-92.089018,3a,15y,4.72h,88.9t/data=!3m6!1e1!3m4!1sSF46s2ZdngZTq0pis1XdRQ!2e0!7i13312!8i6656)?
190: I-530(46) -> I-530/65?
190tul is mileposted from east to west; should it be reversed?
190pra is signed east-west and should definitely be reversed
195/US 371: CR261 (262 per Google?) is gated (https://www.google.com/maps/@33.8980281,-93.6064309,3a,24.3y,276.88h,82.93t/data=!3m6!1e1!3m4!1sSgnsKDF6A37Re3gsQm_hfw!2e0!7i13312!8i6656)
195: AR26 -> AR19/26
197boo and 197new are mileposted from north to south; should they be reversed?
198: CR623 -> CRS623 (https://www.google.com/maps/@35.6540192,-89.9496573,3a,55.5y,179.7h,74.05t/data=!3m6!1e1!3m4!1sJrvReqlMzpL_7_oEktWdxg!2e0!7i13312!8i6656)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 23, 2019, 10:44:23 pm
200: US371 -> US278/371
201: we need to determine whether it still overlaps US 62B through Mountain Home (https://www.google.com/maps/@36.3406492,-92.3850098,3a,31.3y,246.17h,90.75t/data=!3m6!1e1!3m4!1sMADv668y0wv0-Yl078rlLw!2e0!7i13312!8i6656) after the recent deletion inside the bypass.
201sal: ShiFryRd -> CR61 (https://www.google.com/maps/@36.2483211,-92.376561,3a,19.7y,296.1h,84.91t/data=!3m6!1e1!3m4!1sRotXC6-6ixtAzbiKt1Rryw!2e0!7i13312!8i6656)?
201sal: OldMilRd -> CR55 (https://www.google.com/maps/@36.2969715,-92.3899653,3a,17.3y,183.75h,80.02t/data=!3m6!1e1!3m4!1sRgRxirQgEJxsv8EacmNx9w!2e0!7i13312!8i6656)?
201sal: US62 -> US62/412
202yel: US62 -> US62/412
203 is signed north-south so should definitely be reversed
203: the AR274* labels seem wrong, but I don't know what would work better. AR274_Cam, AR274_W, AR274_E?
205 is signed north-south so should definitely be reversed (mainline and 205shu)
205for is mileposted from north to south; should it be reversed?
205for: End -> CR83 (https://www.google.com/maps/@33.7796871,-92.3610706,3a,33.5y,260.27h,80.25t/data=!3m6!1e1!3m4!1s6-y5QHDzT2e3K4PFDq-ARQ!2e0!7i13312!8i6656)?
208: BelCutOff -> BelCutRd (https://www.google.com/maps/@33.4905473,-91.3513487,3a,15y,272.07h,83.48t/data=!3m6!1e1!3m4!1sFNxCvkih8yyLWeDHM-pdHQ!2e0!7i13312!8i6656)
208hal: LevRd -> CR55?
209 (main segment) is mileposted from north to south; should it be reversed?

The west piece of 210 (210heb?) is missing:
End http://www.openstreetmap.org/?lat=35.531004&lon=-92.041542
CaseFordLn http://www.openstreetmap.org/?lat=35.517338&lon=-92.038887
AR25B http://www.openstreetmap.org/?lat=35.516543&lon=-92.028798

211: CR108 -> CR108/111 (https://www.google.com/maps/@36.4131811,-90.7304931,3a,15.1y,194.97h,86.29t/data=!3m6!1e1!3m4!1s5ir2h0x24hZ9hre6f9znqA!2e0!7i13312!8i6656)
215: CR5261 -> CR5440 and move a bit east
215mul: where does the ShoLakeRd name come from?
215ves: where does the NolRd name come from?
216: AR9 -> AR9/10
217: AR116_N -> AR116
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 24, 2019, 12:17:22 pm
220: CamRd -> CheHilTr (https://www.google.com/maps/@35.5847259,-94.444385,3a,49y,97.87h,84.54t/data=!3m6!1e1!3m4!1saffnjd-gnzZ63aWzBmnH5w!2e0!7i3328!8i1664)
223: CroRds -> CR17 or Cro?
223: move WildCheRd north to Wildberry Road? The former is a little dirt track (https://www.google.com/maps/@36.2640533,-92.0574812,3a,59.9y,246.63h,83.25t/data=!3m6!1e1!3m4!1spK_QJN-NYsEbfVmiQ6F9IA!2e0!7i3328!8i1664)
224 is mileposted from east to west; should it be reversed?
224: move CR615 southwest

the south part of 224 (224Ing?) is missing, including its junction with 14 just east of US67:
AR14 http://www.openstreetmap.org/?lat=35.564049&lon=-91.258299
CR7644 http://www.openstreetmap.org/?lat=35.493967&lon=-91.275176
US67 http://www.openstreetmap.org/?lat=35.489215&lon=-91.325885

225cro: CroRds -> Cro (https://www.google.com/maps/@35.4646601,-92.2164652,3a,15.1y,33.74h,88.89t/data=!3m6!1e1!3m4!1sUisQpIijVhl2MljBbC3tQw!2e0!7i13312!8i6656)
226: *OldUS49_N -> *OldUS49_S
there's a 226B (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mcrai_ras.pdf) at Cash, but it's unsigned, so no change
228min: End -> CR534 (https://www.google.com/maps/@35.9861932,-91.1061114,3a,35.3y,332.2h,71.21t/data=!3m6!1e1!3m4!1sAbPcAJ4aFIv60IKDYl5c4Q!2e0!7i13312!8i6656)?
229: US67 -> US67_S
229: SouSt -> SouSt_E (https://www.google.com/maps/@34.5622528,-92.6122656,3a,19.9y,223.78h,91.9t/data=!3m6!1e1!3m4!1s7H2qK7UhWgClLyRcB1RS2w!2e0!7i13312!8i6656) or I-30(116)
230cav: WilRd -> WildCatRd?
231 (main segment) is mileposted from east to west (and may be signed north-south to match the other segments; I can't make out what the signs say); should it be reversed?
233bat: US167/25 -> US167_S? 25 isn't signed at this intersection
233bat: move MilCreRd northeast (https://www.google.com/maps/@35.7863069,-91.6221658,3a,25.7y,52.76h,82.61t/data=!3m6!1e1!3m4!1s85iIT5Ng4jhzF24jtuS_yQ!2e0!7i16384!8i8192)
234: US71_S -> US59/71_S, US71_N -> US59/71_N
235 is mileposted from north to south; should it be reversed?
235: CR5010 -> CR4030/5010
237 is mileposted from north to south; should it be reversed?
237: CR152 -> CR151/152 (https://www.google.com/maps/@33.227648,-94.0047734,3a,35.7y,295.39h,78.42t/data=!3m6!1e1!3m4!1s506mGa92YEMgeM5NHnlGiw!2e0!7i13312!8i6656)
238: US70 -> US49/70
238: PleValRd_W -> PleValRd (the other one is a different road)
239: AR18/151 -> AR18_E? 151 isn't signed here
239osc: PauSt -> End (https://www.google.com/maps/@35.6939906,-89.9638705,3a,75y,108.62h,77.07t/data=!3m6!1e1!3m4!1sq4pLUSguGZtafcecMcO1ZQ!2e0!7i13312!8i6656)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 27, 2019, 02:22:53 pm
240 is mileposted from east to west; should it be reversed?
242 is mileposted from east to west; should it be reversed?
242: add a point at CR217 (https://www.google.com/maps/@34.574604,-90.6466399,3a,41.1y,358.89h,79.92t/data=!3m6!1e1!3m4!1s_0ovGkYSIMFdYptqHnogqw!2e0!7i13312!8i6656), which is unsigned 242S
242: AR185_N -> AR185Wes, AR185_S -> AR185Hel
243: move CR144 northeast to the other leg where the shield is (https://www.google.com/maps/@34.6654697,-90.9167971,3a,30y,312.45h,81.75t/data=!3m6!1e1!3m4!1siERSJ3cszVytkXMnGFy5wg!2e0!7i13312!8i6656)?
243: AR121_S <-> AR121_N
243: CR337 -> CR328/337 (https://www.google.com/maps/@34.7156099,-90.8197057,3a,15y,-32.14h,86.09t/data=!3m6!1e1!3m4!1sWo-aKgKN-clEKmwSNsa0Fw!2e0!7i13312!8i6656)
246: CR639 is gated (https://www.google.com/maps/@34.3683018,-94.1705465,3a,18.9y,187.73h,84.99t/data=!3m6!1e1!3m4!1sbOIHsnAXsKzFgUsATImXPw!2e0!7i13312!8i6656); move just east to CR402

A piece of 247 (247Mor?) is missing:
AR95 http://www.openstreetmap.org/?lat=35.187921&lon=-92.735431
AR132 http://www.openstreetmap.org/?lat=35.171544&lon=-92.735653
AR9B http://www.openstreetmap.org/?lat=35.163048&lon=-92.735939

247pon is mileposted from north to south; should it be reversed?
248 is mileposted from east to west; should it be reversed?
251: GlaRd -> OldBurrRd (https://www.google.com/maps/@36.4814699,-91.0504776,3a,43.6y,55.91h,81.6t/data=!3m6!1e1!3m4!1stL1gNq0PJiezOih-CLPT4g!2e0!7i3328!8i1664)?
252/US 71: why the point at BroSt?
252: OldAR10 -> OldHwy10?
253 is mileposted from north to south; should it be reversed?
253: AR252 -> AR45 (252 isn't signed here)
253lav: CR279 -> CroRd (https://www.google.com/maps/@35.3648384,-94.1547311,3a,28.1y,119.3h,91.25t/data=!3m6!1e1!3m4!1suoMjmqpL56rqLP4hQOhlnA!2e0!7i3328!8i1664)
254: where do the names for the streets come from?
255/US 71B: ZeroSt -> ZeroSt_E?? three junctions makes it hard
255: US64/71Bus_E -> US64/71Bus (no other 64/71B junction)
258 is mileposted from east to west; should it be reversed?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 27, 2019, 04:12:48 pm
260: CR668 -> 3ForRd?
260: CR311 -> CR646?
263: OldBreRd -> CR201?
263: SunFoxRd -> RossRd?
264 (west of US71B) is mileposted from east to west; should it be split and reversed?
264: HigAve -> HigAve_S
264: AirBlvd -> NWARegAir (https://www.google.com/maps/@36.2573626,-94.2920143,3a,26.1y,273.87h,91.04t/data=!3m6!1e1!3m4!1sCKTni4ccDk7omzEqlMqm3Q!2e0!7i16384!8i8192)?
264sil needs to be reversed
265: CR26 -> CR217 (https://www.google.com/maps/@35.8329021,-94.3109186,3a,45.2y,258.47h,79.64t/data=!3m6!1e1!3m4!1s1E2M991KMznP4c95iBFHqg!2e0!7i13312!8i6656)
265: JudCumRd -> CR200 (https://www.google.com/maps/@36.0281552,-94.1937309,3a,17.4y,236.46h,86.41t/data=!3m7!1e1!3m5!1s8TU7A-0H8R-l4rDU3W6lJQ!2e0!5s20160601T000000!7i13312!8i6656)?
267bee is signed north-south (https://www.google.com/maps/@35.0384031,-91.8339898,3a,75y,308.03h,94.53t/data=!3m6!1e1!3m4!1sgoYbar3URDlsNy0l8VvDBA!2e0!7i3328!8i1664) and should be reversed
269 is mileposted from north to south; should it be reversed?
272 is mileposted from east to west; should it be reversed?
272ric: AR59/270 -> US59/270
273iva needs a shaping point
274: CR75 -> CR79 (https://www.google.com/maps/@33.7010467,-92.3569165,3a,39.9y,119.74h,81.83t/data=!3m6!1e1!3m4!1snPoR1U-FyS9c9640UkQEUg!2e0!7i13312!8i6656)
274: AR203_W -> AR203_Cam, AR203_E -> AR203_N, AR203 -> AR203_S?
275: AR129 -> AR129_S (there's an overlap)
276 is mileposted from north to south; should it be reversed?

rename 276 to 276Stu; there's a much longer missing segment:
US165_W http://www.openstreetmap.org/?lat=34.298973&lon=-91.528124
AR276S http://www.openstreetmap.org/?lat=34.223442&lon=-91.520791
AR11 http://www.openstreetmap.org/?lat=34.221157&lon=-91.494157
DevRd http://www.openstreetmap.org/?lat=34.222306&lon=-91.422064
OWLn http://www.openstreetmap.org/?lat=34.237395&lon=-91.402774
US165/152 http://www.openstreetmap.org/?lat=34.238508&lon=-91.342875

and missing 276S:
AR276 http://www.openstreetmap.org/?lat=34.223442&lon=-91.520791
AR11 http://www.openstreetmap.org/?lat=34.208311&lon=-91.521107

277 (main segment) is mileposted from north to south; should it be reversed?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 27, 2019, 05:52:32 pm
280 is mileposted from north/east to south/west; should it be reversed?
281 is signed to use the cutoff north of 14
282/US 71: LakeFortRd -> LakeSmiRd (https://www.google.com/maps/@35.6487311,-94.1603677,3a,46.3y,303.76h,84.57t/data=!3m6!1e1!3m4!1sQIHFPH6JNemnezPV0WC_xA!2e0!7i13312!8i6656)
283fri is mileposted from north to south; should it be reversed?
284: US64Bus/1 -> AR1_N since 64B begins along 284
285: US65/124 -> US65_N (124 isn't signed here)

285 is missing a segment (285Woo?):
End http://www.openstreetmap.org/?lat=35.279863&lon=-92.285419
WooHolRd http://www.openstreetmap.org/?lat=35.279915&lon=-92.285950
BlaRd http://www.openstreetmap.org/?lat=35.258691&lon=-92.360430
US65 http://www.openstreetmap.org/?lat=35.257714&lon=-92.387182

286: US65/65Bus -> I-40; extend west overlapping US 65B to US65Bus/60 (signs (https://www.google.com/maps/@35.0648055,-92.4282587,3a,75y,1.16h,91.33t/data=!3m6!1e1!3m4!1sbvvwrH43aVQ1y7rFjU3ufA!2e0!7i16384!8i8192) are inconsistent (https://www.google.com/maps/@35.065666,-92.4288934,3a,53.1y,352.95h,83.44t/data=!3m6!1e1!3m4!1sAXF-7b4E4m7fhNvORSf-Tg!2e0!7i16384!8i8192))
289zio: BonRd -> BanRd (or CR61 (https://www.google.com/maps/@36.02188,-91.7847496,3a,20.4y,360.95h,85.18t/data=!3m6!1e1!3m4!1sA_2Wef19TOfcYaHi2kdIxg!2e0!7i13312!8i6656)?)
291: AR190_S -> AR190Pra, AR190_N -> AR190Tul
293 is mileposted from north to south; should it be reversed?
294: JPWriLp -> JPWLoopRd (https://www.google.com/maps/@34.852286,-92.0897903,3a,24.5y,294.69h,86.07t/data=!3m6!1e1!3m4!1sqvxfKN2HKM0JjEkWdcZzhw!2e0!7i13312!8i6656)
295com: CR 5451 -> CR5445/5451 (https://www.google.com/maps/@35.8548417,-93.7958856,3a,75y,66.88h,74.29t/data=!3m6!1e1!3m4!1sEgZVXJpAoWzv_o_n2zctEA!2e0!7i3328!8i1664)
Should 295com and 295cro be joined?
297 (main segment) is mileposted from north to south; should it be reversed?

A piece of 298 (298Sim?) is missing:
US270 http://www.openstreetmap.org/?lat=34.608486&lon=-93.674154
ForDr http://www.openstreetmap.org/?lat=34.638169&lon=-93.694303
AR88 http://www.openstreetmap.org/?lat=34.655892&lon=-93.690774

299 is signed south from both ends. Mileposts are from I-30 to 24, so it should be reversed (that would make it west to east).
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 27, 2019, 07:51:00 pm
300: RossHolRd -> Hwy300Spur (https://www.google.com/maps/@34.9375153,-92.5865641,3a,32.8y,56.51h,90.38t/data=!3m6!1e1!3m4!1sCZePLAGV83QalJKisct8nQ!2e0!7i16384!8i8192)
300: AR10 -> AR10_E
300lit is mileposted from east to west; should it be reversed?
I can't find any directional plates on 301, and it's mileposted from west to east, so it should be reversed
304: US67/90 -> US67 (90 isn't signed here)
304: AR90_E -> AR34/90
304N is east-west, so reverse it
304N: US67/90 -> US67 (90 isn't signed here)
304N: move PaceRd_E east to the main intersection
305aus: US67 -> US67/167
306bea -> 306bec
306gle -> 306gie
308: McDDr -> McDSt?
309: AR22/109 -> AR22? 109 isn't signed here except south with 309
309: AuxArcPark -> AuxArcParkRd (https://www.google.com/maps/@35.467395,-93.8235112,3a,21.4y,89.44h,84.1t/data=!3m6!1e1!3m4!1s5S18KCpZvYK4_rD4rlyPrg!2e0!7i13312!8i6656)
310 is mileposted from east to west; should it be reversed?
310eno ends a bit northwest of BayRd, maybe far enough for a separate End point
310eno: AR110 -> AR107
311 continues south from US 62 on Tyson Avenue, but that's unsigned, so no change (except adding a TysAve point on US 62?)
311: CR814 -> CR812/814 (https://www.google.com/maps/@36.3945998,-93.3692663,3a,21.1y,222.19h,83.22t/data=!3m6!1e1!3m4!1syD7mWHP9phN57V1GRQIRFQ!2e0!7i13312!8i6656)

312bly -> 312Num(ber Nine) and add a new 312bly:
AR239 http://www.openstreetmap.org/?lat=35.914348&lon=-89.891841
AR151 http://www.openstreetmap.org/?lat=35.914107&lon=-89.855950

314 is mileposted from east to west; should it be reversed?
316: A1/39 -> AR1/39
316: US49/1_S -> US49_N, US49/1_N -> US49_S (the two overlap in opposite directions so there's no way to be correct with both)
318 is mileposted from north to south and east to west; should it be reversed?
318: CR470 -> CR470/607
319con is signed north-south (https://www.google.com/maps/@35.1111649,-92.5171002,3a,47.4y,266.98h,83.12t/data=!3m6!1e1!3m4!1sNK1Zjxd906i1KLIvEm0S-w!2e0!7i16384!8i8192) so should be reversed
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 27, 2019, 10:29:58 pm
323des is mileposted from north to south; should it be reversed?
323des: where does the LetRd name come from?
323Y is unsigned. so no change
324 is mileposted from north to south (or east to west according to the signs at the north end of the main segment and 324lak); should it be reversed (all but 324rus)?
324rus: +X337905 -> MacAve and shift slightly
326 (main segment) is mileposted from north to south; should it be reversed?
327 is mileposted from north to south; should it be reversed?
327: CR8404 -> CR8403/8404 (https://www.google.com/maps/@35.9536406,-93.2416917,3a,27.7y,350.01h,86.65t/data=!3m6!1e1!3m4!1sCtdBQGKePn2dxLBrqciQAQ!2e0!7i13312!8i6656)
331: OldAR247 -> Hwy247 (https://www.google.com/maps/@35.2506502,-93.0488131,3a,38y,237.04h,85.12t/data=!3m6!1e1!3m4!1s53vsa5DTyiLGemrIf96nMQ!2e0!7i13312!8i6656) or RivRd?
333: BapRd -> BapDr (https://www.google.com/maps/@35.3242372,-93.2540502,3a,20.4y,207.2h,75.1t/data=!3m6!1e1!3m4!1s3XxkStYXww24dwEV_vsx4A!2e0!7i13312!8i6656)
333gil is mileposted from east to west (and has no directional plates); should it be reversed?
336 is mileposted from east to west; should it (main segment) be reversed?
336: AR9_S -> AR9_W (336 is signed east-west)
336: US65/9 -> US65? (9 isn't signed here)
336hig: AR16/92 -> AR16? (92 isn't signed here)
337: LoboRd -> LoboLan (https://www.google.com/maps/@35.456022,-91.924787,3a,38.3y,5.57h,88.43t/data=!3m6!1e1!3m4!1sAF1QipMu3ow9aNvmrB7QyxeVRGgnRUO-FGkeUWKB63V_!2e10!7i5376!8i2688)? (and shift east a bit)
337sug: SugLoafPk -> SugLoafRA (https://www.google.com/maps/@35.541679,-92.2452913,3a,75y,307.42h,84.27t/data=!3m6!1e1!3m4!1smkLCAo0T6ydUcC6I7cxuVQ!2e0!7i3328!8i1664)?
339 is mileposted from north to south; should it be reversed?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 28, 2019, 10:19:47 am
341: CR52 -> CR52/53 (https://www.google.com/maps/@36.3013872,-92.2903175,3a,41.4y,80.68h,84.21t/data=!3m6!1e1!3m4!1sc1LX9xRqQnk-O2YdpMAftQ!2e0!7i13312!8i6656)
342: AR5/341 -> AR5? (341 isn't signed here)
342har is mileposted from east to west; should it be reversed?
343slo: where does the SarKonRd name come from?
345: KirSt -> HouAve (that's the one that continues to 345)
346 has no directional signs and is mileposted from south to north, so it should be reversed
349cac is signed north-south so should definitely be reversed
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on November 30, 2019, 10:37:39 pm
350 is signed east-west everywhere but at US 64, and is mileposted from west to east, so should definitely be reversed
351: CR754 -> CR754/766 (https://www.google.com/maps/@35.9151402,-90.645944,3a,47.2y,298.93h,82.05t/data=!3m6!1e1!3m4!1sdNiyqbHWGPdpmiRz5vCiVg!2e0!7i13312!8i6656)
352: AR164_N -> AR164_E, AR164_S -> AR164_W (signed east-west at both ends)
352: CR2201 -> CR2171/2201 (https://www.google.com/maps/@35.4893566,-93.5995892,3a,16.9y,320.55h,82.18t/data=!3m6!1e1!3m4!1sTY7u83kVQs9GSS0Ar2paVg!2e0!7i13312!8i6656)
353: CR2 -> CR2/15 (https://www.google.com/maps/@33.6578014,-93.6810926,3a,24.3y,9.55h,82.04t/data=!3m6!1e1!3m4!1sfVteOh-KcDl8KKZ9GcxTYA!2e0!7i13312!8i6656)
355 is mileposted from north to south (and is sometimes (https://www.google.com/maps/@33.5740132,-93.6139994,3a,75y,311.08h,86.12t/data=!3m6!1e1!3m4!1sKP76cZGgF8hSWUCF-XKIVA!2e0!7i13312!8i6656) signed east-west); should it be reversed?
355: CR2 -> CR128 (https://www.google.com/maps/@33.4434239,-93.3536769,3a,15.1y,79.58h,87.78t/data=!3m6!1e1!3m4!1sp5x6AJX260mJcTrl147fUw!2e0!7i13312!8i6656)
357: CR535 -> CR535/542 (https://www.google.com/maps/@35.1024482,-90.4455442,3a,75y,62.46h,69.82t/data=!3m6!1e1!3m4!1s2UVP_Py3OCDZGmCPc-juFg!2e0!7i3328!8i1664)
358 is mileposted from east to west; should it be reversed?
358: AR141/168 -> AR141? 168 isn't signed here
359: US64_E -> US64_S, US64_W -> US64_N
Title: Re: usaar: Arkansas state highways
Post by: vespertine on December 02, 2019, 04:26:34 pm
81S may be one of the only unsigned sub-400 routes :(

It is not unsigned anymore. Per field check November 2019, short little AR81S is now signed. Mappit!

Also, re: AR36 - should be split in two. ADOT maps (http://arkansashighways.com/maps/cities/searcy_city.pdf) and GMSV (https://goo.gl/maps/xLvmqR173hA2dQas6) show AR36 going to US64/67/167 (near unsigned 367Y), so a concurrency can't be implied on AR367.

v.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on December 05, 2019, 09:43:07 am
Also, re: AR36 - should be split in two. ADOT maps (http://arkansashighways.com/maps/cities/searcy_city.pdf) and GMSV (https://goo.gl/maps/xLvmqR173hA2dQas6) show AR36 going to US64/67/167 (near unsigned 367Y), so a concurrency can't be implied on AR367.
However, signage at the other end (https://www.google.com/maps/@35.2333131,-91.6981538,3a,30y,152.81h,90.96t/data=!3m6!1e1!3m4!1svxAP6Kw247nKmpR7tvN5WA!2e0!7i13312!8i6656) shows an overlap. Maybe treat the stub west of 367 as a separate segment?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on December 05, 2019, 10:09:17 am
364: CR225 -> CR225/251 (https://www.google.com/maps/@35.3280663,-90.8264342,3a,15y,112.06h,82.5t/data=!3m6!1e1!3m4!1siSeAKh6gyLlmWrm4fW6Twg!2e0!7i13312!8i6656)
364: AR1/1B -> AR1 (1B begins along 364)
365 is mileposted from north to south; should it be reversed?
365: WiseRd -> DexEnt (https://www.google.com/maps/@34.3158858,-92.1082684,3a,44.5y,350.96h,85.87t/data=!3m6!1e1!3m4!1soLLR60aq48irg733iyPOPA!2e0!7i13312!8i6656)?
365: AR100_S -> AR100Nor, AR100_N -> AR100Mau
89/365 has a single isolated ramp to I-40 west
366abe: OakLn -> End (https://www.google.com/maps/@34.604335,-91.3329832,3a,75y,56.53h,71.54t/data=!3m6!1e1!3m4!1sh_doLnFJsWwew9QTlM9jjQ!2e0!7i13312!8i6656)
367: AR13_S -> AR13Sea, AR13_N -> AR13Jud
367: US67/67Bus -> US67(42) since US 67B begins along 367
367: AR36_E may need recentering; 367 southbound uses two sides of the triangle
367: AR157_S -> AR157Jud, AR157_N -> AR157Dia
367: CR4 -> CR4/349 (https://www.google.com/maps/@35.5241361,-91.3812698,3a,35.8y,45.25h,75.37t/data=!3m6!1e1!3m4!1sYEuU6MSLYslA4YeKS18rHw!2e0!7i13312!8i6656)
367: CR55 -> CR55/208 (https://www.google.com/maps/@35.7119688,-91.2109234,3a,31.8y,187.5h,84.46t/data=!3m6!1e1!3m4!1sBGG81Dc7xTXCFD15bSa0eA!2e0!7i13312!8i6656)
367: CR70 -> CR70/76 (https://www.google.com/maps/@35.8259489,-91.1317759,3a,23.6y,64.91h,82.44t/data=!3m6!1e1!3m4!1sEwVS7iNfVOE5H_mLYLLd9A!2e0!7i13312!8i6656)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on December 06, 2019, 02:38:28 pm
368: MainSt -> CR27 (https://www.google.com/maps/@33.7520623,-93.1055859,3a,75y,188.54h,72.84t/data=!3m6!1e1!3m4!1sA0Ny-y95NDz1sxPUJ6nFEQ!2e0!7i3328!8i1664)?
369: AlbPikeRA -> End (https://www.google.com/maps/@34.3734891,-93.8765648,3a,75y,332.04h,78.05t/data=!3m6!1e1!3m4!1sbHzlPHH58TY3dN7HLbRYjA!2e0!7i13312!8i6656)? there's no intersection right there
373: move BayLn northeast
374: AR74/123 -> AR123? 74 isn't signed here
375 (main segment) is mileposted from north to south; should it be reversed?
375: CR81 -> CR64/81 (https://www.google.com/maps/@34.4509043,-94.1226946,3a,75y,209.9h,79.79t/data=!3m6!1e1!3m4!1sg62vnox0q-QfBXloPGbawA!2e0!7i3328!8i1664)? this point is also misplaced
376 around Camden is mileposted in the reverse direction of the old 7 portion, but several signs (https://www.google.com/maps/@33.5357352,-92.8272156,3a,75y,125.24h,79.82t/data=!3m6!1e1!3m4!1sEoVkoultFarsoYoNEgoRRg!2e0!7i13312!8i6656) explicitly overlap 376 *east-west* with 7. At the south end it's signed north, and I can't make out the plates where it crosses 7. Probably no change.
379ode and 379pik are mileposted from north to south; should they be reversed?
379pik: AR19/26 -> AR26? 19 isn't signed here
380 (main segment) is mileposted from east to west; should it be reversed?
380ogd: End -> CR230 (https://www.google.com/maps/@33.5811486,-94.0345629,3a,44.2y,49.65h,79.23t/data=!3m6!1e1!3m4!1s5Yw3ap0yw4Ekl88b3nZqCQ!2e0!7i3328!8i1664)
381 is mileposted from north to south; should it be reversed?
382 is mileposted from east to west; should it be reversed?
382: JimDriPkwy -> JimDriPkwy_W; also needs to be moved east (along with End)
382: AR9 -> AR5/9 (also signed as 14)
384bal is signed east-west (https://www.google.com/maps/@35.5606608,-91.0653852,3a,30y,213.1h,82.79t/data=!3m6!1e1!3m4!1s9NBjP2rBWcXyG-eUKPt3Zw!2e0!7i13312!8i6656) and should be reversed
385jud: US67/167 -> US64/67?
386: ArkDeptCorr -> WriUnit (https://www.google.com/maps/@34.6015878,-92.2166372,3a,44.5y,47.84h,86.65t/data=!3m6!1e1!3m4!1sNv-xWtUBAgMshsvIk2gXwA!2e0!7i13312!8i6656) (or ArkDepCor?)
386tol: maintenance continues northwest to the sharp curve per mileage (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mlono_ras.pdf)
387cam is mileposted from north to south; should it be reversed?
387cam: End -> CR47 (https://www.google.com/maps/@33.5089872,-92.8525366,3a,75y,216.46h,79t,0.58r/data=!3m6!1e1!3m4!1sJ5ZoNbOAzxXn6qfOJak23w!2e0!7i13312!8i6656)?
388: ArkDeptCorr -> CumUnit (https://www.google.com/maps/@34.0391939,-91.6162075,3a,24.1y,354.26h,91.28t/data=!3m6!1e1!3m4!1sHg-3iOV14encm0m0HUl2Tg!2e0!7i13312!8i6656) (or ArkDepCor?)
390 is mileposted from east to west; should it be reversed?
390: where does the CorEngRd name come from? rename LowLakeArea (https://www.google.com/maps/@34.179981,-93.0977646,3a,45.4y,199.87h,82.04t/data=!3m6!1e1!3m4!1sl36ZubLARL8iqRQdjW1Dtg!2e0!7i3328!8i1664)?
393ple: CotRd -> End?

A second piece of 394 (394Rut?) is missing:
AR69_E http://www.openstreetmap.org/?lat=35.722173&lon=-91.491033
RusFerRd http://www.openstreetmap.org/?lat=35.725062&lon=-91.545784
MouRidRd http://www.openstreetmap.org/?lat=35.751702&lon=-91.590765
AR69_W http://www.openstreetmap.org/?lat=35.769219&lon=-91.598974

398rat is mileposted from north to south (and has no directional plates); should it be reversed?
399 is mileposted from north to south; should it be reversed?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on December 06, 2019, 03:01:45 pm
463 is mileposted from north to south; should it be reversed?
463: AR214_S -> AR214McC, AR214_N -> AR214Tru
530 is mileposted from north to south; should it be reversed?
530 is built to have a limited number of intersections, so perhaps we should add points at all other intersections. That means adding:
AutHilRd http://www.openstreetmap.org/?lat=33.977349&lon=-91.918992
OldSCRd_S http://www.openstreetmap.org/?lat=34.059664&lon=-91.958098
530wil: ditto for BarRd http://www.openstreetmap.org/?lat=33.671354&lon=-91.886682
549: AR72_S -> 284, AR72_N -> 287
612: AR112 -> 9
818 has no directional plates, so reverse to go from south to north?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on December 06, 2019, 04:15:32 pm
935-1 is signed (https://www.google.com/maps/@34.245898,-92.017466,3a,15y,246.74h,89.32t/data=!3m6!1e1!3m4!1spV9IrXG_dCVUgTo_X8NqMw!2e0!7i16384!8i8192) and needs a file and a point on us079buspin:
US79B http://www.openstreetmap.org/?lat=34.245870&lon=-92.017542
End http://www.openstreetmap.org/?lat=34.245830&lon=-92.015927

943-1 is unsigned except for state maintenance begins/ends (https://www.google.com/maps/@34.7699009,-91.9093984,3a,58.5y,280.32h,81.4t/data=!3m6!1e1!3m4!1sr9zFI3-703BpxQwxBABJdg!2e0!7i13312!8i6656) :( but US 70 and 31 should probably get a point at FishHatRd http://www.openstreetmap.org/?lat=34.770024&lon=-91.915076

946-1: CR4 -> CR4_S (https://www.google.com/maps/@33.0895491,-93.8667056,3a,39.6y,175h,78.5t/data=!3m6!1e1!3m4!1sTFrgtI6h9YTke4fF17Rjsw!2e0!7i13312!8i6656)

there may be a 947-1 at Luxora but I don't know where or if it's signed

959-1 is unsigned :( but 11 should probably get a point at LakeDesArc http://www.openstreetmap.org/?lat=35.018250&lon=-91.523248

980cli: AR16 -> AR9/16
https://www.arkansashighways.com/maps/Counties/County%20PDFs/StFrancisCounty.pdf shows a 980 at Colt, but it's unsigned :( Maybe add an Arpt point on 1?
980cor: US67 -> US62/67
980fli: Arpt -> CR7023
There's supposed to be a 980 in Hampton, but it's not on current maps, so it was either never built or no longer exists.
980har: US65 -> US62/65
980heb: ChanDr -> ChaDr
980lak: US65 -> US65/278? (but 278 isn't signed here, though there's no reassurance in either direction)
980men: delete Arpt per https://www.arkansashighways.com/maps/Counties/County%20PDFs/PolkCounty.pdf
980mon: Arpt -> End (or realign? (https://www.google.com/maps/@33.6364726,-91.7578997,3a,42.6y,29.81h,84.48t/data=!3m6!1e1!3m4!1sV2pwxV__WZ7_RbI52LduAw!2e0!7i13312!8i6656))
980rec: CR428 -> CR428_W (https://www.google.com/maps/@36.2444376,-90.3132273,3a,15y,269.23h,85.41t/data=!3m6!1e1!3m4!1sv8KwScLclS2ZgtcN-O4D8A!2e0!7i13312!8i6656)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on December 06, 2019, 06:23:07 pm
US 49: AR39 -> AR39_N? or keep as AR39 since AR39/241 is the farthest north?
US 49: AR17 -> AR17_N
US 49: CR202 -> CR203 (https://www.google.com/maps/@35.7779526,-90.8155656,3a,43.7y,293.62h,84.71t/data=!3m6!1e1!3m4!1sSM92THnfBOI10wa4anYgvw!2e0!7i13312!8i6656)? I'm not sure if the TO is supposed to imply it's TO 203, or if a 202 shield fell off below - but if the former, why is there no 202 shield?
US 49: US62 -> US62/1?

US 59/71: DeqLakeRd -> DQLakeRd (https://www.google.com/maps/@34.0999818,-94.3227471,3a,15y,226.41h,90.91t/data=!3m6!1e1!3m4!1sz7GryFZ5Qpr83VLKAMsqrA!2e0!7i13312!8i6656)?
US 59/71: HomAve -> HorAve (https://www.google.com/maps/@34.173381,-94.3149073,3a,50.5y,77.76h,84.44t/data=!3m6!1e1!3m4!1s7cobKNMiEPHNfjxph1utog!2e0!7i13312!8i6656)
US 59/71: FraRd -> CR3 (https://www.google.com/maps/@34.2381895,-94.333336,3a,69.8y,76.08h,71.48t/data=!3m6!1e1!3m4!1skIpcecn4No98hynbR1pOcw!2e0!7i13312!8i6656)?

US 61: AR119_W -> AR119_N, AR119_E -> AR119_S (no directional plates on the latter, but for consistency)
US 61: AR140_S -> AR140_W, AR140_N -> AR140_S
Title: Re: usaar: Arkansas state highways
Post by: yakra on December 12, 2019, 11:21:57 am
AR4: AR4SSpr -> AR4S
AR7: AR7SSpr -> AR7S

AR7SMar:
Reverse points? The usual convention for spur child routes is to order the waypoints beginning at the parent route; I remember this from the CHM days. Though checking the manual now, the only mention I see is "Some spurs might not follow this as they begin at a parent highway and end away from it (e.g., NC I-795: north (I-95) to south)." (http://travelmapping.net/devel/manual/hwydata.php)

US65 and AR9 have a point labeled AR95, but there's no corresponding segment of AR95 in the HB.
It's still signed as of Dec 2018 (https://www.google.com/maps/@35.5616657,-92.4504075,3a,15y,109.04h,87.22t/data=!3m10!1e1!3m8!1sWpzPn9lwHdrDvchRHUp1FQ!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DWpzPn9lwHdrDvchRHUp1FQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D65.043564%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656!9m2!1b1!2i40), and included in the Clinton city (http://www.arkansashighways.com/maps/cities/clinton_city.pdf) and Van Buren county (http://www.arkansashighways.com/maps/Counties/County%20PDFs/VanBurenCounty.pdf) maps.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on December 30, 2019, 12:34:37 pm
I was in Jonesboro earlier this month and noticed US 63 is now signed with US 49 from I-555 to at least AR 226. I did not go any further south on 49/63 so don’t know if 63 is fully signed all the way to I-40 now. This realignment was approved by AASHTO earlier this year.
In addition to changes to the US 63 file, this also means the following files need US49* -> US49/63* (unless we want to wait until we're sure it's well signed and not just signed like a typical Arkansas overlap):
US64 14 17 38 42 158Otw 214 226 269 284 306 364 956-1
Title: Re: usaar: Arkansas state highways
Post by: mapcat on December 30, 2019, 04:06:04 pm
Highways 1-100 are done: https://github.com/TravelMapping/HighwayData/pull/3473 (https://github.com/TravelMapping/HighwayData/pull/3473)

5Lit: I-30SerRd_E -> I-30_E (just as the west split is I-30/35, not just AR35)

AR 5 departs there from the service road between interchanges, not from I-30 itself. I changed the west split to I-30.

Quote
5Lit: add SprRd and BryPkwy (access to I-30; the latter is what OSM and the Goog call Echo Lake Blvd)

Neither of those intersect I-30 (just the service road) and neither intersection with AR 5 has a "To I-30" marker, so I left those points out.

7: AR128_S -> AR128_E, AR128_N -> AR128_W

To disambiguate intersections with different segments of the same route, I went with the root names. 128spa and 128joa in this case.
 
Quote
5 has DeSotoBlvd and 7 has DesBlvd for the same road. I don't know which is correct, since the name isn't signed in public areas.

The Hot Springs Village Comprehensive Master Plan (http://explorethevillage.com/vision/comprehensive-master-plan/final-documents/) uniformly refers to DeSoto Blvd so I settled on DeSotoBlvd for both routes.

11: StiLetRd -> LetRd (https://www.google.com/maps/@34.9202229,-91.5641934,3a,15y,66.38h,89.24t/data=!3m6!1e1!3m4!1spfZi90uLgb6Ll-torxc7qA!2e0!7i13312!8i6656)?

I went with RoyNewRd (opposite road at intersection (https://www.google.com/maps/@34.9200728,-91.5642555,3a,15y,321.16h,90.65t/data=!3m6!1e1!3m4!1sCtmudkMJYlzaitUW4BUwLQ!2e0!7i13312!8i6656)) since the name on that sign matched OSM & Google

Quote
How sure are we that 12 doesn't use 71B to 94 in Rogers? This sign (https://www.google.com/maps/@36.3551327,-94.122447,3a,15y,292.49h,90.03t/data=!3m6!1e1!3m4!1sCQRa-mFW3DPKI9gmD5s_5w!2e0!7i13312!8i6656) points westbound traffic left on 94, and there are some to 12 signs at the 71B/94 intersection. On the other hand, eastbound signs exist on I-49 north showing the routing we have. Some discussion on AARoads. (https://www.aaroads.com/forum/index.php?topic=3390.msg117481#msg117481)

I left it as-is because historical GMSV shows the routing used to follow US71B, but was changed within the past decade (probably 2011, given the date of the AA roads discussion). The "To AR 12 East" sign (https://www.google.com/maps/@36.3334634,-94.1263143,3a,51.9y,73.73h,88.52t/data=!3m7!1e1!3m5!1sWdJPZeu9CHJ9KOlmkpplBQ!2e0!6s%2F%2Fgeo0.ggpht.com%2Fcbk%3Fpanoid%3DWdJPZeu9CHJ9KOlmkpplBQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D286.9288%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192) on 71B at 8th indicates that that is the desired route for traffic now. There's another one heading west at the same location ("To AR 12 West").

Quote
14: LinHillRd -> LinHillLn? OSM shows both names and the Goog shows the latter
14/140: DickKingRd is closed (https://www.google.com/maps/@35.6142156,-90.3907633,3a,38.3y,276.83h,90.8t/data=!3m6!1e1!3m4!1sYEP7Yq5RPg0gqFLAe3cTHw!2e0!7i13312!8i6656)

For the street names that don't match up with OSM, I was using the Arkansas Spatial Data Infrastructure Map Viewer (https://www.arcgis.com/apps/webappviewer/index.html?id=8bd86088bb7b4068a69db5f6567a8d0b). The names were confirmed by the road centerlines and address points layers.

16: OldAR27 -> OldHwy27?

Since it was once AR 27, I left it as-is. I did the same with other former AR and US routes, even when the street signs just say "Hwy".

Quote
17: 3ForRd -> CR43 (https://www.google.com/maps/@35.0984059,-91.2338289,3a,36.5y,19.14h,81.63t/data=!3m6!1e1!3m4!1sbItnrJOLLXrymEdwGYSNFg!2e0!7i3328!8i1664)?

The sign pictured appears to have 3 digits, not 2, so I went with CR668 which is what it's called in the ASDI.

Quote
17: US64Bus -> US64Bus_E (https://www.google.com/maps/@35.2703769,-91.2352796,3a,15.9y,138.1h,85.06t/data=!3m6!1e1!3m4!1swnhA9r6d0wBey-d-y5x3Qw!2e0!7i13312!8i6656) (and US64BusMcC should extend back to US 64)

Eric removed the western segment a couple of years ago, and it's signed "To US 64" (https://www.google.com/maps/@35.258432,-91.234782,3a,75y,22.68h,88t/data=!3m6!1e1!3m4!1sxgQA9UtHXRDseH-2U8HTBg!2e0!7i13312!8i6656) now.

23: OzaHigTr -> CheBend? the actual trail crosses to the north

The waypoint is at the parking lot for the trail, which is signed. The actual trail crossing is unmarked.

27: AR27B -> AR27B_S (it may not return at the north end but it comes damn close)

It's not signed at the north end, so it's not necessary to distinguish the south end from the north end.

Quote
29: 23rdSt_E -> 23rdSt (https://www.google.com/maps/@33.6462368,-93.5871274,3a,15y,342.26h,97.66t/data=!3m6!1e1!3m4!1swxBLagjEm4GnAPDCChlKsQ!2e0!7i13312!8i6656)

Even though there's no corresponding point at the other junction, streets named 23rd St do head both east and west from AR 29.

33/38: where does the GraMilRd name come from?

ASDI (Grady Miller Rd). The blurry sign on GMSV resembles Grady Miller more than it does Jims Lake or Sand Hill, even though the correct name for the road is probably Jims Lake Rd.

Quote
33: AR33B -> AR33B_S? (even though it's not signed back to 33 at the north end)

See notes for 27 above.

Quote
4: US67Spr -> US67Y

It's US67Spr in the HB.

Quote
35 is mileposted from north to south; should it be reversed?

For all of these, I disregarded the mileposts (they often aren't posted on the routes so they have little benefit to drivers) and stayed with S -> N for N/S routes and W -> E for E/W routes.

Quote
35: OldAR13 -> OldHwy13 (https://www.google.com/maps/@33.704655,-91.8075429,3a,21.7y,239.48h,85.1t/data=!3m6!1e1!3m4!1sQ5MHMMEj8LZM_R2zwiWx6Q!2e0!7i13312!8i6656)

US 425 was once AR 13.

Quote
35: CR56 -> RyeCutRd (https://www.google.com/maps/@33.8280859,-92.0780026,3a,21.1y,68.38h,83.71t/data=!3m6!1e1!3m4!1sGbBqew75yp3tJ7Pw9Xf26Q!2e0!7i13312!8i6656)?

The sign blade includes "CCR#56" after the name.

Also, re: AR36 - should be split in two. ADOT maps (http://arkansashighways.com/maps/cities/searcy_city.pdf) and GMSV (https://goo.gl/maps/xLvmqR173hA2dQas6) show AR36 going to US64/67/167 (near unsigned 367Y), so a concurrency can't be implied on AR367.
However, signage at the other end (https://www.google.com/maps/@35.2333131,-91.6981538,3a,30y,152.81h,90.96t/data=!3m6!1e1!3m4!1svxAP6Kw247nKmpR7tvN5WA!2e0!7i13312!8i6656) shows an overlap. Maybe treat the stub west of 367 as a separate segment?

That's how I handled it (AR 36 (Searcy).

43sil/OK20: E0390 -> E390 (https://www.google.com/maps/@36.4526474,-94.6103037,3a,75y,223.47h,83.72t/data=!3m6!1e1!3m4!1sTNQhDx6iy80FMhj6cVNxTw!2e0!7i13312!8i6656)

I changed the name in the AR 43 file and will leave OK 20 to @yakra.

Quote
51: US67_S <-> US67_N
51: US67_ArkN -> US67/7?

Changed all of them to US67_A, US67_B, US67/7, and US67_C.

Quote
53: CR81 -> CR36/81

CR 36 & CR 81 intersect AR 53 at two (admittedly close but) distinct places.

Quote
56: WidRd -> CR36? I can't find signs for either, and neither OSM nor Google lists a name

ASDI again.

Quote
59: move RigDr south to the I-540 overpass?

There's no graph connection to be made there, so I don't see a compelling reason to move it.

66: OakSt_N -> OakSt_E, WalSt_S -> WalSt_W?

Oak St & Walnut St are oriented SW/NE (https://www.openstreetmap.org/#map=16/35.8295/-92.5603) and aren't signed as N/S or E/W, so why would this be any better?

Quote
69: AR69BNew -> AR69BNew_N?

They only intersect once.

Quote
74: are you sure about CR3180? I can't make out the number on GSV and Google and OSM both (from TIGER) label it 3655

3180 connects to 3655, and the last digit of the number in the blurry sign looks more like a 0 than a 5.

Quote
74: presumably CR3850 and CR4500 are on street signs?
74mar, 74sno: ditto for these street names

ASDI again. Changed CR4500 to CR 4500/4840 to include both intersecting roads at the end.

Quote
75/US 64: why is there a point at FroSt?

That was there when I started. Maybe @yakra knows. It's not in use now, but may have been in the past.

Quote
75: where does the name of LockDamRd come from?
75S: where does the name of IndParkRd come from?

ASDI. Technically AR 75 is connected to Lock & Dam Rd by a short gravel road, so I changed the label to "ToLockDamRd".

80: AR28_W -> AR28, since 28 isn't signed at the other intersection (US71)?

US71 should have been US71/28, so I changed that one instead.

Quote
86: OldAR11 -> OldHwy11?

That was once AR 11, so I'm leaving it.

Quote
86hay: where does the HolRd name come from?
86hay: CroRd -> HalRd (https://www.google.com/maps/@34.8172661,-91.6748428,3a,48.7y,76.6h,79.33t/data=!3m6!1e1!3m4!1seyYIgXxQADxzavm5KyFhLg!2e0!7i3328!8i1664)

ASDI again. The Halijan Rd sign is turned the wrong way.

Quote
88alt: LockDamRd -> HarLockDam (https://www.google.com/maps/@34.176984,-91.6709286,3a,75y,153.54h,82.25t/data=!3m6!1e1!3m4!1smjW6Rttpk-FmACLhlPEp2g!2e0!7i13312!8i6656)?

ASDI names it Lock & Dam Rd.

94 continues north from AR340

Yes, but it's unsigned. (https://www.google.com/maps/@36.4979069,-94.1811717,3a,75y,66.65h,94.86t/data=!3m6!1e1!3m4!1sJGsvCqxVLaXb-XXC5cMU7Q!2e0!7i13312!8i6656)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on December 30, 2019, 05:27:25 pm
I need to look at these in more detail, but this stuck out:
Quote
17: US64Bus -> US64Bus_E (https://www.google.com/maps/@35.2703769,-91.2352796,3a,15.9y,138.1h,85.06t/data=!3m6!1e1!3m4!1swnhA9r6d0wBey-d-y5x3Qw!2e0!7i13312!8i6656) (and US64BusMcC should extend back to US 64)

Eric removed the western segment a couple of years ago, and it's signed "To US 64" (https://www.google.com/maps/@35.258432,-91.234782,3a,75y,22.68h,88t/data=!3m6!1e1!3m4!1sxgQA9UtHXRDseH-2U8HTBg!2e0!7i13312!8i6656) now.
What do you mean "now"? Both photos are from August 2013. The state didn't think it was important to sign it heading away from downtown (some states, including Wyoming, have a policy of using 'to' the parent) but put up signs for an overlap towards downtown.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on December 30, 2019, 07:34:11 pm
I need to look at these in more detail, but this stuck out:
Quote
17: US64Bus -> US64Bus_E (https://www.google.com/maps/@35.2703769,-91.2352796,3a,15.9y,138.1h,85.06t/data=!3m6!1e1!3m4!1swnhA9r6d0wBey-d-y5x3Qw!2e0!7i13312!8i6656) (and US64BusMcC should extend back to US 64)

Eric removed the western segment a couple of years ago, and it's signed "To US 64" (https://www.google.com/maps/@35.258432,-91.234782,3a,75y,22.68h,88t/data=!3m6!1e1!3m4!1sxgQA9UtHXRDseH-2U8HTBg!2e0!7i13312!8i6656) now.
What do you mean "now"? Both photos are from August 2013. The state didn't think it was important to sign it heading away from downtown (some states, including Wyoming, have a policy of using 'to' the parent) but put up signs for an overlap towards downtown.

I drove that segment in 2018 and remember the signage being similar to the 2013 GMSV, although I did not check the westbound sign since I was driving the opposite direction.
Title: Re: usaar: Arkansas state highways
Post by: yakra on January 01, 2020, 07:12:40 pm
In addition to changes to the US 63 file, this also means the following files need US49* -> US49/63* (unless we want to wait until we're sure it's well signed and not just signed like a typical Arkansas overlap):
US64 14 17 38 42 158Otw 214 226 269 284 306 364 956-1
Not necessarily. The manual says Two numbered highways may appear in a waypoint (http://travelmapping.net/devel/manual/wayptlabels.php#slash), but does not say it must or shall happen in places where it can. Further text from the same guideline goes on to imply that it's allowable to use only one:
"consider skipping the city abbrev. or even skipping the whole second route."
"If the cross road has 3+ designations, use the main one or two designations. "
Thus, yes, these labels could be changed, but IMO they're fine as they are as well.

AR 5 departs there from the service road between interchanges, not from I-30 itself. I changed the west split to I-30.
Haven't looked to see what you ended up doing here. Just noting that my labeling style has been, for simplicity's sake, to drop references to service roads, frontage roads, ramps, etc., and consider these part of the parent route complex, part of I-30 in this case.

Quote
29: 23rdSt_E -> 23rdSt (https://www.google.com/maps/@33.6462368,-93.5871274,3a,15y,342.26h,97.66t/data=!3m6!1e1!3m4!1swxBLagjEm4GnAPDCChlKsQ!2e0!7i13312!8i6656)
Even though there's no corresponding point at the other junction, streets named 23rd St do head both east and west from AR 29.
Such suffixes are common for "multiplexes" along city streets (e.g., MainSt_N, etc.), but this appears to not be one of those cases, being Bill Clinton Dr.

43sil/OK20: E0390 -> E390 (https://www.google.com/maps/@36.4526474,-94.6103037,3a,75y,223.47h,83.72t/data=!3m6!1e1!3m4!1sTNQhDx6iy80FMhj6cVNxTw!2e0!7i13312!8i6656)
I changed the name in the AR 43 file and will leave OK 20 to @yakra.
Section line roads in Oklahoma are similar to Manitoba: a region-wide grid, with a uniform numbering scheme, that don't always end up signed consistently in the field. @mwasleski chose to standardize on a uniform nomenclature for these statewide. I'll stick with his labeling scheme.

66: OakSt_N -> OakSt_E, WalSt_S -> WalSt_W?
Oak St & Walnut St are oriented SW/NE (https://www.openstreetmap.org/#map=16/35.8295/-92.5603) and aren't signed as N/S or E/W, so why would this be any better?
It's a stretch, but... Main St is a brief interruption in the Oak/Walnut axis of the grid otherwise following AR66's overall E/W orientation? :D
Hey, I said it was a stretch! Doesn't matter much.
OTOH, maybe... MainSt_* labels?

Quote
Quote
75/US 64: why is there a point at FroSt?
That was there when I started. Maybe @yakra knows. It's not in use now, but may have been in the past.
blame (https://github.com/TravelMapping/HighwayData/blame/master/hwy_data/AR/usaus/ar.us064.wpt#L129) -> commit (https://github.com/TravelMapping/HighwayData/commit/9645728a33d99838e8f69fe6acbb88c86bf5ec1e#diff-de487655935fb2c847cfa124ac3d1a45L125-R125)
Title: Re: usaar: Arkansas state highways
Post by: mapcat on January 02, 2020, 07:30:57 pm
https://github.com/TravelMapping/HighwayData/pull/3495 (https://github.com/TravelMapping/HighwayData/pull/3495)

102: I-49 -> I-49/62?

I've not been in the practice of using non-interstate designations in waypoints at interstates

Quote
103: Where does the CR1800 name come from? There's a street sign (https://www.google.com/maps/@36.0795147,-93.4005191,3a,44.2y,292.86h,86.66t/data=!3m6!1e1!3m4!1sq6kwUYIzFA_2N0gsVZLeeQ!2e0!7i3328!8i1664) that might say George Rd.

ASDI calls it CR1800. I can't quite make out what the sign says.

118/US 64: SprRd -> SprHillRd (https://www.google.com/maps/@35.271331,-90.3975307,3a,75y,326.71h,78.52t/data=!3m6!1e1!3m4!1spYiazdAoBW0vSmWrsGG2Ag!2e0!7i3328!8i1664)

ASDI calls it Springhill Rd; more recent GMSV shows the street sign missing.

Quote
119mar is inventoried as two sections, both ending at US 61. The west piece (section 0) is signed north-south (from 14 to US 61), while I can't find any directional signs on the east piece (section 1). Suggest separating and reversing the east piece as 119But.

I'm not convinced that this will be helpful. The sections are so short and so close together. By the standard I established when I began (concurrent along one route, doesn't cross a county line), this appears to be a clear example of when to combine sections.

Quote
124: GraCutRd -> CR33 (https://www.google.com/maps/@35.3889889,-92.3493096,3a,35.5y,104.83h,83.44t/data=!3m6!1e1!3m4!1sWakh09tn9CYbdO03RtTIxQ!2e0!7i3328!8i1664)?

GraCutRd matches ASDI (Gravesville Cutoff Rd). I can't read the county road marker in GMSV.

combine 135 and 135par (https://www.google.com/maps/@36.0525846,-90.4404382,3a,19.1y,338.93h,88.5t/data=!3m6!1e1!3m4!1sEglnabf_6juPzNzr04qOWg!2e0!7i13312!8i6656)

135 is not signed along 49B, and there's no indication for drivers following 412 west that they need to turn onto 49B to get to 135.

Quote
140: the piece east of US 61 doesn't make much sense as part of the same segment, and it's mileposted from south to north, with signs both north (south end) and east (north end); maybe split as 140Osc

I'm almost convinced to go along with you on this one because of the irrational shape of the route, but it goes against the guidelines I set and may or may not be worth making an exception. Anyone else have an opinion?

Quote
145: CR675 -> CR42/679??

Per ASDI, it's 655/675.

Quote
145lit: CR56 -> CR36?

ASDI calls CR56 CR318. GMSV from 2009 shows a 2-digit number on the pentagon, but newer GMSV elsewhere in the county shows many 3-digit routes that match the ASDI numbers, so it's possible that the county renumbered their county roads sometime in the past decade.

151: TX/AR -> StaLineAve?

The manual favors border names over street names when they coincide.

Quote
159dum: OldUS65 -> MainSt_N?

It's not clear it's still called Main St there (It's called Main St in Dumas, but this point is in Mitchellville). ASDI calls the road Hwy 159, and the usually correct ESRI maps call it Old 65 Hwy.

161nor: move TraRd north to the intersection

Trammell Rd has a large Y so I placed the marker approximately halfway between the two intersections.

Quote
169: MillRd -> HanRd_N? (since sources disagree on the former name)

ASDI calls it Mill Yard Rd but GMSV at the other end of the road shows Millyard Rd on the sign, so I changed it to MilRd.

Quote
177: JorRd -> CR64/70 (https://www.google.com/maps/@36.2335301,-92.1840064,3a,29.4y,154.17h,77.86t/data=!3m6!1e1!3m4!1syuvB-HYXIwqCYO3K4KnYVg!2e0!7i3328!8i1664)?

The GMSV is 11 years old there, so since ASDI calls it Jordan Rd, I'm inclined to use that name.

Quote
183: 4thSt -> MilParkRd?

Both 4th St & Mills Park Rd are signed at that intersection, so why is one any better than the other?

Quote
186: extend south to NorRd

The inset on the Franklin County map (http://www.arkansashighways.com/maps/Counties/County%20PDFs/FranklinCounty.pdf) shows it ending at Alix Ln.

Quote
187: BeaParkRd -> DamLakeCamp (https://www.google.com/maps/@36.4185,-93.8499065,3a,52.7y,24.41h,75.09t/data=!3m6!1e1!3m4!1sMsB_luY_gbdjgAF_yfiRcg!2e0!7i16384!8i8192)?

ASDI calls it Beaver Park Rd.

Quote
189: PraRd has a county road number on the sign, but I can't make it out

ASDI calls it Prairie Rd so I'm comfortable leaving it.

Quote
189ham: HamLim -> CR17 (https://www.google.com/maps/@33.2137018,-91.8092565,3a,43.3y,244.22h,78.89t/data=!3m6!1e1!3m4!1stOo8AsLDd7kZh72oQK5HuA!2e0!7i13312!8i6656)?

My interpretation of the manual makes me think that a border (Hamburg Limits) takes precedence over a name change in the middle of a road, even when it's signed. But I could go either way on this.

Quote
195/US 371: CR261 (262 per Google?) is gated (https://www.google.com/maps/@33.8980281,-93.6064309,3a,24.3y,276.88h,82.93t/data=!3m6!1e1!3m4!1sSgnsKDF6A37Re3gsQm_hfw!2e0!7i13312!8i6656)

You meant  WalTr. The point on 371 was not in use, so I replaced it with a shaping point.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 02, 2020, 10:47:57 pm
5Lit: I-30SerRd_E -> I-30_E (just as the west split is I-30/35, not just AR35)

AR 5 departs there from the service road between interchanges, not from I-30 itself. I changed the west split to I-30.
That makes no sense. The east and west splits are functionally equivalent interchanges with the frontage roads. The east split even has a ramp to I-30 east right there.

Also: 5's ConRd point should line up with I-30's 118. Exit 118 feeds directly into 5.

Quote
4: US67Spr -> US67Y

It's US67Spr in the HB.
Should be US67Y or US67Wye.

Quote
35: CR56 -> RyeCutRd (https://www.google.com/maps/@33.8280859,-92.0780026,3a,21.1y,68.38h,83.71t/data=!3m6!1e1!3m4!1sGbBqew75yp3tJ7Pw9Xf26Q!2e0!7i13312!8i6656)?

The sign blade includes "CCR#56" after the name.
There are a whole bunch of sign blades in Arkansas and Louisiana that include parish/county route numbers. I didn't list them because they're generally smaller than the names.

That's how I handled it (AR 36 (Searcy).
AR367 -> AR36/367?

Quote
53: CR81 -> CR36/81

CR 36 & CR 81 intersect AR 53 at two (admittedly close but) distinct places.
You should probably move the point to CR36 then, since 53 traffic has to stop there.

Quote
59: move RigDr south to the I-540 overpass?

There's no graph connection to be made there, so I don't see a compelling reason to move it.
Why not make a graph connection? The I-540 exit is signed for 59 and nothing else on the main signs.

66: OakSt_N -> OakSt_E, WalSt_S -> WalSt_W?

Oak St & Walnut St are oriented SW/NE (https://www.openstreetmap.org/#map=16/35.8295/-92.5603) and aren't signed as N/S or E/W, so why would this be any better?
Because 66 is east-west and US 65 is north-south? It seems to better fit the local geography.

94 continues north from AR340

Yes, but it's unsigned. (https://www.google.com/maps/@36.4979069,-94.1811717,3a,75y,66.65h,94.86t/data=!3m6!1e1!3m4!1sJGsvCqxVLaXb-XXC5cMU7Q!2e0!7i13312!8i6656)
That seems like splitting hairs, since traffic on 94 itself has no indication the route ends at 340.

Quote
183: 4thSt -> MilParkRd?

Both 4th St & Mills Park Rd are signed at that intersection, so why is one any better than the other?
Because the latter is a more important road.

I need to look at these in more detail, but this stuck out:
Quote
17: US64Bus -> US64Bus_E (https://www.google.com/maps/@35.2703769,-91.2352796,3a,15.9y,138.1h,85.06t/data=!3m6!1e1!3m4!1swnhA9r6d0wBey-d-y5x3Qw!2e0!7i13312!8i6656) (and US64BusMcC should extend back to US 64)

Eric removed the western segment a couple of years ago, and it's signed "To US 64" (https://www.google.com/maps/@35.258432,-91.234782,3a,75y,22.68h,88t/data=!3m6!1e1!3m4!1sxgQA9UtHXRDseH-2U8HTBg!2e0!7i13312!8i6656) now.
What do you mean "now"? Both photos are from August 2013. The state didn't think it was important to sign it heading away from downtown (some states, including Wyoming, have a policy of using 'to' the parent) but put up signs for an overlap towards downtown.

I drove that segment in 2018 and remember the signage being similar to the 2013 GMSV, although I did not check the westbound sign since I was driving the opposite direction.
So we have signage showing an overlap. The truncation should be reverted.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 03, 2020, 11:09:46 am
Quote
How sure are we that 12 doesn't use 71B to 94 in Rogers? This sign (https://www.google.com/maps/@36.3551327,-94.122447,3a,15y,292.49h,90.03t/data=!3m6!1e1!3m4!1sCQRa-mFW3DPKI9gmD5s_5w!2e0!7i13312!8i6656) points westbound traffic left on 94, and there are some to 12 signs at the 71B/94 intersection. On the other hand, eastbound signs exist on I-49 north showing the routing we have. Some discussion on AARoads. (https://www.aaroads.com/forum/index.php?topic=3390.msg117481#msg117481)

I left it as-is because historical GMSV shows the routing used to follow US71B, but was changed within the past decade (probably 2011, given the date of the AA roads discussion). The "To AR 12 East" sign (https://www.google.com/maps/@36.3334634,-94.1263143,3a,51.9y,73.73h,88.52t/data=!3m7!1e1!3m5!1sWdJPZeu9CHJ9KOlmkpplBQ!2e0!6s%2F%2Fgeo0.ggpht.com%2Fcbk%3Fpanoid%3DWdJPZeu9CHJ9KOlmkpplBQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D286.9288%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192) on 71B at 8th indicates that that is the desired route for traffic now. There's another one heading west at the same location ("To AR 12 West").
I'm still not convinced that the I-49 overlap is correct. There's signage on 12 itself (https://www.google.com/maps/@36.3551327,-94.122447,3a,27.9y,292.36h,86.72t/data=!3m6!1e1!3m4!1sCQRa-mFW3DPKI9gmD5s_5w!2e0!7i13312!8i6656) showing the surface alignment via 8th, while the only signs supporting I-49 are after you turn.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 03, 2020, 11:54:30 am
US 62: HoltRd -> CR78 (https://www.google.com/maps/@35.9592537,-94.4398613,3a,22.3y,137.44h,82.67t/data=!3m6!1e1!3m4!1s3qnkY6kJ58bntoQihMCtWQ!2e0!7i13312!8i6656)?
US 62: CR28 -> MockSt (https://www.google.com/maps/@35.963561,-94.3182794,3a,15y,109.97h,98.58t/data=!3m6!1e1!3m4!1sbKSiTicZj9BskbU3XaghVg!2e0!7i13312!8i6656)?
US 62: CR27 -> DouSprRd (https://www.google.com/maps/@36.0392418,-94.2540687,3a,56.8y,236.65h,87.63t/data=!3m6!1e1!3m4!1s0P9tHWtAQ4lqmS8K6MlaSw!2e0!7i13312!8i6656)?
US 62: AR12/94 -> AR94_W or AR12_E (AR94_E is also signed for AR12/94 (https://www.google.com/maps/@36.3551327,-94.122447,3a,27.9y,292.36h,86.72t/data=!3m6!1e1!3m4!1sCQRa-mFW3DPKI9gmD5s_5w!2e0!7i13312!8i6656))
US 62: PraRd -> OldLibRd (https://www.google.com/maps/@36.4455287,-94.0110342,3a,27.2y,145.84h,87.24t/data=!3m6!1e1!3m4!1sGsH6WgWMHujLlo4ap05Ciw!2e0!7i13312!8i6656)
US 62: RebLn is in the wrong place. Recommend moving southeast to CR107 (https://www.google.com/maps/@36.4449049,-93.8232335,3a,34.9y,305.6h,77.14t/data=!3m6!1e1!3m4!1sK61apNEw7bMFeRz_vlXuZg!2e0!7i16384!8i8192) http://www.openstreetmap.org/?lat=36.444908&lon=-93.823355 , a slightly more important road.
US 62: move CR208 slightly west to http://www.openstreetmap.org/?lat=36.441814&lon=-93.787140
US 62: CR302 -> RockHouRd (https://www.google.com/maps/@36.3889296,-93.7114401,3a,15y,185.71h,88.53t/data=!3m6!1e1!3m4!1si9vYLDcU0MzNqVFjONOjUw!2e0!7i16384!8i8192)
US 62: PubSq -> ChuSt (https://www.google.com/maps/@36.3654623,-93.5660783,3a,17.9y,298.46h,89.31t/data=!3m6!1e1!3m4!1sv_epmyyccbYIBxypj4ODog!2e0!7i13312!8i6656)? Or if the name for those two half blocks is PubSq, move it south 1/2 block
US 62: AR21_N -> AR21/221?
US 62: AR980 -> AR980Har? there's another 980 intersection
US 62/412: CarLn -> CarDr (https://www.google.com/maps/@36.2324097,-92.8934511,3a,15y,171.7h,87.53t/data=!3m6!1e1!3m4!1sT8ylWDmicwQo3AV3NMZ-_A!2e0!7i13312!8i6656)?
US 62/412: AR178 -> AR178_W
US 62/412: EastMainSt -> OldHwy62E (https://www.google.com/maps/@36.2619575,-92.5706378,3a,75y,287.56h,79.8t/data=!3m6!1e1!3m4!1sATa_H6YwYY1V3DXzW0R2fQ!2e0!7i13312!8i6656)
US 62/412: CR724 -> CR7024 (https://www.google.com/maps/@36.279232,-92.5443624,3a,15y,343.99h,85.33t/data=!3m6!1e1!3m4!1soKjJMOSI6Jp-SsCNwrHv_w!2e0!7i13312!8i6656)
US 62/412: ArkRd -> OldArkRd (https://www.google.com/maps/@36.3174808,-92.3676878,3a,15.2y,186.22h,83.24t/data=!3m6!1e1!3m4!1sK3bkOjTGRHPADW8hU2Lp4A!2e0!7i13312!8i6656)
US 62/412: CraPtRd -> CraRd (https://www.google.com/maps/@36.3756568,-92.3154423,3a,16.3y,319.15h,92.64t/data=!3m6!1e1!3m4!1sjui4blnfaJ0Vtw50LSYgOA!2e0!7i13312!8i6656)
US 62/412: PorCir -> PorCir_W? also needs shifting southwest
US 62/412: HandCoveRd -> HanRd (https://www.google.com/maps/@36.3756547,-92.1463478,3a,16.8y,153.96h,83.15t/data=!3m6!1e1!3m4!1s-4xgrJmbD_2dwwRWoTCAoA!2e0!7i13312!8i6656)
US 62/412: MilCreLn is off
US 62/412: FarmRd101 -> FM101Rd (https://www.google.com/maps/@36.2740775,-91.507359,3a,18.9y,58.15h,91.57t/data=!3m7!1e1!3m5!1ss8GcGPUGrlPnltSiLGpR2g!2e0!5s20130901T000000!7i13312!8i6656) (might be named after a radio station?)
US 62: CorMunAir -> AR980Cor
US 62: US49 -> US49/1?

US 63: US82B -> US167(15), US167_N -> US167(16)
US 63: BolPurRd doesn't intersect; replace with BolPassRd (https://www.google.com/maps/@33.2763699,-92.3492237,3a,15.3y,261.32h,86.53t/data=!3m6!1e1!3m4!1saQ5U_VufIBWdW2Tz-a25lg!2e0!7i13312!8i6656) at what OSM calls Romeo Road?
US 63: AR8_S -> AR8_E (https://www.google.com/maps/@33.5444354,-92.0706767,3a,55.2y,151.07h,86.58t/data=!3m6!1e1!3m4!1sLFO09mHta5ZFAbGKHpxyPg!2e0!7i13312!8i6656), AR8_N -> AR8_W (https://www.google.com/maps/@33.6323403,-92.0742803,3a,34.4y,3.88h,85.89t/data=!3m6!1e1!3m4!1sE-q84MOp15Jlu4Pz4dczRA!2e0!7i13312!8i6656)
US 63: SteLp -> CR22 (https://www.google.com/maps/@33.6645642,-92.0617601,3a,15y,53.31h,85.64t/data=!3m6!1e1!3m4!1sMigio9y8OEwwashzV5sDSQ!2e0!7i13312!8i6656)?
US 63: ChaLn doesn't exist, at least not where shown
US 63/79: WabRd -> MagSt (https://www.google.com/maps/@34.3628049,-91.7951592,3a,22.1y,224.77h,82.92t/data=!3m6!1e1!3m4!1sgVWzNKar6Oek_bOuNgSEFA!2e0!7i13312!8i6656)
US 63/79: SenLp -> SenLp_N?
US 63: AR226 -> 46, WasAve -> 47, AR91_S -> 49
US 63: PauSwiRd -> CR398 (https://www.google.com/maps/@35.9522378,-90.8249228,3a,15y,18.26h,84.47t/data=!3m6!1e1!3m4!1sfmlD-tW4kKbrdPwz4OxcIg!2e0!7i13312!8i6656)
US 63/412: FreeSt -> CR511 (https://www.google.com/maps/@36.0885736,-91.0727014,3a,37y,185.96h,82t/data=!3m6!1e1!3m4!1scu_eW72UrD-Hd13RuZmm_Q!2e0!7i13312!8i6656)?
US 63: CR75 -> TallTimRd (https://www.google.com/maps/@36.3377115,-91.4907559,3a,19.8y,263.7h,84.19t/data=!3m6!1e1!3m4!1sh5mAOgfHMG-EdFNfwrb25Q!2e0!7i13312!8i6656)

US 64: AR162_W -> AR162, AR162_E -> AR162_W (https://www.google.com/maps/@35.4854602,-94.2209613,3a,48.6y,272.21h,80.07t/data=!3m6!1e1!3m4!1sSuGcWu1gl4lwYthqnPWHRg!2e0!7i13312!8i6656)?
US 64: US64BusAlm_E -> US64BusAlm?
US 64: AR352_W -> AR352Mul, AR352_E -> AR352Cla
US 64: CraAve -> CR2250 (https://www.google.com/maps/@35.4348617,-93.5954827,3a,43.4y,152.66h,80.4t/data=!3m6!1e1!3m4!1sdXK93xQOLW6ZnhcMjT-xVg!2e0!7i13312!8i6656)
US 64: AR359 -> AR359_E
US 64: Pin -> CR1715 (https://www.google.com/maps/@35.3457496,-93.3315703,3a,20.8y,65.21h,84.48t/data=!3m6!1e1!3m4!1s3m8mOq4mgIxdB1cAlt2iNg!2e0!7i13312!8i6656)
US 64: DwiMisRd -> MisRd??
US 64: AR133_N -> AR133_W
US 64: I-40(117) -> ToI-40(117)?
US 64: OldAR25 -> OldHwy25?
US 64: HillLoop no longer intersects where shown; move southeast and rename MarFisRd (https://www.google.com/maps/@35.094551,-91.9627873,3a,17.6y,7.24h,92.7t/data=!3m6!1e1!3m4!1s8zK4hLu11h2YRlnJdqoMAw!2e0!7i16384!8i8192) http://www.openstreetmap.org/?lat=35.094877&lon=-91.962808
US 64: US67/167_S and so on -> US67(28), US67(29), US67(31), US67(35), US67(42), US67(44), US67(45), US67(46), US67(48), US67(51), US67(54), US67(55)
US 64: AR17_S -> US64Bus/17 or US64BusMcC_W, US64BusMcC -> US64BusMcC_E
US 64: CR401 -> CR401/825 (https://www.google.com/maps/@35.2621036,-90.6623852,3a,15y,131.18h,84.03t/data=!3m6!1e1!3m4!1sOS6rTZkc__dD6JkAwjMniA!2e0!7i13312!8i6656)
US 64: SprRd -> SprHillRd (https://www.google.com/maps/@35.271331,-90.3975307,3a,50.8y,321.8h,76.27t/data=!3m6!1e1!3m4!1spYiazdAoBW0vSmWrsGG2Ag!2e0!7i3328!8i1664)
US 64: AR118 -> AR118_S (https://www.google.com/maps/@35.208193,-90.2193233,3a,75y,225.56h,82.44t/data=!3m6!1e1!3m4!1sFGEQDuJrxDGLEl148UzUSw!2e0!7i13312!8i6656)

US 65: AR159_A -> AR159Lak_N, AR159_B -> AR159Lak_S, AR159_C -> AR159Mas, AR159_D -> AR159McG, AR159_E -> AR159Ome, AR159_F -> AR159Dum
US 65: CadDr -> FenLn (https://www.google.com/maps/@35.2942068,-92.4028376,3a,17.8y,212.53h,91.57t/data=!3m6!1e1!3m4!1swuHjYZONpCalxyVo6MrhEg!2e0!7i13312!8i6656)
US 65: AR124_W -> AR124/285, AR285 -> AR285_N
US 65: OldAR336 -> CR336 (https://www.google.com/maps/@35.5148665,-92.4374208,3a,16.6y,130.42h,88.55t/data=!3m6!1e1!3m4!1sGswr4uS6LRU4Uj_Runfhxg!2e0!7i16384!8i8192)
US 65: MilRd -> MillRd?
US 65: AR333_S -> AR333Mar, AR333_N -> AR333Gil
US 65: CR26 -> PinGroRd (https://www.google.com/maps/@36.0675196,-92.8836765,3a,20.9y,245.66h,85.22t/data=!3m6!1e1!3m4!1sgL_iR62X4g15dfONIpc2sQ!2e0!7i13312!8i6656)
US 65: HerLn -> CR4054 (https://www.google.com/maps/@36.0649353,-92.9389309,3a,15y,261.82h,91.98t/data=!3m6!1e1!3m4!1sl8r45XcE34p1Nnw-Rs49Aw!2e0!7i13312!8i6656)?
US 65: WolSprRd -> WolfSprRd

US 67: AR174_S -> AR174_E (https://www.google.com/maps/@33.6642189,-93.6001059,3a,28.9y,192.4h,85.5t/data=!3m6!1e1!3m4!1sPwv7axf6lWgCSBXmQWyL5Q!2e0!7i13312!8i6656)
US 67: WalCutRd -> WalCut (https://www.google.com/maps/@34.2504751,-92.8970863,3a,56.1y,108.24h,82.68t/data=!3m6!1e1!3m4!1sRMGUN0e-PUdvQu_WgEPShg!2e0!7i13312!8i6656)
US 67: I-30(106) -> ToI-30(106)?
US 67: I-40(155) -> 155 (https://www.google.com/maps/@34.7822302,-92.2315742,3a,28y,209.67h,92.36t/data=!3m6!1e1!3m4!1svmdvSDpqd7h1C4UqKo9Tyg!2e0!7i13312!8i6656)
US 67: McCBlvd and so on -> 1, 2 (but this is signed for Trammel Road, so is it the same as 3?), 3, 4, 5, 6, 8, 9, 10A, 10B, 11A, 11B (new point (https://www.google.com/maps/@34.8907071,-92.1025992,3a,75y,71.24h,80.96t/data=!3m6!1e1!3m4!1so2Kk9G0LgRjDFHrkg2mWMw!2e0!7i13312!8i6656)), 16, 19, 21, 22, 25, 28, 29, 31, 35, 42, 44, 45, 46, 48, 51, 54, 55, 60, 65, 69, 74, 80, 82, 83, 85, 87, 95, 102, 111, 121
US 67: US67Spr -> US67Y or US67Wye
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 03, 2020, 04:23:38 pm
US 70: AirRd_DeQ -> SevCouAir (https://www.google.com/maps/@34.0445993,-94.4048949,3a,28.6y,318.17h,84.21t/data=!3m6!1e1!3m4!1sMyeErZO6Aol3kGHoFuqsqg!2e0!7i13312!8i6656)?
US 70: EastParkRd -> EParkRd?
US 70: AirRd_Hem -> AdamBroRd (https://www.google.com/maps/@34.4429259,-93.2025044,3a,25.9y,94.33h,86.03t/data=!3m6!1e1!3m4!1sHpthTPTLkTnWxmXe_V3EPw!2e0!7i13312!8i6656) (or AdamBroRd_E?)
US 70/270: the Hot Springs bypass has exit numbers (1 2 3 4 5 7 9 11), but they follow the entire freeway, not 70 or 270. I don't know how to handle these - 2(HSB)? Should US70BusHot_E be 11B (since 11A is to stay on 70)?
US 70: AR88_W -> AR88Hot (if not 4), AR88_E -> AR88Lon
US 70: AR128_W -> AR128Hot (if not 7), AR128_E -> AR128Fou
US 70: AR50_W -> AR50Mad, AR50_E -> AR50Cra
US 70: AR38_W -> AR38Hug, AR38_E -> AR38Wes

US 71/270: CR76 -> CR76E (https://www.google.com/maps/@34.6520809,-94.1583028,3a,19.1y,147.41h,81.93t/data=!3m6!1e1!3m4!1sRYNygSFkfjOZgGiygxAzYg!2e0!7i13312!8i6656) and move south to the intersection with a sign?
US 71/270: WoodRd[sic] is gated (https://www.google.com/maps/@34.7295844,-94.0798681,3a,20.3y,151.28h,85.84t/data=!3m6!1e1!3m4!1se8K5dEojKHLKX8oTk8b3ZQ!2e0!7i13312!8i6656)
US 71: FreCreRd -> FreRd (https://www.google.com/maps/@35.0047381,-94.1205518,3a,15y,213.31h,85.48t/data=!3m6!1e1!3m4!1scOfr4H59hUECRkiFDr50AQ!2e0!7i13312!8i6656)
US 71: why is there a point at BroSt?
US 71: I-49Fut -> AR549
US 71: TrueLoveRd -> CR154 (https://www.google.com/maps/@35.8713756,-94.1233808,3a,36.3y,362.53h,81.11t/data=!3m6!1e1!3m4!1sXq_mhbJT_Q89DtZgoqWOQQ!2e0!7i13312!8i6656)?
US 71: WooRd -> CR35 (https://www.google.com/maps/@35.8834692,-94.166348,3a,26.7y,348.85h,87.3t/data=!3m6!1e1!3m4!1shlGQb82vyI8kmzEEBxI8gw!2e0!7i13312!8i6656)?
US 71: WalMouRd -> CR32 (https://www.google.com/maps/@35.975315,-94.1657796,3a,75y,7.05h,82.33t/data=!3m6!1e1!3m4!1sf-UtzWBfI4fWN3HF-8tv4Q!2e0!7i13312!8i6656)?
US 71: AR112/265 -> 60 (https://www.google.com/maps/@36.0337127,-94.181986,3a,40y,335.73h,89.21t/data=!3m6!1e1!3m4!1s1MzL9x1J_J-PoOd8uI07TA!2e0!7i13312!8i6656)
US 71: AR340 -> 98 (https://www.google.com/maps/@36.4728387,-94.2457464,3a,25.5y,345.7h,91.6t/data=!3m6!1e1!3m4!1s6t8RL8WOShR_ZrA65RbNQg!2e0!7i16384!8i8192)
US 71Fou: US67/82_* -> US82_* since 67 is north-south?
US 71Fou: extend north along the state line to just north of AR296? I'm not sure if there's a defined standard for this sort of situation

US 79: CR469 -> CR118 (https://www.google.com/maps/@33.4496954,-93.0418996,3a,16.6y,310.72h,86.03t/data=!3m6!1e1!3m4!1s__r9erM3iIiUO5AkFhSJIw!2e0!7i13312!8i6656)
US 79: AR205_S -> AR205Shu, AR205_N -> AR205Tho
US 79: CasDr -> CR84 (https://www.google.com/maps/@33.7878349,-92.4873963,3a,18.5y,355.2h,87.75t/data=!3m6!1e1!3m4!1sWdHR8BAwoNgHGxHxV0N7WA!2e0!7i13312!8i6656)?
US 79: US79Bus -> US79BusPin
US 79: OldUS79 is blocked off (https://www.google.com/maps/@34.6731425,-91.3409399,3a,75y,25.53h,85.17t/data=!3m6!1e1!3m4!1s9QOLwMgiVzF30MtQC7uGzA!2e0!7i13312!8i6656)
US 79: AR86_N -> AR86_W (https://www.google.com/maps/@34.6935249,-91.2828151,3a,38.5y,300.13h,82.48t/data=!3m6!1e1!3m4!1s61v_ovK5F79o95Bp-hcSYg!2e0!7i13312!8i6656), AR86_S -> AR86_E (https://www.google.com/maps/@34.6935238,-91.282716,3a,23.2y,113.52h,86.03t/data=!3m6!1e1!3m4!1sdzDPNl242vWU8cZIZTkYXQ!2e0!7i13312!8i6656)

US 82: RockSprRd -> CR18 (https://www.google.com/maps/@33.4179596,-93.8428065,3a,75y,288.09h,77.3t/data=!3m6!1e1!3m4!1s0QmbEqBzaplTY86mJlVSJQ!2e0!7i13312!8i6656)
US 82: MainSt -> HopeRd (https://www.google.com/maps/@33.3643996,-93.503402,3a,16.2y,230.5h,87.42t/data=!3m6!1e1!3m4!1s-kkgBxGMvImog99Z-3HDkA!2e0!7i13312!8i6656)
US 82: AirDr -> SArkAir (https://www.google.com/maps/@33.2091849,-92.8108615,3a,15y,323.64h,87.49t/data=!3m6!1e1!3m4!1s8fv14QEsFbo-MS5-os_wfQ!2e0!7i13312!8i6656)?
US 82: US82BusElD_W -> 17, AR15 -> 18, WestAve -> 19, US63/167 -> 22
US 82: GanCutRd -> GanCut (https://www.google.com/maps/@33.1138257,-92.3212686,3a,15y,285.73h,83.8t/data=!3m6!1e1!3m4!1sdyIJfLqQqkiit5VnUGtu3Q!2e0!7i13312!8i6656)
US 82: move PortCro to http://www.openstreetmap.org/?lat=33.151053&lon=-92.100459
US 82: RamRd -> CR11 (https://www.google.com/maps/@33.1422346,-92.0465152,3a,49.9y,163.03h,84.49t/data=!3m6!1e1!3m4!1sTeF1PYyc3Fxcx_FKJfttvw!2e0!7i13312!8i6656)
US 82: AR133T -> AR133T_S
Title: Re: usaar: Arkansas state highways
Post by: mapcat on January 03, 2020, 08:24:55 pm
https://github.com/TravelMapping/HighwayData/pull/3501 (https://github.com/TravelMapping/HighwayData/pull/3501) addresses 200-299

201: we need to determine whether it still overlaps US 62B through Mountain Home (https://www.google.com/maps/@36.3406492,-92.3850098,3a,31.3y,246.17h,90.75t/data=!3m6!1e1!3m4!1sMADv668y0wv0-Yl078rlLw!2e0!7i13312!8i6656) after the recent deletion inside the bypass.

I'll check with ADOT (and investigate the changes to US 63 as well).

Quote
203: the AR274* labels seem wrong, but I don't know what would work better. AR274_Cam, AR274_W, AR274_E?

I put AR274 at the north end, and AR274_W & _E at the ends of the concurrency.

Quote
208hal: LevRd -> CR55?

ASDI calls it Levee Rd.

Quote
215: CR5261 -> CR5440 and move a bit east

The end is where the Johnson County map's Oark inset (http://www.arkansashighways.com/maps/Counties/County%20PDFs/JohnsonCounty.pdf) shows it.

Quote
215mul: where does the ShoLakeRd name come from?
215ves: where does the NolRd name come from?

ASDI (Shores Lake Rd & Nolan Rd).

231 (main segment) is mileposted from east to west (and may be signed north-south to match the other segments; I can't make out what the signs say); should it be reversed?

It's signed north-south (https://www.google.com/maps/@36.3978138,-91.1084748,3a,75y,126.64h,79.53t/data=!3m6!1e1!3m4!1sXHcBeRmGWlUwrxYKuL3D6g!2e0!7i3328!8i1664) so I reversed it.

Quote
233bat: US167/25 -> US167_S? 25 isn't signed at this intersection

True but since it's in the HB as part of 25 I left it alone.

Quote
239: AR18/151 -> AR18_E? 151 isn't signed here

Likewise.

252/US 71: why the point at BroSt?

@yakra? I have no idea.

Quote
253: AR252 -> AR45 (252 isn't signed here)

Yes but since it's in the HB as part of 252 I corrected it to 45/252.

Quote
254: where do the names for the streets come from?

ASDI (Archey Rd, Little Red River Rd, Shady Grove Rd, Rocky Hill Rd)

Quote
255/US 71B: ZeroSt -> ZeroSt_E?? three junctions makes it hard

Changed to ZeroSt_A & _B.

260: CR668 -> 3ForRd?

ASDI calls it CR 668.

Quote
263: OldBreRd -> CR201?

It's Old Brewer Rd in ASDI.

Quote
264: AirBlvd -> NWARegAir (https://www.google.com/maps/@36.2573626,-94.2920143,3a,26.1y,273.87h,91.04t/data=!3m6!1e1!3m4!1sCKTni4ccDk7omzEqlMqm3Q!2e0!7i16384!8i8192)?

ASDI has Airport Blvd.

Quote
264sil needs to be reversed

It's signed as a W-E route beginning at BraRd.

282/US 71: LakeFortRd -> LakeSmiRd (https://www.google.com/maps/@35.6487311,-94.1603677,3a,46.3y,303.76h,84.57t/data=!3m6!1e1!3m4!1sQIHFPH6JNemnezPV0WC_xA!2e0!7i13312!8i6656)

Although "Ft" is small, it's on the sign.

Quote
285: US65/124 -> US65_N (124 isn't signed here)

Since the HB includes that as part of 124 I'm leaving it in the label.

Quote
286: ...extend west overlapping US 65B to US65Bus/60 (signs (https://www.google.com/maps/@35.0648055,-92.4282587,3a,75y,1.16h,91.33t/data=!3m6!1e1!3m4!1sbvvwrH43aVQ1y7rFjU3ufA!2e0!7i16384!8i8192) are inconsistent (https://www.google.com/maps/@35.065666,-92.4288934,3a,53.1y,352.95h,83.44t/data=!3m6!1e1!3m4!1sAXF-7b4E4m7fhNvORSf-Tg!2e0!7i16384!8i8192))

Using the signs at the end of the I-40 ramps, I'm considering I-40 to be the end.

Quote
289zio: BonRd -> BanRd (or CR61 (https://www.google.com/maps/@36.02188,-91.7847496,3a,20.4y,360.95h,85.18t/data=!3m6!1e1!3m4!1sA_2Wef19TOfcYaHi2kdIxg!2e0!7i13312!8i6656)?)

ASDI calls it Bonetown Rd.

Quote
Should 295com and 295cro be joined?

I'm open to this since they're in the same county and connected to the same route, but they're so short that the gap on AR 16 is longer than either segment.

Quote
299 is signed south from both ends. Mileposts are from I-30 to 24, so it should be reversed (that would make it west to east).

The only place where it's signed south heading away from 24 is at 387 (just south of the end). All other signage shows its north end at I-30.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 03, 2020, 09:54:59 pm
US 165: AR144_S -> AR144Lak, AR144_N -> AR144Gil
US 165: AR159_A -> AR159Mas, AR159_B -> AR159McG, AR159_C -> AR159Ome
US 165: AR169_S -> AR169McG, AR169_N -> AR169Ark
US 165: AR277_S -> AR277Til, AR277_N -> AR277Pea
US 165: AR276_E -> AR276_N

US 167: US167BusElD_S -> 15, US63_N -> 16, ChaRd -> 17
US 167: AR273 -> AR273Iva? (to distinguish from the one at US79Bus/273)
US 167: AR35_N -> AR35? US167BusShe_S would normally be AR35_N
US 167: FR9906 -> CR428??
US 167: AR367_A -> AR367Lit
US 167: see US 67 for exit numbers
US 167: AR367_C -> AR367_N
US 167: OakGroRd -> OakRd (https://www.google.com/maps/@35.6467792,-91.6027472,3a,15y,261.72h,88.97t/data=!3m6!1e1!3m4!1ss42dEydZySGc3vqYV9_Khw!2e0!7i16384!8i8192)
US 167: AR14 -> AR14/25
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 03, 2020, 10:01:43 pm
Quote
215: CR5261 -> CR5440 and move a bit east

The end is where the Johnson County map's Oark inset (http://www.arkansashighways.com/maps/Counties/County%20PDFs/JohnsonCounty.pdf) shows it.
However, there is an end state maintenance (https://www.google.com/maps/@35.6903016,-93.5714904,3a,42.8y,84.89h,78.53t/data=!3m6!1e1!3m4!1s2iW68TFA78urf56nkI8R1A!2e0!7i3328!8i1664) sign to the east.

282/US 71: LakeFortRd -> LakeSmiRd (https://www.google.com/maps/@35.6487311,-94.1603677,3a,46.3y,303.76h,84.57t/data=!3m6!1e1!3m4!1sQIHFPH6JNemnezPV0WC_xA!2e0!7i13312!8i6656)

Although "Ft" is small, it's on the sign.
Sure, but if we're dropping a word we should drop the small one. "If the cross road name has more than 3 words, use one of two options: 1. Pick out the two most important words besides the road type..."
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 04, 2020, 07:19:30 pm
US 270: CreDr -> BigRockCreRd (https://www.google.com/maps/@34.7245686,-93.958071,3a,16.5y,205.54h,87.28t/data=!3m6!1e1!3m4!1sBlKp5N46GCnpn-xdi3vbYA!2e0!7i13312!8i6656)
US 270: NFD33 -> FR33?

US 278: CR52600, CR51000, CR22450 -> I don't know what, but they're not county roads
US 278: SimLp -> SimLp_E
US 278: AR32_W -> AR32Oak, AR32_E -> AR32Wil
US 278: ExpStaRd -> CR4 (https://www.google.com/maps/@33.686163,-93.5779677,3a,22.1y,330.06h,83.97t/data=!3m6!1e1!3m4!1sbkE0H-9qLKOpGwbJi52GjQ!2e0!7i13312!8i6656)?
US 278: AR274 -> AR274Eas, AR274_E -> AR274For
US 278: CR7_W -> CR7Cal, CR7_E -> CR7Bra
US 278: FarRd -> CR25/32 (https://www.google.com/maps/@33.5924522,-92.0918138,3a,31.9y,149.34h,89.19t/data=!3m6!1e1!3m4!1slBDjmawCbNIFqKsxANHL6g!2e0!7i13312!8i6656)?
US 278: CarRd -> SamCarRd (https://www.google.com/maps/@33.6160479,-91.9507392,3a,15.4y,125.03h,89.59t/data=!3m6!1e1!3m4!1seIqMumMNtHx3pJqhmH6WYQ!2e0!7i13312!8i6656)
US 278: 7thSt -> CR133 (https://www.google.com/maps/@33.6294026,-91.9295773,3a,39.3y,296.83h,86.09t/data=!3m6!1e1!3m4!1sTceSmqnQrmmovtOZrUoUzQ!2e0!7i13312!8i6656)?
US 278: US278Byp_E -> US278Byp? (or keep as-is to futureproof?)
US 278: AR159_A -> AR159Mas_N, AR159_B -> AR159Mas_S, AR159_C -> AR159Mas, AR159_D -> AR159Lak_S, AR159_E -> AR159Lak_N
US 278: AR35/208 -> AR35_E, AR35 -> AR35_W

US 371: CR15 -> CR15_W
US 371: AR355_S -> AR355Pat, AR355_N -> AR355Min
US 371: AR200_S -> AR200Ros, AR200_N -> AR200Pre
US 371: move CR50 southeast
US 371: US67 -> US67_N
US 371: ProGroRd -> CR23 (https://www.google.com/maps/@33.9173531,-93.6599326,3a,46.5y,319.82h,78.17t/data=!3m6!1e1!3m4!1sou0Y9fOYt1pboMpFT_7ZOQ!2e0!7i13312!8i6656)

US 412: WilCreRd -> CR851 (https://www.google.com/maps/@36.1743093,-94.3172046,3a,15y,14.14h,83.12t/data=!3m6!1e1!3m4!1sJXr0zC_3Eto-DhcEG_cxEQ!2e0!7i13312!8i6656)?
US 412: SonRd -> CR93 (https://www.google.com/maps/@36.1652707,-94.0464322,3a,19.6y,127.97h,84.69t/data=!3m6!1e1!3m4!1srxTJKKVd9Dc9MWJK4tBkAg!2e0!7i13312!8i6656)?
US 412: WadeRd -> CR389/390 (https://www.google.com/maps/@36.1822742,-93.9870974,3a,24.1y,298.85h,86.2t/data=!3m6!1e1!3m4!1sJ40AfCb5aIdg3m_tFTPUHQ!2e0!7i13312!8i6656)?
US 412: OldUS412 -> CR8110 (https://www.google.com/maps/@36.1612488,-93.8671447,3a,19.4y,323.09h,85.72t/data=!3m6!1e1!3m4!1sw2W9uAS-MLS5Gd8uhbEyAw!2e0!7i13312!8i6656)?
US 412: CR728 -> CR720/728 (https://www.google.com/maps/@36.1554427,-93.4862942,3a,18.2y,265.97h,85.36t/data=!3m6!1e1!3m4!1sd0dhLYRtWlgehwzRG9VJkQ!2e0!7i13312!8i6656)
US 412: US49Spr -> US49Y or US49Wye
US 412: US412Byp -> US412Byp_E (to futureproof?)

US 425: CR28 -> King (https://www.google.com/maps/@33.8086099,-91.8464436,3a,15y,233.45h,85.81t/data=!3m6!1e1!3m4!1sS7FmmnS67lrvndKLlix9LQ!2e0!7i13312!8i6656)
US 425: GriLaddRd -> GriFieRd (https://www.google.com/maps/@34.1396301,-91.9082664,3a,15y,340.87h,84.39t/data=!3m6!1e1!3m4!1suSW3VEv7EHa-C5TwHmCWsw!2e0!7i13312!8i6656)
Title: Re: usaar: Arkansas state highways
Post by: mapcat on January 04, 2020, 09:48:16 pm
https://github.com/TravelMapping/HighwayData/pull/3507 (https://github.com/TravelMapping/HighwayData/pull/3507) finishes my first pass.

I can't find any directional plates on 301, and it's mileposted from west to east, so it should be reversed

I found one. (https://www.google.com/maps/@33.9931985,-93.4658946,3a,75y,50.05h,72.42t/data=!3m6!1e1!3m4!1sjbFIqW1BPGdIgtzimssAmQ!2e0!7i13312!8i6656) Reversed.

Quote
308: McDDr -> McDSt?

ASDI calls it Cummings St, so changed to CumSt.

Quote
310eno ends a bit northwest of BayRd, maybe far enough for a separate End point

That GMSV is over 12 years old, so I'm going with the endpoint shown on the county map (http://www.arkansashighways.com/maps/Counties/County%20PDFs/FaulknerCounty.pdf).

Quote
311 continues south from US 62 on Tyson Avenue, but that's unsigned, so no change (except adding a TysAve point on US 62?)

Since it's unsigned, a point shouldn't be necessary.

311: CR814 -> CR812/814 (https://www.google.com/maps/@36.3945998,-93.3692663,3a,21.1y,222.19h,83.22t/data=!3m6!1e1!3m4!1syD7mWHP9phN57V1GRQIRFQ!2e0!7i13312!8i6656)

Quote
318 is mileposted from north to south and east to west; should it be reversed?

It's hard to tell exactly how it's signed; this sign (https://www.google.com/maps/@34.467293,-90.9478244,3a,83.6y,228.21h,89.77t/data=!3m6!1e1!3m4!1sHlLltpgqDxVeOMydknCrZA!2e0!7i3328!8i1664) looks like it says "South" rather than "East"

Quote
319con is signed north-south (https://www.google.com/maps/@35.1111649,-92.5171002,3a,47.4y,266.98h,83.12t/data=!3m6!1e1!3m4!1sNK1Zjxd906i1KLIvEm0S-w!2e0!7i16384!8i8192) so should be reversed

It's already drafted starting from the south end so I don't undersand what needs to change.

323des: where does the LetRd name come from?

ASDI (Letchworth Rd).

Quote
324 is mileposted from north to south (or east to west according to the signs at the north end of the main segment and 324lak); should it be reversed (all but 324rus)?

I reversed 324ado, which doesn't have any directional signage, so I assume it's a W->E route.

Quote
331: OldAR247 -> Hwy247 (https://www.google.com/maps/@35.2506502,-93.0488131,3a,38y,237.04h,85.12t/data=!3m6!1e1!3m4!1s53vsa5DTyiLGemrIf96nMQ!2e0!7i13312!8i6656) or RivRd?

It's signed as "Hwy 247" and since AR 247 probably used that path in the past, OldAR247 seems appropriate.

Quote
337: LoboRd -> LoboLan (https://www.google.com/maps/@35.456022,-91.924787,3a,38.3y,5.57h,88.43t/data=!3m6!1e1!3m4!1sAF1QipMu3ow9aNvmrB7QyxeVRGgnRUO-FGkeUWKB63V_!2e10!7i5376!8i2688)? (and shift east a bit)

Changed to VogDr per ASDI (Vogel Dr).

343slo: where does the SarKonRd name come from?

ASDI (Saranie Konecny Rd).

350 is signed east-west everywhere but at US 64, and is mileposted from west to east, so should definitely be reversed

It's already drafted starting from the west end so I don't undersand what needs to change.

Quote
355 is mileposted from north to south (and is sometimes (https://www.google.com/maps/@33.5740132,-93.6139994,3a,75y,311.08h,86.12t/data=!3m6!1e1!3m4!1sKP76cZGgF8hSWUCF-XKIVA!2e0!7i13312!8i6656) signed east-west); should it be reversed?

It's signed northbound heading away from US 371, and southbound heading away (east) from AR 29, so I don't see the point of redoing it just because the northwestern-most part is misbehaving.

365: WiseRd -> DexEnt (https://www.google.com/maps/@34.3158858,-92.1082684,3a,44.5y,350.96h,85.87t/data=!3m6!1e1!3m4!1soLLR60aq48irg733iyPOPA!2e0!7i13312!8i6656)?

ASDI calls it Wise Rd.

Quote
366abe: OakLn -> End (https://www.google.com/maps/@34.604335,-91.3329832,3a,75y,56.53h,71.54t/data=!3m6!1e1!3m4!1sh_doLnFJsWwew9QTlM9jjQ!2e0!7i13312!8i6656)

According to ASDI, the easternmost part of AR 366's route is called Apple Bar Ln. AR 366 ends where Oak Ln meets Apple Bar Ln.

368: MainSt -> CR27 (https://www.google.com/maps/@33.7520623,-93.1055859,3a,75y,188.54h,72.84t/data=!3m6!1e1!3m4!1sA0Ny-y95NDz1sxPUJ6nFEQ!2e0!7i3328!8i1664)?

ASDI likes CR27 too (GMSV is illegible) so it's changed.

Quote
376 around Camden is mileposted in the reverse direction of the old 7 portion, but several signs (https://www.google.com/maps/@33.5357352,-92.8272156,3a,75y,125.24h,79.82t/data=!3m6!1e1!3m4!1sEoVkoultFarsoYoNEgoRRg!2e0!7i13312!8i6656) explicitly overlap 376 *east-west* with 7. At the south end it's signed north, and I can't make out the plates where it crosses 7. Probably no change.

Inconclusive, so leaving it alone.

Quote
380ogd: End -> CR230 (https://www.google.com/maps/@33.5811486,-94.0345629,3a,44.2y,49.65h,79.23t/data=!3m6!1e1!3m4!1s5Yw3ap0yw4Ekl88b3nZqCQ!2e0!7i3328!8i1664)

It already was named CR230 (there was no point in the file called "End") but since ASDI calls the other road intersecting the eastern-most end, I changed the label to CR70/230.

Quote
386tol: maintenance continues northwest to the sharp curve per mileage (https://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mlono_ras.pdf)

That map doesn't show enough detail to clearly refute this map (http://www.arkansashighways.com/maps/Counties/County%20PDFs/LonokeCounty.pdf), so I'm keeping the point at the intersection.

Quote
390: where does the CorEngRd name come from? rename LowLakeArea (https://www.google.com/maps/@34.179981,-93.0977646,3a,45.4y,199.87h,82.04t/data=!3m6!1e1!3m4!1sl36ZubLARL8iqRQdjW1Dtg!2e0!7i3328!8i1664)?

ASDI calls it Corps of Engineers Rd.

Quote
393ple: CotRd -> End?

ASDI shows the name changing from Hwy 393 to Cottontown Rd at the endpoint.

530 is built to have a limited number of intersections, so perhaps we should add points at all other intersections. That means adding:
AutHilRd http://www.openstreetmap.org/?lat=33.977349&lon=-91.918992 (http://www.openstreetmap.org/?lat=33.977349&lon=-91.918992)
OldSCRd_S http://www.openstreetmap.org/?lat=34.059664&lon=-91.958098 (http://www.openstreetmap.org/?lat=34.059664&lon=-91.958098)
530wil: ditto for BarRd http://www.openstreetmap.org/?lat=33.671354&lon=-91.886682 (http://www.openstreetmap.org/?lat=33.671354&lon=-91.886682)

I added all but OldSCRd_S, since it was only 0.15 mi from OldSCRd_N.

943-1 is unsigned except for state maintenance begins/ends (https://www.google.com/maps/@34.7699009,-91.9093984,3a,58.5y,280.32h,81.4t/data=!3m6!1e1!3m4!1sr9zFI3-703BpxQwxBABJdg!2e0!7i13312!8i6656) :( but US 70 and 31 should probably get a point at FishHatRd

Since 943-1 is unsigned, I don't see any reason for providing a point for it. If it's signed in the future, a point can be added then.

Quote
https://www.arkansashighways.com/maps/Counties/County%20PDFs/StFrancisCounty.pdf shows a 980 at Colt, but it's unsigned :( Maybe add an Arpt point on 1?

Ditto.

Quote
980mon: Arpt -> End (or realign? (https://www.google.com/maps/@33.6364726,-91.7578997,3a,42.6y,29.81h,84.48t/data=!3m6!1e1!3m4!1sV2pwxV__WZ7_RbI52LduAw!2e0!7i13312!8i6656))

The Drew County map (http://www.arkansashighways.com/maps/Counties/County%20PDFs/DrewCounty.pdf) shows that the end is actually at Commerce Dr, so since the "End Maintenance" sign and the sign showing 980 turning east at the Commerce Dr intersection contradict each other, I'm going with the map and ending it at the turn.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on January 05, 2020, 06:12:05 pm
In addition to changes to the US 63 file, this also means the following files need US49* -> US49/63* ...
... yes, these labels could be changed, but IMO they're fine as they are as well.

Once I hear back from ArDOT I will probably adjust all of the affected US49 labels.

Quote
AR 5 departs there from the service road between interchanges, not from I-30 itself. I changed the west split to I-30.
Haven't looked to see what you ended up doing here. Just noting that my labeling style has been, for simplicity's sake, to drop references to service roads, frontage roads, ramps, etc., and consider these part of the parent route complex, part of I-30 in this case.

I changed I-30 to I-30(117), ConRd to I-30(118), and I-30SerRd_E to MilRd_S. I also located I-30(118) to the waypoint on I-30, and added a shaping point between the two on AR5lit to break the false concurrency.

Quote
Quote
29: 23rdSt_E -> 23rdSt (https://www.google.com/maps/@33.6462368,-93.5871274,3a,15y,342.26h,97.66t/data=!3m6!1e1!3m4!1swxBLagjEm4GnAPDCChlKsQ!2e0!7i13312!8i6656)
Even though there's no corresponding point at the other junction, streets named 23rd St do head both east and west from AR 29.
Such suffixes are common for "multiplexes" along city streets (e.g., MainSt_N, etc.), but this appears to not be one of those cases, being Bill Clinton Dr.

Changed to E23rdSt to differentiate from W 23rd St.

Quote
66: OakSt_N -> OakSt_E, WalSt_S -> WalSt_W?
Oak St & Walnut St are oriented SW/NE (https://www.openstreetmap.org/#map=16/35.8295/-92.5603) and aren't signed as N/S or E/W, so why would this be any better?
It's a stretch, but... Main St is a brief interruption in the Oak/Walnut axis of the grid otherwise following AR66's overall E/W orientation? :D
Hey, I said it was a stretch! Doesn't matter much.
OTOH, maybe... MainSt_* labels?

Going with OakSt_E & WalSt_W based on AR 66's signed direction of travel.

Quote
4: US67Spr -> US67Y
It's US67Spr in the HB.
Should be US67Y or US67Wye.

Sorry, no.

Quote
AR367 -> AR36/367?

Done (changes made to AR36 & AR367 too)

Quote
Quote
53: CR81 -> CR36/81

CR 36 & CR 81 intersect AR 53 at two (admittedly close but) distinct places.
You should probably move the point to CR36 then, since 53 traffic has to stop there.

Sure, why not.

Quote
Quote
59: move RigDr south to the I-540 overpass?
There's no graph connection to be made there, so I don't see a compelling reason to move it.
Why not make a graph connection? The I-540 exit is signed for 59 and nothing else on the main signs.

Okay, fine. Changed US 71 file as well.

Quote
94 continues north from AR340

Yes, but it's unsigned. (https://www.google.com/maps/@36.4979069,-94.1811717,3a,75y,66.65h,94.86t/data=!3m6!1e1!3m4!1sJGsvCqxVLaXb-XXC5cMU7Q!2e0!7i13312!8i6656)
That seems like splitting hairs, since traffic on 94 itself has no indication the route ends at 340.

Wouldn't that be true for almost any route that's partially unsigned?

Quote
Quote
183: 4thSt -> MilParkRd?

Both 4th St & Mills Park Rd are signed at that intersection, so why is one any better than the other?
Because the latter is a more important road.

Personal opinion. Neither of them are particularly important. The point exists because Bryan deserves a point somewhere, and there's a light at that intersection.

Quote
I drove that segment in 2018 and remember the signage being similar to the 2013 GMSV, although I did not check the westbound sign since I was driving the opposite direction.
So we have signage showing an overlap. The truncation should be reverted.

As I said, I only noticed that the signs heading north on 17 failed to mention the business route.

I'm still not convinced that the I-49 overlap is correct. There's signage on 12 itself (https://www.google.com/maps/@36.3551327,-94.122447,3a,27.9y,292.36h,86.72t/data=!3m6!1e1!3m4!1sCQRa-mFW3DPKI9gmD5s_5w!2e0!7i13312!8i6656) showing the surface alignment via 8th, while the only signs supporting I-49 are after you turn.

I'm not changing this.

Approaching AR 12 W from I-49 southbound: 2007 (https://www.google.com/maps/@36.335929,-94.1840933,3a,75y,187.07h,106.42t/data=!3m6!1e1!3m4!1s3LnuvnQvrssIg4osRCxtMg!2e0!7i3328!8i1664) vs 2019 (https://www.google.com/maps/@36.335908,-94.1841428,3a,75y,191.68h,82.98t/data=!3m7!1e1!3m5!1sSoQZJtpLN3SkX2ZNDNjq2A!2e0!6s%2F%2Fgeo3.ggpht.com%2Fcbk%3Fpanoid%3DSoQZJtpLN3SkX2ZNDNjq2A%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D105.74777%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192)

Approaching AR 12 E from I-49 northbound: 2008 (https://www.google.com/maps/@36.3557223,-94.1773997,3a,50.3y,33.67h,96.83t/data=!3m6!1e1!3m4!1suI9H_ZRIvF5r04S449LlHg!2e0!7i3328!8i1664) vs 2019 (https://www.google.com/maps/@36.3557263,-94.1774444,3a,33.8y,38.16h,88.78t/data=!3m6!1e1!3m4!1s2wKrQwYMOzaKALjUnlZTKA!2e0!7i16384!8i8192)

Quote
215: CR5261 -> CR5440 and move a bit east

The end is where the Johnson County map's Oark inset (http://www.arkansashighways.com/maps/Counties/County%20PDFs/JohnsonCounty.pdf) shows it.
However, there is an end state maintenance (https://www.google.com/maps/@35.6903016,-93.5714904,3a,42.8y,84.89h,78.53t/data=!3m6!1e1!3m4!1s2iW68TFA78urf56nkI8R1A!2e0!7i3328!8i1664) sign to the east.

Yes, in a photo that's 12 years old. The map was last updated in 2012.

Quote
282/US 71: LakeFortRd -> LakeSmiRd (https://www.google.com/maps/@35.6487311,-94.1603677,3a,46.3y,303.76h,84.57t/data=!3m6!1e1!3m4!1sQIHFPH6JNemnezPV0WC_xA!2e0!7i13312!8i6656)

Although "Ft" is small, it's on the sign.
Sure, but if we're dropping a word we should drop the small one. "If the cross road name has more than 3 words, use one of two options: 1. Pick out the two most important words besides the road type..."

Going with "LakeFSRd".

Is this everything you wanted to discuss? Anyone else have any thoughts?


https://github.com/TravelMapping/HighwayData/pull/3515 (https://github.com/TravelMapping/HighwayData/pull/3515)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 05, 2020, 06:19:22 pm
Quote
310eno ends a bit northwest of BayRd, maybe far enough for a separate End point

That GMSV is over 12 years old, so I'm going with the endpoint shown on the county map (http://www.arkansashighways.com/maps/Counties/County%20PDFs/FaulknerCounty.pdf).
The 2003 county map shows the same thing as the current one.

I just downloaded http://geostor-vectors.geostor.org/Transportation/SHP/ROAD_INVENTORY_ARDOT.zip and will have a look at endpoints like this when I get a chance. Here are a couple (310eno and 386tol):
(http://i.imgur.com/367a5xb.png)
(http://i.imgur.com/sSGjseO.png)

I don't know how authoritative this is, but it will at least provide another datapoint.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 05, 2020, 09:03:34 pm
US 49busbro: SchSt -> CR936 (https://www.google.com/maps/@35.9072409,-90.5772058,3a,24.2y,20.13h,79.07t/data=!3m6!1e1!3m4!1s1IjozsGeOthJ5jth9SNOYA!2e0!7i13312!8i6656)?
US 49bushel: move ColSt_N north half a block
US 49bushel: AR242_S -> AR242_W (https://www.google.com/maps/@34.5436,-90.6434196,3a,22.1y,186.32h,84.67t/data=!3m6!1e1!3m4!1sXOSwt8w3LNArWPBkOgX63g!2e0!7i13312!8i6656)? directional signage on 242 is inconsistent, also being west on "northbound" out of West Helena
US 49buspar: NorAve -> NorAve_E
US 49sprpar -> US 49ypar or US 49wyepar

US 62sprber: OakViewDr -> OakDr (https://www.google.com/maps/@36.3779894,-93.5731345,3a,20.3y,30h,87.32t/data=!3m6!1e1!3m4!1sj4ZwBrcWONo1pLQGeCuB7g!2e0!7i13312!8i6656)

US 63busjon is now an extension of 463 (points on 18 and 351sjo need renaming)
US 63busmar is now an extension of 149, probably ending at AR14/140 (points on 14, 140, 149, and 308 need renaming)

US 64busmcc is signed south from US 64 along 17, so extend it back and US64 -> US64_E
US 64buswyn: AR1 -> AR1/284

US 65bushar: LakDr -> LakeShoDr (https://www.google.com/maps/@36.227363,-93.1068465,3a,75y,156.24h,97.46t/data=!3m6!1e1!3m4!1s_JLeQmPyOc9ubZBq-D-cvA!2e0!7i13312!8i6656)
US 65buspin: US63_N -> US63/79_N
US 65buspin: move 2ndAve to the underpass
US 65spreud is unsigned :( so no change

US 67bussea: AR367 -> AR367_N
US 67sprwal -> US67ywal or US67wyewal

US 70bushot/270bushot: move SumSt just south and make it SumSt_S? as it is it doesn't really correspond to any intersection
US 70bushot: new point 1 at the Grand Avenue exit, then AR7S -> 2, MillCreRd -> 3, KelSt -> 4, WesDr -> 5, US70_E -> 6
US 70buslit: AshAve -> AshAve_E
Title: Re: usaar: Arkansas state highways
Post by: michih on January 06, 2020, 02:34:01 am
Anyone else have any thoughts?

Just this: http://travelmapping.net/devel/datacheck.php?sys=usaar to be checked and (most likely) marked FP on activation.
There are currently no NMPs: http://travelmapping.net/logs/nmpbyregion/ak.nmp Fine!
and NMPs should be checked before activation: http://travelmapping.net/logs/nmpbyregion/ar.nmp
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 06, 2020, 08:34:32 am
There are currently no NMPs: http://travelmapping.net/logs/nmpbyregion/ak.nmp Fine!
Wrong file: http://travelmapping.net/logs/nmpbyregion/ar.nmp
Title: Re: usaar: Arkansas state highways
Post by: yakra on January 06, 2020, 11:07:34 am
reply in progress
Title: Re: usaar: Arkansas state highways
Post by: mapcat on January 06, 2020, 02:20:20 pm
I'm holding off on the datacheck until I've finished all the edits.
Title: Re: usaar: Arkansas state highways
Post by: michih on January 06, 2020, 03:47:02 pm
I'm holding off on the datacheck until I've finished all the edits.

Sure, sorry! I was not aware that you've not yet finished editing. And I guess that it's not necessary to remember you moving AR151 and AR440 from usansf to usaar on activation. ;)
Title: Re: usaar: Arkansas state highways
Post by: mapcat on January 06, 2020, 06:28:34 pm
US 63busjon is now an extension of 463 (points on 18 and 351sjo need renaming)
US 63busmar is now an extension of 149, probably ending at AR14/140 (points on 14, 140, 149, and 308 need renaming)

Interesting. What's your source? Are they both signed?

Regarding your other usaus and usausb suggestions, those aren't part of usaar and so I will defer to Eric on those. He's reassuming collaboratorship of Arkansas once usaar is activated.

And I guess that it's not necessary to remember you moving AR151 and AR440 from usansf to usaar on activation. ;)

No, I don't think I'll forget that. I may be done editing but want to wait a few more days to see if there are any more suggestions. It looks like Eric is working on something.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 06, 2020, 08:31:24 pm
US 63busjon is now an extension of 463 (points on 18 and 351sjo need renaming)
US 63busmar is now an extension of 149, probably ending at AR14/140 (points on 14, 140, 149, and 308 need renaming)

Interesting. What's your source? Are they both signed?
Not sure about signage, but:
http://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mcrai_ras.pdf
http://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mpoin_ras.pdf
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 06, 2020, 09:53:52 pm
US 71busfay: I-49 -> I-49(85) since it junctions I-49 again
US 71busfay: I-49Fut -> AR549
US 71sprfay: NorBlvd -> GreSt (as the exit is signed both ways)
US 71sprfay: add a point at MallAve (https://www.google.com/maps/@36.1171211,-94.1475735,3a,17.5y,263.49h,88.34t/data=!3m6!1e1!3m4!1sQRDsOopNqIAhkCWUkwuJKw!2e0!7i16384!8i8192)?

US 79buscla: EwanSt_W -> EwanSt?
US 79busmag: AR19 -> AR19_S

US 82sprfel is unsigned :( so no change

US 270busmal: MainSt -> MainSt_N

US 412bushin: ValRd -> CR7295/8490 (https://www.google.com/maps/@36.1445431,-93.8627169,3a,15.4y,221.97h,83.98t/data=!3m6!1e1!3m4!1sbz3jh9ovvqI1c8Ds3vIahA!2e0!7i13312!8i6656)?
US 412byppar: US412 -> US412_E for futureproofing?
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 07, 2020, 02:39:20 pm
I-30: exit 131 westbound is for McDaniel Drive; is this worth adding as a separate point?
I-30: move 141A south to the AR 10 underpass?

I-40: move 1 west to the overpass
I-40: add 146 (https://www.thv11.com/article/news/local/maumelle/the-long-awaited-maumelle-interchange-opens-today/91-756fa554-7c3c-4368-823a-e6dfa78c0fd9)
I-40: move 150 west to the overpass
I-40: 152 -> 152B, add 152A?
I-40: add WhiRivRA (rest area between 193 and 202) since you can turn around
I-40: move 276 to where the Rich Road centerline would intersect?
I-40: move 279A east to the overpass

I-49tex: 29 -> 29A?

I-55: split 3 into 3A (at the frontage underpass or where 131 would hit I-55 if extended) and 3B (at US 70)?
I-55: make 72 an alt name for AR/MO? that's where State Line Road is

I-430: I-30 -> 129 (https://www.google.com/maps/@34.6685383,-92.4056696,3a,54.2y,158.76h,96.31t/data=!3m6!1e1!3m4!1s0-oreJKtK5ozHsT6GhjWCg!2e0!7i13312!8i6656), add 128 at the frontage road overpass

I-440: I-40 -> 138 (https://www.google.com/maps/@34.7135983,-92.264731,3a,75y,297.75h,85.37t/data=!3m6!1e1!3m4!1su-7t2ZsyDYlRtJaZq_BEYw!2e0!7i13312!8i6656)

I-630: 1 -> 139 (https://www.google.com/maps/@34.7344549,-92.266165,3a,75y,113.58h,99.57t/data=!3m6!1e1!3m4!1syGkaITFkFWrlBdSQvVbMvg!2e0!7i13312!8i6656)?
I-630: move 1A west to Main Street (signed destination in both directions)
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 07, 2020, 04:01:59 pm
44mar: add a point at PopSt (https://www.google.com/maps/@34.7673872,-90.757488,3a,35.5y,310.66h,84.06t/data=!3m6!1e1!3m4!1sIKMJBbiKgLVMpEhhXiCEVg!2e0!7i13312!8i6656), where the Great River Road turns

147: AR131_* -> AR131Hor_*, AR131 -> AR131Edm
Title: Re: usaar: Arkansas state highways
Post by: mapcat on January 13, 2020, 08:50:08 pm
44mar: add a point at PopSt (https://www.google.com/maps/@34.7673872,-90.757488,3a,35.5y,310.66h,84.06t/data=!3m6!1e1!3m4!1sIKMJBbiKgLVMpEhhXiCEVg!2e0!7i13312!8i6656), where the Great River Road turns

147: AR131_* -> AR131Hor_*, AR131 -> AR131Edm

https://github.com/TravelMapping/HighwayData/pull/3534
Title: Re: usaar: Arkansas state highways
Post by: radison on January 14, 2020, 11:11:48 am
359: US64_E -> US64_S, US64_W -> US64_N
It appears these are reversed.  Now the easternmost US-64 turn is now labeled US64_N, which is much further south than the previously labeled US64_W.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on January 14, 2020, 12:35:59 pm
359: US64_E -> US64_S, US64_W -> US64_N
It appears these are reversed.  Now the easternmost US-64 turn is now labeled US64_N, which is much further south than the previously labeled US64_W.

Thanks for catching that. Fixed in my fork.
Title: Re: usaar: Arkansas state highways
Post by: Markkos1992 on January 18, 2020, 11:49:39 am
I am linking the below topic as AR 12 is affected.

http://forum.travelmapping.net/index.php?topic=3484.0
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on January 18, 2020, 02:30:29 pm
The intersection of 264 and 265fay has been shifted west; OSM has the new location.
Title: Re: usaar: Arkansas state highways
Post by: neroute2 on April 01, 2020, 09:21:42 am
100nor is gone: https://www.aaroads.com/forum/index.php?topic=26647
Title: Re: usaar: Arkansas state highways
Post by: yakra on May 01, 2020, 02:40:31 am
I still have a hell of a lot of catch-up to do on this thread. :(

In the meantime, AR549 was already in use as an AltRouteName for I-49Tex. 3 of 5 .list files refer to I-49Tex rather than the Bella Vista bypass:
bickendan.list:AR AR549 4 35
dharwood.list:AR AR549 US71Bus RocDellRd
master_son.list:AR AR549 US71Bus RocDellRd
okroads.list:AR AR549 4 35
ovoss_old.list:AR AR549 4 28

We just never got hip to this because so far siteupdate does not account for AltRouteNames when Checking for duplicate list names (https://github.com/TravelMapping/DataProcessing/issues/316).

Recommend changing AR549 to AR549Bel.

Edit: Some pending error check enhancements (https://github.com/TravelMapping/DataProcessing/pull/320) will make this a fatal error in the siteupdate program.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on May 13, 2020, 03:29:01 pm
[Re US63Bus (Marked Tree & Jonesboro)]
Not sure about signage, but:
http://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mcrai_ras.pdf (http://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mcrai_ras.pdf)
http://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mpoin_ras.pdf (http://www.arkansashighways.com/Maps/Counties/County%20RAS/RAS%20Maps%20PDF/mpoin_ras.pdf)

There's no new GMSV at Marked Tree, so I'll punt on that. In Jonesboro, GMSV on the route from August 2019 still shows the 63B signs, and on I-555 from September 2019 still shows the exit signed for both 463 and 63B. The northbound I-555 sign is on the ground with some orange cones around it, so that might mean something. But until someone confirms the signage has changed, I'll leave this alone too.

EDIT: If the rerouting of US63 is confirmed in the field first, I'll make the changes based on that instead.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on May 13, 2020, 08:00:55 pm
I am linking the below topic as AR 12 is affected.

http://forum.travelmapping.net/index.php?topic=3484.0

The intersection of 264 and 265fay has been shifted west; OSM has the new location.

100nor is gone: https://www.aaroads.com/forum/index.php?topic=26647

Thanks for the updates. All are included in this, along with the datacheck and NMP FPs.

I'll give it a final look-over tomorrow and move AR151 & AR440 in, and activate then.
Title: Re: usaar: Arkansas state highways
Post by: yakra on May 13, 2020, 08:42:32 pm
AR980* "Arpt" labels should be changed
I'd still like to review, if not the routes themselves, the discussion in this thread. Sorry that I've still not gotten around to that. :(
Title: Re: usaar: Arkansas state highways
Post by: mapcat on May 14, 2020, 03:43:23 pm
AR980* "Arpt" labels should be changed
I'd still like to review, if not the routes themselves, the discussion in this thread. Sorry that I've still not gotten around to that. :(

https://github.com/TravelMapping/HighwayData/pull/3870

I'll hold off on activating until you're ready.
Title: Re: usaar: Arkansas state highways
Post by: jwood.ok on May 23, 2020, 02:20:23 pm
I saw there were changes to AR 12 out to the West, but the section from AR45 over to AR23 seems to have disappeared.  Was that intentional?
Title: Re: usaar: Arkansas state highways
Post by: mapcat on May 23, 2020, 02:42:14 pm
Nope, that was a copy-paste error on my part. Thanks for catching it. https://github.com/TravelMapping/HighwayData/pull/3909 (https://github.com/TravelMapping/HighwayData/pull/3909)
Title: Re: usaar: Arkansas state highways
Post by: yakra on September 28, 2020, 07:02:35 pm
Quote
140: the piece east of US 61 doesn't make much sense as part of the same segment, and it's mileposted from south to north, with signs both north (south end) and east (north end); maybe split as 140Osc
I'm almost convinced to go along with you on this one because of the irrational shape of the route, but it goes against the guidelines I set and may or may not be worth making an exception. Anyone else have an opinion?
Worth an exception, IMO.
https://historicaerials.com/location/35.704914/-89.966869/T1984/16
Sure, it's not definitive, but there's an implication that 140 was carried on Semmes Ave, with that segment later downloaded. This would explain the S->N mileposting.
This sort of makes AR140 more of a discontinuous route than something that's concurrent but poorly signed.

AR186: The end at AlixLn checks out per shapefiles. OSM has the road plotted too far north though; see Esri WorldImagery.
AR189Ham: Would also go with HamLim.

94 continues north from AR340
Yes, but it's unsigned. (https://www.google.com/maps/@36.4979069,-94.1811717,3a,75y,66.65h,94.86t/data=!3m6!1e1!3m4!1sJGsvCqxVLaXb-XXC5cMU7Q!2e0!7i13312!8i6656)
That seems like splitting hairs, since traffic on 94 itself has no indication the route ends at 340.
I get this argument. I see this sign (https://www.google.com/maps/@36.4978557,-94.1812821,3a,25.1y,66.76h,87.45t/data=!3m7!1e1!3m5!1s-JIPKNK5pYzLNDiUH13brg!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3D-JIPKNK5pYzLNDiUH13brg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D87.80858%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656) as another one of these (https://www.google.com/maps/@43.6635952,-70.2717096,3a,45.9y,242.86h,90.82t/data=!3m6!1e1!3m4!1snsBzRKsTSNyBicO0y1wquw!2e0!7i16384!8i8192). Like they're just not bothering to sign a lame-duck route that only ends in another 100 yards at the state line. I could go either way on this one.

252/US 71: why the point at BroSt?
@yakra? I have no idea.
blame (https://github.com/TravelMapping/HighwayData/blame/master/hwy_data/AR/usaus/ar.us071.wpt#L62) -> commit (https://github.com/TravelMapping/HighwayData/commit/020a70314ceade72e37bccb1e5ab6e3d921dae4c#diff-3669d064c0d7156198addd2e7143426dR62)
This is a recentering of the original location of the AR252_W waypoint, which per HistoricAerials appears to have been accurate back when usaus was first drafted.

AR310Eno: Coords look a bit off at BayRd, unless there's evidence the jct has been recently reconfigured.

Quote
331: OldAR247 -> Hwy247 (https://www.google.com/maps/@35.2506502,-93.0488131,3a,38y,237.04h,85.12t/data=!3m6!1e1!3m4!1s53vsa5DTyiLGemrIf96nMQ!2e0!7i13312!8i6656) or RivRd?
It's signed as "Hwy 247" and since AR 247 probably used that path in the past, OldAR247 seems appropriate.
Confirmed old AR247. (https://historicaerials.com/location/35.250666/-93.048792/T1993/15)
While I normally tend toward "OldUS40" (https://travelmapping.net/devel/manual/wayptlabels.php#olddesignation) style labels, I think this one could wibble its wobble the other way. The kicker for me is that this road is signed as "Hwy 247" rather than "Old Hwy 247", so the "Old Route 40" scenario doesn't quite kick in. Since the road has a current posted name, we don;t quite make it the the "make up a name using the former name" point.

AR380Ogd: US71 -> US59/71
AR530: OldSCRd_N -> OldSCRd, since only one is included (unless... are we considering this a local-road multiplex?)

With the truncation of AR12, I'd be on the lookout to periodically check GMSV for signage disappearing from US71Bus, I-49 & US62. Though it may not happen soon if it does. In any case, It'd be my problem if I'm resuming maint of AR after usaar goes live. :)
Title: Re: usaar: Arkansas state highways
Post by: yakra on November 17, 2020, 10:58:06 am
AR935-1: US79B -> US79Bus
Title: Re: usaar: Arkansas state highways
Post by: mapcat on November 29, 2020, 02:11:01 pm
Worth an exception, IMO.
https://historicaerials.com/location/35.704914/-89.966869/T1984/16 (https://historicaerials.com/location/35.704914/-89.966869/T1984/16)
Sure, it's not definitive, but there's an implication that 140 was carried on Semmes Ave, with that segment later downloaded. This would explain the S->N mileposting.
This sort of makes AR140 more of a discontinuous route than something that's concurrent but poorly signed.
Okay, 140 is split.

Quote
AR310Eno: Coords look a bit off at BayRd, unless there's evidence the jct has been recently reconfigured.
Fixed.

Quote
Quote
331: OldAR247 -> Hwy247 (https://www.google.com/maps/@35.2506502,-93.0488131,3a,38y,237.04h,85.12t/data=!3m6!1e1!3m4!1s53vsa5DTyiLGemrIf96nMQ!2e0!7i13312!8i6656) or RivRd?
It's signed as "Hwy 247" and since AR 247 probably used that path in the past, OldAR247 seems appropriate.
Confirmed old AR247. (https://historicaerials.com/location/35.250666/-93.048792/T1993/15)
While I normally tend toward "OldUS40" (https://travelmapping.net/devel/manual/wayptlabels.php#olddesignation) style labels, I think this one could wibble its wobble the other way. The kicker for me is that this road is signed as "Hwy 247" rather than "Old Hwy 247", so the "Old Route 40" scenario doesn't quite kick in. Since the road has a current posted name, we don;t quite make it the the "make up a name using the former name" point.
Fortunately, a new sign (https://www.google.com/maps/@35.2506364,-93.0488333,3a,75y,256.54h,80.89t/data=!3m7!1e1!3m5!1s_rw50uZNQ8ElP0m3voAsjA!2e0!5s20190901T000000!7i16384!8i8192) mysteriously appeared and solved the problem. OldAR247 -> RivRd.

Quote
AR380Ogd: US71 -> US59/71
Fixed.

Quote
AR530: OldSCRd_N -> OldSCRd, since only one is included (unless... are we considering this a local-road multiplex?)
That was my thinking.

Quote
With the truncation of AR12, I'd be on the lookout to periodically check GMSV for signage disappearing from US71Bus, I-49 & US62. Though it may not happen soon if it does. In any case, It'd be my problem if I'm resuming maint of AR after usaar goes live. :)
Just did a quick lookaround and there aren't any changes (2019 GMSV).

AR935-1: US79B -> US79Bus
Got it.

https://github.com/TravelMapping/HighwayData/pull/4354 (https://github.com/TravelMapping/HighwayData/pull/4354)
Title: Re: usaar: Arkansas state highways
Post by: mapcat on December 20, 2020, 04:30:13 pm
What’s left to do here? Besides the suggested changes to the usaus and usausb routes that I want to defer to yakra, I don’t recall any outstanding problems, so please post a reminder here (or bring up anything new you’ve noticed) so I can investigate. I’ll have time the week after Christmas to deal with anything that needs to be addressed prior to activation.
Title: Re: usaar: Arkansas state highways
Post by: yakra on December 26, 2020, 01:42:10 pm
My posts above take care of the last of my comments TMK.
Title: Re: usaar: Arkansas state highways
Post by: mapcat on December 27, 2020, 12:21:47 pm
With that said, and no further comments, this pull request will promote usaar to active: https://github.com/TravelMapping/HighwayData/pull/4430
Title: Re: usaar: Arkansas state highways
Post by: mapcat on December 27, 2020, 11:21:22 pm
And they're active now. Thanks to everyone for the help with developing this large, untidy system!