Welcome to the Developers PostGIS Wiki!
Everybody is welcome to contribute to this wiki. This wiki is designed for individuals who want to contribute to PostGIS by developing patches or testing out changes.
There will be some sections that are of equal value to both PostGIS users and Developers such as compiling source etc. Feel free to contribute to this and make any corrections you see fit.
- You must login to create new pages and modify existing ones. You can create your own OSGEO Userid or use your existing one or you can use the generic one (login:wiki;password:wiki).
- Please prefix every new page names in this section with "DevWiki" in order to easily distinguish them from other Wiki Trac pages.
- For a quick overview of how to format page's content see this page.
- Directions for getting a backtrace if your query crashes PostGIS.
PostGIS Work Branches
Doxygen Autogenerated Developer Documentation
- PostGIS coding Style Guide
- Code Sprints
- Semantics of EMPTY geometries
- Description of new distance calculation
- How to calculate parameters for affine transformation
- How to calculate "real" parameters from an affine transformation
- Spatial Collection Tutorial
- Topics for discussion on PostGIS 2.0
- Comments/Questions related to ISO19125
- Notes on memory management and code structures in PostGIS
- Code Provenance Review
- FOSS4G2011 Code Sprint Notes
- Grand Unified Configuration Notes
- What functions need a tolerance/precision and how should it be implemented
- Proposal/discussion for clustering functions
Compilation and Installation Guides
- PostgreSQL/PostGIS version support matrix
- More comprehensive list of OS specific install guides
- Directions for PostGIS RPM Installation.
- Directions for PostGIS on Ubuntu.
- Directions for Compiling in Windows.
- Initializing PostgreSQL Data Cluster for testing
- Directions for Creating PostGIS setup.exe for Windows using NSIS.
- Make Check Gotchas.
Patch Submission Guidelines
General model Major.Minor.Micro (1.3.6, 1.4.0,1.5.0SVN)
Basic Steps noted here
We do not release additional functions to micro (aka Patch) releases.
Micro releases will be focused primarily on bug fixes and secondly speed enhancements to existing functions.
PostGIS 3.1 and below will be critical bug and security fixes.
This means that only currently documented functions for PostGIS 3.2 are all you will see in 3.2.1
Bug fixes to existing functions go into latest micro release.
New functions submitted will have to go into the next release (always master branch).
New functions/features that require on disk structural changes will go into next major release.
- Preparing PostgreSQL Specific Regress Tests
- Preparing CUnit Tests
- Preparing Documentation Patches for new features
- Preparing code and other patches
- A step by step guide to contributing to postgis