usaal: Alabama State Routes

[Eth]

AL134 wp US431_N and US431 wp AL134/173 should be synced (btw: why 173 in wp name?)

134 and 173 are concurrent, with 173 ending here. I think that's an artifact of 134 previously running through Headland on Church Street, as I seem to recall it doing maybe 10 years or so ago. (I used to drive this part of US 431 pretty frequently.)

Though by the same token, I suppose that also means AL134's waypoint AL173 should be renamed to AL173_N.

[michih]

The ones that do not get flagged is part of why I have been doing an overhaul of the routes in PA and DE.  I still have not touched HDX to this point.

Well, we use the nmp files for exactly this! HDX is used to visualize the NMPs. If there are unintended NMPs even more apart... I think Jim has offered to change the threshold to any desired value. E.g. creating al.nmp with a different threshold just for the check. It's surely quicker checking these point only instead of checking all points.

However, when I review a system, I check NMP file in HDX first, and do another round with checking that all "links" are indicated in HB. Checking all labels of all routes which should have links, that they really have them. If not, coordinates are different and are usually NMPs just with a bigger distance than our standard threshold. In addition, I use this manual check to figure out that the label names are complete - e.g. in case of more than one intersecting route.

There are many way. Just do it the way you think it's the best for you!

[yakra]

I think Jim has offered to change the threshold to any desired value. E.g. creating al.nmp with a different threshold just for the check.

Another possiblity is adding a commandline argument to use a custom threshold.

[michih]

There are some LABEL_SELFREF errors: http://travelmapping.net/devel/datacheck.php?sys=null&rg=AL

AL261 wp "CR17/52/91" -> "CR17/52"

[yakra]

I see some confusion on city suffixes when used to disambiguate multiple intersections with same-numbered routes. In these cases, Add a suffix with an underscore and those 3 letters. Otherwise, a plain "AL52Opp" or "US98Bro_E" would imply a banner of "Opp" or "Bro", or that they correspond to "AL52Opp" or "US98Bro" in the HB, of which we have none. (In usaal, only AL53Dot has a city abbrev + no banner.)
I ran a search to provide the "Good" examples:

Code: [Select]

yakra@BiggaTomato:~/TravelMapping/HighwayData/hwy_data$ grep _ AL/*/*.wpt | grep -v '_[NEWS] \|_[A-Za-z]\{4\}'
AL/usaal/al.al005.wpt:CR1_Wil http://www.openstreetmap.org/?lat=31.970868&lon=-87.642113
AL/usaal/al.al013.wpt:CR24_Wal http://www.openstreetmap.org/?lat=33.879301&lon=-87.635697
AL/usaal/al.al013.wpt:CR24_Col http://www.openstreetmap.org/?lat=34.730195&lon=-87.667809
AL/usaal/al.al041.wpt:AL136_C http://www.openstreetmap.org/?lat=31.465577&lon=-87.339839
AL/usaal/al.al079.wpt:CR33_Blo http://www.openstreetmap.org/?lat=33.947425&lon=-86.585242
AL/usaal/al.al079.wpt:CR33_Jac http://www.openstreetmap.org/?lat=34.863796&lon=-86.100765
AL/usaal/al.al095.wpt:CR47_Hen http://www.openstreetmap.org/?lat=31.406265&lon=-85.138239
AL/usaal/al.al095.wpt:CR47_Bar http://www.openstreetmap.org/?lat=31.779477&lon=-85.162776
AL/usaal/al.al133.wpt:AL157_Flo http://www.openstreetmap.org/?lat=34.801352&lon=-87.651082
AL/usaal/al.al134.wpt:CR55_Hen http://www.openstreetmap.org/?lat=31.354397&lon=-85.228457
AL/usaal/al.al145.wpt:CR42_Chi http://www.openstreetmap.org/?lat=33.014552&lon=-86.609226
AL/usaal/al.al145.wpt:CR42_She http://www.openstreetmap.org/?lat=33.122830&lon=-86.541892
AL/usaal/al.al157.wpt:CR24_Col http://www.openstreetmap.org/?lat=34.729741&lon=-87.634978
AL/usaal/al.al157.wpt:AL133_Flo http://www.openstreetmap.org/?lat=34.801352&lon=-87.651082
AL/usaal/al.al157.wpt:CR24_Lau http://www.openstreetmap.org/?lat=34.870770&lon=-87.692174
AL/usaal/al.al239.wpt:CR31_Bar http://www.openstreetmap.org/?lat=31.884053&lon=-85.503293
AL/usaal/al.al239.wpt:CR31_Bul http://www.openstreetmap.org/?lat=32.064024&lon=-85.669815
AL/usaus/al.us029.wpt:AL81_NB http://www.openstreetmap.org/?lat=32.423881&lon=-85.690092
AL/usaus/al.us078.wpt:CR35_Fru http://www.openstreetmap.org/?lat=33.730925&lon=-85.432756
AL/usaus/al.us080.wpt:AL81_SB http://www.openstreetmap.org/?lat=32.423388&lon=-85.690935
AL/usaus/al.us080.wpt:AL81_NB http://www.openstreetmap.org/?lat=32.423881&lon=-85.690092
AL/usaus/al.us090.wpt:I-165_End http://www.openstreetmap.org/?lat=30.699833&lon=-88.045866
AL/usausb/al.us098trkmob.wpt:I-165_End http://www.openstreetmap.org/?lat=30.699833&lon=-88.045866Underscores, and city suffixes. Looking good for the most part.

As an aside before moving on, I noticed the _SB and _NB examples, and looked into them. This defies the usual principle of tracing down the "median" of a couplet, and having one point on the intersecting route at that median. There'd be the occasional example for something with really whacked-out geometry, but this is overkill in a straightforward situation like this.
Suggest combining into one point at the existing point where the route traces cross, with AL81_SB as an AltLabel on US80.

Back to the suffix issue, here are the labels that turned up as something in need of attention.
It's possible that some items could have been left out of the search; anything where Alt, Bus, Byp, Trk, Spr or Con referred to a city.
al.al005.wpt: CR29Alb AL25Bibb_S AL25Bibb_N CR29Nau
al.al009.wpt: CR66San CR66Nee
al.al010.wpt: CR7Swe CR23Wil CR65Wil CR7Sau CR65But CR59Luv CR23Bar CR25Hen CR57Hen CR65Hen
al.al014.wpt: CR19Pic CR23Pic CR23Per CR6Per CR37Sel CR19Aut CR6Tal
al.al017.wpt: CR20Was CR34Was CR9Cho CR9Sum CR20Sum CR34Sum CR8Pic CR24Lam CR8Lam CR16Lib CR24Col
al.al021.wpt: CR12Esc CR10Mon CR26Wil CR12Low CR26Low CR7Mon CR29Elm CR10Coo CR49Coo
al.al022.wpt: CR45Dal CR45Chi
al.al025.wpt: CR16Hale CR49Hale CR16Bibb AL5Bibb_S AL5Bibb_N CR49She
al.al033.wpt: CR6Win CR6Law
al.al039.wpt: CR20Sum CR20Gre
al.al041.wpt: CR56Wil CR6Wil CR56Dal
al.al051.wpt: CR11Dale CR2Bar CR2Mac CR11Lee
al.al053.wpt: TN7Truck
al.al055.wpt: CR107Red_S CR107Red_N
al.al069.wpt: CR44Cla CR44Mar
al.al123.wpt: US231Ari
al.al134.wpt: CR1Lev
al.al171.wpt: CR35Ham
al.us011.wpt: CR10Cuba_S CR10Cuba_N CR27Sum CR2York CR19York CR13Liv CR12Liv CR20Epes CR21Epes CR76Bol CR20Bol CR131Eut CR67Ral CR10Fos CR59Tus CR6Arg CR31Cal CR81Col
al.us029.wpt: CR25Rome CR14Ple CR59Luv CR27Bul CR53Tan CR45Cot
al.us031.wpt: CR6Cas CR30Wal CR45Gre CR14Mon CR24Pin CR27Mon CR23Aut CR40Pin CR59Aut CR20Pyr CR23Mid CR59Ver CR24Coo CR47Cla CR50Tho CR42Jem CR33Min CR26Sag CR5Blo CR7Blo CR9Ban CR23Lac
al.us043.wpt: CR84Sal CR6Cor CR10Jac CR16Cla CR35Doy CR16Mar CR47Mar CR20For CR67Ral CR10Fos CR55New CR35Ham CR16Lib
al.us072.wpt: CR24Tus CR71Lau CR33Lim CR71Lim CR33Jac
al.us080.wpt: CR10Cuba_S CR10Cuba_N CR23Dal CR37Sel CR7Low CR23Low CR7Mon CR9Cal CR13Mac CR29Mac
al.us082.wpt: CR35Pic CR30Pic CR49Ref CR16Gor CR47Tus CR30Tus CR1Bib CR16Eol CR29Bib CR16Ada CR15Chi CR1Aut CR10Aut CR29Pra CR22Mon CR15Bru CR22Bul CR35Thr
al.us084.wpt: CR3Cho CR21Cho CR3Cla CR21Cla CR23Zim CR22Wha CR39Cla CR39Mon CR1Per CR23Mon CR15Bel CR35Mon CR43Her CR7Cov CR21Cov CR95Opp AL52Opp CR38Opp CR1Lev CR31Dale CR55Ash
al.us090.wpt: US98Bro_E US98Bro_W US98Mob_W US98Spa_E
al.us098.wpt: US90Bro_E US90Bro_W US90Mob_W US90Spa_E
al.us231.wpt: CR14New AL123Ari CR22Mon CR29Elm CR49Coo CR29Wat CR26Ash CR29Blo CR26Blo CR49Blo
al.us278.wpt: CR49Bea CR35Ham CR49Ham CR57Win CR77Nes CR45Che
al.us280.wpt: CR41She CR41Coo
al.us331.wpt: CR95Opp AL52Opp CR59Mon
al.us411.wpt: CR26Ash CR22Cen CR31Cen
al.us431.wpt: CR12Hen CR137Gle_S CR12Rus CR137Gle_N CR137Pit_S CR137Pit_N CR137Sea_S CR137Sea_N CR137Rus_S CR79Roa
al.us098trkmob.wpt: US98Bro_E US98Bro_W
I have some stuff like this in my regions I need to fix too. The US1Alt labels on ME US1 are a bit dodgy...

[kjslaughter]

Hey guys, I found a naming convention issue on AL 283.  Currently, the south end point is shown as BUS411, but to conform across the site, I think it should be US411BusCen with the route, then banner, then city 1st three letters.

[yakra]

Or just vanilla US411Bus, as that's the only branch of US411Bus that AL281 intersects.

Heh. The existence of that route looks a bit silly. I guess ALDOT must not be too fond of business state routes, AL21BusMon aside.

Speaking of AL21BusMon, Drewry Road has been relocated southward. In Esri WorldImagery, the scar left over from the old route is pretty freshly visible, heading into the current waypoint.
Suggest one waypoint at the new Drewry Rd intersection, and tweaking the existing waypoint to IvySt, which should be close enough for those who want to mark the old alignment.

[yakra]

The following labels all have a banner preceding numerals:
AL/usaal/al.al009.wpt: BUS411
AL/usaal/al.al013.wpt: US72/ALT72
AL/usaal/al.al014.wpt: BUS80/22
AL/usaal/al.al017.wpt: US72/ALT72
AL/usaal/al.al022.wpt: BUS80_E
AL/usaal/al.al052.wpt: BUS84_W
AL/usaal/al.al052.wpt: BUS231/431
AL/usaal/al.al052.wpt: BUS84_E
AL/usaal/al.al053dot.wpt: BUS231
AL/usaal/al.al068.wpt: BUS411_W
AL/usaal/al.al283.wpt: BUS411
AL/usaus/al.us029.wpt: TRK29_S
AL/usaus/al.us029.wpt: TRK29_N
AL/usaus/al.us031.wpt: ALT72_W
AL/usaus/al.us031.wpt: ALT72_E
AL/usaus/al.us043.wpt: US72/ALT72
AL/usaus/al.us072.wpt: US43/ALT72
AL/usaus/al.us080.wpt: BUS80/22
AL/usaus/al.us080.wpt: BUS80/41
AL/usaus/al.us082.wpt: TRK29
AL/usaus/al.us411.wpt: BUS411_W
AL/usaus/al.us411.wpt: BUS411_E
AL/usausb/al.us084busdot.wpt: BUS231/431
AL/usausb/al.us231busdot.wpt: BUS84
AL/usausb/al.us231busdot.wpt: BUS431_N
AL/usausb/al.us431busdot.wpt: BUS84
AL/usausb/al.us431busdot.wpt: BUS231_N

[Griffith]

AL 14 actually crosses I-65 at exit 181 and goes down Fairview Ave. to US31 than proceeds south to US82. I drove it yesterday.

[neroute2]

I'd argue that CR6Cas CR30Wal CR45Gre CR14Mon etc. is the correct way to disambiguate same-numbered routes in multiple counties (assuming those are county name abbreviations). If disambiguation isn't necessary...probably don't.

[formulanone]

Finally realized there was a standardization guide all along... 
http://travelmapping.net/devel/manual/wayptlabels.php

I'd argue that CR6Cas CR30Wal CR45Gre CR14Mon etc. is the correct way to disambiguate same-numbered routes in multiple counties (assuming those are county name abbreviations). If disambiguation isn't necessary...probably don't.

I agree.

Not sure how to go about very similar county names on the same route; US 280 passing through Talladega and Tallapoosa Counties might be the only issue for Alabama, and road names exist for the most prominent of that route category.


How should Alternate US 72 be denoted in shorthand? Many routes show ALT72, but "US72Alt" follows the format.

AL 9
CR66San -> CR66Elm (Elmore County, instead of minor place name)
CR66Nee -> CR66Clay (Clay County, instead of minor place name)
BUS411 -> US411Bus (only crosses US 411 Business once, don't need to mention the town of Centre)

Hey guys, I found a naming convention issue on AL 283.  Currently, the south end point is shown as BUS411, but to conform across the site, I think it should be US411BusCen with the route, then banner, then city 1st three letters.

AL 13
CR22 -> CR22_N
CR22Spr -> CR22_S (same road and county; both unnamed, labelled "22")
US72/ALT72 -> US72/72Alt (or is that redundant...thoughts?)
RoyalAve -> RoyAve
CourtSt - > CouSt

AL 14
MLKDr -> MLKingDr

AL 17
RoyalAve -> RoyAve
CourtSt - > CouSt
CR22Spr - > CR22Fra (located in Franklin County; same point as above in AL 13 - though 2 different CR22s in AL 17's HB)

[formulanone]

AL 20 and US72AltDec
Would recommend two points be added...one for each route
JefSt (Jefferson Street in Courtland) >>  https://www.openstreetmap.org/#map=18/34.67948/-87.35273
 - Leads to west end of town, former alignment of US 72Alt/20.

AL 21
MontRegAir -> MonRegAir

AL 22
Just drove this route last weekend through Maplesville - looks like AL 22 now goes though Foshee Avenue, following the Truck Route on GSV. There's no "AL 22/139 Truck" on ALDOT. Unfortunately, no camera, no proof, so this might have to wait.

AL 24
OldAL24 -> CR460 (signed that way, also used as a consistent description for points on AL 33 and AL 101)
*OldAL24Red -> Eliminate, doesn't point to anything, and not labelled as such. Perhaps use Winnie Frost Road (WinFroRd) instead?

AL 33
US72ALT/20 -> US72Alt/20

[formulanone]

AL 34
CoveAceRd -> CoveAccRd (street sign is spelled properly according to GSV, incorrect in OSM and Google Maps...or just use CR332)

AL 35
PineRidRd -> CR835 (as this is Old AL 35, preserve continuity with other side of old alignment, which should probably also have a point)

Not sure if CR44 is necessary, doesn't lead to much.

Would recommend a point for Airport Road (AirRd), as it's traffic-light controlled and rather busy (from experience). The little airport isn't busy, but the route serves as a defacto bypass to US 11.

[froggie]

Note to self that AL 180 has been turned back east of AL 161 per the January 2019 Baldwin County Milepost Map (which incidentally retains AL 135).

(EDIT). I'll need to fix AL 149 as well.

[michih]

http://travelmapping.net/devel/datacheck.php?rg=AL

AL5 long underscore
AL261 label slashes
etc.