Feature request #12870

Processing: Add PyGeoprocessing

Added by Filipe Dias almost 9 years ago. Updated almost 7 years ago.

Assignee:Victor Olaya
Pull Request or Patch supplied:No Resolution:wontfix
Easy fix?:No Copied to github as #:20961


Link1: https://pypi.python.org/pypi/pygeoprocessing?utm_source=May+2015+Newsletter&utm_campaign=NatCap+Newsletter&utm_medium=email

Link2: http://www.naturalcapitalproject.org/interview_nirmal_bhagabati_and_pygeoprocessing.html?utm_source=May+2015+Newsletter&utm_campaign=NatCap+Newsletter&utm_medium=email

PyGeoprocessing is a Python/Cython based library that provides a set of commonly
used raster, vector, and hydrological operations for GIS processing. Similar
functionality can be found in ArcGIS/QGIS raster algebra, ArcGIS zonal
statistics, and ArcGIS/GRASS/TauDEM hydrological routing routines.

PyGeoprocessing was developed at the Natural Capital Project to create a
programmable, open source, and free GIS processing library to support the
ecosystem service software InVEST. PyGeoprocessing's design prioritizes
computation and memory efficient runtimes, easy installation and cross
compatibility with other open source and proprietary software licenses, and a
simplified set of orthogonal GIS processing routines that interact with GIS data
via filename. Specifically the functionally provided by PyGeoprocessing includes

  • programmable raster algebra routine (vectorize_datasets)
  • routines for simplified raster creation and statistics
  • integration with vector based geometry in many of the routines
  • a simplified hydrological routing library including,
  • d-infinity flow direction
  • support for plateau drainage
  • weighted and unweighted flow accumulation
  • and weighted and unweighted flow distance
Dependencies include
  • cython>=0.20.2
  • numpy>=1.8.2
  • scipy>=0.13.3
  • shapely>=1.3.3
  • gdal>=1.10.1


#1 Updated by Giovanni Manghi almost 9 years ago

  • Category changed from 94 to Processing/Core

#2 Updated by Giovanni Manghi about 7 years ago

  • Easy fix? set to No

#3 Updated by Nyall Dawson almost 7 years ago

  • Resolution set to wontfix
  • Status changed from Open to Closed
  • Description updated (diff)

I think this report should be closed - we're moving away from including providers by default and leaving their implementation to plugin authors. Therefore this needs to be fixed by someone willing to develop a plugin, not within QGIS itself.

Also available in: Atom PDF