Opened 5 years ago
Last modified 5 years ago
#3992 new enhancement
v.import man page should say what -f's ro, rw, and rw+ are
| Reported by: | jidanni | Owned by: | |
|---|---|---|---|
| Priority: | trivial | Milestone: | 7.8.3 |
| Component: | Docs | Version: | git-releasebranch78 |
| Keywords: | Cc: | ||
| CPU: | Unspecified | Platform: | Unspecified |
Description
man v.import -f: document ro, rw, rw+
$ grass --exec v.import -f input=/dev/null 2>/dev/null |\
perl -nwle '/\(([^)]+)/||die; print $1;'|sort|uniq -c
40 ro
2 rw
47 rw+
OK, but the v.import man page should say what -f's ro, rw, and rw+ are.
Yes, the user might guess what ro and rw are, but not rw+!!.
Note:
See TracTickets
for help on using tickets.

For reference, the output is
The
ro,rw, andrw+may come from GDAL/OGR. Since v.import is a wrapper around v.in.ogr, the related source code is this (main.c):if (GDALGetMetadataItem(hDriver, GDAL_DCAP_CREATE, NULL)) pszRWFlag = "rw+"; else if (GDALGetMetadataItem(hDriver, GDAL_DCAP_CREATECOPY, NULL)) pszRWFlag = "rw"; else pszRWFlag = "ro";In GDAL itself I cannot find
pszRWFlag, so no idea what it does and if it is still relevant...One reference seems to be this: https://gdal.org/api/raster_c_api.html#c.GDAL_DCAP_CREATECOPY
I agree that the meaning of
ro,rw, andrw+should be explained in the manual pages of r/v.import and r.in.gdal/v.in.ogr.