{"id":14777,"date":"2025-07-28T10:00:00","date_gmt":"2025-07-28T08:00:00","guid":{"rendered":"https:\/\/www.sigterritoires.fr\/?p=14777"},"modified":"2025-07-26T11:55:36","modified_gmt":"2025-07-26T09:55:36","slug":"building-a-consistent-reusable-qgis-environment-bookmarks-project-templates-and-automation","status":"publish","type":"post","link":"https:\/\/www.sigterritoires.fr\/index.php\/en\/building-a-consistent-reusable-qgis-environment-bookmarks-project-templates-and-automation\/","title":{"rendered":"Building a consistent, reusable QGIS environment: bookmarks, project templates and automation"},"content":{"rendered":"\n

In our previous article, we discovered how the Layer Menu from Project plugin enables you to quickly add layers to a project in progress. Today, we’re extending this logic to build a modular, reusable and professional QGIS environment, whether you’re a freelancer, a trainer or a member of a GIS team.<\/p>\n\n\n\n

The aim: to work faster and more rigorously, while facilitating transmission and collaboration.<\/p>\n\n\n\n

\n\n\n\n\n\n\n

\n\n\n\n

\n

\n

Contenu <\/p>\nToggle<\/span>

The 4 basic bricks<\/a><\/li>

Organize your QGIS favorites<\/a>

Sharing QGIS favorites: where are they stored and how to share them<\/a>

Going further: creating a custom QGIS profile for a reusable work environment<\/a>

To go further…<\/a>

Tracking changes: integrating your QGIS projects into a version control system<\/a>

Next article<\/a><\/li><\/ul><\/nav><\/div>\n

<\/span>The 4 basic bricks<\/span><\/h2>\n\n\n\n

Here are the native or complementary tools we will be combining:<\/p>\n\n\n\n

Tool<\/th> Usage<\/th><\/tr><\/thead>

QGIS favorites<\/strong><\/td> Quick access to GIS folders and files<\/td><\/tr>

QGIS project templates<\/strong><\/td> Standardized starting point for new projects<\/td><\/tr>

Layer Menu from Project<\/strong><\/td> Dynamic import of layers or groups<\/td><\/tr>

PyQGIS scripts<\/strong><\/td>

Automate recurring actions (loading, configuration)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

<\/span>Organize your QGIS favorites<\/span><\/h2>\n\n\n\n

Favorites are visible in the QGIS browser (left panel). They allow you to:<\/p>\n\n\n\n

quickly access your data folders<\/li>\n\n\n\n
point to files or databases that are used regularly<\/li>\n\n\n\n

share a clear working tree with a team<\/li>\n<\/ul>\n\n\n\n

Right-click on a folder > Add to favorites<\/strong>
Rename it for clarity (Municipal data, Base maps, etc.)<\/p>\n\n\n\n

Favorites are saved in the QGIS user profile. To share them with others, you can export\/import the configuration file.<\/p>\n\n\n\n

\n\n\n\n
<\/span>Sharing QGIS favorites: where are they stored and how to share them<\/span><\/h3>\n\n\n\n
Favorites in QGIS (in the file explorer, left column) provide quick access to frequently used folders. They are specific to each user profile and stored locally on the computer.<\/p>\n\n\n\n
<\/span>Location of favorites<\/span><\/h4>\n\n\n\n
Favorites are saved in the user profile folder, in a text file named:<\/p>\n\n\n\n
favorites.xml\n<\/code><\/pre>\n\n\n\n<\/span>Typical path:<\/span><\/h4>\n\n\n\n\nIn Windows: C:\\Users\\<NomUtilisateur>\\AppData\\Roaming\\QGIS\\QGIS3\\profiles\\default\\favorites.xml<\/code><\/li>\n\n\n\n In Linux: ~\/.local\/share\/QGIS\/QGIS3\/profiles\/default\/favorites.xml<\/code><\/li>\n<\/ul>\n\n\n\n<\/span>Sharing your favorites with other users<\/span><\/h4>\n\n\n\nTo share your favorites with others:<\/p>\n\n\n\n \nExport the favorites.xml file<\/li>\n\n\n\n Copy it to the other user’s QGIS profile folder (replacing the existing file or merging the paths)<\/li>\n\n\n\n Restart QGIS for the favorites to be updated<\/li>\n<\/ul>\n\n\n\nWarning<\/strong>: this method replaces existing favorites. For a more refined approach (adding, not replacing), it is preferable to open the file in an editor and copy and paste the desired tags.<\/p>\n\n\n\n <\/span>Going further: creating a custom QGIS profile for a reusable work environment<\/span><\/h3>\n\n\n\nQGIS allows you to create multiple user profiles. Each profile contains an independent configuration:<\/p>\n\n\n\n \nFavorites<\/li>\n\n\n\n Installed extensions<\/li>\n\n\n\n Custom styles<\/li>\n\n\n\n Project templates<\/li>\n\n\n\n Keyboard shortcuts<\/li>\n\n\n\n Database connections<\/li>\n\n\n\n Global variables<\/li>\n\n\n\n Python scripts (macros, custom expressions, etc.)<\/li>\n<\/ul>\n\n\n\nThis allows you to create a consistent and portable QGIS environment for a team, project, or specific task.<\/p>\n\n\n\n <\/span>Create a new profile<\/span><\/h4>\n\n\n\n\nIn QGIS, go to: Settings menu > User Profiles > Manage Profiles<\/li>\n\n\n\n Click on \u201cNew Profile\u201d and give it a descriptive name (e.g., waste_project, GIS_training, community_profile).<\/li>\n\n\n\n QGIS will restart with a blank environment that you can customize as you wish.<\/li>\n<\/ol>\n\n\n\n<\/span>Distribute a profile to other workstations<\/span><\/h4>\n\n\n\nOnce the profile has been configured:<\/p>\n\n\n\n \nClose QGIS<\/li>\n\n\n\n Copy the profile folder from: Windows: C:\\Users\\<UserName>\\AppData\\Roaming\\QGIS\\QGIS3\\profiles\\<profile_name> Linux: ~\/.local\/share\/QGIS\/QGIS3\/profiles\/<profile_name><\/li>\n\n\n\n Paste this folder into the equivalent directory on another computer.<\/li>\n\n\n\n Restart QGIS and select this profile via Settings > User Profiles.<\/li>\n<\/ol>\n\n\n\nTip: You can create a \u201cbase profile\u201d containing favorites, extensions, styles, project templates, etc., and distribute it to an entire team or for training sessions.<\/p>\n\n\n\n <\/span>2. Create QGIS project templates<\/span><\/h2>\n\n\n\nA project template is a .qgz file that serves as the basis for any new project.<\/p>\n\n\n\n Steps:<\/p>\n\n\n\n \nCreate a project with:\n\na base map<\/li>\n\n\n\n empty groups named (Source Data, Results, Annotations)<\/li>\n\n\n\n default symbology<\/li>\n\n\n\n standard layouts (legend, scale, title, etc.)<\/li>\n<\/ul>\n<\/li>\n\n\n\n Save it in a dedicated folder (e.g., C:\\QGIS\\Templates)<\/li>\n\n\n\n In QGIS, go to Preferences > Options > System \u27a4 Set this folder as the project template directory<\/li>\n<\/ol>\n\n\n\nResult: you can create new projects from this template via File > New from Template.<\/p>\n\n\n\n \n\n\n\n<\/span>3. Combine with Layer Menu from Project<\/span><\/h2>\n\n\n\nThen use Layer Menu from Project to enrich your model projects as needed:<\/p>\n\n\n\n \nOn-demand base data<\/li>\n\n\n\n Business modules (cadastre, environment, tourism, etc.)<\/li>\n\n\n\n Styles and external georeferenced layers<\/li>\n<\/ul>\n\n\n\nYou can create multiple .qgz sources, each corresponding to a theme or dataset, and make them accessible in all projects.<\/p>\n\n\n\n <\/span>4. Add automation with PyQGIS<\/span><\/h2>\n\n\n\nTo go even further, you can automate certain tasks:<\/p>\n\n\n\n Examples:<\/p>\n\n\n\n # Automatically add a group and load a PostGIS<\/a> layer<\/code><\/pre>\n\n\n\nlayer = QgsVectorLayer(\u201cdbname=\u2018sig\u2019 table=\u2018zones_inondables\u2019\u201d, \u201cFlood zones\u201d, \u201cpostgres\u201d)<\/code><\/pre>\n\n\n\nif layer.isValid():<\/code><\/pre>\n\n\n\nQgsProject.instance().addMapLayer(layer, False)<\/code><\/pre>\n\n\n\nroot = QgsProject.instance().layerTreeRoot()<\/code><\/pre>\n\n\n\ngroup = root.addGroup(\u201cRisk\u201d)<\/code><\/pre>\n\n\n\ngroup.insertChildNode(0, QgsLayerTreeLayer(layer))<\/code><\/pre>\n\n\n\n\nAutomatically load layers at startup<\/li>\n\n\n\n Apply symbology<\/li>\n\n\n\n Fill fields by expression<\/li>\n\n\n\n Generate a custom PDF layout<\/li>\n<\/ul>\n\n\n\nYou can also trigger these scripts when opening a project via the project properties > Python Actions.<\/p>\n\n\n\n \n\n\n\n<\/span>Summary: your modular QGIS toolbox<\/span><\/h2>\n\n\n\nElement<\/th> Role<\/th> Reusable?<\/th> Shareable?<\/th><\/tr><\/thead> QGIS favorites<\/td> Quick access to folders<\/td> \u2705<\/td> \u26a0\ufe0fmanually<\/td><\/tr> Model project<\/td> Consistent starting point<\/td> \u2705<\/td> \u2705<\/td><\/tr> Plugin Layer Menu<\/td> Ready-to-use layer modules<\/td> \u2705<\/td> \u2705<\/td><\/tr> PyQGIS<\/td> Automated tasks<\/td> \u2705<\/td> \u2705<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n \n\n\n\n<\/span>To go further…<\/span><\/h2>\n\n\n\n\nCreate a shared team environment (with Dropbox, Nextcloud, or Git) containing:\n\nA Models_QGIS\/ folder<\/li>\n\n\n\n A Projects_source\/ folder for Layer Menu<\/li>\n\n\n\n A Scripts\/ folder<\/li>\n<\/ul>\n<\/li>\n\n\n\n Integrate your projects into a version control system to track changes<\/li>\n<\/ul>\n\n\n\n<\/span>Tracking changes: integrating your QGIS projects into a version control system<\/span><\/h3>\n\n\n\nWhen working on a QGIS project with others, or when you want to keep a clear history of changes, using a version control system such as Git becomes a real asset.<\/p>\n\n\n\n <\/span>Why version your QGIS projects?<\/span><\/h4>\n\n\n\nA .qgz or .qgs file contains:<\/p>\n\n\n\n \nthe layer structure<\/li>\n\n\n\n styles<\/li>\n\n\n\n filters and SQL queries<\/li>\n\n\n\n layouts<\/li>\n\n\n\n dynamic expressions<\/li>\n\n\n\n links to data<\/li>\n<\/ul>\n\n\n\nAll this information is stored as text (XML) in the .qgs file contained in a .qgz file. This means that Git can:<\/p>\n\n\n\n \ndetect changes line by line<\/li>\n\n\n\n keep a history of changes<\/li>\n\n\n\n allow you to revert to a previous version<\/li>\n\n\n\n facilitate collaborative work by merging contributions from multiple users<\/li>\n<\/ul>\n\n\n\n<\/span>Practical recommendations<\/span><\/h4>\n\n\n\n\nWork with .qgs files rather than .qgz files, so that you can read and version the file directly (.qgz is a compressed archive). Project menu > Project properties > General: check \u201cSave as .qgs file instead of .qgz.\u201d<\/li>\n\n\n\n Organize your working directory with a clear structure:<\/li>\n<\/ul>\n\n\n<\/div> <\/div><\/div><\/div><\/p>\n\n\n\n\/projet_qgis\/\n\u251c\u2500\u2500 data\/ # donn\u00e9es (id\u00e9alement stables ou en lecture seule)\n\u251c\u2500\u2500 styles\/ # SVG, palettes, ressources graphiques\n\u251c\u2500\u2500 projets\/\n\u2502 \u2514\u2500\u2500 carte_dechets.qgs\n\u2514\u2500\u2500 docs\/ # documents, rapports, notes\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n \nInitialize a Git repository at the root of the project:<\/li>\n<\/ul>\n\n\n<\/div> <\/div><\/div><\/div><\/p>\n\n\n\ngit init\ngit add projets\/carte_dechets.qgs\ngit commit -m \"Version initiale du projet QGIS\"\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n \nCommit regularly after each significant change (adding a layer, new layout, style change, etc.).<\/li>\n<\/ul>\n\n\n\n<\/span>Collaborative best practices<\/span><\/h4>\n\n\n\n\nWork on branches to test alternatives or thematic versions of the map.<\/li>\n\n\n\n Use clear commit comments: \u201cAdded A3 layout with dynamic legend,\u201d \u201cChanged plastic waste style.\u201d<\/li>\n\n\n\n Synchronize your repository via GitHub, GitLab, Bitbucket, or an internal server if the project is confidential.<\/li>\n<\/ul>\n\n\n\n<\/span>Limitations and precautions<\/span><\/h4>\n\n\n\n\nDo not version large binary files (e.g., geopackages, rasters, MBTiles<\/a>): store them elsewhere or in a separate data repository.<\/li>\n\n\n\n Do not edit a .qgs project simultaneously with others without coordination: Git does not always handle complex XML conflicts well.<\/li>\n<\/ul>\n\n\n\n \n\n\n\nTip: You can combine Git and a QGIS project template to quickly deploy a standardized configuration while maintaining complete traceability of changes.<\/p>\n\n\n\n<\/span>Example of a versioned structure<\/span><\/h3>\n\n\n\nTo facilitate collaboration and ensure reproducibility, it is useful to structure your QGIS projects in a tree structure suitable for versioning. Here is an example of an organization that you can reuse:<\/p>\n\n\n\n\nprojects\/: QGIS .qgz or .qgs files (main version, variants)<\/li>\n\n\n\n styles\/: QML files defining map styles<\/li>\n\n\n\n sample_data\/: sample or test dataset<\/li>\n\n\n\n scripts\/: Python or bash automation scripts (imports, processing)<\/li>\n\n\n\ndocs\/: user or technical documentation (e.g., getting started guide)<\/li>\n<\/ul>\n\n\n<\/div> <\/div><\/div><\/div><\/p>\n\n\n\nqgis-modele-projet\/\n\u2502\n\u251c\u2500\u2500 projets\/ \u2190 Projets QGIS (.qgs lisible dans Git)\n\u2502 \u2514\u2500\u2500 base_modele.qgs \u2190 Projet mod\u00e8le de d\u00e9part\n\u2502\n\u251c\u2500\u2500 styles\/ \u2190 SVG, palettes, styles SLD ou QML\n\u2502 \u2514\u2500\u2500 plages_dechets.qml\n\u2502\n\u251c\u2500\u2500 sample_data\/ \u2190 Jeu de donn\u00e9es l\u00e9ger pour test\/d\u00e9mo\n\u2502 \u2514\u2500\u2500 plages_sample.gpkg\n\u2502\n\u251c\u2500\u2500 scripts\/ \u2190 Scripts Python QGIS ou Shell\n\u2502 \u2514\u2500\u2500 init_qgis_env.py\n\u2502\n\u251c\u2500\u2500 docs\/ \u2190 Documentation utilisateur ou interne\n\u2502 \u2514\u2500\u2500 guide_utilisation.md\n\u2502\n\u251c\u2500\u2500 .gitignore \u2190 Fichier d\u2019exclusion (fourni ci-dessous)\n\u251c\u2500\u2500 README.md \u2190 Pr\u00e9sentation du projet (\u00e0 personnaliser)\n\u2514\u2500\u2500 LICENSE \u2190 Licence libre (MIT, CC, etc.)\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n A .gitignore file allows you to exclude temporary files or files specific to each machine.<\/p>\n\n\n <\/div> .gitignore<\/div><\/div><\/div><\/p>\n\n\n\n# Donn\u00e9es volumineuses ou brutes (d\u00e9plac\u00e9es dans sample_data si besoin)\ndata\/\n*.gpkg\n*.tif\n*.csv\n*.mbtiles\n*.zip\n\n# Fichiers temporaires ou syst\u00e8me\n*.qgz\n*.aux.xml\n*.lock\n*.bak\n*.tmp\n*.DS_Store\nThumbs.db\n\n# Layouts ou rendus\n*.pdf\n*.svg\n*.png\n*.jpg\n\n# Caches et environnements virtuels\n.qgis2\/\n.qgis3\/\n__pycache__\/\nvenv\/\n\n# Logs et sauvegardes\n*.log\n*autosave*\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n You can initialize a local Git repository, or host this template on a platform such as GitHub, GitLab, or Bitbucket to share it with your team.<\/p>\n\n\n\n Download a ready-to-use example:<\/p>\n\n\n\n qgis-modele-projet.zip<\/a><\/p>\n\n\n\n \n\n\n\n<\/span>Next article<\/span><\/h2>\n\n\n\nWe will see how to prepare and share a complete portable QGIS environment:<\/p>\n\n\n\n data, styles, templates, and scripts on a USB stick or in a synchronized directory, so you can work or train independently, even without an internet connection.<\/p>\n\n\n\n \n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":" In our previous article, we discovered how the Layer Menu from Project plugin enables you to quickly add layers to a project in progress. Today, we’re extending this logic to build a modular, reusable and professional…<\/p>\n","protected":false},"author":1,"featured_media":14333,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[3394,1377],"tags":[3154,3512,2793],"class_list":["post-14777","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pluigin-en","category-qgis-en","tag-github-en","tag-layer-menu-en","tag-script-en"],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.sigterritoires.fr\/wp-content\/uploads\/2025\/06\/avant_lm2.jpg?fit=500%2C375&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p6XU0A-3Ql","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/14777","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=14777"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/14777\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media\/14333"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=14777"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/categories?post=14777"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/tags?post=14777"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}