Cesium in 2017 - what do you want to see?

CesiumJS
61

https://github.com/AnalyticalGraphicsInc/cesium/issues/4000
I very important to us and I belive to GIS community in general)

62

Once again, thanks for the great discussion; this thread already has over 60 posts and 400 views!

I’ve updated and sorted the Google Doc summary.

Thanks to the new Cesium Consortium with AGI and Bentley, we now have more bandwidth to push Cesium forward. Our focus for the first quarter of 2017 (Jan, Feb, and March) is:

  • 3D Tiles - the spec has already entered the OGC community standard process and the Cesium implementation is pretty widely used. By the end of March, we plan to have the spec and implementation ready for Cesium Community Review:
  • The 1.0 spec is done and ready to be reviewed before we submit it for the final OGC votes. (The remaining spec items are here.)
  • The pull request for the 3d-tiles branch is open. We’ll also cherry-pick parts into master sooner as reasonable.
  • Label quality - there’s already a pull request with some improvements, #4886, and we’ll also explore the AA issues.
  • Performance - some Cesium-wide performance improvements are implicit in 3D Tiles, such as #4387.
  • glTF 2.0 - this is also implicit in 3D Tiles.
    In early April, we’ll plan for the next quarter and see if we can prioritize some of the hot items like sub-surface visualization.

How can you help?

  • We welcome contributions of any shape and size: everything from carefully written bug reports to doc fixes to guest blog posts to engine optimizations. We’ll, of course, graciously credit you. See here to get started.
  • If your organization wants to support the core team by sharing some development costs, contact me directly at pcozzi@agi.com, to discuss the new Cesium Consortium or services projects.

Thanks!

Patrick

63

I’ll toss in one more highlighted request. Per the issue I just filed ( https://github.com/AnalyticalGraphicsInc/cesium/issues/4876 ) , there’s a couple aspects of Cesium’s source that require special configuration to work with Webpack properly (namely, multi-line strings, and use of libs with require() ). It would be great if those could be reworked so that Cesium could completely work with Webpack out of the box.

64

Thanks Mark. Updated.

Patrick

65

Hi all,

There’s also a bug bash next month. Please comment in #4897 if there are bugs or small features you would like to see investigated during this three-day event.

Patrick

66

Hi guys,

Is there any work being done to make the different entity visualisations more feature complete?

For example, you can add an eye offset to a billboard, but not a point. I am unaware of any way that you can get around this, and it results in billboards not being clipped by the ground, while a point on the same entity is.

67

Points are trimmed down versions of billboards that are optimized to draw a lot of them; each per-point property comes at a memory and performance cost so we are careful about adding more. Consider rendering a point to a billboard as a workaround.

Patrick

68

That makes sense, though it doesn't appear that there is an easy way to render a point to a billboard?

If you want a circle or an outlined circle where you can control outline width and radius easily you have to use a point.

If you want the eye offset features you have to use a billboard.

69

Here’s an example of using HTML to create a circle that is used as input for a billboard:

https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Apps/Sandcastle/gallery/development/Billboards.html#L176-L212

If you have any other questions related to this, please start a new thread.

Thanks,

Patrick

70

+1 for z-order
+1 and quicker bug fixes

71

+1 for per-vertex color on polyline entities (issue #4393 on github).

72

Better performance, especially with KML processing!

73

  • New or improved tutorials and code examples. Tutorials and examples on dynamic updates through CZML, e.g. for GPS tracking

  • Other features or improvements, e.g., subsurface visualization, specific visual quality improvements, polylines on terrain, polyline styles, etc. – Dynamic colors/material for polylines

74

+1

75

Would like to see a REST api call on the terrain server that would return terrain height given a lon, lat.
This would be helpful for producing .b3dm tiles (and other tileset types) that have terrain height burned in.

76

Just realized this is probably not the place for this request…and would likely be an elevation service on top of the REST api.
Something like the google maps elevation service…

https://developers.google.com/maps/documentation/javascript/elevation

77

Hi,

I think there is already a function in the cesum Code. You should take a look at :

https://cesiumjs.org/Cesium/Build/Documentation/sampleTerrain.html

https://cesiumjs.org/Cesium/Build/Documentation/sampleTerrainMostDetailed.html

With this function you could implement a really easy and small REST API.

Jannes

78

ES6 modules please. I’m trying to use Cesium with meteor, and meteor doesn’t support npm modules that use AMD.

Aaron

79

Hi Patrick,

I would like you to improve you examples in the sandcastle.

Most of the samples are very basic.

In addition sample projects.

For instance I think that for new developer that start to develop in Cesium should have jump start projects to download so that they can take it from there.

For instance a project for Cesium with Dart, Angularjs, Angular 2 + typescript etc… it will be very useful.

Thanks,

Kfir.

80

+1