Here’s a diff on the .dox for gdaldem, as a suggestion. (I don’t want commit
access on the repository. Is sending the diff by email the appropriate
approach?)
Note I’m assuming that the other modules in gdaldem also assume that x and y
units are the same.
Index: gdal_utilities.dox
==
On 2014-01-24 17:22, Norman Vine wrote:
hmm
this seems to be related to this fairly recent change
http://trac.osgeo.org/gdal/ticket/3732
http://osgeo-org.1560.x6.nabble.com/gdal-dev-Change-of-DECIMAL-PRECISION-in-AAIGrid-td5075524.html
I am just repeating what I wrote in the above-mentioned m
Le vendredi 24 janvier 2014 21:46:50, Simon Richard Proud a écrit :
> Does anyone have any other ideas as to what would be causing gdalwarp to
> output entire blank images when called from a python script? I can get it
> to run using os.system and subprocess.call (using both shell=True and
> shell=
Does anyone have any other ideas as to what would be causing gdalwarp to output
entire blank images when called from a python script?
I can get it to run using os.system and subprocess.call (using both shell=True
and shell=False) but always just get a blank image (all pixels=0). This does
not ha
hmm
this seems to be related to this fairly recent change
http://trac.osgeo.org/gdal/ticket/3732
http://osgeo-org.1560.x6.nabble.com/gdal-dev-Change-of-DECIMAL-PRECISION-in-AAIGrid-td5075524.html
don't know much more
Norman
On Jan 24, 2014, at 11:12 AM, Jonathan Moules
wrote:
> Thanks Norma
Thanks Norman. I'd already seen that page but failed to read it!
However, having tested it, it's not functioning as the manual says.
As best I can tell, DECIMAL_PRECISION=3 should give me 3 decimal places.
But what it instead does it give me 3 significant figures. So 98.354 has
become 98.3.
This b
try
> gdal_translate -of AAIGrid -co DECIMAL_PRECISION=3 abc.vrt abc.asc
see http://www.gdal.org/frmt_various.html
HTH
Norman
On Jan 24, 2014, at 10:01 AM, Jonathan Moules
wrote:
> Hi List,
> I'm trying to mosaic some ASCII grid tiles into a single large ASCII file
> (which can then easily be
Hi List,
I'm trying to mosaic some ASCII grid tiles into a single large ASCII file
(which can then easily be handled).
I'm using this process:
> REM Create list of files
> dir /b /s *.asc > asc_list.txt
>
> REM Turn into VRT
> gdalbuildvrt -srcnodata "-" -vrtnodata "0" -a_srs "EPSG:27700"
>
Dear gdal developers,
I've used gdal_retile.py to retile a set of GeoTIFF files, with 1
grayscale band of type float32. In these files a NoData value is stored. I
used retile to reduce the number of GeoTIFF files from 1300 or so smaller
files to 40 or so larger files. When I use gdalinfo on the or
To Tim Southern -
GDAL uses several different methods find information to georeference
tiff files (Disclaimer: I'm not at all familiar with THE GDAL codebase
and just had a brief look at the relevant c++ files):
1. GDAL look for georeference information embedded in the tiff file and
will u
10 matches
Mail list logo
