Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Good summary! (I was away for a bit)

I would only caution that people shouldn't overindex on mapping costs. When you're talking about entering a major metro area, you need lots of vehicles and depots and so on anyway just to provide the eventual service. So the upfront initial map build out is certainly a component of starting in a new geography, but I think people assume it is somehow dominant. It's not.

The current approach then for ride hailing, which requires depots, means that:

> just turn on the tap, buy a million cars and cover the whole country

is not happening anytime soon.



There seems to be a lot of misconception and misinformation about mapping. People (mostly influencers associated with Tesla) constantly cite it as a major bottleneck for scaling. And there are barely any technical details about the mapping process. Are you able expand on the following:

- Is the initial mapping effort very high and expensive? How long does it take, on an average, to fully map a city the size and complexity of San Francisco?

- How much of the mapping process is automated?

- How are the maps kept up-to-date? We know from Waymo's blog post a while ago [1] that the cars map continuously. But is human intervention required to verify an update (like a new construction zone that was encountered)?

- How much of the country have you already mapped? Waymo says they are testing in 25 cities, so I'm assuming the number is at least 25 cities.

- What does a vehicle do if it detects a mismatch of road conditions vs the onboard map? (I already know the answer, but this is one of the most frequent points of misinformation where people say it stops working)

Anything you can share without revealing your secret sauce is appreciated!

[1] https://blog.waymo.com/2020/09/the-waymo-driver-handbook-map...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: