Territorialisation of OCS-GE data year 2022

Open data API in a single place

Provided by François Semecurbe

Get early access to Territorialisation of OCS-GE data year 2022 API!

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

Dataset information

Country of origin
Updated
2026.02.19 13:01
Created
2026.01.09
Available languages
English
Keywords
inspire
Quality scoring

Dataset description

In this repository, you will find a territorialisation of the OCSGE data. As the vintage of the data is not homogeneous across the territory, it is composite. For each spatial unit, information on the year in which the data were compiled is therefore provided. This date is not a priori complete for tiles, which may cover several vintages. The median year of data is 2022. * Carroyage at 1 000 m of the OCSGE data. The tiles are compatible with those of INSEE; you can therefore link demographic data with the physical environment, directly with id\_carreau\_1km * Carroyage at 200 m of the OCSGE data. The tiles are compatible with those of INSEE; you can therefore link demographic data with the physical environment, directly with id\_carreau\_1km * Data at departmental level, according to the geography of 2025. Areas are expressed in ² km. For each territorial unit, you will find information on the soil cover, its use, as well as on the crossing of these two dimensions. <br /> The projection is EPSG:3035
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