Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Cesium Ion Terrain Provider #10758

Open
dsuren1 opened this issue Jan 16, 2025 · 0 comments · May be fixed by #10763
Open

Add support for Cesium Ion Terrain Provider #10758

dsuren1 opened this issue Jan 16, 2025 · 0 comments · May be fixed by #10763
Assignees
Labels
New Feature used for new functionalities
Milestone

Comments

@dsuren1
Copy link
Contributor

dsuren1 commented Jan 16, 2025

Description

We should implement support for Cesium Ion resources and assets in MS by recognizing the new Cesium terrain provider, cesium-ion.
This should allow users to configure a Cesium Ion Terrain Provider, with the added flexibility to define the assetId, accessToken & server for the terrain. This new configuration will be used inside the TerrainLayer to implement the new provider

{
  "type": "terrain",
  "visibility": true,
  "provider": "cesium-ion",
  "options": {
    "assetId": 1,
    "accessToken": "",
    "server": undefined  // by default uses https://api.cesium.com
  }
}

Note

  • In Cesium Ion, requestWaterMask and requestVertexNormals are not configurable because these settings are managed automatically based on the asset type and data provided by Cesium Ion
  • There is no need to configure the ellipsoid explicitly, as the underlying data from Cesium Ion automatically aligns with the WGS84 ellipsoid.
  • Since Cesium Ion resources are accessed using an access token, it is assumed that the need for a proxy is unnecessary
  • Cesium handles the appropriate attribution and licensing credits when displaying resources from Cesium Ion

Additional Info

Reference ticket - https://github.com/geosolutions-it/support/issues/3946

@dsuren1 dsuren1 added the New Feature used for new functionalities label Jan 16, 2025
@dsuren1 dsuren1 added this to the 2025.01.00 milestone Jan 16, 2025
@dsuren1 dsuren1 self-assigned this Jan 16, 2025
dsuren1 added a commit to dsuren1/MapStore2 that referenced this issue Jan 17, 2025
@dsuren1 dsuren1 linked a pull request Jan 17, 2025 that will close this issue
5 tasks
@dsuren1 dsuren1 linked a pull request Jan 17, 2025 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Feature used for new functionalities
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant