The "Map Imager Layer - Administrative Boundaries" is a Map Image Layer of Administrative Boundaries. It has been designed specifically for use in ArcGIS Online (and will not directly work in ArcMap or ArcPro). This data has been modified from the original source data to serve a specific business purpose. This data is for cartographic purposes only.The Administrative Boundaries Data Group contains the following layers: Populated Places (USGS)US Census Urbanized Areas and Urban Clusters (USCB)US Census Minor Civil Divisions (USCB)PLSS Townships (MnDNR, MnGeo)Counties (USCB)American Indian, Alaska Native, Native Hawaiian (AIANNH) Areas (USCB)States (USCB)Countries (MPCA)These datasets have not been optimized for fast display (but rather they maintain their original shape/precision), therefore it is recommend that filtering is used to show only the features of interest. For more information about using filters please see "Work with map layers: Apply Filters": https://doc.arcgis.com/en/arcgis-online/create-maps/apply-filters.htmFor additional information about the Administrative Boundary Dataset please see:United States Census Bureau TIGER/Line Shapefiles and TIGER/Line Files Technical Documentation: https://www.census.gov/programs-surveys/geography/technical-documentation/complete-technical-documentation/tiger-geo-line.htmlUnited States Census Bureau Census Mapping Files: https://www.census.gov/geographies/mapping-files.htmlUnited States Census Bureau TIGER/Line Shapefiles: https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html and https://www.census.gov/cgi-bin/geo/shapefiles/index.php

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a format usable in a geographic information system (GIS) by employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM), Zone 16, using the North American Datum of 1983 (NAD83). Orthorectify: We orthorectified the interpreted overlays by using OrthoMapper, a softcopy photogrammetric software for GIS. One function of OrthoMapper is to create orthorectified imagery from scanned and unrectified imagery (Image Processing Software, Inc., 2002). The software features a method of visual orientation involving a point-and-click operation that uses existing orthorectified horizontal and vertical base maps. Of primary importance to us, OrthoMapper also has the capability to orthorectify the photointerpreted overlays of each photograph based on the reference information provided. Digitize: To produce a polygon vector layer for use in ArcGIS (Environmental Systems Research Institute [ESRI], Redlands, California), we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format by using ArcGIS. In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map-attribute codes (both map-class codes and physiognomic modifier codes) to the polygons and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer. Geodatabase: At this stage, the map layer has only map-attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

This data set contains high-resolution QuickBird imagery and geospatial data for the entire Barrow QuickBird image area (156.15° W - 157.07° W, 71.15° N - 71.41° N) and Barrow B4 Quadrangle (156.29° W - 156.89° W, 71.25° N - 71.40° N), for use in Geographic Information Systems (GIS) and remote sensing software. The original QuickBird data sets were acquired by DigitalGlobe from 1 to 2 August 2002, and consist of orthorectified satellite imagery. Federal Geographic Data Committee (FGDC)-compliant metadata for all value-added data sets are provided in text, HTML, and XML formats. Accessory layers include: 1:250,000- and 1:63,360-scale USGS Digital Raster Graphic (DRG) mosaic images (GeoTIFF format); 1:250,000- and 1:63,360-scale USGS quadrangle index maps (ESRI Shapefile format); an index map for the 62 QuickBird tiles (ESRI Shapefile format); and a simple polygon layer of the extent of the Barrow QuickBird image area and the Barrow B4 quadrangle area (ESRI Shapefile format). Unmodified QuickBird data comprise 62 data tiles in Universal Transverse Mercator (UTM) Zone 4 in GeoTIFF format. Standard release files describing the QuickBird data are included, along with the DigitalGlobe license agreement and product handbooks. The baseline geospatial data support education, outreach, and multi-disciplinary research of environmental change in Barrow, which is an area of focused scientific interest. Data are provided on four DVDs. This product is available only to investigators funded specifically from the National Science Foundation (NSF), Office of Polar Programs (OPP), Arctic Sciences Section. An NSF OPP award number must be provided when ordering this data.

Map Image Layer de la GDB Replica cartografia, que contiene los shapefile de:sigparques.cartografia.COBE2002SPNN100K = Coberturas 2002sigparques.cartografia.COBE2007SPNN100K = Coberturas 2007sigparques.cartografia.COBE2012SPNN100K = Coberturas 2012sigparques.cartografia.COBE2015SPNN100K = Coberturas 2015sigparques.cartografia.COBE2017SPNN100K = Coberturas 2017sigparques.cartografia.COBE2018SPNN100K = Coberturas 2018sigparques.cartografia.COBE2020SPNN100K = Coberturas 2020Capa con la multitemporalidad de la capa de coberturas a escala 1:100.000. Información disponible para los años 2002, 2007, 2012, 2015, 2017, 2018 y 2020. Para un mayor rendimiento en el despliegue de la información, contiene el feature class de coberturas más la información atributiva en formato tabla. Esta información es producida por Parques Nacionales Naturales de Colombia, por el equipo de Sensores Remotos del Grupo de Gestión del Conocimiento y la Innovación.Estos shapefile hacen parte del Feature Dataset

This dataset contains files created, digitized, or georeferenced by Chris DeRolph for mapping the pre-urban renewal community within the boundaries of the Riverfront-Willow St. and Mountain View urban renewal projects in Knoxville TN. Detailed occupant information for properties within boundaries of these two urban renewal projects was extracted from the 1953 Knoxville City Directory. The year 1953 was chosen as a representative snapshot of the Black community before urban renewal projects were implemented. The first urban renewal project to be approved was the Riverfront-Willow Street project, which was approved in 1954 according to the University of Richmond Renewing Inequality project titled ‘Family Displacements through Urban Renewal, 1950-1966’ (link below in the 'Other shapefiles' section). For ArcGIS Online users, the shapefile and tiff layers are available in AGOL and can be found by clicking the ellipsis next to the layer name and selecting 'Show item details' for the layers in this webmap https://knoxatlas.maps.arcgis.com/apps/webappviewer/index.html?id=43a66c3cfcde4f5f8e7ab13af9bbcebecityDirectory1953 is a folder that contains:JPG images of 1953 City Directory for street segments within the urban renewal project boundaries; images collected at the McClung Historical CollectionTXT files of extracted text from each image that was used to join occupant information from directory to GIS address datashp is a folder that contains the following shapefiles:Residential:Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and property ownersBlack_rented_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and non-owners of the propertyNon_Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as property owners that were not listed as BlackNon_Black_rented_residential_1953.shp: residential entries in the 1953 City Directory not listed as Black or property ownersResidential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposeslastName: occupant's last namelabelShort: combines the Number and lastName fields for map labeling purposesNon-residential:Black_nonResidential_1953.shp: non-residential entries in the 1953 City Directory listed as Black-occupiedNonBlack_nonResidential_1953.shp: non-residential entries in the 1953 City Directory not listed as Black-occupiedNon-residential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationNAICS6: 2022 North American Industry Classification System (NAICS) six-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS6title: NAICS6 title/short descriptionNAICS3: 2022 North American Industry Classification System (NAICS) three-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS3title: NAICS3 title/short descriptionflag: flags whether the occupant is part of the public sector or an NGO; a flag of '0' indicates the occupant is assumed to be a privately-owned businessrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposesOther shapefiles:razedArea_1972.shp: approximate area that appears to have been razed during urban renewal based on visual overlay of usgsImage_grayscale_1956.tif and usgsImage_colorinfrared_1972.tif; digitized by Chris DeRolphroadNetwork_preUrbanRenewal.shp: road network present in urban renewal area before razing occurred; removed attribute indicates whether road was removed or remains today; historically removed roads were digitized by Chris DeRolph; remaining roads sourced from TDOT GIS roads dataTheBottom.shp: the approximate extent of the razed neighborhood known as The Bottom; digitized by Chris DeRolphUrbanRenewalProjects.shp: boundaries of the East Knoxville urban renewal projects, as mapped by the University of Richmond's Digital Scholarship Lab https://dsl.richmond.edu/panorama/renewal/#view=0/0/1&viz=cartogram&city=knoxvilleTN&loc=15/35.9700/-83.9080tiff is a folder that contains the following images:streetMap_1952.tif: relevant section of 1952 map 'Knoxville Tennessee and Surrounding Area'; copyright by J.U.G. Rich and East Tenn Auto Club; drawn by R.G. Austin; full map accessed at McClung Historical Collection, 601 S Gay St, Knoxville, TN 37902; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphnewsSentinelRdMap_1958.tif: urban renewal area map from 1958 Knox News Sentinel article; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphusgsImage_grayscale_1956.tif: May 18, 1956 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/ARA550590030582/usgsImage_colorinfrared_1972.tif: April 18, 1972 color infrared USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR6197002600096/usgsImage_grayscale_1976.tif: November 8, 1976 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR1VDUT00390010/

Esta capa corresponde a la multitemporalidad P1 - P2 de las coberturas de la tierra a escala 1:100.000. Es producida por el equipo de Sensores Remotos del Grupo de Gestión del Conocimiento (GGCI) y la Innovación de Parques Nacionales Naturales de Colombia. Para una mayor rápidez en el despliegue de los datos se encuentra la información atributiva publicada como una tabla.Map Image Layer de la GDB Replica cartografia, que contiene el feature class:

This line shapefile represents division line boundaries in Sri Lanka. The Global Map Sri Lanka version 2 was developed based on Global Map Specifications version 2.2. The data source of Boundary layer was a 1:250,000 map image made in 2012. The data source of Drainage was a 1:250,000 map image made in 1996 and 2008.Only capital area is updated from ALOS stellite images of 2010-2011. The data source of Population Center layer was a 1:250,000 map image made in 1996 and 2008. The data source of Transportation layer was a 1:250,000 map image made in 2012. Only capital area is updated from ALOS stellite images of 2010-2011.

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.

This line shapefile represents the coastline in Sri Lanka. The Global Map Sri Lanka version 2 was developed based on Global Map Specifications version 2.2. The data source of Boundary layer was a 1:250,000 map image made in 2012. The data source of Drainage was a 1:250,000 map image made in 1996 and 2008.Only capital area is updated from ALOS stellite images of 2010-2011. The data source of Population Center layer was a 1:250,000 map image made in 1996 and 2008. The data source of Transportation layer was a 1:250,000 map image made in 2012. Only capital area is updated from ALOS stellite images of 2010-2011.

This line shapefile represents roads in Albania. The Global Map Albania version 2 was developed based on Global Map Specifications version 2.2. The source data of vector layers were a Digital Map 1:25000 and Orthophoto, map image made in 1985 and orthophoto made in 2008. The data source of Elevation layer was developed using orthophoto 2000 year. The data source of Land Use and Vegetation layer were developed using orthophoto 2012 year. IRS, SPOT and RapidEye satellite images, dual coverage, orthophotos (2012), topographic maps for making Land Cover.

Abstract

This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied.

This dataset was sourced from the Queensland Department of Natural Resources and Mines in 2012. Information provided by the Department describes the dataset as follows:

This data was originally provided on DVD and contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology and structural framework map. The maps were done in ArcGIS 9.3.1 and the data stored in file geodatabases, topology created and validated. This provides greater data quality by performing topological validation on the feature's spatial relationships. For the purposes of the DVD, shapefiles were created from the file geodatabases and for MapInfo users MapInfo .tab and .wor files. The shapefiles on the DVD are a revision of the 1975 Queensland geology data, and are both are available for display, query and download on the department's online GIS application.

The Queensland geology map is a digital representation of the distribution or extent of geological units within Queensland. In the GIS, polygons have a range of attributes including unit name, type of unit, age, lithological description, dominant rock type, and an abbreviated symbol for use in labelling the polygons. The lines in this dataset are a digital representation of the position of the boundaries of geological units and other linear features such as faults and folds. The lines are attributed with a description of the type of line represented. Approximately 2000 rock units were grouped into the 250 map units in this data set. The digital data was generalised and simplified from the Department's detailed geological data and was captured at 1:500 000 scale for output at 1:2 000 000 scale.

In the ESRI version, a layer file is provided which presents the units in the colours and patterns used on the printed hard copy map. For Map Info users, a simplified colour palette is provided without patterns. However a georeferenced image of the hard copy map is included and can be displayed as a background in both Arc Map and Map Info.

The geological framework of Queensland is classified by structural or tectonic unit (provinces and basins) in which the rocks formed. These are referred to as basins (or in some cases troughs and depressions) where the original form and structure are still apparent. Provinces (and subprovinces) are generally older basins that have been strongly tectonised and/or metamorphosed so that the original basin extent and form are no longer preserved. Note that intrusive and some related volcanic rocks that overlap these provinces and basins have not been included in this classification. The map was compiled using boundaries modified and generalised from the 1:2 000 000 Queensland Geology map (2012). Outlines of subsurface basins are also shown and these are based on data and published interpretations from petroleum exploration and geophysical surveys (seismic, gravity and magnetics).

For the structural framework dataset, two versions are provided. In QLD_STRUCTURAL_FRAMEWORK, polygons are tagged with the name of the surface structural unit, and names of underlying units are imbedded in a text string in the HIERARCHY field. In QLD_STRUCTURAL_FRAMEWORK_MULTI_POLYS, the data is structured into a series of overlapping, multi-part polygons, one for each structural unit. Two layer files are provided with the ESRI data, one where units are symbolised by name. Because the dataset has been designed for units display in the order of superposition, this layer file assigns colours to the units that occur at the surface with concealed units being left uncoloured. Another layer file symbolises them by the orogen of which they are part. A similar set of palettes has been provided for Map Info.

Dataset History

Details on the source data can be found in the xml file associated with data layer.

Data in this release

*ESRI.shp and MapInfo .tab files of rock unit polygons and lines with associated layer attributes of Queensland geology

*ESRI.shp and MapInfo .tab files of structural unit polygons and lines with associated layer attributes of structural framework

*ArcMap .mxd and .lyr files and MapInfo .wor files containing symbology

*Georeferenced Queensland geology map, gravity and magnetic images

*Queensland geology map, structural framework and schematic diagram PDF files

*Data supplied in geographical coordinates (latitude/longitude) based on Geocentric Datum of Australia - GDA94

Accessing the data

Programs exist for the viewing and manipulation of the digital spatial data contained on this DVD. Accessing the digital datasets will require GIS software. The following GIS viewers can be downloaded from the internet. ESRI ArcExplorer can be found by a search of www.esriaustralia.com.au and MapInfo ProViewer by a search on www.pbinsight.com.au collectively ("the websites").

Metadata

Metadata is contained in .htm files placed in the root folder of each vector data folder. For ArcMap users metadata for viewing in ArcCatalog is held in an .xml file with each shapefile within the ESRI Shapefile folders.

Disclaimer

The State of Queensland is not responsible for the privacy practices or the content of the websites and makes no statements, representations, or warranties about the content or accuracy or completeness of, any information or products contained on the websites.

Despite our best efforts, the State of Queensland makes no warranties that the information or products available on the websites are free from infection by computer viruses or other contamination.

The State of Queensland disclaims all responsibility and all liability (including without limitation, liability in negligence) for all expenses, losses, damages and costs you might incur as a result of accessing the websites or using the products available on the websites in any way, and for any reason.

The State of Queensland has included the websites in this document as an information source only. The State of Queensland does not promote or endorse the websites or the programs contained on them in any way.

WARNING: The Queensland Government and the Department of Natural Resources and Mines accept no liability for and give no undertakings, guarantees or warranties concerning the accuracy, completeness or fitness for the purposes of the information provided. The consumer must take all responsible steps to protect the data from unauthorised use, reproduction, distribution or publication by other parties.

Please view the 'readme.html' and 'licence.html' file for further, more complete information

Dataset Citation

Geological Survey of Queensland (2012) Queensland geology and structural framework - GIS data July 2012. Bioregional Assessment Source Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/69da6301-04c1-4993-93c1-4673f3e22762.

This layer is a high-resolution tree canopy change-detection layer for Baltimore City, MD. It contains three tree-canopy classes for the period 2007-2015: (1) No Change; (2) Gain; and (3) Loss. It was created by extracting tree canopy from existing high-resolution land-cover maps for 2007 and 2015 and then comparing the mapped trees directly. Tree canopy that existed during both time periods was assigned to the No Change category while trees removed by development, storms, or disease were assigned to the Loss class. Trees planted during the interval were assigned to the Gain category, as were the edges of existing trees that expanded noticeably. Direct comparison was possible because both the 2007 and 2015 maps were created using object-based image analysis (OBIA) and included similar source datasets (LiDAR-derived surface models, multispectral imagery, and thematic GIS inputs). OBIA systems work by grouping pixels into meaningful objects based on their spectral and spatial properties, while taking into account boundaries imposed by existing vector datasets. Within the OBIA environment a rule-based expert system was designed to effectively mimic the process of manual image analysis by incorporating the elements of image interpretation (color/tone, texture, pattern, location, size, and shape) into the classification process. A series of morphological procedures were employed to insure that the end product is both accurate and cartographically pleasing. No accuracy assessment was conducted, but the dataset will be subjected to manual review and correction. 2006 LiDAR and 2014 LiDAR data was also used to assist in tree canopy change.

The seamless, county-wide parcel layer was digitized from official Assessor Parcel (AP) Maps which were originally maintained on mylar sheets and/or maintained as individual Computer Aided Design (CAD) drawing files (e.g., DWG). The CRA office continues to maintain the official AP Maps in CAD drawings and Information Systems Department/Geographic Information Systems (ISD/GIS) staff apply updates from these maps to the seamless parcel base in the County’s Enterprise GIS. This layer is a partial view of the Information Sales System (ISS) extract, a report of property characteristics taken from the County’s Megabyte Property Tax System (MPTS). This layer may be missing some attributes (e.g., Owner Name) which may not be published to the Internet due to privacy conditions under the California Public Records Act (CPRA). Please contact the Clerk-Recorder-Assessor (CRA) office at (707) 565-1888 for information on availability, associated fees, and access to other versions of Sonoma County parcels containing additional property characteristics.The seamless parcel layer is updated and published to the Internet on a monthly basis.The seamless parcel layer was developed from the source data using the general methodology outlined below. The mylar sheets were scanned and saved to standard image file format (e.g., TIFF). The individual scanned maps or CAD drawing files were imported into GIS software and geo-referenced to their corresponding real-world locations using high resolution orthophotography as control. The standard approach was to rescale and rotate the scanned drawing (or CAD file) to match the general location on the orthophotograph. Then, appropriate control points were selected to register and rectify features on the scanned map (or CAD drawing file) to the orthophotography. In the process, features in the scanned map (or CAD drawing file) were transformed to real-world coordinates, and line features were created using “heads-up digitizing” and stored in new GIS feature classes. Recommended industry best practices were followed to minimize root mean square (RMS) error in the transformation of the data, and to ensure the integrity of the overall pattern of each AP map relative to neighboring pages. Where available Coordinate Geometry (COGO) & survey data, tied to global positioning systems (GPS) coordinates, were also referenced and input to improve the fit and absolute location of each page. The vector lines were then assembled into a polygon features, with each polygon being assigned a unique identifier, the Assessor Parcel Number (APN). The APN field in the parcel table was joined to the corresponding APN field in the assessor property characteristics table extracted from the MPTS database to create the final parcel layer. The result is a seamless parcel land base, each parcel polygon coded with a unique APN, assembled from approximately 6,000 individual map page of varying scale and accuracy, but ensuring the correct topology of each feature within the whole (i.e., no gaps or overlaps). The accuracy and quality of the parcels varies depending on the source. See the fields RANK and DESCRIPTION fields below for information on the fit assessment for each source page. These data should be used only for general reference and planning purposes. It is important to note that while these data were generated from authoritative public records, and checked for quality assurance, they do not provide survey-quality spatial accuracy and should NOT be used to interpret the true location of individual property boundary lines. Please contact the Sonoma County CRA and/or a licensed land surveyor before making a business decision that involves official boundary descriptions.

GIS (shapefile) boundary of areas damaged by fire following the 1906 earthquake.

This layer was digitized from a raster image of the historic paper map entitled "San Francisco, California, showing the areas destroyed by fire, April 18-21, 1906". The paper map was published by R.J. Waters & Co. in 1906. Scale [ca. 1:21,000]. Raster map downloaded from the Harvard Map Collection, Harvard College Library, Cambridge, Massachusetts: http://ids.lib.harvard.edu/ids/view/7271039?buttons=y

This map features Africa Land Cover at 30m resolution from MDAUS BaseVue 2013, referencing the World Land Cover 30m BaseVue 2013 layer.Land cover data represent a descriptive thematic surface for characteristics of the land's surface such as densities or types of developed areas, agricultural lands, and natural vegetation regimes. Land cover data are the result of a model, so a good way to think of the values in each cell are as the predominating value rather than the only characteristic in that cell.Land use and land cover data are critical and fundamental for environmental monitoring, planning, and assessment.Dataset SummaryBaseVue 2013 is a commercial global, land use / land cover (LULC) product developed by MDA. BaseVue covers the Earth’s entire land area, excluding Antarctica. BaseVue is independently derived from roughly 9,200 Landsat 8 images and is the highest spatial resolution (30m), most current LULC product available. The capture dates for the Landsat 8 imagery range from April 11, 2013 to June 29, 2014. The following 16 classes of land use / land cover are listed by their cell value in this layer: Deciduous Forest: Trees > 3 meters in height, canopy closure >35% (<25% inter-mixture with evergreen species) that seasonally lose their leaves, except Larch.Evergreen Forest: Trees >3 meters in height, canopy closure >35% (<25% inter-mixture with deciduous species), of species that do not lose leaves. (will include coniferous Larch regardless of deciduous nature).Shrub/Scrub: Woody vegetation <3 meters in height, > 10% ground cover. Only collect >30% ground cover.Grassland: Herbaceous grasses, > 10% cover, including pasture lands. Only collect >30% cover.Barren or Minimal Vegetation: Land with minimal vegetation (<10%) including rock, sand, clay, beaches, quarries, strip mines, and gravel pits. Salt flats, playas, and non-tidal mud flats are also included when not inundated with water.Not Used (in other MDA products 6 represents urban areas or built up areas, which have been split here in into values 20 and 21).Agriculture, General: Cultivated crop landsAgriculture, Paddy: Crop lands characterized by inundation for a substantial portion of the growing seasonWetland: Areas where the water table is at or near the surface for a substantial portion of the growing season, including herbaceous and woody species (except mangrove species)Mangrove: Coastal (tropical wetlands) dominated by Mangrove speciesWater: All water bodies greater than 0.08 hectares (1 LS pixel) including oceans, lakes, ponds, rivers, and streamsIce / Snow: Land areas covered permanently or nearly permanent with ice or snowClouds: Areas where no land cover interpretation is possible due to obstruction from clouds, cloud shadows, smoke, haze, or satellite malfunctionWoody Wetlands: Areas where forest or shrubland vegetation accounts for greater than 20% of vegetative cover and the soil or substrate periodically is saturated with, or covered by water. Only used within the continental U.S.Mixed Forest: Areas dominated by trees generally greater than 5 meters tall, and greater than 20% of total vegetation cover. Neither deciduous nor evergreen species are greater than 75% of total tree cover. Only used within the continental U.S.Not UsedNot UsedNot UsedNot UsedHigh Density Urban: Areas with over 70% of constructed materials that are a minimum of 60 meters wide (asphalt, concrete, buildings, etc.). Includes residential areas with a mixture of constructed materials and vegetation where constructed materials account for >60%. Commercial, industrial, and transportation i.e., Train stations, airports, etc.Medium-Low Density Urban: Areas with 30%-70% of constructed materials that are a minimum of 60 meters wide (asphalt, concrete, buildings, etc.). Includes residential areas with a mixture of constructed materials and vegetation, where constructed materials account for greater than 40%. Commercial, industrial, and transportation i.e., Train stations, airports, etc.MDA updated the underlying data in late 2016 and this service was updated in February 2017. An improved selection of cloud-free images was used to produce the update, resulting in improvement of classification quality to 80% of the tiles for this service.What can you do with this layer?This layer can be used to create maps and to visualize the underlying data across the ArcGIS platform. It can also be used as an analytic input in ArcMap and ArcGIS Pro.This layer has query, identify, and export image services available. The layer is restricted to an 16,000 x 16,000 pixel limit, which represents an area of nearly 300 miles on a side. This layer is part of a larger collection of landscape layers that you can use to perform a wide variety of mapping and analysis tasks.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. The WHSA vegetation map was developed using a combined strategy of automated digital image classification and direct analog image interpretation of aerial photography and satellite imagery. Initially, the aerial photography and satellite imagery were processed and entered into a GIS along with ancillary spatial layers. A working map legend of ecologically based vegetation map units was developed using the vegetation classification described in the report as the foundation. The intent was to develop map units that targeted the plant-association level wherever possible within the constraints of image quality, information content, and resolution. With the provisional legend and ground-control points provided by the field-plot data (the same data used to develop the vegetation classification), a combination of heads-up screen digitizing of polygons based on image interpretation and supervised image classifications were conducted. The outcome was a vegetation map composed of a suite of map units defined by plant associations and represented by sets of mapped polygons with similar spectral and site characteristics.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. The vegetation map for Pecos National Historical Park was developed using a combined strategy of automated digital-image classification and direct analog-image interpretation of aerial photography and satellite imagery. Initially, the aerial photography and satellite imagery were processed and entered into a GIS along with ancillary spatial layers. A working legend of ecologically based vegetation map units was developed using the vegetation classification described in Chapter 2 as the foundation. The intent was to develop map units that targeted the plant-association level wherever possible within the constraints of image quality, information content, and resolution. With the provisional legend and ground-control points provided by the field-plot data (the same data used to develop the vegetation classification), a series of automated image segmentation and supervised image classifications were conducted, followed by fine-scale map refinement using direct image interpretation and manual editing. The outcome was a vegetation map composed of a suite of map units defined by plant associations and represented by sets of mapped polygons with similar spectral and physical characteristics

Map Image Layer de la GDB Replica cartografia, que contiene los shapefile de:sigparques.cartografia.COBE2002SPNN100K = Coberturas 2002sigparques.cartografia.COBE2007SPNN100K = Coberturas 2007sigparques.cartografia.COBE2012SPNN100K = Coberturas 2012sigparques.cartografia.COBE2015SPNN100K = Coberturas 2015sigparques.cartografia.COBE2017SPNN100K = Coberturas 2017sigparques.cartografia.COBE2018SPNN100K = Coberturas 2018sigparques.cartografia.COBE2020SPNN100K = Coberturas 2020Capa con la multitemporalidad de la capa de coberturas a escala 1:100.000. Información disponible para los años 2002, 2007, 2012, 2015, 2017, 2018 y 2020. Para un mayor rendimiento en el despliegue de la información, contiene el feature class de coberturas más la información atributiva en formato tabla. Esta información es producida por Parques Nacionales Naturales de Colombia, por el equipo de Sensores Remotos del Grupo de Gestión del Conocimiento y la Innovación.Estos shapefile hacen parte del Feature Dataset

Notice: this is not the latest Heat Island Anomalies image service.This layer contains the relative degrees Fahrenheit difference between any given pixel and the mean heat value for the city in which it is located, for every city in the contiguous United States, Alaska, Hawaii, and Puerto Rico. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2022, with patching from summer of 2021 where necessary.Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter or cooler than the average temperature for that same city as a whole. This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at The Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so The Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). The Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.

This dataset consists of a shapefile of the reefs, islands, sand banks, cays and rocks of the whole Great Barrier Reef (GBR) including Torres Strait. This dataset is an extension of the mapping in the GBR Marine Park to include Torres Strait. The Torres Strait region was mapped at a scale of 1:50,000 (Lawrey, E. P., Stewart M., 2016) and these new features are referred to as the "Torres Strait Reef and Island Features" dataset.

The Complete GBR Reef and Island Features dataset integrates the "Torres Strait Reef and Island Features" dataset with the existing "GBR Features" (Great Barrier Reef Marine Park Authority, 2007) to create a single composite dataset of the whole Great Barrier Reef. This dataset includes 9600 features overall with 5685 from the "GBR Features" dataset and 3927 from the "Torres Strait Reef and Island Features" dataset.

These two datasets can be easily separated if necessary based on the "DATASET" attribute.

All new mapped features in Torres Strait were allocated permanent IDs (such as 10-479 for Thursday Island and 09-246 for Mabuiag Reef). These IDs are for easy unambiguous communication of features, especially for unnamed features.

The reference imagery used for the mapping of the reefs is available on request as it is large (~45 GB). These files are saved in the eAtlas enduring repository.

Methods:

This project mapped Torres Strait using a combination of existing island datasets as well as a semi-automated and manual digitising of marine features (reefs and sand banks) from the latest aerial and satellite imagery. No features were added to the dataset without confirmed evidence of their existence and position from at least two satellite image sources. The Torres Strait Reef and Island Feature mapping was integrated with the existing "GBR Features" dataset by GBRMPA to ensure that there were no duplicate feature ID allocations and to create a single dataset of the whole GBR. The overall dataset development was as follows: 1. Dataset collation and image preparation: - Collation of existing maps and datasets. - Download and preparation of the Landsat 5, 7, and 8 satellite image archive for Torres Strait. - Spatial position correction of Landsat imagery against a known reference image. 2. Sand Bank features: - Manual digitisation of sand banks from Landsat 5 imagery. - Conversion to a polygon shapefile for integration with the reef features. 3. Reef features: - Semi-automated digitisation of the marine features from Landsat 5 imagery. - Manual trimming, cleaning and checking of marine features against available aerial and satellite imagery. 4. Island features: - Compilation of island features from existing datasets (DNRM 1:25k Queensland Coastline, and Geoscience Australia Geodata Coast 100k 2004) - Correction of the island features from available aerial and Landsat imagery. 5. Merging: of marine and island features into one dataset. 6. Classification: of mapped features, including splitting fringing reefs based on changes in classification. 7. ID allocation: - Clustering to make groups of related features (i.e. an island, plus its fringing reefs and related sand banks; a reef plus its neighbouring patch reefs, etc.).
- Merging with the GBR Features dataset. This was to ensure that there were no duplicate allocations of feature IDs. This involved removing any overlapping features above the Great Barrier Reef Marine Park from the GBR Feature dataset. - Allocation of group IDs (i.e. 10-362) following the scheme used in the GBR Features dataset. Using R scripting. - Allocation of subgroup IDs (10-362b) to each feature in the dataset. Using R scripting. 8. Allocation of names: - Names of features were copied from some existing maps (Nautical Charts, 250k, 100k Topographic maps, CSIRO Torres Strait Atlas). For more information about the methods used in the development of this dataset see the associated technical report (Lawrey, E. P., Stewart M., 2016)

Limitations:

This dataset has mapped features from remote sensing and thus in some parts of Torres Strait where it is very turbid this may result in an underestimate of boundary of features. It also means that some features may be missing from the dataset.

This dataset is NOT SUITABLE FOR NAVIGATION.

The classification of features in this dataset was determined from remote sensing and not in-situ surveys. Each feature has a confidence rating associated with this classification. Features with a 'Low' confidence should be considered only as guidance.

This project only digitised reefs in Torres Strait, no modifications were made to the features from the integrated GBR Features dataset.

Format:

This dataset is available as a shapefile, a set of associated A1 preview maps of the Torres Strait region, ArcMap MXD file with map styling and ArcMap map layer file. The shapefile is also available in KMZ format suitable for viewing in Google Earth. TS_AIMS_NESP_Torres_Strait_Features_V1b_with_GBR_Features.shp (26 MB), TS_AIMS_NESP_Torres_Strait_Features_V1b_with_GBR_Features.kmz: Torres Strait features (3927 polygon features) integrated with the (GBRMPA) GBR Features dataset (5685 polygon features). This dataset covers the entire GBR.

Data Dictionary:

• DATASET: (TS Features, GBR Features) Which dataset this feature belongs to. This attribute is used when the Torres Strait Reef and Island Features dataset is merged with the GBRMPA GBR Features dataset.
• LOC_NAME_S: (e.g. Tobin (Zagarsum) Island (10-147a)) Location Name: Name of the feature and its ID
• GBR_NAME: (e.g. Tobin (Zagarsum) Island) Name of the features with no ID
• CHART_NAME: (e.g. Tobin Island) Name of the feature on the Australian Nautical Charts
• TRAD_NAME: (Zagarsum) Traditional name. From various sources.
• UN_FEATURE: (TRUE, FALSE) Unnamed Feature: If TRUE then the feature is unnamed. Useful for limiting labels in maps to features with names.
• LABEL_ID: (10-147a) ID of the feature
• SORT_GBR_I: (10147) ID of each feature cluster made up from the Latitude ID and Group ID. Used for sorting the features.
• FEAT_NAME: (Island, Rock, Reef, Cay, Mainland, Bank, Terrestrial Reef, Other ) Classification of the feature that is used in the GBR Features dataset. See 3.6 Classification scheme for more information.
• LEVEL_1, LEVEL_2, LEVEL_3: Hierarchical classification of the features. See Appendix 3: Feature Classification Descriptions.
• Checked: (TRUE, FALSE) Flag to record if the feature was reviewed in detail (at a scale of approximately 1:5000) after the initial digitisation. Unchecked features were only reviewed at a coarser scale (1:25000) to spot significant problems.
• IMG_SOURCE: (Aerial, AGRI, Landsat, ESRI) Imagery type used for the final digitisation checking and correction. (AGRI - AGRI PRISM by GA, Landsat is Landsat 8 or Landsat 5, ESRI - ArcMap satellite basemap)
• CLASS_SRC: (Aerial, AGRI, Landsat, Google, Marine Chart) Imagery type used to determine the classification of the feature. Often the classification will be an aggregation of information from multiple image sources. This field will record the highest resolution source used. For some small features the classification was obtained from the Marine Chart, generally for Rocky Reefs.
• CLASS_CONF: (High, Medium, Low) Confidence of the classification applied to the feature. The confidence is dependent on the clarity and range of the imagery available for classification. High - Clear high resolution imagery available (Aerial, Google) with good water visibility. Key characteristics of the classification clear visible. Feature classification fits the context for the neighbouring region. For unconsolidated features (such as sand banks) a High confidence classification would be applied if the shape, colour and context fit and in particular if movement is visible over time-lapse Landsat imagery. Medium - Moderate imagery available (Landsat 8 pan sharpened, some high resolution imagery) that shows key characteristics of the feature and the classification fits the context for the neighbouring region. Low - Only Landsat 5 imagery is available, the feature is small and its origin is unclear from the neighbouring context. This is the default confidence rating for any features that were not individually checked.
• POLY_ORIG: (QLD_DNRM_Coastline_25k, New, GBR_Features, AU_GA_Coast100k_2004) Original source of the polygon prior to any modifications. New features correspond to all the mapped marine features. Most features from the other source would have been modified as part of the checking and trimming of the dataset.
• SUB_NO: (100, 101, …) Subgroup number. Numeric count, starting at 100 of each feature in a group. Matches the subgroup ID i.e. 100 -> blank, 101 -> a, 102 -> b, etc.
• CODE: (e.g. 10-147-102-101) Unique code made from the various IDs. This is a GBR Feature attribute.
• UNIQUE_ID: (10147102101) Same as the CODE but without the hyphens, This is a GBR Feature attribute. Note: Version 1b, this attribution is currently out of date.
• FEATURE_C: (100 - 110) Code applied to each of the FEAT_NAMEs.
• QLD_NAME: (Tobin Island) Same as the GBR_NAME
• X_COORD: Longitude in decimal degrees east, in GDA94.
• Y_COORD: Latitude in decimal degrees north, in GDA94.
• SHAPE_AREA: Shape Area in km2
• SHAPE_LEN: Shape perimeter length in km
• CHECKED: (TRUE, FALSE) Whether the features was carefully checked (at a scale of better than ~1:5000) and manually corrected to this level of precision. If FALSE then the feature was only checked to approximately a1:25000 scale.
• PriorityLn: (TRUE, FALSE) Priority Label - If TRUE then this feature's label should be included in a map. Usually correspond to features with names. Use to reduce near duplicate labels of the islands and their surrounding fringing reefs.
• COUNTRY: (Australia, Papua-New Guinea) Sovereignty of the feature. This is based on a spatial join with the Australian Maritime Boundaries 2014a. The Territorial Sea and the Exclusive Economic