Hi,
I've committed a fix (r19493) that will disable the use of the new
GDALCopyWords implementation. The old and new implementations are functionally
equivalent, but the new implementation is in some cases 5-10x faster than the
old implementation. However, there is no problem with disabling it
Hi,
I'll have a look at this issue -- I've never tried compiling the updated
GDALCopyWords with C++Builder. If it isn't too much trouble, could you please
file a ticket on GDAL's trac (http://trac.osgeo.org/gdal) and assign it to me
(pvachon).
Thanks a lot!
Phil
On 2010-04-20, at 4:51 AM, jc
Hi Mateusz,
I would actually wonder if a solution like this would work:
/// @brief Allocate memory on the heap and return a pointer of type T.
/// @param ptr pointer to be populated to the allocated memory
/// @param size the size of a single object to be allocated (or of the entire
region)
///
Hi Ben,
I can't recall the exact details of how the GRASS r.in.gdal mechanism
works, but the results you describe are similar to importing calibrated
data into an integer raster. Calibrated SAR data is typically
represented as floats, as many of the values are in [0, 1), if I am not
mistaken. As s
Hi Vali,
Have you tested this using GDAL trunk? I only had access to a limited
number of TerraSAR-X scenes when writing the GDAL file reader for it, so
it's possible that the high resolution spotlight imagery is structured
differently and thus can't be read by GDAL.
Could you run the gdalinfo too
Hi Jason,
I just tried to reproduce this, but wasn't able to; perhaps you don't
have the latest version of the C Runtimes installed. It looks as though
GEOS_C.DLL has correct manifest data embedded for the VC90 runtime
(Visual Studio 2008) so as long as you have the correct assembly
installed for
Hi Shawn,
I've never seen a NITF RADARSAT-2 image, so the RADARSAT-2 GDAL driver
was not designed to support NITF. Do you know if it's possible to get
some sample datasets in NITF format from somewhere?
At this point, if you want to read the NITF RS2 imagery, it's probably
safest to use the NITF
Hi,
Just out of curiosity, are you using the 'stable' branch, GDAL 1.5? I'm
unable to reproduce the issue using the development branch, but I don't
have a GDAL 1.5 tree handy to build and test. What I might suggest is
grabbing a snapshot of the GDAL 1.6 tree (or doing an SVN checkout of
it), build
Hi Shawn,
If you're using GDAL directly, and don't select a subdataset AND the
program you're writing ignores subdatasets, you can just read the
digital numbers without any other work. A hidden misfeature of the RS2
driver.
However, if you're using it with OpenEV or something, it might be
possibl
Hi Vincent,
I'll fix this one ASAP, don't know how that one got past QA. ;-)
Cheers,
Phil
On Mon, Sep 08, 2008 at 11:31:46AM +0200, Vincent Schut wrote:
> FYI,
>
> the terrasar-x driver assigned the lat of a gcp as its x coordinate, and
> lon as y, which should obviously by lat -> y and lon ->
10 matches
Mail list logo