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.

This is an exercise on the use of Postal Code Conversion Files (PCCF) with GIS. (Note: Data associated with this exercise is available on the DLI FTP site under folder 1873-299.)

LANDISVIEW is a tool, developed at the Knowledge Engineering Laboratory at Texas A&M University, to visualize and animate 8-bit/16-bit ERDAS GIS format (e.g., LANDIS and LANDIS-II output maps). It can also convert 8-bit/16-bit ERDAS GIS format into ASCII and batch files. LANDISVIEW provides two major functions: 1) File Viewer: Files can be viewed sequentially and an output can be generated as a movie file or as an image file. 2) File converter: It will convert the loaded files for compatibility with 3rd party software, such as Fragstats, a widely used spatial analysis tool. Some available features of LANDISVIEW include: 1) Display cell coordinates and values. 2) Apply user-defined color palette to visualize files. 3) Save maps as pictures and animations as video files (*.avi). 4) Convert ERDAS files into ASCII grids for compatibility with Fragstats. (Source: http://kelab.tamu.edu/)

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).

Displacement risk indicator showing the number of housing units subject to conversion into condominiums summarized at the census tract level; available for every year from 2004 through the most recent year of available data.

This project maps the conversion from mid-20th century flood (and sprinkler irrigation) to sprinkler irrigation (center-pivot and other sprinkler), and other land types (fallow, crop, and flood remaining flood) in Montana, by 2019. This file contains results of mapping the conversion from mid-20th century flood (and sprinkler irrigation) to sprinkler irrigation (center-pivot and other sprinkler), and other land types (to cropland—C, hayland--H, fallow –FA, and sprinkler remaining sprinkler) in Montana, by 2019.Over the past 50 years, many producers in Montana have made changes to their irrigation practice and infrastructure in an effort to increase irrigation efficiency, defined as the ratio of water consumed by crops to water diverted or pumped (consumed water ÷ diverted water). Changes in the method of irrigation, especially conversion from flood to sprinkler irrigation, may have significant on-farm benefits such as reduced labor and increased production. Conversion can have both beneficial and adverse impacts on streamflow and aquatic ecosystems depending on local site-specific hydrogeologic conditions and how irrigation water is managed. As part of the Montana Water Center’s effort to better understand the effects of increased irrigation efficiency in Montana (Lonsdale et al. 2020), historic conversion from flood to sprinkler irrigation was analyzed using available agricultural statistics, maps from state and federal sources, and an independent Geographic Information Systems (GIS) analysis. This project presents the GIS analysis and maps the amount and spatial distribution of conversion from flood to sprinkler irrigation, between the mid-20th century and 2019. Historic mid-20th century irrigation was mapped in detail from 1943-1965 by the State Engineer’s Office and from 1966-1971 by the Montana Water Resources Board—the predecessor of the Montana Department of Natural Resources and Conservation (DNRC). A scanned and georeferenced version of the Water Resources Surveys (WRS) was compared with maps of contemporary irrigated land (Montana Department of Revenue’s 2019 Final Land Unit Classification—DORFLU2019) to estimate the area of land converted from flood to sprinkler irrigation. Prior to GIS analysis, both datasets were edited to ensure valid comparison between irrigated field mapping conducted at the two points in time. To estimate the amount of conversion from flood to sprinkler irrigation, and other uses, the GIS layers (WRS flood and sprinkler 1946-1971 and DOR-FLU 2019) were overlain in ArcGIS; then the clipping erase functions were used to select the WRS flood and sprinkler parcels that were shown as sprinkler irrigated in 2019. Additional conversion classes were also mapped that represent the changes from WRS flood and sprinkler to cropland, hayland and fallow, and WRS sprinkler remaining sprinkler.

Please see the main project report: "Montana Conversion from Flood to Sprinkler Irrigation between Mid 20th Century and 2019.pdf" and Appendix C. "Methods and data for GIS mapping of conversion from flood to sprinkler irrigation.pdf" for details of the analysis and results. https://www.hydroshare.org/resource/15392cb3617b4519af6ae8972f603502/data/contents/Appendix_C._Methods_and_data_for_GIS_mapping_of_conversion_from_flood_to_sprinkler_irrigation.pdf

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

The ZIP file consist of GIS files with information about the excavations, findings and other metadata about the archaeological survey.

Want to keep the data in your Hosted Feature Service current? Not interested in writing a lot of code?Leverage this Python Script from the command line, Windows Scheduled Task, or from within your own code to automate the replacement of data in an existing Hosted Feature Service. It can also be leveraged by your Notebook environment and automatically managed by the MNCD Tool!See the Sampler Notebook that features the OverwriteFS tool run from Online to update a Feature Service. It leverages MNCD to cache the OverwriteFS script for import to the Notebook. A great way to jump start your Feature Service update workflow! RequirementsPython v3.xArcGIS Python APIStored Connection Profile, defined by Python API 'GIS' module. Also accepts 'pro', to specify using the active ArcGIS Pro connection. Will require ArcGIS Pro and Arcpy!Pre-Existing Hosted Feature ServiceCapabilitiesOverwrite a Feature Service, refreshing the Service Item and DataBackup and reapply Service, Layer, and Item properties - New at v2.0.0Manage Service to Service or Service to Data relationships - New at v2.0.0Repair Lost Service File Item to Service Relationships, re-enabling Service Overwrite - New at v2.0.0'Swap Layer' capability for Views, allowing two Services to support a View, acting as Active and Idle role during Updates - New at v2.0.0Data Conversion capability, able to invoke following a download and before Service update - New at v2.0.0Includes 'Rss2Json' Conversion routine, able to read a RSS or GeoRSS source and generate GeoJson for Service Update - New at v2.0.0Renamed 'Rss2Json' to 'Xml2GeoJSON' for its enhanced capabilities, 'Rss2Json' remains for compatability - Revised at v2.1.0Added 'Json2GeoJSON' Conversion routine, able to read and manipulate Json or GeoJSON data for Service Updates - New at v2.1.0Can update other File item types like PDF, Word, Excel, and so on - New at v2.1.0Supports ArcGIS Python API v2.0 - New at v2.1.2RevisionsSep 29, 2021: Long awaited update to v2.0.0!Sep 30, 2021: v2.0.1, Patch to correct Outcome Status when download or Coversion resulted in no change. Also updated documentation.Oct 7, 2021: v2.0.2, workflow Patch correcting Extent update of Views when Overwriting Service, discovered following recent ArcGIS Online update. Enhancements to 'datetimeUtil' Support script.Nov 30, 2021: v2.1.0, added new 'Json2GeoJSON' Converter, enhanced 'Xml2GeoJSON' Converter, retired 'Rss2Json' Converter, added new Option Switches 'IgnoreAge' and 'UpdateTarget' for source age control and QA/QC workflows, revised Optimization logic and CRC comparison on downloads.Dec 1, 2021: v2.1.1, Only a patch to Conversion routines: Corrected handling of null Z-values in Geometries (discovered immediately following release 2.1.0), improve error trapping while processing rows, and added deprecation message to retired 'Rss2Json' conversion routine.Feb 22, 2022: v2.1.2, Patch to detect and re-apply case-insensitive field indexes. Update to allow Swapping Layers to Service without an associated file item. Added cache refresh following updates. Patch to support Python API 2.0 service 'table' property. Patches to 'Json2GeoJSON' and 'Xml2GeoJSON' converter routines.Sep 5, 2024: v2.1.4, Patch service manager refresh failure issue. Added trace report to Convert execution on exception. Set 'ignore-DataItemCheck' property to True when 'GetTarget' action initiated. Hardened Async job status check. Update 'overwriteFeatureService' to support GeoPackage type and file item type when item.name includes a period, updated retry loop to try one final overwrite after del, fixed error stop issue on failed overwrite attempts. Removed restriction on uploading files larger than 2GB. Restores missing 'itemInfo' file on service File items. Corrected false swap success when view has no layers. Lifted restriction of Overwrite/Swap Layers for OGC. Added 'serviceDescription' to service detail backup. Added 'thumbnail' to item backup/restore logic. Added 'byLayerOrder' parameter to 'swapFeatureViewLayers'. Added 'SwapByOrder' action switch. Patch added to overwriteFeatureService 'status' check. Patch for June 2024 update made to 'managers.overwrite' API script that blocks uploads > 25MB, API v2.3.0.3. Patch 'overwriteFeatureService' to correctly identify overwrite file if service has multiple Service2Data relationships.Includes documentation updates!

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a GIS-usable format employing three fundamental processes; (1) orthorectify, (2) digitize, and (3) database enhancement. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 12, using North American Datum of 1983 (NAD83). To produce a polygon vector coverage for use in GIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcInfo (Version 8.0.2, Environmental Systems Research Institute, Redlands, California). In ArcTools, we used the ArcScan utility to trace the polygon data and produce ArcInfo vector-based coverages. We digitally assigned map attribute codes (both map class codes and physiognomic modifier codes) to the polygons, and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the 78 individual coverages into a seamless map coverage of GNP and immediate environs. We synchronized polygons and attributes along the boundary between the GNP and WLNP map coverages. Although GNP and WLNP are two separate map coverages, they are seamless in the sense they edge tie perfectly in both polygon location and map attribute.

GIS and concepts, tools and data. Why would anyone want a Postal Code Conversion File (PCCF) or PCCFRF? How do you create your neighbourhood using DLI data and postal codes using SPSS and a few handy steps that will make you look and sound like a genius to your students, director and president?

Sample data in ESRI Shapefile format available for download for testing purposes.

Context

This dataset is part of a series that contains three other datasets:

• UN SDG - EU 27 sample datamart (subset for 7 KPIs)
• Selected Indicators from World Bank 2000-2019: 33 indicators from World Bank website for a data project
• EU 27 Energy sources - consumption 1990-2018 / energy production, import, export by source - consumption by sector

Content

Dataset components

Sources

Processing done

Source: A

Converted .shp files (same name as the one under "dataset components") into CSV by using GDAL 3.0.4, released 2020/01/28, offline, under Windows 10, using the following command line: ogr2ogr -f CSV

Source: B

The data from this source for the time being are not uploaded due to errors in processing the sources (i.e. formatting errors in both .shp files and, when available, the .csv conversion provided by the source).

Anyway, if interested: the list of all the location as of 2011 is within the ZIP file Localita_2011_Point.csv from "Località italiane (shp)"

Selected the ZIP file containing the set of files WGS 84 UTM Zona 32n, latest available as of 2020-12-06: 2011

Release date and timeframe coverage

The collated dataset was released on 2020-12-06.

No timeframe coverage information available (the "localita" file is stated by ISTAT as updated at 2011).

Acknowledgements

Thanks to EEA and ISTAT for publishing the data

Inspiration

Connecting different data points to identify potential correlations, as part of my knowledge update/learning process (and to complement my other publication activities).

As part of a long-term publishing project (started in 2015 at Expo2015 in Milan), routinely share data that collect along my writing journey- generally via articles on my website on business and social change.

The Raster Based GIS Coverage of Mexican Population is a gridded coverage (1 x 1 km) of Mexican population. The data were converted from vector into raster. The population figures were derived based on available point data (the population of known localities - 30,000 in all). Cell values were derived using a weighted moving average function (Burrough, 1986), and then calculated based on known population by state. The result from this conversion is a coverage whose population data is based on square grid cells rather than a series of vectors. This data set is produced by the Columbia University Center for International Earth Science Information Network (CIESIN) in collaboration with the Instituto Nacional de Estadistica Geografia e Informatica (INEGI).

[Metadata] Description: Land Use Land Cover of main Hawaiian Islands as of 1976Source: 1:100,000 1976 Digital GIRAS (Geographic Information Retrieval and Analysis) files. Land Use and Land Cover (LULC) data consists of historical land use and land cover classification data that was based primarily on the manual interpretation of 1970's and 1980's aerial photography. Secondary sources included land use maps and surveys. There are 21 possible categories of cover type. The spatial resolution for all LULC files will depend on the format and feature type. Files in GIRAS format will have a minimum polygon area of 10 acres (4 hectares) with a minimum width of 660 feet (200 meters) for manmade features. Non-urban or natural features have a minimum polygon area of 40 acres (16 hectares) with a minimum width of 1320 feet (400 meters). Files in CTG format will have a resolution of 30 meters. May 2024: Hawaii Statewide GIS Program staff removed extraneous fields that had been added as part of the 2016 GIS database conversion and were no longer needed.For additional information, please refer to https://files.hawaii.gov/dbedt/op/gis/data/lulc.pdf or contact Hawaii Statewide GIS Program, Office of Planning and Sustainable Development, State of Hawaii; PO Box 2359, Honolulu, HI 96804; (808) 587-2846; email: gis@hawaii.gov; Website: https://planning.hawaii.gov/gis.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. Converting delineations to a digital format involved four main procedures: a) preparation of manuscript maps b) input of the spatial data: c) populating of the attribute tables, and d) conversion to GIS. Each step included many quality control steps. Maps were prepared by pin-registering a clean sheet of mylar to each photo and transferring delineations to the new overlay in ink. Each manuscript map was edgematched to the adjoining sheet. Each photo was numbered, and each polygon on the photo was numbered in sequence. An attribute table was created containing a field each for the photo number, polygon sequence number, land use code, layer number, stature type, height, density, and floristic composition attributes.

The files in this data set were obtained from the Global Ionospheric Specification (GIS) derived from COSMIC-2 radio occultation data along with data from other sources. The GIS is normally available from the Department of Earth Sciences at the National Cheng Kung University of Taiwan as NetCDF files. (https://formosat7.earth.ncku.edu.tw) To make access easier for others to access I have converted two GIS files to csv files. These have been used to supplement observations from the GOLD (Global-scale Observations of Limb and Disk) mission, primarily night glow emissions at 135.6 nm. GOLD data are readily available from publicly available sources.

To achieve true data interoperability is to eliminate format and data model barriers, allowing you to seamlessly access, convert, and model any data, independent of format. The ArcGIS Data Interoperability extension is based on the powerful data transformation capabilities of the Feature Manipulation Engine (FME), giving you the data you want, when and where you want it.In this course, you will learn how to leverage the ArcGIS Data Interoperability extension within ArcCatalog and ArcMap, enabling you to directly read, translate, and transform spatial data according to your independent needs. In addition to components that allow you to work openly with a multitude of formats, the extension also provides a complex data model solution with a level of control that would otherwise require custom software.After completing this course, you will be able to:Recognize when you need to use the Data Interoperability tool to view or edit your data.Choose and apply the correct method of reading data with the Data Interoperability tool in ArcCatalog and ArcMap.Choose the correct Data Interoperability tool and be able to use it to convert your data between formats.Edit a data model, or schema, using the Spatial ETL tool.Perform any desired transformations on your data's attributes and geometry using the Spatial ETL tool.Verify your data transformations before, after, and during a translation by inspecting your data.Apply best practices when creating a workflow using the Data Interoperability extension.

We implemented automated workflows using Jupyter notebooks for each state. The GIS processing, crucial for merging, extracting, and projecting GeoTIFF data, was performed using ArcPy—a Python package for geographic data analysis, conversion, and management within ArcGIS (Toms, 2015). After generating state-scale LES (large extent spatial) datasets in GeoTIFF format, we utilized the xarray and rioxarray Python packages to convert GeoTIFF to NetCDF. Xarray is a Python package to work with multi-dimensional arrays and rioxarray is rasterio xarray extension. Rasterio is a Python library to read and write GeoTIFF and other raster formats. Xarray facilitated data manipulation and metadata addition in the NetCDF file, while rioxarray was used to save GeoTIFF as NetCDF. These procedures resulted in the creation of three HydroShare resources (HS 3, HS 4 and HS 5) for sharing state-scale LES datasets. Notably, due to licensing constraints with ArcGIS Pro, a commercial GIS software, the Jupyter notebook development was undertaken on a Windows OS.