GDAL-DATASET-CHECK(1)

πŸ“¦ version 3.13.3, in alpine 3.24, arch rolling, ubuntu stonking

✨ NAME ✨

gdal-dataset-check β€” bestie, this one checks whether there are errors when reading the content of a dataset 🫢

Added in version 3.13. ✨

So basically gdal dataset check checks whether there are errors when reading the content of a dataset, and it returns 1 as the program exit code (or in the return-code output parameter of the algorithm) if that happens, or 0 when no errors are detected. lowkey the simplest little vibe check a dataset can get πŸ’…

WARNING: Most drivers or data formats do not have a built-in integrity mechanism. Thus a successful run of that program does not necessarily mean that the dataset is identical to the state it had just after being generated. The checks performed are generally sufficient to detect whether the dataset is truncated compared to its expected size, but this is not even necessarily guaranteed for some formats (for example the CSV driver may not be able to detect truncation). 😭 so like, no errors β‰  your file is pristine, ok? keep that in mind fr fr

🌸 SYNOPSIS 🌸

Usage: gdal dataset check [OPTIONS] <INPUT>

Check whether there are errors when reading the content of a dataset.

Positional arguments:
  -i, --input <INPUT>                  Input raster, vector or multidimensional raster dataset [required]

Common Options:
  -h, --help                           Display help message and exit
  --json-usage                         Display usage as JSON document and exit
  --config <KEY>=<VALUE>               Configuration option [may be repeated]
  -q, --quiet                          Quiet mode (no progress bar or warning message) [not available in pipelines]

Advanced Options:
  --oo, --open-option <KEY>=<VALUE>    Open options [may be repeated]
  --if, --input-format <INPUT-FORMAT>  Input formats [may be repeated]

πŸ’– OPTIONS πŸ’–

  • --input <FILENAME> β€” your input vector, raster or multidimensional dataset. Required. like, you literally cannot run this without it bestie πŸ‘‘

πŸŽ€ RETURN STATUS CODE πŸŽ€

The program returns status code 0 in case of success, and non-zero in case of error (non-blocking errors emitted as warnings are considered as a successful execution). So warnings are giving "we're fine actually" energy and errors are giving "nope" energy. πŸ’€


🌈 EXAMPLES 🌈

Example 1: Check whether there are errors when reading a dataset

$ gdal dataset check NE1_50M_SR_W.tif

periodt. that's the whole move. πŸ¦‹


πŸ‘‘ AUTHOR πŸ‘‘

Even Rouault <even.rouault@spatialys.com>


1998-2026


okay that's the whole page, bestie β€” this was GDAL's GDAL-DATASET-CHECK(1) from Aug 18, 2026 (the GDAL manual, in case the version energy wasn't obvious πŸ’…). slay, go check ur datasets, and remember: no errors detected is not a promise, it's a vibe check. 🫢✨

πŸ“¦ where this page comes from