IMHO conflicts should never arise if the workflow is properly designed: two users should never edit the same feature at the same time. you can solve a lot of these issues with table partitioning. cheers
Il 20/11/19 12:08, Hernán De Angelis ha scritto: > Hello Andreas > > Thank you very much for your comment. These are definitely things I did > not think about. > > Our people are in two separate buildings (in two separate regions!) but > our systems can handle this without problems. > > The editing conflicts seem more serious to me. I guess these could be > minimized by encouraging users to save edits more often but, as you > write, a proper solution may require proper versioning. But then that > may likely push up the costs. > > Good material for thought and a test. > > Thank you again! > > Hernán > > > > On 2019-11-20 11:40, Andreas Neumann wrote: >> >> Are those 15 people in the same office/same location or distributed? >> If the latter, at how many places are they distributed? >> >> In my experience, using Postgis sources over the internet (not in the >> LAN) is way too slow. It will only upset your users. In such a >> scenario you would have to set up replication. >> >> Another aspect: avoid editing the same features simultaneously by >> different users. Only the last save will stay. QGIS starts an edit >> session and will only save at the end of the sesssion, when you >> actually save the features. In such a scenario you should assign >> certain geographic areas to different users (e.g. user A edits >> features in municipality x, and user b in municipality y, but not x). >> >> Otherwise you will have to deal with handling conflicts. That would >> require more complicated table setups with versioning and conflict >> detection. >> >> Andreas >> >> On 2019-11-20 11:32, Hernán De Angelis wrote: >> >>> I am evaluating setting up a server running PostgreSQL/PostGIS for use >>>>> as data sharing/collaborating environment for spatial data. The user >>>>> group may consist of up to 15 people, mostly using QGIS but one or two >>>>> may use other software (non OS). Data is almost exclusively of vector >>>>> type. The use is within a single organization. >>>>> >>>>> I understand some people in this list have experience with this kind of >>>>> environment and would appreciate if any of you would share any useful >>>>> experience, challenges, thought or things to watch out for. I understand >>>>> basic management routines are critical (user management, user rights), >>>>> as well as a sound backup and update strategy. I also understand that >>>>> proper data management procedures have to be in place, like rules for >>>>> table creation and eventual deletion, attribute selection, etc. But what >>>>> else can go wrong with this kind of setup if not managed properly? >>>>> Thoughts and experiences welcome! >>>> in our experience the solution is pretty straightforward. The only other >>>> challenge I'd add is having good bandwidth, otherwise using PostGIS data >>>> can be sluggish. >>>> All the best. >>> >>> Excellent point, Paolo! I had not thought about it. Thank you! >>> >>> All the best >>> >>> _______________________________________________ >>> Qgis-user mailing list >>> [email protected] <mailto:[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 > -- Paolo Cavallini - www.faunalia.eu QGIS.ORG Chair: http://planet.qgis.org/planet/user/28/tag/qgis%20board/ _______________________________________________ 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
