i.in.spotvgt(1grass)

🌸 NAME 🌸

i.in.spotvgt — bestie, this is the Imports SPOT VGT NDVI data into a raster map module of GRASS. It lives in the GRASS User's Manual (that's the i.in.spotvgt(1grass) situation, iykyk 💅).

🎀 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 that quality map (the SM status map layer, yes her) and filter the NDVI map 🫶
• --overwrite — allows output files to just. overwrite existing files. no cap.
• --help — prints the usage summary, for when you need a lil recap
• --verbose — verbose module output, she's chatty
• --quiet — quiet module output, she's giving nothing
• --ui — force launches the GUI dialog, very main character

💖 Parameters 💖

• input=name [required] — Name of input SPOT VGT NDVI HDF file. Required, bestie, no skipping ✋
• output=name — Name for output raster map

---

💜 DESCRIPTION 💜

So i.in.spotvgt imports SPOT Vegetation (1km, global) NDVI data sets. Obsessed with her.

After import, the digital numbers (DN) are remapped to VEGETATION NDVI values, and then the NDVI color table is applied. The imported DN map? Gone. Removed after remapping. She said no clutter, only vibes. ✨

Apparently missing raster cells due to bad pixel quality are reconstructed by the SPOT operating team in the NDVI file. So the differences between the filtered map (that's the -a flag energy) and the raw NDVI map should be compared. Do the comparison, it's important 🫡

🌈 NOTES 🌈

The SPOT VGT files are delivered in HDF4 (Hierarchical Data Format Release 4) format. So it is required to have the GDAL libraries installed with HDF4 support. That's not optional, that's a prerequisite, periodt.

💀 No HDF4 support in your GDAL? Then this isn't giving what you need it to give. Go install it first.

🍓 EXAMPLE 🍓

Export of entire world SPOT VGT maps

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. 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 the unhelpful large East-West coordinates.

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

⭐ SEE ALSO ⭐

r.in.gdal, r.out.gdal

🧚 REFERENCES 🧚

• SPOT Vegetation (1km, global) NDVI data set server
• SPOT Vegetation FAQ
• 1.13 How 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)

Latest change: Thursday Aug 21 17:49:43 2025 in commit: f81f4c83c0abe31a2d8ecea1b15975c51551c86f

Main index | Imagery index | Topics index | Keywords index | Graphical index | Full index

---

okay that's the whole page, bestie 🫶 © 2003-2026 GRASS Development Team, GRASS 8.5.0 Reference Manual — and yeah, she's running on GRASS 8.5.0, slay 💅✨