Turns out we probably don't need to run the distance matrix on all combinations of the trip points, and then have the genetic algorithm re-order the points. We can probably call a native trip or table api within the OSRM service to return the points in order for us (depending on origin and destination points)
Turns out we probably don't need to run the distance matrix on all combinations of the trip points, and then have the genetic algorithm re-order the points. We can probably call a native trip or table api within the OSRM service to return the points in order for us (depending on origin and destination points)
Check out: http://project-osrm.org/docs/v5.7.0/api/#requests