Opened 6 years ago
Last modified 5 years ago
#3859 new enhancement
r.out.gdal: Add notes about bigtiff and example with BIGTIFF=YES (or similar) to manual
| Reported by: | sbl | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.8.3 |
| Component: | Docs | Version: | svn-trunk |
| Keywords: | r.out.gdal | Cc: | |
| CPU: | All | Platform: | All |
Description
In r.out.gdal I get Error 1 Maximum TIFF file size exceeded. Use BIGTIFF=YES. Would be great if GRASS could use BIGTIFF=IF_NEEDED/IF_SAFER by default when exporting GeoTiff or if it could compute the required creation option from region size, number of bands and data type...
Change History (6)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
| Component: | Raster → Docs |
|---|---|
| Summary: | r.out.gdal: Do not fail with big tiffs if user does not provide BIGTIFF=YES creatopt → r.out.gdal: Add notes about bigtiff and example with BIGTIFF=YES (or similar) to manual |
Thanks for the swift feedback! Point taken. Changed into a documentation ticket (that I could fix myself).
comment:6 by , 5 years ago
| Milestone: | → 7.8.3 |
|---|
Note:
See TracTickets
for help on using tickets.
Replying to sbl:
The idea of using GDAL/OGR is that the code does not need to bother about format-specific options. By now GRASS code does take care of some special formats to prevent errors and/or to follow GDAL instructions, but for code maintenance I would like to keep this to a minimum.
There is a reason (on the GDAL side) why BIGTIFF=YES is not the default: not all (Geo)Tiff drivers support BIGTIFF.