When the source image band having pixel values in the range of 52 and 207
is warped using the following command:
gdal_warp -t_srs wgs84 -r near in_file out_file
The resulted band has the pixel values in the range of 0 and 255 How can I
make the range unchanged during warp?
Bas Smit
Le mercredi 09 juillet 2014 10:49:34, bas smit a écrit :
When the source image band having pixel values in the range of 52 and 207
is warped using the following command:
gdal_warp -t_srs wgs84 -r near in_file out_file
The resulted band has the pixel values in the range of 0 and 255 How can I
The SPOT 5 DIMAP format when translated by gdal, does not report map
information (geotransform and projection), and when it is warped the map
information differs than the result by ENVI software.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
I am interested in using gdalbuildvrt.exe and gdal_translate.exe for
creating a mosaic from a very large number of input files using command
line.
For this purpose, which binary (version/release/distribution/build number)
is preferred to speedup the mosaicing process?
While merging the files using gdal_merge.py the following code works:
subprocess.call([sys.executable,gmerge,'-o','C:\\r.tif','-of','GTiff','D:\\a.tif','D:\\b.tif'],shell=True)
However, when the input files are numerous, each file can not be inserted
separately. In this case, the following code
Hi all,
I have a Python script which converts data from GML (VFR) to PostGIS.
When I am overwriting existing layers in PostGIS, not all layers are
really created. First existing layers are deleted [1] and than created
[2] from scratch.
Steps to reproduce (`git clone
this is not really related to gdal but to python... you should try using
shell=False and adding the entire command in one argument instead of an
array, but I'm not sure that the file globbing (*.tif) would work.
On Wed, Jul 9, 2014 at 12:31 PM, bas smit baspys...@gmail.com wrote:
While merging
Try:
import glob
tifs=glob.glob('D:/*.tif')
subprocess.call([sys.executable,gmerge,'-o','C:/r.tif','-of','GTiff']+tifs)
Luke
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-feeding-input-files-into-gdal-merge-py-tp5150332p5150377.html
Sent from the GDAL - Dev
Hi all,
I'm attempting to upgrade my iOS app from GDAL 1.10.1 to 1.11.0 in order to
take advantage of the new OpenFileGDB driver. However, I've been unable to get
it to compile for iOS so far with the error output below (note that in this
instance it is attempting to compile for i386 for the
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' or 'HAVE_SSE_AT_COMPILE_TIME'
I got around this by disabling both sse and avx at configure, --with-sse=no
--with-avx=no.
-
Jesse
On Jul 9, 2014, at 6:12 PM, Nik Sands nix...@nixanz.com wrote:
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
Hi GDAL devs,
I'm trying to support ESRI File Geodatabase support (read-only) in my iOS app
and have recently got GDAL 1.11.0 compiled and running in the app for its new
OpenFileGDB driver. However, I've been unable to extract features from GDBs
using the exact same code that works fine for
Even
To my surprise, I just got the same result. Further investigation
finds the real problem. You probably noticed the transparent region
in the tif file produced. I needed the image to have a white
background and after many failed attempts to do that within GDAL
finally decided to use
13 matches
Mail list logo
