:!: [b]These guidelines superseded by the Wazeopedia page on [url=https://wazeopedia.waze.com/wiki/UnitedKingdom/Average_Speed_Zones]Average Speed Zones[/url][/b] since Nov 2017
As you may have noticed, there’s now an setting the editor for Average Speed Cameras.
Now this feature is not yet active in the app, but we expect it to appear in an upcoming beta version. Rumours are that there will be a persistent notification on the side of the screen like the traffic jam bar that shows how much longer the average speed zone will be. It’s unlikely that Waze will compute the drivers average speed while in the zone, but we’ll have to see.
:idea: Here are some draft guidelines from the top of my head:
Obviously the speed limit will need to be set correctly. [see guidelines]
Mark all segments from first camera (or sign) to the last - there should be no gaps.
Don’t split a segment if within 100m (300ft) of an existing node
(this equates to an acceptable 3s error for 70 mph, and can be halved for 40mph)
Temporary zones should not be marked yet, as the feature is not active
In future, they should only be marked without splitting segments, and maintained by the editor.
Existing Avg Cameras should be kept, though we’ll review this once the feature becomes live.
The Street Vector Layer extension for WME has icons for segments with average speed cameras.
I wondered this today since I drove a segment I updated on the 15th and the map is updated on the 17th. So guessed it was not active.
As for Temporary Zones I marked one yesterday on the A13/M25 junction since the roadworks here are due for completion in Autumn 2016. But then since they have now permanently made the speed limit here 50mph they might keep the cameras once the roadworks have finished.
As for what it will look like last weekend I went to Germany by car and used Waze for navigation. I have seen the Enforcement Zone that was shown when we was in France since speed Cameras on a navigation device have been illegal in France for a few years. So if this will be what Average Speed Cameras will look then it is a good start to show them.
I’ve noticed a 5ish mile stretch of the A2 is marked as average camera zone when in fact only about a mile is actual average cameras. Going east bound the last average camera is where Well Hall Road (A208) goes over the A2. Also West bound this is where the averageing cameras start and not around the Bexley area where the 50mph speed cameras start. Is there anyone who can change this. Even when editting is available I Still cannot change or put this change forward myself at my level. Thanks
This has already been released (or perhaps it escaped) in the current iOS version.
Camera zone showing on the left hand side similar to traffic jam info when I drove up the M3 to heading for last weekend’s User Conference
I use Android and we are only up to version 4.5.0.901
But with the release notes it says below (I have cut it down)
What’s New:
** NEW** Child reminder alert in the end of a drive - In the end of your first drive, you should see a pop up to opt-in to use this new feature. Please accept it and give us feedback for this new feature.
Average speed cameras - in countries where average speed camera zones are enforced
Known Issue:
Missing the option to manually switch the Map Display mode between Day and Night.
Looks like I will have to complain since it says it should be working but I know it was not when I tested it yesterday.
This thread has raised the issue of a new type of speed camera and how we should deal with them.
Previously SPECS (Average Speed cameras) have needed a dedicated “in” camera and a dedicated “out” camera in each direction for each lane of traffic, which made mapping them in Waze easy.
However with the advent of SPECS 3 Vector which only requires one camera to monitor traffic in both directions (One at each end of average speed check zone) on single Carrageway road.
Waze requires that we indicate which direction the camera is facing (to give the correct warning), however theses cameras are bi-directional. So how do we map them?
(The following are 3 different ways of mapping them on the same stretch of road).
One camera both directions. However the downside is Waze wont alert for the camera in 1 of the the directions, however it should indicate the average speed check zone, which should be fine, however it will lead to load of UR for missing cameras.
Two Cameras superimposed on each other I believe that this method will give the correct feedback to the user, however an editor (If they don’t zoom in) could mistakenly believe only 1 camera is mapped).
Two Cameras mapped with separation As above, I believe that this method will give the correct feedback to the user, however an editor may remove one of the cameras because there is only actually 1 camera out on the road.
I believe that the mere fact that these average speed check zones are been mapped in different ways indicate the some sort of guidelines/policy needs to be formulated.
So to those editors who have a far better understanding of how this beast works, over to you.
If the camera works in both directions, then you have to place 2 cameras on the Waze map, one facing in each direction. These do not have to be exactly on top of each other - bear in mind that GPS accuracy isn’t that great, so even a perfectly placed camera may announce anything up to 10m “wrong” in the app because the app has the driver positioned incorrectly.
Any editor who is concerned that only one camera is mapped will zoom in and see them both.
As for whether or not to map ASCs at all, I would say a definite yes! If you don’t map them, users will simply continue reporting them until you do. And some inexperienced editors have a tendency to approve any camera they see. If the correct cameras are mapped properly, the number of app reports will decrease massively. If you have a mapped camera that you are positive is in the correct location, you can ask a higher-level editor to “nudge” it for you: cameras are automatically locked to the level of the last editor.
Another good reason to map them is safety-related. Slowing down only when you pass an average speed camera is pointless. But there are plenty of drivers who don’t realise this and will slow down for them. Also, drivers with good local knowledge of the camera placements may drive significantly faster up to the first camera they encounter and/or speed up significantly after passing the last one before they leave the ASC zone. So having the cameras mapped provides an indication to users that the behaviour of cars around them may change at those points.
I raised a UR on the A1079 on Monday for two cameras being shown when only one is present, so there are problems with this approach. The extra one has now been deleted (not by me, I’m only a level 1), but I do accept iainhouse’s view that if a camera is shown as only pointing in one direction, people will report a missing one in the opposite direction.
The obvious answer to this seems to be that Waze needs to keep track of technology, and recognise that cameras now point in more than one direction at once. Presumably the UK isn’t the only country to have these cameras, so it will be a problem for others as well. The answer seems to be to have a ‘Bidirectional’ tick box on Cameras, and then the problem will be sorted properly.
If this isn’t done, we’ll end up having to put in something which doesn’t reflect reality, and as Ron9516 points out, each approach has disadvantages.
Is this over to our Country Manager to try and speak to the developers?
The standard response to a user reporting duplicate cameras is to explain to them that this is how we map reversible or bidirectional cameras and close the report as solved. If an editor actually deleted one of them, they are not editing well.
As for speaking to the developers - I’m guessing you are new here, aren’t you? :lol:
The chances of us getting Waze developers to listen to anything are minimal. It’s now 18 months since we asked for a simple functionality change for red light cameras that also measure speed. Nothing has happened. Nothing may ever happen. Meanwhile every red light camera in London sprouts an extra speed camera every week or so and we have to keep deleting them. :x
I am new here, so please excuse me if I’ve not become disillusioned just yet.
It does seem very silly to have loads of volunteer editors here putting in countless hours to corrupt the map by putting copies in of cameras rather than Waze just correcting the basic data structure so it reflects reality.
The road which sparked off this discussion incidentally, the A1079 near Market Weighton, now has the correct number of cameras in there (one at each end of the average speed zones), but they don’t seem to be doubled up (at least as far as I can tell). The editor for each is a string of digits, so I assume not a person as such.
I’ve just been down the A1079 again, and there are still two speed cameras showing where there is really only one. It’s here and I’ve logged a UR.
The guidelines say that the cameras should be on top of each other, and these aren’t, which is probably what’s causing the problem.
The problem seems to persist all the way along the A1079 towards the Killingwoldgraves roundabout (Jn with A0135), with two cameras shown everywhere. Ironically the only place you only see one camera is on the Dual Carriageway section, where there are actually two real ones. I assume that’s because one is not on your road.
The cameras were both created by ditchi56, so aren’t alterable by mere mortals.
This is a tricky issue, as I’ve been ticked off in the past for putting cameras exactly on top of eachother, as this makes it difficult to see that there are two in WME (the web editor).
I’ve move them a bit closer so that you have to zoom in to level 6 in WME before it becomes obvious that there are two.
Dual carriageways are easier because the cameras are automatically separated by being in opposite carriageways, and yes, I think the app does only show the one in your carriageway.
Unfortunately not, because the Waze cameras are directional, i.e. only apply in one direction. If the real camera can rotate, then two Waze cameras are needed if warnings are to be given for both directions of travel.
