wiki:WKTRaster/PlanningAndFunding

Version 31 (modified by pracine, 16 years ago) ( diff )

--

PostGIS WKT Raster Planning and Funding

This is the development page of PostGIS WKT Raster - a project extending PostGIS engine with raster support.

If you need support for raster in PostgreSQL or you have to do raster/vector operations, help us develop WKT Raster! WKT Raster developement is a work in progress. Each slice of 2000$ will bring new functions in! The approximate cost of the whole project is about 60 000$US. If 30 groups each give 2000$US, we will have the best seamless raster/vector set of SQL functions available by the end of 2009!

You can contribute with money or developer time. Contributing give you the opportunity to have a word to say on the development priorities and on the schedule.

For financial contribution, the conversion rate between time and money is 1200$ per week ≈ 5000US$ per month ≈ 60 000 US$ per year. Coders have to be experienced C developer with a minimal object oriented database development experience. There are some developers out there willing to offer their services to implement your needs.

We expect that developers will:

  • Try to follow the schedule or at least arrange it to fit their particular needs as much as possible in accordance with the project roadmap. The project is divided into coherent groups of tasks. We are very flexible on modifying the content of those sections.
  • Contribute to the specifications in order to agree and to keep track of what's done. Specifications of the intented development should be described in the Specifications page and submited to the postgis-devel mailing list for comments before starting development. Ask Pierre Racine to get write access to the specification page.
  • Contribute to the Documentation as much as they can to make sure we produce a coherent and a professional open source product.

Tasks are arranged into coherent groups: Similar functions together and dependencies first.

Developers

WKT Raster development team members with officially allocated tasks:

Funding Contributors

Prime financial contributors who established development of the WKT Raster project:

Development Status

Explanation of status markers used in the tables below:

  • to-do: The task has not yet been funded. Everything is to do.
  • funded: Someone committed some funding or developer time and the task has been assigned to a developper but the task is still to do.
  • in-progress: The task is being implemented.
  • pending: The developer is waiting for other development to continue.
  • buggy: The tast has been implemented but is disfunctional for some reason.
  • done: The task is finished.

TODO: - port the big table ~mloskot

Milestones for Beta 0.1.6

Objective 0.1.6a - Being able to create tables with RASTER fields.

Task Developer Schedule Time Funds (USD) Status
Initial setup: type definition, canonical input/output SS January 2009 4 weeks 2400 by SC, 2600 by MD done

Beta 0.1b

Functionality Being able to select RASTER values based on bbox spatial relation.

Task Developer Schedule Time Funds (USD) Status
Spatial operators with semantic matching PostGIS ones SS February 2009 1 week 1200 by TE done
GiST indexing support PR February 2009 1 week 1200 by SC Done

Beta 0.1c

Being able to import TIFF rasters using raster2pgsql.

Task Developer Schedule Time Funds (USD) Status
gdal2wktraster.py as a prototype of raster2pgsql based on GDAL ML February 2009 1 week DT by MD done
raster2pgsql (tiff only, only one band, option for tiling) ? March 2009 4 weeks 4800 to-do

Beta 0.1d

Being able to get all the properties of a raster by use of the following functions:

  • RT_SRID(raster|geometry) -> integer
  • RT_Width(raster) -> integer
  • RT_Height(raster) -> integer
  • RT_XPixelSize(raster) -> float32
  • RT_YPixelSize(raster) -> float32
  • RT_YPixelSize(raster) -> float32
  • RT_XRotation(raster) -> float32
  • RT_YRotation(raster) -> float32
  • RT_XUpperLeft(raster) -> float32
  • RT_YUpperLeft(raster) -> float32
  • RT_GeoReference(raster) -> string
  • RT_NumBands(raster) -> integer
  • RT_GetBandPixelType(raster, band) -> string
  • RT_BandNoDataValue(raster, band) -> float32
Task Developer Schedule Time Funds (USD) Status
Implementation of RASTER properties accessors ML February 2009 1 week DT by MD done

Beta 0.1e

Being able to intersect vector and raster to produce vector. This includes implementation of the following functions:

  • RT_GetBBox(raster) -> polygon geometry
  • RT_Envelope(raster|geometry) -> polygon geometry
  • RT_Shape(raster) -> polygon geometry
  • RT_AsPolygon(raster) -> polygon geometry set
  • RT_Intersects(raster|geometry, raster|geometry)
  • RT_Intersection(raster|geometry, raster|geometry, ‘raster’|’geometry’)->raster/geometry
Task Developer Schedule Time Funds (USD) Status
Implementation of functions producing raster-vector intersections PR April-June 2009 4 weeks 4800 by SC in-progress

Beta 0.1f

Being able to return a JPEG, a TIFF or a PNG. This milestone includes implementation of the following functions:

  • RT_Band(raster, band) -> raster
  • RT_AsJPEG(raster, band, quality) -> JPEG as "bytea"
  • RT_AsTIFF(raster, band, compression) -> TIFF as "bytea"
  • RT_AsPNG(raster, band) -> PNG as "bytea"
Task Developer Schedule Time Funds (USD) Status
Implementation of JPEG, TIFF and PNG output functions ? April 2009 2 weeks 2400 to-do
Note: See TracWiki for help on using the wiki.