Hosted layers compatibility QA
Hosted-layer browser QA uses pinned public samples rather than files created specifically for Meratyn. Small generated fixtures remain useful for fast unit tests, but they are not treated as proof that the publication workflow handles real files.
Recipient test matrix
The following pinned files cover every representation currently added by the default Catalog plugin:
| Layer family | Pinned public sample | Expected Meratyn layer |
|---|---|---|
| GeoParquet vector | OGC GeoParquet 1.1 Natural Earth example | Vector/GeoJSON |
| FlatGeobuf vector | FlatGeobuf world countries | Vector/GeoJSON |
| GeoTIFF raster | OSGeo/GDAL byte raster | WMS |
| PMTiles archive | OSGeo/GDAL polygon PMTiles | PMTiles |
| COPC point cloud | PDAL Autzen EPSG:4326 excerpt | LiDAR |
| GLB model | Khronos glTF Box | deck.gl scenegraph |
| Published vector service | A local GeoJSON upload from the vector fixture set | WFS-backed GeoJSON |
The repositories retain their own licence and attribution terms. Do not copy a sample into a release artifact without checking the source repository’s licence.
For each sample, QA must exercise the complete path:
- Download the file from the pinned public location and record its checksum.
- Upload it through Meratyn’s browser form and wait for Ready.
- Add it from Meratyn’s Catalog panel.
- Confirm the layer row, representation type, fitted camera, and hosted-layer identity in the saved project.
- Open the public Meratyn project in a fresh anonymous browser session.
- Confirm that the embedded Meratyn viewer loads the layer without a failing Meratyn asset or gateway request.
Provider-backed vectors also test WMS capabilities and map images, plus WFS
capabilities and GeoJSON features. Provider-backed rasters test WMS
capabilities and PNG map images, plus WCS capabilities and GeoTIFF coverage.
Opening a connection from Use & share must include SERVICE and
REQUEST=GetCapabilities; opening a bare service address is not a valid browser
test.
Do not stop at capabilities responses. A raster pass must request the PNG tiles for the fitted viewer extent, and the concurrency check should issue at least 36 adjacent GetMap requests in one burst. This catches metadata lookups or gateway limits that appear healthy one request at a time but fail under a real MapLibre tile load.
The local reference workspace keeps one public project for each row in this matrix, plus a separate WFS project. Each focused project must contain exactly one data layer, have a saved extent around that layer, and reach a visible map without network or runtime errors. Benign renderer warnings should be recorded separately from failures; the small COPC excerpt currently emits a coordinate clamp warning for its root-node cube while its points and range requests remain valid.
Version edges
GeoParquet compatibility is versioned. The recipient matrix pins the stable 1.1 example. The development example on the default OGC repository branch may use GeoParquet 2.0 before the browser’s DuckDB Spatial build supports it, and older pre-1.0 files may omit required geometry metadata. Those files should produce an explicit compatibility error rather than a layer that appears to have been added.