A Brief History of Open Source GIS and an Overview of WebGIS Architecture

Commercial GIS vendors dominate the market with comprehensive product lines covering data acquisition, editing, management, analysis, and web services, but high costs and customization needs make open‑source solutions, especially WebGIS, an attractive alternative.

1. Open Source GIS History

The emergence of digital mapping and Geographic Information Systems (GIS) transformed how we perceive and interact with the world. In the 1960s, landscape designer Lan McHarg introduced layered location information for decision‑making, while Roger Tomlinson, the "father of GIS," completed his PhD on computational handling of layered spatial data and created the Canada Geographic Information System for surveying.

Open source GIS traces back to 1978 when the U.S. Department of the Interior launched the Map Overlay and Statistical System (MOSS), the first widely deployed vector‑based interactive GIS. Shortly after, the Geographic Resource Analysis Support System (GRASS) was born, offering over 350 modules for raster, vector, and image processing, initially for the U.S. military and now widely used in research and industry.

1.1 GIS Origins: MOSS & GRASS

MOSS was designed to monitor environmental impacts of mining, representing the first vector‑based interactive GIS. GRASS later expanded capabilities for land‑management and environmental planning, and today supports spatial data management, image processing, spatiotemporal modeling, and map creation.

1.2 GIS Development: GeoTools, GDAL/OGR, PostGIS, and GeoServer

In 1996, the University of Leeds began a Java‑based GIS library project that became GeoTools, a core component of the popular GeoServer and widely used for web and desktop GIS applications.

Four years later, the Geospatial Data Abstraction Library (GDAL) was released, providing command‑line tools and supporting over 50 raster and 20 vector formats; it underpins applications such as Google Earth, QGIS, and ArcGIS.

In 2001, Refractions Research created PostGIS, enabling spatial data storage in PostgreSQL, and the same year GeoServer was launched to publish spatial data as standard web services. Both projects have become cornerstone open‑source GIS database and server solutions.

1.3 Innovation and Education: Open‑Source Projects Drive Growth

QGIS, first released in 2002, integrates GRASS analysis, GDAL format support, and offers a user‑friendly desktop for editing, mapping, and analysis, interoperating with PostGIS and GeoServer.

The Open Source Geospatial Foundation (OSGeo) and Eclipse LocationTech initiatives, launched in 2006, foster collaborative development and broader adoption of GIS technologies across academia and industry.

In 2011, the "Geo for All" program was created to provide free educational resources, including the FOSS4G Academy and GeoAcademy, promoting worldwide access to geospatial training.

1.4 Standardization: OGC and OpenGIS

The Open Geospatial Consortium (OGC) is a non‑profit standards body that defines interoperable specifications such as WMS, WFS, WCS, WPS, and WMTS, ensuring that GIS software can exchange spatial data reliably.

2. WebGIS Architecture

2.1 WebGIS Components

A complete WebGIS solution typically consists of three layers: geographic and business databases, GIS and web‑application servers, and client‑side rendering.

1) Geographic and Business Databases Geographic databases store vector, raster, address, thematic, and tile data; business databases hold relational data for front‑end applications.

2) GIS Server & Web Application Server GIS servers provide OGC services (WMS, WMTS, WFS, WCS); web application servers retrieve GIS services and business data to deliver web‑based information browsing.

3) Client The client presents all information to end users via browsers or desktop applications.

2.2 Open‑Source WebGIS Solutions

Data production desktop software: use uDig, QGIS, GRASS to collect and process geospatial data.

Data storage: relational data in PostGIS or MySQL Spatial; non‑relational data (tiles, images) in MongoDB.

GIS server: deploy GeoServer, MapServer to generate map tiles and publish services.

Web server: use Geomajas, Tomcat or Apache for website hosting; Nginx as reverse proxy or load balancer.

Front‑end rendering: client‑side maps via OpenLayers, Leaflet, or other JavaScript frameworks (e.g., Vue).

Additional supporting services such as cloud environments and operating systems are also required.

In practice, a typical stack might combine uDig/QGIS, PostgreSQL/PostGIS (or MongoDB), GeoServer, Tomcat, and OpenLayers; high‑performance or high‑availability needs may demand clustering of databases, GIS servers, and web servers.