Waze forum

shawndoc wrote:I tried to, but it was in a heavily built up area, and neither the highlight script nor the new Extended Tools have a way to highlight based on country. I clicked around for several minutes, but couldn't find any nearby segments with Mexico as the country.

It may have been removed already, but all it takes is one segment to make it to the tiles, and it'll continue to be an option on nearby segments. It has to be removed and stay that way across the whole area for a full cycle before it won't be an option.

Having done quite a bit of smudge hunting recently, I've found more oddball states and countries in California (specifically within 50 miles of L.A.) than anywhere else I've looked.

(For some reason, Gemany pops up in Louisiana once in a while also.)

Have you cleared out Portola Valley yet? I specifically ignored that one since it's such a huge project and I don't have much time to dedicate to it.

shawndoc wrote:Now that we have a version of Extended Tools for the new editor where the segment list works in Chrome, I'll probably start cleaning up more.

I tried that, but didn't really find it useful for smudge hunting outside of urban areas. It's come in handy finding a few oddball city names though.

shawndoc wrote:Just based on this discussion, and me trying to fix some of these (fixed a whole bunch of Alabama and "Other" state alt names), I noticed a lot of roads have the same name in the Alt field. So real name and Alt name are exactly the same (Except maybe the state field). Seems like a waste of database entries.

Kinda wish there was a script that automatically deleted alt names if the the street and city match the regular name.

How are you determining what state the alt name is assigned to?

In my smudge hunting, if I see a duplicate name in the alt field, I delete it.

tpmcguire wrote:What do you think about this? It wasnt the first time i saw it today, someone overlaid all of the GSP exit/entrance ramps with new unnamed segments.
Segments selected:
https://www.waze.com/editor/?lon=-73.98 ... s=31887662

Segements not selected, and showing in red:
https://www.waze.com/editor/?lon=-74.30 ... FTTTTTTTFT

I see a parking lot in red off the left which isn't my main concern right now.

I'm not seeing what you're describing here, so I assume someone fixed it.

However, what's your reasoning behind this mess?

Is there really some rule preventing traffic on Navesink from turning left onto Miller? But at the same time, traffic on Miller can make the jog to remain on Miller? The way it is here, the only instruction to traffic on both northbound and southbound miller when they hit Navesink is a "Keep Right". That's it.

Unless there's some really weird situation here, this is the wrong way to handle this intersection.

EDIT: Okay...I see your corrected link.

Looks like someone did some paving. Delete the red roads. They don't need to be there...it looks to me like everything else is correct in that link with the exception of the paving.

If you see any more of this, please report it to me or any other Champ and we'll contact the user in question.

Actually, leave all this alone for now...this is looking more like vandalism. I'm going to turn this over to the administrators.

I don't know why for some reason my Ctrl-C just doesn't want to work.

Okay...I get it...I should've known since it was in New Jersey.

You should play with the angles on that though so you'll get proper turning instructions. LIveMap is what shows that the instructions aren't correct. You are using the LiveMap Navigation Script, right? If not, search it in the forums and install it and you'll be able to see the actual turning instructions.

That would've only gotten a turn right. Check out what I did...you may need to zoom in close to see the actual turns.

Yeah, what you did will probably work even better and it looks less sloppy. However you may need to come straight into that junction to prevent a U-Turn (although at 8 meters, a U-Turn shouldn't happen there anyway).

It's not really going to give the instructions any earlier though. What you may need to do is name the connecting segments "Navesink Ave" to get the proper turn instructions, but since the updates come quickly, it's easy enough to test.

I unlocked those 6 segments, so fix up the other one and double check all those turn restrictions and see how it works.

If this doesn't work, I have another idea, but see what happens with this.

Type in a question. Then it'll give you a bunch of links to what it thinks you're asking. You can usually just ignore that and then click on the e-mail link at the bottom of the list. Then you can type in your info and submit it.

skbun wrote:

jasonh300 wrote:Have you cleared out Portola Valley yet? I specifically ignored that one since it's such a huge project and I don't have much time to dedicate to it.

I'm actually having a hard time finding more of these. Has there been a big cleanup done?

If the answer is no, if you can point me to areas where the smudge still exists, I can try a JS fix I've had in the works to fix these segments quickly. (Also, it may work for other no-city basemap state smudges as well. Toss one or two at me.)

The majority of it was automated I believe.