Hi, So if there is so much interest in having this issue fixed I assume that there would be plenty out there who would fund the fix!
The fix won't happen if noone pays for it - just complaining about this does not help. Get an estimate from some developer (e.g. Sandro Santilli oder Sourcepole) to know how much it would cost to fix. As much as I like GRASS - and it is very good to know that this workaround exists (thanks Stefan for mentioning it!) - I don't think it is reasonable to ask people to go through GRASS to get proper data out of their QGIS digitized data set. Who will take the lead to ask a developer? Andreas Am 14.11.2013 10:40, schrieb Blumentrath, Stefan: > Hi George > > I had a lot of trouble with those issues too, and I would really love to see > them fixed. In other words, I agree with Giovanni that these are pretty > important bugs for many and not really uncommon digitization use-cases and > would support his categorization as blocker... > > However, my current workaround is to ignore the untidiness in the topology at > first and then send the vector dataset through GRASS which is (at least for > not too big datasets) quite convenient using the Sextante/Processing > framework (see also discussion here): > http://osgeo-org.1560.x6.nabble.com/Running-v-clean-on-a-QGIS-vector-layer-Polygon-through-Sextante-td5050418.html > > Cheers > Stefan > > > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
