Gas prices feature: everything you need to know

[Twister_UK]

Has the price reporting functionality just been given a behind the scenes tweak? Every set of prices I submitted today was acknowledged in the client, not by the usual message, but instead by "Your price will be posted once confirmed with other Wazers", which I've never seen before.

Whilst the idea of not posting prices until they've been confirmed seems like a good idea (a few times I've seen completely incorrect prices locally, all appearing to come from the same user...), I think there needs to be some tweaking to the implementation. Based on the client behaviour today, other than that text at the bottom of the price submission screen, there's no other feedback given to the user that their submitted prices are awaiting confirmation, so if you're in an area with a whole bunch of stations and you've forgotten which once you've already submitted that day, you can't then select a station and see that you were the most recent update - until your prices are confirmed, the station details show up exactly the same as before you made your earlier submission, so you might end up trying to resubmit in the belief that you hadn't sibmitted to that station already, or that your earlier submission didn't make it. It'd be useful if the client could mark the stations somehow to show if we've already submitted prices today...

One other thing about this feature-if no-one else confirms the new prices, do they just get lost or do they get posted anyway after a while? I'm thinking that if prices *have* to get confirmed before they're used, some stations could end up with very out of date pricing, especially if by the time the next Wazer passes the station, the prices have changed leaving them unable to confirm. If their updated prices then get put in the confirmation queue, and the prices then change again, will the station ever get updated?

[foxitrot]

Both outdated and unconfirmed prices could be displayed grayed-out, with an appropriate textual remark. If there is a concern regarding points, then these could be delayed or split.

[Twister_UK]

Outdated prices don't need to be highlighted specifically, as the client tells you when they were last updated when you access the price entry screen-what we need is a way of knowing that we've already submitted an unconfirmed price for that station, so that we don't end up wasting time resubmitting.

Having now said that, today at every station I've passed so far, the client has been accepting new prices immediately, so it looks as if something has been changed again...

[Twister_UK]

Having now said that, today at every station I've passed so far, the client has been accepting new prices immediately, so it looks as if something has been changed again...

And now it's saying prices will need confirming again... I think what's happening is that any station where I've regularly submitted prices is still accepting updates straight away, but for stations where I don't usually submit prices it's saying they'll need confirmation. Which seems like an odd logic to use-if Waze thinks I'm capable of submitting prices correctly at some locations, why not any others?

[foxitrot]

Maybe you're not yet being considered a "trusted submitter" at some stations and have to be confirmed at these? (Might make sense, but I doubt anything more is being stored except the very last submitter.)

[Twister_UK]

Well, bang goes that theory... just been queued for confirmation at a station I've been updating almost every day since the fuel prices feature went live in the UK.

[maantje76]

There are indeed problems. I also received these kind of messages last week. I did even received even messages 'Your still a babywazer. You can't update prices'

ImageUploadedByTapatalk1356361642.402372.jpg (66.09 KiB) Viewed 558 times

[maantje76]

ImageUploadedByTapatalk1356361846.429874.jpg (69.99 KiB) Viewed 556 times

I will re-bump my previous support request with these problems...

[fvwazing]

I can think of schemes where a gasstation-owner would want to manipulate prices in his neighborhood and Waze would want to detect that,to prevent such cheating. Or someone does inaccurate pricing, driving by, and thus create systematic errors. It is perfectly possible to detect such "errors" using comparison of historical data and there should be no need to hold up the publishing for confirmation. After some time it would get noticed that often the price is wrong anyway and the user could be blocked (or better: ignored).

[vitj]

Thank you, that was enabled Gas prices in Czech Republic. But we have problem to update prices. Always after command send is answer Pardon, not possible update price. Could you help to us?