View source for Boston Sprint 2013 Agenda

Meeting times and locations can be found: [[Boston Code Sprint 2013]]
=== MapServer ===
[https://github.com/mapserver/mapserver/wiki/Boston-Codesprint-Agenda MapServer sprint plan]

=== GDAL ===
The List
# PostGIS Raster driver (see below)

=== PostGIS / pgRouting ===
General Stuff
# Tutorials for the website
# When are we going to release 2.1.  Steps remaining before we can
# SpGist -- when is that going to happen will make cut for 2.1 or push to 2.2
# How best to integrate Oslandia 3D work, concerns etc.
## Exact Geometry support
## Reference Geometry support
## (SF)CGAL
# Google SoC 2013
# Regression suites (performance, valgrind?)

Geocoding specific stuff
# Integrating Steve Woodbridge - address normalizer into PostGIS
# Packaging as part of windows builds at very least

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

=== PostGIS Raster ===

'''Assigned task'''
# Ticket review (Pierre, Bborie & Regina)
# Raster WKB version 1 format to address shortcomings of version 0 related to out-db rasters (Bborie)
# Performance of expression-based mapalgebra (Bborie)

'''Not yet assigned'''
# QGIS - good support for large coverage (overviews, irregularly tiled coverage), import export. What need to be enhanced?
# ST_CreateOverview()
# Discuss ST_SetZFromRaster(geometry, raster, band) (what about a vertex iterator similar to ST_MapAlgebraFct)
# Test performance of ST_Union() when number of pixel increase
# Define another (faster?) way to rasterize a vector coverage with ST_MakeEmptyTiledCovererage(), ST_BurnToRaster(geometry, raster) & ST_UnionToRaster()
# Discuss a more flexible way to rasterize a vector coverage using ST_MapAlgebraFct()
# Raster using pthreads in the future?
# Rewrite parts of raster2pgsql
# pgsql2raster prototype?
# Discuss "PostGIS Extra PL/pgSQL Function Set"
# Discuss interpolation - from some point, from millions of points
# Test regular blocking constraint
# Discuss viewshed
# ST_SlitToGrid(geometry, x, y)
# Discuss integration of raster2pgsql into the GUI

=== GDAL raster driver (Jorge & David) ===
# GDAL raster driver - good support for overviews, irregularly tiled coverage. There are some nice todo improvements, in no particular order:
## Add write support. Related ticket [http://trac.osgeo.org/gdal/ticket/4617 #4617]
## Improve reading speed. Related ticket [http://trac.osgeo.org/gdal/ticket/5016 #5016]
## Fix bug with metadata precission. Related ticket [http://trac.osgeo.org/gdal/ticket/4214 #4214]
## Check out-db raster support. Related ticket [http://trac.osgeo.org/gdal/ticket/3234 #3234]
## Low range pixel type should be transformed to a higher one. Related ticket [http://trac.osgeo.org/gdal/ticket/4562 #4562]
## Check tickets [http://trac.osgeo.org/gdal/ticket/4531 #4531], [http://trac.osgeo.org/gdal/ticket/4560 #4560] and [http://trac.osgeo.org/gdal/ticket/4561 #4561]
## Rewrite tests (gdal_autotest). Related ticket [http://trac.osgeo.org/gdal/ticket/5010 #5010]
## More tests with Mapserver. Related ticket [http://trac.osgeo.org/gdal/ticket/5010 #5010]
## Tests with QGIS plugin. Related ticket [http://trac.osgeo.org/gdal/ticket/5010 #5010]
## Deal with really BIG raster data in IRasterIO (recursion? split in several calls?). Related ticket [http://trac.osgeo.org/gdal/ticket/5012 #5012]
## Take default user, host, password. Related ticket [http://trac.osgeo.org/gdal/ticket/4533 #4533]
## Review SQL strings (avoid SQL injection). Related ticket [http://trac.osgeo.org/gdal/ticket/5013 #5013]
## Take care of locale (I needed to export LC_ALL=C to make it work with QGIS). Related ticket [http://trac.osgeo.org/gdal/ticket/5014 #5014]
## Allow user to specify resolution strategy when dealing with different pixel size sources (maybe an option in connection string). Related ticket [http://trac.osgeo.org/gdal/ticket/5011 #5011]
## Allow user to specify the desired srid when dealing with different srids. Related ticket [http://trac.osgeo.org/gdal/ticket/5011 #5011]

=== ZOO-Project ===
[http://www.zoo-project.org/trac/wiki/OSGeoCodeSprint2013 ZOO sprint plan]

=== PDAL ===