Had a question about the best way to report weather hazards, primarily fog. I posted a hazard as I enter the fog and periodically while still driving in the fog but eventually Waze tells me that I have posted too many hazards in a short period of time. What is a good rule of thumb for posted hazards like fog so they give other users a realistic idea of what is actually happening on the ground?
When on a two way road, you can post the fog alert as you enter the fog. Then when you leave the fog, post it for the other side of the road. That way drivers coming from the other direction will get the alert coming into the fog from the opposite direction.
This will only work for two-way roads though, since reporting fog on the other side of the road when on a one-way freeway will not be seen as an alert by any driver. Only the only as you enter the fog going your direction.
I really wish Waze would remove rain as a hazard. Heavy rain that is blinding can be a slight hazard but typically general rain while a hazard is also generally EVERYWHERE and about 99% of the time people realize it’s raining without having to see a hazard report about it every 1/2 mile :roll:
In my area anytime we get the slightest sprinkle of rain about 40+ reports are generated!
That is too bad. The original idea was to have only one report on the road go up at the start of the weather hazard and not be reported continuously inside of the hazard since you already know it is there once inside. 
I was actually surprised Waze doesn’t have a flood hazard report since that would be pretty important to know and help keep from driving on roads that are flooded or at least warn them.
It does. Voice command. Search the forum. You’ll only get 5 pages of posts. :mrgreen:
Alan, I don’t use the voice commands and actually did not realize there are other options not available in the UI. I see in the Wiki we have a voice commands page, but I noticed the table being built on the page by Crazycaveman back in Aug 2012 has not been promoted out of the comments yet. I think we should move it to the viewable state, but if you already are familiar with the voice commands, maybe you can take a quick peek at the list?
I think we should also add a note on each entry that is ONLY available by voice command.
It seems strange why we have voice commands that are not supported in the manual UI. It might be interesting to collect a list of such commands or options that are only available by voice if Waze is going to continue to support this option only. However, I disagree with it as a long term solution (voice only commands not in the manual UI). Do you have any background on why they are doing it? If not I can pose the question.
Perlin promised that the voice and manual commands would match “in the next version” back when 3.5 was in beta. She’s gone now, so maybe Hila will be more on top of this.
I doubt it. It’s Yael and the Product group which makes decisions on what the devs work on.
I wasn’t aware of the wiki side. There has been a Voice Commands thread in the App forum since July 2012 I created. Perhaps a wiki version would be useful.
I am moving my Voice Commands questions to that thread to complete the Wiki update.
And since nobody from that department is looking at Bugzilla, who if not Perlin or her successor would inform them of the issues brought up there and communicate that information back to the community?
Not sure why you say that. I am in contact with the team looking at Bugzilla. In fact I just got a few updates to Bugzilla status types that were not in the Wiki. I have even seen one of my reports move to a status of “PRODUCT” meaning it is being scheduled for an upcoming release.
It doesn’t matter. What I was referring to was that Perlin was indeed the person who coordinated the beta team and communicated between beta testers and developers. I erroneously referred to Bugzilla; the bugs I reported went through Centercode. I have a hard time picturing Yael scanning the list of bugs and feature requests.
That’s why feature requests should not go into centercode. It should be reserved for beta bugs only. IMO.
I too think weather waning reports would be a good idea, in Bonnie Scotland the weather changes very quickly at times , from fog , heavy rain and in winter snow. So a thumbs up from me for such an addition to Waze and safe driving being of the utmost importance. The weather forecast can be so wrong at times and as far as I am aware its a feature I havent seen on any other GPS Nav software.
I wish Waze would eliminate the “rain” and “snow” reporting options. If I am within 0.5 miles of the place where you reported rain or snow (which is when these reports seem to go off), then it is almost certainly already raining or snowing where I am.
My complaint is only for these two specific categories; other types of weather hazards are more localized and entirely appropriate for hazard reports.
I agree these two in particular are more helpful telling me when they are 10 miles from my current destination and on my route. If in a convertible I can take action. If I have an uncovered load in a truck, I can take action.
PLEASE remove the “rain” report! Another reason is that when it is raining, what I want to be alerted to are hazards associated with the rain - stopped cars, accidents, etc. - NOT the rain! And I live in Seattle, so it’s even more annoying to see this report!
I always thought the rain and snow warnings were for heavy, sudden squalls, as often witnessed with some of the lake-effect snow squalls along the lake shores or pop-up summertime thunderstorms. The key word is acute - sudden and highly localized. Same for fog, even.
I can’t stand the stopped car alerts that litter the freeways and other high-speed highways all over the place every time someone stops along the side of the road to like answer the phone. It really is an over-dramatic announcement for a mere possible hazard that is off to the side and out of driving lanes, and it really makes people pay less attention to similar but much more serious alerts like objects in the road.
Anyone remember about the boy who kept crying wolf? The more false alerts you have, the higher the chances of a real alert being missed or ignored…