Author Topic: FL: Point Concerns After 3/2023 Trip  (Read 8304 times)

0 Members and 1 Guest are viewing this topic.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3146
  • Last Login:Today at 09:40:09 pm
FL: Point Concerns After 3/2023 Trip
« on: March 25, 2023, 01:09:27 pm »
US 1: 
1.  LongBeaRd>-LongBeaDr
2.  Points should be added at the entrances to Curry Hammock State Park and Windley Key Fossil Reef Geological State Park.
3.  Is JPCReefSP too long?
4.  I still think that FLTpk(1) and FLTpk should be merged into one point.
5.  Should FLTpk(12A) be used here if we are going US1_Cut on FLTpk?
6.  If FL 986 is not being extended east to US 1, then the FL986 label should be renamed.
7.  Did you have any comment on this thread?  (https://forum.travelmapping.net/index.php?topic=4013.0)

US 17:
1. Consider replacing the shaping point north of CR761 with a visible point.
2.  Should *OldUS17_N be renamed?
3. Consider replacing the shaping point northeast of US92_W.  (also affects US 92)
4. I cannot tell based off GSV what is going on at FleCutRd.  (also affects US 92)
5. CenFloPky>-CenFloPkwy (also affects US 92 and US 441)
6. FLTpk(254)>-FLTpk (also affects US 92, does not affect US 441)
7. Consider adding points at Michigan St, Kaley Ave/St, Gore St, and South St due to direct connections to I-4.  (also affects US 92 and US 441, I definitely lean no-build on South St)
8. Consider replacing the shaping point north of FL 40 with a visible point.
9. OldHwy17>-OldUS17 (based on manual I believe)
10. Consider replacing the shaping point north of CR308 with a visible point.
11. Consider replacing the shaping point north of CR308B with a visible point (I think at Sisco Rd).
12. Consider replacing the shaping point south of FL100_E with a visible point.
13. Consider replacing the shaping point north of FL100_E with a visible point.  (also affects FL 100)
14. PecParRd>-PecParkRd
15. Consider replacing shaping points with visible points between PecParRd and FLA1A/200.
16. Consider replacing the shaping point south of FL/GA with a visible point at Owens Farm Rd (OweFarmRd).

US 19:
1.  I do not remember seeing any CR 202 shields on 54th Ave N while driving it between FL 693 and US 19.
2.  Should Evans Rd have its own point?
3.  Consider replacing the shaping point between FL44 and TurOakDr with a visible point.  (also affects US 98)
4. Consider replacing the shaping points with visible points between FL 349 and FL 26.  (also affects US 98 and US 27 ALT (Perry))
5.  CR30_Tay>CR30 (does not affect US 98, does affect US 27 ALT (Perry))
6.  Consider replacing the shaping point north of US27_N with a visible point.

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.

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

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.

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)

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.

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)

US 221:  MainSt_Per>-MainSt

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.

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.

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)

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

FL A1A (Vero Beach):  FL401>-FL528(54A)  (also affects FL 528)  Should GeoKingBlvd be FL528(54B)?  I am unsure.

FL 13:  OldStAugRd>-OldSARd

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

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)

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)

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

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

FL 60:  FL685_S>-FL685

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

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

FL 401:  Should CapeCanAFS be CapeCanSFS?

FL 538: 
1.  MarAve>-9
2.  KoaSt>-11

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.

FL 548:  SloAve>-BonSprBlvd

FL 572:  DraFieRd>-DraFieRd_W

FL 716:  MidRd>-WesBlvd or VetMemPkwy

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

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

Florida's Turnpike:  Should 62 have multiple points?
« Last Edit: October 26, 2023, 12:55:56 pm by Markkos1992 »

Offline ntallyn

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 332
  • Last Login:May 25, 2024, 09:55:05 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #1 on: March 25, 2023, 03:44:33 pm »
FL 134:  NewWorAve_S>-POWPkwy_S  (and I am unsure if FL 134 actually makes it to FL 228)
It doesn't. The west end of 134 says "To 228" (no arrow to follow 134), and the signage on 228 show "To 134". Seems pretty silly to me, but that's how it's signed.

When did the name change happen? I was just out there a couple of weeks ago, and I thought it was still New World Avenue. But I wasn't paying too close attention (I go out that way much too frequently).

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3146
  • Last Login:Today at 09:40:09 pm
Re: FL: Point Concerns After 3/2023 Trip
« Reply #2 on: March 25, 2023, 03:50:30 pm »
FL 134:  NewWorAve_S>-POWPkwy_S  (and I am unsure if FL 134 actually makes it to FL 228)
It doesn't. The west end of 134 says "To 228" (no arrow to follow 134), and the signage on 228 show "To 134". Seems pretty silly to me, but that's how it's signed.

When did the name change happen? I was just out there a couple of weeks ago, and I thought it was still New World Avenue. But I wasn't paying too close attention (I go out that way much too frequently).

Seems to have been 2018

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1855
  • Gender: Male
  • Last Login:May 25, 2024, 04:08:14 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #3 on: March 26, 2023, 05:50:47 am »
When did the name change happen? I was just out there a couple of weeks ago, and I thought it was still New World Avenue. But I wasn't paying too close attention (I go out that way much too frequently).

Seems it happened sometime between January '17 & July '18 per GSV. https://goo.gl/maps/BjngQp1Xx4TRpb8w8

Offline ntallyn

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 332
  • Last Login:May 25, 2024, 09:55:05 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #4 on: March 26, 2023, 10:10:26 pm »
Goes to show how much attention I pay to signage when I know those roads so well.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1855
  • Gender: Male
  • Last Login:May 25, 2024, 04:08:14 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #5 on: June 01, 2023, 03:36:28 am »
FL A1A (Vero Beach):  FL401>-FL528(54A)  (also affects FL 528)  Should GeoKingBlvd be FL528(54B)?  I am unsure.

This signage seems to indicate that FL-528 might make it now to Exit 54B.

However, this signage on the mainlines seems to indicate that FL-528 starts @ Exit 54A.

But, there is however, a '54 MM' along the road, which would indicate FL-528 mileage inside of Exit 54B.  This MM showed up per StreetView between Dec '18 & Jun '19 (same time-frame for the exit numbers).  There's a corresponding one going the other direction too.

But, GIS from 05/27/23 shows the end of FL-528 is still @ FL-401 (Exit 54A).

Opinions anyone?

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3146
  • Last Login:Today at 09:40:09 pm
Re: FL: Point Concerns After 3/2023 Trip
« Reply #6 on: June 01, 2023, 06:09:50 am »
Seems similar to the DE 1 discussion from earlier this year:  https://forum.travelmapping.net/index.php?topic=5048.0

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1855
  • Gender: Male
  • Last Login:May 25, 2024, 04:08:14 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #7 on: June 01, 2023, 07:07:35 am »
Seems similar to the DE 1 discussion from earlier this year:  https://forum.travelmapping.net/index.php?topic=5048.0

Oh yes, that discussion. LOL!

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1855
  • Gender: Male
  • Last Login:May 25, 2024, 04:08:14 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #8 on: August 11, 2023, 09:06:52 pm »
FL A1A (Vero Beach):  FL401>-FL528(54A)  (also affects FL 528)  Should GeoKingBlvd be FL528(54B)?  I am unsure.

This signage seems to indicate that FL-528 might make it now to Exit 54B.

However, this signage on the mainlines seems to indicate that FL-528 starts @ Exit 54A.

But, there is however, a '54 MM' along the road, which would indicate FL-528 mileage inside of Exit 54B.  This MM showed up per StreetView between Dec '18 & Jun '19 (same time-frame for the exit numbers).  There's a corresponding one going the other direction too.

But, GIS from 05/27/23 shows the end of FL-528 is still @ FL-401 (Exit 54A).

Opinions anyone?

Looks like FL-528 has always gotten to 'George King Blvd' per this Nov '07 GSV imagery.  So, will extend it to Exit 54B.


FL 538: 
1.  MarAve>-9
2.  KoaSt>-11

Done.

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

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1855
  • Gender: Male
  • Last Login:May 25, 2024, 04:08:14 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #9 on: October 27, 2023, 08:20:25 am »
Florida's Turnpike:  Should 62 have multiple points?

I don't think so.  When I crafted the route, that slip ramp from EB FL-870 to SB FLTpk already existed, making it easy to just have the 1PPI there & an easy graph connection.
https://maps.app.goo.gl/1RA2YXMC2R4sXrvZ6

Unlike with Exits 49 & 58, which gained the extra slip ramps (allowing for graph connections) after the file was crafted.

Though, if you can convince me otherwise (like when that slip got added), I'd at least consider again about adding an extra point there for both routes.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3146
  • Last Login:Today at 09:40:09 pm
Re: FL: Point Concerns After 3/2023 Trip
« Reply #10 on: October 27, 2023, 08:57:42 am »
Florida's Turnpike:  Should 62 have multiple points?

I don't think so.  When I crafted the route, that slip ramp from EB FL-870 to SB FLTpk already existed, making it easy to just have the 1PPI there & an easy graph connection.
https://maps.app.goo.gl/1RA2YXMC2R4sXrvZ6

Unlike with Exits 49 & 58, which gained the extra slip ramps (allowing for graph connections) after the file was crafted.

Though, if you can convince me otherwise (like when that slip got added), I'd at least consider again about adding an extra point there for both routes.

Yeah, basically this is the opposite of I-476 at PA 63 (Exit 31) in Lansdale (like Exits 49 and 58 here).  I will defer to others on this.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1855
  • Gender: Male
  • Last Login:May 25, 2024, 04:08:14 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #11 on: December 05, 2023, 03:51:41 am »
US 1: 
1.  LongBeaRd>-LongBeaDr
2.  Points should be added at the entrances to Curry Hammock State Park and Windley Key Fossil Reef Geological State Park.
3.  Is JPCReefSP too long?
4.  I still think that FLTpk(1) and FLTpk should be merged into one point.
5.  Should FLTpk(12A) be used here if we are going US1_Cut on FLTpk?
6.  If FL 986 is not being extended east to US 1, then the FL986 label should be renamed.
7.  Did you have any comment on this thread?  (https://forum.travelmapping.net/index.php?topic=4013.0)

1. Fixed.
2. Added.
3. Changed to JohnPenSP, even though same number of letters overall, lol.
4. I still say no, especially since people are using both points.
5. Changed to 'FLTpk_Cut' to match the FL Turnpike file.
6. Weird how the SB US-1 "JCT FL-986" signage has moved (Feb '19 vs Feb '21), as well as them replacing the 'arrow' below the signage @ the intersection (Apr '19 vs Feb '23).  Yet can't find any signage on the road itself till @ 69th Ave, where the 'Begin/End State Maint.' signage is located.  Changed to "72ndSt".
7. Already dealt with separately.

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

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1855
  • Gender: Male
  • Last Login:May 25, 2024, 04:08:14 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #12 on: December 06, 2023, 03:45:56 am »
US 17:
1. Consider replacing the shaping point north of CR761 with a visible point.
2.  Should *OldUS17_N be renamed?
3. Consider replacing the shaping point northeast of US92_W.  (also affects US 92)
4. I cannot tell based off GSV what is going on at FleCutRd.  (also affects US 92)
5. CenFloPky>-CenFloPkwy (also affects US 92 and US 441)
6. FLTpk(254)>-FLTpk (also affects US 92, does not affect US 441)
7. Consider adding points at Michigan St, Kaley Ave/St, Gore St, and South St due to direct connections to I-4.  (also affects US 92 and US 441, I definitely lean no-build on South St)
8. Consider replacing the shaping point north of FL 40 with a visible point.
9. OldHwy17>-OldUS17 (based on manual I believe)
10. Consider replacing the shaping point north of CR308 with a visible point.
11. Consider replacing the shaping point north of CR308B with a visible point (I think at Sisco Rd).
12. Consider replacing the shaping point south of FL100_E with a visible point.
13. Consider replacing the shaping point north of FL100_E with a visible point.  (also affects FL 100)
14. PecParRd>-PecParkRd
15. Consider replacing shaping points with visible points between PecParRd and FLA1A/200.
16. Consider replacing the shaping point south of FL/GA with a visible point at Owens Farm Rd (OweFarmRd).

1. Done @ RivSt.
2. No, as OSM is wrong here (& I just fixed that tonight).  The old road (now Main St) doesn't intersect US-17 here.  Thus, this is a valid label due to no intersection being here.
3. Done @ FraSt.
4. Fletcher Cut-off Road existed till the Dollar General was built there (sometime after Aug '19 per GSV).  When that happened, the entire road (on North side of US-17/92) was completely removed (can be seen in Sat imagery).  Can't tell what the road name is for the private road on the south end (well, can't verify at least).  So, will shift point to Government Center Blvd just to the west since the point isn't in use in either route.
5. Fixed in all 3 routes.
6. Not going to change this, as I want to keep the label the same in all three routes.
7. You forgot about Ameila Street too. ;)  All added in all 3 files.
8. Done @ EmpRd & HagRd.
9. No change. That is it's posted street name.
10. No build here.
11. Done @ SisRd.
12. Done @ BufBluRd.
13. Point removed in both files instead.
14. Fixed.
15. Both removed. New visable points added @ YelBluRd, HarRd, & WilBurBlvd.
16. Done @ OweFarmRd.


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

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3146
  • Last Login:Today at 09:40:09 pm
Re: FL: Point Concerns After 3/2023 Trip
« Reply #13 on: December 06, 2023, 06:25:24 am »
Quote
6. Not going to change this, as I want to keep the label the same in all three routes.

The main reason I report these is that yakra would report them as Extraneous Labels.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1855
  • Gender: Male
  • Last Login:May 25, 2024, 04:08:14 am
Re: FL: Point Concerns After 3/2023 Trip
« Reply #14 on: December 16, 2023, 05:32:55 am »
US 19:
1.  I do not remember seeing any CR 202 shields on 54th Ave N while driving it between FL 693 and US 19.
2.  Should Evans Rd have its own point?
3.  Consider replacing the shaping point between FL44 and TurOakDr with a visible point.  (also affects US 98)
4. Consider replacing the shaping points with visible points between FL 349 and FL 26.  (also affects US 98 and US 27 ALT (Perry))
5.  CR30_Tay>CR30 (does not affect US 98, does affect US 27 ALT (Perry))
6.  Consider replacing the shaping point north of US27_N with a visible point.

1. Must have missed this shield then. No change here.
2. Added.
3. Point added @ 7thAve.
4. Points added @ 989thSt, CR317, & CR55A_DixE.
5. No change, as rather keep the label synced between all 3 routes here since none are leaving @ this intersection.
6. Point added @ TysRd.

https://github.com/TravelMapping/HighwayData/pull/7077
« Last Edit: December 20, 2023, 12:04:16 am by rickmastfan67 »