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
- Managing your portal
- Look & Feel
- Configuring data visualizations
Configuring data visualizations
Updated by Patrick Smith
Although the visualizations of the created datasets are configured both in terms of content and appearance from the edition interface of the datasets themselves, some other global data visualizations configurations such as custom default chart colors, available basemaps, and default map locations, are managed from the Look & feel > Data visualizations subsection of the back office.
Configuring chart default colors
Charts are composed of at least one color, but depending on what they represent, they can be composed of many more. By default, a set of eight colors is used, and Opendatasoft users also have the possibility to use other sets of colors that are available by default as well. The Chart colors configuration allows to define a new set of colors that will replace the original eight-color set.
To add a new default chart color:
- In the Data visualizations configuration interface, look for the Chart color configuration.
- Click on the + Add color button.
- Add the hexadecimal code of the new color, or click the color button to choose a new color using either the "Nice colors" or the color wheel.
- (optional) Click Reorder to reorganize the new color among the others. The order of the colors matters because they will be used one after the other by the chart.
- Click Save in the top right corner of the page.
To delete a color, click the trash button.
Adding basemaps
Basemaps are the canvas on which geographic data are represented. They are used for any map displayed on Opendatasoft, whether it is the visualization map of a dataset or the Map Builder.
A basic basemap is used by default for all maps of all Opendatasoft workspaces. It is possible to change that default basemap, as well as to make other basemaps available in an Opendatasoft portal. It will allow users to change the basemap at any time on a map and even to change the default basemap of a specific dataset.
To manage basemaps, look for the Basemaps configuration in the Data visualizations configuration interface.
Basemaps should be managed from the table of the Basemaps configuration. This table displays the currently available basemaps that can be used on the workspace. It comprises three columns:
- Label, to name the basemaps. Each basemap should have one label per language available on the workspace.
- Basemap, to choose the basemap
- Preview, to see what the basemaps look like
The basemaps table also contains two options:
- The Reorder button to change the order of the basemaps. The first one is the default one on the whole workspace.
- The Trash button to delete a basemap.
Adding default basemaps
By default, Opendatasoft provides several basemaps. They are the default basemaps displayed in the drop-down menu of the Basemap table column. All these default basemaps can be made available on the platform using the table. Even though the basemaps appear in the list of default basemaps, they will only be usable once added to the table.
To add default basemaps to the table and make them available on the workspace:
- Click on the + Add basemap button under the table.
- In the Basemap column, click on the drop-down menu. By default, it should display "Streets" (default basemap for all Opendatasoft workspaces).
- The drop-down menu indicates all basemaps available in the workspace, ordered by basemap providers. Click on the basemap to add it to the workspace.
- In the Label column, indicate a label for the newly added basemap. There must be one label per language (if the workspace supports more than one), otherwise the configurations cannot be saved.
- Click on Save in the top right corner of the page.
Adding custom basemaps
Among the default basemaps, displayed in the drop-down menu of the Basemap table column, are two options that allow the addition of custom basemaps:
- "Custom", to add TMS and other OpenStreetMap compatible basemaps
- "Custom (WMS)", to add WMS basemaps
To add a custom basemap to the workspace:
- Click on the + Add basemap button.
- In the Basemap column of the newly added row of the table, click on the drop-down menu.
- In the drop-down menu, select either "Custom" or "Custom (WMS)". (If adding an IGN basemap, see here for more information.)
- Fill up the basemap configurations.
- If adding a "Custom" basemap, please refer to the table below:
Name
Description
Example
Tiles URL (required)
URL of the basemap.
http://tile.basemapprovider.io/{z}/{x}/{y}.png
Subdomains
Subdomains of the basemap (provided by the basemap provider). Subdomains must be separated with a comma.
a,b,c,d
Zoom min
Minimum zoom available (the most global view we can have of the map).
1
Zoom max
Maximum zoom available (the closer we can be into the map).
21
Attribution
Source of the basemap data. Will be displayed at the bottom of the basemap everywhere it is used.
Basemap data from OpenStreetMap
TMS service
Should only be checked in case the basemap is a strict TMS basemap, with inverted coordinates.
- If adding a "Custom (WMS)" basemap, please refer to the table below:
Name
Description
Example
WMS URL (required)
URL of the basemap.
https://www.basemapprovider.com/wms
Attribution
Source of the basemap data. Will be displayed at the bottom of the basemap everywhere it is used.
Basemap data from OpenStreetMap
Layers (required)
Layer(s) of the basemap (provided by the basemap provider).
LayerName
Tiles images format
Format of the tiles: either .png or .jpeg (provided by the basemap provider).
Styles
Styles of the basemap (provided by the basemap provider).
DefaultStyle
Zoom min
Minimum zoom available (the most global view we can have of the map).
1
Zoom max
Maximum zoom available (the closer we can be into the map).
21
- In the Label column, indicate a label for the newly added basemap. There must be one label per language (if the workspace supports more than one).
- Click on the Save button in the top right corner of the page.
Adding external basemaps
Opendatasoft currently only allows the integration of Mapbox basemaps.
To fully use the default Thunderforest basemaps instead of within the default, limited quotas:
1. Go to the Thunderforest website and sign in to your account.
2. Copy the API Key.
3. Go back to the Look & feel > Data Visualizations subsection of your Opendatasoft back office.
4. In the Basemaps configuration, click on "Thunderforest integration" to expand the related configurations.
5. Paste the API Key in the textbox.
Mapbox integration
Mapbox is a mapping platform that allows to build and design custom maps. They also provide different basic map styles that can be directly used. Opendatasoft allows to integrate these Mapbox basemaps into an Opendatasoft workspace to make them available throughout the portal.
To integrate Mapbox basemaps:
- Go to the Mapbox website and log in.
- In the Mapbox account page, either copy the Default Public Token or create a new Public Token and copy it. This will be used by Opendatasoft to display maps on behalf of the user's own Mapbox account.
- Go back to the Look & feel > Data Visualizations subsection of your Opendatasoft back office.
- In the Basemaps configuration, click on "Mapbox integration" to expand the related configurations.
- Paste the Public Token in the textbox. A message will confirm whether the access token is valid or not.
Using the basemaps table, it is now possible to select one of Mapbox's default styles or add one of your own custom Mapbox basemaps:
- In case of a "Tileset", enter the "Tileset ID" (which is usually under the form )
- In case of a map style created using Mapbox Studio, enter the map identifier (usually under the form ), which is the last part of the "Style URL" provided by Mapbox (for example, means the map identifier is ).
Defining a default Map Builder location
The Map Builder is Opendatasoft's tool to create advanced maps using one or more published dataset from one or more Opendatasoft portal. The Default map builder location configuration allows to define which location the Map Builder will focus on by default when landing on it.
- In the Data visualizations configuration interface, look for the Default map builder location configuration.
- Click on the map, and maintain the click while moving the map until the chosen location is enclosed in the rectangle. Some options are available to help to define the right location:
- + and - to zoom in or out
- [] moves the map to your current location
- The Magnifier icon allows you to make a textual search of a location
- Click Save in the top right corner of the page.