Required Supported Versions GEOS Geometry Engine Open Source Yes 3.4, 3.3, 3.2 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction and solutions. 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 4 Harvard Graduate School of Design

Required Supported Versions GEOS Geometry Engine Open Source Yes 3.4, 3.3, 3.2 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction so' Footnotes 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 4 Harvard Graduate School of Design

Required Supported Versions GEOS Geometry Engine Open Source Yes 3.6, 3.5, 3.4 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.9, 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction rid-X.Y.tar.gz 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 800 Chapter 6. API Reference Django

Supported Versions GEOS Geometry Engine Open Source Yes 3.6, 3.5, 3.4, 3.3 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.9, 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction shifting files1: 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 4 Terry A. Slocum, Robert B. McMaster

Required Supported Versions GEOS Geometry Engine Open Source Yes 3.4, 3.3 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.9, 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction raster spatial data 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 4 Terry A. Slocum, Robert B. McMaster

Supported Versions GEOS Geometry Engine Open Source Yes 3.6, 3.5, 3.4, 3.3 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.9, 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction so' Footnotes 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 4 Terry A. Slocum, Robert B. McMaster

Required Supported Versions GEOS Geometry Engine Open Source Yes 3.4, 3.3 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.9, 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction so' Footnotes [1] The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. [4] Terry A. Slocum, Robert B

Required Supported Versions GEOS Geometry Engine Open Source Yes 3.6, 3.5, 3.4 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.9, 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction so' Footnotes 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 4 Terry A. Slocum, Robert B. McMaster

Required Supported Versions GEOS Geometry Engine Open Source Yes 3.6, 3.5, 3.4 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.9, 4.8, 4.7, 4.6, 4.5, 4.4 GDAL Geospatial Data Abstraction shifting files1: 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 4 Terry A. Slocum, Robert B. McMaster

Supported Versions GEOS Geometry Engine Open Source Yes 3.7, 3.6, 3.5, 3.4 PROJ.4 Cartographic Projections library Yes (PostgreSQL and SQLite only) 5.2, 5.1, 5.0, 4.x GDAL Geospatial Data Abstraction so' Footnotes 1 The datum shifting files are needed for converting data to and from certain projections. For example, the PROJ.4 string for the Google projection (900913 or 3857) requires the null grid EPSG (European Petroleum Survey Group) identifier. However, it may also be associated with custom projections defined in spatial database’s spatial reference systems table. 4 Terry A. Slocum, Robert B. McMaster