Correct!
send from my SGS4, using Tapatalk
Since âstaffâ caused the problem, it sure seems to me like it would be simple and logical for âstaffâ to do a âone timeâ scan of the database and FIX the problem.
Of course, there is always a chance they will mess things up even worse. 
If I had $1 for every time I heard that on hereâŚ
There are SO many fixes that could be done this way, but it seems low on the priority list (if it is even on the list).
What Iâm seeing is unnamed segments here and there. Itâs not like thereâs ever a lot of them. But the procedure to get rid of that alt name is to give the unnamed segment a name. Then delete the alt name, then remove the dummy name. Itâs a bit of a pain.
Why is the alt name field inaccessible when the main name field is empty?
Because those that are designing WME donât have to use it every day. IF they spent hundreds of hours USING it, like some Waze Editors do, they would NOT have it as messed up as it is.
1 Like
Itâs also a pain the other way: setting the alt name on a no name segment to keep detours under control.
Enhancement request: for UR PMs, please include the &mapUpdateRequest= In the permalink.
Whenever I send a UR permalink PM, I copy the UR id from the URO+ popup.
Unless I forget.
Thanks for considering it
+1
Not sure if your doing it already, but please ensure PM links from URS contain a PL which also activates the UR layer.
Sent using Tapatalk for Android 4.4.2
Still really hoping for some way to mass select and mass edit alternate names.
In South Carolina we have an epidemic of alternate road names of âState Rd S-XX-XXXâ which according to our state manager should be changed to simply S-XX-XXX.
Thereâs a handy validator script to find offending segments, but itâs still extremely slow going.
If you select multiple segments with the same primary name and city, it will âmergeâ all the alternates of all selected segments, so you donât know which ones have which alternate names. Especially in cases where only one or two segments may have two S-XX-XXX numbers to apply, it gets really finicky. You have to individually select them segment by segment, one at a time, deselecting before you select the next segment, to confirm that they do indeed all have both S-numbers on them.
If you attempt a mass edit on one S number you may accidentally apply one or both S numbers to segments that didnât originally have it, because you could have some of those segments selected and not know it. For example, select 5 segments that have one S-number on them, then 2 more that have that S-number and a different S-number. If you were to correct that second S-number, it would apply to all 7 segments and not just the 2. If you were to correct the first S-number, Iâm not sure but you run the risk of applying the second uncorrected S-number to all 7 segments as well.
If say the road goes through an intersection and the first S-number is no longer on segments but the second S-number is, then you wind up selecting several segments more, THINKING that they have both S-numbers still on it, but you canât really tell anymore! If it werenât for the validator script which shows you that it has at least ONE S-number on it, you could select any segment at all and it would say that it has all the S-numbers of all segments youâve selected previously!
The validator script does help identify any segments that never had an S-number at all, but in cases where numbers overlap or one number is on one segment but a different number is on the adjoining segment (like at intersections), itâs no help at all. Youâve literally got to select them one by one to be sure youâre not misaligning data.
On top of that, if the primary name and city name are not the same (especially common when crossing city or CDP lines and the city name changes), you canât change the alternate name then either. Even if you wanted to just mass delete alternate names and start over, possibly from a reference map, this still becomes annoying quick. And you still have to worry about adding a S-number thatâs the first one on several segments but the second one on a coupleâŚit might add that other overlapping S-number to all your currently selected segments! Augh!
All in all it would be really helpful if the toolbox was able to address alternate names better. Being able to select all segments by alternate name, regardless of any other properties on the segments, and then edit that alternate name and be able to apply that edit to all the segments at once without touching any other properties on the segments which may have varied primary names, primary cities, and alternate cities (including on the alternate name youâre changing), would be epic. And definitely contribute to peace of mind in making sure no slipups happen!
I know this is one specific circumstance where it would help but I canât imagine that others wouldnât find it just as useful for other similar situations.
~
While weâre at it, I havenât started trying to do this yet as it hasnât been seriously needed in my area, but mass editing city (without affecting other attributes like names and alternate names) would be handy. Draw a landmark/shape and set all segments within that landmark as the same primary city and alternate city. Setting a secondary city using the tool would create an alternate name for every name that includes the primary city and include the secondary city instead. Does that make sense?
Itâs just, messing around with these alternate names/cities is SO annoying, so scripting to make it easier is almost required at this point to do any mass amounts of editing on them.
thortok â you can already set primary city for âall segments in polygonâ. You create the area place, then use âselect all in area placeâ, then use the properties editor.
That does not do the alternate city, of course.
I agree that there are moments when it would be really useful to use the âselect segmentâ tool and work with alternate name. The problem with alternate name is that there are an unlimited number of alternate names for any road. So before such a tool can be written, it has to be decided what it will do in the case that there are 2, 3, or 10 alternate names, if they are empty, if they are different names, if they are the same but with different city⌠thatâs the hard part, really.
How about âweâ agree on a âdummyâ name to use when we NEED to deliberately have a dummy alternate street name? We can also agree that the current blank alternates are to be removed.
You could give a choice whenever a blank is encountered.
- remove the blank alternate
- replace it with the dummy name.
Not sure how easy that would be to program but the use of such a tool should be much less painful than the current method of fixing those blankety blank alternates. 
why would you ever need a blank alternate name and city?
A very good question! I had the mistaken(?) guess that it might be necessary, in some obscure cases, to get proper turn/keep instructions. Aside from that remote possibility, I donât see any reason to keep them. I have never wanted nor needed them!
The basics of the alt name editing would start for me, with a button or shortcut to do the following actions on selected segments:
Check if Street name is similar in all selected segments ă Edit name ădelete alt name ăapply
If thatâs available to start with, it would save a lot of clicking-work
send from my SGS4, using Tapatalk
How to use this on Mac/Safari?
The best solution for Mac that I was able to come up with a couple of years ago was download the Firefox browser. Thatâs still working fine for me, but if someone can find a way of getting scripts and extension to work on Safari that would be nice.
That or use chrome on a Mac. That is what I do and seems to work fine.
Sent from my iPhone using Tapatalk
Ok, I see. The person does not want to use chrome or FF 
I have a problem with restrictions being highlighted as expired that donât start until later today. Normally, restrictions that are on-going or will happen in the future are highlighted yellow and ones that have passed are highlighted in red, but these arenât supposed to be active until 2 or 6 this afternoon and theyâre already highlighted in red. Also, the delete expired restrictions removes these restrictions erroneously.
Yes, indeed, thatâs not how it should be. Iâve logged in the bug (#164).