I just have to say, be very careful deleting all HN’s. Whether manually or with a script. Be sure you have a record or the GIS information easily available to re-add those numbers if necessary.
If you’ll enable your numpad the 1-9 keys will allow you to skip by a specific amount. For example, if the increment is 4 press ‘8’, rather than ‘h’, to enter the house number immediately before the value that needs to be skipped. When you place that house number on the map the value in the ‘Next #’ field will be incremented by 8.
I usually see the need for skip when I’m adding a long sequence using h>click>h>chick>h>click rather than break the rhythm I’ll just drop the unused house number into the middle of the road. When I reach the end of the sequence, I’ll go back to it and, with two clicks, it’s selected and deleted.
I like the numpad sequence change. I’ve been using your method of leaving unused HN’s in the middle of the road. I’ll try the numpad method next time I get a chance.
OK. I tried the number pad method and believe I see what you were describing. To skip ahead several numbers in sequence you will still need to add the next in the previous sequence that was already in the queue. Then go back and clean it up as a secondary step.
The number key shortcuts are (once again) being overridden by other scripts; the regular keyboard number keys are either trying to edit a roundabout (Toolbox) or changing the zoom level (WME FU, possibly?), and the number-pad keys (even numbers only) are scrolling the map (Toolbox).
Thanks for the awesome script! I took a look into the code, but I am too unfamiliar with javascript to dare try something myself.
It would be great if a letter could be appended and iterates over the alphabet. Here in the Netherlands we also have HN like 26A or 40B.
And while you’re busy, also additions like 74-3 and 23-10 are allowed here.
Hypothetically, when given an address of 26X and an increment of 1 should the generated sequence be 26X, 26Y, 26Z, 27A, 27B, …?
What about the second form where we have two numbers separated by a dash, should the script only increment the second number?
Sorry for the late reply, somehow the forum didn’t give me an e-mail notification. When the ‘26X’ series is used, I have never seen it increase into something like 26AA. So I would say your proposal to increase from 26Z to 27A is perfectly fine.
In the second form, only the second number should increase, and that can easily go into three digits and shouldn’t switch from e.g. 10-999 to 11-1, but just keep increasing, so 10-1000.
Hope that covers your question?
Sorry for the late reply, somehow the forum didn’t send me an e-mail notification. When the ‘26X’ series is used, I have never seen it increase into something like 26AA. So I would say your proposal to increase from 26Z to 27A is perfectly fine.
In the second form, only the second number should increase, and that can easily go into three digits and shouldn’t switch from e.g. 10-999 to 11-1, but just keep increasing, so 10-1000.
Hope that covers your question?
This might be a bug, but my knowledge is limited to try and investigate if it’s this script or something else so I’ll share with you guys.
After exiting house number mode and continuing to edit the map, the save button works ok but the Ctrl+S keyboard shortcut greys out the WME and freezes.
Change count on the save button remains visible but if I reload the tab, my changes have actually been saved.
This is a known bug that I helped document and report. It even happens in Incognito with no scripts enabled. It tries to save the webpage. It is very frustrating.
It also happens if you enter HN mode, add/edit or do nothing with HNs, exit HN mode and then make any other edit and use the Ctrl+S keyboard shortcut.
It’s been around since the non-existent streetid bug. I’m not sure it’s well known and it isn’t a major issue, especially if you don’t use keyboard shortcuts, so I’m not holding my breath.