The base map consists of the city’s basic geographical information and has the highest level of detail used in the urban development area as a whole. The map is also used outside the city’s activities in areas such as planning and planning. By providing the base map as open data, the city opens up for wider use and the possibility of new innovative applications.ContentBasic map includes:

BuildingsCommunicationMarket useAddressesRegistermap (property limits and rights, etc.) The information in the register map has no legal effect and may be poorly accurate. In case of exact information requirements, verification should be carried out on the basis of decision documents.AtkomstBaskartan is downloaded via http://kartor.helsingborg.se/oppnageodata/baskarta.phpFormat and object modelThe map is delivered as a zip file containing one GeoJSON file per object type. Coordinate system is SWEREF99 13 30. The files are a direct export from the Helsingborg City Planning Administration’s database and are named as follows:

Object types sometimes have attributes that come from domains. Then a value can be represented in a digit instead of saving a string over and over again. During export we have exploded the domains with the suffix “_resolved” so that they can still be seen in plain text.“PURPOSE”:10, “PURPOSE_resolved”:“Småhus — detached”

The tables in the theme “Registration map” have a specific title in two letters. Exempel:Registerkarta AQIn order to understand the contents of those tables, it may help to examine the attribute “dep” where a more readable description is given. Complete documentation on the registry map is currently missing. However, Lantmäteriet provides similar products where table names exist. Please see exempel:https://www.lantmateriet.se/globalassets/kartor-oc...MetadataEn mapping to translate table names into English can be found here. Structure:[{“Geo object class”:“Facility, point”, “Geo object class English”:“MAPCONSTRUCTIONP”},... ]

Refresh rate The zip file is updated weekly, the night between Saturday and Sunday. In the zip file there is a folder metadata. In it is readme.txt which contains a date stamp that tells you when the actual export was made.

FAQ base map

How can I look at the map without any specific program? Download the zip file and unpack it. Search “GeoJSON viewer” in your browser. For example, http://www.mapshaper.org/. Drag in and drop a GeoJSON file to view it.

Can I use the base map in my CAD system?Plugin/app is available to Autodesk. https://apps.autodesk.com/ACD/en/Detail/Index?id=5...

Can I use the base map in my GIS? QGIS has good support for GeoJSON. ArcMap requires Data Interopability add-on. FME can read and convert.

Can I convert GeoJSON to shape? Several free services are available to convert to shape. Among others, http://www.mapshaper.org/.

This dataset contains both large (A0) printable maps of the Torres Strait broken into six overlapping regions, based on a clear sky, clear water composite Sentinel 2 composite imagery and the imagery used to create these maps. These maps show satellite imagery of the region, overlaid with reef and island boundaries and names. Not all features are named, just the more prominent features. This also includes a vector map of Ashmore Reef and Boot Reef in Coral Sea as these were used in the same discussions that these maps were developed for. The map of Ashmore Reef includes the atoll platform, reef boundaries and depth polygons for 5 m and 10 m.

This dataset contains all working files used in the development of these maps. This includes all a copy of all the source datasets and all derived satellite image tiles and QGIS files used to create the maps. This includes cloud free Sentinel 2 composite imagery of the Torres Strait region with alpha blended edges to allow the creation of a smooth high resolution basemap of the region.

The base imagery is similar to the older base imagery dataset: Torres Strait clear sky, clear water Landsat 5 satellite composite (NERP TE 13.1 eAtlas, AIMS, source: NASA).

Most of the imagery in the composite imagery from 2017 - 2021.


Method:
The Sentinel 2 basemap was produced by processing imagery from the World_AIMS_Marine-satellite-imagery dataset (01-data/World_AIMS_Marine-satellite-imagery in the data download) for the Torres Strait region. The TrueColour imagery for the scenes covering the mapped area were downloaded. Both the reference 1 imagery (R1) and reference 2 imagery (R2) was copied for processing. R1 imagery contains the lowest noise, most cloud free imagery, while R2 contains the next best set of imagery. Both R1 and R2 are typically composite images from multiple dates.

The R2 images were selectively blended using manually created masks with the R1 images. This was done to get the best combination of both images and typically resulted in a reduction in some of the cloud artefacts in the R1 images. The mask creation and previewing of the blending was performed in Photoshop. The created masks were saved in 01-data/R2-R1-masks. To help with the blending of neighbouring images a feathered alpha channel was added to the imagery. The processing of the merging (using the masks) and the creation of the feathered borders on the images was performed using a Python script (src/local/03-merge-R2-R1-images.py) using the Pillow library and GDAL. The neighbouring image blending mask was created by applying a blurring of the original hard image mask. This allowed neighbouring image tiles to merge together.

The imagery and reference datasets (reef boundaries, EEZ) were loaded into QGIS for the creation of the printable maps.

To optimise the matching of the resulting map slight brightness adjustments were applied to each scene tile to match its neighbours. This was done in the setup of each image in QGIS. This adjustment was imperfect as each tile was made from a different combinations of days (to remove clouds) resulting in each scene having a different tonal gradients across the scene then its neighbours. Additionally Sentinel 2 has slight stripes (at 13 degrees off the vertical) due to the swath of each sensor having a slight sensitivity difference. This effect was uncorrected in this imagery.


Single merged composite GeoTiff:
The image tiles with alpha blended edges work well in QGIS, but not in ArcGIS Pro. To allow this imagery to be used across tools that don't support the alpha blending we merged and flattened the tiles into a single large GeoTiff with no alpha channel. This was done by rendering the map created in QGIS into a single large image. This was done in multiple steps to make the process manageable.

The rendered map was cut into twenty 1 x 1 degree georeferenced PNG images using the Atlas feature of QGIS. This process baked in the alpha blending across neighbouring Sentinel 2 scenes. The PNG images were then merged back into a large GeoTiff image using GDAL (via QGIS), removing the alpha channel. The brightness of the image was adjusted so that the darkest pixels in the image were 1, saving the value 0 for nodata masking and the boundary was clipped, using a polygon boundary, to trim off the outer feathering. The image was then optimised for performance by using internal tiling and adding overviews. A full breakdown of these steps is provided in the README.md in the 'Browse and download all data files' link.

The merged final image is available in export\TS_AIMS_Torres Strait-Sentinel-2_Composite.tif.


Source datasets:
Complete Great Barrier Reef (GBR) Island and Reef Feature boundaries including Torres Strait Version 1b (NESP TWQ 3.13, AIMS, TSRA, GBRMPA), https://eatlas.org.au/data/uuid/d2396b2c-68d4-4f4b-aab0-52f7bc4a81f5

Geoscience Australia (2014b), Seas and Submerged Lands Act 1973 - Australian Maritime Boundaries 2014a - Geodatabase [Dataset]. Canberra, Australia: Author. https://creativecommons.org/licenses/by/4.0/ [license]. Sourced on 12 July 2017, https://dx.doi.org/10.4225/25/5539DFE87D895

Basemap/AU_GA_AMB_2014a/Exclusive_Economic_Zone_AMB2014a_Limit.shp
The original data was obtained from GA (Geoscience Australia, 2014a). The Geodatabase was loaded in ArcMap. The Exclusive_Economic_Zone_AMB2014a_Limit layer was loaded and exported as a shapefile. Since this file was small no clipping was applied to the data.

Geoscience Australia (2014a), Treaties - Australian Maritime Boundaries (AMB) 2014a [Dataset]. Canberra, Australia: Author. https://creativecommons.org/licenses/by/4.0/ [license]. Sourced on 12 July 2017, http://dx.doi.org/10.4225/25/5539E01878302
Basemap/AU_GA_Treaties-AMB_2014a/Papua_New_Guinea_TSPZ_AMB2014a_Limit.shp
The original data was obtained from GA (Geoscience Australia, 2014b). The Geodatabase was loaded in ArcMap. The Papua_New_Guinea_TSPZ_AMB2014a_Limit layer was loaded and exported as a shapefile. Since this file was small no clipping was applied to the data.

AIMS Coral Sea Features (2022) - DRAFT
This is a draft version of this dataset. The region for Ashmore and Boot reef was checked. The attributes in these datasets haven't been cleaned up. Note these files should not be considered finalised and are only suitable for maps around Ashmore Reef. Please source an updated version of this dataset for any other purpose.
CS_AIMS_Coral-Sea-Features/CS_Names/Names.shp
CS_AIMS_Coral-Sea-Features/CS_Platform_adj/CS_Platform.shp
CS_AIMS_Coral-Sea-Features/CS_Reef_Boundaries_adj/CS_Reef_Boundaries.shp
CS_AIMS_Coral-Sea-Features/CS_Depth/CS_AIMS_Coral-Sea-Features_Img_S2_R1_Depth5m_Coral-Sea.shp
CS_AIMS_Coral-Sea-Features/CS_Depth/CS_AIMS_Coral-Sea-Features_Img_S2_R1_Depth10m_Coral-Sea.shp

Murray Island 20 Sept 2011 15cm SISP aerial imagery, Queensland Spatial Imagery Services Program, Department of Resources, Queensland
This is the high resolution imagery used to create the map of Mer.

World_AIMS_Marine-satellite-imagery
The base image composites used in this dataset were based on an early version of Lawrey, E., Hammerton, M. (2024). Marine satellite imagery test collections (AIMS) [Data set]. eAtlas. https://doi.org/10.26274/zq26-a956. A snapshot of the code at the time this dataset was developed is made available in the 01-data/World_AIMS_Marine-satellite-imagery folder of the download of this dataset.


Data Location:
This dataset is filed in the eAtlas enduring data repository at: data\custodian\2020-2029-AIMS\TS_AIMS_Torres-Strait-Sentinel-2-regional-maps. On the eAtlas server it is stored at eAtlas GeoServer\data\2020-2029-AIMS.


Change Log:
2025-05-12: Eric Lawrey
Added Torres-Strait-Region-Map-Masig-Ugar-Erub-45k-A0 and Torres-Strait-Eastern-Region-Map-Landscape-A0. These maps have a brighten satellite imagery to allow easier reading of writing on the maps. They also include markers for geo-referencing the maps for digitisation.

2025-02-04: Eric Lawrey
Fixed up the reference to the World_AIMS_Marine-satellite-imagery dataset, clarifying where the source that was used in this dataset. Added ORCID and RORs to the record.

2023-11-22: Eric Lawrey
Added the data and maps for close up of Mer.
- 01-data/TS_DNRM_Mer-aerial-imagery/
- preview/Torres-Strait-Mer-Map-Landscape-A0.jpeg
- exports/Torres-Strait-Mer-Map-Landscape-A0.pdf
Updated 02-Torres-Strait-regional-maps.qgz to include the layout for the new map.

2023-03-02: Eric Lawrey
Created a merged version of the satellite imagery, with no alpha blending so that it can be used in ArcGIS Pro. It is now a single large GeoTiff image. The Google Earth Engine source code for the World_AIMS_Marine-satellite-imagery was included to improve the reproducibility and provenance of the dataset, along with a calculation of the distribution of image dates that went into the final composite image. A WMS service for the imagery was also setup and linked to from the metadata. A cross reference to the older Torres Strait clear sky clear water Landsat composite imagery was also added to the record.

The Bright Earth eAtlas Basemap dataset collection is a satellite-derived global map of the world at a 1:1M scale for most of the world and 1:200k scale for Australia. This map was inspired by Natural Earth II (NEII) and NASA's Blue Marble Next Generation (BMNG) imagery.

Its aim was to provide a basemap similar to NEII but with a higher resolution (~10x).

This basemap is derived from the following datasets: Blue Marble Next Generation 2004-04 (NASA), VMap0 coastline, Coast100k 2004 Australian coastline (GeoScience Australia), SRTM30 Plus v8.0 (UCSD) hillshading, Natural Earth Vector 10m bathymetry and coastline v2.0 (NE), gbr100 hillshading (JCU).

This dataset (World_Bright-Earth-e-Atlas-basemap) contains all the files required to setup the Bright Earth eAtlas basemap in a GeoServer. All the data files are stored in GeoTiffs or shapefiles and so can also be loaded into ArcMap, however no styling has been included for this purpose.

This basemap is small enough (~900 MB) that can be readily used locally or deployed to a GeoServer.

Base map aesthetics (added 28 Jan 2025)

The Bright Earth e-Atlas Basemap is a high-resolution representation of the Earth's surface, designed to depict global geography with clarity, natural aesthetics with bright and soft color tones that enhance data overlays without overwhelming the viewer. The land areas are based on NASA's Blue Marble imagery, with modifications to lighten the tone and apply noise reduction filtering to soften the overall coloring. The original Blue Marble imagery was based on composite satellite imagery resulting in a visually appealing and clean map that highlights natural features while maintaining clarity and readability. Hillshading has been applied across the landmasses to enhance detail and texture, bringing out the relief of mountainous regions, plateaus, and other landforms.

The oceans feature three distinct depth bands to illustrate shallow continental areas, deeper open ocean zones, and the very deep trenches and basins. The colors transition from light blue in shallow areas to darker shades in deeper regions, giving a clear sense of bathymetric variation. Hillshading has also been applied to the oceans to highlight finer structures on the seafloor, such as ridges, trenches, and other geological features, adding depth and dimensionality to the depiction of underwater topography.

At higher zoom levels prominent cities are shown and the large scale roads are shown for Australia.

Rendered Raster Version (added 28 Jan 2025)

A low resolution version of the dataset is available as a raster file (PNG, JPG and GeoTiff) at ~2 km and 4 km resolutions. These rasters are useful for applications where GeoServer is not available to render the data dynamically. While the rasters are large they represent a small fraction of the full detail of the dataset. The rastered version was produced using the layout manager in QGIS to render maps of the whole world, pulling the imagery from the eAtlas GeoServer. This imagery from converted to the various formats using GDAL. More detail is provided in 'Rendered-bright-earth-processing.txt' in the download and browse section.

Change Log 2025-01-28: Added two rendered raster versions of the dataset at 21600x10800 and 10400x5400 pixels in size in PNG, JPG and GeoTiff format. Added

Have you ever wanted to create your own maps, or integrate and visualize spatial datasets to examine changes in trends between locations and over time? Follow along with these training tutorials on QGIS, an open source geographic information system (GIS) and learn key concepts, procedures and skills for performing common GIS tasks – such as creating maps, as well as joining, overlaying and visualizing spatial datasets. These tutorials are geared towards new GIS users. We’ll start with foundational concepts, and build towards more advanced topics throughout – demonstrating how with a few relatively easy steps you can get quite a lot out of GIS. You can then extend these skills to datasets of thematic relevance to you in addressing tasks faced in your day-to-day work.

This data package includes two related data files that can be used as input for habitat network analyses on amphibians using a specific habitat network analysis tool (HNAT; v0.1.2-alpha):

1. AmphibianHabitatNetwork_Parameters.xlsx
2. BiotopeMap_GothenburgRegion_withPondsRoadsAndBuildings.tif

HNAT is a plugin for the open-source Geographic Information System QGIS (https://qgis.org/en/site/). HNAT can be downloaded at https://github.com/SMoG-Chalmers/hnat/releases/tag/v0.1.2-alpha. To run the habitat network analyses based on the input data provided in this package one must install the plugin HNAT into QGIS. This software has been created by Chalmers within a research project financed by the Swedish government research council for sustainable development, Formas (FR -2021/0004), within the framework of the national research program "From research to implementation for a sustainable society 2021". The Excel-file contains the parameters for amphibians and the GeoTiff-file is representing a biotope raster map covering the Gothenburg region in western Sweden. SRID=3006 (Sweref99 TM). Pixel size =10x10 metres. The pixel values of the biotope map correspond to the biotope codes listed in the in the parameter file (see column “BiotopeCode”). For each biotope the parameter file holds biotope specific parameter values for two alternative amphibian models denoted “Amphibians_NMDWater_ponds” and Amphibians_NMDWater_ponds_NoFriction”. The two alternative parameter settings can be used to demonstrate the difference in model prediction with or without the assumption that amphibian movements are affected by barrier effects caused by roads, buildings and certain biotopes biotope types. The “NoFriction” version assumes that amphibian dispersal probability declines exponentially with increasing Euclidian distance whereas the other set assumes dispersal to be affected by barriers. Read the readme file for details on each parameter provided in the parameter file.

The GeoTiff-file is a biotope mape which has been created by combining a couple of publicly available geodata sets. As a base for the biotope map the Swedish land cover map NMD was used (https://geodata.naturvardsverket.se/nedladdning/marktacke/NMD2018/NMD2018_basskikt_ogeneraliserad_Sverige_v1_1.zip). To achieve a greater cartographic representation of small ponds, streams, buildings and transport infrastructure relevant for amphibian dispersal, reproduction and foraging, NMD was complemented by information from a number of vector layers. In total, 20 new biotope classes representing buildings of different height ranging from less than 5 m up to 100 m, were added to the basic land cover map. The heights were obtained by analyzing the LiDAR data provided by Swedish Land Survey (for details see Berghauser Pont et al., 2019). The data was rasterized and added on top of existing pixels representing buildings in the Swedish land cover map. The roads were separated into 101 new biotope classes with different expected number of vehicles per day. Instead of using statistics from the Swedish Transport Administration on observed number of vehicles per day relative traffic volumes were predicted based on angular betweenness centrality values calculated from the road network using PST (Place Syntax Tool, Stavroulaki et al. 2023). PST is an open-source plugin for QGIS (https://www.smog.chalmers.se/pst). Traffic volumes are expected to be correlated to the centrality values (Serra and Hillier, 2019). The vector layer with the centrality values was buffered by 15 m prior to rasterization. After that the new pixel values were added to the basic Land cover raster in sequence following the order of centrality values. Information on small streams with a maximum width of 6 m was added from a vector layer of Swedish streams (https://www.lantmateriet.se/en/geodata/geodata-products/product-list/topography-50-download-vector/). These lines where rasterized and added to the land cover raster by replacing the underlaying pixel values with new class specific pixel values. Small pondlike waterbodies was identified from the NMD data selecting contiguous fragments of the original NMD biotope class 61 with a smaller area than 1 hectare. Pixels representing the smaller water bodies was then changed to 201.

References Berghauser Pont M, Stavroulaki G, Bobkova E, et al. (2019). The spatial distribution and frequency of street, plot and building types across five European cities. Environment and Planning B: Urban analytics and city science 46(7): 1226-1242. Serra M and Hillier B (2019) Angular and Metric Distance in Road Network Analysis: A nationwide correlation study. Computers, Environment and Urban Systems 74: 194-207. Stavroulaki I, Berghauser Pont M, Fitger M, et al. (2023) PST Documentation_v.3.2.5_20231128, DOI:10.13140/RG.2.2.32984.67845.

This dataset contains a set of data related to processed information deriving from fieldwork activities and elaboration of archival information and literature (v. Cat 3, Cat 4, Cat 6 Deliverable D6.2, DMP) collected, accessed, and consulted during the WP1 and WP2 research activities. It constitutes a fundamental part that supports the Land-In-Pro spatial and territorial analysis in WP3, which encompasses activities aimed at informing a webGIS that visualises the transformations the selected context/site has undergone over the years in the pilot site, capturing its former and current conditions and configurations, whilst allowing the definition of indicators for the development of the Land-In-Pro Assessment Tool. The Land-In-Pro Pilot Site Mapping GIS project has been structured to ensure usability for both expert GIS users and non-specialist audiences. The project has been set up by using the open-source mobile application Qfield (v.3.4) during fieldwork, and QGIS (v.3.34 Prizren) during the data processing phase. Set in the Roma40 reference system and Gauss–Boaga cartographic projection (EPSG:3003), it is organised into three main layers (zoning, buildings_mapping, views_mapping) with attribute tables containing information available in both Italian and English languages. The buildings_demolished layer is a support vector layer used only for spatial reference: it provides indicative geometries to georeference demolished buildings. For optimal use of the project, it is recommended to add a base map (e.g., Google Satellite or Bing Maps Satellite Imagery) within QGIS. This provides a clear cartographic background that facilitates the orientation and interpretation of the mapped data. This dataset has been curated by Dr Federica Pompejano and Dr Sara Mauri. It relates to:

• WP2
• Version 1.0; created on October 2, 2023; published on September 30, 2025.
• Federica Pompejano, Principal Investigator, RTD-A, Department Architecture and Design (DAD), Università di Genova (UniGe), federica.pompejano@unige.it (creator and depositor)
• Sara Mauri, Postdoctoral researcher, Department Architecture and Design (DAD), Università di Genova (UniGe), sara.mauri@edu.unige.it (depositor)
• Data originates from the collection of spatial data during fieldwork activities and from the processing of archival sources and literature.
• Keywords: NextGenerationEU, NextGenEu, Ministero dell'Università e della Ricerca, MUR, PNRR, UniGe, DAD, MSCA_0000005, Land-In-Pro, Post-industrial landscape, Industrial heritage, Landscape studies, Architectural conservation, Heritage studies, Fieldwork, Photo survey, Data processing, Architetture, Strutture, Paesaggio. Architecture, Landscape, Structures
• Link: https://landinpro.unige.it/pilotsitemapping

This dataset is part of the Land-In-Pro project, which has received funding from the Ministry of University and Research, General Directorate for Internationalisation and Communication – National Recovery and Resilience Plan (PNRR) - Mission 4 “Education and Research” - Component 2 “From Research to Business” - Investment 1.2 “Funding projects presented by young researchers” and the European Union – Next Generation EU. The content of this database reflects only the authors’ views. The authors, Host Institution, Ministry of University and Research and the European Commission are not responsible for any use that may be made of the information it contains.

This dataset contains a QGIS project (.qgz) along with supporting files including PDFs (.pdf), images (.jpg), text (.txt), XML metadata (.xml), and QGIS packages (.qpkg).

The metadata are contained in a markdown README file (.txt). Metadata is compiled using the online tool DataCite Metadata Generator - Kernel 4.4 provided by DataCite Metadata Working Group. (2021). DataCite Metadata Schema Documentation for the Publication and Citation of Research Data and Other Research Outputs. Version 4.4. DataCite e.V. https://doi.org/10.14454/3w3z-sa82.

Land-In-Pro Pilot Site Mapping © 2025 by Land-In-Pro Project - Federica Pompejano and Sara Mauri, Department of Architecture and Design (DAD), Università di Genova (UniGe) is licensed under Attribution-NonCommercial 4.0 International (CC BY-NC 4.0). If not otherwise indicated, images were acquired by researchers during fieldwork and mapping activities conducted under Land-In-Pro research project's WP2 and WP3 within the territorial context of the pilot site (Ferrania, Cairo Montenotte, Savona, Italy). The information contained in each form is the result of a combined processing of raw fieldwork data and the elaboration of heterogeneous historical sources, including: archival materials (currently under inventory process) from the Ferrania Film Museum in Cairo Montenotte (SV); municipal building records (Municipal Archive of Building Practices, Municipality of Cairo Montenotte, Savona); and historical cadastral maps (Cadastral Map Collection, State Archives of Savona). All consultation permits were previously acquired. Consulted archive materials are available for on-site consultation under each archive's rules and conditions.

Here is an image of the global municipal tax (founcier bati + habitation). Average tax per asset Nancy 2014

To do it again you will need: — QGIS software (Free: https://www.qgis.org/fr/site/forusers/download.html), — a qgs file of your department (http://www.actualitix.com/shapefiles-des-departements-de-france.html) — an export of tax rates (https://www.data.gouv.fr/fr/datasets/impots-locaux/ > Municipal and intercommunal data > Your Department > Local Direct Tax Data 2014 (XLS format)) — data (most days of INSEE here 2012 http://www.insee.fr/fr/themes/detail.asp?reg_id=99&ref_id=base-cc-emploi-pop-active-2012)

Operating Mode: — process your data in your favorite spreadsheet (Excel or OpenOffice Calc) by integrating impot data, and INSEE to pull out the numbers that seem revealing to you — Install QGIS — Open the.qgs of your department

Add columns — Right click property on the main layer — Go to the field menu (on the left) — Add (via pencil) the desired columns (here average housing tax per asset, average property tax per asset, and the sum of both) — These are reals of precision 2, and length 6 — Register

Insert data: — Right-click on the “Open attribute table” layer — Select all — Copy — Paste in excel (or openOffice calcs) — Put the ad hoc formulas in excel (SOMME.SI.ENS to recover the rate) — Save the desired tab in CSV DOS with the new values — In QGIS > Menu > Layer > Add a delimited layer of text — Import the CSV

Present the data: — To simplify I advise you to make a layer by rate, and layers sums. So rots you in three clicks out the image of the desired rate — For each layer (or rate) — Right click properties on the csv layer — Labels to add city name and desired rate — Style for fct coloring of a csv field

Print the data in pdf: — To print, you need to define a print template — In the menu choose new printing dialer — choose the format (a department in A0 is rather readable) — Add vas legend, scale, and other — Print and here...

NB: this method creates aberrations: — in the case where the INSEE does not have a number or numbers that have moved a lot since — it is assumed that only assets pay taxes (which is more fair, but not 100 %)

Intellectual property of A Song of Ice and Fire, this map and all locations copyright George RR Martin (www.georgerrmartin.com).

Map of Westeros (original version) created originally by Tear of the Cartographer's Guild (http://www.cartographersguild.com/showthread.php?t=6683), updated and extended by theMountainGoat (http://www.sermountaingoat.co.uk/map/index.php) in 2012: Updates to Westeros, addition of Essos, Sothoryos, Ibben and the Summer Isles based in part upon the speculative world map drawn by Werthead (www.thewertzone.blogspot.com). Some locations positioned according to the maps drawn by Other-in-Law.

These GIS-map-files are based on this work and are created by cadaei in QGIS 2.8.

The scale is of course not exact, as it is not clear what projection the original map used and on what kind of planet the map is located. I placed the continents roughly on the place of the coordinates of Africa to minimize the distortion near the poles. The scale is slightly too small (the Wall is only 240 miles long), so don't use the map for distance measuring. It's thought to provide the vector-geometry and labels of the world of a Song of Ice and Fire.

Locations have a field 'confirmed' which is '1' for confirmed locations and '0' for locations with speculative location.

The Areas outside the polygons of the file officialMapAreas.shp are the parts of the map which are not official and based on assumptions (see http://www.sermountaingoat.co.uk/map/index.php for more info about how theMountainGoat created these areas) and can be outdated.

Credits

Original Data

Foto von mauRÍCIO SANTOS auf Unsplash

Summary:

The files contained herein represent green roof footprints in NYC visible in 2016 high-resolution orthoimagery of NYC (described at https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_AerialImagery.md). Previously documented green roofs were aggregated in 2016 from multiple data sources including from NYC Department of Parks and Recreation and the NYC Department of Environmental Protection, greenroofs.com, and greenhomenyc.org. Footprints of the green roof surfaces were manually digitized based on the 2016 imagery, and a sample of other roof types were digitized to create a set of training data for classification of the imagery. A Mahalanobis distance classifier was employed in Google Earth Engine, and results were manually corrected, removing non-green roofs that were classified and adjusting shape/outlines of the classified green roofs to remove significant errors based on visual inspection with imagery across multiple time points. Ultimately, these initial data represent an estimate of where green roofs existed as of the imagery used, in 2016.

These data are associated with an existing GitHub Repository, https://github.com/tnc-ny-science/NYC_GreenRoofMapping, and as needed and appropriate pending future work, versioned updates will be released here.

Terms of Use:

The Nature Conservancy and co-authors of this work shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any sale, distribution, loan, or offering for use of these digital data, in whole or in part, is prohibited without the approval of The Nature Conservancy and co-authors. The use of these data to produce other GIS products and services with the intent to sell for a profit is prohibited without the written consent of The Nature Conservancy and co-authors. All parties receiving these data must be informed of these restrictions. Authors of this work shall be acknowledged as data contributors to any reports or other products derived from these data.

Associated Files:

As of this release, the specific files included here are:

• GreenRoofData2016_20180917.geojson is in the human-readable, GeoJSON format, in geographic coordinates (Lat/Long, WGS84; EPSG 4263).
• GreenRoofData2016_20180917.gpkg is in the GeoPackage format, which is an Open Standard readable by most GIS software including Esri products (tested on ArcMap 10.3.1 and multiple versions of QGIS). This dataset is in the New York State Plan Coordinate System (units in feet) for the Long Island Zone, North American Datum 1983, EPSG 2263.
• GreenRoofData2016_20180917_Shapefile.zip is a zipped folder containing a Shapefile and associated files. Please note that some field names were truncated due to limitations of Shapefiles, but columns are in the same order as for other files and in the same order as listed below. This dataset is in the New York State Plan Coordinate System (units in feet) for the Long Island Zone, North American Datum 1983, EPSG 2263.
• GreenRoofData2016_20180917.csv is a comma-separated values file (CSV) with coordinates for centroids for the green roofs stored in the table itself. This allows for easily opening the data in a tool like spreadsheet software (e.g., Microsoft Excel) or a text editor.

Column Information for the datasets:

Some, but not all fields were joined to the green roof footprint data based on building footprint and tax lot data; those datasets are embedded as hyperlinks below.

• fid - Unique identifier
• bin - NYC Building ID Number based on overlap between green roof areas and a building footprint dataset for NYC from August, 2017. (Newer building footprint datasets do not have linkages to the tax lot identifier (bbl), thus this older dataset was used). The most current building footprint dataset should be available at: https://data.cityofnewyork.us/Housing-Development/Building-Footprints/nqwf-w8eh. Associated metadata for fields from that dataset are available at https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_BuildingFootprints.md.
• bbl - Boro Block and Lot number as a single string. This field is a tax lot identifier for NYC, which can be tied to the Digital Tax Map (http://gis.nyc.gov/taxmap/map.htm) and PLUTO/MapPLUTO (https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page). Metadata for fields pulled from PLUTO/MapPLUTO can be found in the PLUTO Data Dictionary found on the aforementioned page. All joins to this bbl were based on MapPLUTO version 18v1.
• gr_area - Total area of the footprint of the green roof as per this data layer, in square feet, calculated using the projected coordinate system (EPSG 2263).
• bldg_area - Total area of the footprint of the associated building, in square feet, calculated using the projected coordinate system (EPSG 2263).
• prop_gr - Proportion of the building covered by green roof according to this layer (gr_area/bldg_area).
• cnstrct_yr - Year the building was constructed, pulled from the Building Footprint data.
• doitt_id - An identifier for the building assigned by the NYC Dept. of Information Technology and Telecommunications, pulled from the Building Footprint Data.
• heightroof - Height of the roof of the associated building, pulled from the Building Footprint Data.
• feat_code - Code describing the type of building, pulled from the Building Footprint Data.
• groundelev - Lowest elevation at the building level, pulled from the Building Footprint Data.
• qa - Flag indicating a positive QA/QC check (using multiple types of imagery); all data in this dataset should have 'Good'
• notes - Any notes about the green roof taken during visual inspection of imagery; for example, it was noted if the green roof appeared to be missing in newer imagery, or if there were parts of the roof for which it was unclear whether there was green roof area or potted plants.
• classified - Flag indicating whether the green roof was detected image classification. (1 for yes, 0 for no)
• digitized - Flag indicating whether the green roof was digitized prior to image classification and used as training data. (1 for yes, 0 for no)
• newlyadded - Flag indicating whether the green roof was detected solely by visual inspection after the image classification and added. (1 for yes, 0 for no)
• original_source - Indication of what the original data source was, whether a specific website, agency such as NYC Dept. of Parks and Recreation (DPR), or NYC Dept. of Environmental Protection (DEP). Multiple sources are separated by a slash.
• address - Address based on MapPLUTO, joined to the dataset based on bbl.
• borough - Borough abbreviation pulled from MapPLUTO.
• ownertype - Owner type field pulled from MapPLUTO.
• zonedist1 - Zoning District 1 type pulled from MapPLUTO.
• spdist1 - Special District 1 pulled from MapPLUTO.
• bbl_fixed - Flag to indicate whether bbl was manually fixed. Since tax lot data may have changed slightly since the release of the building footprint data used in this work, a small percentage of bbl codes had to be manually updated based on overlay between the green roof footprint and the MapPLUTO data, when no join was feasible based on the bbl code from the building footprint data. (1 for yes, 0 for no)

For GreenRoofData2016_20180917.csv there are two additional columns, representing the coordinates of centroids in geographic coordinates (Lat/Long, WGS84; EPSG 4263):

• xcoord - Longitude in decimal degrees.
• ycoord - Latitude in decimal degrees.

Acknowledgements:

This work was primarily supported through funding from the J.M. Kaplan Fund, awarded to the New York City Program of The Nature Conservancy, with additional support from the New York Community Trust, through New York City Audubon and the Green Roof Researchers Alliance.

The High Resolution Digital Elevation Model (HRDEM) product is derived from airborne LiDAR data (mainly in the south) and satellite images in the north. The complete coverage of the Canadian territory is gradually being established. It includes a Digital Terrain Model (DTM), a Digital Surface Model (DSM) and other derived data. For DTM datasets, derived data available are slope, aspect, shaded relief, color relief and color shaded relief maps and for DSM datasets, derived data available are shaded relief, color relief and color shaded relief maps. The productive forest line is used to separate the northern and the southern parts of the country. This line is approximate and may change based on requirements. In the southern part of the country (south of the productive forest line), DTM and DSM datasets are generated from airborne LiDAR data. They are offered at a 1 m or 2 m resolution and projected to the UTM NAD83 (CSRS) coordinate system and the corresponding zones. The datasets at a 1 m resolution cover an area of 10 km x 10 km while datasets at a 2 m resolution cover an area of 20 km by 20 km. In the northern part of the country (north of the productive forest line), due to the low density of vegetation and infrastructure, only DSM datasets are generally generated. Most of these datasets have optical digital images as their source data. They are generated at a 2 m resolution using the Polar Stereographic North coordinate system referenced to WGS84 horizontal datum or UTM NAD83 (CSRS) coordinate system. Each dataset covers an area of 50 km by 50 km. For some locations in the north, DSM and DTM datasets can also be generated from airborne LiDAR data. In this case, these products will be generated with the same specifications as those generated from airborne LiDAR in the southern part of the country. The HRDEM product is referenced to the Canadian Geodetic Vertical Datum of 2013 (CGVD2013), which is now the reference standard for heights across Canada. Source data for HRDEM datasets is acquired through multiple projects with different partners. Since data is being acquired by project, there is no integration or edgematching done between projects. The tiles are aligned within each project. The product High Resolution Digital Elevation Model (HRDEM) is part of the CanElevation Series created in support to the National Elevation Data Strategy implemented by NRCan. Collaboration is a key factor to the success of the National Elevation Data Strategy. Refer to the “Supporting Document” section to access the list of the different partners including links to their respective data.

AbstractCoastline for Antarctica created from various mapping and remote sensing sources, consisting of the following coast types: 'ice coastline', 'rock coastline', 'grounding line', 'ice shelf and front', 'ice rumple', and 'rock against ice shelf', provided as a surface attribute. Covering all land and ice shelves south of 60°S. Suitable for topographic mapping and analysis. High resolution versions of ADD data are suitable for scales larger than 1:1,000,000. The largest suitable scale is changeable and dependent on the region.Changes in v7.11 include updates to the coastline of Adelaide Island and surrounding islands, the grounding line of Alexander Island and the surrounding region, and the ice shelf front of the Brunt Ice Shelf. In addition, sourcedate and revdate attributes were updated to a consistent YYYY-MM-DD format. To indicate limited date precision for earlier records, sourceprec and revprec attributes were introduced.Data compiled, managed and distributed by the Mapping and Geographic Information Centre and the UK Polar Data Centre, British Antarctic Survey on behalf of the Scientific Committee on Antarctic Research. Further information and useful linksMap projection: WGS84 Antarctic Polar Stereographic, EPSG 3031. Note: by default, opening this layer in the Map Viewer will display the data in Web Mercator. To display this layer in its native projection use an Antarctic basemap. The currency of this dataset is November 2025 and will be reviewed every 6 months. This feature layer will always reflect the most recent version. For more information on, and access to other Antarctic Digital Database (ADD) datasets, refer to the SCAR ADD data catalogue. A related medium resolution dataset is also published via Living Atlas, as well medium and high resolution polygon datasets. For background information on the ADD project, please see the British Antarctic Survey ADD project page. LineageDataset compiled from a variety of Antarctic map and satellite image sources. The dataset was created using ArcGIS and QGIS GIS software programmes and has been checked for basic topography and geometry errors, but does not contain strict topology. Quality varies across the dataset, certain areas where high-resolution source data were available are suitable for large-scale maps, whereas other areas are only suitable for smaller scales. Each line has attributes detailing the source, which can give the user further indications of its suitability for specific uses. Attributes also give information, including surface (e.g. grounding line, ice coastline, ice shelf front) and revision date (revdate), accompanied by revprec - date precision, either day, month, or year. Compiled from sources ranging in time from 1990s-2025 - individual lines contain exact source dates in sourcedate field with the corresponding sourceprec field. CitationGerrish, L., Ireland, L., Fretwell, P., Cooper, P., & Skachkova, A. (2025). High resolution vector polylines of the Antarctic coastline (Version 7.11) [Data set]. NERC EDS UK Polar Data Centre. https://doi.org/10.5285/cc0b73c0-3b53-40fb-ae84-b5dce4ac163a If using for a graphic or if short on space, please cite as 'data from the SCAR Antarctic Digital Database, 2025'

Abstract Coastline for Antarctica created from various mapping and remote sensing sources, provided as polygons with surface values for 'land', 'ice shelf', 'ice tongue', or 'rumple'. Covering all land and ice shelves south of 60°S. Suitable for topographic mapping and analysis. This dataset has been generalised from the high resolution vector polygons. Medium resolution versions of ADD data are suitable for scales smaller than 1:1,000,000, although certain regions will appear more detailed than others due to variable data availability and coastline characteristics.Changes in v7.11 include updates to the coastline of Adelaide Island and surrounding islands, the grounding line of Alexander Island and the surrounding region, and the ice shelf front of the Brunt Ice Shelf.Data compiled, managed and distributed by the Mapping and Geographic Information Centre and the UK Polar Data Centre, British Antarctic Survey on behalf of the Scientific Committee on Antarctic Research. Further information and useful linksMap projection: WGS84 Antarctic Polar Stereographic, EPSG 3031. Note: by default, opening this layer in the Map Viewer will display the data in Web Mercator. To display this layer in its native projection use an Antarctic basemap. The currency of this dataset is November 2024 and will be reviewed every 6 months. This feature layer will always reflect the most recent version. For more information on, and access to other Antarctic Digital Database (ADD) datasets, refer to the SCAR ADD data catalogue. A related high resolution dataset is also published via Living Atlas, as well medium and high resolution line datasets. For background information on the ADD project, please see the British Antarctic Survey ADD project page. LineageDataset compiled from a variety of Antarctic map and satellite image sources. The dataset was created using ArcGIS and QGIS GIS software programmes and has been checked for basic topography and geometry errors, but does not contain strict topology. Quality varies across the dataset, certain areas where high resolution source data were available are suitable for large scale maps, whereas other areas are only suitable for smaller scales. Each polygon contains a surface attribute with either 'land', 'ice shelf', 'ice tongue' or 'rumple'. Details of when and how each line was created can be found in the attributes of the high or medium resolution polyline coastline dataset. Data sources range in time from the 1990s to 2025. This medium resolution version has been generalised from the high resolution version. All polygons <0.1km² not intersecting anything else were deleted and the simplify tool was used in ArcGIS with the retain critical points algorithm and a smoothing tolerance of 50m. Citation Gerrish, L., Ireland, L., Fretwell, P., Cooper, P., & Skachkova, A. (2025). Medium resolution vector polygons of the Antarctic coastline (Version 7.11) [Data set]. NERC EDS UK Polar Data Centre. https://doi.org/10.5285/981b1444-c57e-40f1-b6e9-884b44cad00eIf using for a graphic or if short on space, please cite as 'Data from the SCAR Antarctic Digital Database, 2025'.

This is an update of maps produced by Sanderman et al (2018). The improvements to the 3D spatial prediction include:

• new updated global mangrove coverage map (contact Thomas Worthington),

• new ALOS-based DEM of the world AW3D30 v18.04,

• new radar ALOS-based PALSAR radar images of the world,

• additional SOC points (ca 550) published in Rovai et al. (2018) used in model training (see gpkg file).

To open map in QGIS or similar, drag and drop the "mangroves_dSOC_0_100cm_30m.vrt" file. You can than add also the gpkg file contain the training points. A preview (WMS) of the predictions is available here.

Production steps (ensemble predictions using SuperLearner) are explained in detail at:

• R code: https://github.com/whrc/Mangrove-Soil-Carbon/ (see "R_code/GMW_mangroves_SOC_30m.R")
• Tutorial: "Predictive Soil Mapping with R"

Produced for the purpose of Mangrove Restoration Potential Map funded by The Nature Conservancy and IUCN. Contact TNC: Emily Landis <elandis@TNC.ORG>. Contact IUCN / University of Cambridge: Thomas Worthington <taw52@cam.ac.uk>.

This dataset compiles georeferenced media - including videos (480), articles (20), and datasets (6) - specifically curated to facilitate the understanding of reef habitats across northern Australia. It was designed as a research tool for virtual fieldwork with a particular focus on identifying sources of information that allow an understanding of both inshore and offshore reef environments. This dataset provides a record of the literature and media that was reviewed as part of mapping the reef boundaries from remote sensing as part of project NESP MaC 3.17.

This dataset only focuses on media that is useful for understanding shallow reef habitats. It includes videos of snorkelling, diving, spearfishing, and aerial drone imagery. It includes websites, books and journal papers that talk about the structure of reefs and datasets that provide fine scale benthic mapping.

This dataset is likely to not comprehensive. While considerable time was put into collecting relevant media, finding all available information sources is very difficult and time consuming.

A relatively comprehensive search was conducted on:
- AIMS Metadata catalogue for benthic habitat mapping with tow videos and BRUVS
- A review of the eAtlas for benthic habitat mapping
- YouTube searches for video media of fishing, cruises, snorkelling of many named locations.
The dataset is far less comprehensive on existing literature from journals, reports and dataset.

As the NESP MaC 3.17 project progresses we will continue to expand the dataset.


Changelog:

Changes made to the dataset will be noted in the change log and indicated in the dataset via the 'Revision' date.
1st Ed. - 2024-04-10 - Initial release of the dataset


Methods:

Identifying media - YouTube videos
The initial discovery of videos for a given area was achieved by searching for place names in YouTube search using terms such as diving, snorkeling or spearfishing combined with the location name.

Each potential video was reviewed to:

1. Determine if the video had any visual content that would useful for understanding the marine environment.
2. Determine if the footage could be georeferenced to a specific location, the more specific the better.

In cases where the YouTube channel was making travel videos that were of a high quality, then all the relevant videos in that channel were reviewed. A high proportion of the most useful videos were found using this technique.

The most useful videos were those that had named specific locations (typically in their title or description) and contained drone footage and underwater footage. The drone footage would often show enough of the landscape for features to be matched with satellite imagery allowing precise geolocation of the imagery.

To minimise the time required to find relevant videos, the scrubbing feature on YouTube was used to allow the timeline of the video to be quickly reviewed for relevant scenes. The scrubbing feature shows a very quick, but low resolution version of the video as the cursor is moved along the video timeline. This scrubbing was used to quickly look through the videos for any scenes that contained drone footage, for underwater footage. This was particularly useful for travel videos that contained significant footage of overland travel mixed in with boating or shoreline activities. It was also useful for fishing videos where all the fishing activities could be quickly skipped over to focus on any available drone footage or underwater footage from snorkeling or spearfishing.

Where a video lacked direct clues to the location (such as in the title), but the footage contained particularly relevant and useful footage, additional effort was made listen to the conversations and other footage in the videos for additional clues. This includes people in the video talking about the names of locations, or any marine charts in the footage, or previous and proceeding scenes, where the location could be determined, adding constraints to the location of the relevant scene. Where the footage could not be precisely determine, but the footage was still useful then it was added to a video playlist for the region.

In many remote locations there were so few videos that the bar for including the videos was quite low as these videos would at least provide some general indication of the landscape.

When on PC, Google Maps was used to look up locations and act as reference satellite imagery for locating places, QGIS was used to record the polygons of locations and YouTube in a browser was used for video review.

YouTube Playlists:
The initial collection of videos were compiled into YouTube playlists corresponding to relatively large regions. Using playlists was the most convenient way to record useful videos when viewing YouTube from an iPad. This compilation was done prior to the setup of this dataset.

Localising Playlists:
For YouTube playlists the region digitised was based on the region represented by the playlist name and the collection of videos. Google maps was used to help determine the locations of each region. Where a particularly useful video is found in one of the playlists and its location can be determined accurately then this video was entered into this database as an individual video with its own finer scale mapping. However this process of migrating the videos from the playlists to more highly georeferenced individual videos in the dataset is incomplete.

The playlists are really a catch-all for potentially useful videos.

Localising individual videos:
Candidate videos were quickly assessed for likely usefulness by reviewing the title and quickly scrubbing through the video looking for any marine footage, in water or as drone footage. If a video had a useful section then the focus was to determine the location of that part of the footage as accurately as possible. This was done by searching for locations listed in the title, chapter markers, video description, or mentions in video. These were then looked up in Google Maps. In general we would start with any drone footage that shows a large area with distinct features that could be matched with satellite imagery. The region around named locations were scanned for matching coastline and marine features. Once a match was found then the footage would be reviewed to track the likely area that the video covers in multiple scenes.

The video region was then digitised approximately in QGIS into the AU_AIMS_NESP-3-17_Reef-map-geo-media.shp shapefile. Notes were then added about the important features seen in the footage. A link to the video, including the time code so that it would start at the relevant portion of the video. Long videos showing multiple locations were added as multiple entries, each with a separate polygon location and a different URL link with a different start time.

Articles and Datasets
While this dataset primarily focuses on videos, we started adding relevant datasets, websites, articles and reports. These categories of media are not complete in this version of the dataset.


Data dictionary:

RegionName: (String, 255 characters): Name of the location, Examples: 'Oyster Stacks Snorkelling Area', 'Kurrajong Campground', 'South Lefroy Bay'
State: (String, 30 characters): Abbreviation of the state that the region corresponds to. For example: 'WA', 'QLD', 'NT'. For locations far offshore link the location to the closest state or to an existing well known region name. For example: Herald Cay -> Coral Sea, Rowley shoals -> WA.
MediaType: (String, 20 characters): One of the following:
- Video
- Video Playlist
- Website
- Report
- EIS
- Book
- Journal Paper

HabitatRef: (Int): An indication that this resource shows high accuracy spatial habitat information can be used for improving the UQ habitat reference datasets. This attribute should indicate which resources should be reviewed and converted to habitat reference patches. It should be reserved for where a habitat can be located on satellite imagery with sufficient precision that it has high confidence. Media that corresponds to information that is deeper than 15 m is excluded (assigned a HabitatRef of 0) as this is too deep to be used by the UQ habitat mapping.
- 1 - Use for habitat reference data.
- 0 - Only provides general information about the patch. Imagery can be spatially located accurately or detail is insufficient.

Highlight: (String, 255 characters): This records the classification of reef mapping, or research question that this video is most useful for. Not all videos need this classification. In general this attribute should be reserved for those videos that have the highest level of useful information. Think of it as a shortlist of videos that someone trying to understand a particular aspect of categorising reefs from satellite imagery should review. The following are some of the questions associated with each category that the videos provide some answers.
- High tidal range fringing reef: Here we want to understand the structure of fringing reefs in the Kimberleys and Northern Territory where the tides are large and the water is turbid. Is there coral on the tops of the reef flats? Won't the coral dry out if it grows on the reef flat? How will it get enough light if it grows on the reef slope?
- Ancient coastline: Along many parts of WA there are shallow rocky reefs off the coast that appear to be acient coastline. What is the nature of these reefs? Does coral or macroalgae grow on them?
- Seagrass: What does seagrass look like from satellite imagery
- Ningaloo backreef coral: Ningaloo is a very large reef system with a large sandy back. Should the whole back reef

Introduction

We are enclosing the database used in our research titled "Concentration and Geospatial Modelling of Health Development Offices' Accessibility for the Total and Elderly Populations in Hungary", along with our statistical calculations. For the sake of reproducibility, further information can be found in the file Short_Description_of_Data_Analysis.pdf and Statistical_formulas.pdf

The sharing of data is part of our aim to strengthen the base of our scientific research. As of March 7, 2024, the detailed submission and analysis of our research findings to a scientific journal has not yet been completed.

The dataset was expanded on 23rd September 2024 to include SPSS statistical analysis data, a heatmap, and buffer zone analysis around the Health Development Offices (HDOs) created in QGIS software.

Short Description of Data Analysis and Attached Files (datasets):

Our research utilised data from 2022, serving as the basis for statistical standardisation. The 2022 Hungarian census provided an objective basis for our analysis, with age group data available at the county level from the Hungarian Central Statistical Office (KSH) website. The 2022 demographic data provided an accurate picture compared to the data available from the 2023 microcensus. The used calculation is based on our standardisation of the 2022 data. For xlsx files, we used MS Excel 2019 (version: 1808, build: 10406.20006) with the SOLVER add-in.

Hungarian Central Statistical Office served as the data source for population by age group, county, and regions: https://www.ksh.hu/stadat_files/nep/hu/nep0035.html, (accessed 04 Jan. 2024.) with data recorded in MS Excel in the Data_of_demography.xlsx file.

In 2022, 108 Health Development Offices (HDOs) were operational, and it's noteworthy that no developments have occurred in this area since 2022. The availability of these offices and the demographic data from the Central Statistical Office in Hungary are considered public interest data, freely usable for research purposes without requiring permission.

The contact details for the Health Development Offices were sourced from the following page (Hungarian National Population Centre (NNK)): https://www.nnk.gov.hu/index.php/efi (n=107). The Semmelweis University Health Development Centre was not listed by NNK, hence it was separately recorded as the 108th HDO. More information about the office can be found here: https://semmelweis.hu/egeszsegfejlesztes/en/ (n=1). (accessed 05 Dec. 2023.)

Geocoordinates were determined using Google Maps (N=108): https://www.google.com/maps. (accessed 02 Jan. 2024.) Recording of geocoordinates (latitude and longitude according to WGS 84 standard), address data (postal code, town name, street, and house number), and the name of each HDO was carried out in the: Geo_coordinates_and_names_of_Hungarian_Health_Development_Offices.csv file.

The foundational software for geospatial modelling and display (QGIS 3.34), an open-source software, can be downloaded from:

https://qgis.org/en/site/forusers/download.html. (accessed 04 Jan. 2024.)

The HDOs_GeoCoordinates.gpkg QGIS project file contains Hungary's administrative map and the recorded addresses of the HDOs from the

Geo_coordinates_and_names_of_Hungarian_Health_Development_Offices.csv file,

imported via .csv file.

The OpenStreetMap tileset is directly accessible from www.openstreetmap.org in QGIS. (accessed 04 Jan. 2024.)

The Hungarian county administrative boundaries were downloaded from the following website: https://data2.openstreetmap.hu/hatarok/index.php?admin=6 (accessed 04 Jan. 2024.)

HDO_Buffers.gpkg is a QGIS project file that includes the administrative map of Hungary, the county boundaries, as well as the HDO offices and their corresponding buffer zones with a radius of 7.5 km.

Heatmap.gpkg is a QGIS project file that includes the administrative map of Hungary, the county boundaries, as well as the HDO offices and their corresponding heatmap (Kernel Density Estimation).

A brief description of the statistical formulas applied is included in the Statistical_formulas.pdf.

Recording of our base data for statistical concentration and diversification measurement was done using MS Excel 2019 (version: 1808, build: 10406.20006) in .xlsx format.

• Aggregated number of HDOs by county: Number_of_HDOs.xlsx
• Standardised data (Number of HDOs per 100,000 residents): Standardized_data.xlsx
• Calculation of the Lorenz curve: Lorenz_curve.xlsx
• Calculation of the Gini index: Gini_Index.xlsx
• Calculation of the LQ index: LQ_Index.xlsx
• Calculation of the Herfindahl-Hirschman Index: Herfindahl_Hirschman_Index.xlsx
• Calculation of the Entropy index: Entropy_Index.xlsx
• Regression and correlation analysis calculation: Regression_correlation.xlsx

Using the SPSS 29.0.1.0 program, we performed the following statistical calculations with the databases Data_HDOs_population_without_outliers.sav and Data_HDOs_population.sav:

• Regression curve estimation with elderly population and number of HDOs, excluding outlier values (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_elderly_without_outlier.spv
• Pearson correlation table between the total population, elderly population, and number of HDOs per county, excluding outlier values such as Budapest and Pest County: Pearson_Correlation_populations_HDOs_number_without_outliers.spv.
• Dot diagram including total population and number of HDOs per county, excluding outlier values such as Budapest and Pest Counties: Dot_HDO_total_population_without_outliers.spv.
• Dot diagram including elderly (64<) population and number of HDOs per county, excluding outlier values such as Budapest and Pest Counties: Dot_HDO_elderly_population_without_outliers.spv
• Regression curve estimation with total population and number of HDOs, excluding outlier values (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_without_outlier.spv
• Dot diagram including elderly (64<) population and number of HDOs per county: Dot_HDO_elderly_population.spv
• Dot diagram including total population and number of HDOs per county: Dot_HDO_total_population.spv
• Pearson correlation table between the total population, elderly population, and number of HDOs per county: Pearson_Correlation_populations_HDOs_number.spv
• Regression curve estimation with total population and number of HDOs, (Types of analyzed equations: Linear, Logarithmic, Inverse, Quadratic, Cubic, Compound, Power, S, Growth, Exponential, Logistic, with summary and ANOVA analysis table): Curve_estimation_total_population.spv

For easier readability, the files have been provided in both SPV and PDF formats.

The translation of these supplementary files into English was completed on 23rd Sept. 2024.

If you have any further questions regarding the dataset, please contact the corresponding author: domjan.peter@phd.semmelweis.hu

The 5m DEM is derived from the LiDAR2019B dataset (consisting of the 2018, 2019A and 2019B datasets). The 5m DEM has a vertical accuracy of 30cm. The height reference used is the SA Land Levelling Datum and the SAGEOID2010 was employed.The City of Cape Town Ground Level Map 2019 is defined in the City of Cape Town Municipal Planning Amendment By-law, 2019 as: “‘City of Cape Town Ground Level Map’ means a map approved in terms of the development management scheme, indicating the existing ground level based on floating point raster’s and a contour dataset from LiDAR information available to the City”. The Ground Level Map was approved by the City Council on the 27th July 2023.All Raster Image Services (REST):https://cityimg.capetown.gov.za/erdas-iws/esri/GeoSpatial%20Datasets/rest/services/All Raster Image Services (WMS):Use URL below to add WMS Server Connection in ArcGIS Desktop, ArcPro, QGIS, AutoCAD, etc.https://cityimg.capetown.gov.za/erdas-iws/ogc/wms/GeoSpatial Datasets?service=WMS&request=getcapabilities&For a copy or subset of this dataset, please contact the City Maps Office: city.maps@capetown.gov.zaCCT Ground Level Map: ‘How to Access’ Guide – External Users: CCT Ground Level Map: ‘How to Access’ Guide – External Users | Open Data Portal (arcgis.com)Geomatics Ground Level Map Explainer: Geomatics Ground Level Map Explainer | Open Data Portal (arcgis.com)Land Use Management Ground Level Map Explainer: Land Use Management Ground Level Map Explainer | Open Data Portal (arcgis.com)

Reason for SelectionProtected natural areas in urban environments provide urban residents a nearby place to connect with nature and offer refugia for some species. Because beaches in Puerto Rico and the U.S. Virgin Islands are open to the public, beaches also provide important outdoor recreation opportunities for urban residents, so we include beaches as parks in this indicator.Input DataSoutheast Blueprint 2023 subregions: CaribbeanSoutheast Blueprint 2023 extentNational Oceanic and Atmospheric Administration (NOAA) National Centers for Environmental Information (NCEI) Coastal Relief Model, accessed 11-22-2022Protected Areas Database of the United States (PAD-US) 3.0: VI, PR, and Marine Combined Fee EasementPuerto Rico Protected Natural Areas 2018 (December 2018 update): Terrestrial and marine protected areas (PACAT2018_areas_protegidasPR_TERRESTRES_07052019.shp, PACAT2018_areas_protegidasPR_MARINAS_07052019.shp) 2020 Census Urban Areas from the Census Bureau’s urban-rural classification; download the data, read more about how urban areas were redefined following the 2020 censusOpenStreetMap data “multipolygons” layer, accessed 3-14-2023A polygon from this dataset is considered a park if the “leisure” tag attribute is either “park” or “nature_reserve”, and considered a beach if the value in the “natural” tag attribute is “beach”. OpenStreetMap describes leisure areas as “places people go in their spare time” and natural areas as “a wide variety of physical geography, geological and landcover features”. Data were downloaded in .pbf format and translated ton an ESRI shapefile using R code. OpenStreetMap® is open data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF). Additional credit to OSM contributors. Read more on the OSM copyright page. TNC Lands - Public Layer, accessed 3-8-2023U.S. Virgin Islands beaches layer (separate vector layers for St. Croix, St. Thomas, and St. John) provided by Joe Dwyer with Lynker/the NOAA Caribbean Climate Adaptation Program on 3-3-2023 (contact jdwyer@lynker.com for more information)Mapping StepsMost mapping steps were completed using QGIS (v 3.22) Graphical Modeler.Fix geometry errors in the PAD-US PR data using Fix Geometry. This must be done before any analysis is possible.Merge the terrestrial PR and VI PAD-US layers.Use the NOAA coastal relief model to restrict marine parks (marine polygons from PAD-US and Puerto Rico Protected Natural Areas) to areas shallower than 10 m in depth. The deep offshore areas of marine parks do not meet the intent of this indicator to capture nearby opportunities for urban residents to connect with nature.Merge into one layer the resulting shallow marine parks from marine PAD-US and the Puerto Rico Protected Natural Areas along with the combined terrestrial PAD-US parks, OpenStreetMap, TNC Lands, and USVI beaches. Omit from the Puerto Rico Protected Areas layer the “Zona de Conservación del Carso”, which has some policy protections and conservation incentives but is not formally protected.Fix geometry errors in the resulting merged layer using Fix Geometry.Intersect the resulting fixed file with the Caribbean Blueprint subregion.Process all multipart polygons to single parts (referred to in Arc software as an “explode”). This helps the indicator capture, as much as possible, the discrete units of a protected area that serve urban residents.Clip the Census urban area to the Caribbean Blueprint subregion.Select all polygons that intersect the Census urban extent within 1.2 miles (1,931 m). The 1.2 mi threshold is consistent with the average walking trip on a summer day (U.S. DOT 2002) used to define the walking distance threshold used in the greenways and trails indicator. Note: this is further than the 0.5 mi distance used in the continental version of the indicator. We extended it to capture East Bay and Point Udall based on feedback from the local conservation community about the importance of the park for outdoor recreation.Dissolve all the park polygons that were selected in the previous step.Process all multipart polygons to single parts (“explode”) again.Add a unique ID to the selected parks. This value will be used to join the parks to their buffers.Create a 1.2 mi (1,931 m) buffer ring around each park using the multiring buffer plugin in QGIS. Ensure that “dissolve buffers” is disabled so that a single 1.2 mi buffer is created for each park.Assess the amount of overlap between the buffered park and the Census urban area using overlap analysis. This step is necessary to identify parks that do not intersect the urban area, but which lie within an urban matrix. This step creates a table that is joined back to the park polygons using the UniqueID.Remove parks that had ≤2% overlap with the urban areas when buffered. This excludes mostly non-urban parks that do not meet the intent of this indicator to capture parks that provide nearby access for urban residents. Note: In the continental version of this indicator, we used a threshold of 10%. In the Caribbean version, we lowered this to 2% in order to capture small parks that dropped out of the indicator when we extended the buffer distance to 1.2 miles.Calculate the GIS acres of each remaining park unit using the Add Geometry Attributes function.Join the buffer attribute table to the previously selected parks, retaining only the parks that exceeded the 2% urban area overlap threshold while buffered. Buffer the selected parks by 15 m. Buffering prevents very small parks and narrow beaches from being left out of the indicator when the polygons are converted to raster.Reclassify the polygons into 7 classes, seen in the final indicator values below. These thresholds were informed by park classification guidelines from the National Recreation and Park Association, which classify neighborhood parks as 5-10 acres, community parks as 30-50 acres, and large urban parks as optimally 75+ acres (Mertes and Hall 1995).Export the final vector file to a shapefile and import to ArcGIS Pro.Convert the resulting polygons to raster using the ArcPy Polygon to Raster function. Assign values to the pixels in the resulting raster based on the polygon class sizes of the contiguous park areas.Clip to the Caribbean Blueprint 2023 subregion.As a final step, clip to the spatial extent of Southeast Blueprint 2023. Note: For more details on the mapping steps, code used to create this layer is available in the Southeast Blueprint Data Download under > 6_Code. Final indicator valuesIndicator values are assigned as follows:6 = 75+ acre urban park5 = >50 to <75 acre urban park4 = 30 to <50 acre urban park3 = 10 to <30 acre urban park2 = 5 to <10 acre urban park1 = <5 acre urban park0 = Not identified as an urban parkKnown IssuesThis indicator does not include park amenities that influence how well the park serves people and should not be the only tool used for parks and recreation planning. Park standards should be determined at a local level to account for various community issues, values, needs, and available resources. This indicator includes some protected areas that are not open to the public and not typically thought of as “parks”, like mitigation lands, private easements, and private golf courses. While we experimented with excluding them using the public access attribute in PAD, due to numerous inaccuracies, this inadvertently removed protected lands that are known to be publicly accessible. As a result, we erred on the side of including the non-publicly accessible lands.This indicator includes parks and beaches from OpenStreetMap, which is a crowdsourced dataset. While members of the OpenStreetMap community often verify map features to check for accuracy and completeness, there is the potential for spatial errors (e.g., misrepresenting the boundary of a park) or incorrect tags (e.g., labelling an area as a park that is not actually a park). However, using a crowdsourced dataset gives on-the-ground experts, Blueprint users, and community members the power to fix errors and add new parks to improve the accuracy and coverage of this indicator in the future.Other Things to Keep in MindThis indicator calculates the area of each park using the park polygons from the source data. However, simply converting those park polygons to raster results in some small parks and narrow beaches being left out of the indicator. To capture those areas, we buffered parks and beaches by 15 m and applied the original area calculation to the larger buffered polygon, so as not to inflate the area by including the buffer. As a result, when the buffered polygons are rasterized, the final indicator has some areas of adjacent pixels that receive different scores. While these pixels may appear to be part of one contiguous park or suite of parks, they are scored differently because the park polygons themselves are not actually contiguous. The Caribbean version of this indicator uses a slightly different methodology than the continental Southeast version. It includes parks within a 1.2 mi distance from the Census urban area, compared to 0.5 mi in the continental Southeast. We extended it to capture East Bay and Point Udall based on feedback from the local conservation community about the importance of the park for outdoor recreation. Similarly, this indicator uses a 2% threshold of overlap between buffered parks and the Census urban areas, compared to a 10% threshold in the continental Southeast. This helped capture small parks that dropped out of the indicator when we extended the buffer distance to 1.2 miles. Finally, the Caribbean version does not use the impervious surface cutoff applied in the continental Southeast because the landcover data available in the Caribbean does not assess percent impervious in a comparable way.Disclaimer: Comparing with Older Indicator VersionsThere are numerous problems with using Southeast Blueprint

Various data recorded by Historic England relating to aerial investigation and mapping projects. N.B. This is a dynamic dataset that is constantly evolving, not only with the addition of newly completed projects, but also with the reassessment of some earlier projects. See https://historicengland.org.uk/research/methods/airborne-remote-sensing/aerial-investigation/ for further details of Historic England's work with aerial sources. It's currently not possible to provide download access to the earlier hand drawn projects, which are only available as raster files, but these can be viewed via the Aerial Archaeology Mapping Explorer. We aim to create vector monument polygons for these features as the next phase of the project. More information and help with these the layers Detailed MappingThis layer shows the detailed mapping of archaeological features derived from aerial imagery; this includes photographic imagery from many decades taken specifically for archaeological purposes, as well as other photography taken for other reasons and airborne lidar. The data are symbolised initially based on their physical form i.e. cut/negative (e.g. pit, ditch etc) or built/positive (e.g. mound, bank etc) .Field nameField aliasDescriptionMandatory Y/NLAYERLAYERThe layer used for mappingYPROJECTPROJECTProject nameYPERIODPERIODThe presumed date/period assigned to the feature (terminology from FISH thesaurus)YMONUMENT_TYPEMONUMENT_TYPE The presumed type/function assigned to the feature (terminology from FISH thesaurus)YEVIDENCE_1EVIDENCE_1The primary evidence for the feature e.g. cropmark, earthwork etc (terminology from FISH thesaurus)YSOURCE_1SOURCE_1The primary source for the feature e.g. aerial photo reference, documentary source etcYEVIDENCE_2EVIDENCE_2Where available the latest evidence for the feature e.g. cropmark, earthwork etc (terminology from FISH thesaurus) N.B. This was the latest evidence seen and does not necessarily represent the current status of the feature.NSOURCE_2SOURCE_2Where available the latest source for the feature N.B. This was the latest evidence seen and does not necessarily represent the current status of the feature.NHE_UIDHE_UIDComposite of Unique identifier(s) used by Historic EnglandYHER_NOHER_NOComposite of Unique identifier(s) used by Historic Environment RecordsNDHEUID_1DHEUID_1Primary Unique identifier used by Historic EnglandYDHEUID_2DHEUID_2Secondary Unique identifier used by Historic England. Used where a feature may relate to more than one Historic England recordNDHEUID_3 ~ 5DHEUID_3 ~ 5Additional Unique identifier used by Historic England. Used where a feature may relate to more than one Historic England recordNHE_URL1HE_URL1URL link to the relevant Historic England record in Heritage GatewayYHE_URL2HE_URL2URL link to the relevant Historic England record in Heritage GatewayNHE_URL3 ~ 5HE_URL3 ~ 5URL link to the relevant Historic England record in Heritage GatewayNDHERNO_1DHERNO_1Primary unique identifier used by the relevant Historic Environment Record (HER)YDHERNO_2DHERNO_2Secondary unique identifier used by the relevant Historic Environment Record. Used where a feature may relate to more than one HER recordNDHERNO_3 ~ 5DHERNO_3 ~ 5Tertiary unique identifier used by the relevant Historic Environment Record. Used where a feature may relate to more than one HER recordNDHERPREF_1DHERPREF_1Primary alternative unique identifier used by the relevant Historic Environment Record. Some HERs use the same number for both the HER No. and the reference to link to the record; others use different numbers and give them different names e.g MonUIDYDHERPREF_2DHERPREF_2Secondary alternative unique identifier used by the relevant Historic Environment Record. Some HERs use the same number for both the HER No. and the reference to link to the record; others use different numbers and give them different names e.g MonUID Used where a feature may relate to more than one HER recordNDHERPREF_3 ~ 5DHERPREF_3 ~ 5Additional alternative unique identifier used by the relevant Historic Environment Record. Some HERs use the same number for both the HER No. and the reference to link to the record; others use different numbers and give them different names e.g MonUID Used where a feature may relate to more than one HER recordNHER_LINK_1HER_LINK_1URL link to the relevant Historic Environment Record (HER) record in Heritage Gateway YHER_LINK_2HER_LINK_2URL link to the relevant Historic Environment Record (HER) record in Heritage GatewayNHER_LINK_3 ~ 5HER_LINK_3 ~ 5URL link to the relevant Historic Environment Record (HER) record in Heritage GatewayNThe data are symbolised initially based on their physical form i.e. cut/negative (e.g. pit, ditch etc) or built/positive (e.g. mound, bank etc)Layer nameColour (Hex)DescriptionBank#A50026Used to outline banks, platforms, mounds and spoil heaps.Ditch#313695Used to outline cut features such as ditches, ponds, pits or hollow ways.Extent of Feature#FDAE61 (Dashes)Used to depict the extent of large area features such as airfields, military camps, or major extraction.Ridge and Furrow Alignment#74ADD1Line or arrow(s) (hand drawn not a symbol) depicting the direction of the rigs in a block of ridge and furrow.Ridge and Furrow Area#74ADD1 (Dots)Used to outline a block of ridge and furrow .Slope#4575B4The top of the “T” indicates the top of slope and the body indicates the length and direction of the slope. Used to depict scarps, edges of platforms and other large earthworks.Structure#F46D43Used to outline structures including stone, concrete, metal and timber constructions e.g., buildings, Nissen huts, tents, radio masts, camouflaged airfields, wrecks, fish traps, etc. You can find instructions on how to create a QGIS style file (.qml) to recreate our mapping symbology in QGIS via our Open Data Downloads page under Aerial Investigation Mapping data. Monument ExtentsThis layer shows the general extent of the monuments, created from multiple sources, primarily aerial imagery, but referring to other sources such as earthwork surveys, documentary evidence and any information available from the relevant Historic Environment Record etc. This differs from the 'Detailed Mapping' layer, which shows the individual features as they appear on the ground.Field nameField aliasDescriptionMandatory Y/NLAYERLAYERThe layer used for mappingYHE_UIDHE_UIDComposite of Unique identifier(s) used by Historic EnglandYHER_NOHER_NOComposite of Unique identifier(s) used by Historic Environment RecordsNHE_UID1HE_UID1Primary Unique identifier used by Historic EnglandYHE_UID2HE_UID2Secondary Unique identifier used by Historic England. Used where a feature may relate to more than one Historic England recordNHE_UID3 ~ 5HE-UID3 ~ 5Additional Unique identifier used by Historic England. Used where a feature may relate to more than one Historic England recordNHE_URL1HE_URL1URL link to the relevant Historic England record in Heritage GatewayYHE_URL2HE_URL2URL link to the relevant Historic England record in Heritage GatewayNHE_URL3 ~ 5HE_URL3 ~ 5URL link to the relevant Historic England record in Heritage GatewayNHERNO_1HERNO_1Primary unique identifier used by the relevant Historic Environment Record (HER)YHERNO_2HERNO_2Secondary unique identifier used by the relevant Historic Environment Record. Used where a feature may relate to more than one HER recordNHERNO_3 ~ 25HERNO_3 ~ 25Tertiary unique identifier used by the relevant Historic Environment Record. Used where a feature may relate to more than one HER recordNHERPREF_1HERPREF_1Primary alternative unique identifier used by the relevant Historic Environment Record. Some HERs use the same number for both the HER No. and the reference to link to the record; others use different numbers and give them different names e.g MonUIDYHERPREF_2HERPREF_2Secondary alternative unique identifier used by the relevant Historic Environment Record. Some HERs use the same number for both the HER No. and the reference to link to the record; others use different numbers and give them different names e.g MonUID Used where a feature may relate to more than one HER recordNHERPREF_3 ~ 25HERPREF_3 ~ 25Additional alternative unique identifier used by the relevant Historic Environment Record. Some HERs use the same number for both the HER No. and the reference to link to the record; others use different numbers and give them different names e.g MonUID Used where a feature may relate to more than one HER recordNHER_LINK_1HER_LINK_1URL link to the relevant Historic Environment Record (HER) record in Heritage GatewayYHER_LINK_2HER_LINK_2URL link to the relevant Historic Environment Record (HER) record in Heritage GatewayNHER_LINK_3 ~ 25HER_LINK_3 ~ 25URL link to the relevant Historic Environment Record (HER) record in Heritage GatewayNPROJECTprojectProject nameYProject AreaThis layer shows the extent of the various projects carried out by Historic England, it's predecessor bodies and other organisations grant aided by them. It shows the total extent of the project, irrespective of the various counties etc that might be covered. Field nameField aliasDescriptionMandatory Y/NLAYERLAYERThe layer used for mappingYTYPETYPEThe type of mapping carried out for the project e.g. Raster, Vector etcYDRAWFORMATDRAWFORMATThe form of mapping carried out for the project e.g. hand drawn, digitised etcYPROJECT_NAPROJECT_NAThe name of the projectYSTATUSSTATUSThe status of the project e.g. completed, ongoingYSOURCESSOURCESThe sources from which the mapping was derived for the project e.g. oblique aerial photographs, lidar etcYCOMPLETEDCOMPLETEDThe date for the completion of the projectYYEARYEARThe date for the completion of the projectYTEAMTEAMThe team that completed the projectYRRS_NoRRS_NoThe number of the research report relating to the project, where one existsNRRS_URLRRS_URLThe link to the research report relating to the project, where one existsN