Re: [gdal-dev] gdalnumeric.BandWriteArray gdalnumeric.Int8

2009-01-27 Thread Vincent Schut
use 'Byte' instead of Int8. Gong, Shawn (Contractor) wrote: hi list, I have used datablock.astype(gdalnumeric.Int16) in gdalnumeric.BandWriteArray() Is there a gdalnumeric.Int8 to write an 8-bit band/image? thanks, Shawn

[gdal-dev] Non documented (nice, uf) behaviour

2009-01-27 Thread Joaquim Luis
Hi, Still on the ps2raster issue that I mentioned 2 days ago, I was getting a mysterious crashing in Windows when executing a system call with a gdal_translate command. The is not related to GDAL at all but maybe to the quotes needed to wrap the +proj=... arguments. I finally managed to solve

Re: [gdal-dev] Non documented (nice, uf) behaviour

2009-01-27 Thread Frank Warmerdam
Joaquim Luis wrote: Hi, Still on the ps2raster issue that I mentioned 2 days ago, I was getting a mysterious crashing in Windows when executing a system call with a gdal_translate command. The is not related to GDAL at all but maybe to the quotes needed to wrap the +proj=... arguments. I

Re: [gdal-dev] Non documented (nice, uf) behaviour

2009-01-27 Thread Joaquim Luis
I'm not complaining (well on the contrary), but we may need to document this. Since what version is it possible to provide a Proj4 string in a file for -a_srs? Joaquim, Underlying the -a_srs function is the OGRSpatialReference::SetFromUserInput() method which does mention that proj.4

Re: [gdal-dev] Enhancing JP2KAK

2009-01-27 Thread Frank Warmerdam
Greg Coats wrote: The code in 1.6/gdal/frmts/jp2kak/jp2kakdataset.cpp calls upon the http://www.kakadusoftware.com/ JPEG2000 software to display, read, and write .jp2 files. This code has not been updated since 2002, and does not take advantage of any of the major advances in the Kakadu

RE: [gdal-dev] ogr2ogr: KML to any format - export fields

2009-01-27 Thread Christopher Condit
Hi Ednardo- Is there a particular reason that you don't want to go directly from the original MapInfo to SHP? I would suggest that first, that way you don't lose field information. At this point the KML reader is not aware of KML Schemas, so you'll always get a big mashup of fields... This is