Glossary
DCAT distribution fields
DCAT distribution fields are the metadata elements attached to each downloadable distribution of a catalogued dataset - notably downloadURL, mediaType, licence, byte_size and modified dates. Reading them programmatically lets you validate file type, size and licence before downloading a single file.
What is DCAT distribution fields?
In DCAT, a dataset record describes the intellectual object and each distribution describes one downloadable file of it. The distribution is where the operational fields live: where to fetch the file, what format it is, how big it is, under what licence, and when it last changed.
The cataloged records show both sides of the Atlantic using the same pattern. The Data.gov record description cites 'per-distribution downloadURLs and mediaType fields'; data.europa.eu is described as carrying 'a licence and byte_size recorded on every distribution' and 'per-distribution licence, byte size and modified dates'. The aluminium search record lists 'JSON-LD / DCAT-AP' among its formats, and its licence note states that most listed datasets 'display their own licence reference' while resources lacking licence information require consulting 'the licence conditions in the original portal'. That last clause is the operational catch: the field can be empty, and empty means a trip to the source.
Why does DCAT distribution fields matter when choosing a dataset?
Distribution fields are the difference between a harvest script that survives and one that downloads 4 GB of PDFs at 3 a.m.
- mediaType prevents format surprises. A dataset advertising CSV may distribute XLSX; checking mediaType per distribution catches that before your parser breaks.
- byte_size is your bandwidth budget. data.europa.eu records byte size on every distribution, so a harvest can skip or schedule the multi-gigabyte files instead of discovering them mid-download.
- Licence per distribution is a legal boundary. Because the licence URI attaches to each file, one dataset can mix commercial delivery terms 4.0 and unlicensed resources - redistributing the bundle without reading each licence is the risk.
- Modified dates drive incremental pulls. Per-distribution modified dates let you re-fetch only changed files; dataset-level dates hide which of twenty distributions actually moved.
How do you evaluate DCAT distribution fields in a data source?
- Confirm downloadURL and mediaType exist per file. The cataloged Data.gov description cites 'per-distribution downloadURLs and mediaType fields' - a catalog that only links landing pages cannot be harvested automatically.
- Check byte_size before large pulls. data.europa.eu records 'a licence and byte_size recorded on every distribution'; use it to schedule or skip heavy files.
- Read the licence URI on every distribution. The licence is 'declared per distribution via a URI (e.g. creativecommons.org/licenses/by/4.0)'; treat a missing licence as unresolved and consult the original portal, as the cataloged terms direct.
Related terms
Terms that sit next to distribution fields in a DCAT harvest:
- dcat-catalog-search-api — The unauthenticated search endpoint that returns records with these distribution fields.
- per-distribution-license — The licence declaration attached to each downloadable file rather than the dataset.
Frequently asked questions
What fields does a DCAT distribution carry?
The file-level metadata: downloadURL, mediaType, licence, byte_size and modified dates. The cataloged data.europa.eu records describe 'a licence and byte_size recorded on every distribution'.
Why check the licence per distribution instead of per dataset?
Because the licence URI attaches to each file. data.europa.eu declares the licence 'per distribution via a URI (e.g. creativecommons.org/licenses/by/4.0)', so one dataset can contain files under different terms.
What if a distribution has no licence field?
Treat it as unresolved. The cataloged portal terms state that for resources lacking licence information users must consult the licence conditions in the original portal before reuse.
Datasets containing this field
Datasets containing DCAT distribution fields
6 datasets carry dcat distribution fields in the catalog. Open one, count the fields, judge for yourself.
Al Circle - aluminium prices and industry portal
Company name · Country · Product categories …+5 more
Data.gov Catalog - Telecommunications & Carrier Datasets
dcat.title · dcat.description · dcat.publisher.name …+11 more
EU Open Data Portal - Telecommunications Carrier Datasets
id · title · description …+11 more
Wikipedia - List of Mobile Network Operators (Global Top 25 + Country Lists)
Rank · Company · Main markets …+5 more
Wikipedia List of Mobile Virtual Network Operators in the United States
Company · Host network(s) · Market …+7 more
Every listing shows the field dictionary, sample rows, and coverage before you commit. API, files, or your warehouse. Daily, weekly, or hourly.
Get sample rows