I am the author of those changes (adding metadata copy to gdalwarp), and I must confess I had not thought of scale and offset.
What I did do was add non-conflicting metadata (at the dataset and band level) and some band-related stuff like description. I have just tested and gdalwarp does not pass the offset and scale_factor. Kyle - could you check out trunk and have a look? If you need any pointers on the new code just ask. regards, Etienne On Wed, Mar 21, 2012 at 7:08 PM, Frank Warmerdam <[email protected]> wrote: > On Wed, Mar 21, 2012 at 3:01 PM, Kyle Shannon <[email protected]> wrote: >> If I have a dataset with a scale and offset: > ... >> I couldn't find any docs on this. Is this known and/or expected? I would >> think scale and offset would be transferred to the new file. > > Kyle, > > Scale and offset are basically a form of metadata, and it is ambiguous > how much metadata gets transferred by processing tasks, like gdalwarp. > In cases where gdalwarp is being used to warp into an existing output > file it would not be appropriate to transfer the scale and offset. > However, in the case that gdalwarp is initializing a new output file > it would seem reasonable to also copy over the scale and offset. > > I believe some recent changes were made to copy other metadata, > and this would seem to fall into a similar category. I'd suggest > fixing yourself, or writing up a ticket on the topic. > > Best regards, > -- > ---------------------------------------+-------------------------------------- > I set the clouds in motion - turn up | Frank Warmerdam, [email protected] > light and sound - activate the windows | http://pobox.com/~warmerdam > and watch the world go round - Rush | Geospatial Software Developer > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
