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.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?
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.
Re: New Editor Version Dec 19th