1. A concise explanation of the problem you’re experiencing.
Having trouble determining how to maniplate path positions on the fly, reading the values is simple enough but updating them back on the object doesn’t seem quite as simple.
2. A minimal code example. If you’ve found a bug, this helps us reproduce and repair it.
flightTrack = dataSource.entities.getById(‘varioTrack’);
var leadingPath = dataSource.entities.getById('leadingPath');
// this works
leadingPath.position = flightTrack.position;
// something like this doesnt
leadingPath.position = new Cesium.PositionProperty();
leadingPath.position.getValue = function(time, result) {
return flightTrack.position.getValue(time, result);
};
leadingPath.position.getValueInReferenceFrame = function(time, referenceFrame, result) {
return flightTrack.position.getValueInReferenceFrame(time, referenceFrame, result);
};
// I’ve also tried using the callback property without much joy.
3. Context. Why do you need to do this? We might know a better way to accomplish your goal.
We’re trying to track flight paths which appear to drop below the terrain and become invisible for some parts of the time period, this could be because of bad terrain data, bad GPS readings or a combination of both. We’d like to map any values which are below the terrain to at least sit at ground level
4. The Cesium version you’re using, your operating system and browser.
CesiumJS 1.38