Le jeudi 26 mars 2015 19:23:28, Shawn Gong a écrit :
> Hello Even,
>
> To where can I submit the code?
Assuming you intend to contribute that upstream ultimately, ticket with patch
attached / github branch / ...
>
> Thanks,
> Shawn
>
> From: Even Rouaul
Hello Even,
To where can I submit the code?
Thanks,
Shawn
From: Even Rouault [even.roua...@spatialys.com]
Sent: March-26-15 12:52 PM
To: gdal-dev@lists.osgeo.org
Cc: Shawn Gong
Subject: Re: [gdal-dev] NITF2.1 complex data type
Shawn,
>
>
> We receive SAR
Shawn,
>
>
> We receive SAR SLC (single look complex) images in NITF2.1. But the I and O
> bands are separate (HH_I, HH_Q, VV_I, VV_Q, etc)
>
> My colleague modified the gdal NITF driver nitfdataset.cpp to rewrite them
> as NITFComplexRasterBand (see below) It works with a single-pol SLC and
>
Hi list,
We receive SAR SLC (single look complex) images in NITF2.1. But the I and O
bands are separate (HH_I, HH_Q, VV_I, VV_Q, etc)
My colleague modified the gdal NITF driver nitfdataset.cpp to rewrite them as
NITFComplexRasterBand (see below)
It works with a single-pol SLC and outputs as I
Matthew,
> Good morning,
> I've got some raster images for Hawaii, and I've found that running any
> command (gdalinfo, translate, warp) will return the following error in my
> Ubuntu environment:
>
> Warning 1: Unhandled (yet) value for Datum : OHA-M. Defaulting to WGS84...
I guess this comes
Hi,
For all willing mentors & co-mentors :
-- Message transmis --
Sujet : [SoC] Mentor registration procedure
Date : jeudi 26 mars 2015, 12:46:44
De : Margherita Di Leo
À : "OSGeo-SoC"
Dear All,
I'd like to remind that you can find the procedure on how to apply as a
mentor
Good morning,
I've got some raster images for Hawaii, and I've found that running any
command (gdalinfo, translate, warp) will return the following error in my
Ubuntu environment:
Warning 1: Unhandled (yet) value for Datum : OHA-M. Defaulting to WGS84...
I have seen that the files located i
Nicolas,
> Hi list,
>
> As I was reading these RFC I was thinking about an old idea to
> improve the consistency between the different drivers. Instead of having a
> specific test suite for each drivers, it'll be more interesting to have a
> test suite in each driver relying on a generic
Hi list,
As I was reading these RFC I was thinking about an old idea to improve
the consistency between the different drivers.
Instead of having a specific test suite for each drivers, it'll be more
interesting to have a test suite in each driver relying on a generic test suite
