Would it be possible to have a one-key update to a selected street to perform a list of abbreviations? I’d be happy to work with you to write the regexp, but undocumented JavaScript APIs aren’t really my cup of tea, so I’m having trouble figuring out how to write my own extension to do this.
Just wanted to say thanks. Today I found that the city of Eastvale, CA, had about 1/3 of the roads named with the wrong city, and another 1/3 or so with no city selected at all. (I don’t think Eastvale was an official city at the time of the basemap import) This tool has been a lifesaver when it comes to correcting the roads and getting them to match the official city limits.
Would it be possible to modify the script such that the STATE is editable from the “Properties” menu? I thought this would be an easy way to quickly track down and eliminate THIS PROBLEM (incorrect state names on minor unnamed private roads), but I have to zoom in so far to pick the private roads it’s taking forever and I’m pretty sure I’m missing some. If I could create a temporary large landmark, select all in it, and change all states to the correct state, this would greatly speed up the task.
For what it’s worth, I’m not just trying for quick points here. There are lots of these mis-categorized roads, but they are miles and miles apart. I’ve yet to change more than a dozen or so at a time.
Yes it is quite easy to do but,
is it not better to have a drop down box to select one of the available existing state in order to not create wrong state names and so ?
I think this might be applicable also for CityNames.
It’s quite easy to create a new city or state through the standard editor
Mostly. But states and countries are attached to cities. So first off, I would say ‘there should never be a ‘state’ or ‘country’ dropdown in segment editing’.
Ideally what I’d like ‘City’ edit to do is to get cityIDs in view, translate them to names (because a cityID has an associated country and possibly state in the U.S.), and that’s it. States and countries shouldn’t be ‘selectable’ from there, because cities carry the backend data.
The tool should not be able to create new cities.
EDIT: If you would like to see a good routine to translate a cityID to a comma separated series of names (based on what’s in view), please see the highlighter script - specifically, http://waze.cryosphere.co.uk/scripts/wme-highlights.html. This work has basically already been done.
It’s a good thought, but unfortunately, it wouldn’t work. I’ll explain why…
You can’t see ‘all roads’ until you’re zoomed into zoom level 4, as you know. A landmark bigger than your current view (which is 2048x2048) just wouldn’t have the scope to select segments outside the current view that you have.
The biggest view you can get that will select all segments is about 9 square miles. Here’s how to do that, jwk:
The problem is that to fix this properly, you’d need to be able to 'select all streets with state X (which you can do), and change all CityIDs to Y (which you cannot - yet - when that cityID is something involving a null - in this case, ‘No city, Louisiana’.) The WME segment editor itself will let you change a city and state in this batch way, but you’d have to wipe all your street names in the process because it demands a street.
If gdu implements the city select I talked about in my previous post, I think you could do it.
The script already translate all cities in a list with the “autocomplete” feature.
Put it in a select should not be so difficult.
Unless it doesn’t work on your countries?
Take a look at the code you will see how to get the list in a clean array in one line of code…
As my country does not have states, I didn’t check the consequences of doing such action for now
Right…the issue is that what jwk wants to do is to set a cityID to something with a name of “”, which can’t autocomplete. Specifically, 99999xx, which is what Waze assigns in the U.S. to ‘No city, STATE’. Additionally, there’s a bogus cityID that comes up in autocomplete with an ID of 1000000XX, which should never be used. It’s…well, let’s just say it took a lot of work to get all this right. Again, I suggest checking out the highlighter script. There are comments inside that explain. I’ll PM you the code, and the full context is in the script.
I took a drive to south Mississippi back in October, which is where I first came across the (apparently well known) wrong-state issue. I’ve been working on trying to squash all the wrong state roads in the area where I drove before I lose the ability to edit there in a few weeks. It’s horrendously slow going. I just started using this script so it’s sped up, but still I’m quite sure I’m missing lots of roads as I pan around at zoom level 4. All the roads I’m interested in are outside city limits, so that doesn’t apply (anything that has a City name attached to it also has the correct state).
My current process is: Grab a Segment List at Zoom 4. The only visible column is the State. Highlight everything that shows up “Louisiana”, change to “Mississippi” (city is always “Null” for these roads), Apply, and Save. Pan to next spot and repeat.
Incidentally, I already realized that even if you do add the ability to edit states (without changing city or street names), I can’t do what I originally proposed. Because it really doesn’t “select all inside landmark”. It seems to grab random streets in and outside the view area, but definitely not “all”.
Is there anyway to select all “unknown” direction segments using this tool?
I’m working in a lot of area’s that are still basemapped. A quick way to select all the unknown directions and set them to two way would be a god send!
It’s a mix. Typically what I see with this small towns are named streets with unknown direction. A lot of them have extra nodes that need to be removed and it makes it hard to manually select them without having to zoom way in.
Another issue with these basemapped towns is having a lot of one-way’s that should be two way (like dead end roads or cul-da-sac’s etc). Of course the other issue is having the wrong State on some segments, I’m working a town in the middle of MO right now that has IL segments in it uhg
To answer your question - yes, you can select all the segments with Unknown direction using the NbWays column.
The reason for my question was that I’ve seen another US editor say (in a discussion about points-per-week and the Extended Tools add-on) that they didn’t use an addon, but that most of their editing consisted of selecting loads of segments using the (old) “Select entire street” button and then changing them to be Two-way. They seemed to be under the impression that this was a) adding value to the map (which it doesn’t), and b) was in some way morally ok, because they weren’t using an add-on to do it.
Whoa, slow down there. 1st, I’m talking about an area I have first hand knowledge of, there are NO one way streets in these towns. 2nd, we’re talking about basemapped areas, a good number of the streets are in the wrong locations, etc, because this data was imported. These small towns take me forever to clean up.
If the street is set to a one way, even though it’s two way, won’t that generate an auto pin? If unknown waze would eventually learn, but if I have the knowledge why not put it on the map now and make wazing easier for the clients?
Which advises, in part: “…It will change the directionality of a road, enable turns, and reportedly it will change the geometry or layout of a road.
This can cause map errors, especially in areas where there are few wazers. One wazer who always travels one way down a road may change a correctly recorded two-way road into one-way.”
and I’m currently talking about small towns, where there are few wazers.
Edit : side note, I’m not one of those on a “points quest”. I want waze to work correctly when I go driving out to these small towns and rual area’s just as well as it works in the big cities. In a way I feel fortunate, because I have been granted my AM area that covers a big city and many rual and small towns. The whole reason I became a map editor was to improve the user experience around my area.
Please see my post above, according to the page I linked in the wiki, Two-Way roads can be changed to one way, if wazers always drive down the same way. (possible in these small towns)
As far as routing, the engine’s choosing is dependent on more factors, but I can tell you from experience of using the Livemap to test routing I’ve seen the engine prefer an unknown direction “street” before (this was in a downtown area and the routing was taking people down an Alley that was basemapped incorrectly as a street. It’s since been corrected. But there are many factors like origin point, destination point, and all segments between.
Then you shouldn’t say the Wiki says so, cause it probably doesn’t.
No. I’ve had a street go from two-way to one-way, simply because I was the only person driving down it, and I always drove in the same direction.
Maybe. But if you have local knowledge and know all the streets are two-way, then it’s better to set them all to two-way, as that is what they should be. As long as you then take the time to add all the other data - road names, turn restrictions, etc.
uhg