Skip to content

Include route points explicitly in the output layer #296

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

Open
MichaelsJP opened this issue Feb 19, 2025 · 4 comments
Open

Include route points explicitly in the output layer #296

MichaelsJP opened this issue Feb 19, 2025 · 4 comments

Comments

@MichaelsJP
Copy link
Member

MichaelsJP commented Feb 19, 2025

As the title suggests. Include the route geometry as points within the response

@MichaelsJP MichaelsJP changed the title Include the numbering Popups from setting points into the result Include route points explicitly in the output layer Feb 19, 2025
@merydian
Copy link
Collaborator

merydian commented Mar 4, 2025

@koebi some input would be great.

This should be done after #268

@koebi
Copy link
Collaborator

koebi commented Mar 5, 2025

Hey @MichaelsJP,

your issue is a bit unclear to me.
Judging from the previous title, this is about being able to reconstruct or save the points used when creating a route via the GUI part of the plugin. Please correct me if I didn't get what you were saying.

One of the latest releases included the functionality to save the points from the GUI to a dedicated layer.
From my POV, this solves this issue and is an acceptable tradeoff.

What do you think?

@MichaelsJP
Copy link
Member Author

Hey. No. The previous title was a misunderstanding on my side.

The goal is a feature that outputs an additional point layer after a route calculation that just contains the route points.

This is definitely solvable with QGIS itself already.

However, it seems to be a QoL feature for some to just tick a small button and get the additional layer right away.

@koebi
Copy link
Collaborator

koebi commented Mar 12, 2025

Yeah, QGIS has the Extract Vertices processing algorithm, so I'd rather not do that.

Do you have a use case in mind, where this would be an essential step?

Unless there is a huge demand, I'd like to avoid replicating basic QGIS functionality :)

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

No branches or pull requests

3 participants