This layer features special areas of interest (AOIs) that have been contributed to Esri Community Maps using the new Community Maps Editor app. The data that is accepted by Esri will be included in selected Esri basemaps, including our suite of Esri Vector Basemaps, and made available through this layer to export and use offline. Export DataThe contributed data is also available for contributors and other users to export (or extract) and re-use for their own purposes. Users can export the full layer from the ArcGIS Online item details page by clicking the Export Data button and selecting one of the supported formats (e.g. shapefile, or file geodatabase (FGDB)). User can extract selected layers for an area of interest by opening in Map Viewer, clicking the Analysis button, viewing the Manage Data tools, and using the Extract Data tool. To display this data with proper symbology and metadata in ArcGIS Pro, you can download and use this layer file.Data UsageThe data contributed through the Community Maps Editor app is primarily intended for use in the Esri Basemaps. Esri staff will periodically (e.g. weekly) review the contents of the contributed data and either accept or reject the data for use in the basemaps. Accepted features will be added to the Esri basemaps in a subsequent update and will remain in the app for the contributor or others to edit over time. Rejected features will be removed from the app.Esri Community Maps Contributors and other ArcGIS Online users can download accepted features from this layer for their internal use or map publishing, subject to the terms of use below.

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 contains 4 different scale GEODATA TOPO series, Geoscience Australia topographic datasets. 1M, 2.5M, 5M and 10M with age ranges from 2001 to 2004.

1:1 Million - Global Map Australia 1M 2001 is a digital dataset covering the Australian landmass and island territories, at a 1:1 million scale. Product Specifications -Themes: It consists of eight layers of information: Vector layers - administrative boundaries, drainage, transportation and population centres Raster layers - elevation, vegetation, land use and land cover -Coverage: Australia -Currency: Variable, based on GEODATA TOPO 250K Series 1 -Coordinates: Geographical -Datum: GDA94, AHD -Medium: Free online -Format: -Vector: ArcInfo Export, ESRI Shapefile, MapInfo mid/mif and Vector Product Format (VPF) -Raster: Band Interleaved by Line (BIL)

1:2.5 Million - GEODATA TOPO 2.5M 2003 is a national seamless data product aimed at regional or national applications. It is a vector representation of the Australian landscape as represented on the Geoscience Australia 2.5 million general reference map and is suitable for GIS applications. The product consists of the following layers: built-up areas; contours; drainage; framework; localities; offshore; rail transport; road transport; sand ridges; Spot heights; and waterbodies. It is a vector representation of the Australian landscape as represented on the Geoscience Australia 1:2.5 million scale general reference maps. This data supersedes the TOPO 2.5M 1998 product through the following characteristics: developed according to GEODATA specifications derived from GEODATA TOPO 250K Series 2 data where available. Product Specifications Themes: GEODATA TOPO 2.5M 2003 consists of eleven layers: built-up areas; contours; drainage; framework; localities; offshore; rail transport; road transport; sand ridges; spot heights; and waterbodies Coverage: Australia Currency: 2003 Coordinates: Geographical Datum: GDA94, AHD Format: ArcInfo Export, ArcView Shapefile and MapInfo mid/mif Medium: Free online - Available in ArcInfo Export, ArcView Shapefile and MapInfo mid/mif

1:5 Million - GEODATA TOPO 5M 2004 is a national seamless data product aimed at regional or national applications. It is a vector representation of the Australian landscape as represented on the Geoscience Australia 5 million general reference map and is suitable for GIS applications. Offshore and sand ridge layers were sourced from scanning of the original 1:5 million map production material. The remaining nine layers were derived from the GEODATA TOPO 2.5M 2003 dataset. Free online. Available in ArcInfo Export, ArcView Shapefile and MapInfo mid/mif. Product Specifications: Themes: consists of eleven layers: built-up areas; contours; drainage; framework; localities; offshore; rail transport; road transport; sand ridges, spot heights and waterbodies Coverage: Australia Currency: 2004 Coordinates: Geographical Datum: GDA94, AHD Format: ArcInfo Export, ArcView Shapefile and MapInfo mid/mif Medium: Free online

1:10 Million - The GEODATA TOPO 10M 2002 version of this product has been completely revised, including the source information. The data is derived primarily from GEODATA TOPO 250K Series 1 data. In October 2003, the data was released in double precision coordinates. It provides a fundamental base layer of geographic information on which you can build a wide range of applications and is particularly suited to State-wide and national applications. The data consists of ten layers: built-up areas, contours, drainage, Spot heights, framework, localities, offshore, rail transport, road transport, and waterbodies. Coverage: Australia Currency: 2002 Coordinates: Geographical Datum: GDA94, AHD Format: ArcInfo Export, Arcview Shapefile and MapInfo mid/mif Medium: Free online

Dataset History

1:1Million - Vector data was produced by generalising Geoscience Australia's GEODATA TOPO 250K Series 1 data and updated using Series 2 data where available in January 2001. Raster data was sourced from USGS and updated using GEODATA 9 Second DEM Series 2, 1:5 million, Vegetation - Present (1988) and National Land and Water Resources data. However, updates have not been subjected to thorough vetting. A more detailed land use classification for Australia is available at www.nlwra.gov.au.

Full Metadata - http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_48006

1:2.5Million - Data for the Contours, Offshore, and Sand ridge layers was captured from 1:2.5 million scale mapping by scanning stable base photographic film positives of the original map production material. The key source material for Built-up areas, Drainage, Spot heights, Framework, Localities, Rail transport, Road transport and Waterbodies layers was GEODATA TOPO 2.5M 2003

Full Metadata - http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_60804

1:5Million - Offshore and Sand Ridge layers have been derived from 1:5M scale mapping by scanning stable base photographic film positives of the various layers of the original map production material. The remaining layers were sourced from the GEODATA TOPO 2.5M 2003 product.

Full Metadata - http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_61114

1:10Million - The key source for production of the Builtup Areas, Drainage, Framework, Localities, Rail Transport, Road Transport and Waterbodies layers was the GEODATA TOPO 250K Series 1 product. Some revision of the Builtup Areas, Road Transport, Rail Transport and Waterbodies layers was carried out using the latest available satelite imagery. The primary source for the Spot Heights, Contours and Offshore layers was the GEODATA TOPO 10M Version 1 product. A further element to the production of GEODATA TOPO 10M 2002 has been the datum shift from the Australian Geodetic Datum 1966 (AGD66) to the Geocentric Datum of Australia 1994 (GDA94).

Full Metadata - http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_60803

Dataset Citation

Geoscience Australia (2001) Geoscience Australia GEODATA TOPO series - 1:1 Million to 1:10 Million scale. Bioregional Assessment Source Dataset. Viewed 09 October 2018, http://data.bioregionalassessments.gov.au/dataset/310c5d07-5a56-4cf7-a5c8-63bdb001cd1a.

The Digital Geologic Sample Localities of Great Smoky Mountains National Park and Vicinity, Tennessee and North Carolina consists of geologic sample localities mapped as point features. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). The data were captured, grouped and attributed as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.3.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The data layer is available as a feature class in a 9.1 personal geodatabase (grsm_geology.mdb). The Geologic Sample Localities (GRSMGSL) GIS data layer is also available as a coverage export (.E00) file (GRSMGSL.E00), and as a shapefile (.SHP) file (GRSMGSL.SHP). Each GIS data format has an ArcGIS 9.1 layer (.LYR) file (GRSMGSL_GDB.LYR (geodatabase feature class), GRSMGSL_COV.LYR (coverage), GRSMGSL_SHP.LYR (shapefile) with map symbology that is included with the GIS data. See the Distribution Information section for additional information on data acquisition. The GIS data projection is NAD83, UTM Zone 17N. The data is within the area of interest of Great Smoky Mountains National Park.

GIS2DJI is a Python 3 program created to exports GIS files to a simple kml compatible with DJI pilot. The software is provided with a GUI. GIS2DJI has been tested with the following file formats: gpkg, shp, mif, tab, geojson, gml, kml and kmz. GIS_2_DJI will scan every file, every layer and every geometry collection (ie: MultiPoints) and create one output kml or kmz for each object found. It will import points, lines and polygons, and converted each object into a compatible DJI kml file. Lines and polygons will be exported as kml files. Points will be converted as PseudoPoints.kml. A PseudoPoints fools DJI to import a point as it thinks it's a line with 0 length. This allows you to import points in mapping missions. Points will also be exported as Point.kmz because PseudoPoints are not visible in a GIS or in Google Earth. The .kmz file format should make points compatible with some DJI mission software.

The Digital Geologic Map of the Scenic Area, South Dakota is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcView 3.X legend (.AVL) files. The data were completed as a component of the Geologic Resource Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GIS-Geology Coverage/Shapefile Data Model (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 13N. That data is within the area of interest of Badlands National Park.

Shapefiles information containing the basic information about the spatial structure of the STIB-MIVB network: route of the lines and position of the stops of the "commercial" network, that is the basic itineraries "to" and "from".

Exports du découpage administratif français au niveau régional (contours des régions) issu d'OpenStreetMap produit dans sa grande majorité à partir du cadastre. Ces données sont issues du crowdsourcing effectué par les contributeurs au projet OpenStreetMap et sont sous licence ODbL qui impose un partage à l'identique et la mention obligatoire d'attribution doit être "© les contributeurs d'OpenStreetMap sous licence ODbL" conformément à http://osm.org/copyright Il s'agit d'un export semi-automatique avec des géométries allégées et vérifiées topologiquement (pas de chevauchement). A partir de 2016, les géométries sont d'origine, non simplifiées. Descriptif du contenu des fichiers "regions" Origine Les données proviennent de la base de données cartographiques OpenStreetMap. Celles-ci ont été constituées à partir du cadastre mis à disposition par la DGFiP sur cadastre.gouv.fr. En complément sur Mayotte où le cadastre n'est pas disponible sur cadastre.gouv.fr, le tracé des côtes a été fait à partir des images aériennes de Bing. Plus d'infos: http://prev.openstreetmap.fr/36680-communes Format Ces fichiers sont proposés au format shapefile, en projection WGS84 avec plusieurs niveaux de détails (jusqu'en 2015): simplification à 5m simplification à 50m simplification à 100m La topologie est conservée lors du processus de simplification (cf: http://prev.openstreetmap.fr/blogs/cquest/limites-administratives-simplifiees) Contenu Ces fichiers contiennent l'ensemble des régions françaises, y compris les DOM et Mayotte. Pour chaque région, les attributs suivants sont ajoutés: code_insee: code INSEE à 2 chiffres de la région (ex: 42) nom: nom de la région (ex: Alsace) wikipedia: entrée wikipédia (code langue suivi du nom de l'article, ex: fr:Alsace) wikidata: identifiant wikidata de la région surf_km2: superficie de la région en km2 sur le sphéroid WGS84 Historique 01-01-2017 : version basée sur le découpage communal OSM au 01-01-2017 incluant la fusion de 566 communes en 178 communes nouvelles. 01-01-2018 : version basée sur le découpage communal OSM au 01-01-2018 (changement marginal de géométrie) Versions prédécentes disponibles sur: http://osm13.openstreetmap.fr/~cquest/openfla/export/ Pour toute question concernant ces exports, vous pouvez contacter exports@openstreetmap.fr Voir aussi: Cartes au format SVG Contours des communes françaises Contours des EPCI 2014 et Contours des EPCI 2013 Contours des arrondissements français Contours des départements français et Cartes SVG des départements

Exports du découpage administratif français au niveau communal (contours des communes) issu d'OpenStreetMap produit dans sa grande majorité à partir du cadastre. Ces données sont issues du crowdsourcing effectué par les contributeurs au projet OpenStreetMap et sont sous licence ODbL qui impose un partage à l'identique et la mention obligatoire d'attribution doit être "© les contributeurs d'OpenStreetMap sous licence ODbL" conformément à http://osm.org/copyright Un export automatique quotidien au format shapefile est disponible, ainsi qu'un second export avec des géométries allégées et vérifiées topologiquement (pas de chevauchement). Descriptif du contenu des fichiers "communes" Origine Les données proviennent de la base de données cartographiques OpenStreetMap. Celles-ci ont été constituées à partir du cadastre mis à disposition par la DGFiP sur cadastre.gouv.fr. En complément sur Mayotte où le cadastre n'est pas disponible sur cadastre.gouv.fr, ce sont les limites du GEOFLA de l'IGN qui ont été utilisées ainsi que le tracé des côtes à partir des images aériennes de Bing. Plus d'infos: http://prev.openstreetmap.fr/36680-communes Format Ces fichiers sont proposés au format shapefile, en projection WGS84 avec plusieurs niveaux de détails: simplification à 5m simplification à 50m simplification à 100m La topologie est conservée lors du processus de simplification (cf: http://prev.openstreetmap.fr/blogs/cquest/limites-administratives-simplifiees) Contenu Ces fichiers contiennent l'ensemble des communes françaises, y compris les DOM, Mayotte et Saint-Pierre-et-Miquelon. Pour Paris, Lyon, Marseille, ce sont les limites d'arrondissements qui sont fournies à la place des limites de communes. Pour chaque commune ou arrondissement, les attributs suivants sont ajoutés: insee: code INSEE à 5 caractères de la commune nom: nom de la commune (tel que figurant dans OpenStreetMap, si possible conforme aux règles de toponymie) wikipedia: entrée wikipédia (code langue suivi du nom de l'article) surf_ha : surface en hectares de la commune Pour les communes de Bois-Guillaume et Bihorel, les données du GEOFLA ont été corrigées manuellement suite à l'annulation de la fusion le 1er Janvier 2014. Historique 19-12-2013 : première génération du fichier, basé sur le découpage communal OSM au 19-12-2013 20-12-2013 : correction de 2 erreurs (un cimetière militaire était exclu du territoire par erreur, la géométrie de la commune de Landerneau manquait) 06-03-2014 : troisième génération du fichier, basé sur le découpage communal OSM au 06-03-2014 29-06-2014 : remplacement des limites de Paris, Lyon, Marseille par les limites de leurs arrondissements municipaux. 30-06-2014 : ajout de la version "enrichie" 10-10-2014 : ajout d'un export CSV de la version "enrichie" 01-01-2015 : quatrième version du fichier, prenant en compte les fusions de communes au 1/1/2015 ainsi que les communes ayant changé de nom le 3/12/2014. Pour les communes fusionnées et à titre temporaire (attente de publication du COG 2015) le code INSEE conservé est celui de la commune où le chef-lieu est fixé par le JORF. 19-01-2016 : cinquième version du fichier, prenant en compte les fusions de communes au 19/1/2016 ainsi que les changements intervenus en 2015 (nouveaux noms, etc). Voir ce jeu de données pour plus de détail sur les fusions et communes nouvelles. Les arrondissements municipaux (Paris, Lyon, Marseille) sont disponibles dans un fichier séparé avec les communes déléguées issues de la création des communes nouvelles. 11-01-2017 : version prenant en compte les 181 fusions de communes au 1/1/2017 ainsi que les changements intervenus en 2016 (nouveaux noms, fusions, etc). Voir ce jeu de données pour plus de détail sur les fusions et communes nouvelles. 01-01-2018 : version comprenant les 33 fusions de communes au 1/1/2018 et la fusion au 1/7/2017, ainsi que les changements de noms intervenus en 2017. St-Pierre et Miquelon sont dans le fichier des communes des Collectivités d'Outre-Mer. 26-02-2018 : version au 1/1/2018 complétée par 3 communes nouvelles (Aubessagne, Blancs-Coteaux, Geiswiller-Zœbersdorf) soit au total 36 fusions. 01-01-2019 : version au 1/1/2019 comprenant 232 communes nouvelles répertoriées sur wikipédia au 01/01/2019 11-02-2019 : intégration des communes nouvelles répertoriées par l'INSEE 07-03-2019 : correction du code INSEE de La Léchère (73187) 01-01-2021 : Fusion des communes au 1/1/2021 Versions précédentes disponibles sur: http://osm13.openstreetmap.fr/~cquest/openfla/export/ Pour toute question concernant ces exports, vous pouvez contacter exports@openstreetmap.fr Voir aussi : Liste des adjacences des communes françaises Contours des EPCI 2014 et Contours des EPCI 2013 Contours des arrondissements français Contours des départements français et Cartes SVG des départements Contours de régions françaises Contours des futures régions

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 (not yet published) 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.

Change Log: 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.

22 Nov 2023: 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.

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.

Marine satellite imagery (Sentinel 2 and Landsat 8) (AIMS), https://eatlas.org.au/data/uuid/5d67aa4d-a983-45d0-8cc1-187596fa9c0c - World_AIMS_Marine-satellite-imagery

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.

The Digital Folds of Great Smoky Mountains National Park and Vicinity, Tennessee and North Carolina consists of folds mapped as line (arc) features. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). The data were captured, grouped and attributed as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.3.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The data layer is available as a feature class in a 9.1 personal geodatabase (grsm_geology.mdb). The Folds (GRSMFLD) GIS data layer is also available as a coverage export (.E00) file (GRSMFLD.E00), and as a shapefile (.SHP) file (GRSMFLD.SHP). Each GIS data format has an ArcGIS 9.1 layer (.LYR) file (GRSMFLD_GDB.LYR (geodatabase feature class), GRSMFLD_COV.LYR (coverage), GRSMFLD_SHP.LYR (shapefile) with map symbology that is included with the GIS data. See the Distribution Information section for additional information on data acquisition. The GIS data projection is NAD83, UTM Zone 17N. The data is within the area of interest of Great Smoky Mountains National Park.

The Digital Geologic Map of the Mine Run Quadrangle, Virginia is comprised of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata, ArcMap 9.1 layer (.LYR) files, and an ArcMap 9.1 map document (.MXD) file. The data were completed as a component of the Geologic Resources Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 1.3.1 (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.htm). The GIS data is available as an 9.1 personal geodatabase (miru_geology.mdb), as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 18N. That data is within the area of interest of Fredericksburg and Spotsylvania County Battlefields Memorial National Military Park.

Overview

Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.

Our self-hosted GIS data cover administrative and postal divisions with up to 6 precision levels: a zip code layer and up to 5 administrative levels. All levels follow a seamless hierarchical structure with no gaps or overlaps.

The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.

Use cases for the Global Boundaries Database (GIS data, Geospatial data)

• In-depth spatial analysis

• Clustering

• Geofencing

• Reverse Geocoding

• Reporting and Business Intelligence (BI)

Product Features

• Coherence and precision at every level

• Edge-matched polygons

• High-precision shapes for spatial analysis

• Fast-loading polygons for reporting and BI

• Multi-language support

For additional insights, you can combine the GIS data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

Our geospatial data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

All GIS data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our map data

• Precision at every level

• Coverage of difficult geographies

• No gaps, nor overlaps

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

GEODATA TOPO 5M 2004 is a national seamless data product aimed at regional or national applications. It is a vector representation of the Australian landscape as represented on the Geoscience Australia 5 million general reference map and is suitable for GIS applications.
Offshore and sand ridge layers were sourced from scanning of the original 1:5 million map production material. The remaining nine layers were derived from the GEODATA TOPO 2.5M 2003 dataset. Free online. Available in ArcInfo Export, ArcView Shapefile and MapInfo mid/mif. Product Specifications: Themes: consists of eleven layers: built-up areas; contours; drainage; framework; localities; offshore; rail transport; road transport; sand ridges, spot heights and waterbodies Coverage: Australia Currency: 2004 Coordinates: Geographical Datum: GDA94, AHD Format: ArcInfo Export, ArcView Shapefile and MapInfo mid/mif Medium: Free online

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) :

tags['place'] IN ('isolated_dwelling', 'town', 'village', 'hamlet', 'city')

Features may have these attributes:

• name
• name:en
• place
• population
• is_in
• source

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

highway IS NOT NULL

Features may have these attributes:

• smoothness
• name
• surface
• bridge
• source
• width
• oneway
• lanes
• layer
• highway

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

GEODATA TOPO 2.5M 2003 is a national seamless data product aimed at regional or national applications. It is a vector representation of the Australian landscape as represented on the Geoscience Australia 2.5 million general refererence map and is
suitable for GIS applications.
The product consists of the following layers: built-up areas; contours; drainage; framework; localities; offshore; rail transport; road transport; sand ridges; Spot heights; and waterbodies. It is a vector representation of the Australian landscape as
represented on the Geoscience Australia 1:2.5 million scale general reference maps. This data superscedes the TOPO 2.5M 1998 product through the following characteristics: