Clarification on Cesium ion and access token

CesiumJS
1

Hi all,

Apologies if this has been asked, but I didn't see it if so. I've recently been testing v1.47 of CesiumJS and am seeing the access token warning:

This application is using Cesium's default ion access token. Please assign Cesium.Ion.defaultAccessToken with an access token from your ion account before making any Cesium API calls. You can sign up for a free ion account at https://cesium.com.

As I understand, the access token is for using ion. I don't believe I am currently using any ion assets in my app and the access token warning shows when I just use OSM tiles and 3D-tiles hosted by myself. Is this expected behaviour? If I just continue to use CesiumJS can I legitimately manually remove this? Or should it be disappearing on its own? Or do I just register for a Community plan and then not use any ion assets?

2

Cesium ion is also used by default in the geocoder. If you want to suppress the warning, you can either disable the geocoder, if you’re not using it, or configure it to use a different GeocoderService.

3

Thanks for the reply. The message still appears when I disable the geocoder though. Here is a minimal sandcastle example:

4

You’re still getting the Ion message because you’re adding OSM on top of the Bing Maps base layer, rather than replacing it. This seems to work:
https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/#c=ZVBBasMwEPyK8MUpBIleXScUciqkJBDoSZeNvXVEZcnsrh3c0r9XdkhJWt12dmZnRjYMQCpyq1Zqg+z6VleEILjrMByEEOUVupcWGqRxT3FwNdLiywaVXk9eFSo/iXRcGANanEcdk5JnZQudjtSY3Ibvhycb7Gw2ODwjJb+A56vn24wt8moeNzEIuICUL5OTFT5BHc9cqHfwjMsJajBWMUW5xY7AuIURae+qj9vVlNXdVyimzr+xsmVWsowe1xfys2u7SDIVXGhtBNvOpz9hc+zTZdEV8yQszVVU1m5Qrl7Z7E8Dm6nKA3PavPfeH9wn2mxdmsS/k/kItQvNbkDyME6U0+N6ewG11qVJ43+VxOiPQDcXfwA

5

Ah, I see. Yes that has indeed fixed it. Thanks both!