pchilds wrote:Dropping to 25 mph in a 55 mph zone for no reason, is less safe than continuing at 55 mph, as a human driver would. IMO, The database will never be 100%, until those that set the speed limits are electronically transferring the data to Tesla's data provider. Speed limits are changed all the time and for no reason.
There is a road I drive that the speed limit would drop from 55 mph to 45 mph, then a 1/4 mile later it drops to 40 mph, they changed it to 55 mph to 50 mph, then in an 1/8 mile to 40 mph. The government workers must have a quota for speed limit changes or it is outsourced to a private company and they charge by the change.
The car needs a basic speed for the road type, if you are on a divided road the car should not be slowing to 25 mph, 45 mph should be the minimum, no matter what the database thinks it should be.
Maybe people should be driving the cars themselves on such roads, then, if Tesla's autonomous system is unable to do so in conformance with the law. I've got a similar road nearby, although I don't think the speed changes are arbitrary (as I'm usually traveling it by bike, my speed is well under the limit regardless). I agree that speed limits will need to be kept in real time on government databases; for one thing, how else could you handle construction zones when the car itself can't recognize them (as it currently can't). It's either a database, or some type of real-time communication between the hazard and the car, as I rather doubt that the car's sensors can recognize flares or cones and act accordingly. This will undoubtedly be implemented as our roads become increasingly smart and V2V/V2R becomes the norm. In the meantime, most states have basic speed laws for various road types, so having that info in memory as a default fall-back shouldn't be a problem. Whether it would be enough to keep you or Tesla from being ticketed/found at fault will be up to the legislatures and the courts.