I have been going over the toll roads for Orlando. I have a question:
How are you guys naming these roads.
SR-429
SR 429
SR-429 Western Expy
SR 429 Western Expy
or the wiki standard:
State Route 429
I have seen all of these on this particular route alone. Just want to make sure I am getting it the way you guys wanted it.
SR-## should definitely have the hyphen. Seems like everyone is going to the short form everywhere.
I just drove SR-417 and theres a toll every two miles. Too bad the avoid tolls isn’t functional yet.
I’m not drunk…I’m using Tapatalk.
Ultimately it shouldn’t matter, should it? Once we get the shields names will be invisible on the map. SR-417 will probably look better in the navlist but it shouldn’t show up at all anywhere else.
FWIW TTS will say “State Route” for SR with or without the hyphen. The question is, do you want to have it say “State Route” in a state like Florida where they’re not called state routes?
We just need to get it standardized so that there aren’t 1000 variations. The best way to do it would be to use the state abbreviation. Then whatever the state uses could be verbalized however is the local custom. Whether it be State Route or State Highway or LA-##. It works fine in Louisiana like that BTW. Just need it to generate a shield.
I’m not drunk…I’m using Tapatalk.
Thats the reason I asked SR-429 had like 5 different names to it. I haven’t driven this way in a while but I thought each name changed triggered an item in the nav list. It might not trigger a TTS direction but I think it still shows up in the nav list. I agree that it needs to be more consistent. Hence the reason I posted it here. I didn’t really care so much what (Florida AM’s) they wanted it to be, I just wanted to make it more consistent.
BTW, I will take 417 over going downtown through Orlando on I-4 any time. It is a nice relaxing drive compared to going through I-4.
I also find it interesting that three non-floridians are talking about a florida road. These boards really need to get more exposure some how and probably are perfect for these type of discussions.
Just happens that I’m right off the northern end of it right now.
If you simulate in LiveMap, each change does generate an item in nav list. Don’t know about on the client but I suspect it’s still an additional load on the server.
I’m not drunk…I’m using Tapatalk.
None of the above, see this thread from the Florida forum: http://www.waze.com/forum/viewtopic.php?f=193&t=19394
Some background…
When I first started editing Florida roads (as an AM), most of the state roads were labeled “State Rd #”, and they did not have shields because they did not conform to “State Rte” or other shield formats. I did not bother changing them all because there were more important issues to deal with. At some point, I was lead to believe that waze was going to support shields for “SR-###” format. As an experiment, I changed all “State Rd 417 (Toll)” segments to “SR-417 (N/S)”, removed toll and made sure toll was included on all ramps. The TTS was fine (although it said route and not road) and the smaller amount of space it took on the nav-bar was a plus. Still no shields. I then changed a couple of other state roads to “State Rte #” format, and tried to work through support to get shields. Support said the shields should be there, but they never showed up. My guess is because the roads in question also included E/W in the name, which I now know provokes a known bug in shield generation. Another example, ever since the I-4 format was changed from “I- 4” to “I-4 E/W”, we have not seen shields since. I gave up. Later, a new AM in South Florida started the thread regarding SR name formats (see above link), and as a result of that thread it was declared that “State Rd #” format would be used as a preference; since mapcat said that waze promised to support shields for that format some day. Since then, I have not bothered to change any of these SR segments (format changes) because I’m too busy fixing mistakes that are being made daily by new editors that don’t know what they are doing (most of them were invited to fix issues when we AMs closed URs with “Not Identified” for URs that were not map errors but were really routing server issues or just local traffic jam related.
As soon as waze announces a new shield feature (maybe allowing editors to actually define shields in WME), I’m expecting power users (maybe country editors?) to swoop in and make all of the changes while I’m still too busy fixing mistakes made by new editors. :lol:
Don
I know how daunting sifting through user updates can be. That is why I posted this in the forum as I was trying to get 429 fixed up with the toll road marker. I just didn’t know how you guys down there wanted it to be labeled. I was going through the road and I wanted to get it labeled correctly. I was just confused because it seemed to change names every few miles. Most of the other roads I had looked at had a SR-XX designation. I also missed the post you linked to that probably would have answered my question.
I will get it changed over to State Rd 429 N/S in the next day or two
Florida uses the outline of the state with the number over it like Louisiana.
But the informational signs all seem to use SR-##. I could also swear that the signs indicating the end of 417 said St Rte.
I’m not drunk…I’m using Tapatalk.
The weird thing is that the Florida Turnpike Authority refer to them as Toll Rd XX along with their designated name (i.e. Sawgrass Expressway).
Illinois does the same. Mapcat went through and named all the Chicago expressways and tollways.
Sent from my iPhone using Tapatalk
Seminole and Orange County GIS both call it State Road 417, news media uses State Road 417, as do the locals (which is supposed to matter, right?).
Welcome to my nightmare… where the only consistency with road naming by Florida DOT is inconsistency. :lol:
Many roads in Florida have multiple names and I’ve seen many examples where signs change up and down the road from SR-# to some local name and back. It’s a nightmare when you’re editing, and don’t even get me started on how many incorrect signs I have found (causing even more URs).
Hope you don’t think I was being critical of the naming conventions. Just the inconsistency in the naming of the road is what sparked my question. As many times as I have driven on those I just automatically thought they were state routes (FL-417, FL-429, etc.). It is now named SR-429 N/S now throughout the whole length of the road. Is this good enough now for you Floridians or do you want me to change it over to State Rd 429 N/S?
No way, I know you’re not being critical, please don’t take my venting personally, sometimes I just like to complain. :lol:
Personally, I think SR-429 N/S is fine for now because I don’t see the point in thinking too much about the format until shields are working reliably. When waze delivers a working solution for shields, we should then take the time to adopt a consistent naming convention, one that might be influenced by the supported shield formats.
Thanks, Don 
That is fine with me. If I do come across these roads while I am editing something else though, you would like it to say State Rd XX though, correct?
There’s a good chance that shields will never be generated automatically again, and editors will be responsible for adding them. So I agree it’s a good idea to put off any decisions until this is finally settled.
I agree with mapcat, no need to change the format yet. If you’re working on a road that has inconsistent names across segments (and you know they should be the same), maybe just take the easy way out and use the name that is being used on the majority of the existing segments, as long as it follows one of the formats that we’ve discussed.
Some of the state roads switch between a number format and named format, like State Road 436 being Semoran Boulevard, Altamonte Drive and State Road 436, so we try to keep the local name and we use local county GIS as a guideline.
Thanks and regards, Don
Hi all,
Just wondering about SR-60. Noticed most of it is named State Hwy 60, is this the format we’re sticking to? Doesn’t seem to jive with other State roads designated as State Rd xxx. Is State Hwy xx used solely for the purpose of generating a shield?
If this is the way you all agree to name 60 (State Hwy 60), I will leave it alone. Hopefully waze will get us floridians up to the standards of most of the rest of the country. I do know we’re kinda unique with our State Roads vs State Routes 
Thanks, razor2k
Until waze provides a new method for shield generation, it’s a waste of time making name changes, especially if the current name and segments have shields. If you change the segment names, the Shields will be gone.
Sent from my DROID RAZR using Tapatalk 2
Thanks Don, that’s kinda what I thought. Over here I notice very few shields 
I-275 & I-75 have no shields although now that I think about it, I believe some sections did but not now. I think I read somewhere that adding the N/S designations caused shields to disappear :o Hopefully this gets straightened out soon also.
Thanks