Difference between revisions of "Toronto Code Sprint 2009 Agenda"

From OSGeo
Jump to navigation Jump to search
Line 31: Line 31:
  
 
*Discuss WKT Raster roadmap and API
 
*Discuss WKT Raster roadmap and API
*Better solution for importer/exporter (raster2pgsql.exe, PGAdmin extension, new Paul's GUI)?
+
*Better solution for importer/exporter (raster2pgsql.exe, PGAdmin extension, new Paul's GUI, driver for GDAL)?
*Driver for GDAL
 
  
 
== GEOS ==
 
== GEOS ==

Revision as of 11:41, 24 January 2009

Theme

Toronto Code Sprint 2009 : The Need for Speed...

Performance is the universal feature, and the latest Geoserver vs Mapserver results indicate that there are places throughout the C stack that can use improvement.

Proj4

  • Run Mapserver under load and review where Proj4 takes a hit (everywhere)
  • Caching of PJ structs, Should make QGIS and Mapserver faster.
  • Parsing of proj strings. Switching from the hand-coded parser to flex-generated parser might yield some improvement.

Mapserver

  • Run the Geoserver benchmark tests under profiler and review results
  • Single-pass querying, will bring WFS speed up to par
  • Mapserver as Apache module, removes FastCGI instability and is potentially even faster, see #2565

GDAL

  • ?

PostGIS

  • Roadmap for 1.5+
  • New on-disk format? Aligned double?
  • New GEOS coordinate sequence to bind on top of aligned PostGIS structures?
  • Profiling and review profile results

PostGIS WKT Raster

  • Discuss WKT Raster roadmap and API
  • Better solution for importer/exporter (raster2pgsql.exe, PGAdmin extension, new Paul's GUI, driver for GDAL)?

GEOS

  • Administrivia, what to do without a full-time maintainer?
  • Roadmap for 3.2?

libLAS

  • Supporting inline streaming compression
  • Win64 builds