Changes between Version 238 and Version 239 of WKTRaster/SpecificationWorking03
- Timestamp:
- 08/27/12 11:46:27 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WKTRaster/SpecificationWorking03
v238 v239 220 220 221 221 ---- 222 == '''Objective FV.17 - Being able to refer to band by textual name.''' ==222 == '''Objective FV.17 - Being able to refer to band by name. (PostGIS 3.0) ''' == 223 223 224 224 '''Add 8 digit string to each band in the base raster WKB format. … … 231 231 == '''Objective FV.18 - Being able to load rasters from SQL''' == 232 232 233 The idea is to change the rt_band_get_data core function so it load filesystem registered raster data using GDAL into the data base. This allow us to create a list of raster with a new ST_MakeRegisteredRaster("c:/temp/mytiff/*.tif") and to convert them witinot a CREATE TABLE with a ST_MakeBandInDB(rast, band)233 The idea is to change the rt_band_get_data core function so it loads filesystem registered raster data using GDAL into the data base. This allow us to create a list of raster with a new ST_MakeRegisteredRaster("c:/temp/mytiff/*.tif") function and to convert them to internal rasters with a CREATE TABLE indbraster AS SELECT ST_MakeInDB(ST_MakeRegisteredRaster("c:/temp/mytiff/*.tif"), band) statement. 234 234 235 235 '''Changes to the rt_band_get_data core function'''[[BR]] 236 236 '''ST_MakeRegisteredRaster(wildcardPath)'''[[BR]] 237 '''ST_SetPath(raster, band, string)'''[[BR]] 238 '''ST_MakeBandInDB(rast, band)''' 237 '''ST_MakeInDB(rast, band)''' 239 238 240 239 ---- … … 515 514 516 515 ---- 516 == '''Objective FV.29 - Subtiling of rasters (PostGIS 3.0 or create a new raster type)''' == 517 518 Rewrite the RASTER type so that big rasters stored in one row (max 1GB) are internally tiled and quickly accessed. 519 517 520 == '''Other functions''' == 518 521