What would you like to see in CesiumJS in 2025?

CesiumJS
1

Recently, the CesiumJS team has been making improvements in a variety of areas to support the 3D geospatial and visualization ecosystem. Changes in the past year have included visual quality and lighting improvements, support for additional glTF extensions, increased voxel capabilities, better clipping for 3DTilesets, and improving documentation like our guide for using CesiumJS with Webpack and Vite.

Now, we would love your input for what to see in CesiumJS in 2025 and beyond!

Please help us prioritize what you would like to see in CesiumJS. Your feedback can be as short as a vote for a topic, or a more detailed response.

  • Context around use cases helps us prioritize
  • Specific feedback or specific improvements is helpful; e.x. “More learning materials about how to control model animations” or “Add more example code in the API reference docs” are both much more helpful than “More documentation”
  • Links to existing GitHub issues are welcome

A few things on our mind:

We would also appreciate hearing from the community specific suggestions regarding documentation and learning content updates, tooling or packaging updates, and targeted performance benchmarking and optimization that would be most helpful to you.

To incorporate your feedback into the roadmap, we’d love your input by the middle of February. However, we always value your input, so please feel free to add anything afterwards if it comes to mind.

Thanks!
The CesiumJS team

3 Likes
5

Hi Luke,

Thank you for considering community feedback. Our team has been actively working with CesiumJS since 2022, and we would like to bring several important issues to your attention:

  1. 3DTiles 1.1 Rendering Quality Issue We are experiencing significant visual quality issues since the implementation of the Reality Tiler. The textures show much more pronounced flickering and grain effects compared to version 1.0. Despite our attempts to adjust SSE parameters, the problem persists. This issue is detailed in this discussion.

  2. 3DTilesets Clipping Performance While clipping improvements have been mentioned, the current implementation severely impacts performance (see GitHub issue). This feature is crucial for us, and the lack of a performant solution forces us to perform clipping manually during preprocessing. It’s surprising that this functionality isn’t prioritized, especially when other WebGL engines like Esri handle it efficiently. An optimized implementation would save the community hundreds of hours in BIM and 3D model integration.

  3. Tileset Z-index Management The current depth management is limited to depth testing against terrain, which proves insufficient for fine-grained control of individual tilesets. For instance, our semantic buildings appear above the terrain even when they should be hidden by relief features.

depthtestagainstterrain
depthtestagainstterrain1920Ă—1235 298 KB

  1. Dynamic Color Adjustment The ability to modify imagery layer colorimetry at runtime would be invaluable for ensuring color consistency between imagery layers and 3D tilesets.

These improvements seem essential for optimizing CesiumJS usage in a professional context.

Looking forward to your thoughts on these matters and potential solutions.

Best regards.

3 Likes
6

Vector Tiles! Maybe some day :smiling_face_with_tear:

7 Likes
7

Please can you make césium compatible without building or data imagery, i would like too use it for landscaping only, so it should be possible to landscape editor (like coloring ground texture and editor heightmap.

Thanks,

Yoann

1 Like
8
  • Avoidance of text or billboard on LabelCollection or BillboardCollection’s level
  • Smooth globe tile or model tile switching (like Mapbox)
  • Better render performance on high resolution screen, including pick position and pick object
  • Better ground primitive rendering
  • More PolylineAppearance
3 Likes
10

@Luke_McKinstry I need to be notified when all primitive in collection has been created by the worker.

Maybe add the possibility to get the status of the worker createGeometry ?

11

Thanks @Mickael, but it sounds like your question is a bit more specific than the roadmap discussion we’re focusing on here.

I would suggest either:

  1. Opening a new thread with about the question, or
  2. Letting us know the more general reasons behind this question; perhaps performance issues with large amounts of geometry primitives

Thanks!

12

@tbenazzi Thanks for your detailed input!

Would you mind expanding on this point a bit more? We do support runtime color adjustments for imagery layers. I suppose you are looking for additional functionality?

13

@Kevin_Ten_Eyck

Vector tiles are still on our radar :eyes:

That issue has become a bit of a catch-all beyond a 3D Tiles extension– including things like geometry performance broadly, and support for Mapbox Vector Tiles.

Would you mind adding some specifics to your use case? I’m guessing performance of large-scale time-dynamic vector data?

14

Basic support for OGC GeoPose Basic Quaternion:
See JSON schema here:

go to “9.2.3. Standardization Target 2: Basic-Quaternion”

Example GeoPose:

{
  "position": {
    "lat": 47.7,
    "lon": -122.3,
    "h": 11.5
  },
  "quaternion": {
    "x": 0.20054473382601948,
    "y": -0.08111675703887213,
    "z": 0.3660908114262869,
    "w": -0.9050852994339209
  }
}

Set camera by GeoPose + Get GeoPose from current camera pose

Place 3d object by GeoPose, + Get GeoPose of 3d object in scene

Best regards,
Jan-Erik