download the new Data File Converter 5.3.4

Into a schema called aerial and create a full view, 2 and 4 level overview tables, use copy mode for inserting (no intermediary file just straight to db), and -e don't force everything in a transaction (good if you want to see data in tables right away without waiting). Load rasters Massachusetts state plane meters aerial tiles Raster2pgsql -s 4236 -I -C -M *.tif -F -t 100x100 melevation > elev.sqlĪ conversion and upload can be done all in one step using UNIX pipes: raster2pgsql -s 4236 -I -C -M *.tif -F -t 100x100 melevation | psql -d gisdb The raster table will be created in the default schema of the database or user You can leave the schema name out e.g demelevation instead of melevation and Only 0 is supported at this time.Īn example session using the loader to create an input file and uploading it chunked in 100x100 tiles might look like this: E ENDIANĬontrol endianness of generated binary output of raster specify 0 for XDR and 1 for NDR (default) only NDR output is supported now -V version Use copy statements instead of insert statements.Įxecute each statement individually, do not use a transaction.

This applies to the primary key and the spatial index if the Specify the tablespace for the table's new index.

The default tablespace unless the -X flag is also used. Note that indices (including the primary key) will still use Specify the tablespace for the new table. Specify name of destination raster column, default is 'rast'Īdd a column with the name of the file -IĬreate a GiST index on the raster column. Optional parameters used to manipulate database objects NODATA value to use on bands without a NODATA value. Note that your generated sql file will contain both the main table and overview tables. Stored in the database and is not affected by -R.

The pattern o_ overview factor_ table, where overview factor is a placeholder for numerical overview factor and table is replaced with the base table name.

l OVERVIEW_FACTORĬreate overview of the raster. Only the metadata of the raster and path location to the raster is stored in the database (not the pixels). Register the raster as a filesystem (out-db) raster. TILE_SIZE is expressed as WIDTHxHEIGHT or set to the value 'auto' to allow the loader to compute an appropriate tile size using the first raster and applied to all rasters. If unspecified,Ĭut raster into tiles to be inserted one per table row. For more than one band index, separate with comma (,). Index (1-based) of band to extract from raster. If not provided or is zero, raster's metadata will be checked to determine an appropriate SRID. Assign output raster with specified SRID.

Download the new Data File Converter 5.3.4