Even,
Thanks for the quick response. Yeah, I goofed, I meant to say units, guess
I am just getting old. Anyway, thanks for pointing me in the right
direction!
Best regards,
Martin
-Original Message-
From: Even Rouault [mailto:even.roua...@mines-paris.org]
Sent: Thursday, July 10, 201
Martin,
Yes this issue has been reported several times (last time was
http://lists.osgeo.org/pipermail/gdal-dev/2014-May/039251.html) and is a GDAL
bug that the user code shouldn't compensate for. I think it is
https://trac.osgeo.org/gdal/ticket/3901 /
https://trac.osgeo.org/gdal/ticket/4954
Frank, Even or whoever,
I have a source geotiff that has the following projection:
PROJCS["State
Plane",GEOGCS["NAD83",DATUM["North_American_Datum_1983",SPHEROID["GRS
1980",6378137,298.2572221010002,AUTHORITY["EPSG","7019"]],AUTHORITY["EPSG"
,"6269"]],PRIMEM["Greenwich",0],UNIT["degree",0.0
Frank, Even or whoever,
I have a source geotiff that has the following projection:
PROJCS["State
Plane",GEOGCS["NAD83",DATUM["North_American_Datum_1983",SPHEROID["GRS
1980",6378137,298.2572221010002,AUTHORITY["EPSG","7019"]],AUTHORITY["EPSG"
,"6269"]],PRIMEM["Greenwich",0],UNIT["degree",0.0
Hello,
I’m interested in this thread. One comment I can add about gdal_merge.py is
that it does not properly handle nodata values from the full (padded) extent of
the input files. gdalwarp, which can be VERY slow, does handle the nodata
values correctly.
Michele Thornton
From: gdal-dev-boun
I am wondering why you are using gdalwarp for mosaicing images having same
projection instead of gdal_merge.py?
Bas Smit
On Thu, Jul 10, 2014 at 7:14 PM, Chaitanya kumar CH
wrote:
> garfy,
>
> Please provide the gdalwarp command you used. Did you modify GDAL_CACHEMAX?
>
>
> On Thu, Jul 10, 201
Selon Nik Sands :
> PS. (This always happens just AFTER I send to the list, no matter how long I
> mull it over first...)
>
> Actually, I think I see the issue now. The closing bracket is the end of an
> "if ()" stanza in which there is no content at all if neither
> 'HAVE_AVX_AT_COMPILE_TIME' o
Thanks a lot, i was using a version that came with the outdated FWTools.
Works great with the new binaries (1.11) from gisinternals.com
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Unable-to-read-PDS3-img-lbl-Moon-DEM-tp5150432p5150457.html
Sent from the GDAL - Dev maili
garfy,
Please provide the gdalwarp command you used. Did you modify GDAL_CACHEMAX?
On Thu, Jul 10, 2014 at 3:26 PM, garfy wrote:
> Dear All,
>
> I am trying to generate mosaic of 28 input images using *gdalwarp*.
> All are in same projection. It has taken 5 days to generate the final
> output.
Dear All,
I am trying to generate mosaic of 28 input images using gdalwarp.
All are in same projection. It has taken 5 days to generate the final
output.
Please find the gdalinfo of input and output attached. The input files are
passed to warp in the order in which the gdalinfo is present in th
Dear All,
I am trying to generate mosaic of 28 input images using *gdalwarp*.
All are in same projection. It has taken 5 days to generate the final
output.
Please find the gdalinfo of input and output attached. The input files are
passed to warp in the order in which the gdalinfo is present in the
Selon GrJo :
> I've tried to access a lunar elevation model, but gdalinfo and gdal_translate
> give me a strange error message.
>
> "Error1: Sample_bits of 0 is not supported in this gdal PDS reader"
>
> The elevation model is a PDS3 pair (.img with seperate .lbl file), and
> pointing gdalinfo to
Nik,
By using GetFeature() the way you do, you assume that the passed parameter is an
index number whereas it is a feature identifier. In most drivers that don't
really support the concept of feature identifier, both concepts are identical.
But in FileGDB, Feature Identifiers start at 1, and not 0
Hi Martin,
I would say that your Zsj layer is a non-spatial layer. Is it the case ?
If yes, then the output of the log and the content of geometry_columns are
consistant. You may not see it directly when running ogrinfo on the PostGIS DB
since by default only spatial layers are listed. You can how
I've tried to access a lunar elevation model, but gdalinfo and gdal_translate
give me a strange error message.
"Error1: Sample_bits of 0 is not supported in this gdal PDS reader"
The elevation model is a PDS3 pair (.img with seperate .lbl file), and
pointing gdalinfo to the lbl file gives me the
15 matches
Mail list logo
