usala: Louisiana State Highways

[neroute2]

3287 is also on the same district map (and is in GIS), running from 700 east to 343 on Gladu Road. http://wwwapps.dotd.la.gov/engineering/lettings/lets8230.aspx lists it for tentative repaving later this year. Could it be that these 870-* control section numbers are temporary routes for repaving?

Others I can find:
870-10 LA 3192 MP Cutoff (Moreauville-Plaucheville)
870-21 LA 3271 Bad Eye Road south of Farmerville
Neither appears on other sources.

[mapcat]

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

1: ToLA8 -> LA8Spr (it's signed as LA 8 and inventoried as LA 8 Spur per GIS)

Other spurs are signed as spurs. This is not, so it either should be ignored, or go in as another LA 8. Thoughts?

Your readme lists a bunch of spurs that are not signed as spurs: 631, 655, 758, 1077, 1194, 3000, 3100.

Those all have signs on the routes themselves. LA 8 is only signed along LA 1, which according to the GIS, is not LA 8. Based on the sign northbound at the junction with LA 1 directing LA 8 onto the spur, I suppose I can add it.

2: US79Trk_S -> US79Byp_S: it's signed as TRUCK BY-PASS 79 and inventoried as 79 Bypass in GIS and RTP

Since it's specifically a truck bypass, I'm not convinced it's worth changing.

Why do you think it's specifically a truck bypass? It seems more likely that it was originally signed (or planned to be signed) as a plain bypass, but truck plates were added to direct trucks that way. If they wanted it to be a truck route they'd sign it as a truck route (e.g. the one in Minden). Note the difference in styles for US 79 and 9: it's NORTH TRUCK BY-PASS 79 but TRUCK NORTH 9.

There are different styles, yes, but following your logic it should be the truck route of "Bypass 79".

10: I doubt LaioRd is the correct name. Google shows it as the name for not just that short dead end but also for LA 10, and it has the looks of a TIGER error (LA10 somehow became LAIO).

Okay, maybe, but what other name would you give it? The GIS calls it Laio too.

https://atlas.geoportalmaps.com/ptcoupee calls it Balley-Hack Road.

The point isn't necessary for anything but shaping, so I replaced it with a hidden point.

10vil: UniPkwy -> LA467 per GIS and signage

467 does not show up on the "right size" map from 2017, which is newer than GMSV there.

That GSV link is June 2019. This is probably the 467-1 you mention in your readme.

The imagery was still 2016 when I edited the file. Added the point as LA467 and created a new Fort Polk segment of 467.

47/I-510: there seems to be no signage (other than a mile marker) taking I-510 south of exit 2C. And according to GIS, I-510 begins at the exit 2C gore, not the end of the bridge. Delete I-510_S from 47 and LA47_S from I-510?

I believe that the south end of I-510 is included under the "unsigned interstate" rule (and even if it shouldn't be, there's that mile marker, and no "End" sign), so I'm leaving the end there. GIS calls it I-510 all the way to where we end it. As far as I can tell, the end of the bridge is at the exit 2C gore (northbound).

The one point per interchange rule applies here.

Except the endpoint isn't part of an interchange.

107: HwyCutOff -> 115CutRd?

Changed to 107-115Cut which was closest to what was on the signs (Hwy 107-115 Cutoff Rd).

111: BonRd -> YvoBonRd?

GIS says it's just Bonner. Nothing in GMSV.

112: StrCroRd -> StrCro?

GIS calls it unnamed, so going with ESRI again.

113: McNCutOff -> McNCutRd

The sign has a space in Cut Off.

116: RanRd -> EslAF?

Using GIS name (Range Rd) since there is more than one entrance to the airport.

118: KisMoraRd -> End? I don't see any intersecting road

It's the name of the road that continues east of 118's end.

125spr is missing a file.

It's unsigned.

129: PoolRd -> PooRd? It looks like it's Poole Road, which makes sense since it serves Poole's Processing.

The GIS says Pool Rd.

129: LA565_E -> LA565_S, LA565_W -> LA565_N? I don't see any directional plates but it's diagonal and odd numbers generally seem to go north-south in Louisiana

This seems to indicate it's signed South-North, so agreed.

131: needs another point for shaping; RTP shows a proposed state highway at what both OSM and Google call DA Biglane Road, but this is currently a minor dirt road

Actually it's paved, and it goes to an airport, so it works.

151: LA545_W -> LA545_S? it's signed north-south at LA146 (but east-west at LA545_E)
151: LA837_W -> LA837_N, LA837_E -> LA837_S? it's signed north-south at I-20(101)

LA 151 is signed northbound heading toward the north away from both I-20 junctions, which means you can't apply normal N-S route rules to it. For the points in between, I'm treating it like an E-W route.

153 is missing LA1265 http://www.openstreetmap.org/?lat=32.017892&lon=-93.079112 (which needs field checking of signage, though Esri WorldImagery shows it has been rebuilt)

I added a point there (FiveForRd) but will hold off on creating a file for 1265 until signage is confirmed.

163: GorRd -> PRsomething?

My vision evidently is no better than yours, so since the GIS and the street blade say it's Gorton Rd, that's at least not wrong. I changed it to GorRd_S since there are two intersections with it.

175: per GIS and RTP, LA5_W -> LA5, LA5_E -> OldSR5, but this needs field checking

I agree it can wait.

182: LA178_W -> LA178_N, LA178_E -> LA178_S

182 is signed E-W, so I'm leaving these alone.

182: MLKingBlvd -> DrMLKJrBlvd

Yes, but that name is too long.

182: US90BusMor_E -> US90Bus/662 or just LA662_W (signs here give US90Bus a hanging end)

No, its E end is signed at US90.

182: GIS and RTP show that 653 has been extended back west to meet 182 east of LA3087; this needs field checking

November 2019 GMSV shows that the purported extension is still a private drive. The reference in the GIS dates to 2017.

182-2: StPorSt -> StDePSt

The manual suggests dropping propositions such as "de" in street names.

182-2: move the east end northwest to StEtiRd?

The interchange with US90 and LA 182 is under construction in the most recent imagery (March 2019), so it's not clear to me where 182 exits 90, which would determine where 182-2 ends at 182. I left this alone for now but the whole construction area deserves another look once GMSV is updated.

[mapcat]

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

316: BayBlueByp -> BayBlueRd (or BBBypRd?)

For Bayou Blue Bypass Rd, I don't see how either is any better than the other, so I'm leaving it alone.

319: where does the BayLn name come from?

ESRI. Changing it to VerBayLn since GIS and ESRI agree on that, and Bayview Ln may be a private drive.

336-1: per GIS and RTP the west end is at RaiSt

The GIS was edited last week, and now it appears that the end is LA 31, which is consistent with 2019 GMSV.

354 is missing:
LA341 http://www.openstreetmap.org/?lat=30.334537&lon=-91.918670
LA31 http://www.openstreetmap.org/?lat=30.353379&lon=-91.894476

Per the GIS, it's now an extension of 341.

378: IsleCapBlvd is part of the I-10 interchange, so delete? though it's signed both ways from the I-10 west offramp, so maybe not

That was my intention for including it.

384 is signed east-west at LA27 but east-west the opposite way at LA3092. Keep as is?

That's the only way I could think of to handle it.

[mapcat]

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

401: OldLA400 has a name but I can't make it out

Me either, but the GIS calls it Old LA 400 so there's nothing wrong with that.

402: per GIS and RTP the west end is now at End http://www.openstreetmap.org/?lat=29.952945&lon=-91.099555 ; this needs field checking

Well, there was no field check for the former w end, which was probably also based on the GIS at the time, so the new location is fine.

417 is signed as if there's no gap, and per RTP there are plans to take over the gap. So combine the two?

That imagery is from 2011 (and the sign was there in 2008 as well) so it's debatable whether it's indicating imminent future plans or just a mistake. I'd appreciate a field check before combining the segments.

427 has been deleted between LA3064 and LA3246 per RTP, GIS, and April 2019 GSV, so split it in two
427 has also been deleted between LA42_E and the parish line per RTP and GIS, but May 2019 GSV still shows shields, so this needs field checking

GIS shows it deleted between 3064 and the parish boundary (part of this relinquishment dates back to 2017 per GIS edits), so I'll leave the deleted part of the southern segment in for now, but give that segment the suffix since it's likely to be the shorter one eventually.

429: LA44_N -> BurAve_N? see discussion with 44, and maybe split into two 429s?

As I did with 44, I'll leave this alone for now since June 2019 imagery at the western/northern 44/429 junction still has 44 signs.

430sprfra is mostly signed as plain 430, and GIS shows it as such, so treat the spur signs as remnants and merge the two?

For now I'll leave it. The spur was signed as mainline 430 back in 2014, and the most recent imagery of the 430/Spur 430 junction is that same year, so it needs field checking.

469's real south end is at End http://www.openstreetmap.org/?lat=31.139651&lon=-93.148586 per GIS and RTP; +X103442 can be removed

The GIS was updated in January, and June 2019 GMSV shows the end here now

480: DalRanRd -> End?

It ends east of an intersection, and the GIS calls the road that continues on Dalton Ranch Rd. Are you saying that 480 is also called Dalton Ranch Rd there?

481/191: OldLA539 -> OldHwy539

But when it was Hwy 539, it was LA 539, no?

491: add End http://www.openstreetmap.org/?lat=31.597952&lon=-92.841269 and delete RRLevRd

The GIS shows it going past the end of the pavement all the way to the road on the levee.

493: USFS339 -> FR339?

It's signed FS339.

498 is signed east-west, so reverse it

It is, but signed such that the west end (US 71 frontage road) is southeast of the east end (I-49), so the order is correct.

[mapcat]

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

519: GapFarmRd -> GapFarRd??

The GIS has no name for the road, but there's a business on it called Gap Farms Travel Center, so ESRI probably has it wrong.

523: move LA526 to the connector?
526: move LA523 to the connector?

I like making the graph connections when they're this close.

531: PR173 no longer has a shield, but it's still on the street sign (MimsGroRd)

More recent imagery shows the shield.

545 is signed north-south, so LA151_W -> LA151_S and LA151_E -> LA151_S

See comments for LA 151. 545 is sometimes signed N-S, sometimes E-W, which is why even you got confused when suggesting the new names.

568: OldLA568 -> ChuLn_W per GIS, ChuLn -> ChuLn_E
568: move MisAve southwest to HigPl?
568: US65_N -> US65_E or US65 or US65_Gol

I used MisAve since it's where a 90° turn takes place. And I don't see any directional signage on 568, so I'm leaving it as a N-S route since it parallels US 425 or 65 for its entire length.

577sprind now ends at End http://www.openstreetmap.org/?lat=32.290801&lon=-91.474062 per GIS and RTP; this needs field checking

Most recent GMSV is from 2009 so it definitely needs field checking. However I noticed that the existing point was still likely incorrect, so I moved it to the first westbound sign, which coincided with where the pavement began (and matches a section break in the GIS).

579: PanRd -> PanLakeRd

I don't know how you're getting Panther Lake from that image. The GIS says Panther Rd so I'd want to see some more evidence besides a nearby lake called Panther Lake.

588: RivRd -> End?

I don't see anything that tells me the rest of 588 is called River Rd, so no change.

593: add a point at PR10, a planned state highway per RTP

Let's wait until the new highway materializes. It's not needed for shaping.

593: BoatDockRd is a parking lot; move to BusParkRd?

The GIS gives it that name, and although it's not particularly important (it's there for shaping), it does serve a boat dock, whereas BusParkRd appears to serve about 4 trailers.

594: add a point at KanLn, a planned state highway per RTP
596: add a point at SchLn, a planned state highway per RTP

Neither is needed for shaping, so I'll wait.

602-1: signs point 601-1 [sic] west from I-20; should 602-1 be extended to the south frontage road? this may need field checking

The GIS has it extending south but still ending within the interchange, or barely outside; I'm comfortable leaving this alone (1PPI) unless field checking indicates signs south of the eastbound exit ramp.

655 is cut back to only the part from LA655Spr (-> MainSt or MainSt_Loc) to LA308 and 655sprloc is gone; this needs to be field checked

Both 655 and the spur are signed (as 655) from LA 1 in November 2019 imagery; the references in the GIS were changed in Februrary 2019.

693 is gone per GIS and RTP, but was still signed in May 2018 GSV. So this needs field checking.
694: LA693 is gone per GIS and RTP, but was still signed in May 2018 GSV. So this needs field checking.

I'll wait for the field check.

[michih]

448: OWMatRd -> O&WMatRd?

This should be undone. & is an invalid character.

https://travelmapping.net/devel/datacheck.php?rg=LA

[yakra]

clarify LABEL_INVALID_CHAR description #566

[rlee]

300: FireStaRd is too far northwest and should be at http://www.openstreetmap.org/?lat=29.859911&lon=-89.776127
A bit of 300 has been closed. Split into 300 and 300StB?

I rode out to the end of LA 300 at Delacroix by bicycle today. It's a different way to mostly clinch a highway! LA 300 may have to be split into three pieces.
- Closure #1 is west of LA 1245. The road has been fully removed with small cul-de-sacs built on either side. Our bicycle group used a single track of gravel/shell on the south side of the highway to go around the closure. Link here
- Closure #2 is between here and here west of the storm surge barrier near the LA 46/300 eastern junction. The eastbound lane was sliding off into the swamp, so the stretch through the swamp had been closed with signage and barricades. Our group rode around the barriers. From Google, you can see where DOTD had restriped the highway to one lane one way westbound due to the road problems.

[rlee]

625 is unsigned no change

LA 625 is signed on the LA 46 end... barely. One sign on LA 46 EB. LA 625 is not signed on the dead end side. I have the bigger photo if it is needed.

[mapcat]

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

I rode out to the end of LA 300 at Delacroix by bicycle today. It's a different way to mostly clinch a highway! LA 300 may have to be split into three pieces.
- Closure #1 is west of LA 1245. The road has been fully removed with small cul-de-sacs built on either side. Our bicycle group used a single track of gravel/shell on the south side of the highway to go around the closure. Link here
- Closure #2 is between here and here west of the storm surge barrier near the LA 46/300 eastern junction. The eastbound lane was sliding off into the swamp, so the stretch through the swamp had been closed with signage and barricades. Our group rode around the barriers. From Google, you can see where DOTD had restriped the highway to one lane one way westbound due to the road problems.

Thanks for investigating. LA300Ken (Kenilworth) added.

448: OWMatRd -> O&WMatRd?

This should be undone. & is an invalid character.

https://travelmapping.net/devel/datacheck.php?rg=LA

Got it.

625 is unsigned no change

LA 625 is signed on the LA 46 end... barely. One sign on LA 46 EB. LA 625 is not signed on the dead end side. I have the bigger photo if it is needed.

Thanks! Added.

787: ChaCanRd -> PR126? what's the character at the end?

Hard to say. Another leg of PR126 is signed PR126S, so I moved the point to the intersection with that one.

793: End -> PRsomething?

The GIS doesn't show anything there, so whatever it was, it seems to have been vacated.

798-3 ends with a full loop on Beech-Chestnut-Maple, but this is unsigned

Right, there's no signage at all at the west end, so I ended it at the first turn.

799 is more north-south; flip it?

Since it's identical to the US 80 truck route, I kept the points in the same order.

810: NorLn -> NorDr?

GMSV is still blurry, but GIS calls it Hogan Rd so I'll switch to HogRd

938: LA44 -> BurAve? see discussion under 44

Leaving as-is for now.

964: move End southwest to the first railroad crossing per GIS

The GIS has it going a little further than that, so I extended it to the end of the center stripe

That's everything through LA999.

[mapcat]

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

1035-1 and 1035-2 end about 2/3 of a block north of OhioSt (and become 3283-4 and 3283-6 there) per GIS and RTP
1035-1: LA1035-3 -> LA1035-3/3283-2 and LA1035-4 -> LA1035-4/3283-1 (needs field checking)
1035-2: LA1035-4 -> LA3283-1 (needs field checking)
1035-3: LA1035-1 -> LA1035-1/3283-2 (needs field checking)
1035-4: LA1035-1 -> LA1035-1/3283-1 and delete LA1035-2 (needs field checking)

2019 GMSV on LA63 doesn't show the 3283-X's, so I will hold off on all changes to the 1035-X's until both sets can be field checked (anyone going to Livingston anytime soon?)

1042: per RTP and GIS the east end is now at LA37; this needs field checking

GMSV is still from 2016, so this will need to wait also.

1056: WilRd -> EarlWilRd or MtPisRd?

GIS calls it Wilkes Rd, and (ancient) GMSV shows no sign.

1061: add FriChuRd http://www.openstreetmap.org/?lat=30.790604&lon=-90.363171 , a planned takeover per RTP

LA 1061 is posted as extending north from the north end of LA 1054 to LA 38.

Signage at LA 38: https://goo.gl/maps/2nubJ7VDJngj1SRB8
Signage at LA 1054/1061: https://goo.gl/maps/Ez7Q8kNFi8bPpYtd8 (green/white signs have been replaced with black/white signs)

Extension added. I'll wait on the FriChuRd until the new route is signed; the point isn't useful for shaping and in between two points that are less than 2.5 miles apart.

1111: LA1112_* -> BayPlaRd_* per GIS and RTP; needs field checking
1112 is gone per GIS and RTP; needs field checking

Since GMSV still hasn't been updated, I'll wait for confirmation.

1123: VieTerBeau_W -> TerBeauRd_W?

It's not clear why one would be any better than the other.

1138-1: AveAub -> AveLAub? ConPkwy? LA3088?? this needs field checking to see if Contraband Parkway was built and signed as LA 3088

Contraband Pkwy has been built but as of 2019 was not signed. The GIS isn't calling it LA 3088.

1181: delete LevRd, add End http://www.openstreetmap.org/?lat=30.952659&lon=-91.915317 per GIS and RTP

Currently the GIS is showing it ending at Levee Rd.

1203 is signed along state-maintained FroRd from US 165, but this may be a case of a missing TO plate

If it's missing it's been missing for over 11 years and a sign upgrade. I'll add the extension.

1250: US167/107 -> US167 or US167/28? (signs say to 107)

I believe that 107 and 1250 both end at the frontage road/Wadley St intersection.

There's also a TO S 107 here which tells me that 107 doesn't end at 167. I will add a shaping point to 107's northernmost segment to break the false concurrency along 167.

1257: End -> CheSP?

There's a State Maintenance Ends sign a bit beyond the road the GIS calls State Park Rd, so even though the GIS shows the end to be at that road, I'll keep it where it is for now.

1265 needs field checking, but aerials show it's been realigned and paved, so it's very likely that it's signed:
End http://www.openstreetmap.org/?lat=32.004191&lon=-93.096213
LA153 http://www.openstreetmap.org/?lat=32.017901&lon=-93.079101

I'll wait for the field check before adding.

That's everything except the 3000s.

[Duke87]

Per field check this week, LA 3151 is not signed.

[mapcat]

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

3018: WesExpy -> US90Bus (or WBankExpy; if the name is kept the same should be done on 3017)

Changing it to WBankExpy since 3017 has a graph connection with US90Bus while 3018 does not (it ends at the frontage roads).

3019 appears to be unsigned so should be deleted unless I'm missing a sign somewhere

Here it is.

3056: RivRd -> PRsomething?

GMSV hasn't been updated there, so it's still too blurry to read.

3081: move I-59 to the underpass?

There should be a graph connection, and the underpass is 3/8 mi away from the ramps (both directions), so I'll leave this one alone.

3124's new south end is at BogLim http://www.openstreetmap.org/?lat=30.751481&lon=-89.849474 per GIS and RTP; this needs field checking

Signs are absent from LA 21 as of 2018 GMSV, so it's definitely been shortened, but Bogalusa's southern limits have changed per OSM (GIS is not working) so it's possible that's not still the southern end. I'll wait for the GIS to confirm.

Per field check this week, LA 3151 is not signed.

Thanks. Deleted and points preserved as HumRd_N & _S.

3154 cuts between Hickory and Dickory at 9th per GIS and RTP, but southbound traffic has to use the route as shown, so I don't know how to handle this; maybe just one point at MouSt?

Since Dickory is expected to be extended to LA 48 eventually, we need a point at 9th St (current south end of Dickory) more, and since the route takes Hickory southbound and Dickory northbound between 9th & Gardner, I made those the endpoints of the split segment (GarSt is former DicSt_S). FWIW, nothing is signed southbound on that segment, so it's possible that 3154 actually follows Dickory southbound anyway, even though it's impossible to take one-way 9th St to reach Hickory at that end.

Furthermore, I think it's important to note the former routing between Hickory and Dickory.

3159 is gone per GIS and RTP; this needs field checking

Waiting for field check.

3174: OldUS190 -> Old190Rd

As I've done with others, if the road name indicates the former routing of another route, I'll name it after the route.

3205: MainLineRd -> OldOakRd?

GMSV doesn't show a sign, and Esri WorldStreetMap tends to be more accurate than OSM in the state, so I'll stick with what it has.

3218 continues east to the actual bridge structure per GIS and RTP, so extend it east to End at the barricades

Esri imagery shows something built in the right of way between the end and the barricades, so without a field check it's hard to guess where it actually ends now. The difference is about 250 feet, so seems negligible to me.

3272 is a new route east of Arcola, from LA10 north to VerTownRd. Wait for a field check?

Yeah, there's nothing on GMSV yet.

3281's west end is at the wye just to the southeast per GIS

The center lines end at Bayou St, though, and that's the more natural end, so I'll leave it there.

3283-* in Livingston need field checking to see if they're signed

Agreed.

3287 is also on the same district map (and is in GIS), running from 700 east to 343 on Gladu Road. http://wwwapps.dotd.la.gov/engineering/lettings/lets8230.aspx lists it for tentative repaving later this year. Could it be that these 870-* control section numbers are temporary routes for repaving?

Others I can find:
870-10 LA 3192 MP Cutoff (Moreauville-Plaucheville)
870-21 LA 3271 Bad Eye Road south of Farmerville
Neither appears on other sources.

Only 3287 remains in the document (which has been updated since you checked it). Neither 3192 nor 3271 appear in GMSV but deserve field checking. I'm leaving all of these out for now.

That's all from the reviews of the 3000s.

Tying up loose ends from previous comments:

LA 39: since I never heard back from the local government and it's not particularly important, I changed the PR15_* points to Hwy15_*.

LA 182-2: GMSV still dates to 2019, so I can't confirm any signage change.

I think that's everything!


2/11 edit to restore links that mysteriously disappeared.

[formulanone]

1069: LA430/430Spr -> LA430? see discussion under 25 and 430

I didn't see any LA 430 "Spur" banners in Franklinton area last June and July. Everything seems to either point to LA 430 and LA 25 or LA 436 on the south end.

1056: WilRd -> EarlWilRd or MtPisRd?

Street blade only says "Wilkes Road"; here's a not-very-good photo from July 2020:

[mapcat]

1069: LA430/430Spr -> LA430? see discussion under 25 and 430

I didn't see any LA 430 "Spur" banners in Franklinton area last June and July. Everything seems to either point to LA 430 and LA 25 or LA 436 on the south end.

1056: WilRd -> EarlWilRd or MtPisRd?

Street blade only says "Wilkes Road"; here's a not-very-good photo from July 2020:

Thank you! 430Spr will be merged into 430 in the next update.