Implementing an Order Tracking System
summary
A practical case study of building an order-tracking system for Yakitoria: collecting courier GPS data, initial filtering, map-matching to streets, and post-processing to avoid naive "plot raw coordinates" approaches. It covers techniques to minimize lag between the on-screen vehicle and the real courier, problems rendering routes due to treating maps as Euclidean space, handling missing/ended coordinates, and several attempted (but unsuccessful) ideas.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:31First implementation issues
- 5:00GPS errors and impacts
- 7:09Choosing geoservice
- 9:58Data delays and batching
- 11:22Server-client separation
- 13:08Track display problems
- 16:16Debugging tools
- 22:21Project results
- 27:02Future possibilities
- 28:06Q&A
- 31:44Estimation error history
- 32:11Handling inaccurate data
- 33:38Coordinate delays
- 35:04Raw vs filtered data
- 36:53Data transfer protocol
- 37:57Big data processing
- 39:02System support
- 40:08Data transfer stats
related talks
05mALWAES: Automatic Location-Aware Correction System for Online Delivery Platforms
28m"Where, When, Why, and How: Directi
15mBeyondTracks: an OpenStreetMap case study
15mThe turf wars on data - can be a matter of life and death
05mCall of the Wild I Mapping good dogs in the Yukon
05mCall of the Wild II Open source tech for a dog sled race in the Yukon
24m"Good luck with that": Tag Teaming Civic Data
30mDeveloping a Westy Tracking platform on Cloud Foundry