I have decided that when I enter speed limits, I will try to change the speed limit approximately 3 - 5 seconds before the sign. It seems to take Waze 1-2 seconds to display the SL on a new segment, plus as a driver it’s nice to have about a 3 second warning of an SL change (sometimes more in the case of a reduction).
As I drive, I see lots of SL signs on side roads that I’m passing. Anyone have a good way to handle this type of BOTG information? If I am on a 50 MPH road and see a 25 MPH road taking off to the right, that’s nearly impossible to drop a UR on the fly with all of the description.
I’m seeing lots of incorrect SL’s as I drive. It seems that whenn I drop a UR and check, SV is incorrect in many locations. I just ask everyone else in MA to keep an eye on the SL as you drive, there is a lot of opportunity for improvement out there that street view just can’t handle.
[gets on soap box] I wish the SL was always visible, not just when I am exceeding the limit. A lot of the reason I was looking forward to speed limits is so that the dunderheads who drive slow and hold up traffic have another indication that they are driving too slow. Route 114 from Danvers to Lawrence is notorious for the single driver to do 30-35MPH even though the speed limit is 45, and there is no way to get around these fools. If the app showed them the speed limit was actually 45, they might take a moment to look in the rear view mirror and realize they are holding up a line of hundreds of cars… [gets off soap box]
(1) That’s probably fine, assuming that the speed limit doesn’t change going both directions at the signs. there’s some leeway for speed limits anyway. I personally put the limit where the sign is since 1-2 seconds don’t really matter anyway.
Guidance says “However a new junction should never be added for a SL if it will be within 200 feet of an existing junction, or potential junction.” which implicitly indicates that having the speed limit change up to 200 feet (or further) from the actual sign should be okay.
That being said if speed limit changes in both directions at more or less the same place, it’s probably better to just put the speed limit where the sign is, otherwise you have to have two different junctions for speed limits, which is more work and somewhat against guidance. In fact if the two directions speed limits change within probably 200 feet of each other (in opposite directions), I just create a junction half way between the speed limit signs.
(2) Remember that most 25 MPH roads taking off on the right off of a higher speed road are exits (not speed limit in a white rectangle) and are just advisory speed limits which we don’t routinely map. I’m not sure if that’s what you’re referring to, but you’re not supposed to drop URs anyway :? while driving per Waze TOS: “It is strictly forbidden to send traffic updates (such as updates on road accidents and traffic congestion), or to non-verbally interact with the Service or use the Service in a non-verbal manner for any purpose other than navigation while driving.” It seems that your passenger shouldn’t have any trouble with this right?
(3) Agree, though I’m usually driving by myself so it’s hard to drop SL’s.
(4) Totally agree. I think that in the settings for when to show speed limits, in addition to the “at speed limit” and all the exceeding speed limits option, there should also be on that says “always.” That’d be great. That being said, I totally doubt that any wazer is to blame for holding up traffic. They tend to be in a hurry to get where they’re going :lol: .
I agree with not adding junctions, but I think that guidance goes on to say that this is a convenient time to add some PLR’s if need be. I think I’ve only added 2 junctions merely for the sake of speed limits, when there was pretty much nothing around for 0.1’s of miles.
Speaking of which, I’ve also been realizing the need for PLR’s, even for doctor’s offices and things. Not just to navigate to your destination, but so that Waze can help you optimally leave your point of origin (without thinking you’re already heading the wrong way up the street) after your root canal or other surgery.
1 - just a reminder that the driver should also be aware of and watching the road at these times where the speed limit changes. The big sign on the side of the road should be easier to read than the phone’s small screen, so dont loose too much sleep on that one. The real value is when you have gone half a mile down the road and dont remember.
2 - yes it would be nice to have an easier way to submit speed data for side streets, you could try just leaving the other SL with WSLM at that intersection. but I do find the TOS funny in that if you are reporting gas prices while driving it challenges you if you are a passenger… but not for reporting a map issue… just saying.
3 - Dash cam, WSLM, memory… yeah it is tough, but the nice thing with it going live now is we have a lot more people out there who can help point out the errors. And i am SHOCKED, simply SHOCKED to hear that we did not get 100% of the Speed Limits correct after the recent map raid.
4 - remember there is ##@debugspeedSearch Codes with iOS it does show your speed 24/7 even when stuck in traffic on comm ave with all the students playing frogger. Although I doubt the app saying the speed limit is 45mph will solve your issue SR-114, just like having the speed limit is not going to stop people from doing 50mph on Storrow Drive.
Nope. That is a public code revealed in the wiki. While not ready for release to a production Waze app, it is deemed to be a great tool for map editors.
I’m curious what others think about SLs that have been dropped, using WSLM/WURM or created by any method actually, that continue to remain open with no responses. I’ve seen them in WME with open windows of up to 34 days and no response.
Whenever I have created one, it may have taken me a while to close it, but I eventually did.
Do we let the reporter close them? From the way I see the UR, I’m guessing they were created by other editors. I’m making the assumption the custom WSLM/WURM URs are editor created.
Do we try to validate with SV, even though, in some cases, I’ve seen SV as old as 2007? (It’s so nice when SVing in 2011 and all of a sudden I’m back to 2007. How does Google manage that??)
Do we accept them at face value and make the change?
I’m inclined to accept them at face value, make a downlock request and then make the change, especially the WSLM/WURM ones.
I’m reluctant to accept the anonymous ones (the WURM ones tend to be from known editors), as I’ve more than once found the report to be wrong (based on BOTG).
My personal preference is to have someone remind me that I dropped a UR, and I’ll go fix it. Personally I don’t spend enough time looking at UR’s in general (probably because I get anal about fixing each one but that’s a different issue), but I typically forget about them so it’s easy for someone to remind me that it’s there - a link in the HO, or even just a comment “hey bob don’t forget this” so I get an email when I’m at my computer and can go fix it.
Thanks for reminding me, I dropped a few last night (that I’d already forgotten about).
I prefer to have the editor add them themselves as they did the effort for BOTG and since we are live with speed limits there less urgency to add them.
I do not add anonymous ones without visual confirmation. And if they conflict I will inquire.
On the flip side I am not going and confirming a speed limit that is in place if I make other edits to a road segment due to the hassle that can be.
Does it not work on Android? I am not a beta tester and while I do get the popup indicating I have activated SL Debug, nothing changes on my screen. It would be great because I have become obsessed with fixing SL issues. I submitted a request to sign up for the beta a few days ago but haven’t heard anything.
This is also my situation. On my Android app, the code appears to work and displays the debug activated message, but nothing seems to be different and the speed limit is only shown when it is exceeded.
Not sure how long the feature has been there, but I accidentally discovered that if you click the speedometer within the app, you’re given a choice to show speed limits all the time, and also an option to directly report a speed limit addition/correction. It works well.