usafl: Florida State Highways

[rickmastfan67]

US 27: 138thSt -> 138thStExt
US 27: I can't verify the RecRd name; county GIS says the west side is Service Road (a name shared with many other tiny roads) and the east side is SR 84 Ramp
US 27: DeemCity -> HolLandWMA and move north

The 'RecRd' name I think came from Google back in the day to be honest.  Even the 'HERE' maps have that name currently.  So, I'll leave it as-is for the moment.

The other issues listed above have been fixed.

US 27: what does CR17_Lak stand for? hopefully not Lake Placid, since there are two CR 17 intersections closer to it
US 27 -> US98_E -> US98_S, US98_W -> US98_N
US 27/98: FaiDr -> CR634_E, CR634 -> CR634_W
US 27: LibRd -> WilLakePkwy

CR17_Lak: Probably.  Still, now changed to 'CR17_Hig' to match 'county name' on shield instead.
FaiDr -> CR634_E: That CR634 shield is an error one.  On the road itself (right after the intersection with US-27/98), it's posted as CR634A. So, going with the label of CR634A instead, and leaving the 'CR634' label in US-27/98's files as-is.

The other issues listed above have been fixed.

US 27: recenter US441_S
US 27/441: 132ndStRd -> 92ndLp? a similar change was made on 35
US 27/301/441: 92ndPlaRd -> 92ndPlRd
US 27/301/441: BroSt -> Bro (or delete?)
US 27: US301/441_N -> US301/441?

BroSt deleted in all 3 files as it wasn't in-use.

The other issues listed above have been fixed.

US 27: BadRd -> MapSt (could be moved north to CR138)
US 27: CR354 -> CR354/405
US 27: CR53 -> CR53/534
US 27: CR1543 -> CR1543/2195
US 27: CR1555 -> FraBlvd? it's not signed here
US 27: PeaRd -> PeaFarmRd?
US 27: DorCalRd -> ToGA111 or CR157

MapSt: Kept, & added CR138.
CR1555: It is signed.  Just was hidden a bit below the overpass @ the intersection of Franklin & Lafayette.
DorCalRd -> ToGA111 or CR157

US 29: do the CR95A* tags need fixing?

Looks fine to me to be honest.

[rickmastfan67]

US 41: ShaVLRd -> ShaVal? the street name is not signed, and the loop is no longer open to car traffic
US 41: DCTAirp -> DCT&TAir
US 41: 5thAve -> 5thAve_W

DCTTAir instead, as I don't think we have any labels with a '&' in them.

Others tweaked.

US 41: is 1stSt the same interchange as FL80/82?

I would say they are different interchanges here because of the SB having the at-grade intersection with FL-80/82.  So, no change here.

US 41: CR867A -> DelPraBlvd (not signed here)
US 41: CR762 -> TucGra (not signed here)
US 41: LazyRivRd isn't signed and might only be the road inside the gate; move east to DeLeonDr?
US 41: CR777 -> RivRd (not signed here)
US 41: VilPkwy -> WVilPkwy

CR762 is signed. There is an 'END' shield in StreetView from '16, and you can still see it from US-41 in Aug '19.  So, no change on that one.
LazyRivRd -> DeMirAve instead.

All others changed.

US 41: move US301_S closer to the overpass?

Nah. Mainly since US-41 has an intersection with 17th Ave W right after the split, but before the overpass.

US 41: CR672 -> BigBendRd (not signed here)
US 41: BirSt -> BirdSt
US 41: US98_W -> US98_N, US98_E -> US98_S
US 41: CR40/484 -> CR40/336/484
US 41: CR18 -> CR18_W, add CR18_E?
US 41/129: CR6_E -> CR6 (but keep FL6_W; there's an overlap)
US 41: CR148 -> 86thBlvd

CR40/484 -> No change.  We don't have more than 2 routes in a label. At least as it stands, CR's on both sides of the intersection are mentioned.
CR18 tweaks make, and also added to US-441's file.

All others have been fixed.

======

These, and the post right above this have now been submitted.
https://github.com/TravelMapping/HighwayData/pull/3845

[rickmastfan67]

US 90: HydeParkRd is off
US 90: CR189 -> CR189_S, GalCut -> CR189_N
US 90: KingLakeRd -> KinLakeRd
US 90: CR181 -> CR179A/181
US 90: AciDr -> ACIDr
US 90: CR269 -> MainSt (not signed here)
US 90: BrySt -> StaDr

All above fixed.

US 90: CR157 -> MacSt (not signed here)
US 90: FL53_S -> FL53/145
US 90: CR141 -> MyrSt (not signed here)
US 90: MitRd -> 76thSt
US 90: DuvSt -> EadSt
US 90: TimAve -> TimDr
US 90: CR229 -> CR127/229
US 90: FL10_W -> AtlBlvd_W? (I don't think 10 is signed here, only 5)
US 90: StJohBRd -> StJohRd

Reguarding the 'FL10_W' label, it does seem to be mentioned here.  IMO, that's good enough to keep as-is.

All others above fixed.

US 92: FL694/687 -> FL687/694
US 92: WShoBlvd -> WesBlvd
US 92: FL574Pla -> FL574_Pla or FL574_E (it's only one segment that intersects multiple times)
US 92: GrayRd -> GaryRd

FL574 -> FL574_W & FL574Pla -> FL574_E

All others mentioned above fixed.

===

Also snuck in the US-441 reroute in Lake City that has finally been posted, and the newly posted FL-100A.

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

[dfilpus]

Fl 292 appears to have been truncated from the west from the Alabama state line to GonDr. I can't find any discussion of this. GMSV has it signed at the state line.

[rickmastfan67]

Fl 292 appears to have been truncated from the west from the Alabama state line to GonDr. I can't find any discussion of this. GMSV has it signed at the state line.

Because of this post on AARoads.  GIS also confirms this.

[rickmastfan67]

US 98: NorDr -> FaiDr (the more important road here)
US 98: FL399 -> CR399_W, CR399 -> CR399_E
US 98: GSJ at MilEnt http://www.openstreetmap.org/?lat=30.410981&lon=-86.701484
US 98: SceGulfDr -> CR2378
US 98: do we have confirmation that CR30Bay is signed as such? If not, FroBeaRd?
US 98: BecRd -> RicJacBlvd
US 98: two GSJs at CR3031 http://www.openstreetmap.org/?lat=30.188607&lon=-85.760946 SeaDr http://www.openstreetmap.org/?lat=30.185102&lon=-85.730932
US 98: recenter FL368
US 98: CR368A -> 15thSt (not signed)
US 98: move 25thAve one block east (or two to 24thAve, a through street)
US 98: MarSt -> MarSt_W
US 98/319: GulfBeaRd -> GulfBeaDr
US 98/319: move 10thSt west one block to RyanDr
US 98/319: CR67 -> TalSt (not signed here)
US 98: US319_MedN has been realigned
US 98: CagGroRd -> CabGroRd
US 98: US98TrkBro_W -> US98TrkBro_N
US 98/301: CR35A -> CR35Alt_N (CR35Alt in US 301)
US 98: SocLoopRd -> CR35A
US 98: AirRd -> HayTayBlvd
US 98/441: FL15/80 -> FL15/80/812

FL399: I think that one can stay as-is.  While the route is completely confined to the interchange, it is signed enough that people would see those shields on the BGS's.
CR30Bay: I see that a FL-30 shield is still present going EB on US-98 as of 09/19.  However, I took a little bit of a look on the road itself, and found no CR signage.  However, when checking out the intersection of CR-3037 (Wisteria Ln), I found FL-30 signage still present going both directions, which shouldn't be there since that part is a CR route now.  With no CR signage, and GIS saying it's no longer a state highway, I've gone with your suggestion of 'FroBeaRd'.
SeaDr -> SunHarRd after doing some digging since there was no street signage (Googled the name Google showed and got apartment listings).
10thSt -> 11thSt (RyanDr)
FL15/80 -> Stays as-is.  We don't add more than 2 routes in a label.

Everything else has been fixed.
https://github.com/TravelMapping/HighwayData/pull/3910

[rickmastfan67]

401: where does the name ChrColRd come from? How about CT5-10?

401: Came from OSM to be honest.  As for the 'new' label, I guess that can work for now.  However, I did see on that on mainline 401, that they're planning on finally installing a BGS for this exit, as it's on the side of the road in the most recent StreetView.  So, something to keep an eye on for the future I would think in case the label needs to be updated again.

StreetView has been updated.  So, "CT8-10" perhaps instead now?

[dfilpus]

Fl 292 appears to have been truncated from the west from the Alabama state line to GonDr. I can't find any discussion of this. GMSV has it signed at the state line.

Because of this post on AARoads.  GIS also confirms this.

Thanks for the update.

[rickmastfan67]

44: CR468_S -> MorBlvd (signs have been removed), CR468_N -> CR468

Fixed.

US 129: CraLn -> 117thRd
US 192: US17/441 -> US17/92/441
US 192/441: BogCrkRd -> ForRd
US 192: CR523_N -> CR523
US 192/441: HicTreRd -> HicTreeRd
US 192: SpaLn is a gated driveway

US 129: Fixed.
US 192:
1) No change as we only have 2 routes max in a label & I believe here that 441 is more important to mention that 92.
2) Fixed.
3) No change. Reason is because I like to keep the labels the same in a multiplex. Since US-441 intersects that same CR-523 twice, that's why there's a CR523_N label in US-192.
4) Fixed.
5) Replaced with 'OcePraLn' farther to the east. (street blade found, no gate, & had turn lanes both ways on US-192)

US 221: CR356 -> GreSt (not signed here)
US 231: CR2315 -> CR2293/2315
US 231: CamFloRd -> CamRd

US 221: Fixed.
US 231: Both fixed.

US 301: FortHamRd has been moved southwest
US 301: CR672 -> CR672_W?
US 301: US98_E -> US98_S, US98_W -> US98_N
US 301: CR476 -> CR476_E
US 301: ComSt -> ComSt_N or WarmSprAve_W
US 301: CR468 -> WarmSprAve_E
US 301: JarAve no longer exists; move south to OldWireRd
US 301: MainSt -> 146thSt

1) Fixed.
2) Only if I were adding the other part of the route, which I just have.  No shields there in StreetView @ the new CR672_E, but there was a street blade saying 'CR 672', which is good enough for me.
3) Fixed.
4) Agreed.  Fixed.
5/6) WarmSprAve_W/WarmSprAve_E
7-8.) Fixed

US 319: CR375 -> RoseSt (not signed here)
US 319: move MonRd south to OraAve
US 319: CR2196 -> OldSARd (I can't find any signs here)
US 319: ParAve -> ParkAve

1) Fixed.
2) Changed, and kept 'MonRd' as an alt name for it, since it was in use.
3) I couldn't find any signs as well.  Changed.
4) Fixed.

US 331: OwlsHeadRd is a driveway with no signs
US 331: CR282 -> EglSiteC6
US 331: CR2A_E -> CR2, CR2A_W -> CR2A, CR2 -> CR2_W

1) Removed.
2) Changed.
3) CR2A_E -> CR2_E -- Other 2 fixed as suggested.

US 441: SouRivDr -> SRivDr
US 441: FL912 -> CocCrePkwy
US 441: US17/192 -> US17/92/192
US 441: CR437_N -> PlySorRd? (not signed here, but it is signed nearby at the 429 exit)
US 441: FL429ConRd -> SR429ConRd
US 441: ChuDr -> YotRd
US 441: CR234_N -> CR234_E, CR234_S -> CR234_W
US 441: FL24_S -> FL24_W
US 441: FL26 -> FL24/26
US 441: NW59Ter -> 59thTer

1) Fixed.
2) Changed.
3) No change, as we only have 2 routes max in a label.
4) Agreed, since I couldn't find any shields for it at the FL-429 connector road as well, even thought there are a few shields for it inside of the FL-414/429 interchange.  Also renaming CR437_S -> CR437.
5) Changed.
6) Fixed.
7) Corrected.
8-9) Fixed.
10) Corrected.

=====

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

Getting very close to activation!

[yakra]

fl.fl540: Old9FootRd -> ...probably Old9FRd

[rickmastfan67]

I-4: I'm confused about why 7 exists, when US 301's point there is labeled US 92, not I-4.
I-4: move 33 to the underpass
I-4: 81A and 81B are now one interchange serving both roads
I-4: 82 will be folded into 82A when construction is done
I-4: the westbound entrance from GoreSt (between 82 and 82A) is missing; this will remain even after construction is done
I-4: "83" is signed as 82B
I-4: the permanent numbers in the 83A-83B-84 area are: (eastbound) 84A Amelia and 84B Colonial and (westbound) 84A Colonial and 84B Ivanhoe; I don't know how to handle this properly; maybe 83A -> 84A, 83B -> 84, 84 -> 84B

7: Because of being a holdover from the old days that I never fully delt with.  However, since there's now direct ramps from US-301 to WB I-4/from EB I-4 that bypass US-92 being on the 'C/D' roads (different here than US-1/90 on I-95's CD roads because they those use I-95 MM's), I'm going to sync the '7' point to US-301/92 (graph connection).  But I'm also going to add shaping points between 7A/7/7B to prevent a multiplex with US-92 in the area.
33: No change here since the ramps go to completely different roads, and thus justified to be placed right in the middle of the ramps here.
81A-84: Oh boy.  I honestly want to wait till construction is all done (or at least with 95% of the ramps open and shown in OSM) before I mess around with this area, because it's confusing as heck to be honest.
GoreSt: The WB onramp was originally tied completely into the FL-408 ramps there, thus why no separate point.  Once I'm honestly ready to play with this cluster junk, I would think giving it the label of '82' would be appropriate instead here.  Similar as I did with the 'former' 349 interchange on I-95 for US-90/FL-10 which had a number, but it was removed when it's access was moved to the C/D lanes.
83: That was the original number for that 'left' exit going WB.  As I mentioned above, once 95% of the ramps in this area are open and shown in OSM, then I'll come back and get it all setup correctly.

I-10: move 362 west to the underpass
I-75: add 128A?

I-10: Already fixed when doing US-17. No change needed now.
I-75: Already added in a previous changeset. No change needed now.

I-95: 3 -> 2D or 3A
I-95: move 14 to the underpass
I-95: "32A" is part of 33
I-95: 69 -> 69B, 69B -> 69A
I-95: 193 is open
I-95: 261 -> 260C
I-95: 353A is at Church Street, not Beaver Street; Beaver/Union is 353B and Kings is 353C, so probably add 353A, then 353A -> 353B and 353B -> 353C
I-95: 359 -> ClaSt

3: Going with 3A.
14: That's a little bit of a tough one due to where the ramps connect to FL-860. That and FL-915 getting into the mix too.  Would appreciate a few extra opinions on this one before I act.
32A: Yeah, I see what you're saying here. Now '33A'.
69/69B: Hmmm, this one could honestly go either way, since going NB, it's just signed as '69', and I based the # here on the NB ramps.  I think the best course of action here is to merge them together instead @ the 'current 69B location' (ontop of Belvedere Rd) with the label of '69 +69B' since the current distance between the points is only .1 miles. That & the 'current' 69 point should be recentered anyways a little bit more to the north so that it would have been centered between the flyovers, & when doing that, would have probably cut it down to .05 miles, and for sure not worth the extra point here.
193: Already in the file and displayed. No change needed here.
261: Spotted this when dealing with your US-92 post, so, already fixed.
353A/353B: Changing this would break quite a few list files, since '353B' is technically in the right place as it stands ATM.  Only 1 person is using it in I-95's file, but several are using it (I-95(353B)) in US-17's file.  However taking a look at 2 list files that list it as a starting point going 'north', they already have I-95 in that area clinched, so they will have no issues.  So, as far as I can tell, I can make the change without needing to make a news page post on this one.  So, what I'm going to do is just the 353A -> 353B & 353B -> 353C change (due to needing to keep the graph connections), but NOT add a 'new' 353A point.
359: ClaRd, not ClaSt, as it's Clark Road.

I-175: MLKJrStS -> MLKJrSt
I-195: move 2B west to the underpass

I-175: Fixed.
I-195: Already fixed when dealing with US-1.

I-275: 41 -> 41A, 41C -> 41B (and recenter this area)
I-275: add 44A at US 41 Bus.?
I-275: move 46A south to the underpass

40B-42: All recentered, and exit numbers updated.
44A: Agreed, added.  Merged KaySt & ScoSt into 'I-275' in fl.us041bustam's file.
46A: Agreed, fixed.

I-295: 55 -> 54
I-375: 10thSt -> MLKJrSt and move east; delete 8thStN since it's part of the same interchange
I-395: 2A and 2B are both eastbound and both dump out at 2nd Avenue; the only exit westbound is 2; it should probably just be 2 as one interchange

I-295: Fixed.  Came from the 'old' number that was painted on the shoulder before when it was 9A and didn't have the exit numbers posted just yet. https://goo.gl/maps/14HErJZhsqtigXz86
I-375: It was setup this way to prevent a false multiplex with US-19Alt/FL-595 in that area.  How would you suggest to deal with all 3 routes? (No changes done ATM.)
I-395: Hmmm, I'm not sure how I'm going to attack this.  Seems they're in the process of reconfiguring the area based off March '20 StreetView imagery of that area.  Plus we can't forget about the direct WB onramp(s) from 1st Ave (current 2A point).  Anybody else have some opinions on this particular interchange area? (No changes done ATM.)

FLTP: 211th Street is one of the primary destinations for exit 12 northbound, but not for exit 11 southbound. So maybe 11A -> 12, 12 -> 12A, 12A -> 12B (or US1_Cut)?
FLTP: 49 -> 49A and 49A -> 49B? or just combine?
FLTP: move 58 south to the main overpass
FLTP: move 97 south to the underpass
FLTP: 309 -> I-75 (if it needs a number, 307 is correct)
FLTPmia: 0X isn't signed, so maybe 0X -> FL826 and 0XA -> I-95?
FLTPmia: 4XA -> FL852 (no exits, only entrances)

FLTPK:
12: Sadly, '12A' is currently in use, which would throw a kink in doing these changes. As far as I can tell, only 1 user ((sneezy) is using that '12A' label.  Sadly, he only updates via email. :-/  So, for the moment, I've only changed 12A -> US1_Cut +12A till either he updates, or I just say F it, and he gets an extra .38 miles till he updates on his own. LOL.
49: Somebody is using the 'original' exit @ 49.  If they hadn't have added the new SB offramp 49A, I would say no change because of being a classic toll road interchange.  But when they added that ramp, having the 'graph connection' with FL-820 became a possibility.  Since the ramp going SB is 49A @ FL-820, and the 'main' interchange is 49 going NB, I'm just going to leave this as-is.
58: No.  Same reasoning as 49.  Didn't know they were going to add 'more' ramps here.  So, looking in StreetView, the 'new' ramp going NB got the number '58A', and that's what I'm going to label it as in the file, and will keep the original interchange as-is as 58.
97: Will do that.  Also 'merge' PikeRd & FLTpk together @ the same location in both US-98 & FL-80 for the graph connection.
309: Now 307.

FLTPKMia:
0X/0XA: Already changed to FL826 & I-95/826 in a previous update.
4XA: Changed to FL852.

======

Ok, that should deal with everything besides the questionable issues I mentioned above for I-375 & I-395 that I'd like some opinions on from others before touching them.  That and with I-4 that I'm waiting for the project to finish up some more before making changes.

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

[Markkos1992]

For I-95 at 12B, should there be a graph connection with US 441, FL 9, and FL 826 here?

[rickmastfan67]

For I-95 at 12B, should there be a graph connection with US 441, FL 9, and FL 826 here?

One of the most annoying interchange setups for sure in the state.

I might be able to get one for all of the routes @ 12B.  Then add an extra shaping point on I-95 between 12B & 12C to prevent a false multiplex with US-441 & FL-9.

=====

Anybody with opinions on I-95 "14", I-375 (in general), & I-395 "2" that I mentioned in my previous post?

[Markkos1992]

Anybody with opinions on I-95 "14", I-375 (in general), & I-395 "2" that I mentioned in my previous post?

I am fine with I-375 as-is.  For I-395, I think changing 2B to just 2 may be fine as long as the graph connections stay.

I am unsure on I-95 "14" at the moment.  I think it is easier to keep it as-is noting that NMPs would result from a graph connection with FL 860 and the locations of the ramps do not favor one. If there was a direct ramp SB to NE 5th Ave, I would be in favor of the graph connection.

[neroute2]

US221TrkPer has a broken overlap due to the omission of ChuSt.