Query: not using "next named street" in parking lots?

If you think you've found a bug on the website which isn't specifically an App or Map Editor problem, or have a request for new or modified feature of the Community, Forums, or Waze website, use this forum.

Moderator: Unholy

Query: not using "next named street" in parking lots?

Postby AlanOfTheBerg » Fri Oct 26, 2012 6:07 pm

I'd like to see what the community thinks about requesting that Waze not announce the next named street when navigating through parking lots? I've noticed myself and have fielded many URs where drivers get the "turn left at <road name>", "turn right at <road name" when those turns are just within the parking lot.

I would suggest this criteria for "do not announce street name" if:
1) The current/previous segment is a parking lot segment
and 2) The next segment is a parking lot segment

#1 is to allow the situation where some parking lots into large malls are sometimes named and therefore, when entering the parking lot from a street, ramp, highway, etc, that name will be announced. But when exiting the parking lot, this name will not be announced because the current segment is likely a parking lot segment. (If the lot is properly designed with all parking lot road types.)

Whatcha think?
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 9.3.2 | Waze v4.7.0.1
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23441
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1080 times
Been thanked: 4556 times

Re: Query: not using "next named street" in parking lots?

Postby CBenson » Fri Oct 26, 2012 7:28 pm

My initial thought is that that there are some fairly extensive parking lots (particularly in the "towne center" type shopping malls around here) with internal streets that are named where the directions should use the name on the sign.

However, I guess the question here becomes whether named street in a large shopping development are really "parking lot" roads.

My first thought was the lot here which was entirely parking lot segments but has internal street names. However, I see that editors have already changed most of the named streets to "street type." So your proposal should now work fine here.

My second thought was the lot here which again has internal street names (and is admittedly over mapped). But again here the named streets primarily use the "private street" type. So again your proposal should work.

So I guess I'm wondering whether we shouldn't propose to waze the criteria "do not not announce the street name if the next segment is a parking lot segment." And then, if waze adopts the proposal, promulgate an editing guideline that if a street actually has a name it should not be a "parking lot" road, but rather should be a regular street or a private road, depending on whether it should be use for through routing or not.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.3.0.1
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10075
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1004 times
Been thanked: 2234 times

Re: Query: not using "next named street" in parking lots?

Postby CBenson » Fri Oct 26, 2012 7:42 pm

A second thought is that I kind of like the instructions in the parking lot as they usually let me know what exit waze is heading to even though the instruction don't really make sense. Thus, what I thought might be nice is that if the next segment is an unnamed parking lot segment and the name being used is from the next named segment on the route (not a name from a prior segment when the route ends in the parking lot) then the instruction might be "turn right towards Jennifer Rd." rather than "tun right at Jennifer Rd." A bunch of turn instructions "toward" the road that waze is taking you towards might not be too confusing and would give you some idea where the instructions are taking you. Of course if you are inside a named ring road, none of this helps.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.3.0.1
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10075
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1004 times
Been thanked: 2234 times

Re: Query: not using "next named street" in parking lots?

Postby AlanOfTheBerg » Fri Oct 26, 2012 8:22 pm

CBenson wrote:A second thought is that I kind of like the instructions in the parking lot as they usually let me know what exit waze is heading to even though the instruction don't really make sense.

Your proposal is also something I've considered and could support as well. "turn right to" or "turn right towards" are both better language than the current "turn right at" instructions.

My proposal could also be amended, but would require good parking lot creation discipline, to deal with named lot roads, as I've seen those too. How about:

1) The current/previous segment is a parking lot segment
and 2) The next segment is a parking lot segment
and 3) The next segment is unnamed
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 9.3.2 | Waze v4.7.0.1
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23441
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1080 times
Been thanked: 4556 times

Re: Query: not using "next named street" in parking lots?

Postby CBenson » Fri Oct 26, 2012 8:41 pm

AlanOfTheBerg wrote:My proposal could also be amended, but would require good parking lot creation discipline, to deal with named lot roads, as I've seen those too. How about:

1) The current/previous segment is a parking lot segment
and 2) The next segment is a parking lot segment
and 3) The next segment is unnamed

Ok, but if you have requirement 3), why do you need requirement 1)?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.3.0.1
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10075
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1004 times
Been thanked: 2234 times

Re: Query: not using "next named street" in parking lots?

Postby Daknife » Fri Oct 26, 2012 9:42 pm

Hmm and here I was thinking about making up names for every lane and maybe every parking stall for the local Mall. :lol:

Actually I like the Idea Alan, perhaps it might even reduce the inclination of some editors to pave every lane of a Mall because it didn't tell them to turn at the third lane in order to park closest to the food court.
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: 1683
Joined: Sat Dec 24, 2011 11:03 pm
Location: Riverdale, Utah
Has thanked: 456 times
Been thanked: 227 times

Re: Query: not using "next named street" in parking lots?

Postby AlanOfTheBerg » Fri Oct 26, 2012 10:22 pm

CBenson wrote:
AlanOfTheBerg wrote:1) The current/previous segment is a parking lot segment
and 2) The next segment is a parking lot segment
and 3) The next segment is unnamed

Ok, but if you have requirement 3), why do you need requirement 1)?

Ummm...
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 9.3.2 | Waze v4.7.0.1
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23441
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1080 times
Been thanked: 4556 times

Re: Query: not using "next named street" in parking lots?

Postby Scruffy151 » Sat Oct 27, 2012 8:08 am

I think using "to" or "towards" instead of "at" would be much simpler to implement and work as well as this proposal.

No special conditions are needed, those words work as well on complex ramps as they do in parking lots.
Scruffy151
Area Manager
Area Manager
 
Posts: 253
Joined: Sun Nov 13, 2011 3:03 am
Location: Vicksburg, MS
Has thanked: 3 times
Been thanked: 27 times

Re: Query: not using "next named street" in parking lots?

Postby weeezer14 » Sun Oct 28, 2012 7:56 pm

My over-all suggestion for all cases:

1.) Next segment is named and the first word is NOT "to" - use "at"
2.) Next segment is named and the first work IS "to" - use "to"
3.) Next segment is un-named - use "to"

Case one is for most basic intersections.

Case two is mainly for ramps. I have a ramp signed in real life with a "to I-40" sign. This ramp leads to the last bit of another highway (which is not mentioned on any signs at that point) that splits to join each direction of I-40. I bugs me because you are in no way turing "at" I-40 and I use that ramp almost every time I leave my home.

Case 3 covers the parking lot situation as well as things like at-grade connectors where you are in effect turning BEFORE you reach the road and not AT it.

It may be the case where only the US is using "to" in ramp names, but these rules should then still apply to other locales I think.
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
Image
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator
weeezer14
 
Posts: 3761
Joined: Sun Apr 11, 2010 3:27 pm
Location: Knoxville, TN, USA
Has thanked: 46 times
Been thanked: 315 times

Re: Query: not using "next named street" in parking lots?

Postby mssusa » Sun Oct 28, 2012 8:25 pm

This is also important where many new streets are not named yet, not just for parking lots. I have many newer parts of the city where all roads have no names. Many other smaller streets have no names (because they have no postal addresses) and going through a series of unnamed roads hearing incorrect instructions is annoying. I believe using "towards" is much better as a first step in addressing this problem.

Sent from my GT-I9100 using Tapatalk 2
mssusa
Area Manager
Area Manager
 
Posts: 306
Joined: Wed Jul 27, 2011 7:27 am
Location: Riyadh, Saudi Arabia
Has thanked: 10 times
Been thanked: 2 times

Next

Return to Website & Community Issues and Requests

Who is online

Users browsing this forum: No registered users