| | 106 | ----------- |
| | 107 | |
| | 108 | = PostGIS Code Sprint Notes = |
| | 109 | |
| | 110 | == Topic #1: What is bad about PostGIS now? == |
| | 111 | |
| | 112 | * Upgrades (history, backwards compatibility) |
| | 113 | * Repeated code blocks everywhere |
| | 114 | * Windows build/test situation (there is nothing standard) |
| | 115 | * We need a build farm |
| | 116 | * We have similar issues with 32-bit/64-bit testing on any OS |
| | 117 | * harder to catch 64-bit issues |
| | 118 | * Dependencies++ (so many of them, and more coming) |
| | 119 | * GEOS (too slow? maybe) |
| | 120 | * Translations (documentation, untranslated; GUI, untranslated) |
| | 121 | * Inconsistent function names (still) ST_this_thing versus ST_ThisThing |
| | 122 | * Versioning of loaders shp2pgsql, shp2pgsql-gui, etc. |
| | 123 | * if you install a lower version of PostGIS after newer version, it overwrites these files |
| | 124 | * 2.0.1 doesn't work for 9.2 |
| | 125 | * http://trac.osgeo.org/postgis/ticket/1820 (not sure where to put the include I described - in one file or all 3) - I accidentally committed but lower versions still seem to work (so this is working) |
| | 126 | topology however is broken ( http://trac.osgeo.org/postgis/ticket/1822 ) -- we probably shouldn't even have ALTER in creation script. |
| | 127 | |
| | 128 | == Discussion #1: GIT == |
| | 129 | |
| | 130 | * Do we want to move to git? |
| | 131 | * Yes. No. Advantages not so high to be worth the time/effort. Willing to move to git when someone steps up to do the migration, but migration MUST include trac tickets and history and links from commits to tickets to commits. |
| | 132 | * Decision: A svn clone will be added to the github postgis account, updated hourly automatically, so that git-lovers can clone/work from the same repo. |
| | 133 | |
| | 134 | == Discussion #2: CGAL == |
| | 135 | |
| | 136 | * Olivier, interest in CGAL is driven by 3D operations. Starting from an existing base of functionality rather than re-inventing parts. |
| | 137 | Triangulations, etc. |
| | 138 | * CGAL has CMake build system. |
| | 139 | |
| | 140 | == Discussion #3: GEOS == |
| | 141 | |
| | 142 | * MCA: worried about future of GEOS, the performance and design as inherited from JTS is not optimal, and the code is very specialist to the geospatial community |
| | 143 | * ML: when working on raster, advoctated for implementing algorithms natively, linking GDAL is bad idea when the algorithms you need are not so big |
| | 144 | * SS: GEOS is good enough, problem is not language or pattern, it's mostly just algorithms that can be made better |
| | 145 | * MB: BoostGeometry is very flexible, but, that's a drawback, it's hard to understand and get involved. |
| | 146 | * ML: For BoostGeometry, there are users, and questions (use of the library means specifying and generating custom library and test its behaviour -> complex task) , the project is alive. |
| | 147 | * SS: Extend the C-API to provide custom allocators (will also automatically provide interruptability when the allocators are installed by postgis) |
| | 148 | |
| | 149 | == Discussion #4: Raster improvements == |
| | 150 | |
| | 151 | * Faster ST_Union (dustymugs, pramsey fight it out) |
| | 152 | * should be part of larger map algebra rewrite for aggregate support |
| | 153 | * Aggregate versions of stats functions (dustymugs) |
| | 154 | * Faster out-of-db data loading (dustymugs) |
| | 155 | * current testing has shown that in-db is several times faster |
| | 156 | * GDAL |
| | 157 | * Irregular grid support (DZ) |
| | 158 | * Mapalgebra Nearest Neighborhood (ngb) (is there anything we can do about the border edges) perhaps an aggregate ngb function? (might be useful if n tiles in = n tiles out) but ngb operation works on adjacent tiles so you get same solution as ngb of a single raster retiled back out |
| | 159 | * GUI raster loader similar to shp2pgsql-gui |
| | 160 | * Function to Ununion (tilify in the db) |
| | 161 | |
| | 162 | == 2.1 Topics: MCA == |
| | 163 | |
| | 164 | * Performance of new libraries |
| | 165 | * Integration of new libraries |
| | 166 | * Changing build -- are we committed to CMake or not? |
| | 167 | |
| | 168 | == 2.1 Topics: SS == |
| | 169 | |
| | 170 | * EPSG code detection in loader |
| | 171 | * Faster (raster) reprojection |
| | 172 | * strk, can you elaborate on this? |
| | 173 | |
| | 174 | == 2.1 Topics: OC == |
| | 175 | |
| | 176 | * GML 3.2 support (for INSPIRE) |
| | 177 | * add an ID to every geometry |
| | 178 | * geometry_from_* in liblwgeom dir |
| | 179 | * Explore new topo libraries (3D context) |
| | 180 | |
| | 181 | == 2.1 Topics: PR == |
| | 182 | |
| | 183 | * Internal tree for geometry/geography |
| | 184 | * POINTCLOUD |
| | 185 | |
| | 186 | |
