Tool

Validate a GB LTDS CIM file against official Ofgem profiles.

Upload an RDF/Turtle file, choose a profile (EQ v7, SCR v3, SYSCAP v5, Header v1), and run SHACL validation. Free, open, no sign-in. Results include conformance status, per-shape violations, and actionable error messages. Tool loads below.

20Route 20 · Data and standards
Interactive SHACL validator 4 profiles loaded React island Last verified

What this tool does

  • Accepts an LTDS CIM file as RDF/Turtle or RDF/XML, up to 2 MB.
  • Runs SHACL validation against the selected Ofgem profile.
  • Reports conformance, violations, and warnings with line numbers.
  • Points to official artefacts for every profile loaded.
  • Works in-browser; no file ever leaves your device.
SHACL validation tool with LTDS profile selector and results panel

24 July 2025LTDS v2-1-0 goes live · first SHACL-validated release

SHACL validation at scale lets every analyst confirm DNO data is conformant before using it.

Before v2-1-0, every consumer of LTDS data had to guess whether a submission was valid. No standard check existed. With the new release, SHACL validation is the public standard. Any file that passes the rules is structurally conformant; any file that fails has a precise set of violations.

This validator runs the same rules Ofgem uses. You can test a submission before publication, verify a DNO file before a connection study, or run a diff across years to see how a network model has changed.

What will you test first?

Run the tool below. Full documentation on the LTDS profiles is on the overview route.

Tool

LTDS validator

The tool runs in an isolated iframe for security. Theme, reduced-motion and height are synchronised from this page. If the tool fails to load, your browser may block the embed; open the direct route at /gb-islands/ltds-validator.

Interactive tool · LTDS validator

Validator runs against Ofgem LTDS v2-1-0 profiles (EQ v7, SCR v3, SYSCAP v5, Header v1). Source files are hosted at [data/gb-energy/ltds/release-catalog.v2-1-0.json](data/gb-energy/ltds/release-catalog.v2-1-0.json).

Section · Next steps

What to do when your file fails.

A SHACL failure is informative, not fatal. Each violation identifies a specific shape constraint that was not met. Three common failure modes with different fixes.

Most failures cluster around a small number of root causes. Check for missing required properties. Check for cardinality violations. Check for datatype mismatches. This is the most common failure mode. A single source-system bug produces many violations. Start over Less common but hard to debug. Check the source system for duplicate records and asset-id collisions. Start over Fastest to fix once identified. Usually a serialisation configuration issue rather than a data issue. Start over

Check your understanding

Two quick questions.

Semantic meaning of the data Query performance Structural conformance of RDF data to a shape File signature authenticity The data is wrong The submission does not match the profile structure You have been fined Your licence is revoked

Key takeaways

  • This validator runs the Ofgem v2-1-0 SHACL rules against your LTDS file.
  • Supported profiles: EQ v7, SCR v3, SYSCAP v5, Header v1.
  • No file leaves your browser; validation runs locally.
  • A SHACL failure lists the specific shape constraint missed. Fix at source and revalidate.
  • For the regulatory context, read the LTDS overview route.

References

  1. Ofgem: LTDS

    v2-1-0 release, SHACL constraints, profile versions.

    Primary data source.

  2. W3C SHACL

    Validation language specification.

    Standard reference.

Continue with CIM detail for the theoretical basis of the LTDS data model.