Ruido ambiental, Direcciones, transportes, Addresses, Area management/restriction/regulation zones and reporting units, Cartografía, MAPAMA, Ruido de aeropuertos, a restricciones o reglamentaciones y unidades de notificación, IDEE, Environmental noise, 1.3.0, View, Mapas de ruido de aglomeraciones, WMS, OGC, Zonas sujetas a ordenación
The WMS Service (Web Map Service) entitled “Strategic Noise Maps (MER)_Agglomerations_Ferroviario_Ln” allows the visualisation and consultation of the dataset they represent, showing the isophone lines of the Ln index corresponding to the strategic noise maps (MERs) of the agglomerations to be drawn up pursuant to Directive 2002/49/EC on the assessment and management of environmental noise because they have a population of more than 100,000 inhabitants. 3 rd implementation phase of the Directive (2017) The URL of the WMS Service Strategic Noise Maps (MER)_Agglomerations_Ferroviario_Ln is: https://wms.mapama.gob.es/sig/EvaluacionAmbiental/Ruido/MER/Aglomeraciones/Ferroviario/Ln/wms.aspx The reference systems offered by this service are: — For geographical coordinates: CRS: 84, EPSG:4230 (ED50), EPSG:4326 (WGS 84), EPSG:4258 (ETRS 89). — For U.T.M coordinates: EPSG:32628 (WGS 84/UTM zone 28N), EPSG:32629 (WGS 84/UTM zone 29N), EPSG:32630 (WGS 84/UTM zone 30N), EPSG:32631 (WGS 84/UTM zone 31N), EPSG:25828 (ETRS 89/UTM zone 28N), EPSG:25829 (ETRS 89/UTM zone 29N), EPSG:25830 (ETRS 89/UTM zone 30N), EPSG:25831 (ETRS 89/UTM zone 31N), EPSG:23028 (ED50/UTM zone 28N), EPSG:23029 (ED50/UTM zone 29N), EPSG:23030 (ED50/UTM zone 30N), EPSG:23031 (ED50/UTM zone 31N).
Geographical coverage is defined by the delimiting table:
West: —19.00,
this one: 4.57,
South: 27.00,
North: 44.04
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.