Full details are in the download file "README_Dataset-SurvivalAntarcticBiota.md" Software and file formats used. All maps were created using the Antarctic GIS package 'Quantarctica' (https://www.qgis.org/en/site/about/case_studies/antarctica.html) in QGIS ver. 3.22.7. The ACBRs shown in figure 1 and Supplementary figures S1-S7 are included in an 'Environmental management' layer within Quantarctica and colours were chosen to match those used previously. For the land topography of Antarctica we used the shapefiles from 'Bedmachine' (downloaded from NSIDC, https://nsidc.org/data/nsidc-0756/versions/2) in QGIS ver. 3.22.7. Each input data file was saved as .csv files and imported individually into QGIS for: (1) all individual springtail occurrences (separated into each species), (2) geothermal sites (separated into large and small), (3) geochronological dated sites (separated into high refuge support, and low refuge support), and (4) eDNA signals of springtails. These data were then used to create figures 1 and 2 in the main manuscript, and for more detailed information in figures S1-S7 in Supplementary material. Compiled data accessibility. The .csv data files we used in QGIS for springtail records, geothermal and geochronological sites shown in figures 1 and 2 and figures S1-S7 are available at the Royal Society's figshare portal. We also include our QGIS file used to generate the supplementary figures (QGIS_suppl_figs.qgz) and the .qlr 'layer definition file' (All_layers_definition_QGIS.qlr) exported from QGIS, which can be imported into QGIS with Qantarctica along with Bedmachine, which maintains the symbols and colours we used in our figures.Funding provided by: Australian Research CouncilCrossref Funder Registry ID: http://dx.doi.org/10.13039/501100000923Award Number: SR200100005 Data collection. We focussed on ice-free terrain represented by 15 currently recognized Antarctic Conservation Biodiversity Regions (ACBRs); we do not include South Orkney Islands. We compiled all published occurrence records for all springtail species considered to be endemic or native from these 15 ACBRs and from our own unpublished records. We obtained the ten geothermal sites used in the analyses by Fraser et al. from their Table S6. We compiled the geochronological data from all known cosmogenic-nuclide data from Antarctica (https://www.ice-d.org/) and from publications that were used to scrutinise the datasets. Cosmogenic dating is uniquely suited to Antarctic environments, however, there are problematic samples and locations. We include a selection of cosmogenic datasets to represent sites that clearly (or potentially) delineate Last Glacial Maximum surface elevations, and reject datasets where results are inconclusive due to isotope inheritance or incomplete or inconclusive results. From the included datasets we divided cosmogenic sites into two categories based on the 100 km radius around each site (using the criteria from Fraser et al.): (1) those that showed unequivocal endemism; and (2) those where the provenance was equivocal. Setting these criteria, and using springtails as a proxy, was critical to identifying regions where glacial refuges for the vast majority of biota were most likely to have occurred. The origin of terrestrial biota in Antarctica has been debated since the discovery of springtails on the first historic voyages to the southern continent more than 120 years ago. A plausible explanation for the long-term persistence of life requiring ice-free land on continental Antarctica has, however, remained elusive. The default glacial eradication scenario has dominated because hypotheses to date have failed to provide a mechanism for their widespread survival on the continent, particularly through the Last Glacial Maximum when geological evidence demonstrates that the ice sheet was more extensive than present. Here, we provide support for the alternative nunatak refuge hypothesis – that ice-free terrain with sufficient relief above the ice sheet provided refuges and was a source for terrestrial biota found today. This hypothesis is supported here by an increased understanding from the combination of biological and geological evidence, and we outline a mechanism for these refuges during successive glacial maxima that also provides a source for coastal species. Our cross-disciplinary approach provides future directions to further test this hypothesis that will lead to new insights into the evolution of Antarctic landscapes and how they have shaped the biota through a changing climate.

This dataset shows the results of mapping the connectivity of key values (natural heritage, indigenous heritage, social and historic and economic) of the Great Barrier Reef with its neighbouring regions (Torres Strait, Coral Sea and Great Sandy Strait). The purpose of this mapping process was to identify values that need joint management across multiple regions. It contains a spreadsheet containing the connection information obtained from expert elicitation, all maps derived from this information and all GIS files needed to recreate these maps. This dataset contains the connection strength for 59 attributes of the values between 7 regions (GBR Far Northern, GBR Cairns-Cooktown, GBR Whitsunday-Townsville, GBR Mackay-Capricorn, Torres Strait, Coral Sea and Great Sandy Strait) based on expert opinion. Each connection is assessed based on its strength, mechanism and confidence. Where a connection was known to not exist between two regions then this was also explicitly recorded. A video tutorial on this dataset and its maps is available from https://vimeo.com/335053846.

Methods:

The information for the connectivity maps was gathered from experts (~30) during a 3-day workshop in August 2017. Experts were provided with a template containing a map of Queensland and the neighbouring seas, with an overlay of the regions of interest to assess the connectivity. These were Torres Strait, GBR:Far North Queensland, GBR:Cairns to Cooktown, GBC: Townsville to Whitsundays, GBR: Mackay to Capricorn Bunkers and Great Sandy Strait (which includes Hervey bay). A range of reference maps showing locations of the values were provided, where this information could be obtained. As well as the map the template provided 7x7 table for filling in the connectivity strength and connection type between all combinations of these regions. The experts self-organised into groups to discuss and complete the template for each attribute to be mapped. Each expert was asked to estimate the strength of connection between each region as well as the connection mechanism and their confidence in the information. Due to the limited workshop time the experts were asked to focus on initially recording the connections between the GBR and its neighbouring regions and not to worry about the internal connections in the GBR, or long-distance connections along the Queensland coast. In the second half of the workshop the experts were asked to review the maps created and expand on the connections to include those internal to the GBR. After the workshop an initial set of maps were produced and reviewed by the project team and a range of issues were identified and resolved. Additional connectivity maps for some attributes were prepared after the workshop by the subject experts within the project team. The data gathered from these templates was translated into a spreadsheet, then processing into the graphic maps using QGIS to present the connectivity information. The following are the value attributes where their connectivity was mapped: Seagrass meadows: pan-regional species (e.g. Halophila spp. and Halodule spp.) Seagrass meadows: tropical/sub-tropical (Cymodocea serrulata, Syringodium isoetifolium) Seagrass meadows: tropical (Thalassia, Cymodocea, Thalassodendron, Enhalus, Rotundata) Seagrass meadows: Zostera muelleri Mangroves & saltmarsh Hard corals Crustose coralline algae Macroalgae Crown of thorns starfish larval flow Acropora larval flow Casuarina equisetifolia & Pandanus tectorius Argusia argentia Pisonia grandis: cay vegetation Inter-reef gardens (sponges + gorgonians) (Incomplete) Halimeda Upwellings Pelagic foraging seabirds Inshore and offshore foraging seabirds Migratory shorebirds Ornate rock lobster Yellowfin tuna Black marlin Spanish mackerel Tiger shark Grey nurse shark Humpback whales Dugongs Green turtles Hawksbill turtles Loggerhead turtles Flatback turtles Longfin & Shortfin Eels Red-spot king prawn Brown tiger prawn Eastern king prawns Great White Shark Sandfish (H. scabra) Black teatfish (H. whitmaei) Location of sea country Tangible cultural resources Location of place attachment Location of historic shipwrecks Location of places of social significance Location of commercial fishing activity Location of recreational use Location of tourism destinations Australian blacktip shark (C. tilstoni) Barramundi Common black tip shark (C. limbatus) Dogtooth tuna Grey mackerel Mud crab Coral trout (Plectropomus laevis) Coral trout (Plectropomus leopardus) Red throat emperor Reef manta Saucer scallop (Ylistrum balloti) Bull shark Grey reef shark

Limitations of the data:

The connectivity information in this dataset is only rough in nature, capturing the interconnections between 7 regions. The connectivity data is based on expert elicitation and so is limited by the knowledge of the experts that were available for the workshop. In most cases the experts had sufficient knowledge to create robust maps. There were however some cases where the knowledge of the participants was limited, or the available scientific knowledge on the topic was limited (particularly for the ‘inter-reefal gardens’ attribute) or the exact meaning of the value attribute was poorly understood or could not be agreed up on (particularly for the social and indigenous heritage maps). This information was noted with the maps. These connectivity maps should be considered as an initial assessment of the connections between each of the regions and should not be used as authoritative maps without consulting with additional sources of information. Each of the connectivity links between regions was recorded with a level of confidence, however these were self-reported, and each assessment was performed relatively quickly, with little time for reflection or review of all the available evidence. It is likely that in many cases the experts tended to have a bias to mark links with strong confidence. During subsequent revisions of some maps there were substantial corrections and adjustments even for connections with a strong confidence, indicating that there could be significant errors in the maps where the experts were not available for subsequent revisions. Each of the maps were reviewed by several project team members with broad general knowledge. Not all connection combinations were captured in this process due to the limited expert time available. A focus was made on capturing the connections between the GBR and its neighbouring regions. Where additional time was available the connections within 4 regions in the GBR was also captured. The connectivity maps only show connections between immediately neighbouring regions, not far connections such as between Torres Strait and Great Sandy Strait. In some cases the connection information for longer distances was recorded from the experts but not used in the mapping process. The coastline polygon and the region boundaries in the maps are not spatially accurate. They were simplified to make the maps more diagrammatic. This was done to reduce the chance of misinterpreting the connection arrows on the map as being spatially explicit.

Format:

This dataset is made up of a spreadsheet that contains all the connectivity information recorded from the expert elicitation and all the GIS files needed to recreate the generated maps.

original/GBR_NESP-TWQ-3-3-3_Seascape-connectivity_Master_v2018-09-05.xlsx: ‘Values connectivity’: This sheet contains the raw connectivity codes transcribed from the templates produced prepared by the subject experts. This is the master copy of the connection information. Subsequent sheets in the spreadsheet are derived using formulas from this table. 1-Vertical-data: This is a transformation of the ‘Values connectivity’ sheet so that each source and destination connection is represented as a single row. This also has the connection mechanism codes split into individual columns to allow easier processing in the map generation. This sheet pulls in the spatial information for the arrows on the maps (‘LinkGeom’ attribute) or crosses that represent no connections (‘NoLinkGeom’) using lookup tables from the ‘Arrow-Geom-LUT’ and ‘NoConnection-Geom-LUT’ sheets. 2.Point-extract: This contains all the ‘no connection’ points from the ‘Values connectivity’ dataset. This was saved as working/ GBR_NESP-TWQ-3-3-3_Seascape-connectivity_no-con-pt.csv and used by the QGIS maps to draw all the crosses on the maps. This table is created by copy and pasting (values only) the ‘1-Vertical-data’ sheet when the ‘NoLinkGeom’ attribute is used to filter out all line features, by unchecking blank rows in the ‘NoLinkGeom’ filter. 2.Line-extract: This contains all the ‘connections’ between regions from the ‘Values connectivity’ dataset. This was saved as working/GBR_NESP-TWQ-3-3-3_Seascape-connectivity_arrows.csv and used by the QGIS maps to draw all the arrows on the maps. This table is created by copy and pasting (values only) the ‘1-Vertical-data’ sheet when the ‘LinkGeom’ attribute is used to filter out all point features, by unchecking blank rows in the ‘LinkGeom’ filter. Map-Atlas-Settings: This contains the metadata for each of the maps generated by QGIS. This sheet was exported as working/GBR_NESP-TWQ-3-3-3_Seascape-connectivity_map-atlas-settings.csv and used by QGIS to drive its Atlas feature to generate one map per row of this table. The AttribID is used to enable and disable the appropriate connections on the map being generated. The WKT attribute (Well Known Text) determines the bounding box of the map to be generated and the other attributes are used to display text on the map. map-image-metadata: This table contains metadata descriptions for each of the value attribute maps. This metadata was exported as a CSV and saved into the final generated JPEG maps using the eAtlas Image Metadata Editor Application

The Digital Geologic-GIS Map of Yosemite National Park and Vicinity, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (yose_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (yose_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (yose_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (yose_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (yose_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (yose_geology_metadata_faq.pdf). Please read the yose_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and California Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (yose_geology_metadata.txt or yose_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

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 %)

Georeferenced (to WGS1984) and cropped set of about 820 historic maps of Burma at a scale of 1 inch per mile (63,360) covering about 75% of the country. Those topographic maps, originally produced and published by the Great Trigonometrical Survey of India between 1899 and 1946, have been scanned and shared with the public as part of the "Old Survey Of India Maps” Community under a CC BY 4.0 International Licence. Many of these maps are reprints of earlier maps produced before the war. Most mapsheets are early editions (edition 1 or edition 2).

Each of the 820 map sheet scans was georeferenced using the Latitude-Longitude corner coordinates in Everest 1830 projection. Those map sheets were cropped, keeping only the map area - to allow a seamless mosaic without the mapframe overlapping adjacent map sheets when several map sheets are put together in a GIS. Those cropped map sheets were projected from Everest 1830 to WGS1984 (EPSG4326) - standard GPS - projection to make them easier to use and combine with other GIS data.

Those map sheets can be loaded directly in any GIS such as QGIS or ESRI ArcGIS as well as Google Earth.

• The mm_OI_JBv2024 folder contains the cropped end georeferenced map sheets in jpg-format as well as accompagning georeference and metadata incl.
  
  • The mm_OI_JBv2024_kmlLinks contains kml files to easily load the mapsheets into Google Earth
  • The mm_historicOI_EPSG4326.gdb contains an ESRI mosaic dataset to easily load all mapsheets into ArcGIS
• The mm_OI_JBv2024_scanMaps folder contains the uncropped original map scans (renamed though) in jpg-format.
• The mm_topoOI_JBv7_masterlist.xlsx is a masterlist cataloguing all map sheets for easier use and matching them with the original source files as shared as part of the "Old Survey Of India Maps" (e.g. to identify new mapsheets should new maps be released)
• The indexMaps folder contains small scale index maps to locate the map sheets using their map sheet Grid-Letter-nomenclature

All georeferenced map scans are based on maps shared by John Brown via Zenodo

• https://zenodo.org/records/8040798 (63k Maps of Burma, version 7, Published June 14, 2023)
• https://zenodo.org/records/10463372 (63k Maps of Burma--additional 1--20240105, version 1, Published January 5, 2024)

The file naming convention is to first give the number of the 4 degree x 4 degree block followed by the letter (A to P) of the sixteen 1 degree x 1 degree blocks in each 4 degree block eg. 38 D, and this is followed by a number from 1 to 16 to indicate the number of the map in the 1 degree block.

This Number Letter Number designation is followed by the map series type either OI (contains a LCC grid) or OILatLon (only has a Lat-Lon grid), followed by the edition and year of the edition, followed by the date of publication/print. If the information is not available an "X" (for edition) or "0000" (for an unknown year) is used. A best-guess approach was used if the edition and print year and version information was ambiguous.

The files as shared via the "Old Survey Of India Maps" have been renamed to standardize the file naming, sometimes correcting them and to make them unique in the case several editions of the same map sheet were available.

A topographical index produced by the Survey of India is provided to assist the viewer in selecting a particular map of interest.