<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello Andreas</p>
<p>Thank you very much for your comment. These are definitely things
I did not think about.</p>
<p>Our people are in two separate buildings (in two separate
regions!) but our systems can handle this without problems.</p>
<p>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.</p>
<p>Good material for thought and a test.</p>
<p>Thank you again!</p>
<p>Hernán</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2019-11-20 11:40, Andreas Neumann
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b98f0d80c1c3bdd846569770b091886d@carto.net">
<p>Are those 15 people in the same office/same location or
distributed? If the latter, at how many places are they
distributed?</p>
<p>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.</p>
<p>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).</p>
<p>Otherwise you will have to deal with handling conflicts. That
would require more complicated table setups with versioning and
conflict detection.</p>
<p>Andreas</p>
<p id="reply-intro">On 2019-11-20 11:32, Hernán De Angelis wrote:</p>
<blockquote type="cite">
<div class="pre"><span>I am evaluating setting up a server running PostgreSQL/PostGIS for use</span>
<blockquote type="cite">
<blockquote type="cite"><span>as data sharing/collaborating environment for spatial data. The user</span><br>
<span>group may consist of up to 15 people, mostly using QGIS but one or two</span><br>
<span>may use other software (non OS). Data is almost exclusively of vector</span><br>
<span>type. The use is within a single organization.</span><br>
<br>
<span>I understand some people in this list have experience with this kind of</span><br>
<span>environment and would appreciate if any of you would share any useful</span><br>
<span>experience, challenges, thought or things to watch out for. I understand</span><br>
<span>basic management routines are critical (user management, user rights),</span><br>
<span>as well as a sound backup and update strategy. I also understand that</span><br>
<span>proper data management procedures have to be in place, like rules for</span><br>
<span>table creation and eventual deletion, attribute selection, etc. But what</span><br>
<span>else can go wrong with this kind of setup if not managed properly?</span><br>
<span>Thoughts and experiences welcome!</span></blockquote>
<span>in our experience the solution is pretty straightforward. The only other</span><br>
<span>challenge I'd add is having good bandwidth, otherwise using PostGIS data</span><br>
<span>can be sluggish.</span><br>
<span>All the best.</span></blockquote>
<br>
<span>Excellent point, Paolo! I had not thought about it. Thank you!</span><br>
<br>
<span>All the best</span><br>
<br>
_______________________________________________<br>
<span>Qgis-user mailing list</span><br>
<span><a href="mailto:Qgis-user@lists.osgeo.org"
moz-do-not-send="true">Qgis-user@lists.osgeo.org</a></span><br>
<span>List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
target="_blank" rel="noopener noreferrer"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></span><br>
<span>Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
target="_blank" rel="noopener noreferrer"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></span></div>
</blockquote>
<p><br>
</p>
</blockquote>
</body>
</html>