mapbox / mapbox/node-or-tools

RouteLocks is for establish starting points in order, or to assign points to route to visit optimized?

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
155
Forks
47
PR merge metrics
No merged PRs in 30d

Description

I am working with routeLocks to assign some points to a certain route and to visit them along with others remain, in a optimized way. But instead it just makes the VRP to push them in first place to visit starting the route without analyze if those points are optimized.

As you can see in the image red route start from point depot, goes to point 1, next it goes back to point 2, and goes to point 3 which is close to point 1. With routeLock I expected to assign those points to certain route and visit them optimized. As you can see the route is not optimized, it goes far away, and then comes close to depot, then goes far away close to the first point and come back to depot, the traveling time is the highest possible.
geojson io 2

Expected result..
geojson io 4
Or this..
geojson io 3

Any help?
Did I understand wrong?
Is Node-or-tools capable to solve this and assign points to a route and visit them in a optimized way?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the routeLocks entry point and the VRP setup described in the issue; trace how locked points are interpreted during route construction and optimization. Reproduce the route shown in the issue, then establish whether the behavior is expected or needs correction, with the requested optimized route as the completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, node.js
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.