Modelled potential carbon storage based on land cover and published carbon storage values in urban landscapes of the South Midlands
Open data API in a single place
Provided by Government Digital Service
Get early access to Modelled potential carbon storage based on land cover and published carbon storage values in urban landscapes of the South Midlands API!
This dataset shows potential carbon storage as modelled for the urban areas of Milton Keynes/Newport Pagnell, Bedford, and Luton/Dunstable, UK. The modelling approach used the ‘InVEST (Integrated Valuation of Ecosystem Services and Trade-offs) 3.1.0’ ecosystem service model suite, raster land cover maps at two spatial resolutions (5 m and 25 m) and published literature values for carbon storage by land cover. The resulting data are presented in the form of two ‘GeoTIFF’ raster map files (and associated metadata and spatial information files required by software) that can be viewed and manipulated in Geographic Information Software. The units are kg C per square meter. The purpose of the modelling was to help assess and visualise the value that urban green space represents to urban residents and natural systems in just one of many ecosystem services.
This research was conducted as part of the larger 'Fragments, Functions, Flows and Urban Ecosystem Services' (F3UES) programme. Detailed methods and results of this analysis are published in: Grafius DR, Corstanje R, Warren PH, et al (2016) The impact of land use/land cover scale on modelling urban ecosystem services. Landsc Ecol 31:1509–1522. doi: 10.1007/s10980-015-0337-7. Full details about this dataset can be found at https://doi.org/10.5285/9209af2c-24f6-4e37-98fe-550032e97a2c
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.