OGC API Features + CQL2
Collections, items, individual features, BBOX and attribute filters, pagination, CRS requests and CQL2-text filtering over DuckDB-backed and virtual collections.
Protocol-level interoperability
Preserve client contracts. Change the engine.
3DGeoServEngine publishes familiar Esri-compatible and open-standard service shapes while discovering, ingesting and translating remote ArcGIS, GeoServer, MapServer, QGIS Server and OGC endpoints.
Published service surfaces
Esri-compatible endpoints with concrete operations.
These are server-side interfaces, not just remote connectors. Coverage varies intentionally by data type; each row states what the service actually does.
| Service surface | Implemented behavior | Primary sources | Typical consumers |
|---|---|---|---|
| FeatureServer | Service and layer metadata; query with BBOX, spatial, object ID and CQL2 translation; addFeatures, updateFeatures, deleteFeatures, applyEdits; GlobalID, attachments and related-table workflows. | DuckDB spatial, GeoPackage, virtual collections, registered database tables | ArcGIS Pro, ArcGIS Maps SDK, Field Maps/Survey123-style sync, custom REST clients |
| MapServer | Raster map-service directory and export surface through the raster bridge; styles are exposed as browseable services and WMS 1.3.0 equivalents. | Rasterized basemap/style services and upstream raster bridge | ArcGIS clients, WMS clients, tactical map clients |
| VectorTileServer | Service metadata, root MapLibre style JSON, PBF tile path, sprite JSON/PNG and generated default styling for vector sources. | Dynamic or packaged MVT, vector MBTiles/VTPK/GPKG collections | ArcGIS VectorTileLayer, MapLibre, compatible web/native clients |
| StreamServer | Service/layer metadata, current feature snapshot, live WebSocket subscription and event updates suitable for ArcGIS Pro and GeoEvent-style consumers. | TAK/CoT, IoT, GNSS, MQTT, Redis, Kafka REST, WebSocket and normalized operational feeds | ArcGIS Pro, GeoEvent consumers, operational dashboards, custom WebSocket clients |
| SceneServer | I3S service and layer documents, node pages, node geometry/textures and statistics for SLPK/I3S datasets, plus a bridge for registered scene layers. | SLPK, I3S scene layers, 3D conversion workflows | ArcGIS SceneLayer clients and 3D web applications |
| ImageServer | Service metadata; exportImage; identify; samples; histograms and statistics; raster tiles and LERC elevation tiles where appropriate. | Local and remotely registered Cloud Optimized GeoTIFFs | ArcGIS ImageryLayer/ElevationLayer, analytical apps and raster clients |
The Esri REST directory is broad, but “compatible” should always be validated against the specific client versions, renderers, geometry types, editing rules and authentication flows in a migration scope.
Open-standard surfaces
Standards are first-class interfaces, not export checkboxes.
The same datasets can remain available to open-source desktop tools, web clients, catalogs and automation pipelines.
STAC 1.0 + OGC API Records
Search local and discovered assets through STAC collections/items/search and a unified OGC API Records catalog, with a CSW 2.0.2 crosswalk for legacy catalog clients.
WMTS, XYZ, MVT + TileJSON
WMTS 1.0.0 capabilities and REST/KVP tile access, XYZ templates, vector PBF tiles and TileJSON metadata across MBTiles, PMTiles, GeoPackage and generated collections.
WCS 2.0.1 + WMS 1.3
WCS 2.0.1 capabilities and coverage-description/download routing for COG holdings, plus WMS GetCapabilities/GetMap through the raster bridge, alongside the richer ImageServer interface.
OGC 3D Tiles 1.1
Serve and consume 3D Tiles content, including packaged 3TZ, converted scenes and optimized implicit tiling for point clouds and Gaussian splats.
SensorThings, SOS + Moving Features
Connect to and normalize OGC SensorThings, SOS and SensorML feeds; parse OGC Moving Features JSON into time-aware observations for the real-time data plane.
Universal discovery
Start from the server URL, not a hand-built layer URL.
The discovery engine crawls service directories and capabilities documents, classifies protocols, extracts layers and persists normalized records to a local GeoPackage catalog.
01
Auto-detect
ArcGIS REST, GeoServer, WMS, WFS, WCS, WMTS, OGC API, XYZ/TMS and 3D Tiles server patterns.
02
Crawl and classify
FeatureServer, MapServer, ImageServer, VectorTileServer, StreamServer, SceneServer and open-standard layers are recorded with protocol and resource URLs.
03
Decode applications
Read web-map, web-scene and web-application JSON so operational layers, visibility, basemaps and service references can be reconstructed.
04
Add or ingest
Build a frontend-specific add-to-map specification, or stream compatible feature protocols into a local, QGIS-readable GeoPackage.
05
Search the catalog
Query discovered services alongside local assets through OGC API Records and CSW with text, BBOX and protocol filters.
Incremental migration
Run old and new clients at the same time.
A contract-preserving cutover lowers risk because the data plane can change independently of every consuming application.
Existing estateArcGIS web maps and appsQGIS projectsCustom REST integrationsETL and scheduled jobs
→
Compatibility validationSchema and GlobalID mappingRenderer/style translationEdit/attachment round tripsPerformance and security tests
→
Phased cutoverRead-only mirrorDual publishTransactional pilotApplication-by-application switch