TASTEGEO docs
TASTEGEO is a Rust-native geospatial server that reimplements GeoServer's public behaviour (OGC requests, responses and errors, and REST configuration) by sending the same requests to a reference server and comparing the results. It runs as a single executable without a JVM, and the protocol code is separated from PostGIS, GeoPackage, Shapefile and GeoTIFF stores by versioned boundaries. An existing data_dir is only read for diagnosis, and migration happens in stages through shadow traffic comparison and rollback conditions. For now the core contracts have partial support under verification, and it does not claim to be a complete drop-in replacement. A fuller introduction and the compatibility status are at tastegeo.com.
Installation
We don't provide ad hoc download links until verified release files and URLs are registered.
What to check now
- Source version
- TBD
- Supported platforms
- Verifying release targets
- Release status
- Coming Soon
- External docs
- Verified docs
Quick start
- 1
Get the Windows executable with a verified code signature and SHA-256 from the Downloads page and unpack it into one folder.
- 2
Choose one authentication method (anonymous read, Basic or token) and a data_dir, then start the server.
- 3
Check the services with GetCapabilities, and if you run GeoServer in production, send it the same requests to compare the responses.
Key features
OGC services
WMS maps, feature info and legends, WFS queries and transactions, WMTS tiles and WCS coverages, handled at the public HTTP boundary. All are partial support under verification.
REST catalogue
Manage the catalogue (workspaces, stores, layers and so on) and service settings through REST. When enabled, state is saved to a file, and if it becomes corrupted the last good copy is restored.
Store adapters
PostGIS, GeoPackage, Shapefile and GeoTIFF (including COG) sit behind versioned boundaries. Protocol code is not tied directly to any particular store.
Comparison with a reference server
The same request is sent to the reference server and to TASTEGEO, and XML, features, geometry and OGC errors are normalised and compared; rasters are matched against golden images.
Rendering and tile cache
Draws maps with styles applied, and keeps a tile cache aligned with WMTS matrix sets.
Coordinate systems and filters
Coordinate system transformation and OGC filters are handled in a foundation layer independent of the store.
Secure defaults
Everything is denied by default. Only one of read-only anonymous access, Basic authentication that accepts only Argon2id hashes, or token authentication can be enabled, and they are never mixed.
Migration
An existing data_dir is only read for diagnosis, then migrated in stages through a separate conversion, shadow traffic, canary and rollback conditions.
Native distribution
The first release is a Windows x86_64 executable that runs without containers. Linux and macOS open only after verification on real machines.
Supply chain and signing
A dependency licence policy, vulnerability scanning and a CycloneDX SBOM are in place, and releases are verified by code signature and checksum.
Troubleshooting
I can't see a download button.
No public release files have been registered yet. Only ready files appear on the downloads page.
Can I check which operating systems are supported?
The docs only list environments verified for each product. “Being verified” means support isn't confirmed yet.
Where can I check the current feature scope?
The key features in these docs and the product page are written based on the current project source.