mapbox / mapbox/node-or-tools

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

Abierto
#60 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
C++
Estrellas
155
Forks
47
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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?

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
cpp, node.js
Área
backend
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.