As a new wazer and getting into editing I noticed several "map problems" and new roads caused by entering/exiting parking lot or building structures.

Current work around is to add Parking POIs or add the parking lot roads as road type parking.

I believe this could be alleviated by simply not having Waze client record or "count" the GPS track within a set distance from Origin (time device first plugged in or new navigation started) and Destination (device turned off or navigation stopped)

I would recommend a distance of about 100 yards.

This should help cut down on the extra roads caused by normal leaving/arriving patterns.

It could even be utilized when the new pause feature is added to the client. Saving the headache of correcting map problems/roads for frequented gas stops.

8 out of 10 times I use Waze driving to and from work, a route I know very well so I don't need Waze to show me my position on the map.
What I instead would like is a "trip computer" kind of interface, showing me things like my current speed, current speed limit (if known), maybe a color code for traffic ahead on route (green, yellow, red), ETA, current road name (nice to have, not need to have - I know where I am), live updates of incidents (needs to update themselves automatically), textual navigation instructions like "turn right in XX meters" (again optional as I know this route), and a few large buttons for Reporting, Alternative Route Now! (will open map view), Menu.
Police traps and cameras should trigger a large popup window when approaching.
Other optional items on the trip computer screen: GPS signal strength, GPS time, heading, avg speed, distance driven, distance to dest, etc.
It would be cool if the colors of this screen (and even the fonts?) could be customized to match the car's dashboard lighting, or to work optimal for night use or to save battery usage (black background, green or red characters, dim light unless police/cam warning).

The Waze client, and also the "live map" on the web site, hides smaller roads as you zoom out. This is fine in cities where there are many roads. However, in rural areas, the small roads are simetimes the only roads, and if they are hidden then the map can appear completely blank.

I suggest changing to an algorithm that takes the amount of clutter into account. Something like "first disply the major highways; if the screen is not yet too cluttered then also display the minor highways; if the screen is not yet too cluttered then also display the major roads; if the screen is not yet too cluttered then also display the ordinary roads; if the screen is not yet too cluttered then also display the small roads, parking lot roads, private roads, 4x4 tracks, etc."

Create a new type of routing for joy rides. The name could be "Explore".
Waze will generate a route to the user discover his neighborhood and/or help improove waze with cookie munching.

Rationale: many people get in their cars, bikes or bicycles and go for a ride, just for the pleasure, to know more about the neighborhood, to see some countryside etc. Currently no GPS device or app has a way to helping the users in this. This would be a differentiating feature for Waze and also would help improve Waze database with driving data.

More details about the route:
-If the area has unconfirmed roads Waze will prioritize that (cookie munching). If the area map is complete, Waze can prioritize landmarks or other POIs to make the trip interesting.
- User can define desired time limit or distance limit.
- User can choose to prioritize Highways, avenues or streets. Other normal routing options like avoid toll roads, will also apply.
- The route will end at the start point.

I take the same route from work to home everyday because it's the fastest way to beat the rush hour traffic flow. I always route to "home".

Often, I am in the same general area as my workplace and trying to get home and waze puts me on the same roads that I would take take on my work -> home commute. But just as often, this isn't actually the faster way. It does this because it has learned my route preference for going from home to work.

If, when heading home, I could choose a route (ie, "work to home") rather than just a destination (ie, "home"), then Waze would know to send me home on my work -> home route when leaving from work, and it would know that when I just choose "home" for my destination that I want the most efficient route it can find, regardless of my past driving preferences.