Compressing georeferenced images Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm 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 丫 mean? 丫是什么意思?
Should man-made satellites feature an intelligent inverted "cow catcher"?
Is this Kuo-toa homebrew race balanced?
Why are two-digit numbers in Jonathan Swift's "Gulliver's Travels" (1726) written in "German style"?
Did pre-Columbian Americans know the spherical shape of the Earth?
First paper to introduce the "principal-agent problem"
Is the time—manner—place ordering of adverbials an oversimplification?
Was the pager message from Nick Fury to Captain Marvel unnecessary?
Keep at all times, the minus sign above aligned with minus sign below
How to ask rejected full-time candidates to apply to teach individual courses?
Plotting a Maclaurin series
How does TikZ render an arc?
Calculation of line of sight system gain
Why complex landing gears are used instead of simple, reliable and light weight muscle wire or shape memory alloys?
Baking rewards as operations
Fit odd number of triplets in a measure?
Are there any irrational/transcendental numbers for which the distribution of decimal digits is not uniform?
Adapting the Chinese Remainder Theorem (CRT) for integers to polynomials
What is a more techy Technical Writer job title that isn't cutesy or confusing?
Getting representations of the Lie group out of representations of its Lie algebra
Where did Ptolemy compare the Earth to the distance of fixed stars?
French equivalents of おしゃれは足元から (Every good outfit starts with the shoes)
Sally's older brother
Why are current probes so expensive?
Compressing georeferenced images
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm 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;
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
add a comment |
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
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
Apr 15 at 16:01
add a comment |
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
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
qgis r georeferencing compression
edited Apr 15 at 15:53
Vince
14.8k32850
14.8k32850
asked Apr 15 at 15:52
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
Apr 15 at 16:01
add a comment |
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
Apr 15 at 16:01
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
Apr 15 at 16:01
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
Apr 15 at 16:01
add a comment |
2 Answers
2
active
oldest
votes
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.
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
Apr 15 at 18:34
add a comment |
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")
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
Apr 15 at 18:03
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
Apr 15 at 18:25
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 thegdalinfo
command line orgdalUtils
package.
– Spacedman
Apr 15 at 18:27
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
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
Apr 15 at 18:34
add a comment |
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.
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
Apr 15 at 18:34
add a comment |
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.
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.
edited Apr 15 at 17:17
answered Apr 15 at 17:02
SpacedmanSpacedman
25.2k23551
25.2k23551
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
Apr 15 at 18:34
add a comment |
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
Apr 15 at 18:34
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
Apr 15 at 18:34
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
Apr 15 at 18:34
add a comment |
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")
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
Apr 15 at 18:03
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
Apr 15 at 18:25
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 thegdalinfo
command line orgdalUtils
package.
– Spacedman
Apr 15 at 18:27
add a comment |
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")
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
Apr 15 at 18:03
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
Apr 15 at 18:25
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 thegdalinfo
command line orgdalUtils
package.
– Spacedman
Apr 15 at 18:27
add a comment |
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")
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")
answered Apr 15 at 17:25
Jeffrey EvansJeffrey Evans
22.3k22871
22.3k22871
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
Apr 15 at 18:03
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
Apr 15 at 18:25
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 thegdalinfo
command line orgdalUtils
package.
– Spacedman
Apr 15 at 18:27
add a comment |
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
Apr 15 at 18:03
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
Apr 15 at 18:25
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 thegdalinfo
command line orgdalUtils
package.
– Spacedman
Apr 15 at 18:27
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
Apr 15 at 18:03
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
Apr 15 at 18:03
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
Apr 15 at 18:25
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
Apr 15 at 18:25
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
Apr 15 at 18:27
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
Apr 15 at 18:27
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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
Apr 15 at 16:01