Démonstration Datopian, site non officiel de la Communauté d'Agglomération Pays Basque

Datopian erakustaldia, Euskal Herriko Aglomerazio Elkartearen webgune ez ofiziala (itzulpen automatikoa / traduction automatique, à relire)

API and developers

This demo is a static site: the catalogue, every table and the metadata are published as files, in CKAN and DCAT-AP formats. No key, open CORS.

Behind this site the catalogue runs on the PoC’s CKAN service (CKAN 2.11): the same data is served by CKAN’s standard Action API, with search, filters and SQL over the tables; existing CKAN clients and the data.gouv.fr harvester work unchanged.

docs.ckan.org/en/2.11/api

The catalogue

Every dataset: title, description, themes, formats, service

/data/search.json
curl
curl '/data/search.json'

Publishers (CKAN organization_list format)

/data/organizations.json

Themes (CKAN group_list format)

/data/groups.json

A dataset’s metadata (CKAN package_show format): RGA2020_epci

/data/datasets/rga2020_epci.json

Governance report: freshness, schemas, licences and personal data per dataset, per service and per organisation

/data/quality.json

The tables

Every table is a JSON file (CKAN DataStore format: columns then rows), a CSV and, with geometries, a GeoJSON. Example: RGA2020_epci

The whole table as JSON

/data/tables/264fc8d3-8074-4133-a155-03571ba4b424.json
curl
curl '/data/tables/264fc8d3-8074-4133-a155-03571ba4b424.json'

A table with geometries as GeoJSON: RGA2020_epci

/data/tables/264fc8d3-8074-4133-a155-03571ba4b424.geojson

DCAT-AP

The whole catalogue in DCAT-AP 3 (ckanext-dcat), with EU frequency and licence URIs and high-value dataset categories. Every dataset page also gives its own DCAT record.

Catalogue (Turtle)

/catalog.ttl
curl
curl '/catalog.ttl'

Catalogue (RDF/XML)

/catalog.xml

Catalogue (JSON-LD)

/catalog.jsonld

The CAPB’s and the communes’ own datasets (RDF/XML): what data.gouv.fr would harvest

/catalog-capb.xml

Without the copies of national datasets, which stay published by their original publisher.

The static files and the CKAN API

Every file of this demo stands for a call on the PoC’s CKAN service, which also takes filters, paging and SQL.

The static files and the CKAN API
File in this demoCKANCall on the PoC’s CKAN service
/data/search.jsonpackage_search/api/3/action/package_search?q=…&fq=groups:finances
/data/datasets/<name>.jsonpackage_show/api/3/action/package_show?id=<name>
/data/organizations.jsonorganization_list/api/3/action/organization_list?all_fields=true
/data/groups.jsongroup_list/api/3/action/group_list?all_fields=true
/data/tables/<id>.jsondatastore_search/api/3/action/datastore_search?resource_id=<id>&filters={…}&q=…
—datastore_search_sql/api/3/action/datastore_search_sql?sql=SELECT … FROM "<id>"
/data/tables/<id>.csv/datastore/dump/datastore/dump/<id>?format=csv|json|tsv|xlsx
/catalog.ttl, .xml, .jsonldckanext-dcat/catalog.ttl?q=…&fq=organization:<organisation>

Read with no key and no quota. Writing (publishing, updating) uses one CKAN API token per publisher.