The terrain source for the Cesium Viewer quit working a while ago. It turns out that Microsoft/Bing wanted to issue keys to people who were using their code, and this key needed to be added to the javascript for the Viewer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Further information on the BingMaps key requirement:
Without the key your viewer generates the following console message (I found this by loading the viewer URL into Chromium with the developer's console open):
Cesium.js:418 This application is using Cesium's default Bing Maps key. Please create a new key for the application as soon as possible and prior to deployment by visiting https://www.bingmapsportal.com/, and provide your key to Cesium by setting the Cesium.BingMapsApi.defaultKey property before constructing the CesiumWidget or any other object that uses the Bing Maps API.
Note that the key is associated with one particular URL. This means (I think) that you'll need a different key if you run the Cesium code from your own local server. My key is associated with http://daveshangar.org/viewer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The terrain source for the Cesium Viewer quit working a while ago. It turns out that Microsoft/Bing wanted to issue keys to people who were using their code, and this key needed to be added to the javascript for the Viewer.
Further information on the BingMaps key requirement:
Without the key your viewer generates the following console message (I found this by loading the viewer URL into Chromium with the developer's console open):
Note that the key is associated with one particular URL. This means (I think) that you'll need a different key if you run the Cesium code from your own local server. My key is associated with http://daveshangar.org/viewer