Editor Version Dec 19th Official Feedback Thread

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: krankyd, Unholy

Re: Editor Version Dec 19th Official Feedback Thread

Postby Spazinbc » Sun Dec 23, 2012 2:05 am

1. Wazers doing the editing should be able to add photo radar (red light) cameras and speed traps.

2. Wazers should be able to dispute or change an approved edit that they may come across. For example, someone is going crazy and adding red light cameras on every corner when all sources including official and visual indicate that there is only one camera. Yet the Wazer approved the cameras and they cant be removed.
Spazinbc
 
Posts: 38
Joined: Tue Jul 24, 2012 4:10 am
Has thanked: 0 time
Been thanked: 0 time

Re: Editor Version Dec 19th Official Feedback Thread

Postby Spazinbc » Sun Dec 23, 2012 9:36 am

I have another feature request.

For street type, include lane. Seems to be this is the only one missed.
Spazinbc
 
Posts: 38
Joined: Tue Jul 24, 2012 4:10 am
Has thanked: 0 time
Been thanked: 0 time

Re: New Editor Version Dec 19th

Postby Timbones » Wed Dec 19, 2012 4:52 pm

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.
Timbones(6) • UK Country Admin & Coordinator • Forum Moderator • Beta Editor and Routing Expert
Scripts: WME Colour Highlights v1.8 (Feb 2014)WME Route Tester
Timbones
Waze Global Champs
Waze Global Champs
 
Posts: 3677
Joined: Wed Feb 09, 2011 10:33 am
Location: York, UK
Has thanked: 181 times
Been thanked: 626 times

Re: Re: New Editor Version Dec 19th

Postby Timbones » Wed Dec 19, 2012 8:33 pm

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
Timbones(6) • UK Country Admin & Coordinator • Forum Moderator • Beta Editor and Routing Expert
Scripts: WME Colour Highlights v1.8 (Feb 2014)WME Route Tester
Timbones
Waze Global Champs
Waze Global Champs
 
Posts: 3677
Joined: Wed Feb 09, 2011 10:33 am
Location: York, UK
Has thanked: 181 times
Been thanked: 626 times

Re: Editor Version Dec 19th Official Feedback Thread

Postby Timbones » Thu Dec 20, 2012 10:29 am

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).
Timbones(6) • UK Country Admin & Coordinator • Forum Moderator • Beta Editor and Routing Expert
Scripts: WME Colour Highlights v1.8 (Feb 2014)WME Route Tester
Timbones
Waze Global Champs
Waze Global Champs
 
Posts: 3677
Joined: Wed Feb 09, 2011 10:33 am
Location: York, UK
Has thanked: 181 times
Been thanked: 626 times

Re: Editor Version Dec 19th Official Feedback Thread

Postby Timbones » Thu Dec 20, 2012 9:03 pm

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
Timbones(6) • UK Country Admin & Coordinator • Forum Moderator • Beta Editor and Routing Expert
Scripts: WME Colour Highlights v1.8 (Feb 2014)WME Route Tester
Timbones
Waze Global Champs
Waze Global Champs
 
Posts: 3677
Joined: Wed Feb 09, 2011 10:33 am
Location: York, UK
Has thanked: 181 times
Been thanked: 626 times

Re: New Editor Version Dec 19th

Postby TonyG-UK » Wed Dec 19, 2012 4:03 pm

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?
Image
UK Country Manager. Area manager: Wiltshire, UK
TonyG-UK
Beta tester
Beta tester
 
Posts: 525
Joined: Mon Aug 22, 2011 4:36 pm
Location: UK
Has thanked: 2 times
Been thanked: 49 times

Re: New Editor Version Dec 19th

Postby TonyG-UK » Wed Dec 19, 2012 8:30 pm

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.
Image
UK Country Manager. Area manager: Wiltshire, UK
TonyG-UK
Beta tester
Beta tester
 
Posts: 525
Joined: Mon Aug 22, 2011 4:36 pm
Location: UK
Has thanked: 2 times
Been thanked: 49 times

Re: Editor Version Dec 19th Official Feedback Thread

Postby TruckOttr » Tue Jan 01, 2013 6:44 am

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.
ImageImage
Hayward, CA, Reno/Sparks, NV, Elko/Spring Creek, NV and apparently the N. NV section of Portola Valley, CA. :-)
TruckOttr
 
Posts: 314
Joined: Thu Jul 26, 2012 6:54 pm
Has thanked: 16 times
Been thanked: 81 times

Re: Editor Version Dec 19th Official Feedback Thread

Postby Tucuson » Sun Dec 23, 2012 7:23 am

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.
Attachments
waze.jpg
Blurry map images
waze.jpg (88.93 KiB) Viewed 374 times
Galaxy S3, Asus Transformer, Nook Color.
Tucuson
 
Posts: 13
Joined: Sat Jun 23, 2012 5:20 pm
Has thanked: 0 time
Been thanked: 0 time

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: No registered users