One IMHO interesting approach would be http://geoshape.org, which combines GeoNode, GeoGig and some additional packages... ________________________________________ Von: Qgis-user [[email protected]] im Auftrag von J.O. Williams [[email protected]] Gesendet: Mittwoch, 20. Dezember 2017 20:14 An: [email protected] Betreff: Re: [Qgis-user] Versioned editing in QGIS
This sounds like Github for GIS. Anybody know how to implement this? J.O. Williams Denver, CO. On 12/20/2017 11:45 AM, Stefan Blumentrath wrote: > Maybe http://geogig.org can be of interest... > ________________________________________ > Von: Qgis-user [[email protected]] im Auftrag von Morten > Storm [[email protected]] > Gesendet: Mittwoch, 20. Dezember 2017 15:28 > An: [email protected] > Betreff: [Qgis-user] Versioned editing in QGIS > > Hi, > > We have quite a few QGIS users, who are used to working in ArcGIS for Desktop > on an Esri Enterprise Geodatabase. These users want to apply versioned > editing as known from ArcGIS. > > Their basic requirements for versioned editing in QGIS can be summarized as > follows: > - Versioned editing is based on data contained in a central multi-user data > repository (database), preferably PostgreSQL/PostGIS. > - The parent version/default version/master version is the "current" dataset > that all ordinary users access for data browsing purposes. > - Editing users should be able to create independent versions (or branches) > of the data set - either in its entirety or for selected layers/tables in the > data set. > - It is not an ultimate requirement that a specific version/branch can be > shared by multiple users. > - But one user must be able to edit, whereafter another user can review, > approve and commit. > - Generally the "parent version/branch" (default version in ArcGIS > terminology) should not be edited, but this need not be prevented by the > versioning solution. > - The individual user chooses which version/branch he/she wants to edit at > the beginning of an editing session. > - At any given time a user should be able to either delete (if edits are to > be dropped again) or commit the version/branch to the parent/default version. > - A complete history of editing or the ability to regret commit of > version/branch is NOT needed. > > Do anyone know of any solutions, that will allow QGIS users to achieve this? > > > Kind regards, > > Morten Storm > > ARTOGIS a/s > Eltangvej 61 > 6000 Kolding > DENMARK > > Phone +45 75 53 73 93 > Direct +45 76 30 82 22 > Mobile +45 51 51 09 29 > > > _______________________________________________ > Qgis-user mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > _______________________________________________ > Qgis-user mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user _______________________________________________ Qgis-user mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user _______________________________________________ Qgis-user mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
