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.

Sign up for GitHub

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

Jump to bottom

GRASS vectors can be used as Processing input, but fail #20607

Closed
qgib opened this issue Mar 24, 2015 · 2 comments
Closed

GRASS vectors can be used as Processing input, but fail #20607

qgib opened this issue Mar 24, 2015 · 2 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms

Comments

@qgib
Copy link
Contributor

qgib commented Mar 24, 2015

Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 12436
Affected QGIS version: 2.8.1
Redmine category:processing/core
Assignee: Victor Olaya

GRASS vectors loaded in canvas are listed as Processing input, and can be used for analyses, but fail. I got two different failures:

  • Split lines with lines: QGIS gets stuck at 100% CPU forever
  • gdalogr:gridinvdist: data cannot be read
    GDAL execution console output
    Unable to open input datasource
    "/home/paolo//grass/PERMANENT/dtm_points/1_point".
@qgib
Copy link
Contributor Author

qgib commented Mar 24, 2015

Author Name: Paolo Cavallini (@pcav)

Either filter out GRASS vectors, so they cannot be used for analyses (not listed), or, far better, add support for them too.

@qgib
Copy link
Contributor Author

qgib commented Jul 2, 2015

Author Name: Victor Olaya (@volaya)

Fixed in changeset "de728743b73541a320f68d087f4402a6d17620f1".

  • status_id was changed from Open to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms labels May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@qgib