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

Add point widget #23899

Closed
qgib opened this issue Dec 14, 2016 · 5 comments
Closed

Add point widget #23899

qgib opened this issue Dec 14, 2016 · 5 comments

Comments

@qgib
Copy link
Contributor

qgib commented Dec 14, 2016

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

Redmine category:processing/grass


Currently, coordinates have to be entered by hand (in some cases with expressions) for several GRASS modules.
It would be much better to use the coordinate capture widget used e.g. for the new road graph commands.
Affected commands are at least:

  • m.cogo
  • r.circle
  • r.cost.coordinates
  • r.drain
  • r.horizon.height
  • r.lake.coords
  • r.plane (split in two fields)
  • r.spreadpath
  • r.viewshed
  • r.walk.coords
  • r.water.outlet
  • r.what.coords

v.* commands still to be checked.

@qgib
Copy link
Contributor Author

qgib commented Dec 15, 2016

Author Name: Saber Razmjooei (@saberraz)


  • category_id was configured as GUI

@qgib
Copy link
Contributor Author

qgib commented Dec 15, 2016

Author Name: Paolo Cavallini (@pcav)


IMHO this has more to do with Processing that with GUI itself.


  • category_id was changed from GUI to Processing/GRASS

@qgib
Copy link
Contributor Author

qgib commented Dec 28, 2016

Author Name: Alexander Bruy (@alexbruy)


Should be fixed in master.


  • resolution was changed from to fixed/implemented
  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Dec 29, 2016

Author Name: Alexander Bruy (@alexbruy)


  • status_id was changed from Feedback to Closed

@qgib
Copy link
Contributor Author

qgib commented Dec 3, 2018

Author Name: Alister Hood (@AlisterH)


For the record, it looks like the implementation is designed to cater just for algorithms requiring coordinates as a single easting,northing pair i.e. it doesn't cater for:

  • r.plane because it takes the input "split in two fields", or
  • r.walk.coords because it can take the coordinates for more than one point.

EDIT - I have no idea why redmine claims I updated the description!


  • description was changed from Currently, coordinates have to be entered by hand (in some cases with expressions) for several GRASS modules.
    It would be much better to use the coordinate capture widget used e.g. for the new road graph commands.
    Affected commands are at least:
  • m.cogo
  • r.circle
  • r.cost.coordinates
  • r.drain
  • r.horizon.height
  • r.lake.coords
  • r.plane (split in two fields)
  • r.spreadpath
  • r.viewshed
  • r.walk.coords
  • r.water.outlet
  • r.what.coords

v.* commands still to be checked. to Currently, coordinates have to be entered by hand (in some cases with expressions) for several GRASS modules.
It would be much better to use the coordinate capture widget used e.g. for the new road graph commands.
Affected commands are at least:

  • m.cogo
  • r.circle
  • r.cost.coordinates
  • r.drain
  • r.horizon.height
  • r.lake.coords
  • r.plane (split in two fields)
  • r.spreadpath
  • r.viewshed
  • r.walk.coords
  • r.water.outlet
  • r.what.coords

v.* commands still to be checked.

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