Re:Scaling Machine Learning at Uber with Michelangelo
by googlemike on Sunday November 04, 2018 @02:14PM
(#18377536)
Please do not conflate GPS with navigation. There is a massive set of problems you can solve with high fidelity GPS Data (Uber knows it is a driver in a car, verifies it with another GPS entity (rider app reports GPS also), etc). There is not that much overlap between great GPS data and great maps - no amount of great GPS data will give you a good basemap. Please let me know if I am not making sense, I am more than happy to provide examples / explain further!
[ Parent
| on HN ]
Re:Scaling Machine Learning at Uber with Michelangelo
by mi_lk on Sunday November 04, 2018 @05:16PM
(#18378346)
Can you expand on the difference between GPS and navigation?
Re:Scaling Machine Learning at Uber with Michelangelo
by googlemike on Sunday November 04, 2018 @08:53PM
(#18379259)
GPS is a system for determining your position in the world, usually in latitude and longitude.
Navigation is pathfinding in the real world + directions. GPS is useful (But far from the only) system for determining where you are. Navigation is often implemented as a route from point A (in lat, lng) to point B (in lat, lng) and then running an algorithm (such as dijkstra, or A*, but usually something far more advanced) from A to B. The algorithm runs on a routing graph of some kind, produced from processing real world map data.
Re:Scaling Machine Learning at Uber with Michelangelo
by krastanov on Sunday November 04, 2018 @07:46PM
(#18378966)
All that a GPS device gives you is your coordinates (latitude and longitude). It does not tell you whether these coordinates correspond to a street address (you need a map for that). It does not tell you how to move between two points (you need a pretty complicated set of routing algorithms and historical/real-time traffic congestion data to do that).