Description:
This script highlights house numbers which have not yet been “nudged” to aid in quick
diagnosis of routing issues related to the address in question. The highlight
appears as a colored background where a house number is entered. This background
is normally white but will be an orange-ish color for house numbers that have
never been edited.
Nudge All Feature
This feature will slightly move all never-been-edited house numbers in the house number editing window. Nudging is restricted to rank 3+ editors and is performed by pressing Ctrl+Shift+H with the house number editing window open. As was previously discussed in this thread, this feature has little potential for abuse as 1 point is earned per segment edited, not per house number edited. Please edit with care and do not abuse this feature. Also, don’t forget to trigger a tile update by making another edit in the area.
Love the script. Have been using it like a mad-man.
I would like to see an option where all the “forced” HNs can be removed at the same time. I have found the import error(s) that caused the original force can usually be rectified once they are removed. This would be great for L1s and L2s who can’t correct them and need to delete them manually.
Why would you delete them if they are valid, but something causes Waze to push the “force”?
I’ve encountered a number of forced HNs that the “force” dropped off once they were bumped.
Even as an L1 I was able to adjust forced HNs as long as the save did not require them to still be forced.
I had many instances where I would move the forced HN and then try to save it and it would error out, even if it was a valid HN. However, I have noticed that most forced HNs are caused by incorrect numbering or duplication from improperly placed HNs on other streets and usually required correction. Trust me, I don’t want to delete and redo HNs unless it is necessary.
Thank you for the suggestions. The “nudge all” idea was brought up before and would be easy to implement but there was some concern about the potential for abuse (mass editing of numbers without confirming they are in fact correct).
While a button to nudge all visible HNs would be nice, I think it would make for sloppy editing. I don’t see many HNs that don’t require at least a little repositioning to align them with the building structure.
I don’t see a big temptation for mass editing with this tool, simply because bumping one address, or 50 on the same segment still results in only one editing point.
It’s really one of the things I find distasteful about HNs.
I can drive to a location, walk 5 miles logging house numbers through HN Helper, then input them into WME, and it might only be worth 5 points.
The position of the number itself does not matter.
Waze will only route to the stop point on the main road. The HN “pin” can be anywhere from the road to the edge of the light area (it CAN be beyond that, but requires forcing, and still won’t route to that point).
You don’t get additional points for more than one HN move
The HN location will be the same as where the import placed it, so it would be the same as Google
The stop point will now be on the named street and not on some random alley or street behind the address, which is the cause of so much bad routing to addresses.
I would argue that despite being possibly misaligned by a bit, but for so many addresses which USPS/Google has located behind closer to an alley or other roadway, just a small nudge will fix those instantly.
Not with House Numbers. Once you nudge a Waze HN any distance at all, the stop point will always be the attached road. If you get routed elsewhere, then the search result you used in the app was not a Waze HN.
True, but in rural settings, HNs can be off by as much as 1/4 mile. Not much help when waze says you’re here and there isn’t a house in sight. I guess it’s my perfectionism that has me putting the stop point as close to the driveway or house front as possible.
Oh no… that is a completely valid point.
I think Alan’s issue is that it could be extremely useful in metropolitan areas where there might be 50+ HNs on a street… and in your case, it’s not going to make things any worse. Since the Waze imported HNs are generally where the Google pins are, the only change that a bump would make is you might get routed TO the wrong driveway, rather than UP the wrong driveway.
Either way, you’re going to get a UR and make the correction.
Oh yeah, I get this too. I’m surrounded by rural in my home area. For a lot of rural, where long driveways are the norm, and often shared driveways, HNs shouldn’t be used at all anyway because they leave you at the street in the dark on a driveway with 5 houses located “somewhere” down the lane…
This functionality certainly has the ability to be abused, I agree. However, abuse is usually performed because of the payback in edits and points, which leads to level increase and ability to more widely edit objects locked at higher levels. Because of where the HN tool even becomes active in the HN interface, you are locked to a single selected group of same-named segments already, and a subset of what is actually loaded in the editor at the moment, too. You can maybe update 8 normal city-block length segments, or possibly 10-15 smaller segments. Even more depending on the segment sizes. However, an abusers time would be much better spent just updating some other aspect of the segments in the main interface. It’s quite a waste of time to the general abuser to take the time to enter the HN interface and then mass nudge, save, close, select a different street, etc. etc.
With the HN tool, being a coded extension without source code available, it could be set to allow a “mass nudge” for editors at level 3 and higher or something like that.
