Feature request #13654
Enhancements to Dissolve
| Status: | Open | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: |  Victor Olaya | ||
| Category: | Processing/QGIS | ||
| Pull Request or Patch supplied: | No | Resolution: | |
| Easy fix?: | No | Copied to github as #: | 21689 |
Description
History
#1
Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
#2
Updated by Regis Haubourg over 7 years ago
- Description updated (diff)
And I would add :
- implicit topology cleaning using snap2grid + tolerance parameter to reduce the number of Geos errors for incorrect topologies border relations
(and dreaming a bit, add a true topology break step before all algorithms supposing good topology between polygons :) )
#3
Updated by Ger CO over 7 years ago
Please address the issue, that currently all fields (not just the fields used as dissolve fields) are maintained. This is very confusing since we do not know whcih values of non-dissolve fields are maintained.
#4
Updated by Regis Haubourg over 7 years ago
Ger CO wrote:
Please address the issue, that currently all fields (not just the fields used as dissolve fields) are maintained. This is very confusing since we do not know whcih values of non-dissolve fields are maintained.
Hi Ger CO, please consider supporting that work, making a roadmap is a thing, implementing it another.
#5
Updated by Ger CO over 7 years ago
Regis Haubourg wrote:
Ger CO wrote:
Please address the issue, that currently all fields (not just the fields used as dissolve fields) are maintained. This is very confusing since we do not know whcih values of non-dissolve fields are maintained.
Hi Ger CO, please consider supporting that work, making a roadmap is a thing, implementing it another.
Hi Regis,
i understand that implementing is way harder than asking for changes. I have no profound programming background but am willing to dive deeper into that.
Can you tell me how to get started?
#6
Updated by Giovanni Manghi over 7 years ago
Ger CO wrote:
Regis Haubourg wrote:
Ger CO wrote:
Please address the issue, that currently all fields (not just the fields used as dissolve fields) are maintained. This is very confusing since we do not know whcih values of non-dissolve fields are maintained.
Hi Ger CO, please consider supporting that work, making a roadmap is a thing, implementing it another.
Hi Regis,
i understand that implementing is way harder than asking for changes. I have no profound programming background but am willing to dive deeper into that.
Can you tell me how to get started?
http://docs.qgis.org/2.18/en/docs/pyqgis_developer_cookbook/index.html
or if you or your organization don't want to become direct contributors
http://qgis.org/en/site/forusers/commercial_support.html#qgis-commercial-support
#7
Updated by Regis Haubourg over 7 years ago
Hi Regis,
i understand that implementing is way harder than asking for changes. I have no profound programming background but am willing to dive deeper into that.
Can you tell me how to get started?
here is a good start too: https://www.qgis.org/en/site/getinvolved/index.html
By myself I don't code, but I try to help in bugtracker work (far away from Giovanni commitment), long term feature requirements (QEP's) discussions, sometimes translation or documentation. My main work was to find a way to support qgis with fundings at my previous work, and this is a very efficient way. Companies involved are available almost everywhere, and small clear tasks, well identified upstream in tracker or lists are very often not so expensive. Each point of view is valuable in any part of the QGIS (OSGEO in fact) ecosystem. And contributing in one place also sometimes helps having things done in another place ;)