ARCEP Mobile Signal MeasurementsMesures ARCEP

Name: ARCEP Mobile Signal Measurements
Creator: opendatasoft

Mesures ARCEPARCEP Mobile Signal Measurements

APIJoinable5/7Query nowOpen workbench Subscribe🇫🇷France

This dataset provides mobile network signal quality measurements collected according to the ARCEP (French telecoms regulator) protocol, covering the Grand Paris Sud territory. It includes results from measurement campaigns carried out under various conditions, such as from a car, a train, or on foot, allowing assessment of mobile coverage and signal quality across different modes of travel within the area. The data is published via the Grand Paris Sud open data portal and can be used to analyze local mobile network performance and identify coverage gaps or variations across the territory.Mesures mobile de l' ARCEP Données sur les mesures de qualité du signal mobile selon le protocole de l' ARCEP . Ce jeu de données présente les résultats des mesures de qualité du signal mobile sur le territoire de Grand Paris Sud. Ces mesures ont été prise soit à bord d'une voiture, d'un train, e...

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

Trust score

How is this computed?

fair

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

Data schema (14 fields)

Filterable via the API (13)

date_heureoperateursignaltechnologiecommunersrplatitudelongitudelieusituationprotocolecode_inseecode_iris

Click a field to see example values.

Fill	Field	Type	Description
—	date_heureDate heure	datetime	Date et heure de la prise de la mesure.
—	operateur	text	Opérateur du portable avec lequel la mesure a été prise.
—	signal	text	Puissance du signal mobile à partir du dBm reçu.
—	technologie	text	Génération de réseau mobile qui est rattachée à la technologie utilisée, entre 3G, 4G et 5G.
—	communeCommune	text	Commune où la mesure a été prise.
—	rsrp	double	Contient la puissance du signal reçu, en dBm.
—	geop	geo_point_2d	Point géo de la mesure.
—	latitudeLatitude	double	Contient la latitude de la mesure, prise en degré.
—	longitudeLongitude	double	Contient la longitude de la mesure, prise en degré.
—	lieu	text	Type de lieu lors de la prise de la mesure.
100%	situation	text	Situation lors de la prise de la mesure
100%	protocole	text	Protocole utilisé pour la prise de la mesure.
100%	code_inseeINSEE commune code	text	Code Insee de la ville où la mesure a été faite.
100%	code_irisCode iris	text	—

Schema captured from opendatasoft 10 minutes 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 1geop: {"lat":48.60983,"lon":2.58348} · lieu: habitations

{
  "geop": {
    "lat": 48.60983,
    "lon": 2.58348
  },
  "lieu": "habitations",
  "rsrp": -97.53,
  "signal": "Moyen",
  "commune": "Moissy-Cramayel",
  "latitude": 48.60983,
  "code_iris": "772960105",
  "longitude": 2.58348,
  "operateur": "ORANGE",
  "protocole": "WEB",
  "situation": "indoor",
  "code_insee": "77296",
  "date_heure": "2022-06-13T11:03:24+00:00",
  "technologie": "2G/3G/4G/5G"
}

Record 2geop: {"lat":48.60983,"lon":2.58348} · lieu: habitations

{
  "geop": {
    "lat": 48.60983,
    "lon": 2.58348
  },
  "lieu": "habitations",
  "rsrp": -98.37,
  "signal": "Moyen",
  "commune": "Moissy-Cramayel",
  "latitude": 48.60983,
  "code_iris": "772960105",
  "longitude": 2.58348,
  "operateur": "BOUYGUES TELECOM",
  "protocole": "WEB",
  "situation": "indoor",
  "code_insee": "77296",
  "date_heure": "2022-06-13T11:03:59+00:00",
  "technologie": "2G/3G/4G/5G"
}

Record 3geop: {"lat":48.60983,"lon":2.58348} · lieu: habitations

{
  "geop": {
    "lat": 48.60983,
    "lon": 2.58348
  },
  "lieu": "habitations",
  "rsrp": -98.27,
  "signal": "Moyen",
  "commune": "Moissy-Cramayel",
  "latitude": 48.60983,
  "code_iris": "772960105",
  "longitude": 2.58348,
  "operateur": "BOUYGUES TELECOM",
  "protocole": "DOWNLOAD",
  "situation": "indoor",
  "code_insee": "77296",
  "date_heure": "2022-06-13T11:07:54+00:00",
  "technologie": "2G/3G/4G/5G"
}

Record 4geop: {"lat":48.61639,"lon":2.58146} · lieu: habitations

{
  "geop": {
    "lat": 48.61639,
    "lon": 2.58146
  },
  "lieu": "habitations",
  "rsrp": -99.57,
  "signal": "Moyen",
  "commune": "Moissy-Cramayel",
  "latitude": 48.61639,
  "code_iris": "772960105",
  "longitude": 2.58146,
  "operateur": "BOUYGUES TELECOM",
  "protocole": "WEB",
  "situation": "outdoor",
  "code_insee": "77296",
  "date_heure": "2022-06-13T11:29:51+00:00",
  "technologie": "2G/3G/4G/5G"
}

Record 5geop: {"lat":48.64404,"lon":2.53564} · lieu: habitations

{
  "geop": {
    "lat": 48.64404,
    "lon": 2.53564
  },
  "lieu": "habitations",
  "rsrp": -94.42,
  "signal": "Bon",
  "commune": "Tigery",
  "latitude": 48.64404,
  "code_iris": "916170000",
  "longitude": 2.53564,
  "operateur": "FREE MOBILE",
  "protocole": "WEB",
  "situation": "incar",
  "code_insee": "91617",
  "date_heure": "2022-06-20T11:08:45+00:00",
  "technologie": "2G/3G/4G/5G"
}

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

Verification Status

Using the API

Configuration

Base URL: https://data.grandparissud.fr/api/explore/v2.1/catalog/datasets/mesures-arcep

Query examples

curl -s 'https://data.grandparissud.fr/api/explore/v2.1/catalog/datasets/mesures-arcep/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

5 000 req/day

per ipmeasured

observed 10 minutes ago

Dataset

Volume & freshness

Records

17k

17434

Last upstream update

3 years ago

2023-07-27

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.