| | 235 | |
| | 236 | ---- |
| | 237 | |
| | 238 | '''ST_getGDALDrivers() -> set of record''' |
| | 239 | |
| | 240 | As each GDAL installation may be different and ST_AsGDALRaster can be used to support formats other than GTiff, JPEG and PNG, a method is needed to expose to the end user the possible GDAL formats capable of being exported. This function will output the following columns. |
| | 241 | |
| | 242 | idx: the internal GDAL index number |
| | 243 | |
| | 244 | short_name: the GDAL format code. This is the value to pass to the format paramenter of ST_AsGDALRaster |
| | 245 | |
| | 246 | long_name: the full name of the GDAL format |
| | 247 | |
| | 248 | create_options: the creation options available for the format as an XML string. |
| | 249 | |
| | 250 | The formats outputted from ST_getGDALDrivers have been filtered to only those that the GDAL capabilities !CreateCopy and Virtual IO support. |
| | 251 | |
| | 252 | '''Open Question:''' Should the GDAL raster process be capable of supporting the GDAL capability Create? As the GDAL raster process writes nothing to a file in the filesystem (via Virtual IO), should there be support for writing the output GDAL raster temporarily to the filesystem? If so, how is it done in other PostgreSQL extensions in a secure manner? |
| | 253 | |
