Are you looking for more points to be the top scorer ?
Why not earn those points in being the top ‘fixer-upper’ instead of the top useless ‘red road’ paver.
I challenge you all to install Timbones’s Color Highlights for WME and then look at your areas again. I’m sure you will be horrified at the lay of the land in your own home turf when it exposes all the naming flaws, all the pieces of newly tarred roads and the general disarray of the stuff you think is ‘fixed’ and running like clockwork.
Some simple examples… red tars lying underneath existing Highways & roads, portions of road in Pretoria City Center named Centurion, South Africa. Hundreds of unterminated cul-de-sacs, inconsistent City names for roads that are all in the same suburb, hundreds of unnamed roads.
Do yourself (and the rest of the ZA Waze community) a favor and mosey on over to http://userscripts.org/scripts/show/141050. Install this piece of art, and be ready to get shocked…
I discovered this script a week or two ago.
I have found it incredibly useful to identify unnamed, and ‘uncitied’ roads, as well as cul de sacs without a node at the end ("Unterminated roads’). All in all an extremely useful tool for making sure that maps are complete.
Agreed, the tool does make life simpler.
Tim is very open for suggestions, and that’s where the filter by User, filter by City and the counts came from - I think the AMs flooded him with requests via PM. It’s a good thing that there are some bright boykies out there.
One thing to notice about the script is that most of the streets for filters and City / Street names are only exposed by WME if you are at lower zoom levels, i.e. Zoomed in quite high. At zoom level 3 (200m/1000ft) most segments are visible, but not all segments are ‘selectable’. At zoom level 4 (100m/500ft) and lower, all segments are usually selectable.
Only the names from the selectable segments are exposed from WME, so only those would appear in the filter lists. If you are zoomed out too far, the functionality might not be spot on. The script is not really buggy, it’s just that Tim can only work with what is exposed by the WME editor.
If you use Chrome, the script will not be automatically updated, but it will be for Firefox with Greasemonkey.
I use Chrome, as I find it’s WME performance faster than Firefox. In this case, it’s likely better to subscribe to the Forum thread for updates.
For the die-hard Safari fans, Mike Bronner made a Safari extension available at https://github.com/mikebronner/WME-Color-Highlights, or you can follow the link from Timbones’ userscript page at http://userscripts.org/scripts/show/141050
In a nutshell, there’s almost no excuse NOT to install it
Have given it a go but it refuses to agree with my installation of Chrome (21.0.1180.89)…
The script runs but all the roads are hidden regardless of which check boxes are checked. I have uninstalled it but the roads still don’t show. Currently I only see the roads in Chromes “Incognito” mode. Any suggestions?
As at 01:30 ZA time, the International editor is still down. It’s not the script.
You can test it by logging in on http://www.waze.com, you should at least see some roads there, even if you are not allowed to edit them.
To check for loading problems:
For Chrome users, you will see the following in the error log if the road data is not loading: Failed to load resource: the server responded with a status of 500 (Internal Server Error)
or GET (a very long URL ) followed by 500 (Internal Server Error)
To view the log, use the “Control+Shift+J” shortcut & click on Errors in the bottom status bar.
Only errors in the log will be shown, so you do not have to scroll through a few hundred messages to check for errors.
If you use Firefox, you can use 'Tools / Web Developer / Web Console" or the Control+Shift+K shortcut.
That will show something like –
[01:26:03.982] GET {long URL} [HTTP/1.1 500 Internal Server Error 10259ms].
I did also verify that Cape Town is STILL on the map, just in case RodNav had a sleepless night about his neck of the woods
One thing I did notice sometime over the weekend is that the editable segments tend to go off-target with the images on the map if you do a bit of basic work like zoom in / out or pan around. The segments all appear slightly to the right and lower than the actual road image layer, which is also still properly aligned with the Bing image layer.
I thought this was due to one of the custom scripts that I was buggering around with.
I had this previously only with the WME Extended tools installed, but it does it now even with all scripts disabled or even uninstalled. It’s still doing it today.
I had the same issue with no scripts running at all. It seemed to have solved itself after the next tile update - in the position that I indicated as opposed to the one it “moved” to. It seems to come and go, I haven’t had any issues today.
Yes, I’m relieved! Although, imagine all the points and edits I could rack up if I had to map Cape Town from scratch? :o
This has been something I have noticed for months already - long before I discovered scripts. But it’s not always there, and I have no idea what causes it.
I have also noticed this randomly while editing at different times. I think it might be something “hiccing” on the editing server. It does not seem to make trouble, you just have to remember to click off target a little.
Another bit of madness I randomly get is when I click “Save” the editor takes me to any random place in Europe and shows me an error about a road a million miles from where I’m editing.
Ah well… it’s all for nothing we don’t get Map tile updates though… that’s my biggest gripe at the moment. sigh
