The software routing 260,000 grocery deliveries a week
ocadotechnology.com
The software routing 260,000 grocery deliveries a week
1–10 of 41 posts
Re: The software routing 260,000 grocery deliveries a week
#2Re: The software routing 260,000 grocery deliveries a week
#3Re: The software routing 260,000 grocery deliveries a week
#4For someone quite interested in these kind of problems, what's the current best practice for solving these kind of problems? Not on this scale but still large enough that Google's built-in api for solving it (only 25 points allowed) can't do it.
Re: The software routing 260,000 grocery deliveries a week
#5For someone quite interested in these kind of problems, what's the current best practice for solving these kind of problems? Not on this scale but still large enough that Google's built-in api for solving it (only 25 points allowed) can't do it.
This is just self-congratulatory PR, trying to persuade potential investors that's they're a hard tech company.
Re: The software routing 260,000 grocery deliveries a week
#6For someone quite interested in these kind of problems, what's the current best practice for solving these kind of problems? Not on this scale but still large enough that Google's built-in api for solving it (only 25 points allowed) can't do it.
Re: The software routing 260,000 grocery deliveries a week
#7For someone quite interested in these kind of problems, what's the current best practice for solving these kind of problems? Not on this scale but still large enough that Google's built-in api for solving it (only 25 points allowed) can't do it.
Re: The software routing 260,000 grocery deliveries a week
#8For someone quite interested in these kind of problems, what's the current best practice for solving these kind of problems? Not on this scale but still large enough that Google's built-in api for solving it (only 25 points allowed) can't do it.
They also probably decouple their problem into disjoint regions before solving it, to reduce the dimensionality of the problem(s).