Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

investigate whether importing the GUI point list is viable #211

Closed
Tracked by #144
koebi opened this issue Dec 22, 2023 · 5 comments · Fixed by #216
Closed
Tracked by #144

investigate whether importing the GUI point list is viable #211

koebi opened this issue Dec 22, 2023 · 5 comments · Fixed by #216

Comments

@koebi
Copy link
Collaborator

koebi commented Dec 22, 2023

No description provided.

@koebi koebi changed the title investigate whether populating the list from a layer is viable investigate whether importing the GUI point list is viable Dec 22, 2023
@koebi
Copy link
Collaborator Author

koebi commented Dec 22, 2023

We could think about :

  • populating the GUI point list from a layer
  • populating the list via GeoJSON (compare Valhalla)

@merydian
Copy link
Collaborator

Isn't that what the processing algorithms are for? Maybe keeping it the way it is can be a good motivation to try them out?

@koebi
Copy link
Collaborator Author

koebi commented Jan 8, 2024

Huh, good point :)
Maybe that's something we can mention in docs/wiki somewhere?

@merydian
Copy link
Collaborator

merydian commented Jan 8, 2024

What about putting it in the tooltip of the save vertices button?

@koebi
Copy link
Collaborator Author

koebi commented Jan 11, 2024

https://ask.openrouteservice.org/t/how-to-input-a-layer-in-routing-gui/5657/2 just came up regarding this :D

I do agree, a tooltip sounds quite good 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants