Boston Sprint 2013 Agenda

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

MapServer
MapServer sprint plan

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.
 * 4) Exact Geometry support
 * 5) Reference Geometry support
 * 6) (SF)CGAL
 * 7) Google SoC 2013
 * 8) 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 ?
 * 4) pgRouting is looking into the possibility of drop CGAL and GAUL dependency to simplify builds
 * 5) pgRouting 2.0 release (working on building that plan now)

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