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
Search your data with AI (vector search)
The Explore data with AI feature
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 map block in Studio
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
Embedding a Studio page in a CMS
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
What is updated when publishing a remote file?
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 connectors
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
Connecteur Waze
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
Best practices for search engine optimization (SEO)
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 images and fonts
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
- Configuring your portal
- Customizing your workspace's URL
Customizing your workspace's URL
Updated by Patrick Smith
A new Opendatasoft workspace will have a URL in the form: <workspacename>.opendatasoft.com
.
As the workspace's URL is a very important tool for discoverability, branding, and ease of access, there will often be a need to customize this URL. As such, the Opendatasoft platform allows for adding additional names to a workspace. These customization options are currently not exposed in the back office. They must be requested by using the support form in the back office.
In the following, the workspace "name" will represent the first base name of an Opendatasoft workspace, and we will call any additional names "aliases." All of these names are the host part of the URLs used to access the workspace.
Customer-provided DNS aliases
It is also possible to change the base URL of an Opendatasoft workspace to a custom name whose authoritative DNS server you control. For instance, a company called "Example" has an Opendatasoft workspace named example
. Its main URL is example.opendatasoft.com
, but the company might want to set up their workspace in order to use the alias data.example.com
.
This can be done in two steps:
- Create a DNS record of the
CNAME
type for the desired alias with the default name of your Opendatasoft workspace as a value.
data.example.com
would actually mean data.example.com.example.com.
, which is generally not wanted.The DNS record for the above example would look like this:
data.example.com. IN CNAME example.opendatasoft.com.
If one's DNS provider uses relative names, it can look like this: data IN CNAME example.opendatasoft.com.
- The new alias must be registered as an alias of the main workspace on the Opendatasoft platform. To do so, please contact the Opendatasoft support by using the support form in the back office.
Any number of distinct DNS names can be added to an Opendatasoft workspace. Though all names and aliases can be used to access the workspace simultaneously, the first alias will be used by default for URLs generated to access the site from the outside (in a notification email, for example).
User login sessions are also specific to a given workspace name, so it is possible for a user to be authenticated when accessing a workspace via one alias and unauthenticated (anonymous) on another alias, or the main name.
A
or AAAA
types records are not supported by the Opendatasoft platform as the IP address of your workspace is susceptible to change.HTTPS and TLS (SSL) certificates
HTTPS is a widely used protocol that aims at ensuring the privacy and integrity of the exchanges between a website and its users by providing HTTP over a secure communication layer. For these safety and integrity reasons, the Opendatasoft platform enforces the use of HTTPS throughout its services. As such, requests made to Opendatasoft workspaces and all their aliases are HTTPS-enabled. TLS is the actual protocol used to secure HTTPS today, which replaced the original, deprecated SSL protocol.
However, if one chose to use a custom workspace name (for instance, from our example above, data.example.com
), the TLS certificate will be generated by Opendatasoft on one's behalf using Let's Encrypt's services. Certificate generation and renewal are handled by Opendatasoft transparently. The renewal process is completely automated, as long as the DNS entry is set up and stays valid. Let's Encrypt certificates provide the same security level as any other Domain-Validated TLS certificates, and their short lifecycle (3 months) ensures a constantly updated security level. Let's Encrypt certificates are free of charge for Opendatasoft customers.
letsencrypt.org
.Language handling
Suppose you have multiple languages on the Opendatasoft workspace and you use language-specific aliases. In that case, you can request each alias to be linked to a specific language. For instance, if there are two aliases, data.example.co.uk and daten.example.de, it can be requested that users accessing the workspace through the first alias be served English content; and those accessing it through the second alias be served German content by default. Users can then switch languages as usual.