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

GdalTools: unclear results from clipping #13509

Closed
qgib opened this issue Jan 29, 2011 · 2 comments
Closed

GdalTools: unclear results from clipping #13509

qgib opened this issue Jan 29, 2011 · 2 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Jan 29, 2011

Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 3449

Redmine category:python_plugins
Assignee: Giuseppe Sucameli


Currently, when >1 layer is loaded into the canvas, clipping results are difficult to interpret. The tool attempts to clip all the loaded layers, whereas I guess the user expects only the topmost layer will be clipped.

@qgib
Copy link
Contributor Author

qgib commented Feb 3, 2011

Author Name: Giuseppe Sucameli (@brushtyler)


All the active layers (visible ones) are clipped.
When more then one layer are active the result is the merge of all the active layers clipped by the extent.

In this moment there's an issue because the topmost layer is inserted as the first one in the gdal_merge command, but seeing at the "gdal_merge manpages":http://www.gdal.org/gdal_merge.html, "In areas of overlap, the last image will be copied over earlier ones".

So when there are > 1 layers active, in the result the last layer in the TOC is over the topmost one. I'm going to fix it as soon as possible.


  • status_id was changed from Open to In Progress

@qgib
Copy link
Contributor Author

qgib commented Feb 3, 2011

Author Name: Giuseppe Sucameli (@brushtyler)


Replying to [comment:1 brushtyler]:

So when there are > 1 layers active, in the result the last layer in the TOC is over the topmost one. I'm going to fix it as soon as possible.
Fixed in 6129ea5 (SVN r15126).
I guess I can close this ticket.


  • resolution was configured as fixed
  • status_id was changed from In Progress to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins labels May 24, 2019
@qgib qgib added this to the Version 1.7.0 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! Plugins
Projects
None yet
Development

No branches or pull requests

1 participant