parking lot landmarks / traffic analysis
I would like to see certain landmarks not count as traffic analysis. If an area is marked as a restaurant, parking lot, gas station, etc.. the time a waze client spends there should NOT count against traffic analysis. Wazers can't be expecte to turn their nav system on and off just to order a burger, or fill up the tank. In reality, a nav system should be as "hands off" as possible for the daily commute. start waze when you get in the car.. go on your trip, pull over at the gas station and leave waze running. go through the drive through and order lunch.. etc. then when you reach your destination, turn waze off.
And you can with intents.
search: expose intents
If your device platform does not yet support intents (a feature not the name of an app)
The next best choice is waze API
search: waze API
A mature API will also have additional intents exposure or allow third party app to provide intents via APIs
Those allow you to use existing potential YOURSELF to get what you want without creating gui bloat or distracting developers. You do NOT need to be a programmer to wield intents or APIs
Dead reckoning will allow finding parked vehicle in parking structure
The most fascinating use for accelerometer I've ever seen is dead reckoning
This would function best as feedback from high weighted wazers and ought NOT require cartouche.
But it absolutely MUST require a highly precise gps fix. ≤ 8 meters
When creeping logic should engage reliance more on the accelerometer
John Keck commented
In addition to the points mentioned above, some landmarks (Parking Lots especially) should cancel the "snap to road" function in the client.