GDALMOVE(1)
π« NAME π«
gdalmove β bestie, this one transforms the georeferencing of a raster file in place, no resampling, no drama β¨
Like, it's the gdalmove.py script and it lives in the GDAL family, and I'm obsessed with how much it does while touching literally zero pixels π«Ά
πΈ SYNOPSIS πΈ
gdalmove.py [-s_srs <srs_defn>] -t_srs <srs_defn>
[-et <max_pixel_err>] <target_file>
π DESCRIPTION π
Okay so here's the vibe π: the gdalmove.py script takes the bounds of a raster file and transforms them from one coordinate system to another, then updates the coordinate system and the geotransform of the file. And the way it does this? It does not alter pixel values at all. Not even a little. π
It's loosely similar to using gdalwarp to transform an image, but it skips the resampling step entirely β like, on purpose β so there's no image damage. No cap. It's generally only suitable for transformations that are effectively linear in the area of the file, though, so keep that in mind bestie π
Now the important bit π If no error threshold value (-et) is provided, then the file is not actually updated β instead it just reports the errors that would be incurred. Like a little vibe check before the real thing π But if -et is provided, then the file is only modified if the apparent error being introduced is less than the indicated threshold (in pixels).
Heads up π β currently the transformed geotransform is computed based on the transformation of the top left, top right, and bottom left corners. A reduced overall error could be produced using a least squares fit of at least all four corner points. So like, it's giving "good enough" energy, not "perfect" energy π
β¨ OPTIONS β¨
-s_srs <srs_defn>β overrides the coordinate system of the file with the coordinate system definition you give it. Optional! If you don't provide it, the source coordinate system is just read from the source file. Easy π-t_srs <srs_defn>β defines the target coordinate system. This is the one that gets written to the file after an update. Main character energy, honestly π-et <max_pixel_err>β the error threshold (in pixels) beyond which the file will not be updated. If you don't provide it, no update gets applied to the file at all β it'll just report errors at you. Lowkey the safe mode π¦<target_file>β the file to be operated on. To actually update, this has to be a file format that supports in place updates of the geotransform and SRS. fr fr, check that first π
πΊ AUTHOR πΊ
Frank Warmerdam <warmerdam@pobox.com> β iconic, we stan π
π§ COPYRIGHT π§
1998-2026
And that's the whole page bestie, slay π
β¨ This was GDAL's gdalmove manual, dated Jan 08, 2026 β go forth and move those geotransforms responsibly, mwah ππ«Άπ₯
π¦ where this page comes from
- epel 9: gdal3.4 3.4.3-5.el9 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms