Register record·API·FRVERIFIED · checked 2d ago
O
Observatory of 2G, 3G, 4G, 5G NetworksObservatoire 2G, 3G, 4G, 5G
Observatoire 2G, 3G, 4G, 5GObservatory of 2G, 3G, 4G, 5G Networks
This dataset, published on the Pays de la Loire regional open-data portal, stems from an October 2012 government initiative by ministers Arnaud Montebourg and Fleur Pellerin to increase transparency around mobile operators' network deployments. It supports an observatory tracking investments and rollout of mobile infrastructure (2G, 3G, 4G, and 5G) across the region. The data allows monitoring of network coverage and deployment progress by operators, providing a basis for assessing digital infrastructure development at the regional level in France.Par communiqué du 9 octobre 2012, les Ministres Arnaud Montebourg et Fleur Pellerin ont souhaité rendre le processus de déploiement des opérateurs plus transparent par la mise en place d'un observatoire des investissements et des déploiements dans les réseaux mobiles. Les Ministres ont demandé qu...
Trust score
How is this computed?42
fair
Weighted across five axes. Tap a ring for what it measures.
Data schema (27 fields)
Filterable via the API (26)
communeepcidepartementregionsup_ididgenerationemr_lb_systemesta_nm_dptcode_inseedate_majsta_nm_anfrnat_idsup_nm_hauttpo_idadr_lb_lieuadr_lb_add1adr_lb_add2adr_lb_add3adr_nm_cpcom_cd_inseecoordrecordid0adm_lb_lnomstatutemr_dt
Click a field to see example values.
| Fill | Field | Type | Description |
|---|---|---|---|
| 100% | communeCommune | text | Name of the municipality where the mobile antenna is located.Name of the municipality where the mobile antenna is located. |
| 99.8% | epci | text | Name of the inter-municipal cooperation body (EPCI) of the commune.Name of the inter-municipal cooperation body (EPCI) of the commune. |
| 100% | departementDépartement | text | Name of the French department containing the site.Name of the French department containing the site. |
| 100% | regionRégion | text | Name of the French region containing the site.Name of the French region containing the site. |
| 100% | sup_idSup id | text | Identifier of the support structure carrying the antenna.Identifier of the support structure carrying the antenna. |
| 100% | id | text | Unique identifier of the record.Unique identifier of the record. |
| 100% | generation | text | Mobile network generation, e.g. 2G, 3G, 4G or 5G.Mobile network generation, e.g. 2G, 3G, 4G or 5G. |
| 100% | emr_lb_systemeTechnologie | text | Name of the mobile technology/system deployed on the antenna.Name of the mobile technology/system deployed on the antenna. |
| 100% | sta_nm_dptcode_departement | text | Numeric code of the department.Numeric code of the department. |
| 100% | code_inseeINSEE commune code | text | INSEE code identifying the commune.INSEE code identifying the commune. |
| 100% | date_majdate de mise à jour | date | Date the record was last updated.Date the record was last updated. |
| 100% | sta_nm_anfrSta nm anfr | text | ANFR station identifier for the antenna site.ANFR station identifier for the antenna site. |
| 100% | nat_idNat id | text | Code identifying the nature of the support structure.Code identifying the nature of the support structure. |
| 100% | sup_nm_hautSup nm haut | double | Height of the support structure, in meters.Height of the support structure, in meters. |
| 100% | tpo_idTpo id | text | Identifier of the mobile network operator.Identifier of the mobile network operator. |
| 53.9% | adr_lb_lieuAdr lb lieu | text | Place name of the site address.Place name of the site address. |
| 89.6% | adr_lb_add1Adr lb add1 | text | First line of the site's street address.First line of the site's street address. |
| 30.8% | adr_lb_add2Adr lb add2 | text | Second line of the site's street address.Second line of the site's street address. |
| 2.4% | adr_lb_add3Adr lb add3 | text | Third line of the site's street address.Third line of the site's street address. |
| 100% | adr_nm_cpCode postal | text | Postal code of the site.Postal code of the site. |
| — | com_cd_inseeINSEE | text | INSEE code of the commune where the site is located.INSEE code of the commune where the site is located. |
| — | coord | text | Geographic coordinates of the site in degrees-minutes-seconds format.Geographic coordinates of the site in degrees-minutes-seconds format. |
| — | recordid0recordid | text | Internal record identifier.Internal record identifier. |
| — | adm_lb_lnomAdm lb lnom | text | Name of the mobile network operator administering the site.Name of the mobile network operator administering the site. |
| — | statut | text | Operational status of the antenna, e.g. in service.Operational status of the antenna, e.g. in service. |
| — | emr_dtDate de mise en service | date | Date the antenna was put into service.Date the antenna was put into service. |
| — | localisation | geo_point_2d | Geographic coordinates (latitude and longitude) of the site.Geographic coordinates (latitude and longitude) of the site. |
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.
=
Sample data (5 records)
Record 1id: 771911 · epci: Communauté d'agglomération Pornic Agglo
{
"id": "771911",
"epci": "Communauté d'agglomération Pornic Agglo Pays de Retz",
"coord": "47°5'35''N 1°51'4''W",
"emr_dt": "2025-04-18",
"nat_id": "23",
"region": "Pays de la Loire",
"statut": "En service",
"sup_id": "2947265",
"tpo_id": "68",
"commune": "Saint-Hilaire-de-Chaléons",
"date_maj": "2025-04-24",
"adr_nm_cp": "44680",
"recordid0": null,
"code_insee": "44164",
"generation": "3G",
"sta_nm_dpt": "044",
"adm_lb_lnom": "SFR",
"adr_lb_add1": "COMLEC'K VERS MOULIN DU RENAUD",
"adr_lb_add2": null,
"adr_lb_add3": null,
"adr_lb_lieu": "LA CLOUÉE",
"departement": "Loire-Atlantique",
"sta_nm_anfr": "0442700712",
"sup_nm_haut": 34.5,
"com_cd_insee": "44164",
"localisation": {
"lat": 47.09305555555556,
"lon": -1.8511111111111112
},
"emr_lb_systeme": "UMTS 900"
}Record 2id: 653187 · epci: Communauté de communes du Bocage Mayenna
{
"id": "653187",
"epci": "Communauté de communes du Bocage Mayennais",
"coord": "48°26'29''N 1°4'7''W",
"emr_dt": "2016-06-23",
"nat_id": "23",
"region": "Pays de la Loire",
"statut": "En service",
"sup_id": "701617",
"tpo_id": "65",
"commune": "Pontmain",
"date_maj": "2025-04-10",
"adr_nm_cp": "53220",
"recordid0": null,
"code_insee": "53181",
"generation": "3G",
"sta_nm_dpt": "053",
"adm_lb_lnom": "SFR",
"adr_lb_add1": "Rte de Fougères",
"adr_lb_add2": null,
"adr_lb_add3": null,
"adr_lb_lieu": "LA PIROTERIE",
"departement": "Mayenne",
"sta_nm_anfr": "0532700096",
"sup_nm_haut": 34,
"com_cd_insee": "53181",
"localisation": {
"lat": 48.44138888888889,
"lon": -1.0686111111111112
},
"emr_lb_systeme": "UMTS 900"
}Record 3id: 464878 · epci: Communauté de communes du Bocage Mayenna
{
"id": "464878",
"epci": "Communauté de communes du Bocage Mayennais",
"coord": "48°18'55''N 0°46'20''W",
"emr_dt": "2019-10-01",
"nat_id": "23",
"region": "Pays de la Loire",
"statut": "En service",
"sup_id": "756485",
"tpo_id": "74",
"commune": "Châtillon-sur-Colmont",
"date_maj": "2025-04-10",
"adr_nm_cp": "53100",
"recordid0": null,
"code_insee": "53064",
"generation": "4G",
"sta_nm_dpt": "053",
"adm_lb_lnom": "ORANGE",
"adr_lb_add1": "Près N12 - Chem du Pissot",
"adr_lb_add2": "Piste auto cross Forget",
"adr_lb_add3": null,
"adr_lb_lieu": "Forêt de Mayenne",
"departement": "Mayenne",
"sta_nm_anfr": "0532290114",
"sup_nm_haut": 37,
"com_cd_insee": "53064",
"localisation": {
"lat": 48.31527777777777,
"lon": -0.7722222222222223
},
"emr_lb_systeme": "LTE 800"
}Record 4id: 606771 · epci: Communauté d'agglomération Cholet Agglom
{
"id": "606771",
"epci": "Communauté d'agglomération Cholet Agglomération",
"coord": "47°3'17''N 0°56'7''W",
"emr_dt": "2021-10-19",
"nat_id": "26",
"region": "Pays de la Loire",
"statut": "Techniquement opérationnel",
"sup_id": "462505",
"tpo_id": "32",
"commune": "La Séguinière",
"date_maj": "2025-04-10",
"adr_nm_cp": "49280",
"recordid0": null,
"code_insee": "49332",
"generation": "5G",
"sta_nm_dpt": "049",
"adm_lb_lnom": "SFR",
"adr_lb_add1": "9 r des artisans",
"adr_lb_add2": "Le Petit Champ de l'Etang",
"adr_lb_add3": null,
"adr_lb_lieu": "La Ménardière",
"departement": "Maine-et-Loire",
"sta_nm_anfr": "0492700251",
"sup_nm_haut": 35,
"com_cd_insee": "49332",
"localisation": {
"lat": 47.05472222222222,
"lon": -0.9352777777777778
},
"emr_lb_systeme": "5G NR 2100"
}Record 5id: 376389 · epci: Nantes Métropole
{
"id": "376389",
"epci": "Nantes Métropole",
"coord": "47°11'37''N 1°33'4''W",
"emr_dt": null,
"nat_id": "26",
"region": "Pays de la Loire",
"statut": "Projet approuvé",
"sup_id": "3030277",
"tpo_id": "42",
"commune": "Rezé",
"date_maj": "2025-04-24",
"adr_nm_cp": "44400",
"recordid0": null,
"code_insee": "44143",
"generation": "4G",
"sta_nm_dpt": "044",
"adm_lb_lnom": "FREE MOBILE",
"adr_lb_add1": "Rue de l'ile macé",
"adr_lb_add2": null,
"adr_lb_add3": null,
"adr_lb_lieu": null,
"departement": "Loire-Atlantique",
"sta_nm_anfr": "0440990602",
"sup_nm_haut": 31.2,
"com_cd_insee": "44143",
"localisation": {
"lat": 47.19361111111111,
"lon": -1.551111111111111
},
"emr_lb_systeme": "LTE 700"
}Live sample captured at profiling time — values may have changed upstream.
Verification Status
Using the API
Configuration
- Base URL
- https://data.paysdelaloire.fr/api/explore/v2.1/catalog/datasets/234400034_observatoire2g-3g-4g-2018
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://data.paysdelaloire.fr/api/explore/v2.1/catalog/datasets/234400034_observatoire2g-3g-4g-2018/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.
Rate limits
5 000 req/day
per ipmeasured
observed 3 days ago
Dataset
Volume & freshness
Records
43k
43291
Last upstream update
2 years ago
2025-04-27
License
No license declared upstream.
○ Documentation○ Data dictionary○ Versioning
Source: opendatasoft
Machine-readable & source
Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.