Are we planning to have in QGIS implementation of Versioning like Esri?

There is a general need for the the implementation where QGIS is used for planning and planned design in utility can be cancelled. So in a given area two user can plan and edit the existing features. If one job is cancelled, then edits don't be that job is cancelled.

Both users don't see each other work until finalised.

  • Please remember from the Tour that one question per question works best here. Your two major requirements are best researched/asked about separately. – PolyGeo Nov 13 '14 at 9:52
  • Responding to the "or something else" bit, you might find github automatic mapping and diffing of geojson useful github.com/blog/1772-diffable-more-customizable-maps. Also GeoGig, geogig.org – matt wilkie Nov 14 '14 at 11:38
  • Note that the multi-file format of shapefiles can cause issues if multiple users edit a shapefile that is stored/shared a service such as dropbox. When a shapefile is edited, the filesharing service may create a copy of only some components of the shapefile. Or it may associate one user's copy of the .shp component with another user's copy of the .dbf component. This can lead to attributes being associated with the wrong features. – csk Feb 12 '18 at 18:29

Geogig (http://geogig.org/) can do geospatial data versioning. If different users modify the same feature, it can get tricky, but merging and versioning distributed editing is easy. Geogig works on shapefiles, postGIS databases, and a few other data formats. They're working on a QGIS plugin, but I haven't seen any updates on that in a few months.

| improve this answer | |

Yes, https://plugins.qgis.org/plugins/FastVersion/

Is a Qgis plugin that integrates with Postgres-Postgis database and allows versioning, user security administration and project management.

I was trained 18 years ago on SmallWorld GIS. At that time Smallworld had a database technology with versioning capability called VMDS (Version Managed Data Store) and was unique at that time. Versioning, allows multiple revisions of the data without duplicating all the data, or requiring different databases to be created. As data Versioning showed to be very important, other vendors like ESRI-Arcgis implemented their own versioning system, with some similarities and differences. But to be concise: The concept of Version is analogous to the concept that has of drawing in a plane of paper. The creation of a version is analogous to the process of making a photocopy of the parent version. But once the photocopy is created the modifications in the original are NOT transferred to the copy and vice versa. The only way to transfer the changes between two different versions, is through the "POST" function. In the case of SmallWorld, it also has a “MERGE” function to transfer the changes between two different versions.

| improve this answer | |

A lightweight way would be to use git with qgis projects. See this writeup.

| improve this answer | |
  • Git and Mercurial are used for source code version control . They are distributed version control systems. There are other version control systems that are client-server(centralized), like StarTeam. Both centralized and distributed systems have their own pro and cons. Centralized: Pros: Simple BackUp, user security control, crash recovery, simplicity. Cons: Every client must be connected to the server. Distributed: Pros: Clients can work without the need to be connected to any kind of server. Cons: Difficult BackUp, user security control, crash recovery. – Alfredo Garcia Apr 13 '18 at 19:43
  • Table Structured data : ... When you have Database that has tables(layers) and a model (for simplicity supposing that it does not change) those code version control like Git, Mercurial , etc. are not suitable. Gis Data versioning like SmallWorld VMDS(Version Managed Data Store) is a total different animal from Git or Mercurial. en.wikipedia.org/wiki/VMDS – Alfredo Garcia Apr 13 '18 at 19:43
  • What SmallWorld VMDS(Version Managed Data Store) can do easily, it will take months to do it in Git, because VMDS managed the versioning of the model and the object data version. Something similar does ArcGis versioning system. People are confounded and trying to use source code version control for table structured data. – Alfredo Garcia Apr 13 '18 at 19:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.