A lot of folks don’t realize that Elon Musk got his first big break as an entrepreneur building mapping software. He and his brother Kimbal started Zip2 in 1995, which provided phonebook-style business listings along with embedded maps for a little wow factor.
I see no reason why Tesla wouldn't work on its own mapping data:
1. In car navigation has a map to let the driver choose where they want to go. Even a full self driving car needs a map to know where to turn and which exit to take. Making this map up to date as much as possible improves the experience for those who drive in newly developed areas.
2. Tesla already uses a lot of vision and location data from the fleet with consent of the user. Few would object to this collection of data if it means better in-car experience (Google maps is a good precedence to gauge user willingness as most already consent to have their location used for traffic stats, busy hours and more). Also when handled properly, no personal data would be leaking when constructing maps collectively from millions of cars. Google does this with map and in fact, a large number of users willingly spend time to improve Google maps, a 100% proprietary product. In case of Tesla, user spends no time.
3. Tesla has a track record of doing many things in-house that other manufacturers have outsourced (software, computing hardware, seats). Maps, being an essential part of the software stack is no exception to this trend.
4. Map data is of immense value (due to the large investment required to acquire and maintain it) and can become yet another source of revenue for Tesla if it decides to license it to other companies. It would cost Tesla considerably less to produce maps vs Google, as the fleet is paid by Tesla customers.
But, but, but...space will come to the rescue, won't it? Sure, it adds a needlessly complex component to an already complex problem, but...oh, I see...;-)
Again, people overestimate not only the number of Teslas on the road, but where they are actually driving. Even in the Bay Area, they don't drive down every single road/alley much less in bum-f*** Iowa.
I see no reason why Tesla wouldn't work on its own mapping data:
1. In car navigation has a map to let the driver choose where they want to go. Even a full self driving car needs a map to know where to turn and which exit to take. Making this map up to date as much as possible improves the experience for those who drive in newly developed areas.
2. Tesla already uses a lot of vision and location data from the fleet with consent of the user. Few would object to this collection of data if it means better in-car experience (Google maps is a good precedence to gauge user willingness as most already consent to have their location used for traffic stats, busy hours and more). Also when handled properly, no personal data would be leaking when constructing maps collectively from millions of cars. Google does this with map and in fact, a large number of users willingly spend time to improve Google maps, a 100% proprietary product. In case of Tesla, user spends no time.
3. Tesla has a track record of doing many things in-house that other manufacturers have outsourced (software, computing hardware, seats). Maps, being an essential part of the software stack is no exception to this trend.
4. Map data is of immense value (due to the large investment required to acquire and maintain it) and can become yet another source of revenue for Tesla if it decides to license it to other companies. It would cost Tesla considerably less to produce maps vs Google, as the fleet is paid by Tesla customers.
But, but, but...space will come to the rescue, won't it? Sure, it adds a needlessly complex component to an already complex problem, but...oh, I see...;-)
Again, people overestimate not only the number of Teslas on the road, but where they are actually driving. Even in the Bay Area, they don't drive down every single road/alley much less in bum-f*** Iowa.