a-b-street / a-b-street/ltn

Improvements to shortcuts computations : consider upstream and downstream nodes

Abierto
#388 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Rust
Estrellas
21
Forks
7
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

I'm creating an issue to track a old comment made here : https://github.com/a-b-street/ltn/issues/69#issuecomment-2600882440

![Image](https://github.com/user-attachments/assets/c88dd893-3c6e-4d33-b2a0-41791260bdda)

https://www.openstreetmap.org/#map=17/43.600230/3.902979

Both of those shortcuts aren't *shortcuts* because you could reach the outcome faster by another path when entering the shortcut.

> We could check what's allowed at the exit intersection. From that exit, if the only reachable point is the entry intersection, then it's this simple redundant case. If there's anything in between, then maybe it's still a shortcut somebody would take, but it could be weighted less, based on how "useful" exiting there is.

So I would suggest that you should not only take the first-downstream node of the exit, you should also take the first upstream node of the entry.

Most of the shortcuts shown here would be discarded or changed

![Image](https://github.com/user-attachments/assets/596717cf-307e-4978-849a-6933806e0e0a)

For example, this shortcut would never be taken as a car would come from upstream(A) which would give another shortcut

![Image](https://github.com/user-attachments/assets/9ad0bc42-eec5-4491-825d-d040ce44d835)

![Image](https://github.com/user-attachments/assets/8e72a3d7-c966-430a-a001-5ace3c18ceb8)

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.