[Qgis-user] How to force exact/korrekt editing polygon layer, (topological)

[Bernhard Ströbl]

Hi Bernd,

QGIS can prevent gaps/intersections between polygons of the same layer, 
you only have to switch on the options. IMHO QGIS should not always 
prevent this because e.g. users may deliberately leave gaps.

So how can you solve your problem?
1) You could teach your users what the options mean and how to use them 
(I regularly teach my users).
2) You could further prepare a project for them where the snapping 
options are enabled for the layers in question. If you are in PostGIS 
create a new DB user that has full rights on these tables and load the 
layers with this user account, revoke all editing rights from all other 
DB users. Thus your QGIS users can only edit when they use your prepared 
project. Be aware that QGIS stores username and password in the project 
file, but I would not see a problem in this if your users are as dumb as 
you claim :-)
3) If on PostGIS you could enable triggers on insert/update that does 
not accept invalid polygons/overlaps between polygons. No way to prevent 
gaps during editing; gaps must be identified end eliminated afterwards.
(4) I have never tried PostGIS' new topology. Maybe it is worth checking 
it out.

Bernhard

Am 11.01.2017 um 09:24 schrieb Bernd Laskowski:
> Hi Jürgen, what about dumbest assumable user <DAU> or lusers?
>
> Thanks a lot Harrissou
> but I know the standard options to use topological editing funktions.
> I have problems with foolish users. They forget to activat topological
> editing or snap-option and so on.
> We need a solution to prevent saving intersections or/and holes/gaps
> within qgis or postgis.
>
> Regards
> Bernd
>
>
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
>



__________ Information from ESET Mail Security, version of virus signature database 14749 (20170111) __________

The message was checked by ESET Mail Security.
http://www.eset.com