Changes between Initial Version and Version 1 of WKTRaster/SpecificationFinal01


Ignore:
Timestamp:
04/16/09 08:35:09 (16 years ago)
Author:
pracine
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WKTRaster/SpecificationFinal01

    v1 v1  
     1= '''PostGIS WKT Raster Beta 0.1 Final Specifications''' =
     2{{{
     3#!html
     4<div  style='background-color: #F4F4F4; padding: 5px; border: 1px solid gray; float: right; margin-left: 5px; width: 260px; font-size: small;' >
     5}}}
     6'''Quick Links'''
     7
     8 * [wiki:WKTRaster WKT Raster Home Page]
     9 * [wiki:WKTRaster/PlanningAndFunding Planning & Funding]
     10
     11 * [wiki:WKTRaster/SpecificationWorking01 Working Specifications for Beta 0.1.6]
     12
     13 * [wiki:WKTRaster/SpecificationWorking02 Working Specifications for Beta 0.2.4]
     14 * [wiki:WKTRaster/SpecificationFinal02 Final Specifications for Beta 0.2.4]
     15
     16{{{
     17#!html
     18</div>
     19}}}
     20----
     21== '''Objective 0.1.6c - Being able to load rasters in the database ''' ==
     22
     23
     24'''gdal2wktraster.py -''' A prototype of the translation utility implemented in Python and with use of [http://www.gdal.org/ GDAL] and its bindings to Python. Create an SQL commands output to create a table of raster. As input raster file, all GDAL formats are accepted. The script is available as [http://svn.refractions.net/postgis/spike/wktraster/scripts/gdal2wktraster.py gdal2wktraster.py] script.
     25
     26'''Open Questions:'''[[BR]]
     27[[BR]]
     28 1. Should we change names of options to strictly follow those used by raster2pgsql and shp2pgsql?[[BR]][[BR]]  Pierre: Yes! We should follow PostGIS tracks as much as possible in everything we do in this project.[[BR]][[BR]]
     29 1. How can I import all the bands from a multiband TIFF?
     30
     31'''USAGE:'''[[BR]]
     32'''gdal2wktraster.py''' -r rasterfile [-r rasterfile] -t [<schema>.]<table> [<options>]
     33
     34'''-r''' <rasterfile>  Specifies input raster file. Multiple -r options can be specified for a number of input files or wildcards can be used (? and *). At least one input raster file is REQUIRED.[[BR]]
     35'''-t''' <table>  Name of destination table in with or without target schema specified. This parameter is REQUIRED.
     36
     37
     38'''OPTIONS:'''[[BR]]
     39'''-s''' <srid>  Set the SRID field. Default is -1.[[BR]]
     40'''-b''' <nbband>  Specify the number of band. The number of rasterfile must correspond to this number.[[BR]]
     41'''-f''' <field>  Name of target column for raster data. Default column name is rast.[[BR]]
     42'''-I''' Create a GiST index on the raster column.[[BR]]
     43'''-o''' <file> Output file for generated SQL commands. If not specified, stdout is assumed.[[BR]]
     44'''-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]]
     45'''-F''' Add a "filename" column containing the original name of the loaded raster file.
     46
     47
     48'''(-d|c)''' Mutually exclusive inserting options:[[BR]]
     49  '''-d'''  Drops the table, then recreates it and populates it with current raster file data.[[BR]]
     50  '''-c'''  Creates a new table and populates it, this is the default if you do not specify any options.
     51
     52'''-v''' Switch on excessively verbose mode, useful for debugging.[[BR]]
     53'''-h''' Display this help screen.
     54
     55----