Frictionless Data Compatibility
Last updated
Last updated
The Open Data Blend Dataset API is compatible with version 1 of the following Frictionless Data specifications:
It also incorporates the following Frictionless Data patterns:
This means there is a growing ecosystem of data tools that you can use to work with Open Data Blend Datasets.
The Frictionless Libraries simplify integrations with the Open Data Blend Dataset API from many languages, including Python and R. More specifically, you can use the Data Package libraries to programmatically access our datasets and integrate them into your solutions.
An up-to-date list of the supported libraries can be found here, along with documentation on how to use them. Each library varies slightly in its implementation, but the general concepts for working with a Data Package are the same.
The following examples demonstrate how you could use the Python library to interact with the Open Data Blend Dataset API. This is the most mature Frictionless library to date, and one that we recommend. The libraries for the other languages implement a similar method to load data packages and these are explained in each library's documentation.
Install the frictionless
module.
Ensure that frictionless 4.0
or later is installed. Prior versions are not stable releases.
Import the Package
submodule from the frictionless
module.
Loading the Open Data Blend Catalogue metadata.
Loading the catalogue metadata for an Open Data Blend Dataset.
The resources
property is an array of resources. In this context, 'resources' means 'datasets'. In the above example, we are referencing a dataset by its zero-based index position.
Note: The metadata for a dataset in the catalogue is a subset of its full metadata.
Getting the name of the dataset.
Getting the friendly name of the dataset.
Getting the description of the dataset.
Getting the endpoint of the dataset.
Loading Open Data Blend Dataset metadata.
Loading the metadata of a data file.
The resources
property is an array of resources. In this context, 'resources' means 'data files'. In the above example, we are referencing a data file by its zero-based index position.
Getting the name of the data file.
Getting the friendly name of the data file.
Getting the description of the data file.
Getting the table schema of the data file.
Getting the download location of the data file.