Changes between Version 2 and Version 3 of WKTRaster/SpecificationFinal01


Ignore:
Timestamp:
Apr 16, 2009, 8:36:23 AM (15 years ago)
Author:
pracine
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • WKTRaster/SpecificationFinal01

    v2 v3  
    108108
    109109----
     110== '''RASTER_COLUMNS Metadata Table''' ==
     111
     112The following metadata table provides external applications and possibly internal tools the ability to discover tables with raster data, and to learn various information about those datasets.
     113
     114|| '''Column Name''' || '''Type''' || '''Constraints''' || '''Comments''' ||
     115|| r_table_catalog || character varying(256) || NOT NULL || ||
     116|| r_table_schema || character varying(256) || NOT NULL || ||
     117|| r_table_name || character varying(256) || NOT NULL || ||
     118|| r_column || character varying(256) || NOT NULL || ||
     119|| srid || integer || NOT NULL || Use 0 for unknown SRID ||
     120|| pixel_types || ARRAY[[=VARCHAR=]] || NOT NULL || an array of pixeltypes, one per band.  The band count is implicit in the size of this array.||
     121|| out_db || boolean || NOT NULL || false if internal tiles, true if tiles are references to files outside the database ||
     122|| regular_blocking || boolean || NOT NULL || false by default, true if all blocks are equal sized, abutted and non-overlapping, started at top left origin (see below) ||
     123|| nodata_values || ARRAY[[=DOUBLE=]] ||  || an array of nodata values, one per band. The entry may be NULL to indicate no nodata values.||
     124|| pixelsize_x || double || || width of a pixel in geounits (per SRID) ||
     125|| pixelsize_y || double ||  || height of a pixel in geounits (per SRID) ||
     126|| blocksize_x || integer ||  || the width of a block in pixels (NULL if irregular) ||
     127|| blocksize_y || integer ||  || the height of a block in pixels (NULL if irregular) ||
     128|| extent|| GEOMETRY || || a polygon geometry containing all raster tiles, or NULL if predefined bounds are not known.  For "regular_blocking" cases this geometry will be a simple rectangle.  In other cases it might be an irregular polygon. ||
     129
     130If the regular_blocking field is true a number of restrictions are placed on the raster column that is defined:[[BR]]
     131[[BR]]
     132 1. All tiles must have the same size (blocksize_x and blocksize_y).
     133 1. All tiles must be non-overlapping, and appear on regular block grid.
     134 1. The top left block must start at the top left corner of the extent.
     135 1. The right most column, and bottom row of blocks may have portions that extend beyond the raster extent.  These areas will be assumed to be nodata and not part of the described raster.
     136 1. The extent field must be a simple rectangle (non-rotated).
     137
     138It is permissable to for regular_blocking rasters to omit some blocks/tiles (sparse rasters) in which case the missing tiles should be assumed to be all nodata or zero valued.