此场景通过简单的费用参数来优化分配给车辆的停靠站的顺序。这是最简单的路线优化操作模式,可确保在指定时间范围内访问所有车站。
以下示例展示了一个基本场景:一辆车和三艘船,均源自一个称为“仓库”的位置。
查看示例请求
{ "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
。车辆 activity 进展的字段组合如下所示:
request.vehicles[0].startLocation -> transitions[0] -> visits[0] ->
transitions[1] -> visits[1] -> transitions[2] -> ... -> visits[3] ->
transitions[4] -> request.vehicles[0].endLocation
ShipmentRoute
的 transitions
始终比 visits
多一个,因为车辆必须从路线起点的起始位置到达路线起点的第一次造访地点,并从最后一次造访到路线终点的结束位置。如果车辆缺少出发位置或结束位置,则 transitions
仍然会比 visits
多一个,因为第一次或最后一次访问的位置会分别用作车辆的开始位置或结束位置。
在本例中,前三次上车点在两者之间的过渡距离和时长为零,因为所有三个上车点在请求中共享相同的位置。
如需了解详情,请参阅 ShipmentRoute
参考文档(REST、gRPC)。
简单的航点顺序优化
如此示例所示,路线优化将访问作为运送属性进行建模,而不将航点或经停点视为独立实体。不过,您可以将停靠点或航点表示为运单,但只有一个 VisitRequest
表示自提或配送。但仍需为车辆分配 costPerHour
或 costPerKilometer
,以便优化器找到最佳路线(而不是找到任何可行路线)。