<div dir="ltr">great reports in this thread... would make sense to have a best practices page where to store these reports? nothing complex, just nabble links to significant thread or posts. Kind of QGIS practice digest :)<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>Luigi Pirelli<br><br>**************************************************************************************************<br>* LinkedIn: <a href="https://www.linkedin.com/in/luigipirelli" target="_blank">https://www.linkedin.com/in/luigipirelli</a><br>* Stackexchange: <a href="http://gis.stackexchange.com/users/19667/luigi-pirelli" target="_blank">http://gis.stackexchange.com/users/19667/luigi-pirelli</a><br>* GitHub: <a href="https://github.com/luipir" target="_blank">https://github.com/luipir</a><br>* Book: <a href="https://www.packtpub.com/eu/application-development/mastering-geospatial-development-qgis-3x-third-edition" target="_blank">Mastering QGIS3 - 3rd Edition</a></div><div>* Hire a team: <a href="http://www.qcooperative.net" target="_blank">http://www.qcooperative.net</a><br>**************************************************************************************************</div></div></div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 7 Jan 2021 at 12:49, Bo Victor Thomsen <<a href="mailto:bo.victor.thomsen@gmail.com">bo.victor.thomsen@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>As a former (Q)GIS administrator for a Danish municipality with:</p>
<ul>
<li> Ca. 100 QGIS users, some experienced and some total newbies<br>
<br>
</li>
<li>Several hundred different spatial data layers in both
MS-SQLServer, PostgreSQL and some file based formats. <br>
<br>
</li>
<li>Most of the layers read-only but a significant number of
layers editable.<br>
</li>
</ul>
<p>I'll suggest:</p>
<ul>
<li>Don't use WFS for local connections. The added layer of
complexity will make the complete system much slower, more
unstable and more difficult to administer.<br>
<br>
</li>
<li>Use .qlr files to present the individual layers from the
databases for users with symbology and without them having to
use the database connection tabs in the Data Manager.<br>
<br>
</li>
<li>You can save all the different .qlr files in a common network
based directory that can be accessed by all users. And make this
directory a "favourite" directory in the QGIS Data Manager. This
will make data access easy and uniform for every type of data. <br>
<br>
</li>
<li>You can group the .qlr files in logical groups using a
directory structure under the main directory. And give the qlr
files some easily understood names.<br>
<br>
</li>
<li>Use the database access systems to control the individual user
access rights. <br>
<br>
</li>
<li>If you're in a Windows domain based system with windows pc's
and postgres servers running on windows, take a look at the SSPI
access method. This will give you a "Integrated security" like
access to Postgres.<br>
<br>
</li>
</ul>
<pre cols="72">Med venlig hilsen / Kind regards
Bo Victor Thomsen</pre>
<div>Den 06-01-2021 kl. 16:48 skrev Paul
Wittle:<br>
</div>
<blockquote type="cite">
<pre>Hi Alessandro,
I guess the key is ease of data discovery. So if all your geodata is on one database then it is all easy enough but if you have multiple database types / instances then you are relying a lot on users being able to find the right database / instance and then having potentially different login mechanisms for each database.
This is why the idea of WFS seems appealing because we can authenticate at access to the WFS server using a single method; expose all the accessible datasets in a single list and in theory potentially employ greater consistency to the method of updates.
We have found that the SQL issued by each database driver can vary in terms of the SQL optimisation because each one is developed independently of others (i.e. the Oracle data access is not necessary developed with much reference to the Postgres or SQL database data access clients). Whilst fundamentally the SQL statements are still in effect translated into the appropriate SQL for each database type the original statement should in theory be more consistent?
In terms of speed; I suspect you are definitely correct hence my asking the question really.
The comments above are really to simply flesh out the question as to whether or not using a database is really simpler though.
That said; we may also use something like a custom plugin or GeoNetwork as a data discovery tool which is another way of helping users add the right layer without needing to know which database it comes from.
I hope that clarifies the question a little better?
Cheers,
Paul
-----Original Message-----
From: Alessandro Pasotti <a href="mailto:apasotti@gmail.com" target="_blank"><apasotti@gmail.com></a>
Sent: 06 January 2021 15:11
To: Paul Wittle <a href="mailto:P.Wittle@dorsetcc.gov.uk" target="_blank"><P.Wittle@dorsetcc.gov.uk></a>
Cc: <a href="mailto:qgis-user@lists.osgeo.org" target="_blank">qgis-user@lists.osgeo.org</a>
Subject: Re: [Qgis-user] Best practice, database vs WFS
Hi Paul,
if you want to share geodata within your organization on a private network a database is the best solution: faster and simpler. The constraint is that you will need an application (like QGIS) to access your data..
WFS is a web service standard for interoperability, it is ideal for sharing data on the internet over HTTP, there is no need for a particular application to use the service: any HTTP client is able to do that.
Regards
On Wed, Jan 6, 2021 at 3:43 PM Paul Wittle <a href="mailto:paul.wittle@dorsetcouncil.gov.uk" target="_blank"><paul.wittle@dorsetcouncil.gov.uk></a> wrote:
</pre>
<blockquote type="cite">
<pre>Hi,
As I’m sure is clear from the number of posts I’ve done of late we are currently looking at how we use QGIS within our business. I thought I’d ask a question here to see if others are considering it as I can’t find too much chat online about it but I wondered if perhaps there should be some.
We have concluded that in theory the WFS and WFS-T protocols are an OGC standard (<a href="https://www.ogc.org/standards/wfs" target="_blank">https://www.ogc.org/standards/wfs</a>) and that using an OGC compliant server they can be used to front various data source formats; i.e. Postgres, Oracle, SQL Server etc. In theory that means that if you use WFS and WFS-T in QGIS it should mean that user experience becomes more consistent for the people using those layers in QGIS.
That all sounds great, but I can’t seem to even get my WFS to load correctly in QGIS at present and it doesn’t seem to be something that is recommended online. Given that both WFS and direct database access both return full details (vector geometries and attributes) to QGIS; would you expect performance of WFS to be similar or significantly slower?
Is the use of OGC compliant WFS something that you personally feel is something we should be aspiring to use more widely at the local / network level in QGIS or do you favour just loading directly from databases?
I’m honestly very interested to hear what others think on this as theoretically you would think the creation of an OGC standard would have this sort of aspiration but I’m increasingly concluding that this kind of use of WFS is very limited. It seems to me that the most common use case is just for occasional layers where you need to work with others over the internet.
To ensure we are talking about the same thing; I’m thinking that the access to WFS in this context would be locally within your own network or device as clearly going over the internet will add a significant overhead and potential for delay.
Feel free to message me back directly or message the group if you think it is a worthwhile discussion but as I say I’d love to hear what others think.
Cheers,
Paul
This e-mail and any files transmitted with it are intended solely for
the use of the individual or entity to whom they are addressed. It may
contain unclassified but sensitive or protectively marked material and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use
it, or disclose it to anyone else. If you have received this
transmission in error please notify the sender immediately. All
traffic may be subject to recording and/or monitoring in accordance
with relevant legislation. Any views expressed in this message are
those of the individual sender, except where the sender specifies and
with authority, states them to be the views of Dorset Council. Dorset
Council does not accept service of documents by fax or other
electronic means. Virus checking: Whilst all reasonable steps have
been taken to ensure that this electronic communication and its
attachments whether encoded, encrypted or otherwise supplied are free
from computer viruses, Dorset Council accepts no liability in respect
of any loss, cost, damage or expense suffered as a result of accessing
this message or any of its attachments. For information on how Dorset
Council processes your information, please see
<a href="http://www.dorsetcouncil.gov.uk/416433" target="_blank">www.dorsetcouncil.gov.uk/416433</a>
_______________________________________________
Qgis-user mailing list
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
</pre>
</blockquote>
<pre>--
Alessandro Pasotti
QCooperative: <a href="http://www.qcooperative.net" target="_blank">www.qcooperative.net</a>
ItOpen: <a href="http://www.itopen.it" target="_blank">www.itopen.it</a>
This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. It may contain unclassified but sensitive or protectively marked material and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All traffic may be subject to recording and/or monitoring in accordance with relevant legislation. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Dorset Council. Dorset Council does not accept service of documents by fax or other electronic means. Virus checking: Whilst all reasonable steps have been taken to ensure that this electronic communication and its attachments whether encoded, encrypted or otherwise supplied are free from computer viruses, Dorset Council accepts no liability in respect of any loss, cost, damage or expense suffered as a result of accessing this message or any of its attachments. For information on how Dorset Council processes your information, please see <a href="http://www.dorsetcouncil.gov.uk/416433" target="_blank">www.dorsetcouncil.gov.uk/416433</a>
_______________________________________________
Qgis-user mailing list
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
Qgis-user mailing list<br>
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
</blockquote></div>