Facebook
TwitterAttribution 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.
Facebook
TwitterThe 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.
Facebook
TwitterThe Unpublished Digital Geologic Map of Chickasaw National Recreation Area and Vicinity, Oklahoma is composed of GIS data layers and GIS tables in a 10.0 file geodatabase (chic_geology.gdb), a 10.0 ArcMap (.MXD) map document (chic_geology.mxd), and individual 10.0 layer (.LYR) files for each GIS data layer, an ancillary map information (.PDF) document (chic_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 (chic_gis_readme.pdf). Please read the chic_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.0 shapefile format contact Stephanie O’Meara (stephanie_o’meara@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 (chic_metadata_faq.html; available at http://nrdata.nps.gov/geology/gri_data/gis/chic/chic_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: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.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 14N, 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 Chickasaw National Recreation Area.
Facebook
TwitterThe Unpublished Digital Geologic-GIS Map of Fort Laramie National Historic Site and Vicinity, Wyoming is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (fola_geology.gdb), a 10.1 ArcMap (.mxd) map document (fola_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (fola_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 (fola_geology_gis_readme.pdf). Please read the fola_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 (fola_geology_metadata.txt or fola_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:31,680 and United States National Map Accuracy Standards features are within (horizontally) 16.1 meters or 52.8 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 13N, 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 Fort Laramie National Historic Site.
Facebook
Twitter
Facebook
TwitterThe 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.
Facebook
TwitterThe Unpublished Digital Geologic-GIS Map of the West Shasta Copper-Zinc District, California is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (wscz_geology.gdb), a 10.1 ArcMap (.mxd) map document (wscz_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (whis_geology_gis_readme.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 (whis_geology_gis_readme.pdf). Please read the whis_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 (wscz_geology_metadata.txt or wscz_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: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 10N, 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 Whiskeytown National Recreation Area.
Facebook
TwitterThe Unpublished Digital Geologic-GIS Map of the French Gulch 15' Quadrangle, California is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (freg_geology.gdb), a 10.1 ArcMap (.mxd) map document (freg_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (whis_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 (whis_geology_gis_readme.pdf). Please read the whis_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 (freg_geology_metadata.txt or freg_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 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 10N, 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 Whiskeytown National Recreation Area.
Facebook
TwitterThe Unpublished Digital Geologic-GIS Map of Theodore Roosevelt National Park and Vicinity, North Dakota is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (thro_geology.gdb), a 10.1 ArcMap (.mxd) map document (thro_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (thro_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 (thro_geology_gis_readme.pdf). Please read the thro_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: North Dakota 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 (thro_geology_metadata.txt or thro_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: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 13N, 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 Theodore Roosevelt National Park.
Facebook
Twitter
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
This feature layer contains the locations of Natural Gas Import/Export Pipeline Facilities along the borders between the Continental United States, Canada, and Mexico for the Homeland Infrastructure Foundation-Level (HIFLD) Database (https://hifld-dhs-gii.gov/HIFLD) as well as the Energy modeling and simulation community. A Natural Gas Import/Export Pipeline Facility delivers natural gas in and out of the Continental United States between foreign countries.
Facebook
TwitterVector polygon map data of property parcels from New York State containing 2,789,211 features.
Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.
Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.
Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.
Additional metadata, including field descriptions, can be found at the NYS GIS Clearinghouse: http://gis.ny.gov/gisdata/inventories/details.cfm?DSID=1300.
© Contributing counties, NYS Office of Information Technology Services GIS Program Office (GPO) and NYS Department of Taxation and Finance’s Office of Real Property Tax Services (ORPTS).
Facebook
TwitterVector polygon map data of city limits from across the State of Texas containing 2142 features.
City limits GIS (Geographic Information System) data provides valuable information about the boundaries of a city, which is crucial for various planning and decision-making processes. Urban planners and government officials use this data to understand the extent of their jurisdiction and to make informed decisions regarding zoning, land use, and infrastructure development within the city limits.
By overlaying city limits GIS data with other layers such as population density, land parcels, and environmental features, planners can analyze spatial patterns and identify areas for growth, conservation, or redevelopment. This data also aids in emergency management by defining the areas of responsibility for different emergency services, helping to streamline response efforts during crises..
This city limits data is available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.
Facebook
TwitterThe Unpublished Digital Geologic-GIS Map of Hagerman Fossil Beds National Monument and Vicinity, Idaho is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (hafo_geology.gdb), a 10.1 ArcMap (.mxd) map document (hafo_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (hafo_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 (hafo_geology_gis_readme.pdf). Please read the hafo_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: Idaho 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 (hafo_geology_metadata.txt or hafo_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in Google Earth, ArcGIS 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 11N, 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 Hagerman Fossil Beds National Monument.
Facebook
TwitterVector polygon map data of property parcels from Harris County, Texas containing 1,410,276 features.
Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.
Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.
Available for viewing and sharing in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.
Facebook
TwitterThe Unpublished Digital Geologic Map of Glen Canyon National Recreation Area and Vicinity, Utah, Arizona is composed of GIS data layers complete with ArcMap 9.3 layer (.LYR) files, two ancillary GIS tables, a Map PDF document with ancillary map text, figures and tables, a FGDC metadata record and a 9.3 ArcMap (.MXD) Document that displays the digital map in 9.3 ArcGIS. These data formats also fully represent all of the features present on a GRI digital map, as well as containing related ancillary information GIS data tables. The data is also available as a 2.2 KMZ/KML file for use in Google Earth. 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: Utah Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation sections(s) of this metadata record (glca_metadata.xml; available at http://nrdata.nps.gov/glca/nrdata/geology/gis/glca_metadata.xml). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS 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.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.3 personal geodatabase (glca_geology.mdb), and as shapefile (.SHP) and DBASEIV (.DBF) table files. 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 Glen Canyon National Recreation Area, as well as Rainbow Bridge National Monument (RABR), Canyonlands National Park (CANY), Capitol Reef National Park (CARE) and Grand Canyon National Park (GRCA).
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
This nowCOAST™ time-enabled map service provides maps depicting the geographic coverage of the latest NOAA/National Weather Service (NWS) WATCHES, WARNINGS, ADVISORIES, and STATEMENTS for long-duration hazardous weather, marine weather, hydrological, oceanographic, wildfire, air quality, and ecological conditions which may or are presently affecting inland, coastal, and maritime areas. A few examples include Gale Watch, Gale Warning, High Surf Advisory, High Wind Watch, Areal Flood Warning, Coastal Flood Watch, Winter Storm Warning, Wind Chill Advisory, Frost Advisory, Tropical Storm Watch, Red Flag Warning, Air Stagnation Warning, and Beach Hazards Statement. (A complete list is given in the Background Information section below.) The coverage areas of these products are usually defined by county or sub-county boundaries. The colors used to identify the different watches, advisories, warnings, and statements are the same colors used by the NWS on their map at weather.gov. The NWS products for long-duration hazardous conditions are updated in the nowCOAST map service approximately every 10 minutes. For more detailed information about the update schedule, please see: http://new.nowcoast.noaa.gov/help/#section=updateschedule.
The coverage areas of these products are usually defined by county or sub-county boundaries, but for simplicity and performance reasons, adjacent WWAs of the same type, issuance, and expiration are depicted in this service as unified (merged/dissolved) polygons in the layers indicated with the suffix "(Dissolved Polygons)". However, a set of equivalent layers containing the original individual zone geometries are also included for querying purposes, and are indicated with the suffix "(Zone Polygons)". Corresponding zone polygon and dissolved polygon layers are matched together in group layers for each WWA category. The zone polygon layers are included in this service only to support query/identify operations (e.g., in order to retrieve the original zone geometry or other attributes such as a URL to the warning text bulletin) and thus will not be drawn when included in a normal map image request. Thus, the dissolved polygon layers should be used when requesting a map image (e.g. WMS GetMap or ArcGIS REST export operations), while the zone polygon layers should be used when performing a query (e.g. WMS GetFeatureInfo or ArcGIS REST query or identify operations).
The colors used to identify the different watches, advisories, warnings, and
statements are the same colors used by the NWS on their map at
http://www.weather.gov.
The NWS products for long-duration hazardous conditions are updated in the
nowCOAST™ map service approximately every 10 minutes.
For more detailed information about layer update frequency and timing, please reference the
nowCOAST™ Dataset Update Schedule.
Background Information
NWS watches depict the geographic areas where the risk of hazardous weather or hydrologic events has increased significantly, but their occurrence, location, and/or timing is still uncertain. A warning depicts where a hazardous weather or hydrologic event is occurring, is imminent, or has a very high probability of occurring. A warning is used for conditions posing a threat to life or property. Advisories indicate where special weather conditions are occurring, imminent, or have a very high probability of occurring but are less serious than a warning. They are for events that may cause significant inconvenience, and if caution is not exercised, could lead to situations that may threaten life and/or property. Statements usually contain updated information on a warning and are used to let the public know when a warning is no longer in effect. NWS issues over 75 different types of watches, warnings, and advisories (WWAs). WWAs are issued by the NWS regional Weather Forecast Offices (WFOs) and also the NWS Ocean Prediction Center, National Hurricane Center, Central Pacific Hurricane Center, and Storm Prediction Center.
The NWS WWAs are organized on the nowCOAST™ map viewer and within this map service by hazardous condition/threat layer groups and then by the geographic area (i.e. coastal & inland, immediate coast or maritime) for which the WWA product is targeted. This was done to allow users to select WWAs for hazardous conditions that are important to their operations or activities.
Please note that the Tropical Storm and Hurricane Warnings are provided in both the High Wind Hazards: Maritime Areas and Coastal & Inland Areas layer groups and the Flooding Hazards: Coastal Areas layer group. These warnings are included in the Flooding Hazards/Coastal Areas layer group because the NWS uses those warnings to inform the public that tropical storm or hurricane winds may be accompanied by significant coastal flooding but below the thresholds required for the issuance of a storm surge warning. In addition, a tropical storm or hurricane warning may remain in effect when dangerously high water or a combination of dangerously high water and waves continue, even though the winds may be less than hurricane or tropical storm force. The NWS does not issue a Coastal Flood Warning or Advisory when a tropical storm or hurricane warning is in effect; however that does not mean that there is not a significant coastal flooding threat.
</li>
<li>
Coastal & Inland Areas
<ul>
<li>High Wind Watch</li>
<li>Wind Advisory</li>
<li>Lake Wind Advisory</li>
<li>High Wind Warning</li>
<li>Tropical Storm Watch</li>
<li>Tropical Storm Warning</li>
<li>Hurricane Watch</li>
<li>Hurricane Warning</li>
</ul>
</li>
</ul>
Facebook
TwitterVector polygon map data of city limits from Houston, Texas containing 731 features.
City limits GIS (Geographic Information System) data provides valuable information about the boundaries of a city, which is crucial for various planning and decision-making processes. Urban planners and government officials use this data to understand the extent of their jurisdiction and to make informed decisions regarding zoning, land use, and infrastructure development within the city limits.
By overlaying city limits GIS data with other layers such as population density, land parcels, and environmental features, planners can analyze spatial patterns and identify areas for growth, conservation, or redevelopment. This data also aids in emergency management by defining the areas of responsibility for different emergency services, helping to streamline response efforts during crises..
This city limits data is available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.
Facebook
TwitterVector polygon map data of tax parcels from DeKalb County, Georgia containing 239, 731 features.
Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.
Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.
Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.
Facebook
TwitterVector polygon map data of property parcels from Cameron County, Texas containing 175,646 features.
Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.
Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.
Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.
Facebook
TwitterAttribution 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.