Building Support Matrix
Capability |
Support level |
Scope |
Diagnostics |
|---|---|---|---|
Native GeoJSON building import |
|
Available only when the native/Pro path is present. |
|
Native CityJSON building import |
|
Available only when the native/Pro path is present. |
|
Python fallback geometry |
|
Current fallback paths can create zero-geometry building records. |
|
|
|
Typed MapScene recipes record building source identity, support level, geometry count, bounds, and material status. |
|
Scalar PBR materials |
|
Scalar material values exist and MapScene can preserve material status, but production building material rendering is not fully integrated. |
Support matrix entry plus validation diagnostics. |
Textured PBR buildings |
|
|
|
Building workflows must not treat zero-geometry fallback output as successful ingestion.
Textured building material intent requires an albedo texture path, readable local
asset metadata, supported image suffix, and UV coordinates for the affected
geometry. scalar fallback is not textured PBR support; it must be reported as a
placeholder/fallback diagnostic and diagnosed before render. This
non-MVP-blocking textured-material deferral keeps the current offline map workflow
honest while avoiding claims of material parity with DCC or game engines.