FL: Point Concerns After 3/2023 Trip

[rickmastfan67]

US 27: 
1.  Consider adding a point at the entrance to Lake Louisa State Park.
2.  CitTowRd>-CitTowBlvd
3.  It looks like CR356_N should just be CR356 (one intersection).  (also affects US 221, does not affect US 19)
4.  Consider replacing the shaping point west of US19_N with a visible point.

1. Removed nearby 'BraRd' (not in use) and replaced with 'LakeLouSP' @ that intersection.
2. Fixed.
3. Hmmmm. In US-19, both are CR-356 Taylor, but seem to be 'separate segments'.  So, will 'fix' to CR356 in all 3 routes, and relabel 'CR356_S' in US-19 (& US-98/US-27Alt) to 'CR356_Tay' to keep them all synced (since none leave at either intersection).  Especially due to the love of FL using same CR numbers sometimes in other counties.
4. Point added @ StAugRd.

US 27 ALT (Perry): 
1.  US19/98_S>-US19/98
2.  CR356_S>-CR356

1. Since this is the end of a long multiplex with the two routes since it's Northern start/end, I think this is justified to leave as-is.
2. Went with 'CR356_Tay' as mentioned in #3 above.

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

[rickmastfan67]

US 41: 
1.  FL907_S>-FL907
2.  Should a point be added at Riverfront Blvd in Bradenton?  (also affects US 301)
3.  Consider replacing the shaping point south of FL 597 with a visible point.

1. Was to keep it 'synced' label wise with FL-A1A.  However, changed.
2. Hmmm, no 'EXIT' gore signage, however, classic partial exit design.  HOWEVER, are we even sure that's the road name?  I couldn't find a single street-blade w/ that name, or any signage mentioning the address.  Will defer on this till we can verify a road name for the point.
3. Done @ RheaSeeDr.

US 92:
1.  FL574_W>-FL574.  FL574_E should be edited as FL 574 here seems to be a secret designation.
2.  FL15A_S>-FL15A (only one intersection with the route unlike US 17)

1. Agreed.  Will also shorten FL-574 to FL-39 due to it being hidden the last block at least since 2008 per GSV.  Also, FL574_E -> ReySt.
2. Honestly, want to keep the labels synced here between the two routes, due to how long US-17 & US-92 share this multiplex. So, no change as this time.

==

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

[Markkos1992]

2. Hmmm, no 'EXIT' gore signage, however, classic partial exit design.  HOWEVER, are we even sure that's the road name?  I couldn't find a single street-blade w/ that name, or any signage mentioning the address.  Will defer on this till we can verify a road name for the point.

I think either 2ndSt or 3rdSt is fine.  The latter would be a duplicate label though.

[neroute2]

1. Agreed.  Will also shorten FL-574 to FL-39 due to it being hidden the last block at least since 2008 per GSV.  Also, FL574_E -> ReySt.

I'm not sure we should truncate it. The only difference between this and similar routes like I-670 is that there's no direct access from US 92 west to SR 574 west, so westbound signage is not to be expected.

[rickmastfan67]

1. Agreed.  Will also shorten FL-574 to FL-39 due to it being hidden the last block at least since 2008 per GSV.  Also, FL574_E -> ReySt.

I'm not sure we should truncate it. The only difference between this and similar routes like I-670 is that there's no direct access from US 92 west to SR 574 west, so westbound signage is not to be expected.

However, with your example, I-670 has an END shield, but FL-574 doesn't.

[neroute2]

So if I-670 had no end shield, would that change things?

[rickmastfan67]

So if I-670 had no end shield, would that change things?

I doubt it, since it's signed in the other direction @ the huge interchange.

With FL-574, there's 0 mention from US-92 EB, and usually FDOT is pretty good at signing stuff like this if they want to acknowledge the route.

[rickmastfan67]

So if I-670 had no end shield, would that change things?

I doubt it, since it's signed in the other direction @ the huge interchange.

With FL-574, there's 0 mention from US-92 EB, and usually FDOT is pretty good at signing stuff like this if they want to acknowledge the route.

Also, this would be similar to the eastern end of FL-84.  GIS says it goes one block beyond US-1 to Miami Road, but it isn't signed as doing so from US-1.  However, just was randomly looking @ GSV and did discover a street blade that mentions it @ Miami Road as 'SR 84'.  And it's a recent install too, as the old one said 'ST RD 84'.  However, not too keen on extending it still, since people would only see 'WB FL-84' shields @ US-1.

[rickmastfan67]

US 98: 
1.  SemPraWhiRd should be shortened.  (also affects US 441 and FL 80)
2.  CR35Alt>-CR35Alt_S (maybe CR35AAlt??) (may affect the CR35Alt_N label)
3.  OldCraHwy_S>-OldCraHwy (only one intersection unlike US 319)
4.  Consider replacing the shaping point west of FL 363 with a visible point.
5.  Consider replacing the shaping points east of FL 30A and CR 30A with visible points.

1. Changed to 'SPWhiRd'.
2. That road has an identity crises.    Half the time, it's signed as CR-35 ALT, the other times it's CR-35A ALT.  I mean, at that intersection, on the road itself, it has the CR-35 ALT shields.  Anyways, the GIS doesn't even show this segment on the county layer.  But down below, it has a small segment of the route shown as 'CR 35A'.  But that could mean anything, as FL doesn't normally have bannered routes.  Then again, Clinton Ave has the designation of 'CR-52A' in the GIS, but is signed as 'CR-52 ALT' in the field.  So, confusion all around there in that area.  Still, I don't think I'll be changing any of the labels here due to this fact.  The only reason I didn't have the '_S' at the southern junction was because that wasn't the end of the route, even though it doesn't connect back to US-98.
3. No change here, as I don't feel like messing around with this, as the label is in-use, and is technically correct, as I like to keep labels synced between routes along multiplexes as much as possible.
4. No, as over 0.1 miles would be lost if I adjusted it.  Not worth it IMO.
5. There's no roads there with any posted street blades w/ names.  So, no changes here.

2. Hmmm, no 'EXIT' gore signage, however, classic partial exit design.  HOWEVER, are we even sure that's the road name?  I couldn't find a single street-blade w/ that name, or any signage mentioning the address.  Will defer on this till we can verify a road name for the point.

I think either 2ndSt or 3rdSt is fine.  The latter would be a duplicate label though.

I'm going to go with RivBlvd.  This business has a website, and it lists the road as Riverfront Blvd.  That's good enough for me to ID the road name.

==

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

[rickmastfan67]

US 192: 
1.  Replace or remove the shaping point west of ForRd.  (also affects US 441)
2.  OCanCRd>-OldCCRd.  (also affects US 441)
3.  CR523_N>-CR523 (does not affect US 441)

1. Removed (in both routes).
2. No change. This label currently falls in within naming guidelines (#2).
3. Changed, even though I normally like to keep them synced between routes along a multiplex.

US 221:  MainSt_Per>-MainSt

1. Changed, even though I normally like to keep them synced between routes along a multiplex.

US 301: 
1.  DrMLKWay>-MLKWay
2.  Consider replacing the shaping point west of I-75(224) with a visible point.
3.  Consider replacing the shaping point north of HarRd_S with a visible point.
4.  CR35Alt_N>-CR35Alt
5.  WarmSprAve_E should be slightly relocated.

1. Changed.
2. Replaced with GamCt.
3. Replaced with RauRanRd.
4. No change. (See post above this for more info.)
5. Fixed (cross road was realigned there).

US 319: 
1.  Consider replacing the shaping point north of OldCraHwy_N with a visible point.
2.  The shaping point southwest of CR259 can probably be removed.

1. No change. No suitable road here.
2. Lose almost 0.2 miles removing it, so, this one will stay.

US 441:  I-4(80)>-I-4 (does not affect US 17 and US 92, I also see one interchange between US 441 and I-4)

1. No change. I prefer to keep labels synced along multiplexes, and since it's with two other big named US highways (US-17 & US-92), I prefer to keep this label synced at this time between all 3 routes.

=====

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

[rickmastfan67]

FL A1A (Fort Lauderdale):  Should this route be concurrent with US 41 to US 1 at the I-395 ramps? 

Perhaps.  However, with them completing reconfigurating that area like crazy men, I'll hold off on any changes here till it's finished.  This can be brought up in a separate thread once they've finished all the work in that area.

FL 13:  OldStAugRd>-OldSARd

Fixed.

FL 30E: 
1.  StJosPenSP should be shortened.
2.  Is CSanBLDr a viable point?  (and if it is, the label should be shortened)

1. Going w/ 'SJPenSP'.
2. It was in the past.  However, now that stop sign w/ street blade is gone, & gates look like their permanently closed.  Point isn't in-use, so, just converting it to a shaping point.

FL 46 (Sanford): 
1.  CMillARd>-CypMillRd
2.  Consider changing CR431 to OraBlvd as I did not see CR 431 shields at FL 46.
3.  MLKJrBlvd>-MLKBlvd (also affects US 17 and US 92)

1. Fixed.
2. Probably had it labeled as this, due to it being signed @ it's southern end @ CR-46A.  However, will swap the label for now.
3. Changed in all 3 routes.

FL 50:
1.  I-4(84)>-I-4 (only interchange with I-4 unlike US 17/US 92)
2.  FL527_S>-FL527  (only intersection with FL 527 unlike US 17/US 92)

Both changed.

FL 54 (Zephyrhills): 
1.  Consider replacing the shaping point east of MeaPoiBlvd with a visible point.
2.  GorSt looks like it should be CorSt.

1. Replaced with 'RivGlenBlvd'.
2. Fixed.

FL 56:  Consider replacing the shaping point east of I-75 with a visible point.

Done @ CypRidBlvd.

FL 60:  FL685_S>-FL685

Done. Was a leftover from removal of the hidden segments of highways that I missed.

FL 134:  NewWorAve_S>-POWPkwy_S  (and I am unsure if FL 134 actually makes it to FL 228)

GIS data (from 07/20/24) shows that FL-134 is along 'POWPkwy' for that short distance to make it back to FL-228.

However, there's a clear 'END' shield on 103rd Ave.  So, will now 'end' FL-134 @ POW & hide the 'FL228' label under the new 'POWPkwy' label.  Will also add a news entry for this change.

FL 371:  CR2203>-CR373A  (This may be best as a no-build as I see CR2203 signage at FL 373...)

GIS data says it's CR2203.  So, no change.  My guess, mistake signage that the local county or FDOT has failed to notice and/or fix.

FL 401:  Should CapeCanAFS be CapeCanSFS?

Used to be Air Force there.   Updated.

FL 540:  I understand that usafl was done to eliminate FL Routes when there are not signed overlaps with US Routes.  However, I would think that the US 17/FL 540 concurrency would be considered as implied one based on how we handle Arkansas.

Bleep Arkansas. LOL!  FDOT's GIS is usually very good in showing if there is a overlap of a state route on a US highway, both in the field & in the GIS.  However, GIS here is 100% clear, that both sections of FL-540 are separate, and it doesn't have a hidden mulitplex with US-17.  Thus, no change here needed (this is similar to how FL-109 is handled).

FL 548:  SloAve>-BonSprBlvd

Updated.

FL 572:  DraFieRd>-DraFieRd_W

Changed.

FL 716:  MidRd>-WesBlvd or VetMemPkwy

VetMemPkwy

FL 826:  Consider adding a point between US 1 and FL A1A for access to Oleta River State Park.

34thAve added.

FL 953: 
1.  NW21stSt>-21stSt?
2.  Should a point be added for the slip ramp to South River Dr?

1. No.  There's 2 separate 21st St's (NW21stSt & E21stSt).  In this case, it's better to just have the 'directional' addition to allow people to figure out which one they need.
2. Hmmmm, I'm not too sure about adding this one to be honest.  However, I will add a point @ 31stSt just to the south, as it looks like it could be useful.

====

And with that, this thread is finally fully dealt with.

https://github.com/TravelMapping/HighwayData/issues/7575

[ntallyn]

FL 134:  NewWorAve_S>-POWPkwy_S  (and I am unsure if FL 134 actually makes it to FL 228)

GIS data (from 07/20/24) shows that FL-134 is along 'POWPkwy' for that short distance to make it back to FL-228.

However, there's a clear 'END' shield on 103rd Ave.  So, will now 'end' FL-134 @ POW & hide the 'FL228' label under the new 'POWPkwy' label.  Will also add a news entry for this change.

The last time I was out that way, the END FL 134 sign was at the west end of 103rd St, as well as TO FL 134 signs on FL 228. I'll be out that way in a couple of weeks and can do a field check.

[ntallyn]

Field signage is the same as previously reported. The west end of 103rd St is marked END FL 134, with a TO FL 228 sign. Eastbound Normandy Blvd (FL 228) has TO FL 134 signs. Westbound Normandy has a JCT FL 134 sign followed by a TO FL 134 sign. Photos to come when I can get them uploaded.