| | 1 | If you are submitting a patch for a new feature, keep in mind we only allow new feature patches for semi-major and major releases, not for minor releases. So for example if the latest stable version of PostGIS is 1.4 or 1.4 is in freeze mode (which usually happens about 2 months or more before planned release), then your new feature must |
| | 2 | go into 1.5. |
| | 3 | |
| | 4 | For new features, we expect documentation as part of the submission. To document a new function, please do the following: |
| | 5 | 1. Make a copy of template.xml located in trunk/doc of the PostGIS subversion repository ([https://svn.osgeo.org/postgis/trunk/doc]) |
| | 6 | 2. Fill in respective information for your new function and make sure to remove anything that is not relevant. |
| | 7 | a. If its not MM compliant please remove that section, but if it is please note the MM section. |
| | 8 | b. If it doesn't support curves, 3D etc., please remove that too. |
| | 9 | |
| | 10 | 3. Make very sure in the Availability part to note the PostGIS version this is slated for and if it relies on GEOS, the minimum GEOS version required. |
| | 11 | |
| | 12 | 4. Name your xml file accordingly e.g. MySuperFunc.xml. |
| | 13 | 5. Submit this as part of your new function patch. |
