Feel free to call me lazy, but speaking as a Waze user (not as an editor), I like for Waze to know exactly where I am. I don't want to have to find my way to a defined road before I start receiving directions. It is very annoying when Waze thinks that I am on a nearby road and tells me to make turns that don't exist rather than telling me how to get to that road which is what I really want to know. But the icon snaps to the nearby road (which might not even be where I can see it) or overpass rather than showing me where I really am. I have been in many parking lots where I would have appreciated directions on the best way to escape.

I would like to see Waze with enough detail to provide walking directions, especially on places like college campuses. (There are plenty of students who would be willing to manage a small area.)

These details are useful to many people who aren't in the category of commuters trying to avoid traffic jams. The real obstacle is the routing engine.

Speaking as an editor, I did delete a parking lot road that someone created through a parking garage. Waze cannot get a driver out of a building.

These look to be alleys, they should be set to Parking Lot Roads per the Wiki:
http://www.waze.com/wiki/index.php/Best ... g_Lot_Road

The general long approved rule on alleys is draw them in if they provide access to garages, parking, or if addresses are actually in the alleys. If they are just there for garbage trucks to pick up trash, it is safe to leave them out.

vickimachado wrote:I would label the unnamed roads "private road" and leave them there. Individual private driveways don't get mapped, but back "alleys" like these are part of navigation. My opinion.

Agreed. I map these type of roads since people use them as shortcuts or to get around traffic. This way if they use they, they can see on the map where they are.

I just leave them unnamed but set them as service roads rather than private roads.

vickimachado wrote:Yes, they're important, though I see now they should be "parking lot roads" -- I had always selected "private" because in our area you will often see a "private road" sign.

"Service roads" had a separate definition in the Wiki, where I now see they are being phased out:

[/i]

Yep, forgot about the phasing out of service roads.

Sometimes address are on alleys, in my area. Your solution is not universal.

I would label the unnamed roads "private road" and leave them there. Individual private driveways don't get mapped, but back "alleys" like these are part of navigation. My opinion.

Thanks, shawndoc -- I stand corrected! (Resolves to brush up on the Wiki. )

Yes, they're important, though I see now they should be "parking lot roads" -- I had always selected "private" because in our area you will often see a "private road" sign.

"Service roads" had a separate definition in the Wiki, where I now see they are being phased out:

http://www.waze.com/wiki/?title=Road_Ty ... rvice_Road

Also often known as a frontage road.

A smaller street found running alongside a limited access highway or other primary street.
Service roads allow local traffic to enter and exit driveways, parking lots, and intersecting streets without congesting thoroughfare traffic.
(NOTE: Service Roads should NOT be confused with what is often called a "service alley". Service Roads will not prevent routing.)
March, 2013 - it was agreed at the second U.S. Waze Conference that the "Service Road" classification would be phased out and existing Service Roads would be automatically converted to Street type.