i.ortho.rectify(1grass)
β¨ i.ortho.rectify(1grass) β GRASS User's Manual β¨
okay bestie, buckle up π this is i.ortho.rectify from the GRASS manual, and it's literally the glow-up machine for your imagery.
π¦ NAME π¦
i.ortho.rectify β orthorectifies an image by using the image to photo coordinate transformation matrix. no cap. πΈ
π KEYWORDS π
imagery, orthorectify
β¨ SYNOPSIS β¨
i.ortho.rectify
i.ortho.rectify --help
i.ortho.rectify [-cap] group=name [input=name[,name,...]]
extension=string [resolution=float] [memory=memory in MB]
[method=string] [angle=name] [--overwrite] [--help] [--verbose]
[--quiet] [--ui]
π© Flags
-cβ use the current region settings in the target project (location). the default is to calculate the smallest area, so likeβ¦ if you don't say anything, it figures out the tiniest box that fits. π«Ά-aβ rectify all raster maps in group. every single one. main character behaviour π-pβ enable panorama camera correction π₯β¨--overwriteβ allow output files to overwrite existing files (yes, it will absolutely eat your old files, so be sure)--helpβ print usage summary π--verboseβ verbose module output (it tells you everything, and I mean everything)--quietβ quiet module output π€«--uiβ force launching GUI dialog
π Parameters
group=name[required] β name of input imagery groupinput=name[,name,...]β name of input raster map(s)extension=string[required] β output raster map(s) suffixresolution=floatβ target resolution (ignored if-cflag used)memory=memory in MBβ maximum memory to be used (in MB), and it's the cache size for raster rows. Default:300method=stringβ interpolation method to use Options:nearest,linear,cubic,lanczos,linear_f,cubic_f,lanczos_fDefault:nearestangle=nameβ raster map with camera angle relative to ground surface
π DESCRIPTION π
so i.ortho.rectify rectifies an image by using the image to photo coordinate transformation matrix created by g.gui.photo2image and the rectification parameters created by g.gui.image2target. Rectification is the process by which the geometry of an image is made planimetric. This is accomplished by mapping an image from one coordinate system to another. In i.ortho.rectify the parameters computed by g.gui.photo2image and g.gui.image2target are used in equations to convert x,y image coordinates to standard map coordinates for each pixel in the image. The result is an image with a standard map coordinate system, compensated for relief distortions and photographic tilt. Upon completion of the program the rectified image is deposited in a previously targeted GRASS project (location). it's giving glow-up, truly π
Images can be resampled with various different interpolation methods: nearest neighbor assignment, bilinear and bicubic interpolation. The bilinear and bicubic interpolation methods are also available with a fallback option. These methods "fall back" to simpler interpolation methods along NULL borders. That is, from bicubic to bilinear to nearest. πͺ (ladder descending, iconic)
The process may take an hour or more depending on the size of the image, the speed of the computer, the number files, and the size and resolution of the selected window. so likeβ¦ go make a snack π
The rectified image will be located in the target project when the program is completed. The original unrectified files are not modified or removed. your originals are safe, bestie π€
The optional angle output holds the camera angle in degrees to the local surface, considering local slope and aspect. A value of 90 degrees indicates that the camera angle was orthogonal to the local surface, a value of 0 degrees indicates that the camera angle was parallel to the local surface and negative values indicate that the surface was invisible to the camera. As a rule of thumb, values below 30 degrees indicate problem areas where the orthorectified output will appear blurred. Because terrain shadowing effects are not considered, areas with high camera angles may also appear blurred if they are located (viewed from the camera position) behind mountain ridges or peaks. ποΈ like the mountain is doing a photobomb and there's nothing you can do about it.
i.ortho.rectify can be run directly, specifying options in the command line or the GUI, or it can be invoked as OPTION 8 through i.ortho.photo. If invoked though i.ortho.photo, an interactive terminal is used to determine the options.
πΈ Interactive mode πΈ
You are first asked if all images within the imagery group should be rectified. If this option is not chosen, you are asked to specify for each image within the imagery group whether it should be rectified or not. (a little yes/no interview for every single image, be strong πͺ)
More than one file may be rectified at a time. Each file should have a unique output file name. The next prompt asks you for an extension to be appended to the rectified images.
The next prompt will ask you whether a camera angle map should be produced and if yes, what should be its name. π
After that you are asked if overwriting existing maps in the target project and mapset should be allowed. β οΈ
The next prompt asks you to select one of two windows:
Please select one of the following options
1. Use the current window in the target project
2. Determine the smallest window which covers the image
>
If you choose option 2, you can also specify a desired target resolution.
i.ortho.rectify will only rectify that portion of the image that occurs within the chosen window. Only that portion will be relocated in the target database. It is therefore important to check the current window in the target project if choice number one is selected. π fr fr check it.
Next you are asked to select an interpolation method.
Please select one of the following interpolation methods
1. nearest neighbor
2. bilinear
3. bicubic
4. bilinear with fallback
5. bicubic with fallback
>
The last prompt will ask you about the amount of memory to be used by i.ortho.rectify. and then you're done, slay π
π SEE ALSO π
i.ortho.photo, i.ortho.camera, g.gui.photo2image, g.gui.image2target, i.ortho.init, i.rectify
π AUTHORS π
- Mike Baba, DBA Systems, Inc.
- Updated rectification and elevation map to FP 1/2002 Markus Neteler
- Bugfixes and enhancements 12/2010 Markus Metz
π§ SOURCE CODE π§
Available at: i.ortho.rectify source code (history)
Latest change: Saturday Oct 25 22:50:58 2025 in commit: ee87f21833475fd40805f58d1702f7d64478a27b
Main index | Imagery index | Topics index | Keywords index | Graphical index | Full index
and that's the whole manual bestie, no notes, periodt π
okay and for the cute sign-off: this whole thing is Β© 2003-2026 GRASS Development Team, from the GRASS 8.5.0 Reference Manual, and the manual page footer itself reads GRASS 8.5.0 on one side and i.ortho.rectify(1grass) on the other. so like, GRASS 8.5.0, version energy, reference manual date energy. obsessed π«Άβ¨
π¦ where this page comes from
- alpine 3.24: grass-gis-doc 8.5.0-r1 Β· GPL-2.0-or-later
- ubuntu stonking: grass-doc 8.5.0-1ubuntu1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms