additions to readme

hypertidy · Dec 24, 2023 · cb5f020 · cb5f020
1 parent ec9c9a2
commit cb5f020
Show file tree

Hide file tree

Showing 2 changed files with 25 additions and 7 deletions.
diff --git a/README.Rmd b/README.Rmd
@@ -27,6 +27,10 @@ Please note that dsn is not doing anything *with GDAL*, this is pure string hand
 - prefixing a driver declaration to a data source, e.g. `HDF5:/my/files/data.h5` or `NETCDF:C:/temp/nc/afile.nc`
 - wrapping a [subdataset](https://gdal.org/user/raster_data_model.html#subdatasets-domain)  declaration, e.g. `NETCDF:/myfiles/data.nc:variable` that can occur in [NETCDF](https://gdal.org/drivers/raster/netcdf.html#multiple-image-handling-subdatasets) and similar formats
 - wrapping a [VRT connection](https://gdal.org/drivers/raster/vrt.html#vrt-connection-string), e.g. `vrt://myfile.tif?bands=3,2,1`
+- creating a DATAPOINTER connection for the MEM driver, i.e. we can create data arrays as rasters from R
+objects, and use R objects for georeferencing with geolocation arrays (either rectilinear or curvilinear, or degenerate versions of these)
+- datatype helpers for the internal GDT_ types in GDAL
+- creating gcp lists for use with VRT
 
 Please see [vapour::vapour_vrt()](https://hypertidy.github.io/vapour/reference/vapour_vrt.html) for actual use of GDAL to extend a data source name by opening the source and augmenting available information. dsn is intended to support that usage, and in general intends to be purely string handling, and not make use of the format libraries at all.