To help you get started, we've collected the most common ways that GDAL is being used within popular public projects.

sourcepole / ogrtools / ogrtools / pyogr / ogr2ogr.py View on Github

pfnProgress, pProgressArg):
                print(
                    "Terminating translation prematurely after failed\n" +
                    "translation from sql statement.")

                return False

            poDS.ReleaseResultSet(poResultSet)


#/* -------------------------------------------------------------------- */
#/*      Special case for layer interleaving mode.                       */
#/* -------------------------------------------------------------------- */
    elif bSrcIsOSM and gdal.GetConfigOption("OGR_INTERLEAVED_READING", None) is None:

        gdal.SetConfigOption("OGR_INTERLEAVED_READING", "YES")

        # if (bSplitListFields)
        #{
        #    fprintf( stderr, "FAILURE: -splitlistfields not supported in this mode\n" );
        #    exit( 1 );
        #}

        nSrcLayerCount = poDS.GetLayerCount()
        pasAssocLayers = [AssociatedLayers() for i in range(nSrcLayerCount)]

#/* -------------------------------------------------------------------- */
#/*      Special case to improve user experience when translating into   */
#/*      single file shapefile and source has only one layer, and that   */
#/*      the layer name isn't specified                                  */
#/* -------------------------------------------------------------------- */

View more ways to use GDAL

GDAL/OGR in Python

This Python package and extensions are a number of tools for programming and manipulating the GDAL Geospatial Data Abstraction Library. Generally speaking the classes and methods mostly match those of the GDAL and OGR C++ classes. There is no Python specific reference documentation, but the includes Python examples.

The GDAL Python package is built using SWIG. The GDAL project maintains these Python bindings for GDAL/OGR within the gdal source tree. The SWIG-generated files are not checked in and are not part of the gdal release tarballs. The bindings are also made available via PyPi where the swig-generated files are provided.

Building from source

To build from source, there are multiple possible paths.

Dependencies

(As usual, when a package is listed one needs the parts used to build programs against it, called -devel on many systems. This is not special about gdal.)

> - SWIG (4 or greater). > - libgdal (3.10.0 or greater). > - numpy (1.0.0 or greater). This is not force-required by the build, > but many examples and utilities will not work without it. At least > osgeo.gdal_array requires numpy at build time; building without > numpy and installing it later does not result in correct > operation. apparently not and in any case it is an unwarranted > leap. > - setuptools (python) > - wheel (python)

Building when building the rest of GDAL

Python bindings are generated by default when building GDAL from source. For more detail, see Python bindings options

Building just the bindings, from the full tree

Another is to use the gdal source distribution with an already-installed gdal library and headers. To do this, one must create a build directory and run cmake to generate build scripts. Then, run cmake --build . --target python_generated_files. Finally, in swig/python, one can build using setup.py like any other distributed python module.

Building from the PyPi module file

The third is to obtain the PyPi-hosted module file, within which swig has been run; this saves running cmake and generating bindings. See HOWTO-RELEASE for how this is created. Because swig has been run, it need not be installed.

Installation via packging systems

General

Many packaging systems (on GNU/Linux, various BSDs) provide the bindings as a package. Specific instruction are given in cases when that hint might not be sufficient.

pip

Due to the complex nature of GDAL and its components, different bindings may require additional packages and installation steps. GDAL can be installed from the Python Package Index:

pip install gdal

In order to enable numpy-based raster support, libgdal and its development headers must be installed as well as the Python packages numpy, setuptools, and wheel. To install the Python dependencies and build numpy-based raster support:

pip install numpy>1.0.0 wheel setuptools>=67
pip install gdal[numpy]=="$(gdal-config --version).*"

Users can verify that numpy-based raster support has been installed with:

python3 -c 'from osgeo import gdal_array'

If this command raises an ImportError, numpy-based raster support has not been properly installed:

Traceback (most recent call last):
File "", line 1, in 
File "/usr/local/lib/python3.12/dist-packages/osgeo/gdal_array.py", line 10, in 
  from . import _gdal_array
ImportError: cannot import name '_gdal_array' from 'osgeo' (/usr/local/lib/python3.12/dist-packages/osgeo/__init__.py)

This is most often due to pip reusing a cached GDAL installation. Verify that the necessary dependencies have been installed and then run the following to force a clean build:

pip install --no-cache --force-reinstall gdal[numpy]=="$(gdal-config --version).*"

Potential issues with GDAL >= 3.9, Python >= 3.9 and NumPy 2.0 (pip)

The pyproject.toml file of GDAL 3.9 requires numpy >= 2.0.0rc1 (for Python >= 3.9) at build time to be able to build bindings that are compatible of both NumPy 1 and NumPy 2. If for some reason the numpy >= 2.0.0rc1 build dependency can not be installed, it is possible to manually install the build requirements, and invoke pip install with the --no-build-isolation flag.

pip install numpy== wheel setuptools>=67
pip install gdal[numpy]=="$(gdal-config --version).*" --no-build-isolation

Conda

GDAL can be quite complex to build and install, particularly on Windows and MacOS. Pre built binaries are provided for the conda system:

By the conda-forge project:

Once you have Anaconda or Miniconda installed, you should be able to install GDAL with:

conda install -c conda-forge gdal

Usage

Imports

There are five major modules that are included with the GDAL Python bindings.:

>>> from osgeo import gdal
>>> from osgeo import ogr
>>> from osgeo import osr
>>> from osgeo import gdal_array
>>> from osgeo import gdalconst

API

API documentation is available at

Numpy

One advanced feature of the GDAL Python bindings not found in the other language bindings is integration with the Python numerical array facilities. The gdal.Dataset.ReadAsArray() method can be used to read raster data as numerical arrays, ready to use with the Python numerical array capabilities.

Tutorials

See

Gotchas

Although GDAL's and OGR's Python bindings provide a fairly "Pythonic" wrapper around the underlying C++ code, there are several ways in which the Python bindings differ from typical Python libraries. These differences can catch Python programmers by surprise and lead to unexpected results. These differences result from the complexity of developing a large, long-lived library while continuing to maintain backward compatibility. They are being addressed over time, but until they are all gone, please review this list of

Examples

• An assortment of other samples are available in the Python github samples directory with some description in the .
• Several GDAL utilities are implemented in Python and can be useful examples.
• The majority of GDAL regression tests are written in Python. They are available at

One example of GDAL/numpy integration is found in the val_repl.py script.