Author Topic: usaar: Arkansas state highways  (Read 46321 times)

0 Members and 1 Guest are viewing this topic.

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #45 on: December 05, 2019, 09:43:07 am »
Also, re: AR36 - should be split in two. ADOT maps and GMSV 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 shows an overlap. Maybe treat the stub west of 367 as a separate segment?

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #46 on: December 05, 2019, 10:09:17 am »
364: CR225 -> CR225/251
364: AR1/1B -> AR1 (1B begins along 364)
365 is mileposted from north to south; should it be reversed?
365: WiseRd -> DexEnt?
365: AR100_S -> AR100Nor, AR100_N -> AR100Mau
89/365 has a single isolated ramp to I-40 west
366abe: OakLn -> End
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
367: CR55 -> CR55/208
367: CR70 -> CR70/76

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #47 on: December 06, 2019, 02:38:28 pm »
368: MainSt -> CR27?
369: AlbPikeRA -> End? 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? this point is also misplaced
376 around Camden is mileposted in the reverse direction of the old 7 portion, but several signs 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
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 and should be reversed
385jud: US67/167 -> US64/67?
386: ArkDeptCorr -> WriUnit (or ArkDepCor?)
386tol: maintenance continues northwest to the sharp curve per mileage
387cam is mileposted from north to south; should it be reversed?
387cam: End -> CR47?
388: ArkDeptCorr -> CumUnit (or ArkDepCor?)
390 is mileposted from east to west; should it be reversed?
390: where does the CorEngRd name come from? rename LowLakeArea?
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?

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #48 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?

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #49 on: December 06, 2019, 04:15:32 pm »
935-1 is signed 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 :( 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

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?)
980rec: CR428 -> CR428_W

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #50 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? 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?
US 59/71: HomAve -> HorAve
US 59/71: FraRd -> CR3?

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

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: usaar: Arkansas state highways
« Reply #51 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)."

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, and included in the Clinton city and Van Buren county maps.
« Last Edit: December 12, 2019, 12:56:25 pm by yakra »
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #52 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

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1627
  • Last Login:March 26, 2024, 09:50:25 am
Re: usaar: Arkansas state highways
« Reply #53 on: December 30, 2019, 04:06:04 pm »
Highways 1-100 are done: 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 uniformly refers to DeSoto Blvd so I settled on DeSotoBlvd for both routes.

11: StiLetRd -> LetRd?

I went with RoyNewRd (opposite road at intersection) 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 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.

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 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

For the street names that don't match up with OSM, I was using the Arkansas Spatial Data Infrastructure Map Viewer. 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?

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 (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" 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

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

US 425 was once AR 13.

Quote
35: CR56 -> RyeCutRd?

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

Also, re: AR36 - should be split in two. ADOT maps and GMSV 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 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

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 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

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

Quote
88alt: LockDamRd -> HarLockDam?

ASDI names it Lock & Dam Rd.

94 continues north from AR340

Yes, but it's unsigned.
« Last Edit: December 30, 2019, 07:32:17 pm by mapcat »
Clinched:

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #54 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 (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" 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.

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1627
  • Last Login:March 26, 2024, 09:50:25 am
Re: usaar: Arkansas state highways
« Reply #55 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 (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" 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.
« Last Edit: December 30, 2019, 08:08:51 pm by mapcat »
Clinched:

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: usaar: Arkansas state highways
« Reply #56 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, 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
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
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 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 -> commit
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1627
  • Last Login:March 26, 2024, 09:50:25 am
Re: usaar: Arkansas state highways
« Reply #57 on: January 02, 2020, 07:30:57 pm »
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 that might say George Rd.

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

118/US 64: SprRd -> SprHillRd

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?

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

combine 135 and 135par

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?

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 shows it ending at Alix Ln.

Quote
187: BeaParkRd -> DamLakeCamp?

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?

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

You meant  WalTr. The point on 371 was not in use, so I replaced it with a shaping point.
Clinched:

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #58 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?

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 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.
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 (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" 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.
« Last Edit: January 03, 2020, 11:00:27 am by neroute2 »

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 976
  • Last Login:Today at 01:57:37 am
Re: usaar: Arkansas state highways
« Reply #59 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 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.

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 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 showing the surface alignment via 8th, while the only signs supporting I-49 are after you turn.