Impact indicators from data.gouv.fr

Open data API in a single place

Provided by data.gouv.fr

Get early access to Impact indicators from data.gouv.fr API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2026.04.01 01:05
Created
2023.10.05
Available languages
English
Keywords
Quality scoring

Dataset description

This dataset presents the impact indicators of the data.gouv.fr platform. The mission of data.gouv.fr is to ensure the provision of quality open data to promote transparency and efficiency of public action while facilitating the creation of new services. These indicators aim to monitor the extent to which data.gouv.fr meets its objectives. **Objective 1: data.gouv.fr promotes the discoverability of open data** The aim here is to measure the extent to which users find the data they need. **Indicator: percentage of users who answered positively to the question "Did you find what you were looking for?"** **Objective 2: data.gouv.fr promotes open data quality** This is to measure whether data.gouv.fr makes it easy to publish and reference quality data. **Indicator: Average quality score of the 1000 most viewed datasets on the platform.** **Objective 3: data.gouv.fr promotes the reuse of open data** The aim here is to measure the extent to which data.gouv.fr facilitates interactions between data producers and re-users. **Indicator: average time for a "legitimate" response to discussions on datasets (legitimate: reply by a member of the organisation publishing the dataset or by a member of the data.gouv.fr team.)** **Objective 4: data.gouv.fr facilitates access to information of the most important datasets** This is to measure the extent to which data.gouv.fr participates in access to information. **Indicator: number of datasets in the top 100 associated with "quality" reuse (quality reuse is an editorial choice of the data.gouv.fr.** team) ## Data format This dataset shall comply with the "impact of a digital public service" data scheme aimed at ensuring a smooth publication of the impact statistics of digital public services. Its use makes it possible to compare and centralize data from different products, in order to facilitate their understanding and reuse. [Read more](https://schema.data.gouv.fr/etalab/schema-impact-service-public-numerique/0.3.0/) ### Description of columns - **"administration_rattachement" : a**administration to which the digital public service is attached. - **`public_numeric_service_name`**: name of the digital public service - **"indicator":** Name of indicator. - **"value" : v**value of the indicator, as determined on the date indicated in the field 'date'. - **"unite_measure" : u**nity of the indicator - **“is_target” :** Indicates whether the value is a target value (projected to a future date) or whether it is an actual value (measured to a past date). - **`frequency_monitoring`**: frequency with which the indicator is consulted and used by the service. - **"date"**: date when the indicator was measured, or when the target value is desired if it is a target. - **`est_periode`**: Boolean indicating whether the measurement is made over a period (true) or whether it is a stock (false). - **`date_start`**: date of the start of the measurement period, if the indicator covers a period of time. - **“is_automated“**: specifies whether data collection is automated (true) or manual (false). - **"source_collection"**: specify how the collection is carried out: script, survey, manual collection... - **`insee_code` :** if the indicator is calculated at a certain geographical scale, specify the INSEE code of that scale. - **`dataviz_wish`**: indication for visualization producers of the appropriate type of dataviz for this indicator. - **"comments"**: specify the known limitations and biases and justify the choice of the indicator despite its limitations.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks