Compressing georeferenced images Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How to digitize polygons from georeferenced raster fileIllustrator to QGIS workflow for vectorsRaster diff: how to check if images have identical values?What causes wrong placement of JPGs in QGIS 2.8.1?World file in georeferenced file does not work in QGIS?Compressing raster using PyQGIS?Reducing File Size without losing qualityEditing/adding GCPs using QGIS?Geo-referenced UAV image does not align with Sentinel-2Adding compression variable to CopyRaster_management for TIFF Raster Dataset?

What does this Jacques Hadamard quote mean?

How do I make this wiring inside cabinet safer? (Pic)

Do I really need recursive chmod to restrict access to a folder?

Generate an RGB colour grid

Why are there no cargo aircraft with "flying wing" design?

Is "Reachable Object" really an NP-complete problem?

When was Kai Tak permanently closed to cargo service?

Is it a good idea to use CNN to classify 1D signal?

How to tell that you are a giant?

Irreducible of finite Krull dimension implies quasi-compact?

Is grep documentation wrong?

Why didn't Eitri join the fight?

Most bit efficient text communication method?

Can an alien society believe that their star system is the universe?

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

Closed form of recurrent arithmetic series summation

Fundamental Solution of the Pell Equation

How do I find out the mythology and history of my Fortress?

What is the longest distance a player character can jump in one leap?

Denied boarding although I have proper visa and documentation. To whom should I make a complaint?

Significance of Cersei's obsession with elephants?

Is there a kind of relay only consumes power when switching?

What causes the direction of lightning flashes?

What is homebrew?



Compressing georeferenced images



Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?How to digitize polygons from georeferenced raster fileIllustrator to QGIS workflow for vectorsRaster diff: how to check if images have identical values?What causes wrong placement of JPGs in QGIS 2.8.1?World file in georeferenced file does not work in QGIS?Compressing raster using PyQGIS?Reducing File Size without losing qualityEditing/adding GCPs using QGIS?Geo-referenced UAV image does not align with Sentinel-2Adding compression variable to CopyRaster_management for TIFF Raster Dataset?



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















I have a bunch of georeferenced TIFF images created in QGIS. The person creating them saved them as uncompressed (around 1 GB each).
I would like to compress them as LZW to save space.



How can I do that in a programmatic way (e.g. batch)?



I am open to QGIS or R approches. Please consider I do not know how Georeferencing information are attached to an image (e.g. I have seen somewhere references to a world file, but I do not know what it is).










share|improve this question



















  • 2





    TIFF files can be georeferenced in one of two ways: (1) Georeferencing information is embedded in the TIFF file as part of the metadata, so you only have one file, with the extension .tif or .tiff. (2) Georeferencing information is written in a second, ("sidecar") file with the extension .tfw, alongside the TIFF file. If you want more information about how georeferencing info is attached to a tiff file, read this Wikipedia article.

    – csk
    2 days ago

















2















I have a bunch of georeferenced TIFF images created in QGIS. The person creating them saved them as uncompressed (around 1 GB each).
I would like to compress them as LZW to save space.



How can I do that in a programmatic way (e.g. batch)?



I am open to QGIS or R approches. Please consider I do not know how Georeferencing information are attached to an image (e.g. I have seen somewhere references to a world file, but I do not know what it is).










share|improve this question



















  • 2





    TIFF files can be georeferenced in one of two ways: (1) Georeferencing information is embedded in the TIFF file as part of the metadata, so you only have one file, with the extension .tif or .tiff. (2) Georeferencing information is written in a second, ("sidecar") file with the extension .tfw, alongside the TIFF file. If you want more information about how georeferencing info is attached to a tiff file, read this Wikipedia article.

    – csk
    2 days ago













2












2








2








I have a bunch of georeferenced TIFF images created in QGIS. The person creating them saved them as uncompressed (around 1 GB each).
I would like to compress them as LZW to save space.



How can I do that in a programmatic way (e.g. batch)?



I am open to QGIS or R approches. Please consider I do not know how Georeferencing information are attached to an image (e.g. I have seen somewhere references to a world file, but I do not know what it is).










share|improve this question
















I have a bunch of georeferenced TIFF images created in QGIS. The person creating them saved them as uncompressed (around 1 GB each).
I would like to compress them as LZW to save space.



How can I do that in a programmatic way (e.g. batch)?



I am open to QGIS or R approches. Please consider I do not know how Georeferencing information are attached to an image (e.g. I have seen somewhere references to a world file, but I do not know what it is).







qgis r georeferencing compression






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 days ago









Vince

14.8k32850




14.8k32850










asked 2 days ago









FilippoFilippo

8418




8418







  • 2





    TIFF files can be georeferenced in one of two ways: (1) Georeferencing information is embedded in the TIFF file as part of the metadata, so you only have one file, with the extension .tif or .tiff. (2) Georeferencing information is written in a second, ("sidecar") file with the extension .tfw, alongside the TIFF file. If you want more information about how georeferencing info is attached to a tiff file, read this Wikipedia article.

    – csk
    2 days ago












  • 2





    TIFF files can be georeferenced in one of two ways: (1) Georeferencing information is embedded in the TIFF file as part of the metadata, so you only have one file, with the extension .tif or .tiff. (2) Georeferencing information is written in a second, ("sidecar") file with the extension .tfw, alongside the TIFF file. If you want more information about how georeferencing info is attached to a tiff file, read this Wikipedia article.

    – csk
    2 days ago







2




2





TIFF files can be georeferenced in one of two ways: (1) Georeferencing information is embedded in the TIFF file as part of the metadata, so you only have one file, with the extension .tif or .tiff. (2) Georeferencing information is written in a second, ("sidecar") file with the extension .tfw, alongside the TIFF file. If you want more information about how georeferencing info is attached to a tiff file, read this Wikipedia article.

– csk
2 days ago





TIFF files can be georeferenced in one of two ways: (1) Georeferencing information is embedded in the TIFF file as part of the metadata, so you only have one file, with the extension .tif or .tiff. (2) Georeferencing information is written in a second, ("sidecar") file with the extension .tfw, alongside the TIFF file. If you want more information about how georeferencing info is attached to a tiff file, read this Wikipedia article.

– csk
2 days ago










2 Answers
2






active

oldest

votes


















4














You can do this using the command line tool gdal_translate. This is available for Windows, Linux, and Mac OSs (you don't state your OS).



Running:



gdalinfo none.tif


will show the info on the file, including the compression type and the locations:



Driver: GTiff/GeoTIFF
Files: none.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left ( 96.5464352, 17.5351143) ( 96d32'47.17"E, 17d32' 6.41"N)
Lower Left ( 96.5464352, 16.5110349) ( 96d32'47.17"E, 16d30'39.73"N)
Upper Right ( 97.4627168, 17.5351143) ( 97d27'45.78"E, 17d32' 6.41"N)
Lower Right ( 97.4627168, 16.5110349) ( 97d27'45.78"E, 16d30'39.73"N)
Center ( 97.0045760, 17.0230746) ( 97d 0'16.47"E, 17d 1'23.07"N)
[etc]


it doesn't mention a compression type, because it doesn't have one. If your GeoTIFFs aren't compressed they should also not say anything. Note the spatial information is stored in geoTIFF chunks and is output as a bounding box corner set. Great.



Let's compress it. Uncompressed file is 4.7Mb:



$ ls -hs none.tif 
4.7M none.tif


Run this:



$ gdal_translate none.tif lzw.tif -co COMPRESS=LZW
Input file size is 204, 228
0...10...20...30...40...50...60...70...80...90...100 - done.


and get



$ ls -hs lzw.tif 
1.6M lzw.tif


1.6Mbytes in LZW compressed form. Again gdalinfo shows:



$ gdalinfo lzw.tif 
Driver: GTiff/GeoTIFF
Files: lzw.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=PIXEL
Corner Coordinates:
[etc]


Note the COMPRESSION=LZW message.



Loop over your files using your command line interpreter loop functions.



You might also be able to do this via the gdalUtils package in R which will run these command line commands via a shell.



Indeed for my test file:



library(gdalUtils)
gdal_translate(
src_dataset="none.tif",
dst_dataset="lzwR.tif",
co="COMPRESS=LZW")


results in a byte-for-byte identical output file.






share|improve this answer




















  • 1





    some other -co to consider and offers additional compression (lossless) are -mo "INTERLEAVE=PIXEL" -co "INTERLEAVE=PIXEL" -co "TILED=YES" -co "COMPRESS=LZW" -co "PREDICTOR=2"

    – SaultDon
    2 days ago


















3














In addition to @Spacedman's answer, you can set up a loop in R to compress tiffs using LZW with the writeRaster function in the raster package, which still uses GDAL. The options argument allows you to apply LZW compression.



In this example, the file is not overwritten but rather has an "_LZW" appended to the original name. To just overwrite the original file you can omit the paste0 function in writeRaster and just use the file iterator (ie., rfiles[i]). You could also paste a directory path into the file name to aim the compressed files to a different directory. If the tif files are multi-band then you would use stack rather than raster to read the data.



library(raster)
setwd("C:/...")
rfiles <- list.files(getwd(), "tif$")
for(i in 1:length(rfiles))
r <- raster::raster(rfiles[i])
raster::writeRaster(r, paste0(gsub(pattern = "\.tif$", "",
rfiles[i]), "_LZW", ".tif"), overwrite=TRUE,
options="COMPRESS=LZW")






share|improve this answer























  • Thanks Jeffrey Evans and @Spacedman. Just for clarity. I assume that an image georeferenced in qgis and saved as .tif is a geoTif. is this correct? if not... will the solutions you both proposed work anyway?

    – Filippo
    2 days ago











  • I'd be concerned that this would read in the entire +1Gb files. Might not be too efficient. The GDAL command line routines are pretty well optimised.

    – Spacedman
    2 days ago











  • A "geoTIFF" is a TIFF with special metadata blocks in it that give it a spatial reference. Rasters saved from QGIS should have this data and so be valid geoTIFFs - check with the gdalinfo command line or gdalUtils package.

    – Spacedman
    2 days ago











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "79"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f318858%2fcompressing-georeferenced-images%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









4














You can do this using the command line tool gdal_translate. This is available for Windows, Linux, and Mac OSs (you don't state your OS).



Running:



gdalinfo none.tif


will show the info on the file, including the compression type and the locations:



Driver: GTiff/GeoTIFF
Files: none.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left ( 96.5464352, 17.5351143) ( 96d32'47.17"E, 17d32' 6.41"N)
Lower Left ( 96.5464352, 16.5110349) ( 96d32'47.17"E, 16d30'39.73"N)
Upper Right ( 97.4627168, 17.5351143) ( 97d27'45.78"E, 17d32' 6.41"N)
Lower Right ( 97.4627168, 16.5110349) ( 97d27'45.78"E, 16d30'39.73"N)
Center ( 97.0045760, 17.0230746) ( 97d 0'16.47"E, 17d 1'23.07"N)
[etc]


it doesn't mention a compression type, because it doesn't have one. If your GeoTIFFs aren't compressed they should also not say anything. Note the spatial information is stored in geoTIFF chunks and is output as a bounding box corner set. Great.



Let's compress it. Uncompressed file is 4.7Mb:



$ ls -hs none.tif 
4.7M none.tif


Run this:



$ gdal_translate none.tif lzw.tif -co COMPRESS=LZW
Input file size is 204, 228
0...10...20...30...40...50...60...70...80...90...100 - done.


and get



$ ls -hs lzw.tif 
1.6M lzw.tif


1.6Mbytes in LZW compressed form. Again gdalinfo shows:



$ gdalinfo lzw.tif 
Driver: GTiff/GeoTIFF
Files: lzw.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=PIXEL
Corner Coordinates:
[etc]


Note the COMPRESSION=LZW message.



Loop over your files using your command line interpreter loop functions.



You might also be able to do this via the gdalUtils package in R which will run these command line commands via a shell.



Indeed for my test file:



library(gdalUtils)
gdal_translate(
src_dataset="none.tif",
dst_dataset="lzwR.tif",
co="COMPRESS=LZW")


results in a byte-for-byte identical output file.






share|improve this answer




















  • 1





    some other -co to consider and offers additional compression (lossless) are -mo "INTERLEAVE=PIXEL" -co "INTERLEAVE=PIXEL" -co "TILED=YES" -co "COMPRESS=LZW" -co "PREDICTOR=2"

    – SaultDon
    2 days ago















4














You can do this using the command line tool gdal_translate. This is available for Windows, Linux, and Mac OSs (you don't state your OS).



Running:



gdalinfo none.tif


will show the info on the file, including the compression type and the locations:



Driver: GTiff/GeoTIFF
Files: none.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left ( 96.5464352, 17.5351143) ( 96d32'47.17"E, 17d32' 6.41"N)
Lower Left ( 96.5464352, 16.5110349) ( 96d32'47.17"E, 16d30'39.73"N)
Upper Right ( 97.4627168, 17.5351143) ( 97d27'45.78"E, 17d32' 6.41"N)
Lower Right ( 97.4627168, 16.5110349) ( 97d27'45.78"E, 16d30'39.73"N)
Center ( 97.0045760, 17.0230746) ( 97d 0'16.47"E, 17d 1'23.07"N)
[etc]


it doesn't mention a compression type, because it doesn't have one. If your GeoTIFFs aren't compressed they should also not say anything. Note the spatial information is stored in geoTIFF chunks and is output as a bounding box corner set. Great.



Let's compress it. Uncompressed file is 4.7Mb:



$ ls -hs none.tif 
4.7M none.tif


Run this:



$ gdal_translate none.tif lzw.tif -co COMPRESS=LZW
Input file size is 204, 228
0...10...20...30...40...50...60...70...80...90...100 - done.


and get



$ ls -hs lzw.tif 
1.6M lzw.tif


1.6Mbytes in LZW compressed form. Again gdalinfo shows:



$ gdalinfo lzw.tif 
Driver: GTiff/GeoTIFF
Files: lzw.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=PIXEL
Corner Coordinates:
[etc]


Note the COMPRESSION=LZW message.



Loop over your files using your command line interpreter loop functions.



You might also be able to do this via the gdalUtils package in R which will run these command line commands via a shell.



Indeed for my test file:



library(gdalUtils)
gdal_translate(
src_dataset="none.tif",
dst_dataset="lzwR.tif",
co="COMPRESS=LZW")


results in a byte-for-byte identical output file.






share|improve this answer




















  • 1





    some other -co to consider and offers additional compression (lossless) are -mo "INTERLEAVE=PIXEL" -co "INTERLEAVE=PIXEL" -co "TILED=YES" -co "COMPRESS=LZW" -co "PREDICTOR=2"

    – SaultDon
    2 days ago













4












4








4







You can do this using the command line tool gdal_translate. This is available for Windows, Linux, and Mac OSs (you don't state your OS).



Running:



gdalinfo none.tif


will show the info on the file, including the compression type and the locations:



Driver: GTiff/GeoTIFF
Files: none.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left ( 96.5464352, 17.5351143) ( 96d32'47.17"E, 17d32' 6.41"N)
Lower Left ( 96.5464352, 16.5110349) ( 96d32'47.17"E, 16d30'39.73"N)
Upper Right ( 97.4627168, 17.5351143) ( 97d27'45.78"E, 17d32' 6.41"N)
Lower Right ( 97.4627168, 16.5110349) ( 97d27'45.78"E, 16d30'39.73"N)
Center ( 97.0045760, 17.0230746) ( 97d 0'16.47"E, 17d 1'23.07"N)
[etc]


it doesn't mention a compression type, because it doesn't have one. If your GeoTIFFs aren't compressed they should also not say anything. Note the spatial information is stored in geoTIFF chunks and is output as a bounding box corner set. Great.



Let's compress it. Uncompressed file is 4.7Mb:



$ ls -hs none.tif 
4.7M none.tif


Run this:



$ gdal_translate none.tif lzw.tif -co COMPRESS=LZW
Input file size is 204, 228
0...10...20...30...40...50...60...70...80...90...100 - done.


and get



$ ls -hs lzw.tif 
1.6M lzw.tif


1.6Mbytes in LZW compressed form. Again gdalinfo shows:



$ gdalinfo lzw.tif 
Driver: GTiff/GeoTIFF
Files: lzw.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=PIXEL
Corner Coordinates:
[etc]


Note the COMPRESSION=LZW message.



Loop over your files using your command line interpreter loop functions.



You might also be able to do this via the gdalUtils package in R which will run these command line commands via a shell.



Indeed for my test file:



library(gdalUtils)
gdal_translate(
src_dataset="none.tif",
dst_dataset="lzwR.tif",
co="COMPRESS=LZW")


results in a byte-for-byte identical output file.






share|improve this answer















You can do this using the command line tool gdal_translate. This is available for Windows, Linux, and Mac OSs (you don't state your OS).



Running:



gdalinfo none.tif


will show the info on the file, including the compression type and the locations:



Driver: GTiff/GeoTIFF
Files: none.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left ( 96.5464352, 17.5351143) ( 96d32'47.17"E, 17d32' 6.41"N)
Lower Left ( 96.5464352, 16.5110349) ( 96d32'47.17"E, 16d30'39.73"N)
Upper Right ( 97.4627168, 17.5351143) ( 97d27'45.78"E, 17d32' 6.41"N)
Lower Right ( 97.4627168, 16.5110349) ( 97d27'45.78"E, 16d30'39.73"N)
Center ( 97.0045760, 17.0230746) ( 97d 0'16.47"E, 17d 1'23.07"N)
[etc]


it doesn't mention a compression type, because it doesn't have one. If your GeoTIFFs aren't compressed they should also not say anything. Note the spatial information is stored in geoTIFF chunks and is output as a bounding box corner set. Great.



Let's compress it. Uncompressed file is 4.7Mb:



$ ls -hs none.tif 
4.7M none.tif


Run this:



$ gdal_translate none.tif lzw.tif -co COMPRESS=LZW
Input file size is 204, 228
0...10...20...30...40...50...60...70...80...90...100 - done.


and get



$ ls -hs lzw.tif 
1.6M lzw.tif


1.6Mbytes in LZW compressed form. Again gdalinfo shows:



$ gdalinfo lzw.tif 
Driver: GTiff/GeoTIFF
Files: lzw.tif
Size is 204, 228
Coordinate System is:
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich",0],
UNIT["degree",0.0174532925199433],
AUTHORITY["EPSG","4326"]]
Origin = (96.546435160745574,17.535114346013060)
Pixel Size = (0.004491576420598,-0.004491576420598)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=LZW
INTERLEAVE=PIXEL
Corner Coordinates:
[etc]


Note the COMPRESSION=LZW message.



Loop over your files using your command line interpreter loop functions.



You might also be able to do this via the gdalUtils package in R which will run these command line commands via a shell.



Indeed for my test file:



library(gdalUtils)
gdal_translate(
src_dataset="none.tif",
dst_dataset="lzwR.tif",
co="COMPRESS=LZW")


results in a byte-for-byte identical output file.







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 days ago

























answered 2 days ago









SpacedmanSpacedman

25.1k23551




25.1k23551







  • 1





    some other -co to consider and offers additional compression (lossless) are -mo "INTERLEAVE=PIXEL" -co "INTERLEAVE=PIXEL" -co "TILED=YES" -co "COMPRESS=LZW" -co "PREDICTOR=2"

    – SaultDon
    2 days ago












  • 1





    some other -co to consider and offers additional compression (lossless) are -mo "INTERLEAVE=PIXEL" -co "INTERLEAVE=PIXEL" -co "TILED=YES" -co "COMPRESS=LZW" -co "PREDICTOR=2"

    – SaultDon
    2 days ago







1




1





some other -co to consider and offers additional compression (lossless) are -mo "INTERLEAVE=PIXEL" -co "INTERLEAVE=PIXEL" -co "TILED=YES" -co "COMPRESS=LZW" -co "PREDICTOR=2"

– SaultDon
2 days ago





some other -co to consider and offers additional compression (lossless) are -mo "INTERLEAVE=PIXEL" -co "INTERLEAVE=PIXEL" -co "TILED=YES" -co "COMPRESS=LZW" -co "PREDICTOR=2"

– SaultDon
2 days ago













3














In addition to @Spacedman's answer, you can set up a loop in R to compress tiffs using LZW with the writeRaster function in the raster package, which still uses GDAL. The options argument allows you to apply LZW compression.



In this example, the file is not overwritten but rather has an "_LZW" appended to the original name. To just overwrite the original file you can omit the paste0 function in writeRaster and just use the file iterator (ie., rfiles[i]). You could also paste a directory path into the file name to aim the compressed files to a different directory. If the tif files are multi-band then you would use stack rather than raster to read the data.



library(raster)
setwd("C:/...")
rfiles <- list.files(getwd(), "tif$")
for(i in 1:length(rfiles))
r <- raster::raster(rfiles[i])
raster::writeRaster(r, paste0(gsub(pattern = "\.tif$", "",
rfiles[i]), "_LZW", ".tif"), overwrite=TRUE,
options="COMPRESS=LZW")






share|improve this answer























  • Thanks Jeffrey Evans and @Spacedman. Just for clarity. I assume that an image georeferenced in qgis and saved as .tif is a geoTif. is this correct? if not... will the solutions you both proposed work anyway?

    – Filippo
    2 days ago











  • I'd be concerned that this would read in the entire +1Gb files. Might not be too efficient. The GDAL command line routines are pretty well optimised.

    – Spacedman
    2 days ago











  • A "geoTIFF" is a TIFF with special metadata blocks in it that give it a spatial reference. Rasters saved from QGIS should have this data and so be valid geoTIFFs - check with the gdalinfo command line or gdalUtils package.

    – Spacedman
    2 days ago















3














In addition to @Spacedman's answer, you can set up a loop in R to compress tiffs using LZW with the writeRaster function in the raster package, which still uses GDAL. The options argument allows you to apply LZW compression.



In this example, the file is not overwritten but rather has an "_LZW" appended to the original name. To just overwrite the original file you can omit the paste0 function in writeRaster and just use the file iterator (ie., rfiles[i]). You could also paste a directory path into the file name to aim the compressed files to a different directory. If the tif files are multi-band then you would use stack rather than raster to read the data.



library(raster)
setwd("C:/...")
rfiles <- list.files(getwd(), "tif$")
for(i in 1:length(rfiles))
r <- raster::raster(rfiles[i])
raster::writeRaster(r, paste0(gsub(pattern = "\.tif$", "",
rfiles[i]), "_LZW", ".tif"), overwrite=TRUE,
options="COMPRESS=LZW")






share|improve this answer























  • Thanks Jeffrey Evans and @Spacedman. Just for clarity. I assume that an image georeferenced in qgis and saved as .tif is a geoTif. is this correct? if not... will the solutions you both proposed work anyway?

    – Filippo
    2 days ago











  • I'd be concerned that this would read in the entire +1Gb files. Might not be too efficient. The GDAL command line routines are pretty well optimised.

    – Spacedman
    2 days ago











  • A "geoTIFF" is a TIFF with special metadata blocks in it that give it a spatial reference. Rasters saved from QGIS should have this data and so be valid geoTIFFs - check with the gdalinfo command line or gdalUtils package.

    – Spacedman
    2 days ago













3












3








3







In addition to @Spacedman's answer, you can set up a loop in R to compress tiffs using LZW with the writeRaster function in the raster package, which still uses GDAL. The options argument allows you to apply LZW compression.



In this example, the file is not overwritten but rather has an "_LZW" appended to the original name. To just overwrite the original file you can omit the paste0 function in writeRaster and just use the file iterator (ie., rfiles[i]). You could also paste a directory path into the file name to aim the compressed files to a different directory. If the tif files are multi-band then you would use stack rather than raster to read the data.



library(raster)
setwd("C:/...")
rfiles <- list.files(getwd(), "tif$")
for(i in 1:length(rfiles))
r <- raster::raster(rfiles[i])
raster::writeRaster(r, paste0(gsub(pattern = "\.tif$", "",
rfiles[i]), "_LZW", ".tif"), overwrite=TRUE,
options="COMPRESS=LZW")






share|improve this answer













In addition to @Spacedman's answer, you can set up a loop in R to compress tiffs using LZW with the writeRaster function in the raster package, which still uses GDAL. The options argument allows you to apply LZW compression.



In this example, the file is not overwritten but rather has an "_LZW" appended to the original name. To just overwrite the original file you can omit the paste0 function in writeRaster and just use the file iterator (ie., rfiles[i]). You could also paste a directory path into the file name to aim the compressed files to a different directory. If the tif files are multi-band then you would use stack rather than raster to read the data.



library(raster)
setwd("C:/...")
rfiles <- list.files(getwd(), "tif$")
for(i in 1:length(rfiles))
r <- raster::raster(rfiles[i])
raster::writeRaster(r, paste0(gsub(pattern = "\.tif$", "",
rfiles[i]), "_LZW", ".tif"), overwrite=TRUE,
options="COMPRESS=LZW")







share|improve this answer












share|improve this answer



share|improve this answer










answered 2 days ago









Jeffrey EvansJeffrey Evans

22.3k22870




22.3k22870












  • Thanks Jeffrey Evans and @Spacedman. Just for clarity. I assume that an image georeferenced in qgis and saved as .tif is a geoTif. is this correct? if not... will the solutions you both proposed work anyway?

    – Filippo
    2 days ago











  • I'd be concerned that this would read in the entire +1Gb files. Might not be too efficient. The GDAL command line routines are pretty well optimised.

    – Spacedman
    2 days ago











  • A "geoTIFF" is a TIFF with special metadata blocks in it that give it a spatial reference. Rasters saved from QGIS should have this data and so be valid geoTIFFs - check with the gdalinfo command line or gdalUtils package.

    – Spacedman
    2 days ago

















  • Thanks Jeffrey Evans and @Spacedman. Just for clarity. I assume that an image georeferenced in qgis and saved as .tif is a geoTif. is this correct? if not... will the solutions you both proposed work anyway?

    – Filippo
    2 days ago











  • I'd be concerned that this would read in the entire +1Gb files. Might not be too efficient. The GDAL command line routines are pretty well optimised.

    – Spacedman
    2 days ago











  • A "geoTIFF" is a TIFF with special metadata blocks in it that give it a spatial reference. Rasters saved from QGIS should have this data and so be valid geoTIFFs - check with the gdalinfo command line or gdalUtils package.

    – Spacedman
    2 days ago
















Thanks Jeffrey Evans and @Spacedman. Just for clarity. I assume that an image georeferenced in qgis and saved as .tif is a geoTif. is this correct? if not... will the solutions you both proposed work anyway?

– Filippo
2 days ago





Thanks Jeffrey Evans and @Spacedman. Just for clarity. I assume that an image georeferenced in qgis and saved as .tif is a geoTif. is this correct? if not... will the solutions you both proposed work anyway?

– Filippo
2 days ago













I'd be concerned that this would read in the entire +1Gb files. Might not be too efficient. The GDAL command line routines are pretty well optimised.

– Spacedman
2 days ago





I'd be concerned that this would read in the entire +1Gb files. Might not be too efficient. The GDAL command line routines are pretty well optimised.

– Spacedman
2 days ago













A "geoTIFF" is a TIFF with special metadata blocks in it that give it a spatial reference. Rasters saved from QGIS should have this data and so be valid geoTIFFs - check with the gdalinfo command line or gdalUtils package.

– Spacedman
2 days ago





A "geoTIFF" is a TIFF with special metadata blocks in it that give it a spatial reference. Rasters saved from QGIS should have this data and so be valid geoTIFFs - check with the gdalinfo command line or gdalUtils package.

– Spacedman
2 days ago

















draft saved

draft discarded
















































Thanks for contributing an answer to Geographic Information Systems Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f318858%2fcompressing-georeferenced-images%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Category:9 (number) SubcategoriesMedia in category "9 (number)"Navigation menuUpload mediaGND ID: 4485639-8Library of Congress authority ID: sh85091979ReasonatorScholiaStatistics

Circuit construction for execution of conditional statements using least significant bitHow are two different registers being used as “control”?How exactly is the stated composite state of the two registers being produced using the $R_zz$ controlled rotations?Efficiently performing controlled rotations in HHLWould this quantum algorithm implementation work?How to prepare a superposed states of odd integers from $1$ to $sqrtN$?Why is this implementation of the order finding algorithm not working?Circuit construction for Hamiltonian simulationHow can I invert the least significant bit of a certain term of a superposed state?Implementing an oracleImplementing a controlled sum operation

Magento 2 “No Payment Methods” in Admin New OrderHow to integrate Paypal Express Checkout with the Magento APIMagento 1.5 - Sales > Order > edit order and shipping methods disappearAuto Invoice Check/Money Order Payment methodAdd more simple payment methods?Shipping methods not showingWhat should I do to change payment methods if changing the configuration has no effects?1.9 - No Payment Methods showing upMy Payment Methods not Showing for downloadable/virtual product when checkout?Magento2 API to access internal payment methodHow to call an existing payment methods in the registration form?