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.

This Python script (Shape2DJI_Pilot_KML.py) will scan a directory, find all the ESRI shapefiles (.shp), reproject to EPSG 4326 (geographic coordinate system WGS84 ellipsoid), create an output directory and make a new Keyhole Markup Language (.kml) file for every line or polygon found in the files. These new *.kml files are compatible with DJI Pilot 2 on the Smart Controller (e.g., for M300 RTK). The *.kml files created directly by ArcGIS or QGIS are not currently compatible with DJI Pilot.

Displays outlines depicting the current boundaries of WA State Parks lands. This KML file contains a network link to another KML file that is stored on the WA State Parks website. In this way, using this KML file will always display up-to-date boundaries, eliminating the need to download updated KML files.This data layer depicts the current boundaries for WA State Parks, and properties owned by WSPRC (Washington State Parks and Recreation Commission). Property types include State Park, State Park Conservation Area, State Park Heritage Site, State Park Property, State Park Trail, Historical State Park, and Marine State Park. Data is revised monthly or more frequently; however, errors and inaccuracies may exist in the data. This layer is for informational purposes only and is not intended to be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries.For attribute descriptions, see the metadata for the GIS data layer "ParkBoundaries", available online at http://geo.wa.gov/datasets/wa-stateparks::parks-park-boundaries .To download this and other data from Washington State Parks, go to geo.wa.gov and search for "wsprc" (Washington State Parks and Recreation Commission).

There is a Boulder County focus inherited from the Boulder Creek Critical Zone program. If you are aware of a resource worth sharing please let us know. Files are in the versatile KML format for ease of sharing. If you have trouble importing these into ArcGIS or another program just let us know.

SITE EXTENTS: Kml's that shows study site extents. The main set of extents was created by Kyotaek Hwang.

SITE: BOULDER CREEK BOULDER COUNTY More Boulder County data can be found here: https://opendata-bouldercounty.hub.arcgis.com/ Selected kmls include: - Archaeologically_Sensitive_Areas - County_Open_Space - Lakes_and_Reservoirs (included modern glaciers) - mun_wtrsheds_czo (restricted areas) - Open_space_czo - Riparian_Areas_-_2013_ERE - Road_Map_Roads

GEOLOGY - Geological map by Ogden Tweto, clipped here to Boulder Creek, geo_czo_tweto https://coloradogeologicalsurvey.org/publications/tweto-geologic-map-colorado-1979/

• Clipped Cole & Braddock geologic map

SOILS Natural Resources Conservation Service soil maps https://www.nrcs.usda.gov - soilmu_a_co643_bc (boulder County) - soilmu_a_co645_arnf (Arapaho National Forest

GLACIERS Madole's Glaciers LGM. No online source. Check licensing before using in publication

TOPOGRAPHIC Topographic Lines created but the BcCZO from 30m USGS DEM

LIDAR For Lidar: OpenTopgraphy 2010 Lidar, Snow ON Snow Off https://portal.opentopography.org/dataSearch?search=Boulder%20creek%20CZO

SITE: COAL CREEK Coal Creek Trails

The geopusher extension for CKAN automatically converts KML and Shapefile resources uploaded to a CKAN instance into GeoJSON resources. This conversion process allows users to easily access and utilize geospatial data in a modern, web-friendly format without needing to manually reformat the files. The extension operates as a celery task, meaning it can be configured to run automatically when resources are added or updated within CKAN. Key Features: Automatic GeoJSON Conversion: Converts KML and Shapefile resource uploads into GeoJSON format, increasing data usability and accessibility. Celery Task Integration: Operates as a Celery task, enabling asynchronous and automatic conversion upon resource creation or update and allowing other asynchronous operations to be processed at defined times. Batch Conversion: Provides functionality to convert all Shapefile resources on a CKAN instance or a specific subset of datasets at once. Technical Integration: The geopusher extension integrates with CKAN by listening to resource update events. The celery daemon needs to be running for automatic conversion to occur. The extension requires GDAL to be installed on the server to handle the geospatial data conversion. The README shows that the installation and usage involve updating the CKAN configuration Benefits & Impact: By automatically converting geospatial data into GeoJSON, the geopusher extension simplifies the use of KML and Shapefile data within web applications. This automation reduces manual effort, increases accessibility, and helps users to more readily integrate CKAN data into mapping and analysis tools. The automatic conversion ensures that when geospatial data is uploaded to a CKAN repository, users are able to immediately access the data in a suitable format for a wide range of web-based mapping applications, supporting improved data dissemination and collaboration.

This map and corresponding dataset provide the location, satellite images and square footage of existing green roofs within the City of Chicago. This dataset is in KML format. To view or use these files, special GIS software such as Google Earth is required.

This information is derived from an analysis of high-spatial resolution (50cm), pan-sharpened, ortho-rectified, 8-band multi-spectral satellite images collected by Digital Globe’s Worldview-2 satellite. The City supplied the consultant with a 2009 City boundary shapefile to determine the required extent of the imagery. Acquisition of three different strips of imagery corresponding to the satellite’s paths was required. These strips of imagery spanned three consecutive months and were collected in August 2010 (90% coverage), September 2010 (5% coverage) and October 2010 (5% coverage).

The results of the analysis include overall count of vegetated roofs, their total square footage, and the ratio of required to elective vegetated roofs. A total of 359 vegetated roofs were identified within the City of Chicago. The total square footage of these vegetated roofs was calculated to be approximately 5,469,463 square feet. The ratio of required vegetated roofs to elective vegetative roofs was 297:62 (~5:1). The median size of the vegetated roofs was calculated to be 5,234 square feet.

Please note: this is an experimental dataset, due to untested conversion from original KML files to ESRI geodatabase format.

Jupyter Notebooks to compute, plot and save as figures, text files or KML files several aperiodic tilings and layouts for seismic arrays Dependencies: numpy scipy matplotlib pandas scienceplots geopandas shapely pykml utm # UTM for converting between latitude/longitude and UTM coordinates simplekml # simplekml for creating KML files

GEODATA TOPO 250K Series 3 is a vector representation of the major features appearing on 1:250,000 scale NATMAP topographic maps and is supplied in various formats over a defined area. It is primarily designed to provide high quality data for mapping and GIS professionals. Data includes powerlines and pipelines and is supplied for commercial GIS and public use in the formats described below. GEODATA TOPO 250K Series 3 is available as a packaged product in Personal Geodatabase, ArcView Shapefile or MapInfo TAB file formats. Each package includes data arranged in ten main themes - cartography, elevation, framework, habitation, hydrography, infrastructure, terrain, transport, utility and vegetation. Data is also available as GEODATA TOPO 250K Series 3 for Google Earth in .kml format for use on Google Earth TM Mapping Service. All data is based on GDA94 coordinate system, however .kml format data has been converted to WGS84. Use of GEODATA TOPO 250K Series 3 is subject to a licence, the full terms of which are contained within the package. Interactive Maps, Geoscience Australia`s on-line map download system, delivering free download of seamless data. MapConnect will allow you to select a specific area (subject to parameters) and themes or select individual tiles for download. Data will be available in GML and Shape file formats. Customised 250K GEODATA is available where requirements are not met by the packaged or Interactive Maps options. The price will be determined after assessing your needs - contact the Geoscience Australia Sales Centre. Alternately, we may refer you to a third party supplier. Packaged product formats - Personal geodatabase (Geocat # 63999), Shapefiles (Geocat # 64058), TAB files (Geocat # 64059), KML files for use with Google Earth (Geocat # 65137). Product Specifications Themes: Cartography, Elevation, Framework, Habitation, Hydrography, Infrastructure, Terrain, Transport, Utility and Vegetation Coverage: National (Powerlines not available in South Australia) Currency: Data has a currency of less than five years for any location Coordinates: Geographical Datum: Geocentric Datum of Australia (GDA94) Formats: Personal Geodatabase, ArcView Shapefile and MapInfo TAB Medium: Packaged DVD ROM ($99 per package) or online via Interactive Maps Previous Version: Replaces GEODATA TOPO 250K Series 2

Supported file formats: - Avaatech XRF Core Scanner Spectrum (SPE). Example: hdl:10013/epic.42747.d011 - DShip ActionLog Events to PANGAEA event import file and cruise report station list. Example: hdl:10013/epic.42747.d014 - TRiDaS (Tree Ring Data Standard, http://www.tridas.org). Example: hdl:10013/epic.42747.d001 - IMMA (International Maritime Meteorological Archive). Used by the project CLIWOC (García-Herrera et al. 2007, doi:10.1594/PANGAEA.743343) - NOAA IOAS (International Ocean Atlas Series). Example: hdl:10013/epic.42747.d008 - NYA upper air soundings files. Format developed by Marion Maturilli. Example: hdl:10013/epic.42747.d013 - SOCAT (Surface Ocean CO2 Atlas, Bakker et al. 2014, doi:10.1594/PANGAEA.811776). Example: hdl:10013/epic.42747.d012 - CHUAN (Comprehensive Historical Upper-Air Network, Stickler et al. 2013, doi:10.1594/PANGAEA.821222). Example: hdl:10013/epic.42747.d003 - Thermosalinograph (TSG) data. Format developed by Gerd Rohardt. Example: hdl:10013/epic.42747.d002 - Columus GPS Data Logger V-900 format to KML or GPX. Example: hdl:10013/epic.42747.d006

Introduction

Geographical scale, in terms of spatial extent, provide a basis for other branches of science. This dataset contains newly proposed geographical and geological GIS boundaries for the Pan-Tibetan Highlands (new proposed name for the High Mountain Asia), based on geological and geomorphological features. This region comprises the Tibetan Plateau and three adjacent mountain regions: the Himalaya, Hengduan Mountains and Mountains of Central Asia, and boundaries are also given for each subregion individually. The dataset will benefit quantitative spatial analysis by providing a well-defined geographical scale for other branches of research, aiding cross-disciplinary comparisons and synthesis, as well as reproducibility of research results.

The dataset comprises three subsets, and we provide three data formats (.shp, .geojson and .kmz) for each of them. Shapefile format (.shp) was generated in ArcGIS Pro, and the other two were converted from shapefile, the conversion steps refer to 'Data processing' section below. The following is a description of the three subsets:

(1) The GIS boundaries we newly defined of the Pan-Tibetan Highlands and its four constituent sub-regions, i.e. the Tibetan Plateau, Himalaya, Hengduan Mountains and the Mountains of Central Asia. All files are placed in the "Pan-Tibetan Highlands (Liu et al._2022)" folder.

(2) We also provide GIS boundaries that were applied by other studies (cited in Fig. 3 of our work) in the folder "Tibetan Plateau and adjacent mountains (Others’ definitions)". If these data is used, please cite the relevent paper accrodingly. In addition, it is worthy to note that the GIS boundaries of Hengduan Mountains (Li et al. 1987a) and Mountains of Central Asia (Foggin et al. 2021) were newly generated in our study using Georeferencing toolbox in ArcGIS Pro.

(3) Geological assemblages and characters of the Pan-Tibetan Highlands, including Cratons and micro-continental blocks (Fig. S1), plus sutures, faults and thrusts (Fig. 4), are placed in the "Pan-Tibetan Highlands (geological files)" folder.

Note: High Mountain Asia: The name ‘High Mountain Asia’ is the only direct synonym of Pan-Tibetan Highlands, but this term is both grammatically awkward and somewhat misleading, and hence the term ‘Pan-Tibetan Highlands’ is here proposed to replace it. Third Pole: The first use of the term ‘Third Pole’ was in reference to the Himalaya by Kurz & Montandon (1933), but the usage was subsequently broadened to the Tibetan Plateau or the whole of the Pan-Tibetan Highlands. The mainstream scientific literature refer the ‘Third Pole’ to the region encompassing the Tibetan Plateau, Himalaya, Hengduan Mountains, Karakoram, Hindu Kush and Pamir. This definition was surpported by geological strcture (Main Pamir Thrust) in the western part, and generally overlaps with the ‘Tibetan Plateau’ sensu lato defined by some previous studies, but is more specific.

More discussion and reference about names please refer to the paper. The figures (Figs. 3, 4, S1) mentioned above were attached in the end of this document.

Data processing

We provide three data formats. Conversion of shapefile data to kmz format was done in ArcGIS Pro. We used the Layer to KML tool in Conversion Toolbox to convert the shapefile to kmz format. Conversion of shapefile data to geojson format was done in R. We read the data using the shapefile function of the raster package, and wrote it as a geojson file using the geojson_write function in the geojsonio package.

Version

Version 2022.1.

Acknowledgements

This study was supported by the Strategic Priority Research Program of Chinese Academy of Sciences (XDB31010000), the National Natural Science Foundation of China (41971071), the Key Research Program of Frontier Sciences, CAS (ZDBS-LY-7001). We are grateful to our coauthors insightful discussion and comments. We also want to thank professors Jed Kaplan, Yin An, Dai Erfu, Zhang Guoqing, Peter Cawood, Tobias Bolch and Marc Foggin for suggestions and providing GIS files.

Citation

Liu, J., Milne, R. I., Zhu, G. F., Spicer, R. A., Wambulwa, M. C., Wu, Z. Y., Li, D. Z. (2022). Name and scale matters: Clarifying the geography of Tibetan Plateau and adjacent mountain regions. Global and Planetary Change, In revision

Jie Liu & Guangfu Zhu. (2022). Geographical and geological GIS boundaries of the Tibetan Plateau and adjacent mountain regions (Version 2022.1). https://doi.org/10.5281/zenodo.6432940

Contacts

Dr. Jie LIU: E-mail: liujie@mail.kib.ac.cn;

Mr. Guangfu ZHU: zhuguangfu@mail.kib.ac.cn

Institution: Kunming Institute of Botany, Chinese Academy of Sciences

Address: 132# Lanhei Road, Heilongtan, Kunming 650201, Yunnan, China

Copyright

This dataset is available under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0).

Emprise du terrain d'Ifremer à Sète. Dessinée à partir de google earth (image satellite de 11/08/2006 tele atlas) Export en kml et conversion en shp à l'aide de l'outil en ligne : http://freegeographytools.com/2009/online-kml-to-shapefile-converter

Bridges feature class was created by converting an existing KML file of bridge locations maintained by Shasta County Public Works, then adding and populating fields maintained in Public Work's Bridge Inspection Spreadsheet. These additional fields were added to simplify joining the feature class to the spreadsheet, and symbolizing on common attributes.

USA Railroads is a comprehensive database of the nation's railway system at 1:24,000 to 1:100,000 scale. The data set covers all 50 States plus the District of Columbia.This hosted feature service displays at scales up to 1:1,500,000.

The V1 ('flying bomb' or 'doodlebug') and V2 (a ballistic missile) were two new weapons developed by Nazi Germany. In 1944 and 1945 thousands were fired at London. They killed thousands of people and injured many more.

This dataset includes all impact sites for V1s and V2s within the London County Council boundary. These were manually compiled from bomb maps published in 'The London County Council Bomb Damage Maps 1939-1945' by Laurence Ward (Thames and Hudson, 2015). The original LCC Bomb Damage maps are held at the London Archives.

**Please note that this is not a comprehensive dataset of all V1s and V2s. Only those within the London County Council boundary are included.**

We previously analysed this dataset in 'The flying bomb and the actuary', Significance (2019). doi: 10.1111/j.1740-9713.2019.01315.x

The impact sites can also be viewed as a layer on Google Maps. Data is separated into two layers: V1 sites and V2 sites. Each point represents an impact site, with the closest street name (to help with possible cross-reference) and page number in the LCC Bomb Damage Maps: https://www.google.com/maps/d/viewer?mid=1VwyxV_e_LAwzbyJPCAF-C7aCRVNA5W7N&ll=51.509018493447314%2C-0.05324588962980492&z=14

This dataset contains lines for all highways in the state of New Mexico. It is in a vector digital data structure digitized from a USGS 1:500,000 scale map of the state of New Mexico to which highways: Interstate, U.S., and State have been added. The source was ARC/INFO 5.0.1. and the conversion software was ARC/INFO 7.0.3. The size of the file is .36 Mb, compressed.

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

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

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

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