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

When drawing a new polygon it inverts existing parts of the polygon #14389

Closed
qgib opened this issue Oct 29, 2011 · 14 comments
Closed

When drawing a new polygon it inverts existing parts of the polygon #14389

qgib opened this issue Oct 29, 2011 · 14 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality

Comments

@qgib
Copy link
Contributor

qgib commented Oct 29, 2011

Author Name: Gerhardus Geldenhuis (@ggeldenhuis)
Original Redmine Issue: 4462
Affected QGIS version: master
Redmine category:digitising


When you draw a new polygon it inverts already drawn parts of the polygon back to the layer underneath. I would have expected an doubling in colour or half the transparency of the red layer of the polygon. The encircled area in the attached image should be a darker colour rather than inverted.


@qgib
Copy link
Contributor Author

qgib commented Oct 29, 2011

Author Name: Giovanni Manghi (@gioman)


can't see any attached image. It would be useful to understand better what do you mean.

@qgib
Copy link
Contributor Author

qgib commented Oct 29, 2011

Author Name: Gerhardus Geldenhuis (@ggeldenhuis)


Apologies must have missed off the image. Hope it helps to clarify what I mean.


  • 3509 was configured as Screenshot01.png

@qgib
Copy link
Contributor Author

qgib commented Oct 30, 2011

Author Name: Giovanni Manghi (@gioman)


The overlapped part it hasn't a "reverted color" it is (it becomes) a hole. The simple features model does not allow to draw such geometries (self-overlapping), and QGIS let you know by marking those two nodes with a green "X".

I agree with others that eventually allow to draw such wrong geometries it is not right. An option that can be eventually be discussed/added could be the one to make qgis refuse to add invalid geometries.


  • category_id was changed from GUI to Digitising
  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Oct 30, 2011

Author Name: Gerhardus Geldenhuis (@ggeldenhuis)


I should have been clearer. The screenshot is in mid-edit so the edit is not finished. I would certainly agree that you should not be allowed to make "wrong" geometries. What I am suggesting is that when you are digitizing a complex shape it would be useful when you overlap the existing polygon to not become a "hole" but rather double in colour density. That would be more intuitive. I am not suggesting the ability to draw wrong shapes but suggesting a more intuitive way for the polygon "shadow" or whatever the correct terminology is to behave in a more real life physical way. I equate the to folding a piece of semi transparent film over it self, it will darken in colour every time you fold it.

@qgib
Copy link
Contributor Author

qgib commented Oct 30, 2011

Author Name: Giovanni Manghi (@gioman)


Gerhardus Geldenhuis wrote:

I should have been clearer. The screenshot is in mid-edit so the edit is not finished. I would certainly agree that you should not be allowed to make "wrong" geometries. What I am suggesting is that when you are digitizing a complex shape it would be useful when you overlap the existing polygon to not become a "hole" but rather double in colour density. That would be more intuitive. I am not suggesting the ability to draw wrong shapes but suggesting a more intuitive way for the polygon "shadow" or whatever the correct terminology is to behave in a more real life physical way. I equate the to folding a piece of semi transparent film over it self, it will darken in colour every time you fold it.

ok, now is clearer, but the doubt remains, why do so if at the end that area will become an hole anyway?

@qgib
Copy link
Contributor Author

qgib commented Oct 30, 2011

Author Name: Gerhardus Geldenhuis (@ggeldenhuis)


I will explain with an example the first image is midway through editing and the second image is the result. It is per illustration only. However I realize while creating these images that there is a logic problem... I don't think what I am asking is doable anyway... I am expecting the computer to know what I want to do and it can't possibly do that...


  • 3513 was configured as Screenshot-1.png
  • 3512 was configured as Screenshot.png

@qgib
Copy link
Contributor Author

qgib commented Oct 30, 2011

Author Name: Giovanni Manghi (@gioman)


Gerhardus Geldenhuis wrote:

I will explain with an example the first image is midway through editing and the second image is the result. It is per illustration only. However I realize while creating these images that there is a logic problem... I don't think what I am asking is doable anyway... I am expecting the computer to know what I want to do and it can't possibly do that...

I understand your point, but as you say, what the program can do for it?

Any evidence that other sw packages (gvsig, udig, kosmo, etc.) do work in a way that can be considered better than the qgis way?

@qgib
Copy link
Contributor Author

qgib commented Oct 30, 2011

Author Name: Gerhardus Geldenhuis (@ggeldenhuis)


I have not used any of the other software packages mentioned so would unfortunetly have no idea. On the whole so far I have really liked the experience in QGIS

@qgib
Copy link
Contributor Author

qgib commented Oct 30, 2011

Author Name: Giovanni Manghi (@gioman)


Gerhardus Geldenhuis wrote:

I have not used any of the other software packages mentioned so would unfortunetly have no idea. On the whole so far I have really liked the experience in QGIS

at the next developer meeting I will try to have a chat with the devs about this matters (in general how overlapping polygons are handled).

@qgib
Copy link
Contributor Author

qgib commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was configured as Version 1.7.4

@qgib
Copy link
Contributor Author

qgib commented Apr 16, 2012

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was changed from Version 1.7.4 to Version 1.8.0
  • version was configured as master
  • crashes_corrupts_data was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2012

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was changed from Version 1.8.0 to Version 2.0.0

@qgib
Copy link
Contributor Author

qgib commented Jun 28, 2014

Author Name: Jürgen Fischer (@jef-n)


  • fixed_version_id was changed from Version 2.0.0 to Future Release - Lower Priority

@qgib
Copy link
Contributor Author

qgib commented Oct 11, 2014

Author Name: Giovanni Manghi (@gioman)


  • status_id was changed from Feedback to Closed
  • resolution was changed from to wontfix

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality labels May 24, 2019
@qgib qgib added this to the Future Release - Lower Priority milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality
Projects
None yet
Development

No branches or pull requests

1 participant