Skip to content
A common set of test data files and data packages for testing Frictionless Data tooling
Python Makefile HTML
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
files added bigger example of macos roman encoded file Mar 13, 2018
Makefile Added Oct 26, 2019 [README][m]: add a substantive readme with outline of what kind of ma… Feb 1, 2018 [fix][s] fixed descriptor for different-delimeters dataset. Feb 8, 2018

Test data files and data packages for testing Frictionless Data tooling.

These resources may also be useful to others building data tools beyond the Frictionless Data community.


As a Developer writing a library or tool I want to have a set of standard test data files and data packages as a reference for my implementation tests


Contributions are welcome! Please open a pull request.

Please keep files as small as possible (in general we are testing correctness not performance)

Using these materials in your project

We suggest sub-moduling this repo into your own tool.

git submodule TODO

Some files may change over time, e.g. due to data package spec upgrade, but you can still keep old spec versions by submoduling from a specific branch. Below is an example .gitmodules file:

[submodule "SubmoduleTestRepo"]
    path = SubmoduleTestRepo
    url =
    branch = v1.0


We plan to maintain versioned branches of this repo that track the Frictionless Data specifications so that users of this repo can test against data corresponding to specific versions of the specs.

Data Files

We focus on tabular and geo data as these are the common forms of structured data we handle.

Tabular Data


  • CSV structure variants
    • separators: , ; \t
  • CSV type with all table schema types for inference
  • CSV with table schema


  • xls
  • xlsx
  • google spreadsheet


  • GeoJSON


  • PDF (?)

Table Schema

Data Resource

Data Packages

  • datapackage.json
  • README only
  • Basic CSV
  • Inline data
  • ...

Tabular Data

  • consider supplying Table Schemas within a datapackage.json and separately as tableschema.json as some tools take one or the other as input
  • test data for each type, format and constraint combination
  • common date time
  • missing values
  • primary key
  • foreign key (local or url)
  • rdfType

CSV dialect

  • comma, tab, semicolon separated
  • headers
  • reference in-line or at url

Data package views



You can’t perform that action at this time.