CesiumGS / CesiumGS/cesium-native

support vector data in the ITilesetExternals interface or an analog

Open
#1,215 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C++
Stars
623
Forks
277
PR merge metrics
No merged PRs in 30d

Description

We now have support for rasterizing vector features, represented in GeoJSON, into image layers (#1163 on the native side). An obvious next step is to export vector data to Cesium Native clients as "vector tiles", so that a client can render the vector data or otherwise process it. Vector Tiles are a much-requested feature, and it's hard to know where to go with it. A possible approach would be to support tilesets that deliver vector data instead of meshes. If we choose a format for the vector features that is kind of "least common denominator,", then we can implement tileset providers for multiple formats: mvt, 3D tilesets with the MAXAR_content_geojson extension, ITwinFeatureService results...

A related question is how to style these features; see #1208.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the ITilesetExternals interface and the vector-feature rasterization work referenced in #1163. Read the related styling question in #1208 and determine a supported vector-data representation and provider approach; done would require an agreed design rather than the issue's current proposal.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.