Waze forum

TonyG-UK wrote:This raises a few questions, due to the way the client actually processes speed camera information.

• In what unit is the information sent to the client?
• Have you fixed the client to process these properly?

Good questions. It seems that the editor is still storing km/h in the model data, so we still need an appropriate fix in the client. Previously, Waze would only alert if the current speed (mph) is greater than the speed of the camera (km/h), which usually isn't. The client is missing the formula for converting km/h of the camera into whatever the local units the user has selected.

Any cameras which were previously set to have speeds in mph will appear to have the wrong speed, even if they trigger at the correct speed.

bgodette wrote:It's unitless. The only thing that's changed is the text while editing the camera is now mph instead of kph for the UK and US.

Edit: I type too slow.

Not quite. The editor *is* converting the values from km/h to mph when displaying them in the editor. A 40 mph camera is recorded as 65 km/h in the model.

The client still treats them as unitless for the purposes of camera alerts (I'm guessing), so "65" triggers at 65 mph or 65 km/h, depending on your units. Client should be making the appropriate calculation. Either Waze misunderstood this when we explained this, or they have a client beta due out soon...

In the UK, we've stuck to entering km/h before now. Now they look correct in the editor, but won't trigger at the correct speed.

If you've been entering mph in the US, then they'll appear wrong in the editor. Unless they've done something different on NA?

via mobile

BUG: If you makes some changes, and navigate to another page, you no longer get the warning about losing unsaved changes.
(The callback to aboutToLoseChanges() is missing from window.onbeforeunload).

We've seen the zoom 'feature' before, in an earlier beta. It was much better then.

WAZE: Please implement caching of road tiles and compression of other requests (such as Features). I wrote a detailed technical post on how to do this 9 months ago.

via mobile

shirlig wrote: * UK and US now using imperial system in speed cams

This raises a few questions, due to the way the client actually processes speed camera information.

• In what unit is the information sent to the client?
• Have you fixed the client to process these properly?

bgodette wrote:

TonyG-UK wrote:
This raises a few questions, due to the way the client actually processes speed camera information.

• In what unit is the information sent to the client?
• Have you fixed the client to process these properly?

It's unitless. The only thing that's changed is the text while editing the camera is now mph instead of kph for the UK and US. That was a large part of the confusion about speed cameras. The client would alert by just comparing the unitless number vs the displayed speedometer (which is either kph or mph) also as a unitless number.

That's not really true, as the speed set on UK speed cameras has been converted as part of this process. The old value has been taken as km/h and converted to mph under the new editor version. However, the client always takes the value as the local unit. So, as Tim said above, all the speed cameras that were set correctly to work around this client bug now appear to have an incorrect speed in the editor.

Having problems tonight with changes taking several minutes to update in the editor.

A) Make Change
B) Save
C) Map reverts to pre-edit version

Yep. It says it's saving things, but then it goes right back to the previous version.

I am having problems with the map since the update. Areas are showing blurry images and cannot edit because I do not see the roads. Is this going to be fixed soon? I wait to see if the image loads but it never happens.

shawndoc wrote:This is going to take FOREVER to clear, and since they are UR's, its going to be tough to find actual User Requests mixed in with all the auto-URs.

I haven't been able to find any to test with, but if the description text used by these auto-URs contains a specific keyword/phrase, then it should be possible to hide them using my UROverview script (if you're a Chrome or Firefox+Greasemonkey user)...

http://userscripts.org/scripts/show/145186

If anyone does come across a fresh batch of these URs, can you please send me a permalink so I can try grabbing some info about them before any eager editors clear them up - it may be possible for the script to handle them directly, in the same way it deals with other specific types of UR (Missing exit, Turn not allowed etc.)

jemay wrote: https://www.waze.com/editor/?zoom=5&lat ... TTTFTTTTFT

Three in that area now, but don't know how long they will be there...

Excellent, thanks! I've added a specific filtering option to the latest version of the script, anyone who's interested should pay a visit to its thread here (world server) or here (usa server)