Supports Python 3.8 - 3.10 and GDAL 3.1.x - 3.5.x

Reading to GeoDataFrames requires requires geopandas>=0.8 with pygeos enabled.



This package is available on conda-forge for Linux, MacOS, and Windows.

conda install -c conda-forge pyogrio

This requires compatible versions of GDAL and numpy from conda-forge for raw I/O support and geopandas, pygeos, and their dependencies for GeoDataFrame I/O support.


This package is available on PyPI for Linux, MacOS, and Windows.

pip install pyogrio

This installs binary wheels that include GDAL.

If you get installation errors about Cython or GDAL not being available, this is most likely due to the installation process falling back to installing from the source distribution because the available wheels are not compatible with your platform.

Note: binary wheels are currently limited to x86_64 architectures.

Troubleshooting installation errors

If you install GeoPandas or Fiona using pip, you may encounter issues related to incompatibility of the exact GDAL library pre-installed with Fiona and the version of GDAL that gets compiled with Pyogrio.

This may show up as an exception like this for a supported driver (e.g., ESRI Shapefile):

pyogrio.errors.DataSourceError: Could not obtain driver ...

To get around it, uninstall fiona then reinstall to use system GDAL:

pip uninstall fiona
pip install fiona --no-binary fiona

Then restart your interpreter. This ensures that both Pyogrio and Fiona use exactly the same GDAL library.


Clone this repository to a local folder.

Install an appropriate distribution of GDAL for your system. Either gdal-config must be on your system path (to automatically determine the GDAL paths), or either the GDAL_INCLUDE_PATH, GDAL_LIBRARY_PATH, and GDAL_VERSION environment variables need to be set.

Building Pyogrio requires requires Cython, numpy, and pandas.

Pyogrio follows the GeoPandas Style Guide and uses Black and Flake8 to ensure consistent formatting.

Run python develop to build the extensions in Cython.

Tests are run using pytest:

pytest pyogrio/tests


Install GDAL from an appropriate provider of Windows binaries. We’ve heard that the OSGeo4W works.

To build on Windows, you need to provide additional environment variables or command-line parameters because the location of the GDAL binaries and headers cannot be automatically determined.

Assuming GDAL 3.4.1 is installed to c:\GDAL, you can set the GDAL_INCLUDE_PATH, GDAL_LIBRARY_PATH and GDAL_VERSION environment variables and build as follows:

set GDAL_VERSION=3.4.1
python -m pip install --no-deps --force-reinstall --no-use-pep517 -e . -v

Alternatively, you can pass those options also as command-line parameters:

python -m pip install --install-option=build_ext --install-option="-IC:\GDAL\include" --install-option="-lgdal_i" --install-option="-LC:\GDAL\lib" --install-option="--gdalversion=3.4.1" --no-deps --force-reinstall --no-use-pep517 -e . -v

The location of the GDAL DLLs must be on your system PATH.

--no-use-pep517 is required in order to pass additional options to the build backend (see

Also see .github/test-windows.yml for additional ideas if you run into problems.

Windows is minimally tested; we are currently unable to get automated tests working on our Windows CI.

GDAL and PROJ data files

GDAL requires certain files to be present within a GDAL data folder, as well as a PROJ data folder. These folders are normally detected automatically.

If you have an unusual installation of GDAL and PROJ, you may need to set additional environment variables at runtime in order for these to be correctly detected by GDAL:

  • set GDAL_DATA to the folder containing the GDAL data files (e.g., contains header.dxf) within the installation of GDAL that is used by Pyogrio.

  • set PROJ_LIB to the folder containing the PROJ data files (e.g., contains proj.db)