But what you just revealed is something that could make a real difference in FSD capability, depending on whether the data connection is available. It begs a few further questions (answers for which may be unknown now, but if you have any insight please comment):
- Is this drive time server download a new thing, or something that has been added recently? Is it applicable only to FSD beta, or has it been around for legacy NoA as well?
- What happens if the call to the Mothership server fails during the route planning or route execution? Is there a timeout, or does it keep trying as the drive proceeds along the route? Upon failure, does the information devolve to the in-car stored map database (with presumably coarser and/or very stale information), or does it remember data from the most recent drive on or near that route?
- Do you think this map details feature will be an integral enabler of things like parking lot mapping for Actual Smart Summon and presumably required robotaxi pickup/dropoff operation?
Finally, is it your sense that this discovered capability is indeed highly significant for the upcoming development of FSD, or am I extrapolating too far from what you explained? Thanks so much for whatever additional commentary you can provide.