Yeah, I remember that as well. But the boundless project page redirects here: https://github.com/locationtech/geogig and there is still some recent activity, so maybe it's not completely dead?
Matthias On 07/20/2015 01:28 PM, Neumann, Andreas wrote: > > Hi, > > As far as I know, the geogit project was canceled by Boundless. They > did not see enough customer demand to finish it. > > It is a pity, as the project was relatively close to completion. > > Andreas > > On 2015-07-20 13:05, Matthias Kuhn wrote: > >> Hi, >> >> I remember geogig (formerly geogit) offers promising concepts for >> filebased spatial data management with historization and branching. >> Unfortunately I don't know the current status of the project and the >> progress of integration in QGIS. >> >> Matthias >> >> On 07/20/2015 11:25 AM, Neumann, Andreas wrote: >>> >>> Hi Didier, >>> >>> I don't think that anyone is working on a client-side historisation >>> option in QGIS. And there wasn't much demand for that in the past, >>> since most serious GIS data resides in databases. >>> >>> Andreas >>> >>> On 2015-07-20 09:45, didier peeters wrote: >>> >>> Hello Andreas, >>> >>> yes it's for some 'historisation', more precisely to make a >>> filiation, and yes I certainly will use triggers in PostGIS. >>> But I wanted to avoid confusion between different kind of >>> edition operations that I'm not currently foreseeing; I'm not >>> sure it will always be easy to distinct this specific action >>> from others. And I thought that it might also be interesting >>> outside of the database world, to have that "edit and preserve" >>> operation. >>> >>> Didier >>> >>> Le 20 juil. 2015 à 09:10, Neumann, Andreas >>> <[email protected] <mailto:[email protected]>> a écrit : >>> >>> Hi Didier, >>> >>> Is this for historisation purposes? If yes, I would look >>> into database solutions to do historization. >>> >>> The SQL-MM standard has this as a built-in tool set for >>> databases, however, PostgreSQL does not implement this part >>> of the SQL specification (I believe the latest versions of >>> SQL server and Oracle 12 does). However, you can simulate >>> the same in Postgis, using triggers and rules. >>> >>> Andreas >>> >>> On 2015-07-20 08:00, didier peeters wrote: >>> >>> Hello, >>> >>> I would like to find the best solution to the following >>> case: >>> >>> in QGis, when editing a polygon (splitting it in 2 >>> parts) I need to save the original shape, in order to >>> keep the different steps of its evolution; this >>> operation is likely to be repeated several times. The >>> solution I found is to >>> >>> * start by copying the polygon, >>> * then edit it (split) >>> * then pasting back the original one, >>> * then adjust and update the attributes of the 2 new >>> polygons. >>> >>> >>> Is there a less tricky way to achieve this ? >>> >>> If not it would be nice to have an option in the save >>> dialog (with a default behaviour set in the Settings), >>> and I would file a feature request. >>> >>> Didier >>> >>> _______________________________________________ >>> Qgis-user mailing list >>> [email protected] <mailto:[email protected]> >>> http://lists.osgeo.org/mailman/listinfo/qgis-user >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Qgis-user mailing list >>> [email protected] <mailto:[email protected]> >>> http://lists.osgeo.org/mailman/listinfo/qgis-user >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Qgis-user mailing list >>> [email protected] >>> http://lists.osgeo.org/mailman/listinfo/qgis-user > > > >
_______________________________________________ Qgis-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-user
