-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Modeler: project point (cartesian) does not accept an output from algorithm "snap geometry to layer" #42200
Comments
@MMR100 is this a question? a bug report? else? |
@gioman It is a bug. |
@MMR100 So I guess that it works not in the context of the modeller, correct? |
You are correct. The issue occurs only when using the modeller. |
I'm pretty sure this is because project point exclusively accepts point data and the other tool outputs a vector layer. As the constraint is not guaranteed this is not permitted. I don't think its a bug, though the input could be made less strict and fail on execution. |
Though in 3.12 it seemed fine to accept the input. |
@roya0045 so regression? |
No sure, I can't test anything more recent right now, you can validate with a simple model (2 vectorlayer input, going in snap, then to project point). |
be plugged into algorithm inputs requiring a point or line geometry type Fixes qgis#42200
be plugged into algorithm inputs requiring a point or line geometry type Fixes #42200
be plugged into algorithm inputs requiring a point or line geometry type Fixes #42200
be plugged into algorithm inputs requiring a point or line geometry type Fixes #42200
be plugged into algorithm inputs requiring a point or line geometry type Fixes #42200
be plugged into algorithm inputs requiring a point or line geometry type Fixes #42200
be plugged into algorithm inputs requiring a point or line geometry type Fixes qgis#42200
I want to snap points which are near lines and then move them along these lines.
In the graphical modeler, here are the step:
In step 3, the output from step 2 is not available in the list of algorithm outputs.
As a workaround I created an intermediate step between 2 and 3, such as "rename field", then I select the output of this intermediate step and it works.
The text was updated successfully, but these errors were encountered: