Difference between revisions of "Boston Sprint 2013 Agenda"
Jump to navigation
Jump to search
Line 15: | Line 15: | ||
# How best to integrate Oslandia 3D work, concerns etc. | # How best to integrate Oslandia 3D work, concerns etc. | ||
# Google SoC 2013 | # Google SoC 2013 | ||
+ | # Regression suites (performance, valgrind?) | ||
Geocoding specific stuff | Geocoding specific stuff | ||
Line 28: | Line 29: | ||
# Raster seems in darn good shape for 2.1 so least worried about raster. Great job :) | # Raster seems in darn good shape for 2.1 so least worried about raster. Great job :) | ||
# Rework of MapAlgebra for 2.1 or push to 2.2 | # Rework of MapAlgebra for 2.1 or push to 2.2 | ||
− | ## Performance of expression-based mapalgebra | + | ## Performance of expression-based mapalgebra |
# GDAL raster driver | # GDAL raster driver | ||
# Raster using pthreads in the future? | # Raster using pthreads in the future? |
Revision as of 10:52, 19 February 2013
MapServer
GDAL
PostGIS / pgRouting
General Stuff
- 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.
- 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 ?
Raster
- Raster seems in darn good shape for 2.1 so least worried about raster. Great job :)
- Rework of MapAlgebra for 2.1 or push to 2.2
- Performance of expression-based mapalgebra
- GDAL raster driver
- Raster using pthreads in the future?
- Rewrite parts of raster2pgsql