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

[QGIS] Snapping on invisible feature #193

Open
dsavary opened this issue Jun 1, 2017 · 23 comments
Open

[QGIS] Snapping on invisible feature #193

dsavary opened this issue Jun 1, 2017 · 23 comments
Assignees
Labels
Milestone

Comments

@dsavary
Copy link

dsavary commented Jun 1, 2017

In QGIS, we can snap on invisible features even if the snapping options have been defined as "snap on all visible layers". The snapping options don't take into accoount the layer style.
Will this be fixed for QGIS 3.0 ?

Démo GIF : https://share.oslandia.net/public/b91c8e

@haubourg
Copy link
Contributor

haubourg commented Jun 1, 2017

Hi @dsavary
let's split it in two phases:

  • do you have qgis 2.99 installed? That could let you test directly in qgis nightlies. You can have them using the osgeo4w installer, and updating is only a 5-6 click job (just run the osgeo4w/bin/setup.bat and choose advanced installer)

  • before fixing what appears to you as a bug, it must be discussed and see if it really is a bug or a feature for all users. When it appears strange to you, it might be a useful feature to other. When you say layer style is not taken into account, are you talking about invisible feature that are:

    • unchecked classes ?
    • unclassified object (ie object not in any category or range class and not falling in a Else Filter)
    • fully transparent ?
    • not visible because of a blending mode effect ?
    • classified but set with "no symbol" style

For unchecked classes, that would make sense not to have a snapping index. For the others, we'll need to discuss this largely with the community.

@dsavary
Copy link
Author

dsavary commented Jun 1, 2017

I tested with QGIS 2.99 3 week ago. The bug is still not fixed.
I talk about invisible feature that are unchecked classes .
The snapping options check only if the layer are checked. Perhaps, it's not a bug, but a new feature request .

@haubourg
Copy link
Contributor

haubourg commented Jun 1, 2017

Ok, this case is probably an issue. Let's raise the issue on the mailing list.

@haubourg
Copy link
Contributor

haubourg commented Jun 1, 2017

@ponceta
Copy link
Member

ponceta commented Jun 12, 2017

About snapping in QGIS 3 QGEP/QGEP#330

@dsavary
Copy link
Author

dsavary commented Jun 21, 2017

For Lausanne, this issue is important. In the priority, it should be fix for QGIS 3.0 , ideally for QGIS 2.18 LTR if it's still possible. I don't understand the use cases where you would snap the new feature to invisible features on the map ...

@haubourg
Copy link
Contributor

ticket created upstream https://issues.qgis.org/issues/16838

My guess is that the whole snapping workflow deserves something consistent.
We have quite a bunch of good issues and feature requests in that area

@haubourg
Copy link
Contributor

haubourg commented Jul 11, 2017

@dsavary backporting a change to 2.18 seems not possible according to @wonder-sk, it's a little bit more than only a bugfix.
@qwat-psc: what is the priority of this issue when compared to all other issues with snapping? I have in mind the following needs:

@ponceta
Copy link
Member

ponceta commented Oct 2, 2017

IMHO, Snapping on invisible features is a feature.

Removing it completely would be wrong. I suggest to set it optionnal in the same way that snapping on intersections is optionnal.

Default could be set to visible only.

@haubourg
Copy link
Contributor

@wonder-sk Hi Martin,
I have 2 days available in the end of 2017 budget to fix that in QGIS 3 or 3.2. Would you be available to work on that?

@haubourg
Copy link
Contributor

haubourg commented Dec 6, 2017

@wonder-sk Hi in case you had some time left, We are out of budget for 2017. Would you be interested in that for 2018 ?

@wonder-sk
Copy link
Collaborator

Sorry for the delayed response... Sure we can do it in 2018 if you are interested in this feature.

@haubourg
Copy link
Contributor

@wonder-sk well, let's keep that in standby that until I get a clearance for the 2018 actions. Any time estimate on that task?

@wonder-sk
Copy link
Collaborator

Cool... My estimate for this is ~2 days

@haubourg haubourg changed the title Snapping on invisible feature [QGIS] Snapping on invisible feature Mar 12, 2018
@haubourg
Copy link
Contributor

We have an external contributor funding that fix. Work starting soon, thanks!

@dsavary
Copy link
Author

dsavary commented Apr 11, 2018

Good news ! planned for QGIS 3.1 (2018) ? I think not for QGIS 2.18 :) ...

@haubourg
Copy link
Contributor

Planned for 3.2.
3.1 is the current master development version.

2.18 was investigated by Martin and needed API changes >> NoGO

@haubourg haubourg added the External funding feature or bugfix funded by someone else label Apr 12, 2018
@haubourg
Copy link
Contributor

@lbartoletti hub cleanup, I assign you to the task you are already working on

@lbartoletti
Copy link
Collaborator

PR Merged qgis/QGIS#6750

@haubourg
Copy link
Contributor

haubourg commented May 2, 2018

Please keep it opened until we have a green light from the testers :)

@lbartoletti
Copy link
Collaborator

Could be closed now?

@lbartoletti
Copy link
Collaborator

The main bug was fixed one year ago. I fixed a related bug for tracing.

FYI, there is a last related bug qgis/QGIS#26733

Do you want me to take care of it?

@haubourg
Copy link
Contributor

Do you want me to take care of it?

are you talking to me? ;-) Please go ahaed and close qgis/QGIS#26733 and #193 if everything is OK:

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

No branches or pull requests

5 participants