Shapefiles information containing the basic information about the spatial structure of the STIB-MIVB network: route of the lines and position of the stops of the "commercial" network, that is the basic itineraries "to" and "from".
Data from various sources, including 2018 and 2019 multibeam bathymetry data collected by the National Oceanic and Atmospheric Administration (NOAA) and the U.S. Geological Survey (USGS) were combined to create a composite 30-m resolution multibeam bathymetry surface of central Cascadia Margin offshore Oregon. These metadata describe the polygon shapefile that outlines and identifies each publicly available bathymetric dataset. The data are available as a polygon shapefile.
Attribution-NoDerivs 3.0 (CC BY-ND 3.0)https://creativecommons.org/licenses/by-nd/3.0/
License information was derived automatically
The seamless, county-wide parcel layer was digitized from official Assessor Parcel (AP) Maps which were originally maintained on mylar sheets and/or maintained as individual Computer Aided Design (CAD) drawing files (e.g., DWG). The CRA office continues to maintain the official AP Maps in CAD drawings and Information Systems Department/Geographic Information Systems (ISD/GIS) staff apply updates from these maps to the seamless parcel base in the County’s Enterprise GIS. This layer is a partial view of the Information Sales System (ISS) extract, a report of property characteristics taken from the County’s Megabyte Property Tax System (MPTS). This layer may be missing some attributes (e.g., Owner Name) which may not be published to the Internet due to privacy conditions under the California Public Records Act (CPRA). Please contact the Clerk-Recorder-Assessor (CRA) office at (707) 565-1888 for information on availability, associated fees, and access to other versions of Sonoma County parcels containing additional property characteristics.The seamless parcel layer is updated and published to the Internet on a monthly basis.The seamless parcel layer was developed from the source data using the general methodology outlined below. The mylar sheets were scanned and saved to standard image file format (e.g., TIFF). The individual scanned maps or CAD drawing files were imported into GIS software and geo-referenced to their corresponding real-world locations using high resolution orthophotography as control. The standard approach was to rescale and rotate the scanned drawing (or CAD file) to match the general location on the orthophotograph. Then, appropriate control points were selected to register and rectify features on the scanned map (or CAD drawing file) to the orthophotography. In the process, features in the scanned map (or CAD drawing file) were transformed to real-world coordinates, and line features were created using “heads-up digitizing” and stored in new GIS feature classes. Recommended industry best practices were followed to minimize root mean square (RMS) error in the transformation of the data, and to ensure the integrity of the overall pattern of each AP map relative to neighboring pages. Where available Coordinate Geometry (COGO) & survey data, tied to global positioning systems (GPS) coordinates, were also referenced and input to improve the fit and absolute location of each page. The vector lines were then assembled into a polygon features, with each polygon being assigned a unique identifier, the Assessor Parcel Number (APN). The APN field in the parcel table was joined to the corresponding APN field in the assessor property characteristics table extracted from the MPTS database to create the final parcel layer. The result is a seamless parcel land base, each parcel polygon coded with a unique APN, assembled from approximately 6,000 individual map page of varying scale and accuracy, but ensuring the correct topology of each feature within the whole (i.e., no gaps or overlaps). The accuracy and quality of the parcels varies depending on the source. See the fields RANK and DESCRIPTION fields below for information on the fit assessment for each source page. These data should be used only for general reference and planning purposes. It is important to note that while these data were generated from authoritative public records, and checked for quality assurance, they do not provide survey-quality spatial accuracy and should NOT be used to interpret the true location of individual property boundary lines. Please contact the Sonoma County CRA and/or a licensed land surveyor before making a business decision that involves official boundary descriptions.
This data publication is a compilation of six different multibeam surveys covering the previously unmapped Queen Charlotte Fault offshore southeast Alaska and Haida Gwaii, Canada. These data were collected between 2005 and 2018 under a cooperative agreement between the U.S. Geological Survey, Natural Resources Canada, and the National Oceanic and Atmospheric Administration. The six source surveys from different multibeam sonars are combined into one terrain model with a 30-meter resolution. A complementary polygon shapefile records the extent of each source survey in the output grid.
Attribution-NonCommercial-ShareAlike 4.0 (CC BY-NC-SA 4.0)https://creativecommons.org/licenses/by-nc-sa/4.0/
License information was derived automatically
This file contains European countries in a shapefile format that can be used in python, R or matlab. The file has been created by Drin Marmullaku based on GADM version 4.1 (https://gadm.org/) and distributed according to their license (https://gadm.org/license.html).
Please cite as: Sevdari, Kristian; Marmullaku, Drin (2023). Shapefile of European countries. Technical University of Denmark. Dataset. https://doi.org/10.11583/DTU.23686383 This dataset is distributed under a CCBY-NC-SA 4.0 license
Using the data to create maps for publishing of academic research articles is allowed. Thus you can use the maps you made with GADM data for figures in articles published by PLoS, Springer Nature, Elsevier, MDPI, etc. You are allowed (but not required) to publish these articles (and the maps they contain) under an open license such as CC-BY as is the case with PLoS journals and may be the case with other open access articles. Data for the following countries is covered by a a different license Austria: Creative Commons Attribution-ShareAlike 2.0 (source: Government of Austria)
This shapefile contains drains that are maintained by Eaton County, Michigan Drains Office. This dataset has been in a state of non-maintenance for many years and has known issues with completeness and accuracy. The dataset was created by the Eaton County Drains Office circa 2008. The features in this shapefile estimate the rough location of the centerline of the drain right-of-way as legally described.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Download .zipThis is a statewide digital version of the Hydrography layer of the published USGS 1:24OOO-scale topographic map series. It was created from DLG files of each scanned 7.5-minute quad map, using custom ARC/INFO software routines which did the following steps: convert from DLG format to coverage format project from UTM to StatePlane map projection rubbersheet map sheet corners to exact computed quad-corner coordinates run semi-automated Edgematching procedure which joins hydrography lines along the quad edges, using distance-offset (maximum of 100 feet) and attribute-match criteria to determine which lines to join. merge the individual quad coverages and dissolve the quad-edge lines Processing was done using Double Precision coordinates and math, with processing tolerance (Fuzzy) of 1 foot.
In the Database/Dataset Section the items CMAJOR and CMINOR represent coded pairs and are documented together. Up to five pairs in the pat and four pairs in the aat may be present. These will be appear in the tables as CMAJOR1 CMINOR1 CMAJOR2 CMINOR2, etc.
The layer has been provided in both shape file and coverage format. In the case of the shape file separate shape files are provided for point, line, and polygon data. In the coverage format the line and polygon data is combined in one coverage. The shape files will be the choice of most users due to speed of drawing issues. Those users desiring to manipulate the original data may want to use the coverage format. All shapefiles have been combined for simplicities sake into one self extracting zip file which expands to about 500 megabytes. However, the value listed in the file size parameter of the metadata represents only the size of the particular shapefile being documented. Also it should be noted that the coverages contain redefined items which of necessity had to be split into separate items or omitted in the shape files because this option isn't available in shapefiles.
This layer documentation is for the Shapefile which includes line features.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesReal Estate & Land ManagementReal Estate and Lands Management2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov
This polygon shapefile describes the data sources used to create a composite 30-m resolution multibeam bathymetry surface of southern Cascadia Margin offshore Oregon and northern California.
https://maps.islandcountywa.gov/WebFiles/DataDownloads/Metadata/Contour25.htmlhttps://maps.islandcountywa.gov/WebFiles/DataDownloads/Metadata/Contour25.html
25' contours created from 2015 6" resolution Lidar data at a county-wide scale. Intended uses are for cartographic and analysis purposes.
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.
The Office of the Geographer’s Global Large Scale International Boundary Detailed Polygons file combines two datasets, the Office of the Geographer’s Large Scale International Boundary Lines and NGA shoreline data. The LSIB is believed to be the most accurate worldwide (non- W. Europe) international boundary vector line file available. The lines reflect U.S. government (USG) policy and thus not necessarily de facto control. The 1:250,000 scale World Vector Shoreline (WVS) coastline data was used in places and is generally shifted by several hundred meters to over a km. There are no restrictions on use of this public domain data. The Tesla Government PiX team performed topology checks and other GIS processing while merging data sets, created more accurate island shoreline in numerous cases, and worked closely with the US Dept. of State Office of the Geographer on quality control checks.
Methodology:
Tesla Government’s Protected Internet Exchange (PiX) GIS team converted the LSIB linework and the island data provided by the State Department to polygons. The LSIB Admin 0 world polygons (Admin 0 polygons) were created by conflating the following datasets: Eurasia_Oceania_LSIB7a_gen_polygons, Africa_Americas_LSIB7a_gen_polygons, Africa_Americas_LSIB7a, Eurasia_LSIB7a, additional updates from LSIB8, WVS shoreline data, and other shoreline data from United States Government (USG) sources.
The two simplified polygon shapefiles were merged, dissolved, and converted to lines to create a single global coastline dataset. The two detailed line shapefiles (Eurasia_LSIB7a and Africa_Americas_LSIB7a) were merged with each other and the coastlines to create an international boundary shapefile with coastlines. The dataset was reviewed for the following topological errors: must not self overlap, must not overlap, and must not have dangles. Once all topological errors were fixed, the lines were converted to polygons. Attribution was assigned by exploding the simplified polygons into multipart features, converting to centroids, and spatially joining with the newly created dataset. The polygons were then dissolved by country name.
Another round of QC was performed on the dataset through the data reviewer tool to ensure that the conversion worked correctly. Additional errors identified during this process consisted of islands shifted from their true locations and not representing their true shape; these were adjusted using high resolution imagery whereupon a second round of QC was applied with SRTM digital elevation model data downloaded from USGS. The same procedure was performed for every individual island contained in the islands from other USG sources.
After the island dataset went through another round of QC, it was then merged with the Admin 0 polygon shapefile to form a comprehensive world dataset. The entire dataset was then evaluated, including for proper attribution for all of the islands, by the Office of the Geographer.
The hydrographic polygon coverages were created using TIGER/LINE 2000 shapefile data gathered from ESRI's Geography Network. The individual county hydrography line shapefiles were processed into Arc/Info coverages and then appended together to create complete state coverages. They were then edited to remove unwanted features, leaving a state-by-state database of both important and navigable water features. Attributes were added to denote navigable features and names. Also, an attribute was added to the polygons to denote which were water and which were land features. The state databases were then appended together to create a single, nationwide hydrography network containing named arcs and polygons. These features also contain a state FIPS. Because some of the hydro features are represented by lines instead of polygons, the complete hydro dataset consists of 2 shapefiles, one for lines and one for polygons. They must be used together to paint a complete picture.
© US Census and ESRI This layer is sourced from maps.bts.dot.gov.
The hydrographic polygon coverages (NTAD 2015) were created using TIGER/LINE 2000 shapefile data gathered from ESRI's Geography Network. The individual county hydrography line shapefiles were processed into Arc/Info coverages and then appended together to create complete state coverages. They were then edited to remove unwanted features, leaving a state-by-state database of both important and navigable water features. Attributes were added to denote navigable features and names. Also, an attribute was added to the polygons to denote which were water and which were land features. The state databases were then appended together to create a single, nationwide hydrography network containing named arcs and polygons. These features also contain a state FIPS. Because some of the hydro features are represented by lines instead of polygons, the complete hydro dataset consists of 2 shapefiles, one for lines and one for polygons. They must be used together to paint a complete picture.
© US Census and ESRI
This shapefile contains tax parcel polygons for Eaton County, Michigan, USA. Because tax parcel information changes daily, this shapefile contains only geometry, the parcel identifier and a URL link to the current information for each parcel. Parcel geometries are not survey-grade and should not be used to make important decisions like where to build a structure or install a fence. In their current form, they are only useful in spatial terms for getting an inexact idea of where a parcel is located. If you need to know exactly where a property line falls, please consult a certified land surveyor. Parcel geometries will be updated either annually or bi-annually. New splits and combinations are typically not visible in the parcel geometry until changes become official via Board of Review in the following April.
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.
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.
Corresponding hydro-flattened Digital Terrain Model (DTM) files were created in Esri file geodatabase format. 1-foot contours were created from the hydro-flattened digital terrain model data and delivered in Esri file geodatabase format. The SEWRPC 2015 LiDAR project called for the Planning, Acquisition, processing and derivative products of LIDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1.2. The primary set of deliverable data was developed based on the following two horizontal projection/datum systems as specified in the contract: NAD83 (2011) State Plane Wisconson South Zone, US survey feet; NAVD88, US survey feet for Waukesha County LiDAR data was delivered in RAW flight line swath format, and processed to create Classified LAS 1.2 Files formatted to individual 10,000-foot x 10,000-foot tiles. Tile counts are listed below: Waukesha: 187 tiles
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
This is a part of the National Geophysical Data Center (NGDC) Seafloor Surficial Sediment (Deck 41) Data File. Deck 41 is an original data file created by the Marine Geology and Geophysics Group of NGDC from 1970-1975, abstracted from unpublished material contributed to NGDC by multiple groups of individuals. No updates of Deck 41 have been added since 1975. The data that comprise this portion of Deck 41 were generated by R.L. Wigley during 1965 aboard ALBATROSS IV cruises 65-2, 65-13, and 65-14.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
These data-sets are polygon shapefiles that represent flood inundation boundaries for 157 flooding scenarios in an 8-mile reach of the Papillion Creek near Offutt Air Force Base. These shapefiles were created by the U.S. Geological Survey (USGS) in cooperation with the U.S. Air Force, Offutt Air Force Base for use within the USGS Flood Inundation Mapping program. The flood-inundation maps, which can be accessed through the USGS Flood Inundation Mapping Science website at https://www.usgs.gov/mission-areas/water-resources/science/flood-inundation-mapping-fim-program, depict estimates of the areal extent and depth of flooding corresponding to selected water levels (stages) at the USGS streamgages on the Papillion Creek at Fort Crook, Nebr. (station 06610795) and Papillion Creek at Harlan Lewis Road near La Platte, Nebr. (station 06610798). Near-real-time stages at these streamgages may be obtained from the USGS National Water Information System web interface at https://doi.org/10. ...
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Abstract This dataset was created within the Bioregional Assessment Programme for cartographic purposes. Data has not been derived from any source datasets. Metadata has been compiled by the Bioregional Assessment Programme. Cartographic masks for map products GAL_210, used for clear annotation and masking unwanted features from report maps. Dataset History A shapefile was created for the use of masking data to highlight text. Method: * A new polygon shapefile was created with no contentShow full descriptionAbstract This dataset was created within the Bioregional Assessment Programme for cartographic purposes. Data has not been derived from any source datasets. Metadata has been compiled by the Bioregional Assessment Programme. Cartographic masks for map products GAL_210, used for clear annotation and masking unwanted features from report maps. Dataset History A shapefile was created for the use of masking data to highlight text. Method: * A new polygon shapefile was created with no content * The shapefile was then populated in an ArcMap editing session by digitizing polygons which surround text. * ArcMAP's Advanced Drawing Option was then used to mask data behind text. Dataset Citation Bioregional Assessment Programme (2015) Cartographic masks for map products GAL210. Bioregional Assessment Source Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/4bb5f4f2-bae9-44da-a5d7-398622e164df.
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.
Shapefiles information containing the basic information about the spatial structure of the STIB-MIVB network: route of the lines and position of the stops of the "commercial" network, that is the basic itineraries "to" and "from".