← Back to the capability index
Serve · serve.i3s-sceneI3S Scene Serving
Source evaluation — counted evidence Community
Evidence by type
| Evidence type | Detail | Result |
|---|---|---|
| Esri migration assessment | assessKey(s) | scene-service |
| Route entries & proving tests | 6 route entries | 25 proving tests (implemented: 6) |
SDK coverage
| SDK | Status | Entry points | Note |
|---|---|---|---|
| honua-sdk-js | not-covered | — | — |
| honua-sdk-dotnet | partial | Honua.Sdk.Scenes.HonuaSceneClient | Same as serve.3d-tiles-scene: the scene client resolves the I3S endpoint URL and capability tag (HonuaSceneCapabilities.I3s) only; it does not parse or serve the I3S scene-layer protocol itself. |
| honua-sdk-python | partial | honua_sdk.protocols.SceneClient.resolve_scene, honua_sdk.protocols.SceneClient.fetch_tile | I3S-tagged scene endpoints resolve and fetch as opaque bytes through the same generic scene-endpoint resolution used for 3D Tiles, but there is no I3S-specific scene-layer-package (.slpk) node/resource-tree parsing -- only the 3D Tiles tileset.json walker (enumerate_tileset_contents) is implemented. |
Executable samples
No executable sample published for this capability yet.
Known gaps
No open honua-server issues tagged for this capability’s category.
Raw receipts
- capability-keys.v1.json — canonical key definition for
serve.i3s-scene. - capability-matrix.v1.json — honua-server's Phase-A evidence snapshot (entry/test counts, CITE, parity, interop, geobench).
- sdk-js coverage · sdk-dotnet coverage · sdk-python coverage
- honua-samples run-samples CI — executable sample run history.
- capability-matrix.v1.json — the full enriched aggregate backing this page.