" endT ime":" 2019-05-10T17:00:00",     " endLocation":{        " latitude":47.739236,       " longitude":-122.339974      }     }    ]   }  ],  " itineraryItems":[{     ;"name":"CaféTrelfth","   " openingTime":"2019-01-24T08:00:00",   " closingTime":" 2019-01-24T20:00:00",&   " dwellTime":" 01:30 :00.00",    " priority":1,    " location":{     " latitude":47.615006,     &quo t;经度":-122.348236 $    }   },{      ;" name" ;:"Granny Food Truck","   " openingTime":" 2019-01-24T11:00:00",&   " closingTime":" 2019-01-24T14:30:00",&b $ b   " dwellTime":" 01: 30:00.00",    " priority":1,    " location":{     " latitude":47.664440,     " longitude":-122.372138    } ... API输出现在包括行程项目名称。  谢谢! Hi,I need to know more details regarding Multi-Itinerary Optimization API.Let say, I have a sales person who works from 8.00 am to 5.00 pm with lunch break of 1 hours between 1.00 pm to 2.00 pm. And have 15 jobs to visit. And i want to generate optimize route for this sales person. So as per MIO API blog, sales persons shift will be divided in 2 part as 8.00 am - 1.00 pm and from 2.00 pm - 5.00 pm. But, MIO API is also expecting the location of 1.00 pm which is end of 1st shift and 2.00 pm which is start of another shift. As i have to schedule these 15 jobs dynamically, then how do we know the end location of 1<sup>st</sup> shift i.e. location at 1.00 pm and start location of 2nd shift i.e. location at 2.00 pm. I was expecting that the end location of 1st shift and start location of 2nd shift should be set/considered dynamically.Also, MIO API generate routes for each agents/sales person, but it is providing only Latitude and Longitude to visit next, not the name or index of the Itinerary to visit. So is there any way to add Names of client in this generated routes for the sales person in API, so that it will be easier for me to check that, from start location, sales person need to go to record X and from records X, he need to go to record Y.  Thank You! 解决方案 Hi Yogesh, Thanks for your interest in the MIO API. With one agent and multiple shifts, the start and end locations of each shift are optional. Below is an example how you can define the shifts: { "agents": [{   "name": "Salesperson",   "shifts": [{     "startTime": "2019-05-10T08:00:00",     "startLocation": {      "latitude": 47.60897,      "longitude": -122.340914     },     "endTime": "2019-05-10T13:00:00"              }, {     "startTime": "2019-05-10T14:00:00",          "endTime": "2019-05-10T17:00:00",     "endLocation": {      "latitude": 47.739236,      "longitude": -122.339974     }    }   ]  } ], "itineraryItems": [{   "name": "Café Twelfth",   "openingTime": "2019-01-24T08:00:00",   "closingTime": "2019-01-24T20:00:00",   "dwellTime": "01:30:00.00",   "priority": 1,   "location": {    "latitude": 47.615006,    "longitude": -122.348236   }  }, {   "name": "Granny Food Truck",   "openingTime": "2019-01-24T11:00:00",   "closingTime": "2019-01-24T14:30:00",   "dwellTime": "01:30:00.00",   "priority": 1,   "location": {    "latitude": 47.664440,    "longitude": -122.372138   }…The API output now includes the itinerary item names. Thank you! 这篇关于多行程优化API的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持! 上岸,阿里云!
09-05 04:11