Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Submission + - Hidden Obstacles for Google's Self-Driving Cars (technologyreview.com)

Paul Fernhout writes: Lee Gomes at Technology Review wrote an article on the current limits of Google self-driving car technology: "Would you buy a self-driving car that couldn't drive itself in 99 percent of the country? Or that knew nearly nothing about parking, couldn't be taken out in snow or heavy rain, and would drive straight over a gaping pothole? If your answer is yes, then check out the Google Self-Driving Car, model year 2014. Google often leaves the impression that, as a Google executive once wrote, the cars can "drive anywhere a car can legally drive." However, that's true only if intricate preparations have been made beforehand, with the car's exact route, including driveways, extensively mapped. Data from multiple passes by a special sensor vehicle must later be pored over, meter by meter, by both computers and humans. It's vastly more effort than what's needed for Google Maps. ... Maps have so far been prepared for only a few thousand miles of roadway, but achieving Google's vision will require maintaining a constantly updating map of the nation's millions of miles of roads and driveways. Urmson says Google's researchers "don't see any particular roadblocks" to accomplishing that. When a Google car sees a new permanent structure such as a light pole or sign that it wasn't expecting it sends an alert and some data to a team at Google in charge of maintaining the map. ... Among other unsolved problems, Google has yet to drive in snow, and Urmson says safety concerns preclude testing during heavy rains. Nor has it tackled big, open parking lots or multilevel garages. ... Pedestrians are detected simply as moving, column-shaped blurs of pixels — meaning, Urmson agrees, that the car wouldn't be able to spot a police officer at the side of the road frantically waving for traffic to stop. ..."

A deeper issue I wrote about in 2001 is whether such software and data will be FOSS or proprietary? As I wrote there: "We are about to see the emergence of companies licensing that publicly funded software and selling modified versions of such software as proprietary products. There will eventually be hundreds or thousands of paid automotive software engineers working on such software no matter how it is funded, because there will be great value in having such self-driving vehicles given the result of America's horrendous urban planning policies leaving the car as generally the most efficient means of transport in the suburb. The question is, will the results of the work be open for inspection and contribution by the public? Essentially, will those engineers and their employers be "owners" of the software, or will they instead be "stewards" of a larger free and open community development process?"

This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Hidden Obstacles for Google's Self-Driving Cars

Comments Filter:

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (8) I'm on the committee and I *still* don't know what the hell #pragma is for.