Hi, There should certainly not be a space between Nodata and Value as in your mail below. There are two formats relevant for (at least) arcgis: .bil. In this case the keyword is NoData .flt. In this case the keyword is NoData_Value. Capitalization, afaik, is irrelevant. So you could modify the .hdr file as a test, and if it works out as I indicated (NoData=-9999 in stead of NoData Value=-9999) you can file a useful ticket. .flt, by the way, is a float array which appears to be used only as an intermediate (conversion) format, as in the conversion tools: float to raster and vice versa. Hope this helps a little, Jan
On Wed, Mar 6, 2013 at 7:53 PM, Joaquim Luis <[email protected]> wrote: > Hi, > > While playing a bit with Lastools I came across this behavior. I create > outputs in both .bil and .asc ESRI formats > The weird thing is that beeing the .hdr header file common (I mean exactly > equal) to both outputs the .bil format does not recognize the nodata value. > Is this a knwon issue? (GDAL trunk on Windows) > > gdalinfo lixo.bil > ERROR 6: lixo.bil, band 1: SetNoDataValue() not supported for this dataset. > Driver: EHdr/ESRI .hdr Labelled > > > C:\programs\lastools\data>**gdalinfo lixo.asc > Driver: AAIGrid/Arc/Info ASCII Grid > Files: lixo.asc > ... > Band 1 Block=250x1 Type=Float32, ColorInterp=Undefined > NoData Value=-9999 > > Joaquim > ______________________________**_________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/**mailman/listinfo/gdal-dev<http://lists.osgeo.org/mailman/listinfo/gdal-dev> >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
