Changes between Version 27 and Version 28 of WKTRaster/SpecificationWorking01
- Timestamp:
- May 29, 2009, 7:19:53 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WKTRaster/SpecificationWorking01
v27 v28 43 43 '''-s''' <srid> Set the SRID field. Default is -1.[[BR]] 44 44 '''-b''' <nbband> Specify the number of band. The number of rasterfile must correspond to this number.[[BR]] 45 '''-f''' <field> Name of target column for raster data. Default column name is rast.[[BR]]45 '''-f''' <field> Name of target column for raster data. Default column name is ''rast''.[[BR]] 46 46 '''-I''' Create a GiST index on the raster column.[[BR]] 47 '''-o''' <file> Output file for generated SQL commands. If not specified, stdoutis assumed.[[BR]]47 '''-o''' <file> Output file for generated SQL commands. If not specified, ''stdout'' is assumed.[[BR]] 48 48 '''-R''' Simply register the raster in the database. Absolute path to the raster and georeferencing informations are stored instead of the raster actual data.[[BR]] 49 49 '''-F''' Add a "filename" column containing the original name of the loaded raster file. … … 84 84 '''(-d|a|b|c|p)''' Mutually exclusive inserting options:[[BR]] 85 85 '''-d''' Drops the table, then recreates it and populates it with current raster file data.[[BR]] 86 '''-a''' Appends raster file into current table, must be exactly the same pixel size, number of band, nodatavalue and pixel type.[[BR]]86 '''-a''' Appends raster file into current table, must be exactly the same pixel size, number of band, NODATA value and pixel type.[[BR]] 87 87 '''-B''' Appends raster files as a new bands. When tiled with the –t option, the new band is inserted tiled in the same way as the original band.[[BR]] 88 88 '''-c''' Creates a new table and populates it, this is the default if you do not specify any options.[[BR]] … … 90 90 91 91 '''-r''' <raster_column> Specify the name of the raster column (mostly useful in append mode).[[BR]] 92 '''-D''' Use postgresqldump format (defaults to sql insert statements).[[BR]]93 '''-I''' Create a GiST index on the b box of the raster column.[[BR]]92 '''-D''' Use PostgreSQL dump format (defaults to sql insert statements).[[BR]] 93 '''-I''' Create a GiST index on the bounding box of the raster column.[[BR]] 94 94 '''-?''' Display this help screen 95 95 … … 255 255 || out_db || boolean || NOT NULL || false if internal tiles, true if tiles are references to files outside the database || 256 256 || 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) || 257 || nodata_values || ARRAY[[=DOUBLE=]] || || an array of nodata values, one per band. The entry may be NULL to indicate no nodatavalues.||257 || nodata_values || ARRAY[[=DOUBLE=]] || || an array of nodata values, one per band. The entry may be NULL to indicate no NODATA values.|| 258 258 || pixelsize_x || double || || width of a pixel in geounits (per SRID) || 259 259 || pixelsize_y || double || || height of a pixel in geounits (per SRID) || … … 267 267 1. All tiles must be non-overlapping, and appear on regular block grid. 268 268 1. The top left block must start at the top left corner of the extent. 269 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 nodataand not part of the described raster.269 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. 270 270 1. The extent field must be a simple rectangle (non-rotated). 271 271 272 It is permiss able to for regular_blocking rasters to omit some blocks/tiles (sparse rasters) in which case the missing tiles should be assumed to be all nodataor zero valued.272 It is permissible 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. 273 273 274 274 ---- … … 354 354 a. ML: Prefer native build toolsets on supported platform (Windows/Visual C++, GCC/Linux, etc.). On Windows, avoid Cygwin, MinGW, wherever possible. Issue directly related to point a).[[BR]][[BR]] 355 355 a. Is cmake a possibility?[[BR]][[BR]] 356 1. '''GiST indexing:''' is wrapping PostGIS Gist function in plpgslqsufficient? From Paul comments it seems actually that cast are sufficients.[[BR]][[BR]]356 1. '''GiST indexing:''' is wrapping PostGIS Gist function in PL/PgSQL sufficient? From Paul comments it seems actually that cast are sufficients.[[BR]][[BR]] 357 357 1. '''API:''' Any other SQL raster function you would like to see?[[BR]][[BR]] 358 358 a. ML: RT_AsJPEG - What JPEG implementation to use?[[BR]][[BR]]
