GeoD CLI

Install the GeoD command line on Windows x64 with Node.js 18 or newer:

npm install --global [email protected]
geod --version
geod --help

Or run without a permanent global installation:

npx --yes [email protected] --help

GeoD plans and acquires geodata from a JSON request, writes imagery and GeoJSON with source metadata, and inspects existing bundles:

geod plan --request request.json
geod fetch --request request.json --out ./geod-output
geod inspect --bundle ./geod-output

Choose a built-in raster source or register your own licensed tile URL locally:

geod sources list
geod sources default --id nasa_gibs_blue_marble
geod sources register --id my_tiles --name "My imagery" --url "https://example.com/{z}/{x}/{y}.png" --attribution "Provider"
geod sources probe --id my_tiles --zoom 5 --x 26 --y 12
geod plan --request request.json --source my_tiles

Requests may use imagery.sourceId (and overlays[].sourceId) instead of a URL. sources update and sources remove manage custom entries. CLI registrations stay in the current user's own configuration, separate from the desktop app and GeoStyle. Tianditu sources require your own GEOD_TIANDITU_TOKEN; standard OSM public tiles are blocked for offline exports.

Imagery requests support multiple zoom levels, GeoTIFF/PNG/JPEG mosaics, MBTiles, GeoPackage, raw XYZ tiles, overlays, polygon clipping, TIFF compression and overviews. Add --work-dir ./geod-work to fetch to reuse validated tiles after an interruption. The download and export run on your own computer.

See the GeoD CLI 0.3 guide for request examples and limits.

Version 0.3.0 includes the Windows x64 geod.exe directly in this npm package. Installation does not fetch a binary from GitHub, run a postinstall script, or require Rust, Tauri, GDAL or a separate Visual C++ runtime installation. The Node launcher passes arguments directly to the executable, preserves the current directory and native stdout/stderr, and returns its exit code (including cancellation code 130).

macOS, Linux and Windows ARM64 are not supported by this package version. The npm launcher requires Node.js; the separately published portable ZIP and Windows installer run without Node.js. Fetching map data requires access to the sources in the request and remains subject to their terms and availability. This package does not include map data or an AI service.

Package integrity

The build verifies the frozen upstream portable ZIP, its executable and build metadata before packaging. build-info.json records the native source revision and executable hash. There are no runtime npm dependencies or install hooks.

For maintainers, run node scripts/package-geod-cli-npm.mjs from the repository. The resulting tarball is staged under output/geod-cli-public-0.3.0/npm/; the executable is not checked into the package source directory. Direct packing without the verified executable fails.