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.
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.
PLEASE NOTE: These data do not include data over Tasmania. Please see links relevant to that area.
GEODATA TOPO 250K Series 3 is a vector representation of the major topographic features appearing on the 1:250,000 scale NATMAPs supplied in KML format and is designed for use in a range of commercial GIS software. Data is arranged within specific themes. All data is based on the GDA94 coordinate system.
GEODATA TOPO 250K Series 3 is available as a free download 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.
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, kml, Shapefile and MapInfo TAB
Release Date: 26 June 2006
This dataset shows the tiling grid and their IDs for Sentinel 2 satellite imagery. The tiling grid IDs are useful for selecting imagery of an area of interest.
Sentinel 2 is an Earth observation satellite developed and operated by the European Space Agency (ESA). Its imagery has 13 bands in the visible, near infrared and short wave infrared part of the spectrum. It has a spatial resolution of 10 m, 20 m and 60 m depending on the spectral band.
Sentinel-2 has a 290 km field of view when capturing its imagery. This imagery is then projected on to a UTM grid and made available publicly on 100x100 km2 tiles. Each tile has a unique ID. This ID scheme allows all imagery for a given tile to be located.
Provenance:
The ESA make the tiling grid available as a KML file (see links). We were, however, unable to convert this KML into a shapefile for deployment on the eAtlas. The shapefile used for this layer was sourced from the Git repository developed by Justin Meyers (https://github.com/justinelliotmeyers/Sentinel-2-Shapefile-Index).
Why is this dataset in the eAtlas?:
Sentinel 2 imagery is very useful for the studying and mapping of reef systems. Selecting imagery for study often requires knowing what the tile grid IDs are for the area of interest. This dataset is intended as a reference layer. The eAtlas is not a custodian of this dataset and copies of the data should be obtained from the original sources.
Data Dictionary:
Overview
Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.
Our self-hosted geospatial data cover administrative and postal divisions with up to 5 precision levels. All levels follow a seamless hierarchical structure with no gaps or overlaps.
The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.
Use cases for the Global Administrative Boundaries Database (Geospatial data, Map data)
In-depth spatial analysis
Clustering
Geofencing
Reverse Geocoding
Reporting and Business Intelligence (BI)
Product Features
Coherence and precision at every level
Edge-matched polygons
High-precision shapes for spatial analysis
Fast-loading polygons for reporting and BI
Multi-language support
For additional insights, you can combine the map data with:
Population data: Historical and future trends
UNLOCODE and IATA codes
Time zones and Daylight Saving Time (DST)
Data export methodology
Our location data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson
All geospatial data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.
Why companies choose our map data
Precision at every level
Coverage of difficult geographies
No gaps, nor overlaps
Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.
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.
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).
Overview
Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.
Our self-hosted GIS data cover administrative and postal divisions with up to 6 precision levels: a zip code layer and up to 5 administrative levels. All levels follow a seamless hierarchical structure with no gaps or overlaps.
The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.
Use cases for the Global Boundaries Database (GIS data, Geospatial data)
In-depth spatial analysis
Clustering
Geofencing
Reverse Geocoding
Reporting and Business Intelligence (BI)
Product Features
Coherence and precision at every level
Edge-matched polygons
High-precision shapes for spatial analysis
Fast-loading polygons for reporting and BI
Multi-language support
For additional insights, you can combine the GIS data with:
Population data: Historical and future trends
UNLOCODE and IATA codes
Time zones and Daylight Saving Time (DST)
Data export methodology
Our geospatial data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson
All GIS data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.
Why companies choose our map data
Precision at every level
Coverage of difficult geographies
No gaps, nor overlaps
Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Open data is the first step to an informed, transparent, and engaged floodplain management community throughout the United States and territories. Explore our data and tools, provide feedback on what you would like to see next, and find out about opportunities to get involved.This site provides floodplain management geospatial data that can be useful to support community preparedness, resiliency, research, and more. The data is available for download as CSV, KML, Shapefile, and accessible via web services to support application development and data visualization.
For updates about floodplain management data, guidance on metadata, and known
shapefile conversion issues, please contact Martin Waysome at martin.waysome@fema.dhs.gov.Hub Page Lineage:Site Last Major Update: 02/29/2024 Site Initial Creation: Created by Quentin Cummings (quentin.cummings@fema.dhs.gov) 01/22/2022Site Management: Martin Waysome, 01/02/2023
The Florida Wiildlife Corridor (layer name Florida_Wildlife_Corridor_2021.shp): This vector layer was created from the original raster grid 2021 version of the Florida Ecological Greenways Network (FEGN) by combining the Priority 1, Priority 2, and Priority 3 values in the raster layer and converting to a shapefile using the Raster to Polygon command with the simplify option to remove the jagged edges of the original raster layer, reduce file size, and the make conversion to a kml file feasible. The Florida Wildlife Corridor is now part of a new state law intended to protect the corridor through enhanced land protection planning and funding. The Florida Wildlife Corridor is defined in the state law as The Florida Wildlife Corridor represents the most important opportunities to protect a functionally connected statewide system of public and private conservation lands essential for protecting Florida's native biodiversity, water resources, and other ecosystem services while providing a sustainable natural resource economy including a variety of resource-based recreational activities.The FEGN guides OGT ecological greenway conservation efforts and promotes public awareness of the need for and benefits of a statewide ecological greenways network. It is also used as the primary data layer to inform the Florida Forever and other state and regional land acquisition programs regarding the location of the most important wildlife and ecological corridors and large, intact landscapes in the state. The FEGN identifies areas of opportunity for protecting a statewide network of ecological hubs (large areas of ecological significance) and linkages designed to maintain large landscape-scale ecological functions including priority species habitat and ecosystem services throughout the state. Inclusion in the FEGN means the area is either part of a large landscape-scale “hub”, or an ecological corridor connecting two or more hubs. Hubs indicate core landscapes that are large enough to maintain populations of wide-ranging or fragmentation-sensitive species including black bear or panther and areas that are more likely to support functional ecosystem services. Highest priorities indicate the most significant hubs and corridors in relation to completing a functionally connected statewide ecological network, but all priority levels have conservation value. FEGN Priorities 1, 2, and 3 are the most important for protecting a ecologically functional connected statewide network of public and private conservation lands, and these three priority levels (P1, P2, and P3) are now called the Florida Wildlife Corridor as per the Florida Wildlife Corridor legislation passed and signed into law by the Florida Legislature and Governor and 2021, which makes protection of these wildlife and ecological hubs and corridors a high priority as part of a strategic plan for Florida’s future. To accomplish this goal, we need robust state, federal, and local conservation land protection program funding for Florida Forever, Rural and Family Lands Protection Program, Natural Resources Conservation Service easements and incentives, federal Land and Waters Conservation Fund, payments for ecosystem services, etc.
Important Note: This item is in mature support as of October 2024 and will retire in December 2026. A new version of this item is available for your use.This layer presents National and State parks and forests, along with County, Regional and Local parks within the United States. It provides thousands of named parks and forests at many levels.This layer uses TomTom source from March 2023.
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.
Tornado TracksThis feature layer, utilizing data from the National Oceanic and Atmospheric Administration (NOAA), displays tornadoes in the United States, Puerto Rico and U.S. Virgin Islands between 1950 and 2022. A tornado track shows the route of a tornado. Per NOAA, "A tornado is a narrow, violently rotating column of air that extends from a thunderstorm to the ground. Because wind is invisible, it is hard to see a tornado unless it forms a condensation funnel made up of water droplets, dust and debris. Tornadoes can be among the most violent phenomena of all atmospheric storms we experience. The most destructive tornadoes occur from supercells, which are rotating thunderstorms with a well-defined radar circulation called a mesocyclone. (Supercells can also produce damaging hail, severe non-tornadic winds, frequent lightning, and flash floods.)"EF-5 Tornado Track (May 3, 1999) near Oklahoma City, OklahomaData currency: December 30, 2022Data source: Storm Prediction CenterData modifications: Added fields Calculated Month and DateFor more information: Severe Weather 101 - Tornadoes; NSSL Research: TornadoesSupport documentation: SPC Tornado, Hail, and Wind Database Format SpecificationFor feedback, please contact: ArcGIScomNationalMaps@esri.comNational Oceanic and Atmospheric AdministrationPer NOAA, its mission is "To understand and predict changes in climate, weather, ocean, and coasts, to share that knowledge and information with others, and to conserve and manage coastal and marine ecosystems and resources."
https://data.gov.tw/licensehttps://data.gov.tw/license
The Water Resources Agency integrates information on meteorology, rainfall, alerts, disasters, collapses, monitoring, flooding potential, debris flow, and hydrological resources to provide KML downloads. Users can visualize real-time situations using Google Earth.This dataset is linked to a list of KML (Keyhole Markup Language) files. The format is based on XML (eXtensible Markup Language) syntax standards and is developed and maintained by Keyhole, a company under Google, for expressing geographic annotations. Documents written in KML language are KML files, using the same XML file format, and are used in Google Earth-related software and GIS systems for the exchange of geographic data. The encoding of this data's KML fields is UTF-8.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Global EEZ layer are the layers gathered from gazetted datasets that the Pacific Community (SPC) has received from the project countries. In areas where there are no gazetted datasets provisional layers are being sourced from the Global Marine Regions database (https://www.marineregions.org/).
There are two layers available, he .shp file layer and the .kml layer which are being used by partners and member states in particular FFA for the Regional Fisheries Surveillance Center (RFSC).
117 original plate boundaries from Esri Data and Maps (2007) edited to better match 10 years of earthquakes, land forms and bathymetry from Mapping Our World's WSI_Earth image from module 2. Esri Canada's education layer of plate boundaries and the Smithsonian's ascii file from the download section of the 'This Dynamic Planet' site plate boundaries were used to compare the resulting final plate boundaries for significant differences.
World Countries Generalized represents generalized boundaries for the countries of the world as of August 2022. The generalized political boundaries improve draw performance and effectiveness at a global or continental level. This layer is best viewed out beyond a scale of 1:5,000,000.This layer's geography was developed by Esri and sourced from Garmin International, Inc., the U.S. Central Intelligence Agency (The World Factbook), and the National Geographic Society for use as a world basemap. It is updated annually as country names or significant borders change.
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.
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.
The Unpublished Digital Surficial Geologic-GIS Map of Gateway National Recreation Area and Vicinity, New Jersey and New York is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (gwsf_geology.gdb), a 10.1 ArcMap (.MXD) map document (gwsf_geology.mxd), individual 10.1 layer (.LYR) files for each GIS data layer, an ancillary map information (.PDF) document (gate_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 (gwsf_gis_readme.pdf). Please read the gwsf_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: New Jersey Geological Survey and New York State Museum. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (gwsf_metadata_faq.html; available at http://nrdata.nps.gov/geology/gri_data/gis/gate/gwsf_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:100,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: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 18N, 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 Gateway National Recreation Area.
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.