Leisure Activities of Île-de-France Residents in Summer 2012Loisirs franciliens pratiqués en été 2012

Loisirs franciliens pratiqués en été 2012Leisure Activities of Île-de-France Residents in Summer 2012

APIDiscovered1/7blocked by verifiedQuery nowOpen workbench Subscribe🇫🇷France

This dataset presents a study by the Comité Régional du Tourisme (Regional Tourism Committee) on leisure activities practiced by residents of the Île-de-France region during the summer of 2012. It forms part of the priorities set out in the 2011-2016 Regional Strategy for Tourism and Leisure Development in Île-de-France, which aims to improve residents' access to leisure and tourism activities within their own region. The data is published via the Île-de-France open data portal and can be used to analyze regional leisure habits and inform tourism policy planning.Étude du Comité Régional du Tourisme sur les loisirs franciliens pratiqués durant l'été 2012. Parmi les axes prioritaires définis dans la « Stratégie régionale de développement du tourisme et des loisirs en Ile-de-France 2011/2016 » figure celui de permettre un meilleur accès des Francilien(ne)s...

⬇ Export CSV List records Select & filter Run verified request Read the docs

Trust score

How is this computed?

poor

Weighted across five axes. Tap a ring for what it measures.

Data schema (3 fields)

Filterable via the API (3)

loisirsdepartementvaleur_en

Click a field to see example values.

Fill	Field	Type	Description
100%	loisirs	text	Type of leisure activity practiced.Type of leisure activity practiced.
100%	departementDépartement	text	Île-de-France department where the activity was practiced.Île-de-France department where the activity was practiced.
100%	valeur_enPratique en %	double	Percentage of respondents practicing the activity.Percentage of respondents practicing the activity.

Schema captured from opendatasoft 3 days ago.

Query the data

Pick columns and a sort, then fetch a live preview straight from the source. Choose an API-filterable column (marked ▾) under “Where” to pick from its list of values.

Where=

Sort by

Sample data (5 records)

Record 1loisirs: ["Fêtes/manifestations locales"] · valeur_en: 14.9

{
  "loisirs": [
    "Fêtes/manifestations locales"
  ],
  "valeur_en": 14.9,
  "departement": [
    "Val-de-Marne (94)"
  ]
}

Record 2loisirs: ["Ping-pong, tennis, badminton..."] · valeur_en: 8.9

{
  "loisirs": [
    "Ping-pong, tennis, badminton..."
  ],
  "valeur_en": 8.9,
  "departement": [
    "Val-d'Oise (95)"
  ]
}

Record 3loisirs: ["Spectacle de danse, théâtre"] · valeur_en: 8.5

{
  "loisirs": [
    "Spectacle de danse, théâtre"
  ],
  "valeur_en": 8.5,
  "departement": [
    "Essonne (91)"
  ]
}

Record 4loisirs: ["Shopping"] · valeur_en: 29.5

{
  "loisirs": [
    "Shopping"
  ],
  "valeur_en": 29.5,
  "departement": [
    "Essonne (91)"
  ]
}

Record 5loisirs: ["Cyclisme, VTT"] · valeur_en: 22

{
  "loisirs": [
    "Cyclisme, VTT"
  ],
  "valeur_en": 22,
  "departement": [
    "Seine-et-Marne (77)"
  ]
}

Live sample captured at profiling time — values may have changed upstream.

Verification Status

Using the API

Configuration

Base URL: https://data.iledefrance.fr/api/explore/v2.1/catalog/datasets/loisirs-franciliens-pratiques-en-ete-2012

License

Licence Ouverte 2.0 (France / Etalab)Open

✓ Redistributable
✓ Attribution required

Query examples

curl -s 'https://data.iledefrance.fr/api/explore/v2.1/catalog/datasets/loisirs-franciliens-pratiques-en-ete-2012/records?limit=20' -H 'Accept: application/json'

First 20 records of the dataset as JSON.

Uses the Opendatasoft Explore v2.1 syntax — supports select, where, group_by and order_by.

Full API documentation ↗

Rate limits

10 000 req/day

per ipmeasured

observed 3 days ago

Dataset

Volume & freshness

Records

368

Update cadence

Annual

declared upstream

Last upstream update

8 years ago

2019-03-16

Temporal coverage

2012 → ongoing

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: opendatasoft

Machine-readable & source

JSON

Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.