Open qgib opened 8 years ago
Author Name: Giovanni Manghi (@gioman)
Author Name: Regis Haubourg (@haubourg)
And I would add :
(and dreaming a bit, add a true topology break step before all algorithms supposing good topology between polygons :) )
Author Name: Ger CO (Ger CO)
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.
Author Name: Regis Haubourg (@haubourg)
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.
Author Name: Ger CO (Ger CO)
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?
Author Name: Giovanni Manghi (@gioman)
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
Author Name: Regis Haubourg (@haubourg)
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 ;)
Author Name: Bernhard Ströbl (Bernhard Ströbl) Original Redmine Issue: 13654
Redmine category:processing/qgis Assignee: Victor Olaya
This ticket lists enhancements to Processing's Dissolve from several tickets. The enhancements should be included in QGIS 3.0.