Hi Yann,
Sharing reference datasets as files in /usr does not sound like a good idea
when you already have a database. I strongly recommend using the database
for this, except for rasters. And yes, offline editing works with
database, except fpr rasters :)
Regards
Régis
Le jeu. 5 déc. 2019 à
Thank you all for your answers.
Alessandro: the resources folder contains only read-only data (reference
rasters or vectors from French national geographic institute, not to be
modified). I deploy these layers on every workstation. Is it still a bad
practice for read-only reference data to
Hi,
In my setup - using PGSERVICES - all vector, raster, styles and projects
are stored on database. This is my preferred way to organize the data:
on a database. QGIS Server also takes advantage of this setup and
publish the projects directly from the database, using the rasters (in
db or out of
Not sure if it is a good idea, but you might find a workaround using a
startup script or plugin containing this functionality:
https://qgis.org/pyqgis/master_temp/core/QgsPathResolver.html
I guess it will be too tricky/hacky but I hope it helps you.
Raymond
On 05-12-2019 12:18, Alessandro
On Thu, Dec 5, 2019 at 11:58 AM Yann Voté wrote:
> Hi all,
>
> I can't find a solution to the following issue, or a way to work around
> it: I have created a project with some PostgreSQL layers to edit and
> some raster layers on local filesystem. I work on a Linux computer and
> have put the
Hi all,
I can't find a solution to the following issue, or a way to work around
it: I have created a project with some PostgreSQL layers to edit and
some raster layers on local filesystem. I work on a Linux computer and
have put the local layers into the pkg data path resources folder
