wiki:WKTRaster/PlanningAndFunding

Context Navigation

Version 69 (modified by pracine, 14 years ago) ( diff )
—

PostGIS WKT Raster Planning and Funding

Quick Links

WKT Raster Home Page

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

Need raster? - 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!

Time or Money - You can contribute with money or developer time (DevTime). 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.

Expectations - 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.

Advices to developers - We can assure degree of quality with obeying basic rules and development cycle process, most of them are easily executable:

If you add new C API function, always add test case for it in test/core.
If you add new SQL function, always add test case for it in test/regression.
Always do full build of WKT Raster before commit (with new tests included).
Always run all WKT Raster unit tests before commit (with new tests included).
Do not commit anything if any of the two occurs: a) WKT Raster build failed b) WKT Raster tests failed.
Try to do full rebuild and full tests run of all related components: GEOS + PostGIS + WKT Raster.
Frequently check if WKT Raster build is "green" in the very our Hudson bay http://office.refractions.net:1500/view/WKTRaster/
Don't worry if something got broken after a commit. A broken code is a daily bread and errors are valuable. Just don't let buggy commits to accumulate, but fix as soon as first error is spotted.
Adding new test cases are the only time consuming element, but even a very simple test is worth (i.e. test/regress/rt_box2d.sql)

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

Developers

WKT Raster development team members with officially allocated tasks:

Mateusz Loskot (ML) at (Cadcorp)
Pierre Racine (PR) at (University Laval)
Sandro Santilli (SS)
Jorge Arévalo (JA) at (Deimos Space)

Unofficial WKT Raster development members with unofficially allocated tasks:

David Zwarg (DZ) at (Avencia, Inc.)

Funding Contributors

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), (Michigan Tech Research Institute): $1200 USD

Development Status

Explanation of status markers used in the tables below:

todo: 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.

Milestones for Beta 0.1.6

Objectives and Tasks	Coder	Approx. Schedule	Time	Fund (US$)	Status
Objective 0.1.6a - 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
Objective 0.1.6b - 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
Objective 0.1.6c - Being able to load raster in the database (specifications)
gdal2wktraster.py as a prototype of raster2pgsql.exe based on GDAL	ML	February 2009	1 week	DevTime from MD	done
raster2pgsql.exe (tiff only, only one band, option for tiling)	TBD	March 2009	4 weeks	4800	todo
Objective 0.1.6d - Being able to get all the properties of a raster (all the "Get" functions). (specifications)
- ST_SRID(raster\|geometry) → integer - ST_GetWidth(raster) → integer - ST_GetHeight(raster) → integer - ST_GetXPixelSize(raster) → float32 - ST_GetYPixelSize(raster) → float32 - ST_GetYPixelSize(raster) → float32 - ST_GetXRotation(raster) → float32 - ST_GetYRotation(raster) → float32 - ST_GetXUpperLeft(raster) → float32 - ST_GetYUpperLeft(raster) → float32 - ST_GetGeoReference(raster) → string - ST_GetNumBands(raster) → integer - ST_GetBandPixelType(raster, band) → string - ST_GetBandNoDataValue(raster, band) → float32	ML	February 2009	1 weeks	DevTime from MD	done
Objective 0.1.6e - Being able to intersect vector and raster to produce vector. (specifications)
- ST_ConvexHull(raster) → polygon geometry - ST_Envelope(raster\|geometry) → polygon geometry - ST_Shape(raster) → polygon geometry - ST_AsPolygon(raster) → polygon geometry set - ST_Intersects(raster\|geometry, raster\|geometry) - ST_Intersection(raster\|geometry, raster\|geometry, ‘raster’\|’geometry’)→raster/geometry	JA	July - August 2010	4 weeks	4800 by SC / DevTime from JA	in-progress
Objective 0.1.6f - Being able to return a JPEG, a TIFF or a PNG. (specifications)
- ST_Band(raster, band) → raster - ST_AsJPEG(raster, band, quality) → JPEG as "bytea" - ST_AsTIFF(raster, band, compression) → TIFF as "bytea" - ST_AsPNG(raster, band) → PNG as "bytea"	ML	July - August 2010	2 weeks	2400 / DevTime from ML	todo
Objective 0.1.6g - Being able to read and write WKT Raster with GDAL driver. (specifications)
- Read a WKT Raster from database (in-db/out-db, regular/irregular blocking) - Create a new WKT Raster in database (in-db/out-db, regular/irregular blocking)	JA	July - August 2010	4 weeks	DevTime from JA	in-progress

Milestones for Beta 0.2.4

Objectives and Tasks

Coder

Approx. Schedule

Time

Fund (US$)

Status

Objective 0.2.4a - Being able to register TIFF and JPEG tiles as raster stored outside the database. (specifications)
Mostly changes to raster2pgsql.exe and ST_RasterFromText(). - ST_GetPath() → string - ST_SetPath(string)	TBD	November 2010	2 weeks	2400	todo
Objective 0.2.4b - Being able to import JPEG rasters using raster2pgsql.exe. (specifications)
Mostly changes to raster2pgsql.exe	TBD	November 2010	1 week	1200	todo
Objective 0.2.4c - Being able to intersect vector and raster to produce raster. (specifications)
- ST_AsRaster(geometry, pixelsize) → raster - Changes to ST_Intersection	TBD	November 2010	4 weeks	4800	todo
Objective 0.2.4d - Being able to use "group by" to accumulate tiles to form a new raster. (specifications)
- ST_Union(raster\|geometry, raster\|geometry, ‘raster’\|’geometry’) → raster/geometry - ST_Accum(raster set\|geometry set, ‘raster’\|’geometry’) → raster/geometry	TBD	November 2010	2 weeks	2400	todo

Other Important Milestones