Sarah Mulholland wrote:
In looking at the NITF 2.1 spec, I notice that the number of bands (NBANDS) in an image is by default represented by an ascii charactacter ‘0’ to ‘9’. There’s an XBANDS field that you can use for images with more bands when there are multispectral bands in excess of 9. I notice that when I call “driver.Create” with more than 9 bands, python seg faults when I call GetRasterBand for the first band. Would I be correct in assuming that gdal doesn’t support the XBANDS feature in the NITF?
Sarah, That would appear to be the case. I encourage you to file a ticket on the issue. 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 Programmer for Rent _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
