Package Guide
The Data Package is a core Frictionless Data concept meaning a set of resources with additional metadata provided. You can read Data Package Spec for more information.
#
Creating PackageLet's create a data package:
As you can see it's possible to create a package providing different kinds of sources which will be detected to have some type automatically (e.g. whether it's a glob or a path). It's possible to make this step more explicit:
#
Describing PackageThe specs support a great deal of package metadata which is possible to have with Frictionless Framework too:
If you have created a package, for example, from a descriptor you can access this properties:
And edit them:
#
Resource ManagementThe core purpose of having a package is to provide an ability to have a set of resources. The Package class provides useful methods to manage resources:
#
Saving DescriptorAs any of the Metadata classes the Package class can be saved as JSON or YAML:
#
Package OptionsThe Package constructor accept a few additional options to tweak how it and the underlaying resources will work:
#
BasepathWill make all the paths treated as relative to this path.
#
DetectorDetector object to tweak metadata detection.
#
OnerrorThere are 3 possible values for reacting on tabular errors:
- ignore (default)
- warn
- raise
#
TrustedBy default an error will be raised on unsafe paths. Setting trusted
to True
will disable this behaviour.
#
HashingWill be passed to underlaying resources as a default hashing algorithm.
Detector object to tweak metadata detection.
#
Import/ExportIt's possible to import and export package from/to:
- bigquery
- ckan
- sql
- zip
#
BigQueryThis functionality is in the draft state.
#
CkanThis functionality is in the draft state.
#
SqlThis functionality is in the draft state.
#
ZipThis functionality is in the draft state.