Incorrect street signs

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: krankyd, Unholy

Re: Incorrect street signs

Postby AndyPoms » Tue Aug 06, 2013 7:16 pm

You can always C) Report the incorrect signage to the Town/State DPW/DOT...
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5924
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 885 times

Re: Incorrect street signs

Postby AndyPoms » Wed Aug 07, 2013 11:43 am

Be careful with those "honorary" designations, most of the time they are not permanent (we have one intersection that changes name each March (for one of the St. Patrick's Day Parades).
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 5924
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 89 times
Been thanked: 885 times

Re: Incorrect street signs

Postby daknife » Wed Aug 07, 2013 2:26 am

Let alone we country managers having to fix every pot hole on every rural route. And my employer is starting to complain about the amount of time I've spent rebuilding a couple landslide damaged roads. :lol:

As to the OP, could it be that the city has designated that one stretch slightly differently for some specific reason? For example I've yet to find an official city map of SLC that identifies the block of 300 West between South Temple and 100 South as John Stockton Drive, or the one block of 100 S between 300 West and 400 West as Malone Drive. So named in honor of John Stockton and Karl Malone. Stockton drive and Malone Drive. I haven't put the names in as primary on the SLC maps and in SLC the grid number designators are almost always also listed, but the situation could be similar.
Image
AM in Utah; CM USA
Utah Forum: Utah Forum
Samsung Galaxy S4 running 4.4 KitKat on Sprint
daknife
Waze Mentor
Waze Mentor
 
Posts: 1612
Joined: Sat Dec 24, 2011 11:03 pm
Location: American Fork, Utah
Has thanked: 356 times
Been thanked: 188 times

Re: Incorrect street signs

Postby daknife » Thu Aug 08, 2013 7:43 am

Very True, the one I use as an example has held that name Since Stockton and Malone retired. Then there is the road up to the nearby Cabela's that was named Cabela's Drive in it's honor when the store opened. Now Adobe just finished a big new building built across the road and it suddenly became Adobe Way.
Image
AM in Utah; CM USA
Utah Forum: Utah Forum
Samsung Galaxy S4 running 4.4 KitKat on Sprint
daknife
Waze Mentor
Waze Mentor
 
Posts: 1612
Joined: Sat Dec 24, 2011 11:03 pm
Location: American Fork, Utah
Has thanked: 356 times
Been thanked: 188 times

Incorrect street signs

Postby dbwiddis » Tue Aug 06, 2013 5:45 pm

What do you do when users submit update requests because the waze directions (which match correct road names) conflict with incorrect street signage?

Two examples:
1. This intersection is on "S Martin L. King Blvd". So says every map I can access, including the county GIS. Every other street sign on that street says "Blvd." However, the sign at the intersection with Wall st. says "Martin L. King Ave". Should I (a) change a road segment to the "Ave" name so waze instructions match the sign? (Ugh), or (b) leave it as is and politely tell the user the sign is wrong? (What I just did, seeking confirmation.)

2. This intersection is on "N Rock Springs Dr." However, the (brand new) sign incorrectly says "W Rock Springs Dr." For this one, I just renamed the road "Rock Springs Dr." to avoid the issue entirely.

What would you do in these cases?
Image
AM Las Vegas, Nevada
dbwiddis
Beta tester
Beta tester
 
Posts: 114
Joined: Sat Jan 05, 2013 2:02 am
Location: Las Vegas, NV, USA
Has thanked: 39 times
Been thanked: 11 times

Re: Incorrect street signs

Postby huckd » Tue Aug 06, 2013 11:05 pm

shawndoc wrote:
What good is that going to do? I've reported the broken street light through Waze a half dozen times and its still broken.


Oh no. Is Waze's street light repair department falling down on the job again???
Image
Area Manager in SW Georgia, USA.
huckd
 
Posts: 71
Joined: Fri May 03, 2013 1:45 pm
Location: Albany, GA, USA
Has thanked: 39 times
Been thanked: 6 times

Re: Incorrect street signs

Postby jasonh300 » Tue Aug 06, 2013 6:02 pm

dbwiddis wrote:What do you do when users submit update requests because the waze directions (which match correct road names) conflict with incorrect street signage?

Two examples:
1. This intersection is on "S Martin L. King Blvd". So says every map I can access, including the county GIS. Every other street sign on that street says "Blvd." However, the sign at the intersection with Wall st. says "Martin L. King Ave". Should I (a) change a road segment to the "Ave" name so waze instructions match the sign? (Ugh), or (b) leave it as is and politely tell the user the sign is wrong? (What I just did, seeking confirmation.)

2. This intersection is on "N Rock Springs Dr." However, the (brand new) sign incorrectly says "W Rock Springs Dr." For this one, I just renamed the road "Rock Springs Dr." to avoid the issue entirely.

What would you do in these cases?


It is indeed a conundrum. I had this exact problem a couple of days ago. Someone reported that Lafitte St should be Lafitte Ave. I checked it out and in the blurry streetview image, sure enough, that's how it reads on the sign, at that particular intersection where the UR was left and the turn instruction was made. I checked every other sign for about 6 blocks in either direction, and not another one had Avenue on it.

So I changed that one block to Avenue. I don't really know if that was the right choice, but it will give correct TTS instructions. The street is one-way, so it shouldn't interfere with any other instructions where the signs are different. The streetview image is 5 years old, so if it's been like that for that long, it's unlikely to change anytime soon. For all practical purposes, Lafitte Street is called Lafitte Avenue in that one block (and being New Orleans, where streets are constructed, named, and given one-way/two-way direction without reason or rhyme, it may very well be intentional).
Image
New Orleans, Louisiana
Regional Coordinator, South-Central Region
Waze FAQ ... Best Map Editing Practice ... Waze chat on IRC.
jasonh300
Waze Global Champs
Waze Global Champs
 
Posts: 6868
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA USA
Has thanked: 239 times
Been thanked: 628 times

Re: Incorrect street signs

Postby jasonh300 » Tue Aug 06, 2013 7:47 pm

shawndoc wrote:What good is that going to do? I've reported the broken street light through Waze a half dozen times and its still broken.


:o
Image
New Orleans, Louisiana
Regional Coordinator, South-Central Region
Waze FAQ ... Best Map Editing Practice ... Waze chat on IRC.
jasonh300
Waze Global Champs
Waze Global Champs
 
Posts: 6868
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA USA
Has thanked: 239 times
Been thanked: 628 times

Re: Incorrect street signs

Postby jasonh300 » Tue Aug 06, 2013 11:36 pm

huckd wrote:Oh no. Is Waze's street light repair department falling down on the job again???


So many people sign on as Area Managers without realizing it's one of their many duties...
Image
New Orleans, Louisiana
Regional Coordinator, South-Central Region
Waze FAQ ... Best Map Editing Practice ... Waze chat on IRC.
jasonh300
Waze Global Champs
Waze Global Champs
 
Posts: 6868
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA USA
Has thanked: 239 times
Been thanked: 628 times

Re: Incorrect street signs

Postby PhantomSoul » Thu Aug 08, 2013 8:24 pm

The primary names of segments with addresses (house numbers) along them really need to reflect the name you would use if you were searching for one of those addresses, regardless of local signage, no?

I realize this could be confusing in terms of the banner display and TTS, but isn't that what short, way finder segments are for? I know it's more work and creates more junctions, but it also reflects nearby addresses more accurately while displaying/reading what you actually see on the sign if you need to turn at the intersection.
Image
Wazing the Garden State... one jughandle at a time.
AM: New York City; New Jersey
AT&T iPhone 5 / iOS 7.1 / Waze 3.7.8
PhantomSoul
Waze Mentor
Waze Mentor
 
Posts: 556
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 59 times
Been thanked: 77 times

Next

Return to Waze Map Editor

Who is online

Users browsing this forum: Google Feedfetcher, OllieUK, wkeverae