Metadata, licensing & provenance

The record that travels with the data: what it describes, who may use it, which version it is, and what produced it.

The four questions a dataset has to be able to answer about itself. four questions a dataset has to answer about itselfparcels_2026.gpkgwhat does it describe?who may use it, and how?which version is this?what produced it?answer none of them andthe file is a rumourNone of the four is in the geometry, and none of them survives a copy unless it was written down

Metadata is the record that travels with a dataset, and it exists to answer four questions the geometry cannot: what does this describe, who may use it and how, which version is this, and what produced it.

None of the four survives a copy unless somebody wrote them down. A file with no licence cannot be republished, a file with no version cannot be compared with last month’s, and a file with no provenance cannot be defended when a number in it is challenged. The standards — ISO 19115, FGDC, STAC, DCAT — are mostly agreements about where to put those answers so that a machine can find them.

The pages below cover what each standard is for, how to write and read the records from Python, how to attach provenance to a pipeline output, and how to check a catalogue is telling the truth about its own contents.

Learning paths run through this topic too — see the end of this page.

🧭 Start with the concepts

The ideas the how-to guides below assume you already have.

Show every concept in this topic

⚙️ Then do the task

Step-by-step walkthroughs with code you can copy and adapt.

Show every how-to guide in this topic

🔧 When it breaks

The errors this topic produces, with the cause explained rather than just the command.

Related topics

Subjects that keep coming up alongside this one, most overlap first.

Keep browsing

Metadata, licensing & provenance sits in Governance & trust. Every topic on the site is listed on the topics index.