Changes between Version 107 and Version 108 of WKTRaster/SpecificationWorking01


Ignore:
Timestamp:
Jan 21, 2010, 10:34:27 PM (14 years ago)
Author:
pracine
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • WKTRaster/SpecificationWorking01

    v107 v108  
    632632 3. This prevent us from constantly having to adjust our code to changes in the PostGIS C API.
    633633
     634----
     635== '''The pros and cons of using GDAL VS implementing our own raster services''' ==
     636
     637A discussion is going on to find if we are better to use GDAL for most raster operations or if we should reimplement our own C raster functions them being based on GDAL algorythms or anything else. Here are the pros and cons of using GDAL:
     638
     639'''Pros'''
     640
     641 * We do not have to reinvent the whell for many WKT Raster functions (AsPolygon, AsRaster, AsJPEG, AsTIFF, AsPNG, etc...). This means a shorter WKT Raster development time.
     642
     643 * We can contribute to GDAL by fixing bugs and sometime implement new features. Actually most new WKT Raster features (eg. ST_MapAlgebra()) could be implemented in GDAL by WKT Raster folks and then used by WKT Raster.
     644
     645'''Cons'''
     646
     647 * We must translation WKT Raster WKB to GDALDataset with bands (likely using GDAL MEM driver).
     648
     649 * We must compile and link with GDAL.
     650
     651 
    634652== '''Specification Comments following the Code Sprint''' ==
    635653