i.in.spotvgt(1)
π i.in.spotvgt π
okay so bestie, welcome to i.in.spotvgt, straight out of the GRASS GIS User's Manual. she's a lil module with a big job and honestly? she ate. let's get into it π«Ά
β¨ NAME β¨
i.in.spotvgt β Imports SPOT VGT NDVI data into a raster map. that's it, that's the whole vibe π
π·οΈ KEYWORDS π·οΈ
imagery, import, NDVI, SPOT
π SYNOPSIS π
i.in.spotvgt
i.in.spotvgt --help
i.in.spotvgt [-a] input=name [output=name] [--overwrite] [--help]
[--verbose] [--quiet] [--ui]
π Flags:
-aβ Also import quality map (SM status map layer) and filter NDVI map. she's doing extra credit fr fr β¨--overwriteβ Allow output files to overwrite existing files. no cap, this one's got main character energy π--helpβ Print usage summary--verboseβ Verbose module output--quietβ Quiet module output--uiβ Force launching GUI dialog
π¦ Parameters:
input=name[required]β Name of input SPOT VGT NDVI HDF file. yes bestie, required means REQUIRED, no skipping πoutput=nameβ Name for output raster map
πΈ DESCRIPTION πΈ
so i.in.spotvgt imports SPOT Vegetation (1km, global) NDVI data sets. iconic behavior.
once the import is done, the digital numbers (DN) get remapped to VEGETATION NDVI values and the NDVI color table is applied. and then β plot twist β the imported DN map gets removed after remapping. she cleans up after herself, we love a tidy queen π§
here's the tea tho: apparently missing raster cells due to bad pixel quality are reconstructed by the SPOT operating team in the NDVI file. so you should lowkey compare the differences between the filtered map (that's the -a flag) and the raw NDVI map. side by side, bestie. it's giving detective work π
π NOTES π
The SPOT VGT files are delivered in HDF4 (Hierarchical Data Format Release 4) format. so yeah, it is required to have the GDAL libraries installed with HDF4 support. no HDF4 support? no import. periodt. π
β EXAMPLE β
π Export of entire world SPOT VGT maps
okay so when you're working with SPOT VGT with entire world extent, it is recommended to zoom to w=180W and e=180E instead of using the map extent for map export. why? because these entire world SPOT VGT data are exceeding -180.0 degree, which can lead to unhelpful large East-West coordinates in the exported file. not cute. π
It is also recommended to then use an export command which respects the user settings. Example:
# import:
i.in.spotvgt 0001_NDV.HDF
# export:
g.region w=180W e=180E n=75:00:16.071429N s=56:00:16.069919S res=0:00:32.142857 -p
r.out.gdal 0001_NDV format=GTiff out=spotndvi.tif
slay. copy it, paste it, thank me later π
π₯ SEE ALSO π₯
r.in.gdalr.out.gdal
π REFERENCES π
- SPOT Vegetation (1km, global) NDVI data set server
- SPOT Vegetation FAQ
1.13How must I read the 8 bits of the status map? - Quality map
π AUTHOR π
Markus Neteler
π» SOURCE CODE π»
Available at: i.in.spotvgt source code (history)
Accessed: Saturday Jan 17 05:41:52 2026
Main index | Imagery index | Topics index | Keywords index | Graphical index | Full index
and that's a wrap bestie!! π this whole thing is Β© 2003-2025 GRASS Development Team, GRASS GIS 8.4.2 Reference Manual, running on GRASS 8.4.2. go import some NDVI, you got this π β¨π¦
π¦ 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