Does a GDALDriver know his own name? GetDescription from GDALMajorObject
maybe? The problem is that there is a Driver abstraction object in the
Node.js bindings that supports opening a file through that driver. I
guess this is the reason the original author used pfnOpen.
On 08/10/2020 17:38, Even Rouault wrote:
Yes, you're using an implementation detail when using pfnOpen, that is
not supposed to be used by user code. You should rather use GDALOpen /
GDALOpenEx / GDALDataset::Open instead of using directly driver->pfnOpen
Those functions are the ones that set the poDriver member of the
GDALDataset
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
--
Momtchil Momtchev<[email protected]>
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
