Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 4.5
-
Fix Version/s: 5.0
-
Component/s: None
-
Labels:None
Description
When working with AATSR data, the pixel info display in BEAM appears to calculate the time an individual pixel was calculated based on the extent of the product, the difference between the start and stop times given in the MPH and the distance of the pixel from the start of the product. This yields inaccurate results which could be improved by using the timing information contained within the SPH instead.
public interface TimeCoding {
ProductData.UTC getTime(PixelPos pos, ProductData.UTC time);
}
public class Product {
...
public TimeCoding getTimeCoding() {...};
...
}
public class RasterDataNode {
...
public TimeCoding getTimeCoding() {...};
...
}