🗃️
Stable

Data Management

Native support for PostGIS, GeoPackage, Shapefile, GeoTIFF, and over 40 additional formats. Automatic schema detection, reprojection, and indexing.

Documentation →
Beta

WMS/WFS/WCS Engine

Fully compliant OGC implementation with tile caching, feature filtering, and dynamic styling via SLD, CSS, and vector tiles.

API Reference →

System Architecture

\n
Component Version Status Last Updated
Core Engine 2.24.1 Production 2024-11-15
Web UI 3.2.0 Production 2024-11-12
Tile Cache 1.8.4 Production 2024-11-10
Security Module 2.1.0 Maintenance 2024-11-08

Performance

Optimized for high-concurrency environments. Multi-threaded request handling, memory-mapped file I/O, and Redis-backed tile caching.

Security

Role-based access control, LDAP/Active Directory integration, OAuth2/OIDC support, and TLS 1.3 enforcement by default.

Extensibility

Plugin architecture with Maven-based build system. Over 120 community and enterprise extensions available.

Technical Specifications

r>
SpecificationDetails
RuntimeJava 17+ (LTS)
Servlet ContainerApache Tomcat 10.x, Jetty 12.x, or embedded Undertow
Database SupportPostgreSQL/PostGIS (recommended), Oracle, SQL Server, GeoPackage, SpatiaLite
OGC StandardsWMS 1.3.0, WFS 2.0, WCS 2.1, CSW 3.0, WMTS 1.0, GeoJSON, GeoPackage
ReprojectionGDAL/PROJ integration with over 2,000 CRS definitions
StylingSLD 1.1, CSS4 for Vector Tiles, ECSS, and runtime dynamic styling
ContainerizationOfficial Docker images, Kubernetes operators, Helm charts

Release History

VersionRelease DateTypeHighlights
2.24.1Nov 15, 2024MinorPerformance improvements for large vector datasets
2.24.0Oct 01, 2024MajorNative GeoJSON API, updated Web UI, Java 17 baseline
2.23.5Sep 12, 2024PatchSecurity fixes for LDAP authentication module
2.23.4Aug 28, 2024PatchGDAL 3.8 compatibility updates
2.23.3Jul 15, 2024PatchTile cache optimization and memory leak fixes

Project Governance

GeoServer is governed by an open steering committee comprising maintainers from leading geospatial organizations. All technical decisions follow RFC-style proposals with community voting.

Contributor Model

We operate under a CLA-free contribution model with DCO sign-off. Code reviews require approval from at least two core maintainers. CI/CD pipelines run comprehensive test suites across multiple JDK versions.