🔌

DCAT

The catalogue vocabulary that lets one open-data portal harvest another. It is the difference between a portal that is listed nationally and one that is an island.

How this list is decided. Membership is not a field an editor set: it is every published entry whose own text names DCAT, matched at build time, with the sentence printed under each row so you can judge the match yourself. 3 entries in 3 cities.

✔ Every published entry is checked against the public sources it cites before publication.

Where it appears in the atlas

🇬🇧 Bristol Open Data Bristol: one licence stated, forty-four in the metadata Official

In the portal's machine-readable DCAT feed, the form an aggregator reads, 70 of the 201 datasets present expose a licence a machine can resolve, 69 of them the Open Government Licence v3 URL and one an NHS terms page, while 39 expose an empty licence field.

🇫🇷 Nice OpenData NCA: a clean licence on a catalogue that stopped growing since 2014 · Official

Portal's own policy page: "Nice Côte d'Azur propose d'utiliser la Licence Ouverte d'Etalab", open-source stack (Drupal, CKAN, Piwik), DCAT compliance for harvesting, membership of OpenDataFrance, and partnership agreements with member communes defining each party's role.

🇺🇸 Washington D.C. Washington D.C.'s open data policy, ArcGIS Hub portal and licence since 2014 · Official

The portal, opendata.dc.gov, runs on Esri's ArcGIS Hub and serves a DCAT-US feed.

Others in this group

The whole layer

Every standard, protocol and licence the atlas names, with the open-data licence ladder in one table: Standards & licences.

✉️ Get the next source-checked smart-city project in your inbox

One short email a week: the Landmark, one Insight, the new cities. No spam, one-click unsubscribe. About the newsletter · RSS