#include <gdal_priv.h>
Public Member Functions | |
GDALDataset * | Create (const char *pszName, int nXSize, int nYSize, int nBands, GDALDataType eType, char **papszOptions) |
CPLErr | Delete (const char *pszName) |
GDALDataset * | CreateCopy (const char *, GDALDataset *, int, char **, GDALProgressFunc pfnProgress, void *pProgressData) |
Public Attributes | |
GDALDataset *(* | pfnOpen )(GDALOpenInfo *) |
GDALDataset *(* | pfnCreate )(const char *pszName, int nXSize, int nYSize, int nBands, GDALDataType eType, char **papszOptions) |
CPLErr(* | pfnDelete )(const char *pszName) |
GDALDataset *(* | pfnCreateCopy )(const char *, GDALDataset *, int, char **, GDALProgressFunc pfnProgress, void *pProgressData) |
void * | pDriverData |
void(* | pfnUnloadDriver )(GDALDriver *) |
This roughly corresponds to a file format, though some drivers may be gateways to many formats through a secondary multi-library.
|
Create a new dataset with this driver. What argument values are legal for particular drivers is driver specific, and there is no way to query in advance to establish legal values. Equivelent of the C function GDALCreate().
|
|
Create a copy of a dataset. This method will attempt to create a copy of a raster dataset with the indicated filename, and in this drivers format. Band number, size, type, projection, geotransform and so forth are all to be copied from the provided template dataset. Note that many sequential write once formats (such as JPEG and PNG) don't implement the Create() method but do implement this CreateCopy() method. If the driver doesn't implement CreateCopy(), but does implement Create() then the default CreateCopy() mechanism built on calling Create() will be used. It is intended that CreateCopy() would often be used with a source dataset which is a virtual dataset allowing configuration of band types, and other information without actually duplicating raster data. This virtual dataset format hasn't yet been implemented at the time of this documentation being written.
|
|
Delete named dataset. The driver will attempt to delete the named dataset in a driver specific fashion. Full featured drivers will delete all associated files, database objects, or whatever is appropriate. The default behaviour when no driver specific behaviour is provided is to attempt to delete the passed name as a single file. It is unwise to have open dataset handles on this dataset when it is deleted. Equivelent of the C function GDALDeleteDataset().
|