Getting started
Exploring and using data
Exploring catalogs and datasets
Exploring a catalog of datasets
What's in a dataset
Filtering data within a dataset
An introduction to the Explore API
An introduction to the Automation API
Introduction to the WFS API
Downloading a dataset
Creating maps and charts
Creating advanced charts with the Charts tool
Overview of the Maps interface
Configure your map
Manage your maps
Reorder and group layers in a map
Creating multi-layer maps
Share your map
Navigating maps made with the Maps interface
Rename and save a map
Creating pages with the Code editor
How to limit who can see your visualizations
Archiving a page
Managing a page's security
Creating a page with the Code editor
Content pages: ideas, tips & resources
How to insert internal links on a page or create a table of contents
Sharing and embedding a content page
How to troubleshoot maps that are not loading correctly
Creating content with Studio
Creating content with Studio
Adding a page
Publishing a page
Editing the page layout
Configuring blocks
Previewing a page
Adding text
Adding a chart
Adding an image block to a Studio page
Adding a choropleth map block in Studio
Adding a points of interest map block in Studio
Adding a key performance indicator (KPI)
Configuring page information
Using filters to enhance your pages
Refining data
Managing page access
How to edit the url of a Studio page
Adding a map block in Studio
Visualizations
Managing saved visualizations
Configuring the calendar visualization
The basics of dataset visualizations
Configuring the images visualization
Configuring the custom view
Configuring the table visualization
Configuring the map visualization
Understanding automatic clustering in maps
Configuring the analyze visualization
Publishing data
Publishing datasets
Creating a dataset
Creating a dataset from a local file
Creating a dataset with multiple files
Creating a dataset from a remote source (URL, API, FTP)
Creating a dataset using dedicated connectors
Creating a dataset with media files
Federating an Opendatasoft dataset
Publishing a dataset
Publishing data from a CSV file
Publishing data in JSON format
Supported file formats
Promote mobility data thanks to GTFS and other formats
Configuring datasets
Automated removal of records
Configuring dataset export
Checking dataset history
Configuring the tooltip
Dataset actions and statuses
Dataset limits
Defining a dataset schema
How Opendatasoft manages dates
How and where Opendatasoft handles timezones
How to find your workspace's IP address
Keeping data up to date
Processing data
Translating a dataset
How to configure an HTTP connection to the France Travail API
Deciding what license is best for your dataset
Types of source files
OpenStreetMap files
Shapefiles
JSON files
XML files
Spreadsheet files
RDF files
CSV files
MapInfo files
GeoJSON files
KML/KMZ files
GeoPackage
Connectors
Saving and sharing connections
Airtable connector
Amazon S3 connector
ArcGIS connector
Azure Blob storage connector
Database connector
Dataset of datasets (workspace) connector
Eco Counter connector
Feed connector
Google BigQuery connector
Google Drive connector
How to find the Open Agenda API Key and the Open Agenda URL
JCDecaux connector
Netatmo connector
OpenAgenda connector
Realtime connector
Salesforce connector
SharePoint connector
U.S. Census connector
WFS connector
Databricks connector
Harvesters
Harvesting a catalog
ArcGIS harvester
ArcGIS Hub Portals harvester
CKAN harvester
CSW harvester
FTP with meta CSV harvester
Opendatasoft Federation harvester
Quandl harvester
Socrata harvester
data.gouv.fr harvester
data.json harvester
Processors
What is a processor and how to use one
Add a field processor
Compute geo distance processor
Concatenate text processor
Convert degrees processor
Copy a field processor
Correct geo shape processor
Create geo point processor
Decode HTML entities processor
Decode a Google polyline processor
Deduplicate multivalued fields processor
Delete record processor
Expand JSON array processor
Expand multivalued field processor
Expression processor
Extract HTML processor
Extract URLs processor
Extract bit range processor
Extract from JSON processor
Extract text processor
File processor
GeoHash to GeoJSON processor
GeoJoin processor
Geocode with ArcGIS processor
Geocode with BAN processor (France)
Geocode with PDOK processor
Geocode with the Census Bureau processor (United States)
Geomasking processor
Get coordinates from a three-word address processor
IP address to geo Coordinates processor
JSON array to multivalued processor
Join datasets processor
Meta expression processor
Nominatim geocoder processor
Normalize Projection Reference processor
Normalize URL processor
Normalize Unicode values processor
Normalize date processor
Polygon filtering processor
Replace text processor
Replace via regular expression processor
Retrieve Administrative Divisions processor
Set timezone processor
Simplify Geo Shape processor
Skip records processor
Split text processor
Transform boolean columns to multivalued field processor
Transpose columns to rows processor
WKT and WKB to GeoJson processor
what3words processor
Data Collection Form
About the Data Collection Form feature
Data Collection Forms associated with your Opendatasoft workspace
Create and manage your data collection forms
Sharing and moderating your data collection forms
Dataset metadata
Analyzing how your data is used
Getting involved: Sharing, Reusing and Reacting
Discovering & submitting data reuses
Sharing through social networks
Commenting via Disqus
Submitting feedback
Following dataset updates
Sharing and embedding data visualizations
Monitoring usage
An overview of monitoring your workspaces
Analyzing user activity
Analyzing actions
Detail about specific fields in the ods-api-monitoring dataset
How to count a dataset's downloads over a specific period
Analyzing data usage
Analyzing a single dataset with its monitoring dashboard
Analyzing back office activity
Using the data lineage feature
Managing your users
Managing limits
Managing users
Managing users
Setting quotas for individual users
Managing access requests
Inviting users to the portal
Managing workspaces
Managing your portal
Configuring your portal
Configure catalog and dataset pages
Configuring a shared catalog
Sharing, reusing, communicating
Customizing your workspace's URL
Managing legal information
Connect Google Analytics (GA4)
Regional settings
Pictograms reference
Managing tracking
Look & Feel
Branding your portal
Customizing portal themes
How to customize my portal according to the current language
Managing the dataset themes
Configuring data visualizations
Configuring the navigation
Adding IGN basemaps
Adding assets
Plans and quotas
Managing security
Configuring your portal's overall security policies
A dataset's Security tab
Mapping your directory to groups in Opendatasoft (with SSO)
Single sign-on with OpenID Connect
Single sign-on with SAML
Parameters
- Home
- Publishing data
- Dataset metadata
- Referencing your datasets with your national open data portal (DCAT-AP)
Referencing your datasets with your national open data portal (DCAT-AP)
Updated by Carole Bodilis
– Belgium (Flanders)
– Germany
– Italy
– Spain
– Sweden
– Switzerland
For European countries outside of this list and countries outside Europe, we advise you to contact your national portal to see if one of these catalog exports may be suitable. If not, contact Opendatasoft support.
For France, please refer to this article dedicated to uploading your data to data.gouv.fr.
When you publish open datasets on your portal, you can upload them to your national portal in three steps:
- Fill in the DCAT and/or DCAT-AP interoperability metadata, plus the DCAT-AP for your country
- Ask our Support to activate a specific export in RDF format that complies with your country's DCAT-AP specification
- Use the export URL to upload your data to the national portal
Interoperability metadata and RDF exports to DCAT-AP standards are not available by default on the Opendatasoft platform, but can be activated on request by sending an email to Support or by contacting your CSM directly. The steps to be taken depend on the requirements of your national portal, and this article explains how to proceed depending on your country.
Concretely, you can expose the metadata associated with each of your datasets on your national portal, as well as the download links (called "distributions" in the DCAT standard). Then, once your data is on your national portal, it can also be uploaded to the European portal.
Here, for example, is a dataset published by the city of Bologna which is present at once:
- On their Opendatasoft portal: https://opendata.comune.bologna.it/explore/dataset/eventi-bologna-agenda-cultura/information/
- On the Italian national portal: https://www.dati.gov.it/view-dataset/dataset?id=f3c3a340-fffe-4516-b5ee-a2004b76b275
- On the European portal: https://data.europa.eu/data/datasets/eventi-cultura-bologna
This increases the discoverability of your data, while allowing you to manage your data on your Opendatasoft platform.
Step 1: Fill in the interoperability metadata
When you publish a dataset, you need to fill in the metadata that will be uploaded to your national portal.
Below you'll find the additional metadata templates to be filled in, depending on your country. If your country is not listed, either the standard DCAT/DCAT-AP metadata suffices, or else Opendatasoft does not currently support your standard.
Country | Metadata template |
Belgium (Flanders) | |
Germany | |
Italy | |
Switzerland |
Step 2: Request activation of your country's RDF export format
Once you have completed the interoperability metadata, you need to ask Support to activate your country's DCAT-AP RDF export format. The export activation request should include the information about your catalog that is listed in the "Required information" column.
Below is the information you need to provide when sending your message to Support. If your country is not listed, go directly to step 3.
Country | DCAT-AP standard to activate | Required infomation (and the required language) | Corresponding DCAT-AP property |
Belgium (Flanders) |
|
| |
Germany |
|
| |
Italy |
|
| |
Spain | DCAT-AP-SP |
|
|
Sweden |
|
| |
Switzerland |
|
|
Step 3: Retrieve the catalog export URL in the RDF format
Here are the URLs to use to have your portal harvested by your national portal:
Country | RDF link (what follows the root URL) | URL of your national portal |
Belgium (Flanders) | /api/v2.1/catalog/exports/dcat_ap_vl | |
Belgium (Wallonia) | /api/v2.1/catalog/exports/dcat | |
France | /api/v2.1/catalog/exports/dcat | |
Germany | /api/v2.1/catalog/exports/dcat_ap_de | |
Italy | /api/v2.1/catalog/exports/dcat_ap_it | |
Spain | /api/v2.1/catalog/exports/dcat_ap_sp | |
Sweden | /api/v2.1/catalog/exports/dcat_ap_se | |
Switzerland | /api/v2.1/catalog/exports/dcat_ap_ch | |
Other countries | /api/v2.1/catalog/exports/dcat |