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

Split v.generalize GRASS module in two #15232

Closed
qgib opened this issue Jun 1, 2012 · 4 comments
Closed

Split v.generalize GRASS module in two #15232

qgib opened this issue Jun 1, 2012 · 4 comments

Comments

@qgib
Copy link
Contributor

qgib commented Jun 1, 2012

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

Redmine category:processing/grass
Assignee: Victor Olaya


See #12818

@qgib
Copy link
Contributor Author

qgib commented Oct 4, 2014

Author Name: Giovanni Manghi (@gioman)


  • category_id removed 59
  • 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/GRASS

@qgib
Copy link
Contributor Author

qgib commented Feb 9, 2016

Author Name: Médéric RIBREUX (Médéric RIBREUX)


Hello,

I've made "a Pull-Request":#2776 for this feature request.
As said, I've chosen to split v.generalize in 4 parts because now in GRASS7, there are 4 different groups of algorithms:

  • simplification
  • smoothing
  • displacement
  • network

The displayed parameters have been limited to parameters that are actually used by the group of algorithm, resulting in a much more easier to use algorithms.

I have made some tests with all the different algorithms and it seems to work without bug.

Feel free to test, review and make comments if needed !


  • status_id was changed from Open to In Progress

@qgib
Copy link
Contributor Author

qgib commented Feb 27, 2016

Author Name: Alexander Bruy (@alexbruy)


Fixed in changeset "1c585a14c88831bb25e2dfe29b8169e07d8b767b".


  • status_id was changed from In Progress to Closed

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

No branches or pull requests

1 participant