Travel Mapping

Highway Data Discussion => In-progress Highway Systems & Work => Topic started by: rickmastfan67 on June 27, 2016, 07:00:52 am

Title: usafl: Florida State Highways
Post by: rickmastfan67 on June 27, 2016, 07:00:52 am
http://tm.teresco.org/hb/index.php?sys=usafl
Original thread: http://clinched.s2.bizhat.com/viewtopic.php?t=399&mforum=clinched (only viewable if you were a collaborator on the old forums, sorry, can't fix that)

What will be included:
Only posted segments of state highways.  If the route is completely hidden under another highway, it will not be added (like FL-8 being entirely under I-10).

Toll Routes:
These routes carry State Route numbers, but they use a different type of shield, and normally, they aren't split into toll and non-toll route except a few (like FL-528/Toll FL-528). They are considered to be part of the main Florida State Highway system, and not a separate system.  However, we possibly might be looking at displaying both type of shields in the HB (http://tm.teresco.org/forum/index.php?topic=322.0).  Otherwise, I would recommend to at least display the type of shield that has the longest segment of the two in the HB when the time comes to add the shield code for Florida.

There are also very few bannered State Highways compared to US Highways in FL. In fact, there are only two bannered routes that I know of via Wikipedia:
Truck FL-14 (Madison)
Business FL-44 (New Smyrna Beach)

There are also several suffixed state routes with "A", "B", & "E".  They will be included as 'normal' state highways, but will be treated like they were bannered, and have city abbreviations in the file name.

Sources:
OSM
Google StreetView (to verify if posted)
FDOT Shapfiles (http://www.dot.state.fl.us/planning/statistics/gis/road.shtm)

=====

As of the time of this post, only the routes under 100 have been cleaned up and split apart and no longer have their 'hidden' segments included.  So, if you want to review any of the highways, I recommend starting there, as the ones above 100 are still in the process of being 'split' apart where needed and that process will take some time.
Title: Re: usafl: Floride State Highways
Post by: yakra on July 30, 2016, 01:51:21 am
Isn't the correct spelling "Fluoride"?  8)
Title: Re: usafl: Florida State Highways
Post by: Markkos1992 on July 30, 2016, 05:01:52 am
Reposting from other thread (http://tm.teresco.org/forum/index.php?topic=90.msg843#msg843):  (this was posted April 12th, note that it was just about a city typo and was not point-related, so I apologize if I violated the no points rule then)

Minor, but for FL 20, the Gainesville file is spelt Gainsville without the "e" for whatever reason.

I guess I have watched too much SEC football over the years to not miss that.


-Mark AKA 74/171FAN
Title: Re: usafl: Florida State Highways
Post by: Jim on July 30, 2016, 01:24:25 pm
Reposting from other thread (http://tm.teresco.org/forum/index.php?topic=90.msg843#msg843):  (this was posted April 12th, note that it was just about a city typo and was not point-related, so I apologize if I violated the no points rule then)

Minor, but for FL 20, the Gainesville file is spelt Gainsville without the "e" for whatever reason.

I guess I have watched too much SEC football over the years to not miss that.


-Mark AKA 74/171FAN

Fixing this one for the next update.  Will be in GitHub in a moment.  Thanks.
Title: Re: usafl: Florida State Highways
Post by: Markkos1992 on July 31, 2016, 07:39:21 am
Reposting from other thread (http://tm.teresco.org/forum/index.php?topic=90.msg843#msg843):  (this was posted April 12th, note that it was just about a city typo and was not point-related, so I apologize if I violated the no points rule then)

Minor, but for FL 20, the Gainesville file is spelt Gainsville without the "e" for whatever reason.

I guess I have watched too much SEC football over the years to not miss that.


-Mark AKA 74/171FAN

Fixing this one for the next update.  Will be in GitHub in a moment.  Thanks.

It was changed to Gainseville (it should be Gainesville).  I just checked to verify that.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on July 31, 2016, 07:54:39 am
Just submitted a pull request cleaning up routes FL-100 to FL-111.
https://github.com/TravelMapping/HighwayData/pull/713
Title: Re: usafl: Florida State Highways
Post by: oscar on July 31, 2016, 12:13:08 pm
From my draft TM entries for FL state routes:

FL 29 Truck (La Belle): not in HB, my notes show such a signed route but not where it goes, and neither online maps nor a quick peek at GMSV at Bridge St. south of FL 80 help either

FL 72: waypoint FL785 -> FL758

FL 84Nap: waypoint CR951 -> FL951 (951 signed as state route at least from FL 84 to I-75)

FL 267 extends north at least to US 90, and online maps indicate it reaches the FL/GA border.

FL 732 extends east to FLA1A, as shown in OSM

Do with these what you want. especially the last two can wait until we get into higher numbers.
Title: Re: usafl: Florida State Highways
Post by: Jim on July 31, 2016, 03:37:23 pm
FL 29 Truck (La Belle): not in HB, my notes show such a signed route but not where it goes, and neither online maps nor a quick peek at OSM at Bridge St. south of FL 80 help either

I was just through there a couple weeks ago.  I believe there was a sign where Bridge St branches from NB FL 29, but no sign where FL 80 crosses Bridge St.  We drove up Main St, so I don't know if there was any indication of the route along Bridge St. itself.
Title: Re: usafl: Florida State Highways
Post by: mapmikey on July 31, 2016, 07:35:30 pm
GMSV shows it posted in both directions on FL 29:

https://goo.gl/maps/QCYUXRWJnht
https://goo.gl/maps/U1JSsQQKrJ22
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 02, 2016, 12:09:26 am
GMSV shows it posted in both directions on FL 29:

https://goo.gl/maps/QCYUXRWJnht
https://goo.gl/maps/U1JSsQQKrJ22

And it looks like FL-80 might have a truck route there as well.  Will have to look into this more.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 02, 2016, 12:22:48 am
GMSV shows it posted in both directions on FL 29:

https://goo.gl/maps/QCYUXRWJnht
https://goo.gl/maps/U1JSsQQKrJ22

And it looks like FL-80 might have a truck route there as well.  Will have to look into this more.

Ok, looks like the FL-80 is just a directional one.  FL-29 looks to be a legit route, as it has at least 1 shield along the route itself as of 2011 going SB per StreetView.  So, I'll at least be adding the FL-29 Truck route there.
Title: Re: usafl: Florida State Highways
Post by: froggie on August 02, 2016, 11:17:01 am
Mentioned on another thread, but you missed FL 115 north of Jacksonville.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 02, 2016, 08:38:49 pm
Mentioned on another thread, but you missed FL 115 north of Jacksonville.

For whenever whomever's working on this system (presumably James) gets back to it, there's a segment of FL 115 missing from the browser, running north of Jacksonville.  GMSV from 2015 shows it signed, and April 2016 FDOT shapefiles show it as a state highway route.

It's already there, and has been for awhile.
http://tm.teresco.org/hb/?r=fl.fl115cal
Title: Re: usafl: Florida State Highways
Post by: froggie on August 03, 2016, 01:23:57 pm
You're aware that FDOT shapefiles show it as a continuous route, right?  Presuming you split it because of an apparent lack of signage along I-95.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 03, 2016, 11:39:18 pm
You're aware that FDOT shapefiles show it as a continuous route, right?  Presuming you split it because of an apparent lack of signage along I-95.

Yes, I'm very aware.  However, I've been splitting up routes that have 'unsigned' segments.  There's nothing on US-1 Alternate & I-95 to justify an "implied" multiplex between the two segments, thus, the route should stay split.  And yes, that means when I get to it, removing the segment I have on the 'main' file along US-1 Alternate.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 03, 2016, 11:54:50 pm
On another note,  with FL-109 (http://tm.teresco.org/hb/?r=fl.fl109), I currently have the section along Cesery Blvd (northern end) as part of the route. (StreetView (https://goo.gl/maps/TL2ciNiTULH2))  The GIS backs this up.  However, signage in the field designates this as FL-109A, which it was part of at one time. (StreetView: [1] (https://goo.gl/maps/fFBwf82vDRS2) [2] (https://goo.gl/maps/EhTrS7wP3kP2))

So, should I keep that part as FL-109, or add a new file for FL-109A along that segment.  Note, FL-109A used to exist, but now it's CR-109A (unposted) north of FL-115.
Title: Re: usafl: Florida State Highways
Post by: yakra on August 06, 2016, 05:18:24 pm
Lagging sign replacement? I'd kinda lean toward including as part of FL109.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 16, 2016, 04:03:38 am
Lagging sign replacement? I'd kinda lean toward including as part of FL109.

Well, that's how I have it currently.  Though, I'm still open to turning that segment into '109A' if needed.
Title: Re: usafl: Florida State Highways
Post by: theFXexpert on October 09, 2016, 05:26:50 pm
I noticed by going up I-75 today that all of the FL48 shields for exit 314 were replaced with county pentagons with the I-75 widening project. There is a CR48 pentagon reassurance shield going eastbound from I-75. The state road 48 shields are still up at the US301 intersection though.

The exit 321 northbound signs replaced the CR470 pentagons with State Road 470 shields. The southbound signs still have the pentagons.

EDIT: Streetview images:
FL470 -> https://www.google.com/maps/@28.6831238,-82.1344862,3a,27y,47.9h,84.82t/data=!3m6!1e1!3m4!1s1kFgA3uxEJDrS4-U6W_jHg!2e0!7i13312!8i6656?hl=en

-> https://www.google.com/maps/@28.7205564,-82.1164671,3a,16.6y,42.05h,88.25t/data=!3m6!1e1!3m4!1sIZ7xjaZW146HZ3hxD3rLtQ!2e0!7i13312!8i6656?hl=en

CR48 -> https://www.google.com/maps/@28.6744604,-82.1393889,3a,27.1y,208.89h,89.89t/data=!3m6!1e1!3m4!1si-Xrq0MIcz94wdWWV5Ew0w!2e0!7i13312!8i6656?hl=en
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on October 16, 2016, 01:47:06 am
Interesting.  I'll have to see what the GIS data says about this as well.
Title: Re: usafl: Florida State Highways
Post by: mefailenglish on November 06, 2016, 06:23:28 pm
If there's anything I can do to help expand this beyond FL802 to FL9336, please let me know.  I live in South Florida, where most of these routes are, so I'm motivated, and can get ground truth.

Thanks,  --Joe
Title: Re: usafl: Florida State Highways
Post by: michih on November 07, 2016, 03:27:16 am
If there's anything I can do to help expand this beyond FL802 to FL9336, please let me know.  I live in South Florida, where most of these routes are, so I'm motivated, and can get ground truth.

Thanks. Please refer to the site start page (http://tm.teresco.org/):

Quote
Some experienced users volunteer to help the project. If this interests you, start by reporting problems with existing highway data. Those who have learned the project's structure and highway data rules and guidelines can help greatly by providing review of new highway systems in development. Highly experienced users can learn how to plot new highway systems under the guidance of experienced contributors. Again, see the project forum for more information.

The rules are described on the old CHM site: http://cmap.m-plex.com/tools/manual.php.
Project data is hosted on GitHub: https://github.com/TravelMapping/.
Title: Re: usafl: Florida State Highways
Post by: Jim on January 06, 2017, 10:41:57 pm
Drove a chunk of FL429 today.  It currently joins FL414 north of their junction and ends near US 441.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on January 27, 2017, 12:08:14 pm
Just cleaned up the routes between 112 & 173. (#1088 (https://github.com/TravelMapping/HighwayData/pull/1088))
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on January 27, 2017, 12:10:57 pm
I noticed by going up I-75 today that all of the FL48 shields for exit 314 were replaced with county pentagons with the I-75 widening project. There is a CR48 pentagon reassurance shield going eastbound from I-75. The state road 48 shields are still up at the US301 intersection though.

CR48 -> https://www.google.com/maps/@28.6744604,-82.1393889,3a,27.1y,208.89h,89.89t/data=!3m6!1e1!3m4!1si-Xrq0MIcz94wdWWV5Ew0w!2e0!7i13312!8i6656?hl=en

GIS data dated 01/21/17 still shows this as a State Route 48.  So, I'm inclined to leave it as-is for now.

As for 470, GIS data doesn't acknowledge it yet, and still shows it as a county route.
Title: Re: usafl: Florida State Highways
Post by: mefailenglish on January 28, 2017, 05:40:58 pm
I've been buried at work but here and there have been looking through the higher number routes.  Unfortunately I lost half of my notes, but I still have these:

Routes to delete:
FL 249 (overlap of US 129 & US 90)
FL 261 (overlap of US 319)
FL 290 (now a county route)
FL 329 (SR segment unsigned & overlapped by FL 20 in Gainesville, only CR segment is signed)
FL 369 (overlap of US 319)
FL 375 (overlap of US 319)
FL 377 (overlap of US 319)
FL 500 (overlaps of US 192, US 441, US 27, US 27 Alt)
FL 517 (US 92)
FL 530 (US 192)
FL 533 (former US 98/301 truck in Dade City, now mainline 98/301 and unsigned)
FL 546 (TO US 92, US 92, not signed)
FL 555 (US 17)
FL 592 (I-375)
FL 594 (I-175)
FL 595 (US 19 Alt)
FL 599 (US 41)

Need to add:
FL 399 (this only consists of 1/3 mi of the route between US 98 and just short of the bridge to the barrier island, the rest being CR 399, but it is (https://goo.gl/maps/7VB2aQ2G1pA2) signed (https://goo.gl/maps/LJW8hqa6Eqz))
FL 451

Modifications:
FL 200:  Should be split into two segments:  between US 41 and US 27/301/441; then from US 1/23/301 in Callahan to its end in Fernandina Beach
FL 400:  Eliminate waypoints 1 - 79, relabel waypoint 80 like I-4/95.
FL 569:  Eliminate waypoint 1 (FL 618), the route no longer goes south of FL 60

Just wanted to dump these here before I lost them too.
Title: Re: usafl: Florida State Highways
Post by: theFXexpert on January 29, 2017, 03:02:31 pm
I've been buried at work but here and there have been looking through the higher number routes.  Unfortunately I lost half of my notes, but I still have these:

Routes to delete:
FL 249 (overlap of US 129 & US 90)
FL 261 (overlap of US 319)
FL 290 (now a county route)
FL 329 (SR segment unsigned & overlapped by FL 20 in Gainesville, only CR segment is signed)
FL 369 (overlap of US 319)
FL 375 (overlap of US 319)
FL 377 (overlap of US 319)
FL 500 (overlaps of US 192, US 441, US 27, US 27 Alt)
FL 517 (US 92)
FL 530 (US 192)
FL 533 (former US 98/301 truck in Dade City, now mainline 98/301 and unsigned)
FL 546 (TO US 92, US 92, not signed)
FL 555 (US 17)
FL 592 (I-375)
FL 594 (I-175)
FL 595 (US 19 Alt)
FL 599 (US 41)

Need to add:
FL 399 (this only consists of 1/3 mi of the route between US 98 and just short of the bridge to the barrier island, the rest being CR 399, but it is (https://goo.gl/maps/7VB2aQ2G1pA2) signed (https://goo.gl/maps/LJW8hqa6Eqz))
FL 451

Modifications:
FL 200:  Should be split into two segments:  between US 41 and US 27/301/441; then from US 1/23/301 in Callahan to its end in Fernandina Beach
FL 400:  Eliminate waypoints 1 - 79, relabel waypoint 80 like I-4/95.
FL 569:  Eliminate waypoint 1 (FL 618), the route no longer goes south of FL 60

Just wanted to dump these here before I lost them too.

There is a FL200 sign with 301 at the CR325 intersection at Island Grove. But I agree that it should be split since it's the only instance 200 is co-signed with 301. It looks like an error. Similarly, I think FL212 should be deleted.
FL594 is signed between FL687_S and FL687_N (https://www.google.com/maps/@27.7669187,-82.6384322,3a,50.3y,206.63h,86.51t/data=!3m6!1e1!3m4!1sK6KrTJ6NMfZcXkB7IoUgFA!2e0!7i13312!8i6656?hl=en)
FL595 is signed in downtown St. Petersburg Along with US19Alt. Although, it's inconsistent. Sometimes there's only a 595 sign, only a US19Alt sign, or both. 595 signs simply disappear west of I-275 if I remember correctly.

Additionally:
FL559 got extended south from US92 in Auburndale to FL655.
FL651 is unsigned.
FL655 south of the 'RecHwy' point is signed as FL620.
FL683 is unsigned.
FL684 is not signed east of the 'US41/41Bus' point.
FL685 is only signed between US92 and FL60 on Henderson Blvd.

Also, I will say for the record that FL109 is fine as it is.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on January 29, 2017, 07:06:45 pm
Need to add:
FL 399 (this only consists of 1/3 mi of the route between US 98 and just short of the bridge to the barrier island, the rest being CR 399, but it is (https://goo.gl/maps/7VB2aQ2G1pA2) signed (https://goo.gl/maps/LJW8hqa6Eqz))

That one is debatable.  Normally, for us to consider the route as 'signed', there needs to be at least a shield on the mainline (couldn't find one).  So this one might not make the cut.
Title: Re: usafl: Florida State Highways
Post by: ntallyn on January 30, 2017, 09:59:02 pm

...
I think FL212 should be deleted.
...

FWIW, FL212 has a single sign in both directions along Beach Blvd. I think they are both just east of I-295, but I can verify that (if necessary) when I head out that way this weekend. However, considering those are the only signs, and the entirety of the route overlaps US 90, I don't think it's a necessary route.
Title: Re: usafl: Florida State Highways
Post by: theFXexpert on January 31, 2017, 10:28:10 am

...
I think FL212 should be deleted.
...

FWIW, FL212 has a single sign in both directions along Beach Blvd. I think they are both just east of I-295, but I can verify that (if necessary) when I head out that way this weekend. However, considering those are the only signs, and the entirety of the route overlaps US 90, I don't think it's a necessary route.

Yes, The only FL212 signs are with US90 reassurance markers just east and west of 295. I actually go through there relatively often.
Title: Re: usafl: Florida State Highways
Post by: CharlotteAllisonCDTG on February 08, 2017, 10:45:47 pm
I just got on the forum, so -- if this has already been mentioned before -- I apologize for asking again.  When will the Florida State Road system be added to the site officially?  I get tired of seeing the "Ignoring line matching highway in system in development" error lines at the top of my log file.  LOL.
Title: Re: usafl: Florida State Highways
Post by: oscar on February 08, 2017, 10:56:06 pm
I don't know the answer. I do know (having driven most or all of them) that there a lot of routes in south Florida > FL802 not yet in the HB. I have more than 60 of those high-numbered routes in my draft list entries file (which I keep offline, separate from my online list file).
Title: Re: usafl: Florida State Highways
Post by: CharlotteAllisonCDTG on February 08, 2017, 11:07:45 pm
I attended college in Pensacola and was stationed (Navy)  in Pensacola and Jacksonville, so I have lots of highways under my belt.  I have all of them at the top of my log as errors.
Title: Re: usafl: Florida State Highways
Post by: mapcat on February 08, 2017, 11:47:18 pm
I think someone has posted that if you include a # at the beginning of the line in your .list, it will be ignored and not show up in your log. For now I just do what Oscar does, and keep my usafl (and usaca, canqc, etc) entries separate from my working list, ready to paste in when the time comes. rickmastfan67 is still revising the system and there probably will be many changes to the existing routes before the set goes to preview, so even if what you have now looks correct, you'll probably still see some log entries once he's finished.
Title: Re: usafl: Florida State Highways
Post by: si404 on February 09, 2017, 03:47:06 am
I think someone has posted that if you include a # at the beginning of the line in your .list, it will be ignored and not show up in your log.
Or there's the other way and just skim over the 'Ignoring line matching highway in system in development' and 'Unknown region/highway combo in line' errors, putting up with them (on the rare occasions you look at your log file).
Title: Re: usafl: Florida State Highways
Post by: mapcat on February 09, 2017, 08:44:17 am
Or there's the other way and just skim over the 'Ignoring line matching highway in system in development' and 'Unknown region/highway combo in line' errors, putting up with them (on the rare occasions you look at your log file).
Right, although I check fairly regularly for errors since changes sometimes break my .list (or people forget to provide alt labels when they edit). It's easier to spot these when I don't have to wade through dozens of other errors.
Title: Re: usafl: Florida State Highways
Post by: mapmikey on February 09, 2017, 07:37:20 pm
I've been buried at work but here and there have been looking through the higher number routes.  Unfortunately I lost half of my notes, but I still have these:

Routes to delete:
FL 249 (overlap of US 129 & US 90)
FL 261 (overlap of US 319)
FL 290 (now a county route)
FL 329 (SR segment unsigned & overlapped by FL 20 in Gainesville, only CR segment is signed)
FL 369 (overlap of US 319)
FL 375 (overlap of US 319)
FL 377 (overlap of US 319)
FL 500 (overlaps of US 192, US 441, US 27, US 27 Alt)
FL 517 (US 92)
FL 530 (US 192)
FL 533 (former US 98/301 truck in Dade City, now mainline 98/301 and unsigned)
FL 546 (TO US 92, US 92, not signed)
FL 555 (US 17)
FL 592 (I-375)
FL 594 (I-175)
FL 595 (US 19 Alt)
FL 599 (US 41)

Need to add:
FL 399 (this only consists of 1/3 mi of the route between US 98 and just short of the bridge to the barrier island, the rest being CR 399, but it is (https://goo.gl/maps/7VB2aQ2G1pA2) signed (https://goo.gl/maps/LJW8hqa6Eqz))
FL 451

Modifications:
FL 200:  Should be split into two segments:  between US 41 and US 27/301/441; then from US 1/23/301 in Callahan to its end in Fernandina Beach
FL 400:  Eliminate waypoints 1 - 79, relabel waypoint 80 like I-4/95.
FL 569:  Eliminate waypoint 1 (FL 618), the route no longer goes south of FL 60

Just wanted to dump these here before I lost them too.

There is a FL200 sign with 301 at the CR325 intersection at Island Grove. But I agree that it should be split since it's the only instance 200 is co-signed with 301. It looks like an error. Similarly, I think FL212 should be deleted.
FL594 is signed between FL687_S and FL687_N (https://www.google.com/maps/@27.7669187,-82.6384322,3a,50.3y,206.63h,86.51t/data=!3m6!1e1!3m4!1sK6KrTJ6NMfZcXkB7IoUgFA!2e0!7i13312!8i6656?hl=en)
FL595 is signed in downtown St. Petersburg Along with US19Alt. Although, it's inconsistent. Sometimes there's only a 595 sign, only a US19Alt sign, or both. 595 signs simply disappear west of I-275 if I remember correctly.

Additionally:
FL559 got extended south from US92 in Auburndale to FL655.
FL651 is unsigned.
FL655 south of the 'RecHwy' point is signed as FL620.
FL683 is unsigned.
FL684 is not signed east of the 'US41/41Bus' point.
FL685 is only signed between US92 and FL60 on Henderson Blvd.

Also, I will say for the record that FL109 is fine as it is.

Just got back from a week in St Petersburg FL...

FL 595 is signed prominently from both directions of US 19 (and US 19 ALT is mentioned from US 19 to only go northbound, though there is reassurance US 19 ALT signage leaving the intersection and over to the one-way pair at I-275); it is prominently posted from US 92 and FL 687; I drove it westbound and saw no 595 shields (but plenty of 19 ALT) but GMSV shows one EB on 4th just past I-275 and a set after MLK Ave.

FL 546 is signed prominently from both directions of US 92 and also a reassurance marker leaving US 92; not signed from I-4 or as best I can tell from GMSV after leaving I-4.

I can confirm that FL 687 is co-signed with US 92 at every opportunity along its duplex in addition to its solo segments north and south of US 92.

i can also confirm that FL 524 ends at FL 501 and that no signed state route connects with nearby FL 528 - https://goo.gl/maps/K71NAXibuYB2

FL 501 is not signed at FL 520 and is not signed anywhere south of Michigan Ave as far as I can tell.
Title: Re: usafl: Florida State Highways
Post by: mefailenglish on February 15, 2017, 10:38:21 am
Need to add:
FL 399 (this only consists of 1/3 mi of the route between US 98 and just short of the bridge to the barrier island, the rest being CR 399, but it is (https://goo.gl/maps/7VB2aQ2G1pA2) signed (https://goo.gl/maps/LJW8hqa6Eqz))

That one is debatable.  Normally, for us to consider the route as 'signed', there needs to be at least a shield on the mainline (couldn't find one).  So this one might not make the cut.
That's funny.  I actually had that same thought (debatable) in my original post, but must've removed it while I was editing it.

A few more thoughts from 600-802:

FL600/FL600tam: delete, all hidden
FL615: remove BellAve, route starts at CR611
FL620: add (the first two waypoints of FL655 are actually FL620)
FL651: delete, unsigned (already mentioned)
FL655: see FL620
FL683: delete, unsigned portion of US301 (already mentioned)
FL685: trim to first two waypoints only.  Beyond there is not signed. (already mentioned)
FL700:  Keep standalone piece in Palm Beach Co, Old Connors Rd/Main St.  Technically beyond Canal Point to Okeechobee it's also signed occasionally (as is FL 15) along with their US highway companions (https://goo.gl/maps/oCT9gwtKGs62) but since FL015 doesn't go past Canal Point in the usafl system I'd say do the same with FL700.  Delete all the rest of FL700 as it's hidden under US98.
FL700Bro:  Keep

FL707.  This one is weird.  On the delete side:  It's not in the FLDOT shapefiles.  And it's signed as CR707 in downtown Stuart.  However, in the streetview, there are multiple FL 707 shields north of the drawbridge up to "TO US 1"/NW Wright Blvd. 

FL739:  Extend south to Alico Rd/US 41 interchange.  Delete north of FL80, becomes hidden under US41Bus.
FL750:  The route was extended west from FL291 to US29, and that's what's in the shapefiles.  However, there is currently no FL750 signage that I could find west of FL291, including with the interchange with I-110. 

Just my 2¢.  --Joe
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on March 05, 2017, 08:53:12 pm
Just cleaned up FL-187 to FL-212 (https://github.com/TravelMapping/HighwayData/pull/1142).
Title: Re: usafl: Florida State Highways
Post by: CharlotteAllisonCDTG on March 05, 2017, 11:00:58 pm
Has FL212 been deleted?
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on March 06, 2017, 09:21:40 pm
Has FL212 been deleted?

Yes.
Title: Re: usafl: Florida State Highways
Post by: CharlotteAllisonCDTG on March 06, 2017, 10:40:45 pm
Thank you for letting me know.  I saw that it was an error on my log file.  I went to the entry, and it had lots of red wording, but no actual content.  So, I didn't know what had happened.
Title: Re: usafl: Florida State Highways
Post by: Eth on May 13, 2017, 05:41:36 pm
Was finally getting around to adding some stuff to my list file from a FL trip last year and came upon an issue that it doesn't look like anyone else has yet raised: FL 404 should be extended west to I-95 at waypoint 188.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 18, 2017, 11:33:47 pm
Was finally getting around to adding some stuff to my list file from a FL trip last year and came upon an issue that it doesn't look like anyone else has yet raised: FL 404 should be extended west to I-95 at waypoint 188.

Will be dealt with when I get to that route in the overhaul process. ;)
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 19, 2017, 06:19:56 am
Just cleaned up FL-228 to FL-277 (https://github.com/TravelMapping/HighwayData/pull/1263). 8)
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 27, 2017, 01:00:12 pm
Need to add:
FL 399 (this only consists of 1/3 mi of the route between US 98 and just short of the bridge to the barrier island, the rest being CR 399, but it is (https://goo.gl/maps/7VB2aQ2G1pA2) signed (https://goo.gl/maps/LJW8hqa6Eqz))

That one is debatable.  Normally, for us to consider the route as 'signed', there needs to be at least a shield on the mainline (couldn't find one).  So this one might not make the cut.

After doing some more research on FL-399, the route (even though it's signed on the BGS's on US-98) doesn't even leave the interchange with US-98, and thus, will not make the cut.  GIS data shows it ending right @ the gore point, and there this Begin/End Maintenance sign (https://goo.gl/maps/YSgpKxNaaNL2) in the same location.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 27, 2017, 01:46:27 pm
Was finally getting around to adding some stuff to my list file from a FL trip last year and came upon an issue that it doesn't look like anyone else has yet raised: FL 404 should be extended west to I-95 at waypoint 188.

Will be dealt with when I get to that route in the overhaul process. ;)

Alright, had some time to research this one, and no, FL-404 will not be extended to I-95.  There are several reasons why.
1. GIS data doesn't show it going past CR-509.
2. While the BGS's on I-95 mention it, it seems FDOT goof and forgot to add the 'TO' text with it.  Proof of this is EB trailblazer on the 'supposed' route, here (https://goo.gl/maps/fCRG43MQ1Lx).  All signage going WB that I could find is just "TO I-95" shields.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 27, 2017, 04:32:14 pm
FL-281 to FL-414 (https://github.com/TravelMapping/HighwayData/pull/1280) have just been updated. 8)
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 30, 2017, 12:21:39 pm
And now FL-415 to FL-536 (https://github.com/TravelMapping/HighwayData/pull/1288) have just been updated. 8)
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 31, 2017, 08:26:37 am
I've been buried at work but here and there have been looking through the higher number routes.  Unfortunately I lost half of my notes, but I still have these:

Routes to delete:
FL 546 (TO US 92, US 92, not signed)

Just hit this route in my cleanup progress, and it IS signed on it's non US-92 alignment. [1] (https://goo.gl/maps/nXDC7z3Voan) [2] (https://goo.gl/maps/ERGGqgJ3irk)

Not sure why it isn't signed from I-4, but it is at least signed from US-92, and will be included between I-4 & US-92.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on June 02, 2017, 12:49:29 am
FL 594 (I-175)

FL594 is signed between FL687_S and FL687_N (https://www.google.com/maps/@27.7669187,-82.6384322,3a,50.3y,206.63h,86.51t/data=!3m6!1e1!3m4!1sK6KrTJ6NMfZcXkB7IoUgFA!2e0!7i13312!8i6656?hl=en)

Alright, finally far enough along do deal with this route.

Now, we know the route is signed (only going WB) between the two directions of FL-687 (hidden US-92 per FDOT GIS data, but that's a different story) since it's on separate one-way roads.  Now, as it stands, FL-687 has a 'centered' point for FL-594, but FL-594 has separate points for each way of FL-687.  So, do we just chalk this up to being one route that will not be shown in the "Intersecting highways shown" feature when it comes to TM, or should we try to figure out how to somehow sync the two for at least one of the intersections on FL-687?

If I wanted to have the two routes synced to any of the two ways of FL-687, I'd sync it with 4th Street so that I-175 can be included properly in this clusterfuck since FL-594 is the hidden number for it.

Once we can decide how to deal with FL-594, I'll get another batch of fixed routes ready to upload to the site.

=====

As for FL-595, I think keeping it between US-92 & US-19 would be the best solution since at several cross streets per StreetView, there is still signage for it (including at US-19's intersection).  If later all that signage gets replaced with US-19 Alternate signage, then we can consider axing that part of the route too to the 'hidden' land of unsigned FL state routes. lol.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on June 02, 2017, 05:44:13 am
FL707.  This one is weird.  On the delete side:  It's not in the FLDOT shapefiles.  And it's signed as CR707 in downtown Stuart.  However, in the streetview, there are multiple FL 707 shields north of the drawbridge up to "TO US 1"/NW Wright Blvd.

Between June '15 (https://goo.gl/maps/reKBLP5cQ432) & Sept '16 (https://goo.gl/maps/195fC8QiHAm), FL-707 shields were removed from around the intersection of Wright Blvd & Dixie Hwy per StreetView.  Would be assuming that the remaining ones around the bridge have been removed as well.  Though Sept '16 imagery on US-1 still shows a few FL-707 shields (https://goo.gl/maps/K6dqqaU84CH2) for the SB ramp.

So, with this evidence, and with it no longer being in the GIS data, FL-707 will be axed.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on June 03, 2017, 04:28:59 am
FL750:  The route was extended west from FL291 to US29, and that's what's in the shapefiles.  However, there is currently no FL750 signage that I could find west of FL291, including with the interchange with I-110. 

January '17 StreetView shows a pair of FL-750 shields between I-110 & FL-291 (also still seen going back as far as June '13).  However, April '16 shows nothing between I-110 & US-29.  So, for the moment, I'll at least extend it to I-110.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on June 03, 2017, 11:51:38 am
And now FL-539 to FL-802 (https://github.com/TravelMapping/HighwayData/pull/1303) have just been updated and the first new routes above 802 have also been added in ages. ;D
Title: Re: usafl: Florida State Highways
Post by: Jim on June 03, 2017, 01:13:32 pm
And now FL-539 to FL-802 (https://github.com/TravelMapping/HighwayData/pull/1303) have just been updated and the first new routes above 802 have also been added in ages. ;D

That's worthy of a site update.  I'll launch one now.
Title: Re: usafl: Florida State Highways
Post by: Jim on June 03, 2017, 09:44:30 pm
Minor items: FL 50's points at I-75 and I-4 don't need exit numbers.
Title: Re: usafl: Florida State Highways
Post by: JJBers on June 04, 2017, 11:57:24 pm
Any eta dates yet? I have a lot of mileage on this system.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on June 05, 2017, 09:53:45 am
Any eta dates yet? I have a lot of mileage on this system.

No ETA...  I work on this when I have the free time.  Just was lucky enough to have the time to finally get everything old up-to-date pretty much.  Now comes the time of creating new files which takes a little longer to do.
Title: Re: usafl: Florida State Highways
Post by: yakra on June 07, 2017, 01:48:24 pm
Now, we know the route is signed (only going WB) between the two directions of FL-687 ... since it's on separate one-way roads.
WB is a typo for EB, I presume.

Now, as it stands, FL-687 has a 'centered' point for FL-594, but FL-594 has separate points for each way of FL-687.
Aah, I see that FL687 has changed (https://github.com/TravelMapping/HighwayData/commits/master/hwy_data/FL/usafl/fl.fl687.wpt) since you wrote your post. K. Moving on...

So, do we just chalk this up to being one route that will not be shown in the "Intersecting highways shown" feature when it comes to TM, or should we try to figure out how to somehow sync the two for at least one of the intersections on FL-687?

If I wanted to have the two routes synced to any of the two ways of FL-687, I'd sync it with 4th Street so that I-175 can be included properly in this clusterfuck since FL-594 is the hidden number for it.
Looks like this is what you did. Yeah man, I'm on board with your solution. For the (graphing) reasons you cited, as well as...
Well, consider FL594 as a bit of an (*ahem*) operational part of the couplet, paired with the northbound alignment of FL687 on 3rd St. If the 175-594-687 corridor were a single route here that turned a corner, that's where I would put the waypoint.  Way I look at things, it's about optimal from the visual/graphing/logical/what-have-you standpoint.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on June 08, 2017, 03:32:57 am
Minor items: FL 50's points at I-75 and I-4 don't need exit numbers.

I-4's is because it's synced label wise with US-17 & US-92.

I'll fix the I-75 one.
Title: Re: usafl: Florida State Highways
Post by: yakra on June 09, 2017, 12:53:15 am
I-4's is because it's synced label wise with US-17 & US-92.
Ah, but that doesn't quite determine it. US202/ME9/ME137 have 2 "PondRd"s and one "PondRd_Alb". Having properly done point labeling in the context of the route being mapped wins out over syncing labels "verbatim" with other routes.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on June 10, 2017, 12:27:09 pm
I-4's is because it's synced label wise with US-17 & US-92.
Ah, but that doesn't quite determine it. US202/ME9/ME137 have 2 "PondRd"s and one "PondRd_Alb". Having properly done point labeling in the context of the route being mapped wins out over syncing labels "verbatim" with other routes.

Well, I personally try to keep the labels synced as much as possible for states I have control of when dealing with multiplexes. lol.
Title: Re: usafl: Florida State Highways
Post by: yakra on June 11, 2017, 04:43:38 am
Hm. Style guide sez don't use exit numbers when there's only one junction; that would overrule syncing labels between files. I'm with Jim here.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on June 11, 2017, 04:48:24 am
Hm. Style guide sez don't use exit numbers when there's only one junction; that would overrule syncing labels between files. I'm with Jim here.

But US-17 & US-92 do have a few junctions with I-4.  That's what I was trying to keep FL-50 synced with them and make it easier to just repair a block of data in the future if I needed to.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on July 01, 2017, 01:56:51 am
Just submitted FL-808 to FL-818 (https://github.com/TravelMapping/HighwayData/pull/1419).
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on July 10, 2017, 04:57:14 am
Just submitted FL-820 to FL-838 (https://github.com/TravelMapping/HighwayData/pull/1434).
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 05, 2017, 07:28:47 am
Just submitted FL-842 to FL-909 (https://github.com/TravelMapping/HighwayData/pull/1513).

~30 more routes to go!
Title: Re: usafl: Florida State Highways
Post by: SSOWorld on August 05, 2017, 08:52:10 am
Is there any map left? (I didn't look for myself ;) )
Title: FL 243
Post by: ntallyn on August 13, 2017, 08:22:03 pm
FL 243 has been extended to Pecan Park Rd. It heads due north from FL102 to Owens Road and then in a northeastern direction, meeting with Pecan Park Rd (the east-west portion) at its current intersection with Bainebridge Rd. The routing is visible on the satellite view in the HB.
Title: Re: FL 243
Post by: rickmastfan67 on August 13, 2017, 10:35:42 pm
FL 243 has been extended to Pecan Park Rd. It heads due north from FL102 to Owens Road and then in a northeastern direction, meeting with Pecan Park Rd (the east-west portion) at its current intersection with Bainebridge Rd. The routing is visible on the satellite view in the HB.

That's nuts.  I tried with the Satellite view on Google's main web page, and I didn't see the new highway, but do in the version we get served in the HB.

But is it really posted as FL-243? GIS data agrees that it is, but I'd like some proof first.

At least adding in the 'northern' most part of it into OSM (so I can get the coordinates) will be easy, as over half the route is shown on Bing Sat imagery.
Title: Re: usafl: Florida State Highways
Post by: ntallyn on August 17, 2017, 10:02:28 pm
It really is posted. I was on my bicycle in a group, so I couldn't stop for a photo, but I did see a marker northbound, as well as one on eastbound Pecan Park indicating that FL 243 headed south from the intersection. I'll be at the airport in a couple of weeks and I'll try to remember to get a few photos.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 18, 2017, 04:38:33 am
It really is posted. I was on my bicycle in a group, so I couldn't stop for a photo, but I did see a marker northbound, as well as one on eastbound Pecan Park indicating that FL 243 headed south from the intersection. I'll be at the airport in a couple of weeks and I'll try to remember to get a few photos.

Cool beans.  I've already added the new segment of FL-243 into OSM (https://www.openstreetmap.org/changeset/51104770) so I can get the coordinates for the file here. :)

Kinda surprised that FDOT didn't take over the segment of Pecan Park to I-95 so that they could have a continuously signed route.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 18, 2017, 05:52:25 am
Ok, here's an interesting case with a route that I just came up upon that I would like some opinions on.

==
http://www.openstreetmap.org/?lat=25.847949&lon=-80.209162

FL-934 happens to have a segment that's 'divided' between two different streets.  Normally, we just center between the two and call it a day (because normally they are one-way pairs).  Well, this isn't the case here.  One street is 2-way (NW 79th St), and the other one is one-way WB (NW 81st St/NW 82nd St).  Well, normally, DOT's would only sign one of the two roads with WB shields.  However, FDOT is signing BOTH roads with WB shields at a few intersections (US-441 @  NW 81st St (https://goo.gl/maps/sqCfPjMnjEC2) & US-441 @  NW 79th St (https://goo.gl/maps/EtysGhKeG8R2)), & along both roads themselves.

So, I have 2 ideas to deal with this.
1. Create a 'separate' file for NW 81st St/NW 82nd St and keep the mainline on NW 79th St.  Fixes would be required for the US-441 & US-1's files since it's 'centered' for both of them.  Keep the original label location 'hidden' and then add 2 new labels for each separate intersection (maybe w/ labels like FL934_79th/FL934_81st?).  Selecting a 'city' name for the 81st/82nd one might be tricky as well.
2. Have the route just 'centered' between the two roads and ignoring the separate 'WB' road.  A fix would be required for I-95, as it's already split with points for each road (7 & 7A).  Would 'merge' both points together at the center point and keep 7 shown, and hide 7A (if in use, deleted if not).

Option 2 would be the easiest to implement, as it would only affect one 'active' route, however, Option 1 would be the more accurate for the site since the route is posted WB on both roads (& the GIS shows both roads).

Opinions please.
Title: Re: usafl: Florida State Highways
Post by: yakra on August 18, 2017, 03:32:36 pm
God man, these cases are annoying.

I'd go with Option 2.
Signage (https://www.google.com/maps/@25.8480439,-80.1725075,3a,27.2y,275.36h,93.34t/data=!3m9!1e1!3m7!1s9RqaN6bucEWL1P9jn9v5tw!2e0!7i13312!8i6656!9m2!1b1!2i41) at the WB split at the E end is suggestive of one of those one-way "truck routes" located on one half of its parent route (confused yet?). I left a theoretical NH4TrkDov out of the HB for these reasons. (http://tm.teresco.org/forum/index.php?topic=2090.msg6715#msg6715)
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 19, 2017, 06:15:23 am
God man, these cases are annoying.

I'd go with Option 2.
Signage (https://www.google.com/maps/@25.8480439,-80.1725075,3a,27.2y,275.36h,93.34t/data=!3m9!1e1!3m7!1s9RqaN6bucEWL1P9jn9v5tw!2e0!7i13312!8i6656!9m2!1b1!2i41) at the WB split at the E end is suggestive of one of those one-way "truck routes" located on one half of its parent route (confused yet?). I left a theoretical NH4TrkDov out of the HB for these reasons. (http://tm.teresco.org/forum/index.php?topic=2090.msg6715#msg6715)

Yeah, I know, right? lol.  Yeah, I've been thinking the last 24h that Option 2 would be the best we could do, as it does future proof us in case for some odd reason, they get rid of the WB lane on NW 79th St.

The '7' point on I-95 is in use, but 7A isn't.  So, just centering 7 between the two roads should work perfectly.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 23, 2017, 09:00:19 am
Sending usafl to preview land. :)  Just submitted the last files for routes FL-915 to FL-9336 to allow this to happen. :D

https://github.com/TravelMapping/HighwayData/pull/1555
Title: Re: usafl: Florida State Highways
Post by: yakra on August 23, 2017, 12:24:11 pm
BOOM!
The first usafl post in the CHM forum was dated Sat Jul 25, 2009. So it's old enough to buy a... MAD magazine?
Great to see it hitting this milestone. I'll have to dust off the .list file I made for my parents and see what I can uncomment.
Title: Re: usafl: Florida State Highways
Post by: Jim on August 23, 2017, 04:26:52 pm
I'll definitely be running an update tonight to get this in.  Thanks for the huge amount of work to get it this far!
Title: Re: usafl: Florida State Highways
Post by: Jim on August 23, 2017, 11:23:24 pm
usafl now in preview on site!  Great to see a 1000-mile bump in my stats, and I still have a bunch of waypoint label errors to fix in my list file.
Title: Re: usafl: Florida State Highways
Post by: oscar on August 24, 2017, 10:43:10 am
Just starting to munch through my rough draft list file entries.

Starting at the end, but otherwise in no particular order:

FL9336 -- EveNatPk => EveNP or EveNatPark (prefer the first, NP is our standard abbrev for National Park; while Pk is used as an abbrev for other words like Pike); also need to synch coordinates with FL9336 point in fl.mainparkrd in the usanp preview set.
Title: Re: usafl: Florida State Highways
Post by: yakra on August 24, 2017, 01:47:11 pm
EveNP seconded.
Title: Re: usafl: Florida State Highways
Post by: Jim on August 24, 2017, 07:57:02 pm
I suggest a point on FL 776 at the entrance to Charlotte Sports Park.
Title: Re: usafl: Florida State Highways
Post by: mapcat on August 24, 2017, 10:21:37 pm
Thanks for getting this set to preview! The only error I've found so far is that the FL785 point on FL72 should be FL758.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 25, 2017, 05:52:03 am
Just starting to munch through my rough draft list file entries.

Starting at the end, but otherwise in no particular order:

FL9336 -- EveNatPk => EveNP or EveNatPark (prefer the first, NP is our standard abbrev for National Park; while Pk is used as an abbrev for other words like Pike); also need to synch coordinates with FL9336 point in fl.mainparkrd in the usanp preview set.

Fixed.

I suggest a point on FL 776 at the entrance to Charlotte Sports Park.

Done.

Thanks for getting this set to preview! The only error I've found so far is that the FL785 point on FL72 should be FL758.

Fixed.

https://github.com/TravelMapping/HighwayData/pull/1560
Title: Re: usafl: Florida State Highways
Post by: ntallyn on August 27, 2017, 03:36:51 pm
FL228 appears to have an extra shaping point between I-95(353A) and I-95(353B), which is breaking the concurrence with I-95.

FL243 has points for PeaParkRd_N and PeaParkRd_S. These should be PecParkRd_N and _S.

Also, it appears that FL 9336 is ordered between FL933 and FL934, instead of after FL997. Is this because the system treats it like 933A (or something like that)?

After lots and lots of lines in Florida, those are the only things I saw!
Title: Re: usafl: Florida State Highways
Post by: Duke87 on August 27, 2017, 06:57:58 pm
Also, it appears that FL 9336 is ordered between FL933 and FL934, instead of after FL997. Is this because the system treats it like 933A (or something like that)?

Sort of.

It's because the system sorts routes alphabetically, not numerically. To compensate for this it has long been standard practice to zero-pad routes up to three digits (hence, for example, US 1 having a URL ending in "fl.us001"). If not for this zero padding, you would also see things like 93 come between 929 and 930. However since we don't zero-pad up to 4 digits, 9336 comes alphabetically between 933 and 934. (fl.fl933, fl.fl9336, fl.fl934).

This is also why all of the A1As are at the end of the list - A comes alphabetically after 9.
Title: Re: usafl: Florida State Highways
Post by: oscar on August 31, 2017, 09:38:48 pm
I've finished munching through my draft list file entries, to make corrections as needed and add them to the list file I submitted earlier today.

There were a few routes not in the HB, the first two of which I think were in the HB but no more. I commented out those lines. What happened to them, especially if they are now in the HB under a different number?

FL 55
FL 408Spr
FL 913 -- my notes had this as possibly unsigned

Also, for the two A1A segments in the Jacksonville region, MayFer => MayFry (we've been using Fry as abbrev for Ferry pretty regularly).
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 31, 2017, 10:17:51 pm
FL 55
FL 408Spr
FL 913 -- my notes had this as possibly unsigned

FL-55 = hidden route under 3 different US highways.
FL-408 'spr' = completely torn up, and no longer exists.  Was a spur from FL-408 to FL-417 & even had it's own interchange in-between them, but was removed when they added the 'missing' ramps at the direct interchange for both routes.
FL-913 = hidden.  Checked the entire area of it's SR status in StreetView, and couldn't find even one shield.
Title: Re: usafl: Florida State Highways
Post by: bhemphill on August 31, 2017, 10:27:36 pm
Should FL60 have a point at 27th Ave in Vero Beach, since 27th Ave turns into FL607 eventually to the south?
Title: Re: usafl: Florida State Highways
Post by: yakra on September 01, 2017, 12:31:51 am
FL-408 'spr' = completely torn up, and no longer exists.  Was a spur from FL-408 to FL-417 & even had it's own interchange in-between them, but was removed when they added the 'missing' ramps at the direct interchange for both routes.
*checks Historic Aerials*
Wow... that whole operation seems kind of a wasted effort...
Title: Re: usafl: Florida State Highways
Post by: yakra on September 01, 2017, 02:22:31 am
Should FL60 have a point at 27th Ave in Vero Beach, since 27th Ave turns into FL607 eventually to the south?
Similarly (though on a smaller scale), Recommend a point on FL39 at Alexander St, a bit south of KniGriRd, for its connection south to FL39A.

FL986: 72ndSt_W endpoint label? As Oscar recently said re CA162, "I prefer intersecting roads/boundaries over continuation road names/numbers, the former better defines where the ... route ends)" Maybe FLTpk, even if there's no actual interchange there?

US41: FL80/82 -> FL82?
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 01, 2017, 02:32:25 am
FL-408 'spr' = completely torn up, and no longer exists.  Was a spur from FL-408 to FL-417 & even had it's own interchange in-between them, but was removed when they added the 'missing' ramps at the direct interchange for both routes.
*checks Historic Aerials*
Wow... that whole operation seems kind of a wasted effort...

Well, the 'spur' was the original alignment of FL-408 before it was extended farther east.
Title: Re: usafl: Florida State Highways
Post by: yakra on September 01, 2017, 03:57:27 am
Still though, seems a waste to demolish it. It was more direct that the "direct" ramps farther east, and it provided another local access point that is now missing.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 13, 2017, 03:37:24 am
FL228 appears to have an extra shaping point between I-95(353A) and I-95(353B), which is breaking the concurrence with I-95.

FL243 has points for PeaParkRd_N and PeaParkRd_S. These should be PecParkRd_N and _S.

Fixes submitted.

Also, for the two A1A segments in the Jacksonville region, MayFer => MayFry (we've been using Fry as abbrev for Ferry pretty regularly).

Done.

https://github.com/TravelMapping/HighwayData/pull/1605
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 14, 2017, 10:03:39 pm
Quote from: emory
A segment of SR 12 that runs through Quincy has been relinquished to the city. Specifically the portion running from SR 269 to US 90 along E. King Street. Rather than gap the route, SR 12 now runs south down the entirety of SR 269/Quincy Bypass and co-signs with US 90/SR 10 until it hits its former routing. http://www2.dot.state.fl.us/Straight-linesOnlineGIS/blank.aspx?docId=106084

http://www.aaroads.com/forum/index.php?topic=2017.msg2258664#msg2258664

Not sure if this means that FL-269 has been decommissioned, or will be co-signed with FL-12 there.  Will have to look @ the GIS data later.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 26, 2017, 08:32:02 am
Just took a look at the datacheck page, and all but 4 of the errors are 'distance' errors.  Those shouldn't be issues, but I'll take a look later and see if I might be able to find points around the ~5 mark in between and nip them that way.

Otherwise, the other 4 are 3 'self ref' and 1 sharp angle.  All are FPs (just verified that).  So, have submitted them to the FP list (https://github.com/TravelMapping/HighwayData/pull/1628).
Title: Re: usafl: Florida State Highways
Post by: Jim on January 01, 2018, 08:19:26 pm
By email from user aaroads:

Quote
Thinking about another change I wanted to mention, the alignment of FL 39 in Hillsborough County shifted from I-4 westward onto the new Alexander Street alignment. Old FL 39 north from I-4 was supposed to be designated as CR 39, but now it is signed as FL 39A. FL 39A was previously assigned along Alexander Street south from I-4. This is now part of FL 39 as well, with FL 39 wrapping around the southwest side of Plant City. The previous alignment for FL 39 south from I-4 through Downtown Plant City was turned over to the city for maintenance and decommissioned.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on January 04, 2018, 05:08:54 am
By email from user aaroads:

Quote
Thinking about another change I wanted to mention, the alignment of FL 39 in Hillsborough County shifted from I-4 westward onto the new Alexander Street alignment. Old FL 39 north from I-4 was supposed to be designated as CR 39, but now it is signed as FL 39A. FL 39A was previously assigned along Alexander Street south from I-4. This is now part of FL 39 as well, with FL 39 wrapping around the southwest side of Plant City. The previous alignment for FL 39 south from I-4 through Downtown Plant City was turned over to the city for maintenance and decommissioned.

FDOT GIS data is confirming this finally.  This was one area where I was still a tad confused earlier with.  So, now fixing it will be a piece of cake.

=====
Also will still have to do reroute of FL-12 onto FL-269 later up in Quincy, while leaving FL-269 'for now', as I have no proof 269 will become unsigned yet.

EDIT: Now submitted. (https://github.com/TravelMapping/HighwayData/pull/1806)
Title: Re: usafl: Florida State Highways
Post by: oscar on April 07, 2018, 08:40:06 am
In the Orlando area:

-- the main and Mt. Plymouth segments of FL 429 are now connected by a new segment, so the route files can be merged into a single route

-- branching from the new segment is a new route, FL 453 (also a toll road), between FL 429 and FL 46

Both additions are shown in OSM/Mapnik, and shown as open if you zoom in enough.

I drove both additions, on my way down to south Florida. I don't recall seeing any exit numbers, which doesn't mean they aren't there.
Title: Re: usafl: Florida State Highways
Post by: oscar on April 11, 2018, 07:32:39 am
A few more comments, but I'm still in south Florida so more might be forthcoming:

-- FL 925 appears to be signed only on the northbound one-way frontage road along NB I-95 (NW 3rd Ave.). It has a regular reassurance marker, and an End sign assembly at NW 8th St. (where the HB places FL 925's north end). But there appear to be no route markers on the southbound frontage road on the other side of I-95 (NW 3rd Ct.). The waypoints in the middle of I-95 seem to assume that FL 925 includes both frontage roads, but are you sure it doesn't include only the northbound frontage road?

-- FL 811 (Oakland Park)'s north endpoint is labeled DixHwy_N. Since that FL 811 segment is Dixie Hwy both north and south of that endpoint, the label doesn't indicate the point on Dixie Hwy where the state route ends. Also, the CHM instruction manual says it is not appropriate to use the continuing road in the label, since the road name doesn't change where the route ends. The endpoint appears to be at the northern city limit of Fort Lauderdale/southern city limit of Pompano Beach, so For/Pom or PomBeaLim would be better endpoint labels.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on April 15, 2018, 08:39:33 pm
In the Orlando area:

-- the main and Mt. Plymouth segments of FL 429 are now connected by a new segment, so the route files can be merged into a single route

-- branching from the new segment is a new route, FL 453 (also a toll road), between FL 429 and FL 46

Both additions are shown in OSM/Mapnik, and shown as open if you zoom in enough.

I drove both additions, on my way down to south Florida. I don't recall seeing any exit numbers, which doesn't mean they aren't there.

Exit numbers are shown here.
https://www.aaroads.com/guides/fl-429-north-wekiva-pkwy/

Anyways, now submitted (https://github.com/TravelMapping/HighwayData/pull/1963).
Title: Re: usafl: Florida State Highways
Post by: oscar on April 15, 2018, 09:06:12 pm
Another one for you:  FL404 extended west to I-95 (I drove it today, OSM/Mapnik shows it).

Still one more morning in north Florida, so you're not safe yet. Plus some lesser comments on point labels I'll save until I'm back home.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on April 15, 2018, 09:42:17 pm
Another one for you:  FL404 extended west to I-95 (I drove it today, OSM/Mapnik shows it).

FDOT GIS data as of 04/07/18 does not acknowledge it.

Last time I checked into this, only signage was 'TO' banners.
See: http://tm.teresco.org/forum/index.php?topic=323.msg6059#msg6059
Has this changed?
Title: Re: usafl: Florida State Highways
Post by: oscar on April 15, 2018, 09:49:09 pm
I only drove the supposed FL 404 extension westbound. No FL 404 signage WB west of CR509, though I did see (in my rearview mirror) the BGS on SB I-95 that you mentioned in your previous post.

So I didn't see anything new.
Title: Re: usafl: Florida State Highways
Post by: oscar on April 18, 2018, 04:40:18 pm
Some last comments on endpoints, now that I'm back home.

FL 401: North endpoint is labeled SamCPhiPkwy, for the continuation road. But at that point, that the road changes names is not obvious to travelers. What is obvious is that you've crossed the property line of a military base, with sentry stations right ahead so you need to be looking for a turnaround point before the sentries (which I found, and used). I suggest SamCPhiPkwy => CapeCanAFS.

FL 607: North endpoint is labeled 27thAve. That's where, if a traveler looks carefully, the road name changes from Emerson Avenue to 27th Avenue. But even a careless traveler will notice the St. Lucie/Indian River county line signs. Assuming that FL 607 ends at the county line, rather than North Blvd. or 25th St. SW, I suggest 27thAve => StLuc/IndRiv or StL/Ind.

FL 716: West endpoint is labeled PortSLBlvd_W, even though the road doesn't change name there, which the instruction manual suggests the continuation road should not be used (in similar circumstances, when I couldn't come up with a better endpoint name, I've used "End"). But the real rub is that there is a regular (not End) FL 716 marker in each direction between that point and the next intersection west of the Turnpike, Cameo Blvd. I saw no FL 716 markers west of Cameo Blvd. Maybe CamBlvd would be the appropriate endpoint and label?
Title: Re: usafl: Florida State Highways
Post by: neroute2 on April 21, 2018, 04:26:05 pm
A few comments/corrections:
As far as I know, as-maintained SR 7's current north end is at SR 704, despite signage continuing north. But this may have changed recently.
SR 15 (Okeechobee)'s north end is weird due to it being a normally-unsigned route. There is reassurance (http://www.google.com/maps/@27.1222133,-80.6774213,3a,75y,332.96h,88.9t/data=!3m6!1e1!3m4!1sMpBQVatedZE0uNkgCjEUCA!2e0!7i13312!8i6656) at the Martin-Okeechobee county line. So maybe we should end it (and SR 700) there, which is the FDOT district boundary.
SR 15 (Orlando): GolRd -> OldGolRd, GolRdExt -> GolRd (hopefully this doesn't break anything)
SR 19: CR452 (not signed here) -> LakeEusDr (this is also on SR 44 and US 441)
SR 50: HanRd should be added between US27 and CR455. This is a major Turnpike connector now that exit 278 is open. CR535 should be added between CR545 and DanRd. Maybe BluAve (former SR 439 north) between CR439 and FL408(1). FL527_S should be FL527_N. MagBlvd should be added between US17/92_N and BenRd to match SR 526 and SR 15 (Orlando). ClaSt should be moved west to CR13.
SR 60: the west end is a bit east of the circle, but I don't remember the details. CR501 should be added between CR1 and US19.
SR 84 extends a block east of US 1 (unless it's been truncated recently).
SR 700: see SR 15
Title: Re: usafl: Florida State Highways
Post by: neroute2 on April 21, 2018, 05:30:33 pm
I think SR 102 continues west to the airport.
Why is SR 109 split in two? The overlap with SR 115 is signed 'to' (http://www.google.com/maps/@30.3272627,-81.597023,3a,15y,26.56h,89.04t/data=!3m7!1e1!3m5!1sFpjGfQEkxzMVvFqGvschSg!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DFpjGfQEkxzMVvFqGvschSg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D170.6224%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), and I know similar overlaps are included in TM. If I'm not mistaken, there's actually been a reconfiguration so both directions of SR 109 now stay on the frontage road.
Does SR 112 actually continue west of FL953_N?
SR 114 is signed (at least on I-95). Waypoints are FraSt (if we're counting interchange-related stubs like that), I-95, and Blvd.
Why is SR 267 split in two?
SR 405 is signed east from US1_S to the end (https://www.google.com/maps/@28.5276624,-80.7811155,3a,75y,119.68h,75.49t/data=!3m6!1e1!3m4!1s8VokGU-L3B7T0opBpe2mWA!2e0!7i13312!8i6656) at the JFK Space Center.
SR 414 has new interchanges between FL434 and I-4: GatDr, MaiSumBlvd, and KelRd (Lake Destiny Road will no longer have any direct access when construction is done). HopeRd should be WymRd. There's also a new exit 4B at Marden Road.
SR 419/434: GarAve should be moved west to TusRd.
SR 423: CurSt -> ChuSt, WyhRd -> WymRd
SR 426: move OakHillDr west to WinSprBlvd?
SR 436: the south end is north of CargoRd at the canal bridges.
SR 482: as with other similar routes that end at interchanges with nearby roads (e.g. SR 421), the route extends west of I-4 to TurLakeRd.
SR 524 continues east to SR 528.
SR 526: BurAve -> BumAve
SR 527: OraAve -> LakeviewSt or GarAve or something that isn't actually SR 527
SR 536: signs continue west of I-4 to the WDW property line (marked on OSM)
SR 551: GolRdExt -> OldGolRd
SR 586, SR 590, SR 686, SR 688: add CR501?
SR 594 extends west to the eastbound end of I-175.

US 17/92: add CR580 in Haines City, CR54 -> RonReaPkwy, CR535 -> HamBroRd, CR531 -> PleHillRd (neither CR 535 nor CR 531 is signed or recognized by the county), US17/92Trk_S -> FL423, FL414/17Trk -> FL414 (these are much better signed than the truck routes), DirDr -> CR4162, SaxBlvd -> CR4146
US 17/92/441: CR527A -> LanRd
US 17: move KatSt one block north to CR4053
US 27: add CR17_HaiCity, RonReaPwky -> RonReaPkwy, add CROld50 in Minneola
US 192: AvaRd -> CR545_N, CR545 -> CR545_S, KisParkRd -> OCanCRd (to match US 441)
US 192/441: CR523_N -> CR523
US 441: add CR437_N and CR437_S just south of SR 429, CR452 -> LakeEusDr, CR44_E -> CR44LegA, CR44_W -> CR44
US 17/92 Truck (Orlando): WyhRd -> WymRd_S, HopeRd -> WymRd_N
Title: Re: usafl: Florida State Highways
Post by: neroute2 on April 27, 2018, 10:32:32 pm
SR 997 has been truncated (the south end is now 8thSt): http://www.aaroads.com/forum/index.php?topic=2017.msg2322548#msg2322548
Title: Re: usafl: Florida State Highways
Post by: SSOWorld on July 19, 2018, 07:08:26 am
FL US1AltJac FL115_S  There is only one connection.

Also, not sure about this but the Hart Expressway might be a popular route.  It branches between US1Alt and US90 without a number (signed at least).  US1Alt (Jacksonville) follows it then turns south two WPs short of the end.

In general there are many Waypoints that could be combined into one (or left alone, whatever) thanks to interchange ramps that go way apart (say the above Hart Expressway or for FL836 at the turnpike's  Exit 26. (WPs 26 and 26A)
Title: Re: usafl: Florida State Highways
Post by: Eth on August 18, 2018, 12:53:23 pm
Would it be reasonable to include waypoints at Sans Souci Blvd on FL922 and US1? It seems to be a well used connector between the two routes (and, selfishly, one that I used last time I was in the area, leaving me currently unable to claim any of FL922) that Google Maps routes you on by default if making the south-to-east movement.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on August 22, 2018, 09:40:18 am
FL US1AltJac FL115_S  There is only one connection.

This comes from the times that it was planned to include the full route of FL-115 (it's hidden there along US-1 Alt up to I-95).

Otherwise, US-1 Alt's file could use some label cleanup and some other minor fixes.

for FL836 at the turnpike's  Exit 26. (WPs 26 and 26A)

See: http://forum.travelmapping.net/index.php?topic=2549.msg10244#msg10244
Title: Re: usafl: Florida State Highways
Post by: Jim on September 08, 2018, 09:48:20 am
This system has been in preview for over a year.  Is it awaiting any further review before activation?
Title: Re: usafl: Florida State Highways
Post by: ntallyn on September 09, 2018, 10:09:16 pm
This system has been in preview for over a year.  Is it awaiting any further review before activation?

As I was driving down I-95 this afternoon, I saw that FL 9B was now open south of I-95 (apparently to CR 2209 [St. Johns Parkway], as the signs have a TO CR 2209 symbol). As I was already late for my appointment, I'll have to grab that section in a couple weeks when I go down that way again.

Never mind. I didn't see any mention of it in the discussion above, but I do see that the HB has the extension open.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on October 02, 2018, 01:13:42 pm
On FL50, CR439 should be CR439_S given this sign:
(http://i.imgur.com/69XgnMr.jpg)
Note that there is no other signage anywhere for CR 439 north (which is Bluford Avenue). A BluAve point should be added anyway, since it's a former state road.
Title: Re: usafl: Florida State Highways
Post by: Jim on December 03, 2018, 08:48:21 pm
From user skatcher by email:

I noticed a “confusing” waypoint on the .list name FL FL616. Waypoint 1 (CR587/N West Shore Blvd) is labeled as ShoBlvd. I noticed when West Shore Blvd crosses FL US92 and FL FL60 both those pages label the waypoint as CR587. I think from a consistency standpoint the Waypoint should be changed to CR587. If not, then at least change the waypoint to WShoBlvd as N West Shore Blvd becomes S West Shore Blvd south of FL60.
Title: Re: usafl: Florida State Highways
Post by: charliezeb on January 16, 2019, 07:30:20 pm
FL 590 (Clearwater) east end (waypoint 8) is listed as SunPoiRd, for Sunset Point Rd. But Sunset Point Rd becomes Main Street once it gets into Safety Harbor, which it does at McMullen Booth Rd (CR 611). Wondering if the waypoint should be redesignated MainSt, even if it would break the 7 of us (including myself) who have clinched the segment.
Title: Re: usafl: Florida State Highways
Post by: ntallyn on January 27, 2019, 06:34:49 pm
FL 243 now is listed on the BGS at the Pecan Park exit on I-95 (Exit 364). As the weather was bad, I couldn't see if there was a sign on Pecan Park Road itself (and there's still construction going on at the interchange; it may not be signed on Pecan Park yet anyway).
Title: Re: usafl: Florida State Highways
Post by: charliezeb on February 07, 2019, 07:05:29 pm
FL 998 has apparently been added to the system, Campbell Dr in Homestead between Krome Ave (FL 997) and Dixie Hwy (US 1). It's signed, and FL 997 is no longer signed between US 1 and FL 998. I clinched FL 998 this morning, after doing the (old) length of FL 997 yesterday. If someone can verify this with FDOT data, perhaps the routes can be added/modified.
Title: Re: usafl: Florida State Highways
Post by: formulanone on March 12, 2019, 09:37:35 pm
Thanks for all the work, everyone! I can't think of too many missing points. Would love to see a lot of former state roads, but I think the county system might be a bit too much esoteric detail, and not all counties sign them.

Here's FDOT's straight-line diagram on SR 998 ->
http://www2.dot.state.fl.us/straight-linesonlinegis/blank.aspx?docId=106280

Never mind, you can't access the SLDs directly.
https://fdotewp1.dot.state.fl.us/slogis/

Then select District D6, choose Miami-Dade, then scroll down to SR 998 (or roadway ID 87290000), and hit "Launch PDF".
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on April 23, 2019, 04:40:10 am
Going to start working thru all the previous posts over the next few weeks and address them post by post so we can hopefully get this finally activated.

However, I have at least pushed all changes related to the new FL-998, and cleaned up US-1 Alt in Jacksonville (which includes shortening FL-126 to Spring Park Road, as there's no signage for it to the East of it, and thus treating it as unsigned there & adding said point to US-1 Alt too).

https://github.com/TravelMapping/HighwayData/pull/2774
Title: Re: usafl: Florida State Highways
Post by: Markkos1992 on April 23, 2019, 06:55:52 am
Going to start working thru all the previous posts over the next few weeks and address them post by post so we can hopefully get this finally activated.

However, I have at least pushed all changes related to the new FL-998, and cleaned up US-1 Alt in Jacksonville (which includes shortening FL-126 to Spring Park Road, as there's no signage for it to the East of it, and thus treating it as unsigned there & adding said point to US-1 Alt too).

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

I am not sure if you wanted to do anything in regards to the linked post below.

http://forum.travelmapping.net/index.php?topic=2535.msg10905#msg10905

Checking it previously, I know that FL 228 is not signed along the freeway to US 90, but should it be included in some form based on it being a freeway?
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on April 24, 2019, 03:49:36 am
I am not sure if you wanted to do anything in regards to the linked post below.

http://forum.travelmapping.net/index.php?topic=2535.msg10905#msg10905

Checking it previously, I know that FL 228 is not signed along the freeway to US 90, but should it be included in some form based on it being a freeway?

I don't think adding it would be a problem, as long as I add the entire "Hart Expressway" (including US-1 Alt's part), as it would be 5 miles in length.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on April 24, 2019, 04:15:17 am
Some last comments on endpoints, now that I'm back home.

FL 401: North endpoint is labeled SamCPhiPkwy, for the continuation road. But at that point, that the road changes names is not obvious to travelers. What is obvious is that you've crossed the property line of a military base, with sentry stations right ahead so you need to be looking for a turnaround point before the sentries (which I found, and used). I suggest SamCPhiPkwy => CapeCanAFS.

Changed in my local copy.

FL 607: North endpoint is labeled 27thAve. That's where, if a traveler looks carefully, the road name changes from Emerson Avenue to 27th Avenue. But even a careless traveler will notice the St. Lucie/Indian River county line signs. Assuming that FL 607 ends at the county line, rather than North Blvd. or 25th St. SW, I suggest 27thAve => StLuc/IndRiv or StL/Ind.

Changed to "StL/Ind" in my local copy. *****

FL 716: West endpoint is labeled PortSLBlvd_W, even though the road doesn't change name there, which the instruction manual suggests the continuation road should not be used (in similar circumstances, when I couldn't come up with a better endpoint name, I've used "End"). But the real rub is that there is a regular (not End) FL 716 marker in each direction between that point and the next intersection west of the Turnpike, Cameo Blvd. I saw no FL 716 markers west of Cameo Blvd. Maybe CamBlvd would be the appropriate endpoint and label?

Found the 'East FL-716 (https://goo.gl/maps/5oQb44MJnrsyuP5a9)' shield you were referring to @ Cameo Blvd.
GIS data still says that the end is the edge of the bridges over the Turnpike.  However, because of that 'East' shield, I'm willing to extend it to Cameo Blvd due to the signage, & being a more logical end point.  Changed in my local copy.
Title: Re: usafl: Florida State Highways
Post by: yakra on April 24, 2019, 03:03:20 pm
StL/Ind
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on April 26, 2019, 08:31:45 am
A few comments/corrections:
As far as I know, as-maintained SR 7's current north end is at SR 704, despite signage continuing north. But this may have changed recently.

StreetView from June '16 does indicate 0 signs for FL-7 above FL-704.  Willing to shorten it to FL-704 till when/if any proof shows up that it is indeed signed North of there on the road itself.

SR 15 (Okeechobee)'s north end is weird due to it being a normally-unsigned route. There is reassurance (http://www.google.com/maps/@27.1222133,-80.6774213,3a,75y,332.96h,88.9t/data=!3m6!1e1!3m4!1sMpBQVatedZE0uNkgCjEUCA!2e0!7i13312!8i6656) at the Martin-Okeechobee county line. So maybe we should end it (and SR 700) there, which is the FDOT district boundary.

I checked around the intersection with FL-76 and couldn't find any signage for it (& FL-700).  It's weird that there's more signage for it well North of that intersection. So, you could say the signage in that district is hit-and-miss.  But I would have no problems extending both of them north to that county line.  Just figuring out what to label said point in US-98/441's files is the issue.  Guessing 'FL15/700' in the US files would work the best.

SR 15 (Orlando): GolRd -> OldGolRd, GolRdExt -> GolRd (hopefully this doesn't break anything)

Fixed.  Doesn't 'break' anything since the system is still in 'preview', and thus label changes can happen without warning and break list files since it's not required to keep a hidden label.

SR 19: CR452 (not signed here) -> LakeEusDr (this is also on SR 44 and US 441)

Fixed in all 3 files.

SR 50: HanRd should be added between US27 and CR455. This is a major Turnpike connector now that exit 278 is open. CR535 should be added between CR545 and DanRd. Maybe BluAve (former SR 439 north) between CR439 and FL408(1). FL527_S should be FL527_N. MagBlvd should be added between US17/92_N and BenRd to match SR 526 and SR 15 (Orlando). ClaSt should be moved west to CR13.

Wasn't aware a new exit has been opened on the Turnpike.  HanRd added to FL-50's file, as well as the new interchange to the Turnpike file.
CR535: Not going to add this one.  DanRd point is close enough.  Can't go around adding every single County route.  Especially since we're in an urban area right here, 2 miles is the normally recommended distance between points (unless it's routes we map or actual interchanges), and the distance currently between 'CR545' & 'DanRd' is 1.52 miles.
BluAve: Not going to add this one.  Same reasoning as CR535.
FL527_S: Staying as is, as I like to keep multiplexed routes the same label wise unless a duplicate label issue would arise.  Makes it easier to copy/paste any fixes that are needed between files.
MagBlvd: Agreed.  Added.
ClaSt: Done.  ClaSt removed, replaced with CR13 to the west.

SR 60: the west end is a bit east of the circle, but I don't remember the details. CR501 should be added between CR1 and US19.

GIS data agrees putting western end @ the western side of the bridge, first 'EB' FL-60 shield on the 'east' side of the bridge. Thus, adding a new point 'CauBlvd' at western end of the bridge as the starting point for the route.
CR501: Reasonable distance gap that it closes.  Added.

SR 84 extends a block east of US 1 (unless it's been truncated recently).

GIS data agrees, signage in the field doesn't agree (June/July '18 StreetView).  Will treat the east side 'block' as unsigned, and leave as is.

==

All changed are made in my local files at the moment.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on April 29, 2019, 05:16:01 am
I think SR 102 continues west to the airport.

GIS data shows FL-102 ending at the edge of the bridge overpass of FL-243.  Can't find any shields beyond that.  Plus for the longest time, the only shield that I was aware of for the route, was this one (https://goo.gl/maps/1aWBFcjzBJ8jCYSe8).  And I personally know that a shield had been there since at least 1996.  However, a new 'JCT FL-102' (https://goo.gl/maps/VyaCeZE72f8g3ZLS6) shield was added on the new extension of FL-243.

Plus, that entire area seems to be currently being reconfigured, especially the I-95 NB on/off ramps.  Plus it also looks like that they are installing a 'Michigan Left (https://goo.gl/maps/vner96gjWXwFMABt7)' here.  Not too sure how it's going to work with the two service roads on either side of Airport Road.  All I know is that the Airport Road/Duval Road intersection there has always been a pain to use.

Anyways, who knows, maybe some more FL-102 shields will be on the way once all the construction in that area is done.  Either way, as it currently stands, the route will stay as-is.

Why is SR 109 split in two? The overlap with SR 115 is signed 'to' (http://www.google.com/maps/@30.3272627,-81.597023,3a,15y,26.56h,89.04t/data=!3m7!1e1!3m5!1sFpjGfQEkxzMVvFqGvschSg!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DFpjGfQEkxzMVvFqGvschSg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D170.6224%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), and I know similar overlaps are included in TM. If I'm not mistaken, there's actually been a reconfiguration so both directions of SR 109 now stay on the frontage road.

Oh boy, this one has always pissed me off. lol.  To be honest, I was going to have FL-109A between Cesery Blvd because of all the '109A (https://goo.gl/maps/NjKreyqZv9W8Lb4T6)' shields that were on it (and then this point would have been mute).  However, it seems FDOT finally decided to put the proper '109 (https://goo.gl/maps/4pw8zmzJ3Zyhxdw18)' shields up in the last few years.

Anyways, at the 'dogbone' part of the 'western' interchange, they did recently change the signage to add a 'SOUTH FL-109 (https://goo.gl/maps/K2jzALRWp3g82Y439)' mention (it was previously a spot they mentioned which way to go for NB FL-109).  While that was making me lean to adding it, I followed the 'EB' service road and found this "JCT FL-109 (https://goo.gl/maps/xv6S4WRV2WBCXfSb7)" shield (formerly a 109A).  And then @ the intersection, I find a brand spanking new FL-109A shield (https://goo.gl/maps/xpXMAHnNGD97vpP46) with a 'left' (yes, a LEFT) arrow under it.  Somebody doesn't want the road to die......

Also, other signage @ University & FL-115 say 'TO FL-109 South (https://goo.gl/maps/bKt81XTtYEGrF4rVA)' which muddies the water some more.  Also, GIS show that 109 does have a gap here.  GIS says that the 'FL-109 Arl (http://travelmapping.net/hb/?units=miles&r=fl.fl109arl) segment should end South of FL-115 @ the intersection of University/Tanglewood (however signage in field doesn't support this part).

I'm honestly thinking of leaving it as-is, as we don't always consider the 'TO' signage as implied, and can't use an 'implied multiplex' defense here IMO because FL-115 doesn't use the Service Roads at all.  Sometimes there will be a gap.  Just happens unfortunately.

On a side note, I'll still have to correct the location of the 'UniBlvd_N' point, as that intersection has been move to the North some since the bridge for University there has been replaced and the intersection with Cesery had been reconfigured some.

Does SR 112 actually continue west of FL953_N?

GIS says yes.  Signage says yes. 1 (https://goo.gl/maps/NVPMxyi5o6vwpw8i8), 2 (https://goo.gl/maps/rXG6CNvjDFJ5mkfr7), & the 'BEGIN shield (https://goo.gl/maps/jwYvtqb1zPJwwEo96)', complete with a 0.0 MM in the background.  So, no changes needed here.

SR 114 is signed (at least on I-95). Waypoints are FraSt (if we're counting interchange-related stubs like that), I-95, and Blvd.

1 sign with shield still present going NB on I-95 as of December '18 (https://goo.gl/maps/7uKpuxQubr1Ckef87).  All other signs on I-95 say '8th Street' only.  No signage at the bottom of each ramp from I-95.  No signage along the road itself.  Considering route as unsigned (I remember back in the day when it WAS signed, but that was back when it continued all the way to US-1/17).  So, no changes here.

Why is SR 267 split in two?

'Curret' GIS agrees that there's no gap (though I thought I saw at one time the GIS data showing a gap with FL-20 only filling it).  Signage doesn't agree.  There is just a single 'TO' North FL-267 shield (https://goo.gl/maps/F6xUo3nDyDh8ede38) @ the 'southern' intersection, and no FL-267 'TO' signs on FL-20 at all going WB, just FL-20 shields.  Same thing happens going the other direction from the 'northern' intersection. Single 'TO' South FL-267 shield (https://goo.gl/maps/U5Awk39MzfHjq9SP7) on the route itself before the intersection (1 on FL-20 before the intersection (https://goo.gl/maps/4VrdmnJwSNKyqB6d8)), and no 'TO' South FL-267 signage going EB on FL-20.  Honestly makes this hard to make the 'implied multiplex' defense here without any 'TO' signage along the 'implied multiplex' itself.  I still could go either way on this one.  Anybody else have any opinions on this?

SR 405 is signed east from US1_S to the end (https://www.google.com/maps/@28.5276624,-80.7811155,3a,75y,119.68h,75.49t/data=!3m6!1e1!3m4!1s8VokGU-L3B7T0opBpe2mWA!2e0!7i13312!8i6656) at the JFK Space Center.

GIS says no (shows end @ the start/end of the ramps from US-1 on eastern side of the interchange, which would activate the '1-point per interchange' rule since it's inside of the interchange).  Signage on NB US-1 (https://goo.gl/maps/STJvgToaubjBEyaJ6) & SB US-1 (https://goo.gl/maps/UkggNueme7Hr3TgW8) says yes.  END (https://goo.gl/maps/mF84RxPKxHwvdTNf8) & BEGIN (https://goo.gl/maps/kJ7TfovCxiJUghv1A) shields found 0.3 miles from supposed end along CR-405 (per GIS).

Extending it to the 'U-Turn' connection @ the Begin/End shields, as JFKSCen.

SR 414 has new interchanges between FL434 and I-4: GatDr, MaiSumBlvd, and KelRd (Lake Destiny Road will no longer have any direct access when construction is done). HopeRd should be WymRd. There's also a new exit 4B at Marden Road.

GatDr, MaiSumBlvd, and KelRd: Added.
HopeRd: no change.  Signed as Hope Road (https://goo.gl/maps/8XuaLMjnVEd5sBk16) TO Wymore Road (https://goo.gl/maps/Xq5PMUKGr9vYrNed7).
Marden Rd: Already in the file ATM on the site, but as Exit 5 (https://goo.gl/maps/JzjAXSqMN3HzmTK69).  So no change needed here unless you have recent photographic proof that the exit number has been changed since StreetView was last there.
I-4: recentered interchange to new bridges.

SR 419/434: GarAve should be moved west to TusRd.

No, GarAve is needed for shaping reasons.  However, still added a point @ TusRd.

SR 423: CurSt -> ChuSt, WyhRd -> WymRd

Fixed.

SR 426: move OakHillDr west to WinSprBlvd?

Main reason I had it at that point was because that road was dead center inside of that curve, and made a logical point to gain the most mileage.  However, I've now moved it to the point you suggested.

SR 436: the south end is north of CargoRd at the canal bridges.

GIS agrees.  However, no ground signage between those bridges & FL-528.  1 BGS-style sign (https://goo.gl/maps/1sYdg2zRrCZLbsxSA) that looks more like 'advance signage' for a route you're going to JCT with.  No Begin/End State Maintenance signs on either road @ the bridges.

Result: shortening it to it's interchange with FL-528.

SR 482: as with other similar routes that end at interchanges with nearby roads (e.g. SR 421), the route extends west of I-4 to TurLakeRd.

GIS doesn't agree, shows end at the intersection with the WB I-4 off-ramp. "Begin State Maint" sign (https://goo.gl/maps/Ki8jDBjHTPs8HKb79) is also there (END is also there going other way).  Since it's within the interchange footprint, no changes here.

SR 524 continues east to SR 528.

GIS agrees.  Signage doesn't agree.  END shield (https://goo.gl/maps/xeA8BxhPpSXFbTcv6) at intersection with FL-501.  Signage on FL-528 going WB (https://goo.gl/maps/h9Co5fk2igqxgKY6A) agrees w/ END shield and has a "TO" above the FL-524 shield.  EB Signage (https://goo.gl/maps/iudBgzKPn3dTw4PW8) doesn't have a "TO" shield, but there's also no signage at the end of the ramp.  There's also a 'JCT shield (https://goo.gl/maps/mZncnjEZ61BWmJNs6) for FL-524 on what's supposed to be itself.

So, as far as I can tell, FDOT doesn't want to sign it up to FL-528 (due to the END shield I mentioned above), thus, no changes will happen here as that part can be considered 'unsigned'.

SR 526: BurAve -> BumAve

Fixed.

SR 527 (Winter Park): OraAve -> LakeviewSt or GarAve or something that isn't actually SR 527

OraAve -> GarAve

SR 536: signs continue west of I-4 to the WDW property line (marked on OSM)

GIS shows 'western' end at the end of the ramps from I-4.  No standalone signage between the I-4 ramps & the WDW signage welcoming you. Signage on WB I-4 (https://goo.gl/maps/oh6WVzxqZ2yX2AZh6) shows no FL-536 'West' shield, only 'East'.  Since the western 'end' is within the interchange footprint per GIS, and no other signage proving otherwise (this BGS (https://goo.gl/maps/E7hJWVG6GJ8JvGBW6) doesn't count since it still is technically the road and inside of the interchange), no changes here.

SR 551: GolRdExt -> OldGolRd

Fixed.

SR 586, SR 590, SR 686, SR 688: add CR501?

Sure, why not.  Added to all 4 routes.

SR 594 extends west to the eastbound end of I-175.

No changes here, as we have I-175 ending 4th Street (the location of it's 'start' going WB).  I know, it's complicated because of FL-594 only being signed EB due to Dali Blvd being one-way between 4th & 3rd Street.  It was the best solution that could be arranged and keep 'graph connections' with FL-687 too.  Otherwise, we couldn't have FL-594 on the site.  Honestly wish this was one route FDOT didn't want to sign.

US 17/92: add CR580 in Haines City, CR54 -> RonReaPkwy, CR535 -> HamBroRd, CR531 -> PleHillRd (neither CR 535 nor CR 531 is signed or recognized by the county), US17/92Trk_S -> FL423, FL414/17Trk -> FL414 (these are much better signed than the truck routes), DirDr -> CR4162, SaxBlvd -> CR4146

CR580: Added.
RonReaPkwy: Changed & recentered.
HamBroRd/PleHillRd: Done.
FL423/FL414: Done & see below in "US 17/92 Truck (Orlando)" section.
CR4162/CR4146: Done.

US 17/92/441: CR527A -> LanRd

Done.

US 17: move KatSt one block north to CR4053

Done.

US 27: add CR17_HaiCity, RonReaPwky -> RonReaPkwy, add CROld50 in Minneola

CR17_HaiCity: Added as 'CR17_Hai'.
RonReaPkwy: Fixed, old label depreciated as in-use.
CROld50: Added.

US 192: AvaRd -> CR545_N, CR545 -> CR545_S, KisParkRd -> OCanCRd (to match US 441)

All fixed.

US 192/441: CR523_N -> CR523

No change here, as there's a corresponding 'CR523_S' in US-441's file that's the southern part of this same road.

US 441: add CR437_N and CR437_S just south of SR 429, CR452 -> LakeEusDr, CR44_E -> CR44LegA, CR44_W -> CR44

All changed except 'CR44_W' do to conflict with FL-44 file, which has a 'CR44' point (but might come back to this at a later time).
"CR44_E -> CR44LegA" also fixed in FL-44's file.  However, a separate post about FL-44 will be coming at a later time.

US 17/92 Truck (Orlando): WyhRd -> WymRd_S, HopeRd -> WymRd_N

Shields seem to have been removed at the Northern end. Apr '15 (https://goo.gl/maps/eWcVafBQ33hFNCsa9) -> July '15 (https://goo.gl/maps/LQawpFoKUmK3v7e79).  Similar story at the 'Southern' end, May '15 (https://goo.gl/maps/aMytpF8ks3YDvw6b6) -> July '15 (https://goo.gl/maps/6rynWd1h2BzTfTx87).  Signage even @ I-4 & FL-423 is now gone (Apr '11 (https://goo.gl/maps/EoexgJoxzQoDX4f77) -> Dec '18 (https://goo.gl/maps/BbTQUi3uY2KghWYcA)).

Considering both routes now as 'dead' even though 'problem bridge' remains, and will remove them both from site on next update.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on April 30, 2019, 08:02:55 pm
SR 414 has new interchanges between FL434 and I-4: GatDr, MaiSumBlvd, and KelRd (Lake Destiny Road will no longer have any direct access when construction is done). HopeRd should be WymRd. There's also a new exit 4B at Marden Road.

HopeRd: no change.  Signed as Hope Road (https://goo.gl/maps/8XuaLMjnVEd5sBk16) TO Wymore Road (https://goo.gl/maps/Xq5PMUKGr9vYrNed7).
I suppose both directions do have an exit to Hope Road, but the eastbound entrance is from Sandspur Road (formerly the eastbound exit was too, but now that's only from I-4 east).
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 20, 2019, 09:35:17 am
I am not sure if you wanted to do anything in regards to the linked post below.

http://forum.travelmapping.net/index.php?topic=2535.msg10905#msg10905

Checking it previously, I know that FL 228 is not signed along the freeway to US 90, but should it be included in some form based on it being a freeway?

I don't think adding it would be a problem, as long as I add the entire "Hart Expressway" (including US-1 Alt's part), as it would be 5 miles in length.

Oh boy, and it seems part of this is going to be removed next year. :/
https://www.firstcoastnews.com/article/news/local/comparing-the-hart-bridge-expressway-project-in-jacksonville-to-similar-projects-around-us/77-4a19b0f4-f590-4e94-a2b9-d0f4d29bff3f
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on May 20, 2019, 10:47:57 am
https://github.com/TravelMapping/HighwayData/pull/2872

This includes the 3 posts talked about above, plus the addition of the "Hart Bridge Expressway" to the site.
Title: Re: usafl: Florida State Highways
Post by: Duke87 on June 11, 2019, 04:39:35 pm
FL 886 is not signed.

Source: personally field verified this morning.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on June 11, 2019, 08:27:16 pm
FL 886 is not signed.

Source: personally field verified this morning.

Did you go northbound and southbound on US 1 at 886?
Title: Re: usafl: Florida State Highways
Post by: formulanone on June 17, 2019, 06:35:51 am
FL 886 is not signed.

Source: personally field verified this morning.

Did you go northbound and southbound on US 1 at 886?

I've never seen a reassurance marker either, but there have been 886 shields on US 1 for a while; this photo is from mid-2013:

(https://live.staticflickr.com/7560/28433692590_dcccf6798f_c.jpg) (https://flic.kr/p/KjA7c9)
Title: Florida: peer review
Post by: neroute2 on September 03, 2019, 08:10:20 am
2: it may have been signed in the past, but I can't find any current signage for the 81 overlap. Truncate west end to 81.
2: StMarkSt would make more sense to the west at MainSt.
2: CR2A is not signed. Recommend changing to OldHwy2 (name from Jackson County Property Appraiser GIS).
2: OceAve should be OscAve.
2oke: CR250 is a dirt road that is not useful for shaping and has no shields or street signs. If you want to keep it, Baker County PA shows it's EddyRd.
4: HutLn might be better just to the east at BooLn.
4: ForRd should be 3NotTrl (the former is not signed at 4).
4: Key Mill Road - move west to CR4B?
5: 6thAve -> 6thAveS, since there's a 6th Ave North on the other side of town.
5: 10thAve -> 10thAveN for the same reason.
5: the north end as maintained and signed is now at the C-51 Canal bridge.
5aday: WilTraRun is such a minor road. Move just east to MilDr?
5aday: move AlcSt south to FloSt?
6: add a point at CR751?
7: maintenance has been extended north to 60thSt.
9bjac: 1 is now open: "Marconi will be the first neighborhood to open in eTown in May 2019. It will be a gated community with homes starting in the mid $300,000s." (https://www.actionnewsjax.com/news/local/etown-vision-for-9b-s-e-town-parkway-exit-revealed-homes-to-feature-smart-home-technology/927228515)
10alak: S7thSt -> LakAve
12: GOEdenRd -> GarEdenRd (omit 'of')
12: FL269 is a bad name for a waypoint given the overlap; how about KingSt?
13: is ToFL16 necessary? It's just a pair of ramps in a large intersection.
15orl: FL408(12A) -> BumRd?
16: are ToFL230 and ToFL13 necessary?
17: HarRd -> CodyVilRd
17: ToCR640 ditto
19: NF77 -> NF74 (https://www.google.com/maps/@29.4726514,-81.7386952,3a,15.1y,6.7h,86.38t/data=!3m6!1e1!3m4!1sMfC4BpezO4MBS4bceX13dQ!2e0!7i16384!8i8192)? Street sign blades say NFR 77 though.
Title: Re: Florida: peer review
Post by: neroute2 on September 03, 2019, 06:32:06 pm
20: LocTerRd should either be renamed AlaTerRd or moved west to the more important SiteC6Rd.
20: US331 needs moving.
20: AspPlaRd is a private dirt road with gates. There's no need for a point there.
20: CR267 -> CR2224
23: 32 should move south to the overpass
23: 35 should move north, replacing 35A
29: JanSceDr -> CR837_W, CR837 -> CR837_E
29: WhiRd -> MarFieRd (the former isn't signed at 29)
30: BeaSchRd -> ClaAve
30apor: FL30 -> US98
30e: SeaDr should be moved north to the cul-de-sac and renamed StJosPenSP
31: CR763_S -> CR763, CR763_N -> NHogBayExt (or move just north to CR760)
35: 92ndPlaRd -> 92ndPlRd (it's a double suffix)
37: FourConMineRd -> FourCorMineRd
37: MainSt -> MainAve, MainSt_Lak -> MainSt
37: OldFL37 -> OldHwy37 (https://www.google.com/maps/@27.8507206,-81.9732456,3a,27.2y,261.23h,90.28t/data=!3m6!1e1!3m4!1sanIw8ml1XFFTklTd-GoEMw!2e0!7i16384!8i8192)
37: the actual north end is at MainSt_Lak; beyond there is unsigned SR 35. The only sign I know of that says otherwise (https://www.google.com/maps/@28.0510641,-81.9581135,3a,22.5y,125.87h,89.17t/data=!3m6!1e1!3m4!1sHDhAYs-_qU_EgOugTuoq1w!2e0!7i16384!8i8192) is on a side street north of where we end it.
Title: Re: Florida: peer review
Post by: neroute2 on September 03, 2019, 09:34:32 pm
40: CR328 needs to be moved west
40a doesn't exist anymore and was probably never signed
44: HerBlvd -> BueVisBlvd
44: the US 441 "overlap" is all signed with to plates
44: CR44 -> CR44_E
44: BlueLakeDr -> BlueLakeAve
45: SocSt -> ScoSt (but why here? why not 7thAve?)
45: FolAve -> FloAve (but why here? why not ColDr?)
46: recenter FL453
46: CR15 -> US17/92_N, US17/92_N -> FrenchAve_N
47: WatRd -> WatSt
49: is only signed as US 129, so shouldn't be in CHM
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 04, 2019, 04:41:53 am
This post will detail a possible split that might be needed for two routes, FL-19 & FL-44 along US-441 in the Leesburg & Eustis areas.  Dealing with this now would be for the best before any possible activation to prevent any future issues with either re-combining or splitting them.

US 441: add CR437_N and CR437_S just south of SR 429, CR452 -> LakeEusDr, CR44_E -> CR44LegA, CR44_W -> CR44

All changed except 'CR44_W' do to conflict with FL-44 file, which has a 'CR44' point (but might come back to this at a later time).
"CR44_E -> CR44LegA" also fixed in FL-44's file.  However, a separate post about FL-44 will be coming at a later time.

It seems that both FL-19 & FL-44 routes might need to be split into two separate files each.  1 for above & below US-441 bases on signage.  While the GIS data from FDOT (dated 08/31/19) shows them both on US-441, signage in the field says otherwise, but can also be very confusing depending on the location.  We'll start off with FL-19's case.

FL-19:
SB:
On it's Northern end w/ US-441, we happen to have this signage on the on-ramp to NB US-441 (https://goo.gl/maps/3QUoc9KRX3AoNzLB7) clearly showing a SB FL-19 shield w/o a 'TO' banner (ignore the FL-44 shield, as I think it was there from when FL-44 was routed along here, as there's a 'TO FL-44 East' shield on the other side).  However, when you flip around to look at the left turn onto that ramp from NB FL-19 (https://goo.gl/maps/ahjFMrL4TthupX59A), there is clearly a 'TO' banner there.  Now, on 'NB US-441', you have this set of shields (https://goo.gl/maps/sW69gJRETZksHdQR7) that do have a FL-19 SB (note, no mention of FL-44, but we'll get to that later), however, the problem here is that FL-19 HAS NOT joined US-441 yet at this point, so, FL-19 traffic will NOT see this shield, which leads me to believe it was possibly suppose to be a TO FL-44 West shield instead.  However, you do have this 'set' at the offramp from NB US-441 to NB FL-19 (https://goo.gl/maps/iuFSjuupsnziJ4Ks8) showing each direction.

So, the first US-441 NB shield that FL-19 SB traffic does see, is this assembly (https://goo.gl/maps/eFjLhA8vW2cnR44m6), which has NO mention of FL-19, BUT does have a 'TO FL-44 West' shield instead.  The 2nd 'NB' shield of US-441, is this one (https://goo.gl/maps/HxekrwZjgeNK7XEaA), which lacks any mention of either FL-19 or FL-44.  The first mention again of FL-19, is the following BGS (https://goo.gl/maps/Jg1WwxxB5fNta4oh7) at it's 'southern' intersection with US-441.  Then, right before the intersection, we have this little 'confusing' shield assemblies (https://goo.gl/maps/E66txvSHMrMPLiGg9), showing a 'TO' banner above FL-19, when there shouldn't be one, because that IS FL-19 you're turning onto.

NB:
This direction isn't much better.  No shields along US-441, just like in the SB direction.  Just US-441 shields.  Starting @ the 'southern' intersection with US-441, we have this shield assembly showing a 'TO' North FL-19 shield (https://goo.gl/maps/nTgLJaxwEGu9EPw9A) with a set of US-441 shields for both of it's directions.  However, on mainline SB US-441, you have this North FL-19 shield w/o a 'TO' banner (https://goo.gl/maps/2Lq9tZea7Swg3ckQ8) right before the intersection.  This would be the only place FL-19 North gets any mention till it's interchange where it leaves US-441 SB (https://goo.gl/maps/JE62tNPX8GiXkRfR7).


So, with the way signage is, it's making me lean towards splitting the route in half.  However, could we consider this as an 'implied' multiplex, though the lack of any shields along the route itself with US-441 is worrisome, as all we're relying on is at the start/ends?  Would greatly appreciate opinions on this one, as it's been driving me nuts.

Gap would be: 3.28 miles

====

FL-44:
WB:
As with FL-19 along US-441, there are no 'normal' shields, however, in several locations, there are 'TO' shields directing travelers to the 'other half' of the route. (Examples: [1] (https://goo.gl/maps/eFjLhA8vW2cnR44m6), [2] (https://goo.gl/maps/E66txvSHMrMPLiGg9))  Now, @ the 'eastern' end of the route, just as with NB FL-19, we have ourselves a 'TO' West FL-44 shield at it's intersection with US-441 (https://goo.gl/maps/LVp4spBcPFt6VRH19). However, unlike with US-441 @ FL-19 (both ends), there is NO mention of West FL-44 on US-441 at this intersection, just East FL-44 (with a curious 'TO' Bypass North FL-19 shield) (https://goo.gl/maps/jDJxyGqMcWWZJjQH8).  All other mentions of FL-44 WB I've found along NB US-441, have been of the 'TO' variety.

EB:
Now, at the other end, on SB US-441, we have a clear 'TO' East FL-44 shield (https://goo.gl/maps/9yYdVnH6WfphReVz5) on the US-441 mainline before it's intersection with FL-44.  Now, on EB FL-44 approaching the intersection with US-441, we have this shield assembly, again, clearly showing a 'TO' banner above the FL-44 East shield (https://goo.gl/maps/M5wZhHmNScs4m1Uk8).  And as with FL-19, the first shield on US-441, is just a solo US-441 shield after that intersection.  There are a few 'TO' East FL-44 shields along US-441 SB (https://goo.gl/maps/QnYSfpCCYNnjbB258) as well (like on NB US-441) letting you know you're still heading towards the other half.

Gap would be: 11.5 miles

As with FL-19, I'm also leaning towards splitting this file in half.  It honestly seems FDOT (even with the acknowledgement in the GIS data) wants both routes to have a 'gap' in them.

So, I'd appreciate any opinions you guys want to give before I make any 'major' changes to either route.  At least with the system still in 'preview', major changes like this can happen without needing to be documented on the 'updates' page, and allow me to break list files without having to worry on keeping any labels.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 04, 2019, 06:28:03 am
Would it be reasonable to include waypoints at Sans Souci Blvd on FL922 and US1? It seems to be a well used connector between the two routes (and, selfishly, one that I used last time I was in the area, leaving me currently unable to claim any of FL922) that Google Maps routes you on by default if making the south-to-east movement.

Seems to be a reasonable addition.  Added into my local copies of both files.

On FL50, CR439 should be CR439_S given this sign:
(http://i.imgur.com/69XgnMr.jpg)
Note that there is no other signage anywhere for CR 439 north (which is Bluford Avenue). A BluAve point should be added anyway, since it's a former state road.

Normally, I wouldn't add the '_S' if there's no posted counterpart for the other direction.  However, I've done it in this case and added the other part as the label you suggested.  However, with the gap of only 0.25 between the two points, it's pushing it on being added since it doesn't directly connect to an interchange.

Changed in my local copy.

From user skatcher by email:

I noticed a “confusing” waypoint on the .list name FL FL616. Waypoint 1 (CR587/N West Shore Blvd) is labeled as ShoBlvd. I noticed when West Shore Blvd crosses FL US92 and FL FL60 both those pages label the waypoint as CR587. I think from a consistency standpoint the Waypoint should be changed to CR587. If not, then at least change the waypoint to WShoBlvd as N West Shore Blvd becomes S West Shore Blvd south of FL60.

FL-616: No shields for CR-587 posted at the intersection, hence used the road name.  Label however changed to WShoBlvd due to the N/S changing part.
FL-60: Posted there (https://goo.gl/maps/vj71YpGb8UGpBaim9). Label stays as-is.  But I'm open to changing to 'WShoBlvd' too, as that does look like a pretty old shield that 'might' have been left behind.
US-92: Not posted here.  CR587 -> WShoBlvd

FL 590 (Clearwater) east end (waypoint 8) is listed as SunPoiRd, for Sunset Point Rd. But Sunset Point Rd becomes Main Street once it gets into Safety Harbor, which it does at McMullen Booth Rd (CR 611). Wondering if the waypoint should be redesignated MainSt, even if it would break the 7 of us (including myself) who have clinched the segment.

Was going originally off of what the road was listed as in OSM.  Anyways, I could break it even more for you guys by shortening it to down one intersection to the south @ Delaware Street because of this "Begin/End of State Maintenance (https://goo.gl/maps/URWf2Gjp68Fsizm59)" set of signs there, even though there's a West FL-590 shield (https://goo.gl/maps/FT6DBCnNQ9dy7JNH7) before the 'Begin' sign mentioned before. :P  Delaware Street is where the GIS data agrees that segment ends/begins.  Opinions?

FL 243 now is listed on the BGS at the Pecan Park exit on I-95 (Exit 364). As the weather was bad, I couldn't see if there was a sign on Pecan Park Road itself (and there's still construction going on at the interchange; it may not be signed on Pecan Park yet anyway).

Thank you for the heads up.  However GIS data doesn't show it going along Pecan Park yet.  And with StreetView being from December '18 with it being still under-construction, I don't feel confindent to extend the route to I-95 at this time yet.  However, StreetView on I-95 from March '19, does show the shield on the BGS for the exit (https://goo.gl/maps/YZh5CtHxMC6835d48), so, something I do need to keep an eye on for the future to update.

===

Ok, this should bring this thread up-to-date to just before the conversation on FL-886. :)
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 04, 2019, 06:54:08 am
FL 886 is not signed.

Source: personally field verified this morning.

Did you go northbound and southbound on US 1 at 886?

I've never seen a reassurance marker either, but there have been 886 shields on US 1 for a while; this photo is from mid-2013:

(https://live.staticflickr.com/7560/28433692590_dcccf6798f_c.jpg) (https://flic.kr/p/KjA7c9)

Maybe we can consider FL-886 as a red-headed cousin of FL-102?  102 only had one shield for AGES until recently when a 2nd showed up along FL-243.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 04, 2019, 02:59:47 pm
I was thinking about 19, and could go either way on it. 44 should definitely get split.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 04, 2019, 05:03:45 pm
50: CR587 is a more major road than CR493. Recommend adding the former and possibly deleting the latter.
50: KetRd -> CroRitRd, the more important road at the intersection?
50: DeerIslRd should be moved east and renamed OakAve, the more important road there (renamed from Old SR 50).
51: I can't verify the CanRd name on signs or GIS (http://www.lafayettepa.com/GIS/Search_F.asp?GIS). GIS labels LongTreRd as Turkey Road.
52: ShaRidRd should move west to ColRd, a more important road.
52: StaDr is a private driveway. Move just east to OldSanAnnRd?
14: add HarGreDr south of Madison to match the point on 53?
54: BlaLakeRd -> AstPkwy since Black Lake Road is a loop that returns to 54?
54zep: DorSt -> GeiEstDr?
56: MarBlvd -> ManBlvd
56: extend east to US 301
59: BethPageRd -> BetRd? (it's one word on sign, though it's two at the other end, and two words on property appraiser GIS)
60: move BayDr east to the overpass
60: why HowAve and not ArmAve?
60: FL45 -> FL45_N (it's unsigned to the south)
60: MainSt_BarE -> FlaDr
60: 91MileRd -> 91MineRd
60: LakeWalRd -> WLakeWalRd (it goes to West Lake Wales)
60: CenAve needs to move east
60: interchange with HesRd (https://www.google.com/maps/@27.8945705,-81.5802853,3a,16.6y,77.78h,90.79t/data=!3m6!1e1!3m4!1sVfPj2GC_b3SWeniZXWe1Tw!2e0!7i13312!8i6656) in Lake Wales
61: CR260 -> CR2204
61: FL371 -> CR1555? (SR 371 is no longer state maintained or signed on SR 61, but there is reassurance after you turn)
62: JohnGriRd -> JohnGillRd, but why is there a point here?
64: move 15thSt east to 14thSt?
64: WMainSt -> MainSt
64: SteRSRd -> SteRobSpec (per street blades)
65: NorSt -> NorRd
65: LChipPRd doesn't exist; move just south to WOShuRd (name from property appraiser GIS)?
66: WinCrkRd -> WooCrkTr and move it east
69: CR278 -> BirRd
Title: Re: Florida: peer review
Post by: formulanone on September 04, 2019, 07:09:44 pm
29: JanSceDr -> CR837_W, CR837 -> CR837_E

There's CR 837 signs on FL 29, but there's no reassurance markers on that route. I think it's much more well-known as Janes Scenic Drive (or Janes Memorial Scenic Drive); however, I'm not sure what the standards are for TM.
Title: Re: Florida: peer review
Post by: rickmastfan67 on September 05, 2019, 02:03:54 am
I'm not sure what the standards are for TM.

If there's shields @ the intersection, it's fair game, even if there's a lack of them on the road when it comes to County Routes, since we aren't adding the route itself to the site.  Now, if it was a state route, and the only mention of it was at a single intersection, that might be a different story (ala FL-886 above).  Those are case-by-case ones.
Title: Re: Florida: peer review
Post by: rickmastfan67 on September 05, 2019, 05:33:47 am
2: it may have been signed in the past, but I can't find any current signage for the 81 overlap. Truncate west end to 81.
2: StMarkSt would make more sense to the west at MainSt.
2: CR2A is not signed. Recommend changing to OldHwy2 (name from Jackson County Property Appraiser GIS).
2: OceAve should be OscAve.
2oke: CR250 is a dirt road that is not useful for shaping and has no shields or street signs. If you want to keep it, Baker County PA shows it's EddyRd.
4: HutLn might be better just to the east at BooLn.
4: ForRd should be 3NotTrl (the former is not signed at 4).
4: Key Mill Road - move west to CR4B?

2: GIS no longer shows the overlap (confirmed w/ StreetView), so, removed from FL-81 & appropriate changed made to it's file too.  All other issues mentioned fixed as well.
2oke: That point is there for distance reasons. Otherwise, it would be 15.6 miles between usable points. Still, renamed to suggested as it's shown in OSM too.
4: All suggestions made.

5: 6thAve -> 6thAveS, since there's a 6th Ave North on the other side of town.
5: 10thAve -> 10thAveN for the same reason.
5: the north end as maintained and signed is now at the C-51 Canal bridge.
5aday: WilTraRun is such a minor road. Move just east to MilDr?
5aday: move AlcSt south to FloSt?

5: All changes made, including appropriate label changes to US-98/FL-80 for the old route.
5aday: #1 changed. #2 AlcSt -> GolfAve as it kept mileage a little better.

6: add a point at CR751?
7: maintenance has been extended north to 60thSt.
9bjac: 1 is now open: "Marconi will be the first neighborhood to open in eTown in May 2019. It will be a gated community with homes starting in the mid $300,000s." (https://www.actionnewsjax.com/news/local/etown-vision-for-9b-s-e-town-parkway-exit-revealed-homes-to-feature-smart-home-technology/927228515)

6: Added.
7: However, signage doesn't.  Can you provide proof it is indeed signed now?  I mean, sure, there's the overhead signage @ FL-704, but that's been there for ages, from the time that StreetView last traveled up the road itself, and showed that it had no signage along it.  If I can get that proof, I'd be more that happy to extend it.
9bjac: Unhiden.

10alak: S7thSt -> LakAve
12: GOEdenRd -> GarEdenRd (omit 'of')
12: FL269 is a bad name for a waypoint given the overlap; how about KingSt?

10alak: Fixed.
12: #1 fixed. #2 To be honest, I'm not even sure the overlap exists.  StreetView was last there back in '17, before the reroute of FL-12 in that area onto FL-269.  Now, FL-269 is still shown in the GIS data, but not sure if it's become hidden under FL-12 there.  As for changing the label to 'KingSt', as far as I can tell, the name continues in both directions from that intersection still.  So, 'FL269_N' to signify the end of the overlap maybe?

13: is ToFL16 necessary? It's just a pair of ramps in a large intersection.
15orl: FL408(12A) -> BumRd?
16: are ToFL230 and ToFL13 necessary?

13: Since the 'intersection' was pretty big, I thought it would be a wise idea to allow accurate mapping for people.  It's about 0.3 miles distance between the 'parent' point.  Plus, some people are already using it, so it seems to be a reasonable point to keep as it.  As for the name, that's honestly the best I could come up with.
15orl: Ramps are super close to/from FL-408 there, so I'll just leave that one as-is.
16: Same deal as with 13 above.

17: HarRd -> CodyVilRd
17: ToCR640 ditto
19: NF77 -> NF74 (https://www.google.com/maps/@29.4726514,-81.7386952,3a,15.1y,6.7h,86.38t/data=!3m6!1e1!3m4!1sMfC4BpezO4MBS4bceX13dQ!2e0!7i16384!8i8192)? Street sign blades say NFR 77 though.

17: #1, fixed.  #2, re-centered CR640, and deleted the 'To' one, even thought it looks like this was bypassed once before.  But this was a smaller one unlike the other 2, thus making it easier to do this with since it's with a road we don't map.
19: Street blades, Google, both say 77.  Could OSM be in the wrong here?  Doubt FDOT would post the wrong street blade, but you never know.  Leaving as-is for now.


All the changes have been made in my local files and will be submitting in a bit.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 05, 2019, 06:42:12 am
All talked about changes have been submitted.
https://github.com/TravelMapping/HighwayData/pull/3107
Title: Re: usafl: Florida State Highways
Post by: yakra on September 05, 2019, 09:47:31 am
FL19 on US441 is a pretty clear implied multiplex.

WShoBlvd, if we strictly apply the manual, would be WestShoBlvd. Necessary directional identifiers are abbreviated "normally": Nor/Sou/East/West. Though, how much do we really care about that rule these days? Not sue how wide it ever came into use in practive; I'm fine with WShoBlvd.

I'm not sure about the FL44 split; the TO shields would be enough to kick it up to implied multiplex level. My canonical example is NS2 via NS102.


Does usafl have its own standards on when there's an implied multiplex, as some systems do?
Title: Re: Florida: peer review
Post by: neroute2 on September 05, 2019, 10:27:32 am
7: maintenance has been extended north to 60thSt.

7: However, signage doesn't.  Can you provide proof it is indeed signed now?  I mean, sure, there's the overhead signage @ FL-704, but that's been there for ages, from the time that StreetView last traveled up the road itself, and showed that it had no signage along it.  If I can get that proof, I'd be more that happy to extend it.
If we had just come across this in a vacuum, we'd see the signage on SR 704 and conclude that it continues north. The only reason this is a debate is that we're looking at the history of the situation.

19: NF77 -> NF74 (https://www.google.com/maps/@29.4726514,-81.7386952,3a,15.1y,6.7h,86.38t/data=!3m6!1e1!3m4!1sMfC4BpezO4MBS4bceX13dQ!2e0!7i16384!8i8192)? Street sign blades say NFR 77 though.

19: Street blades, Google, both say 77.  Could OSM be in the wrong here?  Doubt FDOT would post the wrong street blade, but you never know.  Leaving as-is for now.
I linked to street view that shows a 74 shield. Do we go by shields or street signs?
The Ocala NF map (https://www.fs.usda.gov/Internet/FSE_DOCUMENTS/fseprd610383.pdf) (last page) also shows 74. Looks like a renumbering.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 05, 2019, 11:38:28 am
70: PineLevRd -> PineLevSt
70: move LigRanRd east to PlaLakBlvd?
70: OldFL8 -> OldSR8_N; maybe add OldSR8_S
70: should McCRd be MccRd or McCarRd?
70: FL713 -> FLTpk?
71: DynDockRd -> OldDynDockRd
71: HarNealLp -> HarNeelLp
71: LewBailRd -> LewBaiRd
72: BeeRidRdExt -> LorRd ("Fka Bee Ridge Rd Ext" (https://www.google.com/search?q=bee+ridge+extension+lorraine))
72: MyaSParkRd -> MyaRivSP
73: FinkBCRd -> FriBCRd
77: HoaSeaRd -> HouSeaDr or MarBayDr
77: CryLakeRd -> CryLakeDr
77: JohRd -> JohnEricRd
79: SugDollRd -> SugRd (one word on sign)
80: US27_N needs to move
80/US27: OldFL80 -> OldUS27, CorBlvd -> CorBlvd_N, OldUS27 -> CorBlvd_S (https://www.google.com/maps/@26.6823014,-80.7515014,3a,19.5y,180.85h,93.8t/data=!3m7!1e1!3m5!1sEGalEZbYiEFOTBJ61wTPEQ!2e0!5s20110501T000000!7i13312!8i6656)
80: SemWhiRd -> SemPraWhiRd
80: FolRd -> ForHillBlvd or CreBlvd
80: PreRd -> PikeRd
80: move MilAve west to the underpass? or at least west to line up with the road to the south, since it's a gated private driveway to the north
80: FL5 -> OliAve
81: SubStaRd -> SubRd (one word per street sign)
81: CR2_W -> CR2/2A?
82: MicLinkAve -> MicAveLink
84: HatRd -> HiaRd
84: I-595(7) -> DavRd? Why is this one I-595(*) but the others aren't?
84: I-595(8X) doesn't exist on the SR 84 C/D roads
85: GRMBondBlvd -> GenBondBlvd (https://www.google.com/maps/@30.4891782,-86.5622911,3a,15y,207.09h,87.85t/data=!3m6!1e1!3m4!1sN19Uss04JiqNkzQ4y-kZOA!2e0!7i16384!8i8192)
85: NWFLRegAir -> DesFWBAir
85: McWAve -> 77thSpeForWay, needs to be moved south a bit
85: CR85A_W -> CR85A_S, CR85A_E -> CR85A_N? CR 85A is signed north at the 'west' end
87: OlfChoRd -> OLFChoRd? OLF stands for Outlying Field
89: RWitRd -> RWhiRd
Title: Re: usafl: Florida State Highways
Post by: yakra on September 05, 2019, 07:09:30 pm
http://travelmapping.net/devel/manual/wayptlabels.php (search for MLKingBlvd):
OldDynDockRd would instead be OldDynRd, OldDockRd, DynDockRd, OldDDRd, ODynDRd or ODDockRd.
SemPraWhiRd would instead be SemPraRd, SemWhiRd, PraWhiRd, SemPWRd, SPraWRd or SPWhiRd.
Et cetera...
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 05, 2019, 07:20:59 pm
100: CR231A -> CR100A
100: CR18 -> CR18_W, SE9thAve -> CR18_E
100: CR201 -> JohnAndHwy
101: MayNavSta -> NavStaMay
104: US1 -> US1/23
105: 105 south is signed to turn left on the connector (named Zoo Parkway, not Heckscher Drive) to end at US 17, with reassurance after the turn. There is also reassurance northbound on the connector. I can't find any reassurance on the road to I-95. Recommend ending 105 at US 17 south of the interchange, with the HecDr point renamed ToI-95.
105: DaveRawBlvd -> BloIslTer? I can't find any signs with the name.
121: SandHillRd is a dirt track with no street signs; convert to shaping point?
122: BouSt -> Blvd
126: the logical east end is where Emerson Street becomes Emerson Street Expressway
145: PawPawSt -> PawSt (one word on sign)
145fwb: FerAve_S -> FerRd_S, FerAve_N -> FerRd_N
189fwb: GRMBondBlvd -> GenBondBlvd (as on 85)
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 05, 2019, 07:51:42 pm
200fer: US1/301 -> US1/23?
200fer: PinPl -> PineGroPl
200fer: MagSt -> MagLn
202: move SanBlvd east to the overpass and rename BeaPkwy?
211: McDufAve -> McDAve or McDuffAve
228: move I-10(362) west to the bridges?
230: LynLn -> ToFL16
231lak: CR231 should be a bit to the south (https://www.google.com/maps/@29.9834128,-82.355849,3a,75y,197.1h,72.41t/data=!3m6!1e1!3m4!1sQFgLRAt-8bYjBwUFKnmPfg!2e0!7i13312!8i6656)
235: per GIS, the south end is one block to the north at CR 2054 *west*; signage (https://www.google.com/maps/@29.786669,-82.4937281,3a,22.7y,301.24h,87.44t/data=!3m6!1e1!3m4!1sb-00EoANlJohGJ4TSbqJdQ!2e0!7i13312!8i6656) at the end we currently have is ambiguous, but looks county-installed
263: TalRegAir -> TalIntAir
267qui: GouRd -> HopLanRd
295: PenNAS -> NASPen
298: SanSebDr -> SanSebCir
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 05, 2019, 08:13:27 pm
FL19 on US441 is a pretty clear implied multiplex.

Still have it in one piece for now.

WShoBlvd, if we strictly apply the manual, would be WestShoBlvd. Necessary directional identifiers are abbreviated "normally": Nor/Sou/East/West. Though, how much do we really care about that rule these days? Not sue how wide it ever came into use in practive; I'm fine with WShoBlvd.

Yeah, sometimes rules need to 'evolve'. lol.

I'm not sure about the FL44 split; the TO shields would be enough to kick it up to implied multiplex level. My canonical example is NS2 via NS102.

But how long is the NS2 one?  This FL-44 one is 10+ miles.  There has to be limits to be honest.

Does usafl have its own standards on when there's an implied multiplex, as some systems do?

Mostly depends on how the signage is.  FDOT can be a tricky beast with all the 'hidden' routes under US/Interstate routes.  Pretty much have to decide on the fly.  Look @ FL-109.  I have it split into two parts.  GIS agrees with that, but there are 'TO' shields between the two parts.  Re-merge the two, or keep separate?  Same deal with FL-267 as it has 'TO' shields along FL-20.

I mean, how far are we going to go with 'implied'?  I mean, I can see it with super short segments sometimes, but the FL-44 one above is 10+ miles of 'TO' signage (which isn't as frequent as the US-441 shields along that 'gap'.  Sure, the GIS shows it being along US-441, but we're getting into dangerous territory here again on what's signed and what's not.  I took FORVER to try to get that all fixed up, and I'm not about to go back and just have to rebuild entire routes again with unsigned segments.
Title: Re: usafl: Florida State Highways
Post by: oscar on September 05, 2019, 08:43:41 pm
Does usafl have its own standards on when there's an implied multiplex, as some systems do?

usaca has no standard on implied multiplexes, other than that the implied route can follow only one signed route.

CA 1 has several multiplexes with US 101, one of them over 60 miles long, though I don't recall whether that or the others have some CA 1 signage alongside US 101 signage. There are other implied multiplexes here and there in rural areas, some of which are fairly long.

Alaska has one implied multiplex (the state's only multiplex), which is about 14 miles long.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 05, 2019, 09:08:11 pm
usaca has no standard on implied multiplexes, other than that the implied route can follow only one signed route.
http://travelmapping.net/hb/index.php?r=ca.ca016
http://travelmapping.net/hb/index.php?r=ca.ca099
Do these need to be split?
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 05, 2019, 09:43:26 pm
320: MSStaPark -> ManSprSP?
345: CR345 -> CR332/345?
363: FL61A -> GaiAve
363: FL371 -> GaiSt? (still signed on SR 363, but no longer maintained, and no reassurance in the area)
366: FL371 is the new east end, and most signs have been removed (the only ones I can find are this old one (https://www.google.com/maps/@30.4393629,-84.2805711,3a,37.8y,25.35h,85.81t/data=!3m6!1e1!3m4!1sP884dtAv7D63G7l4Pwq6WQ!2e0!7i13312!8i6656) on US 27 north and this left turn (https://www.google.com/maps/@30.4388054,-84.3003469,3a,26.6y,271.32h,83.33t/data=!3m6!1e1!3m4!1sWpMAmj5WY63si2URkgKOiQ!2e0!7i13312!8i6656))
371: FL366 is the new north end. The only signs I can find beyond there are westbound reassurance at SR 61 and a trailblazer on northbound SR 363.
397: EAFBase -> EglAFB?
397eaf: EAFBase -> EglAFB? rename the file to 397egl?
399 is signed at least once (https://www.google.com/maps/@30.3576037,-87.161035,3a,16.6y,278.97h,87.56t/data=!3m6!1e1!3m4!1sVNirx_m2gGDErCZygsqpXg!2e0!7i16384!8i8192), and begin/end state maintenance is posted.
Title: Re: usafl: Florida State Highways
Post by: oscar on September 05, 2019, 09:47:37 pm
usaca has no standard on implied multiplexes, other than that the implied route can follow only one signed route.
http://travelmapping.net/hb/index.php?r=ca.ca016
http://travelmapping.net/hb/index.php?r=ca.ca099
Do these need to be split?

Maybe 16, whose multiplex follows I-5 and US 50, and is poorly signed if at all.

99, IIRC that multiplex (also over shorter segments of I-5 and US 50) is reasonably well-signed.

I'll copy this over to the usaca thread, as a to-do list item.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 05, 2019, 10:17:15 pm
401: where does the name ChrColRd come from? How about CT5-10 (https://www.google.com/maps/@28.4166145,-80.6309291,3a,47.3y,86.8h,90.15t/data=!3m6!1e1!3m4!1s7zzJ0tv6ipqVnYkL_m3eDg!2e0!7i16384!8i8192)?
404: CR509 -> WicRd
408: should 11A be an alternate label for 10C?
415 should have a point at CR4162, which connects to I-4.
419/434: GarAve -> EagWindAve
435: I-4 needs recentering
435: CR526 -> OldWinGarRd (CR 526 isn't signed here)
50: CR435 -> HiaRd, CR431 -> PineHilRd (not signed here)
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 05, 2019, 10:51:09 pm
500atav: FL500 -> US441
508: EddAllSt -> EddAllRd
528: move 4A west to OBT?
528: 20 is closed and 19 is open
540: JacLeeLn is an unposted gated driveway. Change to a shaping point?
540cyp: RegRd -> LegWay
563: HarBlvd_S -> BeaBlvd? or should it be moved farther south to about here (https://www.google.com/maps/@27.9907781,-81.9752713,3a,75y,194.14h,72.02t/data=!3m6!1e1!3m4!1sENuk8LZztgAAxD9Iev8cjA!2e0!7i16384!8i8192) per GIS?
566 should be reversed to go from west to east
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 06, 2019, 09:57:08 am
686: TerPkwy -> TerBlvd
693: CenAve -> CR150 (reassurance after you turn)
693: 38thAve -> CR184 (ditto)
708: OldDixHwy -> PBObaHwy
710: SilFoxLn -> FoxBroRd (the more major side)
713: TunFeeRd[sic] is a ramp with no street signs.
717: CR880 -> FL880 (it's signed correctly at this end)
732jen: BreDr is an apartment entrance with no sign
739: US41Bus_S -> FL82? I can't find any signage pointing US 41 Bus. along SR 82
776: OldEngd -> OldEngRd
780: extend east to FruRd_E (https://www.google.com/maps/@27.3386943,-82.4399986,3a,27.8y,296.79h,88.46t/data=!3m6!1e1!3m4!1sV9SF9ZpU-2nDtuwpEORCxA!2e0!7i16384!8i8192) (not CobRd; that's being realigned to the east)
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 06, 2019, 10:37:31 am
800: why is FroRd not east at the underpass?
807 ends at AirCen (https://www.google.com/maps/@26.6794297,-80.0746238,3a,75y,53.88h,87.18t/data=!3m6!1e1!3m4!1sDMax9vTz1V-RIlmkvzGo4g!2e0!7i16384!8i8192)
811: isn't I-95 part of the FL786 interchange?
814: as of April 2019, it is still signed on US 1 and with a JCT assembly SR A1A; it we want to be consistent we should either restore this or truncate 845
818: NobHillRd -> 100thAve
842efl is gone from GIS, and signage seems to have been removed
845: GIS shows it being removed from Palm Beach County, which apparently happened in 2017, but it's still signed as of April 2019
850: GIS shows it's gone; as of April 2019, signs are still present at the east end, with at least one JCT assembly (https://www.google.com/maps/@26.8104519,-80.0769293,3a,15.7y,229.23h,89.22t/data=!3m6!1e1!3m4!1s46D3L0950JZbTyBXNeOI1g!2e0!7i16384!8i8192) still at the west end
880 is signed as state at the east end but county at the west end
886: FloWay -> PortBlvd?
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 06, 2019, 11:34:07 am
924: 42nd/37thAveCon -> 42nd37thAveCon?
934: 81stSt and BayDr seem useless
944: NorMiaAve -> MiaAve
953: MirMile -> CorWay (more prominent on signs)
953: 42nd/37thAveCon -> 42nd37thAveCon?
986: still signed on US 1
994: CarBlvd -> 200thSt (more prominent on signs)
9336: KroAve -> 177thAve (more prominent on signs)
a1a: AtlAve -> CR4075
a1a: HighBriRd -> HigRd (one word on signs)
a1a: CDMarPkwy -> CamDelMar (Camino is the road type)
a1a: AnaRd -> AnaParkRd
a1a: Google shows that US1Bus_N has been realigned to match SanCarAve; Esri World Imagery shows it under construction but doesn't confirm the configuration
a1a: PerRd -> Gate5?
a1a: MayFry -> StJohRivFry
a1afer: MayFry -> StJohRivFry
a1afer: HugPark -> AlaBoatRamp
a1afer: MagSt -> MagLn
a1afer: PinPl -> PineGroPl
a1afor: FIFerDr -> TerIsle
a1afor: TerDr -> FLHIntAir?
a1afor: FL842 -> LasOlasBlvd
a1afor: CarReal -> CamReal
a1ansb: continue north along the ramps to US 1?
a1aver: SebISPark -> SebInlSP?
a1aver: GeoJKingBlvd -> GeoKingBlvd
Title: Re: usafl: Florida State Highways
Post by: oscar on September 07, 2019, 10:32:10 am
Followups on the FL 44 split:

-- For the new FL 44 (DeLand), FLA1A => LiveOakSt, and synch it with the corresponding point in the A1A (New Smyrna Beach) file.

-- In California, I'm treating TO signs as good enough to take us out of "implied multiplex" territory. In response to neroute2's comment here, I kept a 9.6-mile multiplex on CA 99 in Sacramento, with adequate TO signs for travelers to follow the route over US 50 and I-5. CA 16 got split. The lack of any CA 16 signage on the longer supposed multiplex with I-5 and US 50 was just one of the reasons for that split. But if there had been TO CA 16 signage, and no other issues, I would not have split the route.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 08, 2019, 10:07:46 pm
-- In California, I'm treating TO signs as good enough to take us out of "implied multiplex" territory.

That's what I'm trying to do as well unless it's insanely short.
Title: Re: usafl: Florida State Highways
Post by: oscar on September 08, 2019, 11:55:20 pm
-- In California, I'm treating TO signs as good enough to take us out of "implied multiplex" territory.

That's what I'm trying to do as well unless it's insanely short.

What I'm trying to do is for "TO" signs being enough to treat an 'implied multiplex" just like a regular multiplex, no matter how long (unless perhaps the gap between "TO" signs is so long that travelers would forget they were on a multiplex). One such example is I-41/US 41 in Wisconsin. where there are sometimes I-41/US 41 sign assemblies, but other stretches there are just I-41 markers and occasional signs telling US 41 travelers to follow I-41.
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 10, 2019, 07:18:59 am
Should Jacksonville's Mathews Expressway be added to usasf? It's got three interchanges.

us001altjac: JesSt has a separate interchange, and HaiSt should be moved north to the underpass.
us001bussta: see a1a for potential combining of SanCarAve and FLA1A_N
us019altstp: OldFL60 -> CleSt, OldUS19Alt -> FtHarAve
us019altstp: AldRd -> CR816 (signed on reassurance here)
us019altstp: FL582 -> TarAve
us027altper: JoshEze -> JoshEzeRd
Title: Re: usafl: Florida State Highways
Post by: neroute2 on September 12, 2019, 05:47:04 pm
us041busbra: remove W suffixes; 8thAveW -> 14thSt?
us041busbra: FL 43 -> 10thSt
us041busfor: PonRd -> CR78A (there's reassurance after you turn)
us041bustam: remove E and W prefixes
us041bustam: is WilAve really important enough?
us041bustam: CR598 -> SliAve
us041bustam: EBirSt -> BirdSt
us041busven: GolDr -> GolfDr
us041busven: VenAveE -> VenAve
us090altpen: I-10(5) -> I-10
us098buspan: remove W prefixes
us098buspan: W11thSt -> CR28
us098buspan: BobLitRd -> Hwy22-A
us098buspan: BoaRacRd_E -> BoatRaceRd
us098buspen: AkcSt_S -> AlcSt_S
us098trkbro: US98_W -> US98_N, US98_E -> US98_S
Title: Re: usafl: Florida State Highways
Post by: yakra on September 18, 2019, 10:02:32 pm
FL FL417
49 <-> 49A
Length: 0.22 mi
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 19, 2019, 01:38:36 am
FL FL417
49 <-> 49A
Length: 0.22 mi

I could merge that into one point (I think I did it this way because of CR-427), but then I might have to do the same to 50A-50-50B right above it.  That one (50) is a pretty confusing setup of ramps.
Title: Re: usafl: Florida State Highways
Post by: rickmastfan67 on September 19, 2019, 07:27:10 am
NE2, I'll try to start looking over your newer posts this weekend when I have the time. ;)