Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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 Unpublished Digital Geologic-GIS Map of Navajo National Monument and Vicinity, Arizona is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (nava_geology.gdb), a 10.1 ArcMap (.mxd) map document (nava_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (nava_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (nava_geology_gis_readme.pdf). Please read the nava_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 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. Google Earth software is available for free at: http://www.google.com/earth/index.html. 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). 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 (nava_geology_metadata.txt or nava_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:125,000 and United States National Map Accuracy Standards features are within (horizontally) 63.5 meters or 208.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 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 GIS data projection is NAD83, UTM Zone 12N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Navajo National Monument.
The Unpublished Digital Geologic-GIS Map of Moores Creek National Battlefield, North Carolina is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (mocr_geology.gdb), a 10.1 ArcMap (.mxd) map document (mocr_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (mocr_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (mocr_geology_gis_readme.pdf). Please read the mocr_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 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. Google Earth software is available for free at: http://www.google.com/earth/index.html. 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). 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 (mocr_geology_metadata.txt or mocr_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:250,000 and United States National Map Accuracy Standards features are within (horizontally) 127 meters or 416.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 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 GIS data projection is NAD83, UTM Zone 17N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Moores Creek National Battlefield.
The Digital Geologic-GIS Map of Yosemite National Park and Vicinity, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (yose_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (yose_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (yose_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (yose_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (yose_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (yose_geology_metadata_faq.pdf). Please read the yose_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and California Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (yose_geology_metadata.txt or yose_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
The USNIC Great Lakes Ice Chart Web Service is made up of Analysis polygon features classes. The Great Lakes Analysis GIS Shapefile and KMZ file are created and loaded into CloudGIS Database for use in the USNIC Great Lakes Ice Chart Web Service from the North American Ice Service daily Great Lakes Analysis coordinated between the U.S. National Ice Center and Canadian Ice Service. The daily Great Lakes Analysis contains SIGRID-3 information on ice conditions that are separated into various fields including total ice concentration, ice types and their respective partial concentrations, and floe size, among others. This analysis is updated daily, valid at 18 UTC, and available at https://usicecenter.gov/Products/GreatLakesData.The SIGRID-3 vector archive format is one of the World Meteorological Organization (WMO) standards for archiving digital ice charts. The U.S National Ice Center (USNIC) creates SIGRID-3 ice charts on a regular basis for a number of regions in the Arctic, Antarctic, Great Lakes and U.S. East Coast. These SIGRID-3 files have two main components: the shapefile containing the ice analysis information (ice polygons and related attributes) and the metadata describing the ice analysis data under the SIGRID-3 format. Current and legacy data for many USNIC products can be found through the USNIC website (https://usicecenter.gov/), the National Snow and Ice Data Center (https://nsidc.org/) or, for the Great Lakes specifically, through the Great Lakes Environmental Research Laboratory (https://www.glerl.noaa.gov/). The joint North American Ice Service analysis from which this USNIC product derives represents ice conditions valid at approximately 1800 UTC but is analyzed from imagery over the preceding 24hrs. Imagery utilized includes synthetic aperture radar (SAR), geostationary imagery such as GOES, polar orbiting imagery such as VIIRS, other optical or infrared sensors prioritized by regency and image quality, and application of an understanding of conditions gained from surface stations, radar, and forecast weather conditions.Update Frequency: Daily at 1800UTCLink to metadataFor questions about the underlying data or other ice datasets, please see https://usicecenter.gov/Contact.Questions/Concerns about the service, please contact the DISS-GIS team.Time Information:This service is not time enabled.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The datasets presented are mapped Demand Responsive Transport (DRT) routes and destinations, created by data provided by Local Link rural transport services in the Republic of Ireland. The datasets were created to provide representations of the areas of service which the services are willing to pick up passengers. The data are available in (zipped) shapefiles and KMZ file format.
South Sudan administrative levels 0 (country), 1 (state), and 2 (county) boundary polygon, line, and point shapefiles and KML files and gazetteer; Abyei boundary polygon shapefile and KMZ file; and live services.
This administrative boundaries Common Operational Database (COD-AB) was endorsed by the South Sudan Inter Cluster Coordinating Group (ICCG) and Humanitarian Country Team (HCT) on August 14, 2018.
These boundary files are suitable for database or GIS linkage to the South Sudan administrative levels 0-2 2014 and 2018 population statistics tables available on HDX.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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).
Burkina Faso administrative level 0 (country), 1 (administrative region), 2 (province), and 3 (department) boundary polygon and line shapefiles and KMZ files, and gazeteer
The administrative level 0 and 1 shapefiles are suitable for database or GIS linkage to the CSV population statistics tables.
NOTE that the ITOS live services are for a previous version of the boundaries
The Unpublished Digital Geologic-GIS Map of Virgin Islands National Park, Virgin Islands is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (viis_geology.gdb), a 10.1 ArcMap (.mxd) map document (viis_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (viis_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (viis_geology_gis_readme.pdf). Please read the viis_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 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. Google Earth software is available for free at: http://www.google.com/earth/index.html. 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). 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 (viis_geology_metadata.txt or viis_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 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 GIS data projection is NAD83, UTM Zone 20N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Virgin Islands National Park.
Côte d'Ivoire administrative level 0 (country), 1 (district / autonomous city), 2 (region), and 3 (department) boundary polygons, lines, and points shapefiles, geodatbase, KMZ files, and live services, and gazetteer
The Climate Prediction Center releases a US Hazards Outlook daily, Monday through Friday. The product highlights regions of anticipated hazardous weather during the next 3-7 and 8-14 days and examples include heavy snow, high winds, flooding, extreme heat and cold and severe thunderstorms. The product highlights regions of anticipated hazardous weather during the next 3-7 and 8-14 days. Three separate files are available for download for each time period. A soils shapefile (and KMZ) contain severe drought and enhanced wildfire risk hazards. A temperature file contains temperature, wind, and wave hazards, and a precipitation file contains rain, snow, and severe weather hazards. The contents of these file are mashed up to create one composite graphic per time period as well as being displayed on an interactive Google Map
The Unpublished Digital Geologic Map of Bering Land Bridge National Preserve and Vicinity, Alaska is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (bela_geology.gdb), a 10.1 ArcMap (.MXD) map document (bela_geology.mxd), individual 10.1 layer (.LYR) files for each GIS data layer, an ancillary map information (.PDF) document (bela_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.TXT) and FAQ (.HTML) formats, and a GIS readme file (bela_gis_readme.pdf). Please read the bela_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O’Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 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. Google Earth software is available for free at: http://www.google.com/earth/index.html. 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). 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 (bela_metadata_faq.html; available at http://nrdata.nps.gov/geology/gri_data/gis/bela/bela_metadata_faq.html). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:500,000 and United States National Map Accuracy Standards features are within (horizontally) 254 meters or 833.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 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.2. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone AD_1983_Alaska_AlbersN, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Bering Land Bridge National Preserve.
This USGS data release includes two ESRI polyline shapefiles (file_names.shp) describing the describing the steepest-descent lines calculated at two levels of detail (See Process Step for explanation). To increase access to these data, KMZ (Compressed Keyhole Markup Language) versions of the polyline feature layers are included in this release (file_names.kmz). In addition to these data layers, two supplementary data layers from the Big Island Mapping Project (BIMP) showing lava flows originating on Mauna Loa and Kilauea volcanoes, originally published in Trusdell, Wolfe, and Morris (2006), are included for context and reference. Both ESRI polygon shapefiles and KMZ versions of these files are included, naming conventions are identical as the files in this release. This metadata file provides information for the GIS data files unique to this data release. Below are the files that comprise this release, including the metadata files: Steepest-Descent_lines_3M_m2.shp Steepest-Descent_lines_750K_m2.shp Steepest-Descent_lines_3M_m2.KMZ Steepest-Descent_lines_750K_m2.KMZ Kilauea1983-1996_from_BIMP.shp ML1984_from_BIMP.shp Kilauea1983-1996_from_BIMP.kmz ML1984_from_BIMP.kmz mauna_loa_steepest_descent_lines_FGDC.xml mauna_loa_steepest_descent_lines_FGDC.txt
This file contains points that describe locations of oil shale core holes and rotary holes in the state of Colorado and is available as an ESRI shapefile, Google Earth KMZ file, and ASCII text file.
This feature layer, Draft Blackwater River Loop Alignment: 2023, describes a draft route of the proposed Blackwater Loop Trail close to Davis, West Virginia. The data associated with this layer were received from Civil & Environmental Consultants, Inc. Source and date:This data was received as a Google Earth KMZ file from Civil & Environmental Consultants, Inc. on 2/8/2023.Purpose:This data was created in order to propose a trail in Davis, VA. The draft route is needed in order to propose the trail.Processing:ABRA imported the received KMZ file into ArcGIS as a shapefile. The shapefile was uploaded to ArcGIS online and published as a feature layer.Symbolization:The following symbolization is how it appears in the Parsons to Davis online map provided by ABRA.Draft Blackwater River Loop: dotted blue polyline
https://www.caliper.com/license/maptitude-license-agreement.htmhttps://www.caliper.com/license/maptitude-license-agreement.htm
Healthcare Data for use with GIS mapping software, databases, and web applications are from Caliper Corporation and contain point geographic files of healthcare organizations, providers, and hospitals and an boundary file of Primary Care Service Areas.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
This data set provides GIS shapefiles and Google Earth kmz files containing polygons delineating slow-moving (0.5-6 cm/year in the radar line-of-sight direction) landslides and subsiding fan deltas in the Glacier Bay region of Alaska and British Columbia. Landslides and fan deltas were identified from displacement signals captured by Interferometric Synthetic Aperture Radar (InSAR) interferograms of Sentinel-1 C-band Synthetic Aperture Radar images. The images were acquired at 12-day intervals from June to October from 2018 to 2020. We applied the persistent scatterer InSAR (PSInSAR) methods to images from both descending (scene P145) and ascending (scene P50) satellite tracks. We used PSInSAR results from the descending track as a primary means to identify ground movement and then used results from the ascending track to confirm the ground movement. The overlapping area covered by both images is 14,780 sq. km.
Each polygon in the shapefile and .kmz file outlines an area of movi ...
Laos administrative level 0 (country), 1 (province / khoueng or prefecture / kampheng nakhon), and 2 (district / muang) boundary shapefiles, KMZ files, and EMF files, geodatabase, and gazetteer
These shapefiles are suitable for database or GIS linkage to the Lao People's Democratic Republic levels 0-2 Population Statistics COD-PS CSV tables.
This file contains points that describe locations of oil shale core holes that contain nahcolite in the state of Colorado and is available as an ESRI shapefile, Google Earth KMZ file, and ASCII text file.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.