usaal: Alabama State Routes

[froggie]

US 43 is not concurrent with I-359.  It follows the service roads.  This is why I did things the way I did.  Though under 1PPI I could arguably truncate 359 to 15th.

[Markkos1992]

Yeah I did not think about that, but you are right.  One thing to mention about your last update is that an updates entry is needed for the deletion of US 231 BUS in Ozark.  I presume that you overlooked it due to updates not being needed for the AL Routes since they are still in preview.

[mikeandkristie]

I think something weird just happened with AL 41.  It looks like the US80_E point got moved causing a weird zigzag through Selma at the northern end.  Attaching a screenshot.  I think it moved from the green arrow up to the red arrow.  So, it shoots up to US 80 going around the north of town and then back down to the next point almost mirroring the business route.  I spotted it when I saw our mileage jump on AL 41.  We went around Selma on US 80 and not through town which is how I spotted it.

Mike

[yakra]

I'm with michih on the 29/80/81 item. The midpoint of the couplet can just be collapsed into a single point with US29_S (that's the one that has the graph connection with AL81 anyway), call it US29/81 maybe, and give it whatever AltLabels it needs.

[michih]

• Are US231, US411 and AL23 wps in Ashville intended? I think so, let me know and I mark it FP.

Yes, this is another crazy situation where the routes follow the long way around the courthouse block.  This should be a FP.

• AL176 has two shaping points +x02 and +x03 close together. Is it intended? If so, I can mark it FP.
• Same at AL25 +x25 and +x26, intended?

Yes.  In both of these cases, I was trying to avoid the "sharp corner" error due to the switchbacks on both routes (especially 176).

• AL167 wps AL/FL and CR9 seem to be intended too. Mark FP?

Yes.  Here, the intersection is not at but is just north of the state line...too far away to consider both one-and-the-same.

NMPs marked FP: https://github.com/TravelMapping/HighwayData/pull/5670/commits/56bee5f8a8e3435d534fbb94b667c407955c1eae

[SSOWorld]

US 43 is not concurrent with I-359.  It follows the service roads.  This is why I did things the way I did.  Though under 1PPI I could arguably truncate 359 to 15th.

Should we move beltway 8 off the Sam Houston Tollway in Texas then?

[mapcat]

• Removed BUSINESS 231 in Ozark.  2019 GMSV shows no more signage along 231.

Premature? I drove it last week, and it's still signed in Ozark, although the signage is still missing along US 231.

[formulanone]

I think something weird just happened with AL 41.  It looks like the US80_E point got moved causing a weird zigzag through Selma at the northern end.  Attaching a screenshot.  I think it moved from the green arrow up to the red arrow.  So, it shoots up to US 80 going around the north of town and then back down to the next point almost mirroring the business route.  I spotted it when I saw our mileage jump on AL 41.  We went around Selma on US 80 and not through town which is how I spotted it.

Mike

I just saw that, too.

https://travelmapping.net/hb/showroute.php?units=miles&r=al.al041

Looks like the point was accidentally connected to AL 22 instead of at US 80, as before.

[froggie]

• Leaving 80/29/81 as-is.  Someone going from SB 81 to WB 80 would not have that "graph connection" to 29.
• Fixed the bad coordinate on 41.
• Clarified the northern endpoint of I-359 as 15th St under 1PPI.
• Signage isn't "missing" on 231 for the Ozark business route.  Per an upthread commenter, it has been removed.   I interpreted this as the business route no longer exists.  As that commenter also noted, remaining signage in Ozark can be explained by the fact that cities in Alabama are not unlike Tennessee (or Mississippi) when it comes to (lack of) removing old/outdated signage.

[Markkos1992]

I am linking to this post related to AL 59 here since I think it got lost in the shuffle (https://forum.travelmapping.net/index.php?topic=4817.msg26957#msg26957).

[froggie]

^ In the queue.  I did lose it in the previous shuffle.  Not a big enough change to where I feel the need to do more than just update the intersection coordinates.

[Markkos1992]

I'll post any further comments I have for Alabama in this post for now.  It may be a few days (if not longer) until I finish updating everything in my list file.  (I will probably also do a general post for MS later as well, but obviously that is super low priority.)

I-65:  I think that 260A should be 261D.  Also 260 maybe should be 260B.

I-165:  I think that US90/98Trk is a better label for the south end than plain US90.  I try to avoid using truck labels for the most part (especially with how often truck routes appear and disappear in PA), but using plain US90 here implies to my brain that there is no concurrency with I-165.

I-459:  23 needs to be recentered. (added 4/26/2022)

US 11:
1.  BlkWarPkwy>-JoeMalPkwy.  (also affects US 43)
2.  AcadDr>-AcaDr.  (also affects AL 5)
3.  VisLandPkwy>-AlaAvePkwy (also affects AL 5)
4.  CentSt>-CenSt.  (also affects US 78)

US 31: 
1.  I-459(13B)>-I-459.  (added 3/31/2022) 
2.  BroMedCenDr needs to be shortened.
3.  The ALT72 labels should be US72Alt instead.  (added 6/29/2022)

US 43/AL 69:  9thSt should be StiBlvd.  Could UnivBlvd be shortened to UniBlvd?

US 45: 
1.  PleAv>-PleAve 
2.  I-65(8 )>-I-65.
3.  BelRd>-UniBlvd.
4.  AL17_N>-AL17.  (since for TM purposes we are not considering AL 17 as concurrent with US 45)

US 78: 
1.  Should CR12_W and CR12 be merged into one point?  (also affects AL 5)
2.  PrattHwy should be PraHwy.  (also affects AL 5)
3.  8thAveBir>-8thAve (also affects AL 5)
4.  24thSt>-24thSt_S.

US 82: 
1.  CR47_Tus>-CR47.
2.  CR30_Tus should maybe be RiceMineRd as I did not see any CR 30 shields in the area.  I did not look at the other CR 30s.
3.  CampusDr>-CamDr.
4.  I-59(73)>-I-20/59.  (added 3/31/2022)

US 90:  I-65(1)>-I-65.  (added 4/5/2022)

US 278: I-59(183)>-I-59.

US 280: I-459 (19)>-I-459.

US 431:
1.  EBroadSt should at least be shortened.
2.  I-59(183)>-I-59.

AL 5:
1.  FinBlvd>-AL378.
2.  I-22(85)>-I-22 (added 3/31/2022, only one interchange between AL 5 and I-22)

AL 217:  HigBlvd>-UniBlvd.

AL 261:  CR17/52/91 needs to be shortened.

AL 269: 
1.  5PoiWestAve, NewMulLoopRd, AllShoCreRd, and PumCenCutOffRd should be shortened.
2.  AdaEnsRd>-CR65.

[ntallyn]

I saw some signs for AL4 in downtown Birmingham this weekend. I'm assuming it's not included in the HB because it's completely concurrent with US11 or US78?

[formulanone]

AL 66 All good.

AL 67
US72ALT/20_W -> US72Alt/20_W
US72ALT/20_E -> US72Alt/20_E
CR41-> DanRd (Like Madison County, Morgan County rarely posts county roads, most shields do not exist.)
CR35 -> EvaRd


 

[formulanone]

AL 14
BUS80/22 -> AL22/80BusSel

AL 68
411BUS -> US411BusCen
...or use US411_N for consistency, because US411_S is in use?

AL 69
US43 -> US43_A
CR20/48 -> CR20 (no CR48 signage visible, only 20)
US43_S -> US43_B
CR44_Mar (I think this is an unnecessary point)
US43_N -> US43_C
5thSt -> RiceMineRd (consistent with AL 297 and with signage on US 82)
Recommend adding a point for MouPkwy, just north of CR50 in Moundville, which is a direct route to a point of interest.

AL 70, AL 71, AL 73
All good.

AL 74
The standalone portion is fine, but do we care about the 165-mile concurrency with US 278?

AL 75
For Albertville: Recommend removing OneCutOffRd, but including nearby Turnpike Road, a busier road.

AL 76
all good

AL 77
CR53 -> CR053 (this might be signed "053", as per most Chambers County signage, but can't tell from GSV)
...otherwise, all good.

AL 79, AL 81
all good.