A WebGIS is a map that opens in a browser: no installation, always updated, accessible by multiple departments and, if desired, by citizens. It's the alternative to PDF-distributed cartography, which becomes outdated the day after printing. Let's see why the transition is convenient, the three possible approaches, and the actual costs.

The problem is not the PDF

PDF is perfect for attaching a drawing to an act. The problem arises when it becomes the way the organization stores and shares territorial knowledge. From there, three unaccounted costs emerge:

The three ways to go online

1. Publish without writing code

Tools like uMap (open source) or Felt Maps allow you to upload your data and get a shareable map in no time. Perfect for a thematic map, public consultation, or an informational layer to disseminate immediately. The limit comes when you need complex consultation logic or integration with other municipal systems.

2. Build the application with a library

Leaflet and OpenLayers are the two JavaScript libraries powering most production WebGIS systems. With Leaflet, you achieve a lot with little code; OpenLayers handles more complex cases — special projections, multiple WMS and WFS services, advanced interactions. Here, the map becomes a custom application, requiring someone to maintain it.

3. Rely on a managed platform

If the goal is to make the territory consultable without worrying about servers, updates, and backups, the solution is a managed platform: the data remains the entity’s responsibility, but technical maintenance does not. This is the approach of SmartLands services, from GIS hosting to custom WebGIS.

How much does it cost

Software is not the main expense: QGIS, Leaflet, OpenLayers, and uMap are all free and open-source. The real costs are two others, and it’s best to face them before starting:

Do it in-house or outsource it

It’s not a binary choice. The combination that works best for municipalities is hybrid: the platform is provided by the vendor, but the data remains in the office’s hands. For this to work, however, the entity needs at least one person who can read and correct the data — otherwise, every change becomes an external request.

This is why the most solid path starts with training: the Basic QGIS Course for data autonomy, the WebGIS Course to understand how and with what to publish them online, from libraries to no-code tools.

Want a dedicated edition for your entity?

We’ll tailor the program to your territory’s real data — road networks, house numbers, green areas, toponymy, signage — so training hours also yield operational results. We’ve already conducted training activities for the Municipality of San Gimignano, the Municipality of Casalecchio di Reno and theOrder of Architects of Florence.

Request the program for your entity.

Frequently asked questions

What’s the difference between GIS and WebGIS?

GIS is the system for managing and analyzing territorial data, typically via installed software. WebGIS is their publication on the web: accessible via browser, with no installation required.

Do you need a dedicated server?

Not always. A map published with no-code tools doesn’t require your own infrastructure. When handling sensitive data or large volumes, however, dedicated hosting becomes the right choice.

Do data become public automatically?

No. Visibility is decided layer by layer: some data remain office-only, while others are opened to the public.

Leave a Reply

Your email address will not be published. Required fields are marked *