Mappoint 路由解决方案
我正在努力更新内部路由解决方案，该解决方案已经运行良好一段时间了。然而，需求的变化导致了一些问题。在谷歌搜索时，我发现了一款名为 MapPoint 2010 的 Microsoft 产品。
据我了解，该产品有一个可以在 .net (c#) 中使用的 API。目前，我们使用 Google 地图对工程师的地址和出发位置进行地理编码。我希望能够将此数据传递给 MapPoint，将每个工作位置标记为第一次呼叫、上午呼叫或下午呼叫，用最大分配标记每个工程师，并要求 MapPoint 将工作分配给工程师。完成后，提取数据并将其传回我们的 SQL 数据库。 MapPoint 可以做到这一点吗？
有没有人有使用 MapPoint 来满足此类需求的经验？
标记
I'm working on updating an in-house routing solution that has been working well for some time. However a change in requirements is causing some problems. While googling, I came across a Microsoft product called MapPoint 2010.
From what I've read this product has an API that can be used from .net (c#). At present we use Google Maps to geocode the address and start locations of our engineers. I would like to be able pass this data to MapPoint, tag each job location as first call, am call or pm call, tag each engineer with a max allocation and ask MapPoint to allocate jobs to engineers. Once this completes, extract the data and pass it back to our SQL database. Is this something MapPoint can do?
Has anyone experience of using MapPoint for this type of requirement?
Mark
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我相信 MapPoint 本身并不提供此类功能，但可以帮助您根据资源量和请求将任务分配给工程师并将工程师分配到不同的位置。但这个逻辑基本上需要你来实现。
I believe that MapPoint does not provide such functionality by itself, but could help you with allocating tasks to your engineers and engineers to locations depending of the amount of resources and requests you have. But this logic basically needs to be implemented by you.
是的，正如您所发现的，MapPoint 可以进行简单的路由，甚至“旅行商路由”，但是它不能进行任何时间或容量优化。
有一些扩展可以满足您的需求，但价格通常至少比 MapPoint 高一个数量级 - 这是因为它在计算上是一件“困难”的事情。成本较低的产品之一是“TourSolver”。它带有自己的数据和路由引擎，但使用 MapPoint 进行数据输入和最终路由显示。
Yes as you've found, MapPoint can do simple routing, and even "Traveling Salesman Routing", however it cannot do any time or capacity optimization.
There are extensions available to do what you are looking for, but the price is typically at least an order of magnitude higher than MapPoint - this is because it is a "difficult" thing to computationally do. One of the lower cost products is "TourSolver". This ships with its own data and routing engine, but uses MapPoint for data input and final route display.