01Rust-native runtimeOriginal brand artwork
Qualification
Release qualification in progress
TasteGeo
GeoServer compatibility,
rebuilt in Rust.
Rebuilding GeoServer compatibility in Rust.
A Rust-native geospatial server built by comparing existing OGC requests and operational behavior with a reference server.
01
01 / 07
Compatibility-firstRust edition 2024GPL-2.0-or-later
02
Protocol + store wall
One surface.
Many contracts.
Every core contract in the generated matrix is currently partial support under validation. This is a measured compatibility surface, not a completion claim.
01
WMS
Maps, feature info, and legends
02
WFS
Feature queries and transactions
03
WMTS
Matrix sets and tile cache
04
WCS
Coverage subsets and output
05
REST
Catalog and service configuration
06
PostGIS
Primary vector adapter
07
GeoPackage
Portable SQLite datasets
08
Shapefile
Bounded vector ingestion
09
GeoTIFF
Raster and coverage store
10
COG
Cloud-optimized raster target
03 / Compatibility surfaceWorks with existing
Works with existing
GeoServer clients.
We validate compatibility by preserving protocol semantics, errors, catalogs, and operational flows. This is not a declaration of complete compatibility with any product.
WMS request
SERVICE=WMS
REQUEST=GetMap
VERSION=1.3.0Normalized evidenceSemantic comparison
WMS consumersCompatibility target
WFS consumersCompatibility target
WMTS clientsCompatibility target
REST automationCompatibility target
PostGIS workflowsAdapter under validation
Existing data_dirRead-only analysis path
OGC toolingSemantic comparison target
Map rendering clientsGolden image target
TasteGeo compatibility philosophy
Keeptheclients.Replacetheruntime.
Keep the clients. Move the runtime to Rust.
04
Workspace architecture
Boundaries before
speed.
We fix dependency direction and verify public HTTP behavior. No storage engine or framework gets to define protocol semantics.
01 / Foundation
Foundation
Protocol- and storage-independent values, parsers, coordinate systems, and observability boundaries.
geometrycrsfilterogc-commonconfigobservability02 / Domain
Domain
Catalog, security, style, and versioned extension contracts live in one layer.
catalogsecuritydatastore-apistyleplugin-api03 / Adapters
Adapters
Data access is isolated so protocol implementations never depend directly on a particular store.
store-postgisstore-geopackagestore-shapefilestore-geotiff04 / Services
Services
OGC services and the administration API are assembled above rendering and cache layers.
rendertile-cachewmswfswmtswcsrest-api05 / Assembly + Verification
Assembly + verification
The server assembles boundaries; verification tools compare only public HTTP and fixtures.
servercompat-tests05 / ReadinessEvidence before
View verification fixtures
Evidence before
declaration.
TasteGeo separates local code-quality gates from external release qualification. Core contracts remain partial support under validation while final promotion is in progress.
Current statusRelease qualification in progress
01 / 05
Compatibility
Send the same request to the reference server and candidate, then normalize and compare semantics.
- Normalize XML namespaces and attributes
- Compare feature and geometry semantics
- Raster golden images
- OGC exception parity
06
Captured output
Make the difference
visible.
We verified each fixture's content type and binary signature. Reference captures are never presented as candidate output.
Verified source fixtureWMTS tile fixture
Reference capture / image/png / 256 x 256
Decorative assetService terrain
Original brand artwork / not test evidence
Verified source fixtureRaster output fixture
Reference capture / image/png / 256 x 256
Verified source fixtureWMS world fixture
Reference capture / image/png / 64 x 32
THE TASTEGEO METHODCompatibility is
Compatibility is
demonstrated, not declared.
TasteGeo builds reproducible comparisons and operational evidence before making completion claims.