此场景使用简单的费用参数来优化分配给车辆的经停顺序。这是最简单的路线优化操作模式,可确保在指定时间范围内访问所有经停点。
以下示例演示了一种基本场景,其中包含一辆车和三批货物,所有这些货物都源自一个称为“仓库”的位置。
查看示例请求
{ "populatePolylines": true, "populateTransitionPolylines": true, "model": { "globalStartTime": "2023-01-13T16:00:00-08:00", "globalEndTime": "2023-01-14T16:00:00-08:00", "shipments": [ { "deliveries": [ { "arrivalLocation": { "latitude": 37.789456, "longitude": -122.390192 }, "duration": "250s" } ], "pickups": [ { "arrivalLocation": { "latitude": 37.794465, "longitude": -122.394839 }, "duration": "150s" } ] }, { "deliveries": [ { "arrivalLocation": { "latitude": 37.789116, "longitude": -122.395080 }, "duration": "250s" } ], "pickups": [ { "arrivalLocation": { "latitude": 37.794465, "longitude": -122.394839 }, "duration": "150s" } ] }, { "deliveries": [ { "arrivalLocation": { "latitude": 37.795242, "longitude": -122.399347 }, "duration": "250s" } ], "pickups": [ { "arrivalLocation": { "latitude": 37.794465, "longitude": -122.394839 }, "duration": "150s" } ] } ], "vehicles": [ { "endLocation": { "latitude": 37.794465, "longitude": -122.394839 }, "startLocation": { "latitude": 37.794465, "longitude": -122.394839 }, "costPerKilometer": 10.0, "costPerHour": 40.0 } ] } }
路由优化请求字段
如概览中所述,最重要的路由优化请求属性是 vehicles
和 shipments
。
除了车辆和运单之外,该请求还包含以下字段:
多段线
populatePolylines
和 populateTransitionPolylines
用于指定路线优化是否应返回多段线。
该服务使用 Maps JS 多段线编解码器(使用可打印的 ASCII 字符表示二进制多段线数据)对多段线进行编码。您可以使用交互式多段线编码器实用程序来直观呈现通过路线优化计算的路径。本指南中的示例将 populatePolylines
和 populateTransitionPolylines
设为 true,但其他指南将其设为 false 以缩减响应大小。
如需了解编码格式,请参阅编码多段线算法格式。
全球时间限制
model.globalStartTime
和 model.globalEndTime
可设置为任意 24 小时时间段。这样,输出时间戳更易于解读。
造访地点
示例请求仅使用 model.shipments[].pickups[].arrivalLocation
和 model.shipments[].deliveries[].arrivalLocation
。此外,还有一个 departureLocation
属性,适用于车辆从与到达地点不同的位置离开的情况,例如一个停车场,入口在建筑物的一侧,出口在另一侧。在此指南和后续指南中,假定到达点和出发点相同。
到达和出发时间 waypoint
也存在,作为 latLng
的替代选项。Waypoint
字段支持使用 Google 地点 ID 来替代 LatLng
,并且还可以指定车辆标题。如需了解详情,请参阅参考文档(REST、gRPC)。
示例中的限制
此场景通过以下几种方式限制优化器:
- 所有活动都必须在全局开始时间与结束时间之间完成。 在此场景中,鉴于货运距离较近且全球时间窗口较广,开始时间和结束时间是非常宽松的约束条件。
- 必须完成所有运单。这是未在
shipments
上指定惩罚性费用时的默认行为。 - 在车辆上设置了
costPerKilometer
和costPerHour
。
费用在费用模型参数中进行说明。
路由优化响应属性
查看对示例请求的响应
{ "routes": [ { "vehicleStartTime": "2023-01-14T00:00:00Z", "vehicleEndTime": "2023-01-14T00:36:41Z", "visits": [ { "shipmentIndex": 2, "isPickup": true, "startTime": "2023-01-14T00:00:00Z", "detour": "0s" }, { "shipmentIndex": 1, "isPickup": true, "startTime": "2023-01-14T00:02:30Z", "detour": "150s" }, { "isPickup": true, "startTime": "2023-01-14T00:05:00Z", "detour": "300s" }, { "startTime": "2023-01-14T00:11:25Z", "detour": "0s" }, { "shipmentIndex": 1, "startTime": "2023-01-14T00:19:29Z", "detour": "503s" }, { "shipmentIndex": 2, "startTime": "2023-01-14T00:29:02Z", "detour": "1324s" } ], "transitions": [ { "travelDuration": "0s", "waitDuration": "0s", "totalDuration": "0s", "startTime": "2023-01-14T00:00:00Z", "routePolyline": {} }, { "travelDuration": "0s", "waitDuration": "0s", "totalDuration": "0s", "startTime": "2023-01-14T00:02:30Z", "routePolyline": {} }, { "travelDuration": "0s", "waitDuration": "0s", "totalDuration": "0s", "startTime": "2023-01-14T00:05:00Z", "routePolyline": {} }, { "travelDuration": "235s", "travelDistanceMeters": 795, "waitDuration": "0s", "totalDuration": "235s", "startTime": "2023-01-14T00:07:30Z", "routePolyline": { "points": "kvteFtfjVAA?C?C@C?A?C@AFMj@s@JKb@k@Zc@LSjA}ARWDGdAxAdAvAXa@@k@AsA\\c@FKp@_A\\c@Ze@fA{ALSFGd@o@rAgBB{BZc@" } }, { "travelDuration": "234s", "travelDistanceMeters": 793, "waitDuration": "0s", "totalDuration": "234s", "startTime": "2023-01-14T00:15:35Z", "routePolyline": { "points": "cwseFti_jVRWj@w@x@eAHLNRHJbApAHLX\\V^?@hA~AT\\PVFFDHDFJNp@~@NRLNNTFFUZIJY^Y^g@p@[`@KP{@fAEFSXe@l@c@h@WZY\\?BELk@v@MNa@l@" } }, { "travelDuration": "323s", "travelDistanceMeters": 1204, "waitDuration": "0s", "totalDuration": "323s", "startTime": "2023-01-14T00:23:39Z", "routePolyline": { "points": "cuseFhjVSTY`@Yb@GHEDIJEF]f@IJi@r@oAbBeCfDKLaApAKNQVIPKPCDQJIBIBM@iAJeALqBVC@C?A?QBYDI@C?_@Dc@FO@a@FDp@HfAHvABVDl@Dj@PpCQDiALsALAQASKwAOgBEe@COCYEa@Es@Eg@" } }, { "travelDuration": "209s", "travelDistanceMeters": 665, "waitDuration": "0s", "totalDuration": "209s", "startTime": "2023-01-14T00:33:12Z", "routePolyline": { "points": "{zteFxbajV?CAYEc@AMC_@AOAK?E?CCWAOAKCe@CY?WScDEm@d@EFA\\ENCB?XEVC^E`@EhBUVCNEB?@?\\Er@IMUe@k@k@w@AAMQa@i@SWQWMQi@u@AC?A" } } ], "routePolyline": { "points": "kvteFtfjVAA?C?C@C?A?C@AFMj@s@JKb@k@Zc@LSjA}ARWDGdAxAdAvAXa@@k@AsA\\c@FKp@_A\\c@Ze@fA{ALSFGd@o@rAgBB{BZc@RWj@w@x@eAHLNRHJbApAHLX\\V^?@hA~AT\\PVFFDHDFJNp@~@NRLNNTFFUZIJY^Y^g@p@[@KP{@fAEFSXe@l@c@h@WZY\\?BELk@v@MNa@l@STY@Yb@GHEDIJEF]f@IJi@r@oAbBeCfDKLaApAKNQVIPKPCDQJIBIBM@iAJeALqBVC@C?A?QBYDI@C?_@Dc@FO@a@FDp@HfAHvABVDl@Dj@PpCQDiALsALAQASKwAOgBEe@COCYEa@Es@Eg@?CAYEc@AMC_@AOAK?E?CCWAOAKCe@CY?WScDEm@d@EFA\\ENCB?XEVC^E`@EhBUVCNEB?@?\\Er@IMUe@k@k@w@AAMQa@i@SWQWMQi@u@AC?A" }, "metrics": { "performedShipmentCount": 3, "travelDuration": "1001s", "waitDuration": "0s", "delayDuration": "0s", "breakDuration": "0s", "visitDuration": "1200s", "totalDuration": "2201s", "travelDistanceMeters": 3457 }, "travelSteps": [ { "duration": "0s", "routePolyline": {} }, { "duration": "0s", "routePolyline": {} }, { "duration": "0s", "routePolyline": {} }, { "duration": "227s", "distanceMeters": 794, "routePolyline": { "points": "kvteFtfjVAA?C?C@C?A?C@AFMj@s@JKb@k@Zc@LSjA}ARWDGdAxAdAvAXa@@k@AsA\\c@FKp@_A\\c@Ze@fA{ALSFGd@o@rAgBB{BZc@" } }, { "duration": "233s", "distanceMeters": 791, "routePolyline": { "points": "cwseFti_jVRWj@w@x@eAHLNRHJbApAHLX\\V^?@hA~AT\\PVFFDHDFJNp@~@NRLNNTFFUZIJY^Y^g@p@[`@KP{@fAEFSXe@l@c@h@WZY\\?BELk@v@MNa@l@" } }, { "duration": "322s", "distanceMeters": 1205, "routePolyline": { "points": "cuseFhjVSTY`@Yb@GHEDIJEF]f@IJi@r@oAbBeCfDKLaApAKNQVIPKPCDQJIBIBM@iAJeALqBVC@C?A?QBYDI@C?_@Dc@FO@a@FDp@HfAHvABVDl@Dj@PpCQDiALsALAQASKwAOgBEe@COCYEa@Es@Eg@" } }, { "duration": "208s", "distanceMeters": 666, "routePolyline": { "points": "{zteFxbajV?CAYEc@AMC_@AOAK?E?CCWAOAKCe@CY?WScDEm@d@EFA\\ENCB?XEVC^E`@EhBUVCNEB?@?\\Er@IMUe@k@k@w@AAMQa@i@SWQWMQi@u@AC?A" } } ], "vehicleDetour": "2201s", "routeCosts": { "model.vehicles.cost_per_hour": 24.455555555555556, "model.vehicles.cost_per_kilometer": 34.57 }, "routeTotalCost": 59.025555555555556 } ], "totalCost": 59.025555555555556, "metrics": { "aggregatedRouteMetrics": { "performedShipmentCount": 3, "travelDuration": "1001s", "waitDuration": "0s", "delayDuration": "0s", "breakDuration": "0s", "visitDuration": "1200s", "totalDuration": "2201s", "travelDistanceMeters": 3457 }, "usedVehicleCount": 1, "earliestVehicleStartTime": "2023-01-14T00:00:00Z", "latestVehicleEndTime": "2023-01-14T00:36:41Z", "totalCost": 59.025555555555556, "costs": { "model.vehicles.cost_per_kilometer": 34.57, "model.vehicles.cost_per_hour": 24.455555555555556 } } }
路线优化响应包含一个表示建议路线的顶级 routes
字段,每辆车对应一条路线。由于本指南中的示例请求仅指定了一辆车,因此 routes
中包含一个 ShipmentRoute
消息。
ShipmentRoute
个房源
ShipmentRoute
消息类型的两个最重要的属性是 visits
和 transitions
。
每个 Visit
都表示通过请求消息的其中一个 VisitRequest
完成取货或送货。光顾是指有效地分配由车辆在某个地点和时间完成的工作。
每个 Transition
表示从一个位置前往另一个位置的车辆。过渡可以在车辆的起点、访问位置和车辆的端点之间发生。
如需重建车辆的完整路线,必须组合 ShipmentRoute
的 visits
和 transitions
。各字段组合到车辆活动进展的过程如下所示:
request.vehicles[0].startLocation -> transitions[0] -> visits[0] ->
transitions[1] -> visits[1] -> transitions[2] -> ... -> visits[3] ->
transitions[4] -> request.vehicles[0].endLocation
ShipmentRoute
始终比 visits
多一个 transitions
,因为车辆必须在路线开始时从其起始位置行驶到其第一次访问,以及在路线结束时从最后一次访问到结束位置。如果车辆缺少开始位置或结束位置,其 transitions
仍然会比 visits
多一个,因为首次访问或最后一次访问的位置分别用作车辆的开始位置或结束位置。
在此示例中,前三个自提服务在它们之间具有转换,距离和时长为零,因为所有三个自提服务在请求中位于相同的位置。
如需了解详情,请参阅 ShipmentRoute
参考文档(REST、gRPC)。
简单的航点顺序优化
如此示例所示,路线优化将访问建模为运单的属性,并且不将航点或经停点视为独立实体。不过,您可以将经停点或航点表示为运单,并且只有一个 VisitRequest
表示取货或送餐。车辆仍必须分配有 costPerHour
或 costPerKilometer
,优化器才能找到最佳路线(而不是寻找任何可行路线)。