Unified TIDAS CLI

The TIDAS command-line tools are distributed as one cross-platform Rust executable named tidas. This site documents stable command semantics; the authoritative source for versions, platform archives, checksums, and installation prerequisites is the GitHub Latest Release. This keeps a copied version number from drifting away from the actual release.

🚀 Obtain and verify a release

End users should choose the prebuilt archive for their operating system and architecture from Latest Release, then verify it against the SHA256SUMS from that same release. An attached Homebrew formula or Winget manifest describes the corresponding archive and hash; consult the release notes before assuming an external tap or Winget Community package is available.

Developers who install from crates.io should first check the release's Rust and native dependency requirements, then use the version selected from Releases:

# Copy the version from Releases/latest and remove a leading v if present.
TIDAS_VERSION="<release-version>"
cargo install tidas --version "$TIDAS_VERSION" --locked

After installation, do not infer the version from an archive name. Inspect the binary that is actually on the command path and its embedded asset fingerprints:

tidas version --format json

This output is the preferred way to confirm the effective CLI and contract versions together with the JSON Schema, XSD, XSLT, and methodology fingerprints.

🔍 Seven unified subcommands

• tidas convert converts between supported TIDAS JSON and eILCD XML paths.

• tidas import brings supported EcoSpold, SimaPro, openLCA, or ILCD sources into the unified workflow.

• tidas export creates deterministic TIDAS/ILCD ZIPs from database records and optional object storage.

• tidas validate validates TIDAS JSON or ILCD XML offline and can write a deterministic JSONL issue stream.

• tidas release validates, converts, and builds reproducible release packages.

• tidas ruleset inspects the rulesets packaged with the executable.

• tidas version reports binary, contract, asset, and runtime fingerprints.

Use tidas <command> --help as the source of truth for current flags. For automation, prefer the command's supported structured output, report-file, and resource-bound options.

✅ Understand validation levels

--schema-only is a structural Schema diagnostic. It is not a complete consistency check and does not prove that a dataset can be converted to eILCD. Before delivery, run ordinary validate and, when the target workflow requires eILCD, exercise the applicable conversion path:

tidas validate ./tidas-package --schema-only --format json
tidas validate ./tidas-package --issues ./issues.jsonl --format json
tidas convert ./tidas-package --output ./eilcd-package --to ilcd --format json

Other common entry points include:

tidas convert ./eilcd-data --output ./tidas-package --to tidas --format json
tidas import ./database.zip --output ./imported --target both --format json

The CLI embeds and integrity-checks the JSON Schema, XSD, XSLT, and methodology assets needed at runtime, so normal use does not require copying assets from old source directories. For audit or reproduction, retain the fingerprint output of tidas version --format json.

Migrate from legacy commands

The former standalone executables and Python-package argument layout are no longer the active path documented by this site:

Inputs are usually positional, outputs use --output, and conversion direction uses --to ilcd|tidas. Inspect tidas <command> --help for every migrated step instead of carrying legacy flags forward.

📬 Get help and contribute

• 📚 Source and complete CLI documentation: tidas-tools repository

• 📌 Questions and feature requests: Create an Issue

• 📦 Authoritative release history: GitHub Releases

TIDAS is an open-source LCA data system developed by the Tiangong project. See TIDAS architecture for the boundary between the data contract and its tools.