What Is GeoServer? How to Publish Spatial Data With OGC Standards

What Is GeoServer and What Does It Do?

GeoServer is an open source map server that shares spatial data as standard web services. According to the official GeoServer overview, it runs on Java. It also lets users share and edit map data from any major source through open standards.

In practice, GeoServer sits between your data and your users. For example, your data might live in a PostGIS database, a folder of shapefiles or a set of satellite images. GeoServer reads that data and applies a style. Then it answers requests from web maps, desktop tools such as QGIS and mobile apps. Because each request follows Open Geospatial Consortium (OGC) rules, the client never needs to know where the data lives.

The project also has a long track record. The Open Planning Project, a New York non-profit, started GeoServer in 2001. In addition, people from the GeoServer team founded GeoTools, the Java toolkit that still reads much of its data. Today the code sits on GitHub under the GPL, so you pay no licence fee for the server itself.

Which OGC Standards Does GeoServer Support?

GeoServer supports the main OGC web services: WMS, WFS, WCS and WMTS, and it also offers WPS as an add-on. In addition, it is the reference build for WFS and WCS. So the OGC uses it to show how those standards should work.

Each standard answers a different need. For example, a web map needs a picture of the network, so it calls WMS. However, an analyst who wants to query or edit pipe data needs the real features, so they call WFS. The table below shows what each service sends back.

GeoServer also offers OGC API Features, the newer web-style successor to WFS. As a result, one catalogue can serve older GIS clients and modern web developers. However, WPS needs its own limits, because one heavy process can use a lot of memory.

Which Data Sources Can GeoServer Publish?

GeoServer publishes vector data from databases and files, and it also serves raster data from image files. The most common pair is GeoServer with PostGIS, because the database runs the queries while GeoServer runs the web services.

Still, data quality matters more than the store type. For instance, a utility moving records out of an old system should clean shapes and fields first. Our GIS data migration team often loads clean data into PostGIS with FME, and then GeoServer publishes it.

One simple rule follows from this. Keep one master copy of each dataset and let GeoServer read it directly. Otherwise copies drift apart, and then users see different answers in different portals.

How Do Styling and Tile Caching Work in GeoServer?

GeoServer styles layers with SLD by default. In addition, its tile cache, GeoWebCache, stores drawn tiles so repeat requests return fast. Together they control how maps look and how fast they load.

Styling with SLD and CSS

Styled Layer Descriptor (SLD) is an XML format for colours, symbols, labels and scale rules. It is precise but long. So GeoServer also offers CSS, YSLD and MBStyle add-ons, which say the same thing in fewer lines. Many teams write styles in CSS, because the files are easier to read and review.

Tiling with GeoWebCache

GeoWebCache ships inside GeoServer. It sits between the map client and the map server and saves tiles as users ask for them. As a result, the server does not redraw the same area for every user. The built-in version also sets up each layer in the two most common map grids.

• WMTS: this is the standard OGC tile service, so modern web clients can use it.
• TMS: this simpler tile scheme also works with many JavaScript map libraries.
• WMS-C: this serves cached WMS tiles at /gwc/service/wms for older clients.
• Direct link: this is off by default, but once you switch it on, WMS calls with TILED=TRUE come from the cache.

Tile caching suits stable layers such as basemaps, boundaries and imagery. By contrast, if a layer changes every few minutes, such as an outage area, live WMS usually works better.

How Do You Publish Spatial Data With GeoServer, Step by Step?

Publishing a layer in GeoServer follows a fixed order: workspace, store, layer, style and then tests. You can do each step in the web admin pages, or you can script it through the REST API.

For one layer, these steps take minutes. However, a catalogue with hundreds of layers needs scripts, naming rules and version control for styles. That is often where GIS software development work starts.

How Should You Secure and Deploy GeoServer in Production?

A live GeoServer needs new default passwords, request limits, production logging and tight data access. The GeoServer production guide lists these settings. If teams skip them, servers often end up slow or exposed.

Security also works at several levels. First, users, groups and roles control who signs in. Next, layer rules grant read, write or admin rights per workspace and layer. Finally, service rules can block tasks such as WFS edits. But if one user holds several roles, the least strict right wins, so plan roles with care.

For high uptime, a common pattern runs several GeoServer nodes behind a load balancer. In this setup, all nodes share one data folder. This works well if settings rarely change. However, GeoServer reads its settings at start-up, so each node needs a reload after changes. GeoWebCache also needs extra setup in a cluster.

Where Do Utilities and Government Agencies Use GeoServer?

Utilities and government agencies use GeoServer to share one master dataset with many systems through open standards. It often works as the publishing layer beside a core GIS, rather than in place of it.

• Electric and water networks: teams publish asset layers to field apps and outage portals, often as part of a wider electric utility GIS programme.
• Sharing between agencies: boundaries, land parcels and planning layers go out as WMS and WFS, so other teams use them without file transfers.
• Smart city portals: imagery and asset layers feed public and internal dashboards in smart city GIS projects.
• Mixed estates: an open source stack serves data to teams that also use Esri ArcGIS or other tools.

In Malaysia, the public sector already shares map data through MyGDI, the Malaysia Geospatial Data Infrastructure. It supports GIS work at federal, state and local levels. So open web services fit this model well, because each agency can publish once while others read the data in their own tools.

How Does GeoServer Compare With MapServer and ArcGIS Enterprise?

GeoServer, MapServer and ArcGIS Enterprise all publish OGC services. However, they differ in language, setup style and licence. So the right choice depends on your skills, your platform and your support model.

All three serve WMS and WFS, so the table lists only the extra services. In addition, GeoServer offers WPS as an add-on, and ArcGIS Enterprise also offers OGC API Features.

These tools also work side by side. For example, many teams keep a paid core GIS and then add GeoServer to share some layers with partners. Therefore the real question is often which layers each server should publish.

What Mistakes Should Teams Avoid With GeoServer?

Most GeoServer issues come from setup, not code. In fact, the five mistakes below cause most slow maps, empty layers and security gaps.

Each of these is cheap to fix early but costly to fix later. So build the checks into your release process rather than relying on memory.

Frequently Asked Questions

Is GeoServer the Right Map Server for Your Organisation?

GeoServer is a strong choice if you need to publish spatial data through open OGC standards with no licence fee. It reads PostGIS, files and imagery, and then serves WMS, WFS, WCS and WMTS. It also gives admins a browser interface plus a REST API. However, it rewards careful setup: safe defaults, request limits, caching and clean source data.

If you plan a new publishing layer, start with a short review of your data, users and current GIS. Our GeoServer consulting and development team can then design, deploy and support it beside your current tools. You can also get in touch to talk through a specific use case.