[gdal-dev] raw x-y-z height map.

2008-11-13 Thread Eran Burstain
Hi. I want to convert a height map (DTED or other format) to simple ASCII file with X,Y,Z coordinates, supplemental data (datums) should be in separate file (.vrt), Is there support in such a format ? ___ gdal-dev mailing list gdal-dev@lists.osgeo.org

RE: [gdal-dev] NITF TRE support

2008-11-13 Thread Dan Greve
Kurt, I am in the same boat. I have modified the GDAL driver to read AIMIDB and ACFTB similiar to BLOCKA metdata, but I do not have the capability to write these TREs. The TRE creation option should allow this, but I haven't found a good example of how to do this. Hopefully the developer

Re: Gdal Bug? was: Re: [gdal-dev] JP2MRSID Issues

2008-11-13 Thread Michael P. Gerlek
Stephen, Frank: Yes, this is indeed a Kakadu error coming from underneath our SDK. The error feels like the sort of thing that happens when one is requesting a bounding box that is outside of the legal bounds for the image at that magnification level: that is, perhaps the scene parameters being

[gdal-dev] GDAL encounters problem with very small files, part 2

2008-11-13 Thread Matthieu Rigal
Hi all, hi Frank, OOps, I have forgot to say that I unfortunately have only the version 1.4.2 of GDAL/OGR here. If it works on your machine, then it may come from this out-of-date version But please check it also from your side... Best regards, Matthieu Rigal RapidEye AG Molkenmarkt

[gdal-dev] Re: GDAL encounters problem with very small files

2008-11-13 Thread Frank Warmerdam
Matthieu Rigal wrote: Hi all, hi Frank, I am encountering problem with gdal_translate and gdalinfo with very little images. I have for example a 9*16 pixels image, georeferenced, 16bits and 8bits, that I have tested in 2 formats : .pix PCIDSK and .tif GTiff. And both times, I get errors :

[gdal-dev] GDAL encounters problem with very small files

2008-11-13 Thread Matthieu Rigal
Hi all, hi Frank, I am encountering problem with gdal_translate and gdalinfo with very little images. I have for example a 9*16 pixels image, georeferenced, 16bits and 8bits, that I have tested in 2 formats : .pix PCIDSK and .tif GTiff. And both times, I get errors : gdal_translate: symbol

Re: [gdal-dev] OGR WFS driver

2008-11-13 Thread Frank Warmerdam
Johan Nouvel wrote: Hello all, I know GDAL has a WMS and WCS driver, but no WFS driver. After looking into the mailing list archives I have found no references to a WFS driver. For my job, we have developped such a driver (in readonly mode, but write mode is planned) , based on OGR and its

[gdal-dev] (no subject)

2008-11-13 Thread Sarah Mulholland
I need to write multiple images to a NITF file. I notice on the gdal NITF page that gdal only writes one image or raster of data to a file. On another page, I see that multiple images in a NITF can be read as subdatasets. Is the documentation up to date that subdatasets in a NITF file are a

Re: [gdal-dev] raw x-y-z height map.

2008-11-13 Thread Frank Warmerdam
Eran Burstain wrote: Hi. I want to convert a height map (DTED or other format) to simple ASCII file with X,Y,Z coordinates, supplemental data (datums) should be in separate file (.vrt), Is there support in such a format ? Eran, No, there is currently no direct support for such a format in

[gdal-dev] Re: Gdal Bug? was: Re: JP2MRSID Issues

2008-11-13 Thread Jukka Rahkonen
Stephen Woodbridge woodbri at swoodbridge.com writes: PPS. I don't understand your point where you seem to suggest that converting to tiff first is slower than other mechanisms. Are you suggesting it takes 2-3 hours to convert a 500MB jpeg2000 image to GeoTIFF? Perhaps you need to

Re: [gdal-dev] OGR WFS driver

2008-11-13 Thread Stefan Keller
Hi Johan, Nice proposal! 2008/11/13 Frank Warmerdam [EMAIL PROTECTED]: ... I'm also curious what you do for parsing the GML. Do you process it through the existing OGR GML driver? WFS mandates GML but allows others. So, if yes, would it be difficult to parametrize the response file format?

Re: [gdal-dev] nitf xbands supported?

2008-11-13 Thread Frank Warmerdam
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.