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

Support GRASS rasters as inputs in Processing #16635

Closed
qgib opened this issue Apr 27, 2013 · 11 comments
Closed

Support GRASS rasters as inputs in Processing #16635

qgib opened this issue Apr 27, 2013 · 11 comments
Labels
Feature Request Feedback Waiting on the submitter for answers Processing Relating to QGIS Processing framework or individual Processing algorithms stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@qgib
Copy link
Contributor

qgib commented Apr 27, 2013

Author Name: Anita Graser (@anitagraser)
Original Redmine Issue: 7727

Redmine category:processing/core
Assignee: Victor Olaya


As reported: http://osgeo-org.1560.x6.nabble.com/Should-it-be-possible-to-use-GRASS-rasters-in-Sextante-td5048075.html

I'm working with QGIS sample data GRASS datset. Loaded the airports and
gtopo30. I can select the airport layer in Sextante dialogs but not
gtopo30.


Related issue(s): #21457 (duplicates)
Redmine related issue(s): 13408


@qgib
Copy link
Contributor Author

qgib commented Apr 28, 2013

Author Name: Victor Olaya (@volaya)


This is a complex issue.

GRASS layers cannot be used in their native format by other apps like SAGA, OTB, etc. They have to be converted. But to convert a layer when its needed, SEXTANTE uses GDAL. GDAL, however, does not support GRASS layers, so the only way of doing it is to load the layer into memory and then write it to a GDAL-supported format. This will not work for large layers.

Finding a solution for all cases doesn't seem to be easy... I would like to think a bit more about this before adding a solutino that will not work in many cases, which will make SEXTANTE unstable in case of using GRASS layers.

Ideas and comments are welcome


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Apr 28, 2013

Author Name: Paolo Cavallini (@pcav)


This is why libgdal1-1.9.0-grass exists

@qgib
Copy link
Contributor Author

qgib commented Jun 19, 2014

Author Name: pvanbosgeo - (pvanbosgeo -)


Any development on this?

@qgib
Copy link
Contributor Author

qgib commented Oct 4, 2014

Author Name: Giovanni Manghi (@gioman)


  • crashes_corrupts_data was configured as 0
  • version was configured as 2.4.0
  • category_id removed 63
  • project_id was changed from 78 to 17

@qgib
Copy link
Contributor Author

qgib commented Oct 4, 2014

Author Name: Giovanni Manghi (@gioman)


  • category_id was configured as Processing/Core

@qgib
Copy link
Contributor Author

qgib commented Oct 12, 2014

Author Name: Giovanni Manghi (@gioman)


  • tracker_id was changed from 1 to 2
  • priority_id was changed from High to Normal
  • subject was changed from Can't use GRASS rasters to Support GRASS rasters as inputs in Processing

@qgib
Copy link
Contributor Author

qgib commented Mar 24, 2015

Author Name: Paolo Cavallini (@pcav)


Apparently, GRASS rasters are supported by GDAL:

gdalinfo --formats | grep -i grass
GRASSASCIIGrid (rov): GRASS ASCII Grid

@qgib
Copy link
Contributor Author

qgib commented Mar 24, 2015

Author Name: Paolo Cavallini (@pcav)


So, it seems that GRASS rasters are simply filtered out. In this case, the fix would be trivial.

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0

@qgib qgib added Feedback Waiting on the submitter for answers Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms labels May 24, 2019
JamesShaeffer pushed a commit to JamesShaeffer/QGIS that referenced this issue Nov 20, 2019
@github-actions
Copy link

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Jul 14, 2021
@github-actions
Copy link

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Feedback Waiting on the submitter for answers Processing Relating to QGIS Processing framework or individual Processing algorithms stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

No branches or pull requests

1 participant