Shawn,
I would be willing to test your patches for the netCDF driver if you file a
ticket and supply sample data, as Ivan stated. Thanks
On Apr 29, 2010 7:56 PM, "Shawn GONG" wrote:
Hi list,
My colleague, Adam Klein, and I have made changes to the following drivers:
netCDF: corrects for longit
Hi Shawn/Adam,
My suggestion is that you should file a ticket for each problem you solved describing the reasons
for the changes maid. You should attach the changed source code to the ticket and some sample data
too (or the path to where I get download it from) so that we can test your changes.
Hello,
I am attempting to build gdal 1.7.1 with hdf4 4.2.5 on windows VS 2008. I
built HDF with no problems, however when I try to build GDAL with HDF
(MODIFY nmake) it fails because of linker errors.
Any help would be greatly appreciated.
Sample of errors..
1>hdf4imagedataset.obj : error
Hi list,
My colleague, Adam Klein, and I have made changes to the following drivers:
netCDF: corrects for longitudes >180 deg (western hemisphere)
RSAT2: able to ingest NITF complex products
TSX: utilizes all GCPs instead of the default of 5 (4 corners + 1 centre)
Please advise how to submit the
Maurício,
The doc of AutoIdentifyEPSG() tells :
"""
* This method inspects a WKT definition, and adds EPSG authority nodes
* where an aspect of the coordinate system can be easily and safely
* corresponded with an EPSG identifier. In practice, this method will
* evolve over time. In theory
Hi list,
I was recently trying to use OGRSpatialReference::GetAuthorityCode from the
python API and I've found that it worked on WGS 84 UTM but not on SIRGAS
2000 UTM.
Sirgas: http://spatialreference.org/ref/epsg/31974
WGS: http://spatialreference.org/ref/epsg/32720
I've taken the .prj description
Alexander,
This has been fixed in http://trac.osgeo.org/gdal/ticket/3247
Use the latest version 1.7 overcome this issue. It was not incorporated in
1.6 branch.
On Thu, Apr 29, 2010 at 10:39 PM, Alexander Bruy
wrote:
> Hi all,
>
> when writing a script in Python for processing shapefiles I found
Hi all,
when writing a script in Python for processing shapefiles I found
that I can add to the shapefile new fields with the same name many
times without any error or warning. But AFAIK all fields in shapefile
must have unique field names. Is this a bug and I need to post a
ticket? Or maybe I do
This actually works just as expected but I was being dense. The odd
points with the negative coords are in Alaska and Hawaii which is
outside of this domain. After removing these and accounting for the
image size:
gx = gx % 1073
gy = gy % 689
everything works as expected.
la...@ucar.edu wrot
Also, this is the gdalinfo of the image I am trying to match:
Driver: GTiff/GeoTIFF
Files: /tmp/1725.tif
Size is 1073, 689
Coordinate System is:
PROJCS["unnamed",
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7
Hello,
I'm trying to figure out how to take a list of points and put them on a
mercator projected image using the gdal python bindings. I'm trying to
match it with a NDFD grid that I've been able to create and put on google
maps from a GRIB2 file. This is what I have:
geo = [-14483681.357462916
Franz Schiller wrote:
Greetings
I've been using GDAL for a while without any major issues or
difficulties. But, now I'm facing a difficulty with a gdalwarp
operation. And i hope that someone can help me or giving me a few tips:
I'm trying to do this: Converting a Geotiff to a EPSG 3763 (Portug
Eloi Ribeiro wrote:
Hi,
I keep receiving this warning using GDAL (1.6.3 released 2009/11/19 on
Ubuntu desktop 9.10) whith GRIB2 files:
"Warning: Investigate Template 4.8 bytes 35-41
Warning: Investigate Template 4.8 bytes 35-41
(...)
Warning: Investigate Template 4.8 bytes 35-41
Warning: Inve
Konstantin Baumann wrote:
Motion: GDAL/OGR 1.7.3 RC2 is declared the official 1.7.2 release.
I presume you meant "GDAL/OGR 1.7.3 _RC3_ is declared the official
1.7.2 release."
And I presume you all meant "GDAL/OGR 1.7._2_ _RC3_ is declared the official 1.7.2
release", right? :-)
Yes, my mi
Konstantin Baumann wrote:
Motion: GDAL/OGR 1.7.3 RC2 is declared the official 1.7.2 release.
I presume you meant "GDAL/OGR 1.7.3 _RC3_ is declared the official
1.7.2 release."
And I presume you all meant "GDAL/OGR 1.7._2_ _RC3_ is declared the official 1.7.2
release", right? :-)
Nice cat
Hi,
I keep receiving this warning using GDAL (1.6.3 released 2009/11/19 on
Ubuntu desktop 9.10) whith GRIB2 files:
"Warning: Investigate Template 4.8 bytes 35-41
Warning: Investigate Template 4.8 bytes 35-41
(...)
Warning: Investigate Template 4.8 bytes 35-41
Warning: Investigate Template 4.8 byt
> -Original Message-
> From: gdal-dev-boun...@lists.osgeo.org [mailto:gdal-dev-
> boun...@lists.osgeo.org] On Behalf Of Daniel Morissette
> Sent: Tuesday, April 27, 2010 17:28
> To: gdal-dev
> Subject: Re: [gdal-dev] Motion: Promote GDAL/OGR 1.7.2 RC3 to Final
> Release
>
> Frank Warmerdam
17 matches
Mail list logo
