Changes between Version 1 and Version 2 of WKTRaster/SpecificationWorking01

Timestamp:

04/16/09 07:36:41 (16 years ago)

Author:

pracine

Comment:

—

WKTRaster/SpecificationWorking01

@@ -218 +218 @@
    * polygonize with GDAL or GRASS, that generates some internal structure for those libraries, and you turn that into a WKT form of polygon. That can be passed to PostGIS, and you don't need to link to liblwgeom.[[BR]][[BR]]
  1. Best practice for band referencing: having a band parameter (index?) or always use RT_Band()[[BR]][[BR]]-e.g. SELECT RT_AsTIFF(RT_Band(raster,2),60) FROM coverandtemp[[BR]][[BR]]SELECT RT_AsTIFF(RT_Band(raster,2),RT_Band(raster,1),60) FROM coverandtemp[[BR]]or[[BR]]SELECT RT_AsTIFF(raster,2,60) FROM coverandtemp[[BR]][[BR]]Pierre: Having a band parameter (or a list of band) for each function trying to access a band would be preferable to avoid useless memcopy of band data.[[BR]][[BR]]
- 1. Architecture & design issues:
-
+ 1. Architecture & design issues:[[BR]][[BR]]
    * How to handle no NODATA? Pierre from Frank input: We'll need a HasNoDataValue flag for each band.[[BR]][[BR]]
- 1. Documentation
-
-   * Setup a structure (likely on a Wiki), sections for developers and for users
-
-   * Update existing documents like RFCs - they are out of date.
-
+ 1. Documentation[[BR]][[BR]]
+   * Setup a structure (likely on a Wiki), sections for developers and for users[[BR]][[BR]]
+   * Update existing documents like RFCs - they are out of date.[[BR]][[BR]]
    * Describe key terms: canonical format, serialized format, transfer format (WKB), in-db raster, out-db raster, etc. This should help people to grasp the WKT Raster key elements quickly, and help them to decide which document/RFC to read in details.[[BR]][[BR]]
- 1. Development Roadmap
-
+ 1. Development Roadmap[[BR]][[BR]]
    * Review current schedule.
    * Add note on a website where users should (or should not) expect 1 release - clear statement.