Boston Sprint 2013 Agenda

Meeting times and locations can be found: Boston Code Sprint 2013

PostGIS / pgRouting

General Stuff

1. When are we going to release 2.1. Steps remaining before we can
2. SpGist -- when is that going to happen will make cut for 2.1 or push to 2.2
3. How best to integrate Oslandia 3D work, concerns etc.
   1. Exact Geometry support
   2. Reference Geometry support
   3. (SF)CGAL
4. Google SoC 2013
5. Regression suites (performance, valgrind?)

Geocoding specific stuff

1. Integrating Steve Woodbridge - address normalizer into PostGIS
2. Packaging as part of windows builds at very least

pgRouting

1. Packaging pgRouting for windows to be availabe in stack builder along side PostGIS
2. Discussion of how pgRouting / PostGIS can better work together and melding the two projects
3. Side note both Oslandia 3D work and pgRouting both use CGAL, possible opportunity/concern there ?
   1. I am looking into the possibility of drop CGAL and GAUL dependency to simplify builds
4. pgRouting 2.0 release (working on building that plan now)

Raster

1. Raster seems in darn good shape for 2.1 so least worried about raster. Great job :)
2. Raster WKB version 1 format to address shortcomings of version 0 related to out-db rasters
3. Rework of MapAlgebra for 2.1 or push to 2.2
   1. Performance of expression-based mapalgebra
   2. Performance of ST_Clip
4. GDAL raster driver - good support for overviews, irregularly tiled coverage. Some nice todo improvements:
   1.  Add write support. Related ticket #4617
   2.  Fix bug with metadata precission. Related ticket #4214
   3.  Check out-db raster support. Related ticket #3234
   4. Low range pixel type should be transformed to a higher one. Related ticket #4562
   5. Check tickets #4531, #4560 and #4561
   6. Rewrite tests (gdal_autotest). Related ticket #5010
   7. More tests with Mapserver. Related ticket #5010
   8.  Tests with QGIS plugin. Related ticket #5010
   9. Deal with really BIG raster data in IRasterIO (recursion? split in several calls?). Related ticket #5012
   10.  Take default user, host, password. Related ticket #4533
   11.  Review SQL strings (avoid SQL injection). Related ticket #5013
   12. Take care of locale (I needed to export LC_ALL=C to make it work with QGIS). Related ticket #5014
   13.  Allow user to specify resolution strategy when dealing with different pixel size sources (maybe an option in connection string). Related ticket #5011
   14.  Allow user to specify the desired srid when dealing with different srids. Related ticket #5011
5. QGIS - good support for large coverage (overviews, irregularly tiled coverage), import export. What need to be enhanced?
6. ST_CreateOverview()
7. Test performance of ST_Union() when number of pixel increase
8. Define another (faster?) way to rasterize a vector coverage with ST_MakeEmptyTiledCovererage(), ST_BurnToRaster(geometry, raster) & ST_UnionToRaster()
9. Discuss a more flexible way to rasterize a vector coverage
10. Raster using pthreads in the future?
11. Rewrite parts of raster2pgsql
12. pgsql2raster prototype?
13. Discuss "PostGIS Extra PL/pgSQL Function Set"
14. Discuss interpolation - from some point, from millions of points
15. Test regular blocking constraint
16. Discuss viewshed
17. Discuss integration of raster2pgsql into the GUI