Not to mention that throttling has significantly impacted the “reward” for farming edits.
So it’s easy to protect if we need to, but given the inability to actually cheat/farm points with House Numbers, i don’t see why it needs to be protected. Would be cool to see this feature added.
The same could be said for a number of other tools that have been abused in the past.
I’ve been “throttled” after running the auto-lock routine on a fairly small area.
Most local editors who have been doing a lot of basemap cleanup have reported apparent throttling.
Regarding the coloring: do you have a suggestion for a color to use? You can use this tool to find an example: http://www.w3schools.com/tags/ref_colorpicker.asp.
With some input on the color I should be able to release a new version soon. It will have the highlights when zoomed further out and nudging abilities.
I’m good with the colors as they are, but I can see on some displays the orange might tend to “lose” the HNs.
I’d say a nice solid yellow would work well, maybe a bright orange.
Something that won’t get lost compared to white, but also won’t hide the numbers.
Let me know what the current color is and I’d be happy to.
[quote=“taco909”]
Not for this tool, no. You’re missing the main point that you can’t be throttled for making a change to 100 house numbers on a segment because it is only changing 1 segment and therefore 1 edit.
The current color is #FF9966. I was playing with a shade of blue, #8DE8FF, or maybe a lighter orange than what it is now, #FFC266.
To stay in the same color but lighter, #FFAD85 seems fine to me.
hello SAR85. you really made my day today! thanks for wonderful skript.
I would stand for having “delete all non-nudged house numbers”
for security reasons, it should be possible to restrict access to such button only to L4/L5/whatever level you say
let me explain why we despreadly need this.
the house numbers story is rather old. seeing your join date, you can’t be aware of the history.
first house numbers were added in old map editor called Cartouche. those were single housenumbers located on exact positions on segments (Cartouche was replaced by Papyrus a.k.a. WME in early 2012, so my memories are just pieces). If I remember correctly, the HN functionality was removed from Cartouche some months before decommisioning.
in WME for long time there was no possibility to set HNs. but after some time, developers added option to set house number range for segment. so user could define first and last HN values for both sides of particular segment. This was meant to extrapolate the rest from those bordering numbers.
this approach was complete fail, but many ranges were already set by fellow map editors. moreover, if someone splitted segment with HN range with junction node (e.g. connected other segment in the middle), the range was recalculated (by some magical logic only known by developers)
in March 2013 Waze launched current system for house numbers. they converted those old range-bordering HNs into “regular” new ones (represented now as non-nudged) and created complete mess.
just check this permalink
screenshot
how many wrongly possitioned duplicated HNs you see?
and the real pain in the ass? if there are set some HNs on street, Waze often ignores that for particular search there is not perfect match in Waze map (and googlemaps got the perfect match), Waze search extrapolate the position. if there are duplicated HNs set in Waze map, the search result is incorrect.
we definetly MUST get rid of non-nudged HNs.
with current version of script we are glad those are highlighted
with the “delete all” button it would be great
and with possibility to do that with lower zoom level perfect
please, if there are no technical difficulties, add the “delete” button
thank you for your effort.
PS I asked HQ (Ori) if they are able to delete those range-numbers from DB for our country. unfortunately the answer was “no”
Did a new version of WME break this script from working?
Not getting highlight for untouched addresses.
I’m encountering similar issues
Same here. Script not working.
(not the author) The new WME update changed some of the Javascript classes used for pulling the HN data, those will have to be updated when possible. I can’t find the new equivalent of one of them though (W.appPresenter.sidebar.editPanel.typeToEditorClass.segment.houseNumbersControl). typeToEditorClass is now TYPE_TO_EDITOR_CLASS but .segment has no .houseNumbersControl property.
Thanks for letting me know, everyone. I will look into it and get a fix out ASAP.
Sent from my HTC One using Tapatalk
A lot of what Waze has done recently in WME was to only instantiate some of the code when the relevant UI elements are active. Those classes may only exist while the HN editor is visible.
I checked this, the class doesn’t exist whether HNs are active or not. Don’t know if it was moved somewhere else or what happened. I’m probably wrong though, I usually am.
Looks like the script is broken since the recent updates. Any idea when an update will be released?
HN Tool has been updated! The fix should make highlighting work for now, although it is not quite as elegant as I would like. I will continue to look for a way around the issue.
Unfortunately for those who were looking forward to an auto-nudge feature, the WME update may make that impossible.
It looks like this is exactly what happened. Now the houseNumbersControl does not exist until the HN editing window is opened. When the HN editing window is closed, the control is destroyed. This alone would not create too many problems but what also changed is that the control gets created inside a closure and is never assigned to an accessible property as it was in earlier versions.