iOS 3.5.1 official feedback thread

[perlin]

One other item I noticed was that the "cookie eating" behavior was a little erratic.

I was in an area on Saturday night that had quite a few unmunched roads, so I drove a few of them because I needed some details to make map updates. I noticed that when I would reach a section where the cookies displayed, the icon on the map wouldn't change and the cookies would stay behind. After I had driven a short distance, then it would start munching and quickly stop and show that I posted 1 point. On some really long sections, it would restart and go for a way, but it would stop again before I reached the end of the section.

I'll try to recreate this in my local area on debug mode, but I'll have to find some roads with cookies left on them.

If you succeed to recreate the problem, please send the debug logs and mention the date & time of the drive.

Will do. Just to confirm, I only need to send the logs from within the application, correct?

Yes.

[TigPT]

I didn't found a topic or category for Feature request, so here it is.

Split this post if this is not the right place for it.

Feature Request: Simple speed limit indicator. Is always useful if not annoying and here is my suggestion.

If (waze know current road speed limit) and if (current speed is above current road speed limit) then (change the velocimeter image to one with the proibit sign or something like that).

Reverse this if speed is below or if enter a road of unknown speed limit.

[jasonh300]

I didn't found a topic or category for Feature request, so here it is.

Split this post if this is not the right place for it.

Feature Request: Simple speed limit indicator. Is always useful if not annoying and here is my suggestion.

If (waze know current road speed limit) and if (current speed is above current road speed limit) then (change the velocimeter image to one with the proibit sign or something like that).

Reverse this if speed is below or if enter a road of unknown speed limit.

The problem is that there's no reliable way to gather this data without Waze going from a free app to a very expensive app.

It could be crowdsourced like a lot of the other data we currently have, but the data would have to be 100% complete before it would be reliable...that would never happen.

I had a GPS app on an old Window Phone several years back with a speed limit and overspeed alert feature. However, it seemed to guess the speed limit based on the road type. The problem was that is that it was rarely right. It often thought the speed limit was 45 when it was actually 30. Any interstate highway was set at 70, even through cities where the speed limit dropped as low as 50.

[TigPT]

Well the info is available based on map editor crowdsourced but yes, it can't be 100% reliable, but thats is true for maps and other info on waze.

[OldGnome]

Well the info is available based on map editor crowdsourced but yes, it can't be 100% reliable, but thats is true for maps and other info on waze.

There are a number of threads on this topic. The results boil down to, "yes, it can be useful information, but it won't be accurate enough to rely upon."

We all realize the maps are also crowd-sourced, but that happens as a result of driving and editing. There is no way to capture the speed limit information as a result of driving. It will never be anywhere near as accurate as the maps.

[McCracken808]

I would ask that Waze check it's ETA calculations. I regularly drive a route that takes me 1.5 - 2 hours with traffic. When I start the route, Waze gives me an ETA of 30-35 mins. It's wrong everytime.

[ahcheong]

May I know why the map updated, but the paved route (red line) still appear in waze client?

I'm using iPhone 4 with iOS 6.0.1

Please advice.

[WeeeZer14]

May I know why the map updated, but the paved route (red line) still appear in waze client?

I'm using iPhone 4 with iOS 6.0.1

Please advice.

It has been this way for a very long time (or forever). You can think of it as a bug OR a feature -- it lets you verify that the roads ended up where you recorded them

[ahcheong]

It has been this way for a very long time (or forever). You can think of it as a bug OR a feature -- it lets you verify that the roads ended up where you recorded them

so waze will consider it as bug and try to fix it?

[perlin]

I would ask that Waze check it's ETA calculations. I regularly drive a route that takes me 1.5 - 2 hours with traffic. When I start the route, Waze gives me an ETA of 30-35 mins. It's wrong everytime.

What are the origin and destination points of the route?