In a previous job, when we didn't use postgres, I would create the template QGS (with all the styles, print layouts & etc ) and generally have the data as ArcGIS Rest Servers, WFS OR a discipline specific gpkg that was only read that once they copied, they could edit. I had this set up for each discipline (geology, water, environment & etc). It meant they were starting with the base project and data and they could do with it as they wanted.
But if you want to build onto the data, I would probably look at Kart <https://kartproject.org/>possibly along with postGIS. Kind regards Em Emma Hain — Product Manager/Senior GIS Analyst e...@north-road.com [image: https://north-road.com] *North Road* Cartography • Development • Spatial Analysis ------------------------------ *north-road.com* <http://north-road.com> <https://twitter.com/northroadgeo> <https://www.linkedin.com/company/north-road-studios> <https://www.facebook.com/North-Road-997236690392419/home> QGIS User Conference 2025 <https://uc2025.qgis.org/> 2-3 June, Norrköping, Sweden FOSS4G 2025 <https://2025.foss4g.org/> 17-23 November, Auckland, New Zealand On Thu, 20 Mar 2025 at 08:25, Tobias Schula via QGIS-User < qgis-user@lists.osgeo.org> wrote: > On Wednesday, 19 March 2025, 23:05:47 CET Greg Troxel via QGIS-User wrote: > > It sounds like > > > > When multiple people are using the same project file, whether via > > pgsql or a shared filesystem, they need to have a plan for performing > > writes to that project file, because there is no mechanism for merges > > or handling conflicts. > > > > is the general statement then. > > This worked for me in the past: > Create a _template_ project with all your styles, database connections, > links, > color ramps, scripts, etc. and hand it out to the users or install it for > them. Then they can all access the same data, have the same styles and so > on, > but their project gets saved on their local machine. This is also a great > fallback, if somebody messes up their project beyond repair. > > Still, it's a bit messy, because file paths might get broken and everyone > has > to re-authenticate with the database. You will also get a lot of warnings > about missing fonts, because until recently, QGIS would default to > different > fonts on windows macos and linux. > > As far as I know, there is no solution for seamless access by everyone, > it's > all quirky. > -- > Tobias A Schula > Forestry Expert > > geospatial@schula.org_______________________________________________ > QGIS-User mailing list > QGIS-User@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user >
_______________________________________________ QGIS-User mailing list QGIS-User@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
