shawndoc wrote:

AlanOfTheBerg wrote:

shawndoc wrote:Just had new roads I was drawing in default to Mexico for the country. This was in Northern Fresno, CA. A good 5 hour drive from Mexico.

Look for the possible other segments assigned to Mexico nearby. This will influence the country available in the drop-down. Mexico comes first alphabetically, and just like the state drop-down, the default is the first alphabetically.

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.

Hmm. Okay, two things. If there is only one country in view, the highlighter script won't suffix the city list with the country. If there IS more than one country or state, you'll see something like this as the list:

Santa Ana, California, United States
Santa Ana, California, Mexico
Santa Ana, Nevada, United States
...

That is to say, implicitly, the highlighter script DOES search by country and state as well and will show them to you if there is more than one.

But the second thing is, another source of 'Mexico' can be the landmarks layer. Did you try something like this?

1. Start at zoom level 3 at that location with the landmarks layer on only.
2. Click a landmark. Then 'Edit'. You'll see that Mexico is in fact a dropdown, and there are other cities like 'sa', 's', and so on from badly filled in landmark cities in this area.
3. Zoom in, look at the roads layer. Mexico was still in the dropdown for me.

BUT...

Do the same thing above with only the roads layer on to start, and Mexico (and these other cities) were NOT in the dropdown.

...yes, alas, get.cities, which determines cities/states/countries in the dropdowns also checks the landmarks layer - but only if it's enabled. Additionally, the highlighter script does NOT check landmarks for location information because it doesn't know to check on that layer.

shawndoc wrote:Oh thanks. I didn't realize it picked up on alt cities. How do I tell which one is out of state when it shows the same city several times?

If you are only seeing something like:

Tustin
Santa Ana
Santa Ana
Los Angeles

...then you are using an old version of the script before that functionality was built in. Make sure you're on 1.5 or the newest beta. When an alt street has the selected city, it will be highlighted with a dashed line. When the primary street does, it'll have a solid line.

One of your Mexico culprits would be this, north of Fresno...

https://www.waze.com/editor/?zoom=5&lat ... FFTFTTTTFT (landmarks on, try clicking a segment and editing cities)...

https://www.waze.com/editor/?zoom=5&lat ... FFTFTTTTFT (landmarks off, and you'll note the country dropdown is different).

If you can't find segments up this way with 'Alabama' on them, maybe landmarks in the area do.

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.)

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.

PhantomSoul wrote:The yellow segments when a segment is selected mean those segments have a soft turn to the node of the selected segment they touch. The magenta ones show reverse connectivity (RevCons). Red segments, when another segment is selected show U-Turn segments (SelfCons). The last two need to be corrected when seen - the sidebar shows a hint as to what to do if you select a node with a RevCon or SelfCon. Soft turns also need to be corrected, but only if you know for sure which turns are or are not allowed at a given intersection. Further information on Soft Turns, Reverse Connections, and U-Turn Connections can be found in the wikis.

The red highlight segments come up when new roads are added without putting in a city name and street name or checking the corresponding boxes saying it doesn't have a city or name. Maybe there's a script error that put them there and maybe they'll disappear just the same? Freeway offramps are usually kept under level 5 locks to prevent vandalism, so that would be my guess. Anyone here know if something's going on?

I am sorry...the first link was wrong. It was supposed to be the same location as the second link, with all of the red segments selected. My question is why did this user add all of these red segments, directly on top of the existing ramps? Every red segment lays on top of a previously existing ramp. In this link, I moved some of the unnamed segment so it exposes the existing ramp below.
https://www.waze.com/editor/?lon=-74.30 ... s=71058138

jasonh300 wrote:

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.

Jayson,
It seems you are as awesome copying links as i am tonight. You sent me a link to Louisiana, but i think you meant to send me this link:https://www.waze.com/editor/?lon=-73.98 ... TTTTTTTTFT

If you haven't driven in NJ before...it is a very very very stupi....i mean special place. We like to screw up drivers from the other 49 states by prohibiting left turns on many major highways. While on Navesink Ave, left turns are prohibited at Miller St. but, Miller St is allowed to go across the highway which is a left turn. You can see the restriction signs for Navesink Ave in this street view.https://maps.google.com/maps?q=miller+s ... 73,,0,-2.6

I guess i could consolidate the two 1way segments into a 2way segment for miller, i was trying to keep it separated since there is a physical median.

It is a crazy looking intersection.

I haven't tried navigating with the client yet but the Live Map seems to route properly.

jasonh300 wrote: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.

As for the instructions, it should be left or right turns. I increased the right departure angle and made more of a curve on the end. the left turn instruction should come on the other side of Navesink Ave for each direction.

jasonh300 wrote: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.

Ok, so that would give a Right then Left turn... How about this? Would it make a difference in giving the left turn instruction sooner? I dont have clearance to correct the turn(straight) restrictions on what I changed on Miller St.
Here:
https://www.waze.com/editor/?zoom=10&la ... s=70759790

and here:
https://www.waze.com/editor/?zoom=10&la ... s=71089129

Anyone know why these red streets were put on top of existing roads? the user did this somewhere else on a GSP exit north of here before I think.

https://www.waze.com/editor/?lon=-74.20 ... TTTTTTTTFT

The user is GlnH
I dont see any posts in the forum by them.