add a hint to geopackage documentation about trouble with NFS / Samba Shares
|Reported by:||rnuske||Owned by:||warmerdam|
Would it be possible to add the known SQLite Limitations to the description of the GPKG Driver documentation or link to SQLite more prominently?
This question is based on the assumption, that the Geopackage driver uses the SQLite Driver internally and such shares its limitations.
I tried to write a Geopackage on a samba share via the st_write function of the R package sf and failed. Same with ogr2ogr, eg.
ogr2ogr -f GPKG dat1.gpkg dat1.shp
Lorenzo Busetto hinted (https://github.com/r-spatial/sf/issues/628), that I was probably bitten by the fact, that SQLite has problems writing on networked file systems (in my case: a samba share mounted on a linux system). Roger Bivand pointed out that there is a note on the SQLite Driver Documentation, which I missed looking only at the Geopackage Documentation.
Could the sentence
SQLite databases often due not work well over NFS, or some other networked file system protocols due to the poor support for locking. It is safest to operate only on SQLite files on a physical disk of the local system. from http://gdal.org/drv_sqlite.html be copied to the Limitations section of http://www.gdal.org/drv_geopackage.html?