open-elevation-cli

open-elevation

Elevation data for any GPS coordinate

open-elevation is a single pure-Go binary. It reads public open-elevation data over plain HTTPS, shapes it into clean records, and prints output that pipes into the rest of your tools. No API key, nothing to run alongside it.

The same package is also a resource-URI driver, so a host program like ant can address open-elevation as open-elevation:// URIs.

Install

go install github.com/tamnd/open-elevation-cli/cmd/open-elevation@latest

Or grab a prebuilt binary from the releases, or run the container image:

docker run --rm ghcr.io/tamnd/open-elevation:latest --help

Usage

open-elevation page <path>                      # fetch one page as a record
open-elevation page <path> -o json              # as JSON, ready for jq
open-elevation page <path> --template '{{.Body}}'  # just the readable body text
open-elevation links <path>                     # the pages it links to, one per line
open-elevation --help                           # the whole command tree

Every command shares one output contract: -o table|json|jsonl|csv|tsv|url|raw, --fields to pick columns, --template for a custom line, and -n to limit. The default adapts to where output goes (a table on a terminal, JSONL in a pipe), so the same command reads well by hand and parses cleanly downstream.

This is a fresh scaffold. It ships one example resource type, page, wired end to end. Model the real open-elevation records in open-elevation/ and declare their operations in open-elevation/domain.go; each one becomes a command, an HTTP route, and an MCP tool at once.

Serve it

The same operations are available over HTTP and as an MCP tool set for agents, with no extra code:

open-elevation serve --addr :7777    # GET /v1/page/<path>  returns NDJSON
open-elevation mcp                   # speak MCP over stdio

Use it as a resource-URI driver

open-elevation registers a open-elevation domain the way a program registers a database driver with database/sql. A host enables it with one blank import:

import _ "github.com/tamnd/open-elevation-cli/open-elevation"

Then ant (or any program that links the package) dereferences open-elevation:// URIs without knowing anything about open-elevation:

ant get open-elevation://page/<path>   # fetch the record
ant cat open-elevation://page/<path>   # just the body text
ant ls  open-elevation://page/<path>   # the pages it links to, each addressable
ant url open-elevation://page/<path>   # the live https URL

Development

cmd/open-elevation/   thin main: hands cli.NewApp to kit.Run
cli/                 assembles the kit App from the open-elevation domain
open-elevation/                the library: HTTP client, data models, and domain.go (the driver)
docs/                tago documentation site

make build      # ./bin/open-elevation
make test       # go test ./...
make vet        # go vet ./...

Releasing

Push a version tag and GitHub Actions runs GoReleaser, which builds the archives, Linux packages, the multi-arch GHCR image, checksums, SBOMs, and a cosign signature:

git tag v0.1.0
git push --tags

The Homebrew and Scoop steps self-disable until their tokens exist, so the first release works with no extra secrets.

License

Apache-2.0. See LICENSE.