Hello,
In order to ensure compatibility between GeoserverTerrain provider and Cesium b26 release, I updated the provider in compliance with terrain provider requirements ( getErrorEvent -> errorEvent, getCredit -> credit, getTilingScheme -> tilingScheme, isReady -> ready).
In my case, geoserver provides imagery layer (images via web map service) and terrain data (arraybuffers via web map service).
My update of Cesium was made in mars first.
In these following cases, I don't have problems:
- when imagery Layer is provided by bings server and terrain provided by Cesium Terrain provider
- when imagery Layer are provided by my geoserver and terrain provided by Cesium Terrain provider
In these following cases, Imagery layer and Terrain provider seem blocked:
- when imagery Layer is provided by bings server and terrain provided by my geoserver
- when imagery Layer are provided by my geoserver and terrain provided by my geoserver
Moreover, I found these facts during my debugging researches (firefox and chrome) :
- XMLHttpRequest for terrain tiles worked
- Imagery layer don't make XMLHttpRequest after get first level tiles (very low resolution level)
- Sometimes, I have problem with line "frustumCommandsList.length = numFrustums;" from
function updateFrustums(near, far, farToNearRatio, numFrustums, frustumCommandsList) {
frustumCommandsList.length = numFrustums;
for (var m = 0; m < numFrustums; ++m) {
var curNear = Math.max(near, Math.pow(farToNearRatio, m) * near);
var curFar = Math.min(far, farToNearRatio * curNear);
var frustumCommands = frustumCommandsList[m];
if (!defined(frustumCommands)) {
frustumCommands = frustumCommandsList[m] = new FrustumCommands(curNear, curFar);
} else {
frustumCommands.near = curNear;
frustumCommands.far = curFar;
}
}
}