Design a Fleet That Collects Mapping Data

Design a vehicle fleet system for collecting mapping data. Explain how collection goals become fleet work, how vehicles upload observations, and how the collected data is validated and tracked. ### Constraints & Assumptions The source specifies fleet-based map-data collection without a sensor suite, geography, or freshness target. State those assumptions. Focus on collection coordination and data handling; autonomous driving behavior is outside this practice design unless separately specified. ### Clarifying Questions Which regions and data types need coverage? How is freshness measured? What connectivity and local-storage limits exist? How are duplicate observations, quality, and collection progress assessed? ### What a Strong Answer Covers A collection-task model, fleet assignment, offline buffering, resumable uploads, provenance, quality checks, coverage tracking, and re-collection decisions. ### Follow-up Questions What if a vehicle disconnects or uploads the same segment twice? How do you prioritize stale or low-quality regions? How do you avoid treating an uploaded file as proof that a mapping task is complete?