r.in.aster(1)
π r.in.aster β bestie edition π
okay so this is r.in.aster, a GRASS GIS manual page, and it's literally about georeferencing, rectifying, and importing Terra-ASTER imagery + relative DEMs using gdalwarp. no cap, it's a whole vibe. π°οΈβ¨
π NAME π
r.in.aster β georeference, rectify, and import Terra-ASTER imagery and relative DEMs using gdalwarp. it's giving satellite glow-up energy fr fr π°οΈπ
π KEYWORDS π
raster, import, imagery, ASTER, elevation
β¨ SYNOPSIS β¨
r.in.aster
r.in.aster --help
r.in.aster input=name proctype=string band=string output=name
[--overwrite] [--help] [--verbose] [--quiet] [--ui]
π«Ά Flags π«Ά
--overwriteβ lets your output files just bulldoze any existing files in their way. main character energy, honestly. π₯--helpβ prints the usage summary so you're not out here guessing. π--verboseβ verbose module output, aka it tells you EVERYTHING. talkative queen. π£οΈ--quietβ quiet module output. shhh, she's mysterious. π€«--uiβ forces the GUI dialog to launch. pop-up era. πͺβ¨
πΈ Parameters πΈ
input=name[required] β name of the input ASTER image. yes bestie, you gotta tell her which one. πproctype=string[required] β the ASTER imagery processing type, and your options are Level 1A, Level 1B, or relative DEM. pick your fighter:- Options:
L1A,L1B,L1T,DEM - Default:
L1B
- Options:
band=string[required] β list the L1A, L1B or L1T band you want to translate (1,2,3n,...), or just sayallif you want every single band translated. go big or go home. πΆ- Default:
all
- Default:
output=name[required] β base name for the output raster map (the band number gets appended to the base name, so it knows which sibling is which π)
π DESCRIPTION π
r.in.aster rectifies, georeferences, and imports Terra-ASTER imagery into your current project using gdalwarp, hdf 4, and r.in.gdal, and it pulls the projection parameters from g.proj. she can import Level 1A, Level 1B, their relative DEM products, and Level 1T. versatile icon. π¦
You can run this program interactively or non-interactively from the command line β either way works, no gatekeeping. In either case, you (yes you) have to specify:
- an input
*.hdffile name - the type of processing used
- the image band to import
- an output GRASS raster map name
The type parameter can take values of L1A, L1B, L1T or DEM.
The band parameter can take values of 1, 2, 3n, 3b, 4-14
π₯ NOTES π₯
r.in.aster requires the GDAL library to be in the user's path and the hdf 4 driver to be installed. Also, the GDAL library must be compiled with hdf support. no hdf support, no slay. that's just the rules. π
bestie pls double-check your GDAL build before you come crying to me, k? π₯Ί
π AUTHORS π
Michael Barton, Arizona State University and Paul Kelly
β SOURCE CODE β
Available at: r.in.aster source code (history)
Accessed: Saturday Jan 17 05:41:52 2026
Main index | Raster index | Topics index | Keywords index | Graphical index | Full index
Β© 2003-2025 GRASS Development Team, GRASS GIS 8.4.2 Reference Manual
and that's the whole page, bestie!! π this was r.in.aster(1) from the GRASS GIS 8.4.2 User's Manual, and the page was accessed Saturday Jan 17 05:41:52 2026. go forth and import some ASTER imagery, you absolute legend. periodt. ππ¦β¨
π¦ where this page comes from
- fedora 44: grass 8.4.2-4.fc44 Β· 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