> Actually the whole coverage model as build originally by M. Desriusseaux was > based on this kind of hack, png images with integer values that are > transformed > to a phisical value via a linear transformation, under the assumption that > the quantization occurring in PNG encoding via the palette is not going > to affect significantly the data (e.g., the encoding error is significantly > lower than the sensor error). > > The tests in this package provide some examples on how to use these > concepts: > https://github.com/geotools/geotools/tree/master/modules/library/coverage/src/test/java/org/geotools/coverage/grid > > Basically the idea is that the coverage is build using the png as the > rendered image, and the grid sample > dimensions do contain the transformations to the geophisic interpretation of > the coverage, which > can be obtained as a GridCoveage by getting the geophisics view of it
So you think the "range" file contains the offset and scale values necessary for the conversion? >From Gaby's email I thought more there was some kind of lookup table, but your guess makes way more sense. Andrea ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
