Custom Connector
Rennes Metropole Open Data Portal Connector
France
The Rennes Metropole Open Data Portal Connector provides access to public datasets from the Rennes Metropole Open Data API. It simplifies access to catalog, dataset, and record data, supporting retrieval and export in JSON, CSV, Parquet, GPX, and DCAT — leveraging ODSQL for filtering, sorting, grouping, and pagination for municipal, transport, geospatial, and public-service applications.
Overview
Integration Overview
This document provides a detailed guide for each integration point, its purpose, configuration, and workflow support using the Rennes Metropole Open Data Portal Connector.
- getDatasets. Query catalog datasets.
- listExportFormats. List export formats for the catalog.
- exportDatasets / exportCatalogCSV / exportCatalogDCAT. Export the catalog in a chosen format, CSV, or DCAT.
- getDatasetsFacets. List facet values for datasets.
- getRecords. Query dataset records.
- listDatasetExportFormats. List export formats for a specific dataset.
- exportRecords / CSV / Parquet / GPX. Export a dataset’s records in a chosen format.
- getDataset. Show dataset information.
- getRecordsFacets. List record-level facet values.
- getDatasetAttachments. List dataset attachments.
- getRecord. Read a single dataset record.
Documentation
Detailed Integration Documentation
Get Datasets
| Action | getDatasets |
|---|---|
| Purpose | Retrieves available datasets from the Rennes catalog, optionally filtered and sorted with ODSQL. |
| Configuration | Configure the base URL via CONNECTOR_ENV_RENNESOPENDATA_BASE_URL. |
| Parameters | Optional: select; where (e.g. records_count > 1000); order_by; limit (default 10, max 100); offset; refine; exclude; lang; timezone; group_by; include_links; include_app_metas. |
| Output | Successful: JSON with links and a datasets array (metadata, fields, features). Failure: ODSQLError. |
| Workflow example | Execute getDatasets with where=“records_count > 1000” and limit=20 to list Rennes datasets. |
Catalog Exports (formats / export / CSV / DCAT)
| Action | listExportFormats / exportDatasets / exportCatalogCSV / exportCatalogDCAT |
|---|---|
| Purpose | Lists catalog export formats and exports the catalog in a chosen format, CSV (delimiter options), or RDF/XML (DCAT). |
| Configuration | Configure the base URL via CONNECTOR_ENV_RENNESOPENDATA_BASE_URL. |
| Parameters | exportDatasets required: format (csv/json/rdf). CSV optional: delimiter; list_separator; quote_all; with_bom. DCAT required: dcat_ap_format (e.g. _ap_fr); optional include_exports, use_labels_in_exports. |
| Output | Successful: a JSON list of export links or a file. Failure: ExportError / FormatError. |
| Workflow example | Call listExportFormats, then exportCatalogCSV with delimiter=, for spreadsheet tools. |
Get Datasets Facets
| Action | getDatasetsFacets |
|---|---|
| Purpose | Enumerates facet values for Rennes datasets for guided navigation and filtering. |
| Configuration | Configure the base URL via CONNECTOR_ENV_RENNESOPENDATA_BASE_URL. |
| Parameters | Optional: facet (e.g. publisher); refine; exclude; where; timezone. |
| Output | Successful: JSON with links and facets (name, count, state, value). Failure: error details. |
| Workflow example | Execute getDatasetsFacets with facet=publisher to display interactive filters. |
Records, Dataset Info & Single Record
| Action | getRecords / getDataset / getRecord / getRecordsFacets |
|---|---|
| Purpose | Queries dataset records; retrieves dataset metadata and features; reads a single record by ID; and enumerates record-level facets. |
| Configuration | Configure the base URL via CONNECTOR_ENV_RENNESOPENDATA_BASE_URL. |
| Parameters | Required: dataset_id (getRecord also needs record_id; getRecordsFacets takes facet). Optional: select, where, group_by, order_by, limit, offset, refine, exclude, lang, timezone, include_links, include_app_metas. |
| Output | Successful: JSON with total_count + results, dataset metadata, a single record, or facet values. Failure: error details. |
| Workflow example | Execute getRecords with dataset_id and where=“population > 100000”, then getRecord for detail. |
Dataset Exports (formats / CSV / Parquet / GPX) & Attachments
| Action | listDatasetExportFormats / exportRecords / exportRecordsCSV / exportRecordsParquet / exportRecordsGPX / getDatasetAttachments |
|---|---|
| Purpose | Lists a dataset’s export formats, exports its records in a chosen format / CSV / Parquet (snappy/zstd) / GPX, and lists its attachments. |
| Configuration | Configure the base URL via CONNECTOR_ENV_RENNESOPENDATA_BASE_URL. |
| Parameters | Required: dataset_id (and format for exportRecords). Optional: select, where, order_by, group_by, limit, refine, exclude, lang, timezone, use_labels, compressed, epsg; CSV delimiter options; parquet_compression; GPX name_field/description_field_list/use_extension. |
| Output | Successful: a file in the requested format, or a list of attachments. Failure: error details. |
| Workflow example | Execute exportRecords with dataset_id and format=csv, then getDatasetAttachments to download supporting files. |
Example Workflow: Smart City Data Integration
| Retrieve datasets | Use getDatasets for transport, environment, or public-service datasets. |
|---|---|
| Query dataset | Execute getDataset for field structure and metadata. |
| Fetch records | Use getRecords with where=“population > 100000” for targeted results. |
| Export & visualize | Export via exportRecordsCSV or exportRecordsParquet, then process in BI or mapping tools. |
Support
For technical support, contact custom-connectors-support@isolutions.sa.