usaal: Alabama State Routes

[mapcat]

AL 176-199 review

AL 176, 177, 178, 179, 180, 185, 186, 187, 189, 191, 192, 196, 198, 199 all fine

AL 181
SheHigRd -> CR24

AL 182
StaParkRd2 -> CamRd per Gulf State Park map
some more points at beaches may be helpful

AL 183
NorSt -> CR12
CR33 -> CR20 (change on AL 5 too)
MatMooRd -> CroRd (that's the road that's signed there)

AL 184
CR48 -> CouLineRd

Truck 185 exists, as well as Truck 10 (both follow AL 245)

AL 188
W end is at the End State Maintenance sign (next to the Waffle House) per the ALDOT county map, but signage at I-10 does not mention that segment
move CR19 to center of roundabout
CR23 -> PadSwiRd

AL 193
CR22 -> CR 20
LauRd -> LauRd_W
N end is at End State Maintenance sign (Hermitage Rd) per county map, but like AL 188, the signs stop where the point currently exists

AL 195
CR25 -> RoseHillRd
CR23 -> CR3434

[froggie]

I've begun doing peer review edits, going back to the first batch that formulaone began 5 years ago.  For this first round (pull request submitted just now), I've gotten through about halfway on page 9 of this thread.  A handful of things I'd like to point out in response to some of the peer review suggestions:

• AL 15 is now signed through Andalusia (confirmed via recent GMSV) where it is not concurrent with US 29 (AL 15 is primarily the hidden state route for US 29).  So I've added the standalone portion through Andalusia.  No AL 100 shields yet.
• GMSV shows a single AL 300 reassurance shield departing from US 11/43.  Given precedent, I've added AL 300 to the system.
• Per ALDOT milepost data, mainline AL 22 was realigned in Maplesville onto the former TRUCK AL 22.  So the latter route is now removed.
• The *OldAL24Red point on AL 24 is because that's where the four lane ended for many years and old AL 24 contined into Red Bay proper.  It's intended for those users (like me) who traveled AL 24 before the Red Bay bypass was built.  Utilizing such points where alignments change after the route list is originally made is a long-standing policy and the asterisk is meant to highlight those "change" points.
• Some of the points I chose (like CR44 on AL 35 or CR265 on AL 51) are intended as shaping points, but following another long-standing policy of using active points instead of hidden shaping points where feasible.
• The AL 48/GA 5 border point is in the correct location, per field review and GMSV.  It's the map companies that show the state border as slightly off its actual location.  There may be a few others like this.
• A false positive will be needed on AL 50 at "Old280Rd".  That's the actual name of that road per street blades.
• I don't remember if it had been requested or not, but UseSt on AL 52 (and US84BusDot too) is a waypoint in use.  Presumably as a connection to Range St (which underpasses AL 52/BUS 84).  As it's an in-use waypoint, I'm not removing it.  That said, the Range St point is indeed useless and not being used so I'm removing that.

[froggie]

Second round of peer review edits has been submitted.  Have gotten up to AL 133 now, so into mapcat's comments.  Some specific responses, primarily for F-1 and/or Mapcat since they provided the majority of peer review comments:

• It was suggested to add Truck US 98 to the US 90 label at I-165's endpoint.  I opted not to because I already have 2 hidden labels in use at that point and I am loathe to add a third.
• Leaving 5thSt on US 43/AL 69 as-is because the road is signposted as such on both sides of 43/69 and is a point-in-use.
• I have not included AL 4 because signage is somewhat inconsistent and it's completely concurrent with US routes or I-22.  If there was a clear segment that it was consistently signed along, I'd be open to include it given precedent next door in Georgia.
• Since F-1 brought it up, same deal with AL 74's concurrency along US 278.  It does appear that there is signage along the 278/74 concurrency now.  Does that signage go all the way to the Georgia line?  Doing a quick GMSV check, 74 appears to be signed as far as Double Springs but not in Cullman.
• McDRd on AL 86 is actually in the correct spot.  If you look at satellite imagery, the road was relocated to the west of the creek.
• On AL 105 near Ozark, the existing CR36 point is primarily for shaping purposes, but following the aforementioned policy of using waypoints where feasible.  I don't see a need for that CR 36/39 point at the present so a directional suffix isn't required.
• I'm a little confused about AL 304.  Project information I've found suggests it's supposed to run between US 31 and I-65, but the reassurance shield photo F-1 posted upthread is east of I-65.  How far east is it supposed to go?
• RE: AL 14 in Eutaw.  What we have in the browser is correct as of 2014, but it does appear that sometime after I created the lists, ALDOT rerouted AL 14 to follow the route as described by vespertine.  I've fixed this, though in the process I also had to tweak US 11 around the county courthouse.  I'll need to keep more existing points than I'd like to b/c they're in use and at least one user list will be broken on AL 14 but it can't be helped.
• Added TRUCK AL 10 and TRUCK AL 185 (both in Greenville).
• Extended AL 118 west concurrent with US 278 per signage as reported by mapcat.
• Mapcat mentions a small stub off of AL 129 connecting to AL 241, which is also signed as vanilla AL 129.  It's intended as the connection between 278 West and 129 North.  I'm not sure how (or if at all) to incorporate it.

[rickmastfan67]

• Mapcat mentions a small stub off of AL 129 connecting to AL 241, which is also signed as vanilla AL 129.  It's intended as the connection between 278 West and 129 North.  I'm not sure how (or if at all) to incorporate it.

'Named' segment of AL-129?

Did something similar to that with FL-295.
https://travelmapping.net/hb/showroute.php?units=miles&r=fl.fl295&lat=30.425826&lon=-87.272998&zoom=16
https://travelmapping.net/hb/showroute.php?units=miles&r=fl.fl295wpe&lat=30.425826&lon=-87.272998&zoom=16

[rickmastfan67]

Just gonna throw this in here, a few AL threads in the main area that should also be addressed so they can be finally marked as solved.

AL 4 signage
AL: US98/US90 incorrectly formatted waypoint labels "I10*"
AL: I-85 southern end now has an exit number (0)

[froggie]

^ I have deleted the two that have already been addressed.

[michih]

Just gonna throw this in here, a few AL threads in the main area that should also be addressed so they can be finally marked as solved.

AL 4 signage
AL: US98/US90 incorrectly formatted waypoint labels "I10*"
AL: I-85 southern end now has an exit number (0)

^ I have deleted the two that have already been addressed.

None of them is "marked solved" though.

[rickmastfan67]

Just gonna throw this in here, a few AL threads in the main area that should also be addressed so they can be finally marked as solved.

AL 4 signage
AL: US98/US90 incorrectly formatted waypoint labels "I10*"
AL: I-85 southern end now has an exit number (0)

^ I have deleted the two that have already been addressed.

None of them is "marked solved" though.

These are the 2 he removed:
https://forum.travelmapping.net/index.php?topic=4307.0
https://forum.travelmapping.net/index.php?topic=6447.0

[mapcat]

AL 201-225 review

AL 201, 202, 207, 208, 211, 213, 221, 225 all fine

AL 204
ReeMillRd -> ReaMillRd

AL 205
OldGunGadRd -> OldGunRd (per signs)
PhiDr -> BeuCutRd
MainSt -> MainSt_E
SolRd -> RabTownRd (the only road with a sign)
OneCutOffRd -> OneCutRd
PleGroRd -> PleGroRd_S

AL 210
FortSt -> ForSt

There's a Truck 52 following AL 210 on the south loop

AL 212
AL111 -> BriSt_E
remove segment east of that point

AL 215
35thSt -> 10thAve (35th has a new name, if you like that better) (it's long)
15thSt -> 15thSt_W

AL 216
KeeMillRd -> CR32
BraSt -> CR93
RocBraRd -> CR109
ALJctRd -> AlaJctRd

AL 217
HigBlvd -> UniBlvd
NewRd -> CR31

AL 219
SheHugRd -> SheHueyRd
BarRd -> BarCemRd (per sign)

AL 223
CR8 -> CR8_W
CR22 -> CR22_W


I'll try to finish the rest this weekend.

[mapcat]

AL 227-269 review (won't get the rest until tomorrow)

AL 229, 233, 237, 247, 253, 259, 261, 263 all fine

AL 227
DuckSprRd -> Eto/Dek
AubCarrSceDr -> LakeGunSP

AL 235
ForHillDr -> ForHilDr
CR203 -> PlaRd

AL 239
MidSt -> MidSt_S
CR31_Bar -> CR31 (see below)
CR14_E -> CR35
CR14_W -> CR14
CR31_Bul -> CR31_E (CR31 continues west on Daniel Rd)

AL 241
add a point for the short AL 129 connector if you don't draft a file for it

AL 243
CR69 is unsigned, and has no name in the ALDOT GIS (or in the low-functionality county GIS), but CR6 is the next road north and it is signed

AL 245
ConSt -> CR45
NewSeaRd -> CR41 (same for Truck 10 and Truck 185)

AL 248
East end is probably okay (ALDOT GIS agrees it's at the gate, but the mileage figure on county map places it inside Fort Novosel at the Red Cloud Rd/Andrews Ave split)

AL 249
Signage places the north end at Enterprise Rd, so it should have a short concurrency with AL 27

AL 251
LinLn -> CR63 (and recenter in the roundabout)
CR109 -> LimRd
CR96 -> WooSprRd
CR103 -> GatRd

AL 255 (in usansf)
add point for Mid City Way north of Bradford Dr (separate ramp)

AL 257
CR41 -> BurAcrRd
extend north end to Marina Dr per ALDOT GIS and county map (N end of Duncan Bridge)

AL 265
AL56 -> CR56

AL 269
NewMulLoopRd -> NewMulLp
AllShoCreRd -> ShoCreRd (per signage)
PumCenRd -> CR61
CR61 -> CorGorRd

[mapcat]

AL 271-759 review

AL 273, 279, 289, 291, 293, 295, 297, 300, 301, 302, 378, 382, 759 (in usansf) all fine

AL 271
TayRd -> UniCt and recenter point on intersection

AL 277
CR96 is now barricaded, so switch to CR579 or the entrance to the Google facility.

AL 281
CheStaPark -> CheSP
CR24Con -> CR24
FR500 -> CR500

AL 283
CR22_Che -> CR22
US 411/Business 411 in Centre are signed Truck 411/US 411. Some of each are unbannered but I never saw a Business sign.

AL 285
Technically it's not in the state system within the park, but it's signed as if it is so I agree with how it's drafted.

AL 287
Signs north of I-65 in both directions show it ending/CR 47 beginning roughly 1/4 mile north of the interchange.

AL 605
AL605_S & _N -> US231_S & _N

Review complete.

[rickmastfan67]

US 411/Business 411 in Centre are signed Truck 411/US 411. Some of each are unbannered but I never saw a Business sign.

https://forum.travelmapping.net/index.php?topic=6447.0

[froggie]

Submitted my next batch of edits, up through AL 182 (and not AL 172 as I mistakenly put in the pull request).  Some specific comments/responses:

• Left CR21 on AL 147 as-is because that is the road name AFAICT.  It doesn't help that there are no shields or streetblades on the AL 147 side but there is a CR 21 shield on the Waverly end.
• On AL 148, the reason for the FR603 point is to break up a 10+ mile segment with a minimum of intervening shaping points, because of the winding nature of 148 through Talladega National Forest.  FR603 appears on ALDOT's Talladega County map for the road south of 148, so given the lack of signage at the intersection (not uncommon for parts of rural Alabama), I used that designation.
• The reason I have AL 110 end at AL 126 and not I-85 is because that's its endpoint per ALDOT Milepost Maps.  Yes, AL 110 is signed off of I-85 but that's probably to reduce driver confusion.  Worth noting that both Atlanta Hwy and the "southern leg" of AL 126 were US 80 prior to 2010 so that played a factor as well.  When US 80 was relocated onto I-85 that year, AL 126 took over instead of AL 110.
• On AL 154, leaving CR44 as-is because there's a CR44 reassurance shield just west of the intersection.
• On AL 171, instead of Shamblin Rd, I'm using Shamblin Cutoff as that's what the road is signed as on Rose Blvd and I intended this point as the connection between AL 171 and Rose Blvd.
• Added TRUCK AL 28 and TRUCK AL 41, both in Camden.

[froggie]

The final round has been submitted.  Once that's ingested, I don't see anything else preventing us from activating usaal.

• Added TRUCK AL 52 Dothan.
• ALDOT defines the western terminus of AL 188 as being 0.126 miles north of the I-10 centerline, or at the northern edge of the I-10 interchange right-of-way.  This technically puts it just south of the entrance to TA.  Between it officially being within the interchange footprint, plus signage showing AL 188 south and CR 11 north, I've opted to keep it simple and leave the waypoint at I-10.  Similar definitions exist for AL 193 and a handful of state routes that end along I-85.
• On AL 195, leaving CR23 as-is as that's what it's signed as from AL 195 and is also labeled as such on the Winston County map.
• Per ALDOT's Dale County Milepost Map, when AL 27 was relocated off of Enterprise Rd, AL 249 was truncated to US 231.  My guess is the signage just hasn't been "collected" yet.
  
• The north end of AL 271 is the way it is because it's not actually at the University Court intersection.  It's defined as 0.5mi N of the I-85 centerline, which puts it where signage and the pavement change show...just south of University Court.
• On AL 283, CR22_Cen is labeled as-is to match the US 411 list...there are multiple CR22 points on US 411.
• AL 287's northern end is another of those cases where, when a state route ends at an interstate, the route technically ends at the far edge of the Interstate right-of-way.  I've generally used the "1PPI" principle in these cases.
• Mentioned upthread and in another thread, but given the inconsistent signage of TRUCK US 411 vs. vanilla US 411 in Centre, and in an effort to avoid having to break lists as much as I can, I'm leaving things in Centre as-is.  ALDOT's Milepost maps, while updated regularly, are generally useless when it comes to US routes because they use the underlying state route.  ALDOT's Cherokee County map clearly shows BUS US 411 and vanilla US 411, but hasn't been updated in 15 years.  When/if ALDOT submits a request to AASHTO to realign US 411 through Centre versus around it, I'll re-review things.

[rickmastfan67]

Just wanna mention these here too, but there's a few datacheck errors on the US highways in AL still that need to be addressed on the currently active data:

Code: [Select]

al.us029 CR25_Rome LONG_UNDERSCORE This is always a true error and cannot be marked false positive.
al.us031 CarBlvd VISIBLE_HIDDEN_COLOC al.us280@+CarrBlvd al.us031;CarBlvd;;;VISIBLE_HIDDEN_COLOC;al.us280@+CarrBlvd
al.us084 CR13_Avon LONG_UNDERSCORE This is always a true error and cannot be marked false positive.
al.us084 CR31_Dale LONG_UNDERSCORE This is always a true error and cannot be marked false positive.
al.us280 5th/6thAve VISIBLE_HIDDEN_COLOC al.us031@+5th/6thAve al.us280;5th/6thAve;;;VISIBLE_HIDDEN_COLOC;al.us031@+5th/6thAve
And here's the ones in the usaal system:

Code: [Select]

al.al025 CR16_Bibb LONG_UNDERSCORE This is always a true error and cannot be marked false positive.
al.al025 CR16_Hale LONG_UNDERSCORE This is always a true error and cannot be marked false positive.
al.al025 CR49_Hale LONG_UNDERSCORE This is always a true error and cannot be marked false positive.
al.al050 Old280Rd LACKS_GENERIC al.al050;Old280Rd;;;LACKS_GENERIC;
al.al069 +x19 HIDDEN_JUNCTION 3 al.al069;+x19;;;HIDDEN_JUNCTION;3
al.al069 CR222 DUPLICATE_LABEL This is always a true error and cannot be marked false positive.
al.al106 CR1/106 LABEL_SELFREF NO_COLOC al.al106;CR1/106;;;LABEL_SELFREF;NO_COLOC
al.al110 CR2,CR7_N VISIBLE_DISTANCE 10.65 al.al110;CR2;CR7_N;;VISIBLE_DISTANCE;10.65
al.al126 AL126 LABEL_SELFREF NO_SUFFIX al.al126;AL126;;;LABEL_SELFREF;NO_SUFFIX
al.al126 AL126,AL126_E DUPLICATE_COORDS (32.369817,-86.13948) al.al126;AL126;AL126_E;;DUPLICATE_COORDS;(32.369817,-86.13948)
al.al210 US431_S,US231_S DUPLICATE_COORDS (31.190575,-85.401567) al.al210;US431_S;US231_S;;DUPLICATE_COORDS;(31.190575,-85.401567)
The only one in the usaal system that doesn't need to be addressed, is the one on AL-110, as that one automatically disappears when a system is activated.