Hi Vicent,

Since the SetNoDataValue and GetNodataValue is based on the limitation of 
GeoTiff I would not expect DeleteNoDataValue to be any different. For example, 
there is no way to set/get NoData for individuals bands, there is no way to 
set/get an array of NoData values or NoData value ranges. For drivers that 
support such thinks, the DeleteNoDataValue will probably delete all NoData 
values from the dataset.

But that is something that can't be resolved by the RFC 58. I think.

Very often, I find unsigned 8 bit images with absurd NoData value, like -9999. 
That is probably a software specific flag value. The problem is that in 
gdal_translate there is no option to prevent that NoData to be passed from one 
format to another. So I am about to implement a value range check on the 
CreateCopy to avoid that.

Would that be feasible to accept the option "-a_nodata NO" on GDAL command 
lines, to indicate that NoData should not pass from the input to the output 
dataset?

Best regards,

Ivan


Date: Tue, 19 May 2015 08:50:50 +0200
From: sc...@sarvision.nl
To: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] RFC 58: Removing Dataset Nodata Value


  
    
  
  
    On 05/18/2015 08:37 PM, Sean Gillies wrote:

    
      Hi all,
        

        
        In consultation with Even Rouault, I've written up RFC 58. 
        

        
          https://trac.osgeo.org/gdal/wiki/rfc58_removing_dataset_nodata_value
        

        
        The gist of it: allowing deletion of a nodata value defined
          for a dataset, thereby rendering all pixels valid without
          copying data to a new file.
        

        
        I'd love your feedback and thumbs up or thumbs down on this
          RFC. Thanks,
      
    
    As daily users of gdal me and my collegues would like to give this a
    very big thumbs up. We've really been missing this. Thanks a lot for
    starting this RFC.

    

    Vincent.

    

    
      
        

        
        --
        Sean Gillies
        

        
        

        
      
      

      
      

      _______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
    
    

  


_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev                                
          
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Reply via email to