geospatial-viewers
Skill78 starsChanged 8 months agoApache-2.0View on GitHub
This skill should be used when viewing, previewing, or inspecting geospatial files from the command line. Covers interactive raster viewing (viewtif), interactive vector viewing (viewgeom), and non-interactive terminal-inline viewing (viewinline) for GeoTIFF, Shapefile, GeoJSON, GeoPackage, GeoParquet, CSV, HDF, NetCDF, and more.
In this repository19 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- detect-objectsSkill
- gdalSkill
- geoparquet-validationSkill
- geospatial-frontendSkill
- geozarrSkill
- overture-dataSkill
- parallel-geospatialSkill
- planet-bulk-downloadSkill
- pmtiles-pipelineSkill
- portolan-bootstrapSkill
- portolan-cliSkill
- portolan-thumbnailsSkill
- reading-portolanSkill
- register-catalogSkill
- search-stacSkill
- sourcecoopSkill
- tesseraSkill
- zarr-multiscalesSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Need interactive zoom/pan/contrast?: Use viewtif (rasters) or viewgeom (vectors).
- Very specific: line 19
Quick inline preview in iTerm2/WezTerm/Konsole?: Use viewinline (no GUI window, renders in terminal).
- Very specific: line 20
CSV/Parquet analysis (stats, histograms, SQL)?: Use viewinline.
- Very specific: line 21
Vector file as table (describe, filter, sort)?: Use viewinline --table.
- Very specific: line 22
Headless server / SSH / HPC?: Use viewinline (renders on local terminal, no X11 needed).
- Very specific: line 26
Always prepend uvx to auto-install and run without modifying the local environment:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Geospatial Viewers
Three CLI tools for quick-look inspection of geospatial data. Always run them via uvx so they are auto-installed without polluting the project environment.
| Tool | Purpose | PyPI |
| viewtif | Interactive Qt viewer for rasters (GeoTIFF, HDF, NetCDF, FileGDB) | uvx viewtif |
| viewgeom | Interactive Qt viewer for vector datasets | uvx viewgeom |
| viewinline | Non-interactive terminal-inline viewer (rasters, vectors, CSV, Parquet) | uvx viewinline |
Choosing the Right Tool
- Need interactive zoom/pan/contrast? Use
viewtif(rasters) orviewgeom(vectors). - Quick inline preview in iTerm2/WezTerm/Konsole? Use
viewinline(no GUI window, renders in terminal). - CSV/Parquet analysis (stats, histograms, SQL)? Use
viewinline. - Vector file as table (describe, filter, sort)? Use
viewinline --table. - Headless server / SSH / HPC? Use
viewinline(renders on local terminal, no X11 needed).
Running with uvx
Always prepend uvx to auto-install and run without modifying the local environment:
uvx viewtif file.tif
uvx viewgeom boundaries.geojson
uvx viewinline file.tifFor optional extras, use the --from flag:
uvx --from "viewtif[geo]" viewtif raster.tif --shapefile overlay.shp
uvx --from "viewtif[netcdf]" viewtif data.nc
uvx --from "viewgeom[parquet]" viewgeom data.geoparquetQuick Reference
# Raster inspection
uvx viewtif image.tif
uvx viewtif image.tif --shapefile boundaries.shp
uvx viewtif image.tif --rgb 4 3 2
uvx viewtif image.tif --vmin 280 --vmax 320
uvx viewtif huge_raster.tif --scale 10
# NetCDF / HDF
uvx --from "viewtif[netcdf]" viewtif data.nc --subset 1 --timestep 100
# FileGDB raster
uvx viewtif "OpenFileGDB:/path/to.gdb:RasterName"
# Remote files
AWS_NO_SIGN_REQUEST=YES uvx --from "viewtif[geo]" viewtif s3://bucket/raster.tif --shapefile local.shp
# Vector inspection
uvx viewgeom boundaries.geojson
uvx viewgeom landuse.shp --column area_sqkm
uvx viewgeom earthquake.geojson --filter "mag > 5"
uvx viewgeom earthquake.geojson --duckdb "SELECT * FROM data WHERE mag > 5"
uvx viewgeom earthquake.geojson --duckdb "SELECT mag FROM data WHERE mag > 5" --save filtered.geojson
# Terminal-inline preview
uvx viewinline file.tif --colormap
uvx viewinline sentinel2.tif --rgb 4 3 2
uvx viewinline boundaries.geojson --color-by population
uvx viewinline file.nc --subset 1 --timestep 10
# CSV / Parquet analysis
uvx viewinline data.csv --describe
uvx viewinline data.csv --hist area_km2 --bins 30
uvx viewinline data.csv --scatter longitude latitude
uvx viewinline data.csv --sql "SELECT State, AVG(Income) FROM data GROUP BY State"
# Vector as table
uvx viewinline counties.shp --table --describe
uvx viewinline data.geoparquet --table --where "POP > 100000" --sort POP --desc
# Image gallery
uvx viewinline outputs/ --gallery 4x3References
references/viewtif.mdreferences/viewgeom.mdreferences/viewinline.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

