I would suggest MisssyO to force a map update of the area with problems.

Map update is not always forced all the time in all phones everytime there is an update on the map, the update has to have a threshold on map changes within a tile to trigger the auto update. It is gradually updated on users on the area.

You can still manually force the map update if you go to navigation menu, Config (The sprocket icon in the top left of the destination screen) - Screen and Map - Data Transfer (at the bottom of the list) - Refresh map in my area.

I hope this can help you with the data update.

Best regards from Talca, Chile,

On the email - there should be a link where your report is located - can you please post that here?

This is the email in its entirety, except for the footer:

Hi MisssyO,

You received a comment on the map issue you reported, from 08.29.2016 on N Martin Luther King Jr. Blvd, Baltimore - “35 mph”. An editor from the Waze mapping community wants to solve the problem, but needs some more information.

SirGadwall on 08.30.2016 07:29 PM:

This speed limit report is being closed because it was on a road segment with an already verified speed limit confirmed using recent street view imagery or other means.

You can reply using the Waze mobile app, or https://www.waze.com/editor/?zoom=5&lat ... 14&env=usa in the Waze map editor.

Except that when I'm driving on that road, Waze says that the speed limit is 25 mph....

I'm finding many verified speed limits which are wrong, so it can't be taken for granted

fernandoanguita wrote:You can still manually force the map update if you go to navigation menu, Config (The sprocket icon in the top left of the destination screen) - Screen and Map - Data Transfer (at the bottom of the list) - Refresh map in my area.

This option is not available on the current iOS version.

That road IS showing 25 on the segments north of the intersection with Madison. A reasonably recent Street View photo shows a 25 zone sign just north of madison on the northbound side and a 35 sign just south of Madison on the southbound side.

I'm not really sure where the problem is here.

You submitted a SLUR indicating that the actual limit here is 35MPH.

StreetView confirms there's a 35MPH sign at the point where you submitted your report.

WME shows that the most recent edits along this section of road were in June, and that the limit along here is already set/verified to 35MPH...


Put yourself in SirGadwall's shoes - you've submitted a report which appears to be nothing more than a confirmation of the information already present in WME, and since there's nothing that appears to need to change in the map data, the response they sent back to you is technically correct, if a little cold. Personally when dealing with such reports I'd thank the user for taking the time to verify the limit data, but that's a side issue.


Now, are you saying that your copy of the app was indicating a limit other than 35MPH here? If so then that *is* an issue, I'm just not sure it's one that could be fixed within WME given that the speed limit values in the map data appear to have been correct for at least the last 2 and a half months.

MisssyO wrote:Except that when I'm driving on that road, Waze says that the speed limit is 25 mph....

This isn't the first time I've heard from a user complaining that the limit shown in the app isn't the same as that set in the map data, and where there haven't been any recent changes to the map data which might have indicated that at the time of their journey the limit data could have been set incorrectly...

Unfortunately, as noted above, once we've set the limit data correctly in the map editor, there isn't much else we can do - how the limit data then gets processed for use within the app, and how the app itself decides which limit to show onscreen, is entirely the responsibility of the Waze developers, but they aren't the ones reading/dealing with map issue reports