Hi Stefan
Did you try a developer version (e.g. nightly build)? I think my
workaround does solve the problem for most usages. It does not solve the
problem only if you do avoid intersection to background layers and those
layers are not editable.
I would really love to see a propper fix for that and that
digitizing can not silently end up in incorrect results.
Then you might consider contributing to the geos project
(http://trac.osgeo.org/geos/).
Regards,
Marco
Am 19.03.2013 21:11, schrieb SBL:
Hi Bert
I know quite a few people (including me) who ran into the same, pretty
anoying, problem.
And in general it is a known issue. See: http://hub.qgis.org/issues/2921
Did I understand you correctly that you already tried the workaround Marco
suggests at the end of the ticket? This would indicate that activating
topological editing is not enough (at least not in QGIS 1.8)...
Did you also try activating snapping on lines and nodes as well?
From my personal point of view this issue is a mayor obstacle of using QGIS
for digitising (though the digitising functions otherwise are really good
and handy). I would really love to see a propper fix for that and that
digitizing can not silently end up in incorrect results.
At least you could clean your already digitised and incorrect data using
GRASS and the topological vector format there...
Cheers
Stefan
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Polygon-digitalization-tp5040680p5041455.html
Sent from the Quantum GIS - User mailing list archive at Nabble.com.
_______________________________________________
Qgis-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-user
--
Dr. Marco Hugentobler
Sourcepole - Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
[email protected] http://www.sourcepole.ch
Technical Advisor QGIS Project Steering Committee
_______________________________________________
Qgis-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-user
