|Version 20 (modified by 13 years ago) ( diff ),|
WKT Raster Planning and Funding
Table of Contents
This is the development page of PostGIS WKT Raster - a project extending PostGIS engine with raster support.
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.
WKT Raster development team members with officially allocated tasks:
Prime financial contributors who established development of the WKT Raster project:
- Steve Cumming (SC): 2400 + 4800 + 4800 + 1200 = $13200 USD
- Martin Daly (MD), (Cadcorp): $2600 USD and 2 weeks of Development Time (DT)
- Tyler Erickson (TE): $1200 USD
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 of development of Beta 0.1.
Being able to create tables with RASTER fields.
|Initial setup: type definition, canonical input/output||SS||January 2009||4 weeks||2400 by SC, 2600 by MD||done|
Being able to select RASTER values based on bbox spatial relation.
|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|
Being able to import TIFF rasters using raster2pgsql.
|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)||TBD||March 2009||4 weeks||4800||to-do|
Being able to get all the properties of a raster (all the Get functions).
|'''Objective, Task'''||'''Developer'''||'''Schedule'''||'''Time'''||'''Funds (USD)'''||'''Status'''|
||ML||February 2009||1 week||DT by MD||done|
Being able to intersect vector and raster to produce vector.
|Implementation of functions: RT_GetBBox, RT_Envelope, RT_Shape, RT_AsPolygon, RT_Intersects, RT_Intersection||PR||April-June 2009||4 weeks||4800 by SC||in-progress|
Being able to return a JPEG, a TIFF or a PNG.