Changes between Version 26 and Version 27 of WKTRaster/Documentation01

Timestamp:

Dec 9, 2009, 12:12:01 PM (14 years ago)

Author:

pracine

Comment:

—

WKTRaster/Documentation01

@@ -213 +213 @@
 We also think that this approach is compliant (at least in philosophy) with the ISO 19123 "Abstract Specification Schema for Coverage Geometry and Functions" specification (not to be confused with the OCG Web Coverage Service) in which a coverage can be represented as a point layer, a polygon layer, a TIN layer or a raster layer, and in which any positional value of the coverage is accessible without having to know the data structure upon which the coverage is based.
 
+'''Objective 3: Storage Flexibility (in-db & out-db storage) -''' PostGIS WKT Raster enables the user to simply "register" basic metadata (pixeltype, with, height, georeference, etc…) of images stored in the filesystem, without having to actually load their data values into the database. This way, web or desktop applications:
+
+ * do not have to retrieve images from the database but might instead access them directly from the filesystem (e.g. as JPEG files);
+ * can nevertheless use most PostGIS WKT Raster operators and functions on those rasters, transparently.
+
+This is "out-db" storage as opposed to the more natural "in-db" storage.
+
+
+
 == '''3.2 - Integration with PostGIS''' ==