Highlight by City will include the State as well, including No City for each State.
Hi Tim,
With the release of the parking types to the editor would it be possible to vary the colouring of the different parking lots :?: I’m guessing the polygons do not have any info stored but surely they must link to their data somehow and you could read which type is selected (showing my coding knowledge
)
If it is possible may I suggest Public be left as is, Restricted has an Orange border, & Private has a Red border (all with the blue fill)
While I’ve got you wondering, I find having Construction Site highlighted a Brown so I can keep an eye on new developments & just for ‘fun’ Cemetary in Grey as a difference from Parks at a glance.
New Version! v2.22
- Added ‘Unpaved’ to Road Types, under Special Flags
- Added highlight for streets without house numbers (thanks jangliss)
- excluding Roundabouts, Freeways, Ramps and Non-drivables
- Parking lots now have different border colours depending on their type:
- green = public, orange = restricted, red = private, dashed = not set
- Removed highlight for unterminated segments (no longer occurs)
Note: I’m planning to remove the ‘Soft-turns and U-turns’ highlight in the next version…
Could you please split settings for Highlight places to:
Color places (by categories)
and
Highlight places (by filters like recently edited, or edited by…)
Currently it enables/disables both.
Thanks.
I am seeing many occurrences of this error in the console under the new beta:
WME Color Highlights: 2.22
Uncaught TypeError: Cannot read property ‘appendChild’ of undefined
at initialiseHighlights (eval at <anonymous> (:2:297), <anonymous>:1265:10)
One request, one possible bug. I did not read through the entire thread so my apologies if these came up before and were dismissed and not possible or not wanted.
Possible bug: I have been using the script extensively while auditing city segments, especially under the newer guidance for alt city names attached to ZIP code city names in the US. Generally I use the highlight city option inverted, to highlight segments with incorrect city naming. However, when something happens to my WME browser tab and it gets buggy and I have to load a new tab, the “invert” checkbox becomes unchecked. Not a huge deal, but since the other checkbox selections always come back the same, wondering if this one can be saved for browser reloads, too.
Request: I am also auditing for missing HNs, and the “No HNs” option is great for that. The no HNs feature for TB only works on Street segments, while Highlights works on Streets and higher types (thank you), but neither works on PR segments. Can Color Highlights be modified to show when a PR is named but has no HNs?
Thanks for all your hard work on this stuff, much appreciated.
Thank you for continuing to put time and effort into this!
Sean
Routing Preference (Cyan)
Does not highlight in new WME…
I had a segment cloned when deleting a junction node. This happens after 20-30 edits in an editing session
Dave
Just checking to make sure you posted this in the channel you intended. It doesn’t look like a Color Highlights issue at first glance.
Have you considered expanding the speed limits section?
ie Highlight roads with a 20mph limit?
Jon
Hi!
I use the ‘U-turns’ highlight to check when they are set/unset on the mapraids in India, where, by default U-turns should be on, except on highways.
But it does not seem to work for streets, just for highways? Is that correct?
Anyway, please keep it!
Thanks,
Would it be possible to have an option to show even parking lot roads which are unnamed?
This would be useful in parking lots which are partially named and partially unnamed.
With the release of the “unpaved” attribute, it would be great to have an option to show streets with it.
Thanks,
Under the “Highlight a Road Type” selection, one of the choices is “Unpaved”. I’ve been using it and it works fine.
Thanks for all your efforts with this script – it is really great!
Recently I’ve been running into a recurring issue that seems to be coming from Color Highlights ![]()
VM21548:751 Uncaught TypeError: Cannot read property 'attributes' of undefined
at highlightBadNodes (eval at <anonymous> (:2:398), <anonymous>:751:28)
https://drive.google.com/file/d/0B7tnwIeX4x20RzRMQUM4OEs3T1U/view?usp=sharing
I’m not able to recreate it on demand, but it does seem to occur pretty regularly on some roads. In this instance, it occurred when I deleted an unneeded node, creating this segment:
https://www.waze.com/editor/?env=row&lon=73.38296&lat=25.59934&zoom=5&segments=334088313
The error repeats until I de-select the segment or scroll it out of the active window. It generally does not reappear when I re-select that same segment. I am running ver 2.22 of Color Highlights and the current version of Chrome on Windows 10.
Hi.
The option for “Headlights required” is near to be implemented? Yes?
Thanks. A lot.
I was about to raise an objection that the problem with that is that I’m already using that drop-down to highlight Parking Lot Roads. However, PLRs in unhighlighted form look different enough now (and are colored differently from Private Roads), so they’re pretty visible without extra coloring. So, glad to know that the option is there in the drop-down. I’ve set it now, and it does a great job of showing which ones are “unpaved.”
With Color Highlights enabled in beta WME (it works fine in production WME), entering Street View just gives a white screen for the street view and clicking the X in the street view window doesn’t close SV. My log is full of this error:
Uncaught TypeError: Cannot read property ‘length’ of undefined
at initialize.highlightSegments (eval at <anonymous> (:2:398), <anonymous>:168:54)
at initialize.triggerEvent (https://beta.waze.com/assets-editor/js/vendor-d87b4056f92296faad78.js:101:6363)
at initialize.moveTo (https://beta.waze.com/assets-editor/js/vendor-d87b4056f92296faad78.js:105:31078)
at initialize.setCenter (https://beta.waze.com/assets-editor/js/vendor-d87b4056f92296faad78.js:105:27363)
at initialize.updateSize (https://beta.waze.com/assets-editor/js/vendor-d87b4056f92296faad78.js:105:25413)
at initialize.resize (https://beta.waze.com/assets-editor/js/app-2ea221dd01ab8f25574b.js:12:31703)
at r (https://beta.waze.com/assets-editor/js/vendor-d87b4056f92296faad78.js:16:15568)
at dispatch (https://beta.waze.com/assets-editor/js/vendor-d87b4056f92296faad78.js:27:803)
at p.handle (https://beta.waze.com/assets-editor/js/vendor-d87b4056f92296faad78.js:26:30905)
As it looks like there is a problem with the WME Colour Highlights App since short time.
It doesn’t highlight anymore anything.
Best Regards
LenaMax07
P.S. A great thank you for that fantastic tool!