Open Data Hub Cli — Open Data Hub 命令行工具

Open Data Hub 命令行工具

Use odh for public Open Data Hub API work. It is JSON-first, non-interactive, and suitable for scripts and 代理s.

First 检查s

运行 these before relying on the 命令行工具:

odh version odh doctor --timeout 10s

If odh is not 安装ed, use the latest release from galjos/odh-命令行工具 or build it from source:

go build -o odh ./cmd/odh

When 运行ning from a source 检查out, use ./odh instead of odh.

API Discovery

列出 known API surfaces:

odh APIs

Fetch OpenAPI specs as JSON:

odh openAPI mobility odh openAPI tourism

Use odh call for known 端点s rather than scrAPIng a UI:

odh call tourism /v1/ODHActivityPoi \ --param pagenumber=1 \ --param pagesize=1 \ --param 种子=42

Curated Commands

Tourism point of interest:

odh tourism poi --limit 1 --种子 42 --fields DetAIl.en.Title,Gps信息

Mobility latest measurements:

odh mobility latest \ --station-type EChargingStation \ --data-type number-avAIlable \ --limit 5

Mobility type and data-type discovery:

odh mobility types --kind event odh mobility datatypes --station-type TrafficSensor --origin A22 --limit 100

A22 traffic diagnostics:

odh mobility 事件 --origin A22 --latest --limit 20 odh a22 状态 --limit 10

Interpretation Rules 解析 stdout as JSON. Treat nonzero exit codes as 失败s. Treat stderr as diagnostics, not data. Do not infer live A22 traffic from TrafficForecast rows alone. Prefer odh a22 状态 for A22 because it 报告s current-event avAIlability and warns when forecast rows are not current incident data. Use --where and --param key=value instead of manually constructing 查询 strings when a curated command supports them.