Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.
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).
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 polygon files contains 2015-2016 school-year data delineating school attendance boundaries. These data were collected and processed as part of the School Attendance Boundary Survey (SABS) project which was funded by NCES to create geography delineating school attendance boundaries. Original source information that was used to create these boundary files were collected were collected over a web-based self-reporting system, through e-mail, and mailed paper maps. The web application provided instructions and assistance to users via a user guide, a frequently asked questions document, and instructional videos. Boundaries supplied outside of the online reporting system typically fell into one of six categories: a digital geographic file, such as a shapefile or KML file; digital image files, such as jpegs and pdfs; narrative descriptions; an interactive web map; Excel or pdf address lists; and paper maps. 2015 TIGER/line features (that consist of streets, hydrography, railways, etc.) were used to digitize school attendance boundaries and was the primary source of information used to digitize analog information. This practice works well as most school attendance boundaries align with streets, railways, water bodies and similar line features included in the 2015 TIGER/line "edges" files. In those few cases in which a portion of a school attendance boundary serves both sides of a street contractor staff used Esri’s Imagery base map to estimate the property lines of parcels. The data digitized from analog maps and verbal descriptions do not conform to cadastral data (and many of the original GIS files created by school districts do not conform with cadastral or parcel data).The SABS 2015-2016 file uses the WGS 1984 Web Mercator Auxiliary Sphere coordinate system.Additional information about SABS can be found on the EDGE website.The SABS dataset is intended for research purposes only and reflects a single snapshot in time. School boundaries frequently change from year to year. To verify legal descriptions of boundaries, users must contact the school district directly.All information contained in this file is in the public _domain. Data users are advised to review NCES program documentation and feature class metadata to understand the limitations and appropriate use of these data.
Mineral resource occurrence data covering the world, most thoroughly within the U.S. This database contains the records previously provided in the Mineral Resource Data System (MRDS) of USGS and the Mineral Availability System/Mineral Industry Locator System (MAS/MILS) originated in the U.S. Bureau of Mines, which is now part of USGS. The MRDS is a large and complex relational database developed over several decades by hundreds of researchers and reporters. While database records describe mineral resources worldwide, the compilation of information was intended to cover the United States completely, and its coverage of resources in other countries is incomplete. The content of MRDS records was drawn from reports previously published or made available to USGS researchers. Some of those original source materials are no longer available. The information contained in MRDS was intended to reflect the reports used as sources and is current only as of the date of those source reports. Consequently MRDS does not reflect up-to-date changes to the operating status of mines, ownership, land status, production figures and estimates of reserves and resources, or the nature, size, and extent of workings. Information on the geological characteristics of the mineral resource are likely to remain correct, but aspects involving human activity are likely to be out of date.
This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. American Indian tribal subdivisions are administrative subdivisions of federally recognized American Indian reservations/off-reservation trust lands or Oklahoma tribal statistical areas (OTSAs). These entities are internal units of self-government and/or administration that serve social, cultural, and/or economic purposes for the American Indian tribe or tribes on the reservations/off-reservation trust lands or OTSAs. The Census Bureau obtains the boundary and attribute information for tribal subdivisions on federally recognized American Indian reservations and off-reservation trust lands from federally recognized tribal governments through the Census Bureau's Boundary and Annexation Survey (BAS). For the 2020 Census, the boundaries for tribal subdivisions on OTSAs were also obtained from federally recognized tribal governments through the Participant Statistical Areas Program (PSAP). Note that tribal subdivisions do not exist on all reservations/off-reservation trust lands or OTSAs, rather only where they were submitted to the Census Bureau by the federally recognized tribal government for that area. The boundaries for American Indian tribal subdivisions are as of January 1, 2020, as reported by the federally recognized tribal governments through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries for tribal subdivisions on OTSAs are those reported as of January 1, 2020 through PSAP.
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).
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
Open Database License (ODbL) v1.0https://www.opendatacommons.org/licenses/odbl/1.0/
License information was derived automatically
This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) :
tags['railway'] IN ('rail','station')
Features may have these attributes:
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.
This data set provides a generalized outline of the 72 counties in Wisconsin. The data is derived from 1:24,000-scale sources.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This feature class contains county boundaries for all 64 Colorado counties and 2010 US Census attributes data describing the population within each county.
Retirement Notice: This item is in mature support as of October 2023 and will retire in December 2025. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. This layer shows the Municipality level boundary of South Africa in 2021. The boundaries are optimized to support both visualization and analysis in ArcGIS Online. Each set of boundaries contains name, ID, and/or population counts for context. The layers can be enhanced with additional attributes using data enrichment tools in ArcGIS Online.Additional boundaries for South Africa are available in a hierarchy of geographies that nest into each other. These layers were published in June 2022. South Africa Administrative BoundariesCountryProvinceDistrictMunicipalityMainPlaceSubPlaceSmallArea
Una división administrativa, órgano administrativo, unidad administrativa, o subdivisión del territorio, es una parte de un país u región, delimitada con el propósito de mejorar, planificar o hacer más eficiente su administración.Las subregiones-provincias como unidad administrativa corresponden a subdivisiones al interior de los departamentos de Colombia e históricamente han sido reconocidas como tales (Mendoza, 1989). La mayoría de los departamentos presentan históricamente este tipo de organización territorial (provincia/subregión) como por ejemplo los departamentos de: Antioquia, Boyacá, Nariño y Cundinamarca, entre otros.El propósito de la publicación de la capa de subregiones-provincias, es facilitar la estandarización de nombres y códigos, la difusión y publicación de resultados de investigaciones demográficas, sociales, económicas, ambientales, judiciales, entre otras, así como, una base para suplir las necesidades de información más detallada, útil en la toma de decisiones para las entidades territoriales en las etapas del ordenamiento territorial y ambiental.Para generar la capa de Subregión-provincia se partió de la revisión de información histórica, cartográfica y publicaciones en los departamentos del país y entidades del orden nacional como el DANE, en donde se identificaron los municipios que les pertenecen a cada una de las subregiones-provincias reconocidas en cada departamento. Posteriormente sobre la base cartográfica de municipios de SIGOT-IGAC de 2012 se realizó la asociación por los códigos de municipio del DANE, para finalmente y con el software GIS ArcMap, se realizó la generalización por el código asignado en la propuesta de la publicación del autor en 2013 “Propuesta de Codificación de Nuevas Divisiones Administrativas” y el nombre identificado para cada subregión-provincia en Colombia.La capa de Subregión-provincia cubre el territorio de Colombia, sobre el cual se identificaron estos tipos de unidades administrativas en los departamentos ypresenta los siguientes atributos:COD_DEPTO: Código DANE del DepartamentoCOD_SUBREGION: Código asignado a la Subregión - ProvinciaNOM_SUBREGION: Nombre de la Subregión - ProvinciaAutor: Josué López Gil (Ingeniero Catastral y Geodesta).Información de referencia: Datos alfanuméricos de referencia:DANE (2005): Tabla de provincias https://www.dane.gov.co/files/censo2005/provincias/subregiones.pdf.Página Web de las gobernaciones y Secretarias de Planeación de los departamentos de Colombia.López Gil, Josué (2013). “Propuesta de Codificación de Nuevas Divisiones Administrativas”, recuperado de http://www.dane.gov.co/candane/images/DT_DANE/Propuesta_de_codificacion.pdfCapa Geográfica de referencia (Polígono): SIGOT-IGAC 2012, Nivel de municipio de las capas temáticas recuperado de http://sigotn.igac.gov.co/sigotn/default.aspx
This dataset was created by TxDOT for internal purposes. TxDOT is not the authority for county boundary data for the state. These features were digitized by TxDOT from georeferenced USGS topo maps to enable the classification of roadway attributes for the purposes of satisfying federal and state reporting requirements, and to serve as a base layer for TxDOT's cartographic products. This version utilizes a generalized boundary along the coast, which is sometimes necessary for analysis in which it is important to encompass segments of roadways that travel over water. Roadways on bridges or causeways that span intracoastal waterways are not covered by detailed polygons that precisely follow the coastline, therefore a generalized boundary is needed for some types of analysis where it is important to preserve such relationships.Use at your own risk. Update Frequency: As NeededSource: Texas General Land OfficeSecurity Level: PublicOwned by TxDOT: FalseRelated LinksData Dictionary PDF [Generated 2025/03/14]
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.