对路线上的停靠点进行分组
我正在从事一个项目，我必须在我们的软件包中为一家害虫防治公司组织服务路线。我们讨论了几种以最有效的方式组织每天停靠的选项。
每天我们有 80-100 个停靠点，每种技术有 10 个左右的停靠点，并且这些停靠点在大多数情况下可以在一个月内以任何方式延长至 7 天，以适应效率。
忽略无法移动的站点，让客户安排技术人员驾驶最短距离的日子的良好起点是什么？
我们每一站都有纬度和经度。目前，我们并不担心桥梁、河流等地理障碍。我们可能会稍后解决这个问题，但目前来说，直线飞行就足够了。有什么想法吗？
编辑：
我们还为每个客户提供“地图网格”。每个地图网格都是半平方英里，并且在我们整个服务区域内形成完美的网格。这些可用于分组和包含路线。通常我们的路线包含大约 100 个半紧密分组的网格。
I work on a project where I have to organize service routes for a pest control company in our software package. We discussed several options to organize the stops for each day in the most efficient manner possible.
Each day we have 80-100 stops, 10 or so stops per tech, and these stops can, for the most part, be moved up to 7 days either way in the month to accomodate efficiency.
Ignoring the stops that can't be moved, what would be a good starting point to get the customers organized into days where the shortest distances are driven by the technicians?
We have lat and long on every stop. For now, we are not worrying about geographic barriers like bridges, rivers, etc. We might tackle that later, but as the crow flies is good enough for now. Any ideas?
EDIT:
We also have "map grids" for each customer. Each map grid is a square half mile, and are in a perfect grid across our entire service territory. These could be used for grouping and containing routes. Usually our routes contain about 100 grids in a semi-tight grouping.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
类似于这个。
您从一个简单的旅行订单开始，然后开始随机交换条目。
每次交换时，您都会测量行程的总长度，如果新的长度更好，则保留它，否则您会撤消交换。
这样做一千次左右，行程就应该开始合理了。
Similar to this.
You start with a naive travel order, and then start randomly swapping entries.
Each time you swap, you measure the total length of the trip, and if the new length is better you keep it, otherwise you undo the swap.
Do it a thousand times or so, and the trip should start to be reasonable.