Creating a dataset using dedicated connectors
You can create datasets based on data from remote services for which we have created dedicated connectors.
For a list of available connectors, see the table of connectors to remote services below. Some connectors are only available on-demand and may be subject to pricing.
In Catalog > Datasets, click on the New dataset button.
In the wizard that opens, select the desired service under the Configure a remote service section.
Configure the connection to your source.
For some remote services, you can select a saved connection or configure a new connection.
If you configure a new connection, select the Save connection information check box to save your connection.
From the preview of the first 20 records that appears, configure the source.
Configure the dataset information or use the prefilled values:
In the Dataset name field, enter the title for this dataset.
In the Dataset technical identifier field, enter a meaningful identifier for this dataset.
If you want anyone with access to your domain to be able to explore the dataset, toggle off Access restricted to allowed users and groups.
After creating a dataset, an editing interface opens. Only users granted with the right permissions, either "Create dataset" or "Edit dataset," can use this interface.
Using this interface you can process the data, configure the datasets and their visualizations, and manage the publishing of the dataset. For more information, see Processing data, Configuring metadata, Configuring visualizations, and Publishing a dataset.
Connectors to remote services
Opendatasoft can connect to a variety of remote services.
Contact your local support team to get on-demand connectors activated on your domain. Some of them are subject to pricing.
Connector | Description | Availability | Can retrieve data from a folder | Incremental updates possible | Can be saved and shared |
Retrieves data from an Airtable base | On demand | N/A | ✅ | ✅ | |
Retrieves data from a file stored in an Amazon S3 bucket | On demand | Files only | ❌ | ✅ | |
Retrieves data from an ArcGIS server | Default | N/A | ❌ | ❌ | |
Retrieves data from a file stored in a Blob storage | On demand | N/A | ❌ | ✅ | |
Retrieves data using the US Census Bureau's API | On demand | N/A | ❌ | ❌ | |
Creates a dataset from the catalog of an Opendatasoft domain | Default | N/A | ❌ | ❌ | |
Retrieves data from a Denodo table | On demand | N/A | ❌ | ❌ | |
Retrieves data about Eco Counter counters and counting sites | On demand | N/A | ✅ | ❌ | |
Retrieves data from Atom and RSS feeds | Default | N/A | ✅ | ❌ | |
Retrieves data from a Google BigQuery table | On demand | N/A | ✅ | ❌ | |
Retrieves files located in Google Drive | On demand | Files only | ❌ | ✅ | |
Retrieves the state of JCDecaux bike stations | On demand | N/A | ✅ | ❌ | |
Retrieves data using the Netatmo API | On demand | N/A | ✅ | ❌ | |
Retrieves events from OpenAgenda agendas | On demand | N/A | ✅ | ❌ | |
Pushes real-time data to the platform | On demand | N/A | ✅ | ❌ | |
Retrieves data using the Salesforce API | On demand | N/A | ✅ | ❌ | |
Retrieves files located in SharePoint | On demand | Files only | ❌ | ✅ | |
Retrieves data from a Snowflake table | On demand | N/A | ❌ | ❌ | |
Retrieves data from a Waze flow | On demand | N/A | ❌ | ✅ | |
Retrieves data from a WFS service | On demand | N/A | ❌ | ❌ |