OSGeo knowledge base
This page matches the webinar "Open Source GIS/GEO in practice". Here are the recording, ten widely used QGIS plugins, building blocks for your geo infrastructure, and a step-by-step plan you can open when you want the checklist and more detail.
Webinar recording: "Open Source GIS/GEO in practice"
Rewatch or revisit a section? This recording matches the step-by-step plan and QGIS plugin list further down the page.
The top 10 most-used QGIS plugins
During the webinar we showed ten widely used QGIS plugins: from basemaps and data sources to web publishing and the GeoApps link. Below is the same list with short notes and links.
Show the full list (all 10 QGIS plugins)
GeoApps <> QGIS plugin
The GeoApps route for QGIS workflows, installation, and publishing. The short URL /qgis redirects here.
What parts make up a modern geo infrastructure?
A modern geo stack connects data sources, services, and maps people actually use. Many teams blend open-source tooling on the desktop with a managed layer for sharing and sign-in. Expand the table for a common example.
Show the full table (parts & examples)
The last row, for example, lists a map platform such as GeoApps alongside open-source building blocks—your own mix may look different.
| Part | Example | What for |
|---|---|---|
| Desktop workbench | e.g. QGIS | Make maps, answer spatial questions, and check data before you share it. |
| Data storage | Often PostgreSQL + PostGIS | Where the authoritative map layers live: reliable, searchable, and connectable to other systems. |
| Online maps | e.g. GeoServer or similar | So maps work in a browser or apps, not only on the specialist’s PC. |
| Keeping data fresh | Scripts or schedulers | Repeatable steps to refresh data from source systems on a schedule (less manual work, fewer mistakes). |
| Web & access | Map in site/portal, links | Where colleagues and citizens see the map, and where you connect sign-in and other software. |
| Portal / map platform | GeoApps or comparable | A commercial platform (not open source): you buy or subscribe with support and ongoing product work. Sits alongside QGIS and self-hosted parts as a managed layer for viewers, data, and integrations. |
Roadmap: open source GIS and modern GIS
See the step-by-step plan below. Twelve steps from vision to scale. Steps 1 to 8 combine a short work list with deeper detail: open a step to see everything. Then migration, data, publishing, automation, roles, training, governance, and advanced use cases.
Define what GIS should deliver for the organisation
Work list (short)
In plain language, write down why you want open source (for example: less dependence on one vendor, easier links to other systems, or more control over data). Decide how far you want to go: maps on the PC only, maps on intranet or website as well, or a broader map-and-data setup.
- Involve the right people early: business (geo), IT, privacy/security if relevant, and someone who knows your contracts.
- Name processes that really cannot slip (permits, crisis, citizen desk). You wait longer with those or build a safe parallel path.
- Make success concrete: for example “20 colleagues work independently in QGIS” or “the map layer is ready automatically every night”.
Deeper detail
Do not start with tools: start with the question: what must GIS deliver?
Think about:
- more data-driven working
- better online map services
- less dependence on proprietary software
- lower licence costs
- better integration with databases, dashboards, and fieldwork
- public map applications or participation
- support for policy advisors, project leads, and field staff
Output: A short GIS vision with concrete use cases.
Map the current GIS architecture
Work list (short)
Make a simple list: which programs and contracts, where map files live, who makes maps, and who helps when something breaks. That quickly shows where it hurts.
- For each important map layer: who owns it, how often it must be refreshed, and whether you may share the data (licence and privacy).
- What other systems connect to it? Think of reports, case systems, organisation sign-in, or maps on phones for field staff.
- Briefly note what feels messy: old scripts, loose files, missing documentation. That usually decides what you tackle first.
Deeper detail
Map what runs today and where it hurts.
Inventory:
- which desktop GIS software is in use
- which online viewers or platforms exist
- which databases are used
- which web services are used
- links with FME, ArcGIS, QGIS, PostgreSQL/PostGIS, aerial imagery, street imagery, PDOK, Geopunt, and similar
- where data lives: on-prem, SaaS, or local
Output: Current architecture plus pain points.
Define the target modern GIS stack
Work list (short)
You do not have to replace everything at once. Many teams start with QGIS and a central place for map data; online maps for colleagues and citizens come later. Choose what fits your people and IT agreements, and what you can maintain.
- Discuss where software runs: on your servers, with a vendor in the cloud, or a mix. Think about backups and who applies updates.
- Keep test and production separate: try first, then roll out. A short written runbook prevents panic when something goes wrong.
- A hybrid route is normal: open source on the desktop and a commercial web platform (such as GeoApps) for sharing, sign-in, and links, or the other way around.
Deeper detail
Choose what you need per layer.
Examples per layer:
- Desktop GIS: QGIS
- Database: PostgreSQL/PostGIS
- Open data: PDOK, Geopunt, OpenStreetMap, BAG, BGT, aerial imagery
- Online GIS: e.g. GeoApps or another web GIS platform
- ETL/data integration: FME, GDAL/OGR, ogr2ogr, or alternatives
- Fieldwork: QField or an online fieldwork app
- Dashboards/storytelling: dashboards, map tours, participation maps
Output: Target architecture.
Build a migration plan
Work list (short)
Open source brings freedom and responsibility: who may do what, which passwords must never be shared, and how do you back up? Agree this with IT and privacy, so no one has to guess later.
- Who tracks security notices for the products you use, and how quickly do you patch?
- Keep a simple rule for which QGIS (or other) plugins are allowed, so people do not install unknown add-ons blindly.
- Make clear who helps users when something breaks: service desk, GIS team, or a partner.
Deeper detail
Decide what moves, is rebuilt, or is connected. Start with a pilot instead of everything at once.
Decide:
- which data must be migrated
- which existing maps must be rebuilt
- which services are replaced or linked
- which user groups transition
- which processes are modernised first
- what stays on desktop vs moves online
Output: Phased migration plan.
Set up QGIS as the desktop GIS baseline
Work list (short)
Pick one concrete example (one map product or one workflow). Train the people who will run it, and show them where to ask questions. If it works, you expand.
- Agree what “good enough” means: map speed, data correctness, availability outside office hours.
- Brief managers and colleagues in plain language: less jargon, more real examples.
- Unsure between “build everything yourself” and a ready-made web platform? Read our open source vs commercial piece and GeoApps vs QGIS.
Deeper detail
Install QGIS LTR and configure a reusable baseline.
- PDOK plugin
- Geopunt plugin where relevant
- QuickMapServices
- QuickOSM
- GeoApps plugin or other web GIS connection
- database connections to PostGIS
- standard project templates
- branding/styling for map layers
- access rights and work instructions
Output: A working QGIS baseline environment.
Set up the central data environment
Work list (short)
Converting old files often takes longer than installing new software. Work in small steps, spot-check boundaries and labels, and record who keeps the “right” version.
- Watch coordinate systems: one agreed rule for converting “old” to “new” so layers do not drift apart.
- A short note per layer (where it comes from, may I share it?) helps colleagues and prevents mistakes later.
- Track versions: which export belongs to which moment, especially when several people work in parallel.
Deeper detail
Avoid scattered, siloed data.
- PostgreSQL/PostGIS as the central database where possible
- open standards: WMS, WFS, WMTS, GeoPackage
- central datasets for BAG, BGT, aerials, OSM, your own registers
- clear data quality agreements
- versioning and ownership per dataset
Output: A central, reusable geodata foundation.
Publish data to online GIS
Work list (short)
Open standards make it easier to switch vendors later or share data. In the Netherlands you often use national feeds (such as PDOK); note where they fit and who owns them.
- Put map URLs and sign-in details for each service in one place, so people do not reinvent the wheel.
- If you load many external maps: agree whether you may cache them briefly to avoid overload.
Deeper detail
Make maps usable for people who are not GIS specialists.
- online viewers
- dashboards
- participation maps
- fieldwork apps
- story maps
- internal policy maps
- public web maps
Output: Policy staff, project leads, field teams, and citizens can use geo without QGIS: first online GIS applications.
Automate workflows
Work list (short)
Software ages: plan once a year (or more) which versions you upgrade and how you roll back if something breaks. Small regular care prevents big crises.
- One page of “what do I if…” (blank map, full disk, expired certificate) saves hours in incidents.
- Open source lives on communities; occasionally spending time on docs or a bug report helps everyone.
Deeper detail
Which manual GIS tasks can you automate? Use FME, GDAL/OGR, scripts, or platform capabilities.
Examples:
- fetching data from PDOK or Geopunt
- scheduled dataset refresh
- geocoding
- area analyses
- reporting
- ETL processes
- dashboard updates
- publishing map layers
Output: Less manual work, more reliable processes.
Define operations, roles, and responsibilities
Deeper detail
The GIS expert does not disappear; the role evolves.
- GIS specialist
- geo information manager
- data steward
- GIS application manager
- product owner for geo applications
- SLA manager for SaaS GIS
- PostGIS database administrator
- advisor on geo information products
- digital twin / AI geo specialist
Output: A clear operations and roles model.
Train users by audience
Deeper detail
Not everyone needs to become a QGIS power user.
- GIS specialists: QGIS, PostGIS, styling, analysis
- admins: data, access, publishing, quality
- policy staff: online maps and dashboards
- field staff: fieldwork apps
- management: dashboards and reporting
Output: Adoption plan plus training.
Anchor open source governance
Deeper detail
Make explicit choices about open source.
- which open source software you use
- how updates are managed
- how plugins are reviewed
- how documentation is maintained
- how the organisation contributes to communities
- membership or donation to QGIS NL or OSGeo if relevant
- open standards in procurement
Output: Written open source governance agreements.
Scale to advanced use cases
Deeper detail
After the basics: grow toward strategic applications.
- 3D GIS
- digital twins
- AI queries on geo data
- automated area analyses
- scenario comparison
- policy monitoring
- energy, climate, mobility, real estate, and public space
Output: GIS as strategic information supply, not only as a map tool.
Advisory call: prepare and book
Aligning briefly as a team (or with your partner) first keeps a call with us focused. Then pick a time below to walk through the roadmap, modern GIS, open source, and how GeoApps could fit your situation.
Questions to align on internally
- Which processes must never stop during a transition?
- Who will keep map data up to date and check that it is correct?
- Is there money and time for operations (hosting, updates, helpdesk), on top of any licence savings?
- Which rules apply to us (privacy, procurement, vendor contracts)?
- Do we want one central place for all map layers, or several sources we combine?
- Where do we use open source, and where (if at all) a commercial platform like GeoApps, and who supports each part?
What we can discuss with you
- Applying the roadmap to your situation and clarifying what to tackle first.
- Modern GIS, open source, and hybrid options (for example QGIS plus web) in your context.
- Where GeoApps fits alongside or together with your open source stack, and what operations and adoption require.
Ready to talk? Pick a time slot below that works for you.
Is the scheduler not loading properly? Open Calendly in a new tab
Other topics worth reading
Articles and guides that connect to this topic.
