Search Results

GDAL 1.9 is available for Oneiric 11.10 in ubuntugis unstable. https://launchpad.net/~ubuntugis/+archive/ubuntugis-unstable? …

I assume you are using GDAL/OGR 1.11 and reading the API tutorial for the latest (2.x) version. The API changed quite a bit between 1.x and 2.x. … The OGR API tutorial for GDAL 1.11 is http://gdal.org/1.11/ogr/ogr_apitut.html …

i.e: subprocess.check_call([r"C:\Path\to\gdalbuildvrt", "-separate", "-input_file_list", inlist, outVRT]) OR os.environ['PATH'] = ';'.join(r'c:\Path\to\gdal\bin\directory',os.environ['PATH']) subprocess.check_call …

No, you'll have to clip to match. But you can speed up the process considerably by writing out a VRT instead of a GeoTIFF. gdalwarp -of VRT -q -cutline convex_hull.shp -tr 0.5 0.5 -of GTiff -srcnoda …

The output data data type defaults to the input data type which is Byte in your case. Your output needs to be floating point as all the values will be between -1 and 1. When the values get written to …

Without downloading the whole gdal package, you can get it from http://svn.osgeo.org/gdal/trunk/gdal/swig/python/scripts/gdalcompare.py …

You have a typo in your command - the 1st argument should be "color-relief" not "color-relif".

I couldn't open it using /vsigzip//vsicurl/ or /vsitar//vsicurl/. It's a tar.gz of multiple files. Your best option is to download it (manually or you can script with curl or wget, or in python vi …

As you've noticed, some GDAL commandline tools support a -q flag, but not all. There's no -q or --quiet type flag in the arguments common to all GDAL raster and vector commandline tools. …

C:\Temp>gdalinfo --version GDAL 1.11.2, released 2015/02/10 I think there are 2 issues: 1. … The Windows NetCDF driver isn't trying to open your .nc file Your answer that says "Under Windows (at least with GDAL installed using the OSGeo4W installer) GDAL comes with an older library for netCDF …

The gdal_calc.py script isn't an executable. Try calling python gdal_calc.py etc... subprocess.call([sys.executable, 'C:\\gdal_calc.py', '-A', 'C:\\a.tif', '--outfile=C:\\result.tif', '--calc="A+1"'] …

ExecuteSQL is a method of a DataSource object, not a Layer. Use something like the following instead: data_source = ogr.Open(dataset) full_lyr = data_source .GetLayer(0) layerName = full_lyr.GetName …

You can use Dataset.RasterCount to test if the dataset is raster and Dataset.GetLayerCount() for vector. Source: http://osgeo-org.1560.x6.nabble.com/Discover-whether-a-GDALDataset-is-raster-or-vector …

(untested as I'm not running GDAL >=2.0dev): from osgeo import gdal def read_vsimem(filepath): """ Read GDAL vsimem files """ vsifile = gdal.VSIFOpenL(filepath,'r') gdal.VSIFSeekL(vsifile, … 0, 2) vsileng = gdal.VSIFTellL(vsifile) gdal.VSIFSeekL(vsifile, 0, 0) return gdal.VSIFReadL(1, vsileng, vsifile) def write_vsimem(filepath,data): """ Write GDAL vsimem files """ vsifile …

Delete that and your .hdr file will work and your .bin will be recognized by GDAL. Even better, use the VRT's suggested by @mdsumner. …