MarcL20 wrote:The hardest one we already have that its the average aquired by the client. Adding a Max speed in database is simple since it will be done by the editor and is just another data field that you will add to waze road registers. I dont know how is waze algorithm but instead of comparing just with the average, using existing methods "and" maxspeed shouldnt be difficult.
Your using Max speed as a synonym for a Speed Limit. There has been huge discussions about this prior.
If your referring to the max speed driven on a road segment (which can be really off, considering some may drive 70 mph on a typically 30 mph road), then, this information will again be relatively useless, unless if it used some sort of moving average for the maximum speed driven on a segment.
But then it wouldn't even be used for routing, but to help display perpetual slow average traffic as a jam. But that's not even needed, as Waze already knows that segment is slow.
So, basically, as I said, this suggestion would require a lot of work (think, you add in a field in the database, then you have to populate the records with information for that field, then you have to integrate the field with the servers and client, which would require a complete restructuring of the interfaces being used within the code.
EDIT: It's never as simple as *just* adding another field to a database. It's much more complicated, and would require much more work than you think.
Simply put, absolutely no gain, for a lot of work, and probably a lot of feature-breaking bugs.