Skip to content
GEOSAT
Back to the migration study

EVIDENCE ANALYSIS · NOT A GEOSAT CLIENT

Solothurn: QGIS, PostGIS and open-source investment

Solothurn replaced ArcInfo and ArcView3 with QGIS, GRASS and PostGIS, and reported investing approximately $30,000 per year in QGIS.

Organization

Canton of Solothurn · Solothurn, Switzerland

Evidence type

Reported annual open-source investment

Evidence date

Case contributed in May 2009

Technologies mentioned

QGIS · GRASS GIS · PostGIS · MapServer · Python

Reported annual open-source investment

≈ $30,000/year invested

A phased FOSSGIS strategy

Solothurn’s parliament decided in 2001 to migrate from Windows to Linux to reduce supplier dependency, encourage competition and lower licensing costs. The SO!GIS team applied that direction to an open geospatial architecture serving more than 3,500 canton employees.

The sequence was gradual. UMN MapServer and a web client came first. Geospatial data then moved from shapefiles to PostGIS. Finally, after evaluating desktop alternatives, QGIS with GRASS replaced ArcInfo and ArcView3 in 2006.

Fifty users are not 3,500 QGIS seats

The source says more than 50 people used QGIS Desktop in their daily work. The 3,500 employees were consumers of the broader SO!GIS services and infrastructure, not 3,500 QGIS desktop users.

That distinction matters in licensing analysis. A wide portal can serve an entire organization while only a smaller group needs advanced editing, analysis and cartographic production.

Replacement required development

Solothurn contracted nearby providers to build missing features and developed Python plugins. These included tools for discovering published PostGIS layers and searching municipalities, addresses and cadastral parcels without exposing users to the underlying data-model complexity.

The result was not a free copy of the previous interface. It was a platform adapted to institutional workflows with custom development and commercial support.

What approximately $30,000 a year means

The article reported that the canton had invested approximately $30,000 in QGIS every year since 2007. It presented that spending as more efficient and targeted than support paid to the previous provider.

The figure is not savings, a license fee or complete TCO. It represents investment in QGIS features and evolution. The original page uses the $ sign; for rigor, we do not convert this historical amount to COP or present it as a current operating benchmark.

What it proves and what it does not

It proves an explicit replacement of ArcInfo and ArcView3 with QGIS and GRASS, a move to PostGIS, and an open stack sustained through commercial development.

It does not publish previous license cost, net savings, complete infrastructure, internal staffing or the full cost of web services. It also does not show that every proprietary function was replaced without adaptation.

Lesson for Colombia

The most useful financial lesson is to budget reinvestment. Part of avoided licensing expense can fund plugins, automation, support and improvements controlled by the organization.

The technical lesson is to separate user profiles. Many people can consume web services while a smaller group needs desktop QGIS. This design can lower cost without assuming that every employee requires the same tool or capability.

APPLY THE CASE TO YOUR DATA

Calculate first; then validate every workflow

Use annual Esri spend for a preliminary range. We then build the functional inventory and real migration budget.