Facebook
TwitterIndividual boundary polylines were created by first making a point shapefile of the line endpoints or a series of points, then converting the points to a polyline. The point/polyline conversion was done using XTools 'Make One Polyline from Points' tool. Point locations were based on latitude/longitude coordinates given in the technical report or geographic landmark (i.e. islands, points, state/international boundary lines, etc.). Points requiring an azimuth bearing were created in a projected view (UTM Zone 17 NAD27) using the Distance and Azimuth Tools v. 1.6 extension developed by Jenness Enterprises.The polyline shapefiles created in step 1 and an existing polyline shapefile of the international boundary were merged together using the ArcView GeoProcessing Wizard.The shapefile generated in step 2 was converted to a line coverage using the ArcToolbox Conversion Tools - Feature Class to Coverage.The line coverage topology was cleaned and updated using the ArcInfo Workstation CLEAN (dangle length and fuzzy tolerance both set to 0.001) and BUILD commands.The boundary line coverage and an existing Lake Erie shoreline shapefile (derived from ESRI 100k data) were merged together using the ArcView GeoProcessing Wizard.The shapefile generated in step 5 was converted to a line coverage using the ArcToolbox Conversion Tools - Feature Class to Coverage.Topology of the boundary/shoreline coverage was cleaned and updated using the ArcInfo Workstation CLEAN (dangle length and fuzzy tolerance both set to 0.00001) and BUILD commands. BUILD was done for both line and polygon topology.The polygon feature from the coverage generate in step 7 was converted to a shapefile using Theme\Convert to Shapefile in ArcView.
Facebook
TwitterIndiana Reference Post point Inventory created as an ESRI point shapefile consisting of a Feature point geometry. The data set was compiled by Road Inventory of the Indiana GIS Department of Transportation (INDOT) . Dataset is classified as sde Feature Class. The Feature Class is projected Coordinate System: NAD 1983, UTM, Zone 16 N. The Projections is Transverse Mercator.Each Reference Post point Inventory is placed as to Position, Measure, and by Reference Post Name. The posts are "names" for known spots on the road. The names are sequentially numbered along the road. The Reference Post point Inventory is Dated as of 2006-2015.
Facebook
TwitterThose portions of Lake Huron grids 304 and 305 north of a line beginning at the southerly point of land on the easterly side of Dudley Bay (Cadogan Point); then running southwesterly in a straight line to the southeasterly end of Beaver Tail Point; then running westerly in a straight line to the southeasterly end of Whitefish Point in Mackinac County. Regulations: All commercial fishing is prohibited for the period from the Friday before Memorial Day through Labor Day only. Maps for general reference only: refer to text of Consent Decree 2000 for exact locations and provisions.Created a new polygon shapefile in ArcGIS 8.1. Digitized missing target area from Chippewa county 1:24,000 DRG. The new polygon feature was then commbined with the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer using the union tool from the geoprocessing wizard in Arc Map. The desired features were then selected and exported as a new shapefile. Created a new polygon shapefile in ArcGIS 8.1. A point was located on the USGS Mackinac county 1:24,000 DRG as outlined in the Consent Decree 2000 documentation. The new pollygon layer was created using the snapping tool in ArcMap. Starting form the above point location and heading in a clockwise direction (as outlined in the Consent Decree 2000 documentation) extending the polygon boundaries beyond the improved US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer created earlier. The new polygon feature was then commbined with the preceding layer using the union tool from the geoprocessing wizard in Arc Map. The desired features were then selected, exported as a new shapefile, and reprojected from Michigan georef to Decimal Degrees to create the final Les Cheneaux Island Closure C layer.The boundaries represented on consent decree maps are approximations based on the text contained in the 2000 Consent Decree. For legal descriptions of geographic extent or details pertaining to regulations for these representations refer to the original 2000 Consent Decree Document.
Facebook
TwitterThe files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a format usable in a geographic information system (GIS) by employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM), Zone 16, using the North American Datum of 1983 (NAD83). Orthorectify: We orthorectified the interpreted overlays by using OrthoMapper, a softcopy photogrammetric software for GIS. One function of OrthoMapper is to create orthorectified imagery from scanned and unrectified imagery (Image Processing Software, Inc., 2002). The software features a method of visual orientation involving a point-and-click operation that uses existing orthorectified horizontal and vertical base maps. Of primary importance to us, OrthoMapper also has the capability to orthorectify the photointerpreted overlays of each photograph based on the reference information provided. Digitize: To produce a polygon vector layer for use in ArcGIS (Environmental Systems Research Institute [ESRI], Redlands, California), we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format by using ArcGIS. In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map-attribute codes (both map-class codes and physiognomic modifier codes) to the polygons and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer. Geodatabase: At this stage, the map layer has only map-attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.
Facebook
TwitterDescription: Lake Huron grid 303 within the area encompassed by a line from Coats Point on Marquette Island along the western shore of said island to Cube Point; then due west to the shore of Brulee Point (Mismer Bay Point); then southeasterly along said shore to the southern tip of Brulee Point; then southeasterly to Coats Point on Marquette Island. Regulations: Tribal Commercial Fishing open to trap net fishing targeting whitefish shall be permitted in the area described above. Maps for general reference only: refer to text of Consent Decree 2000 for exact locations and provisions.Created a new polygon shapefile in ArcGIS 8.1. A point was located on the USGS Mackinac county 1:24,000 DRG as outlined in the Consent Decree 2000 documentation. The new pollygon layer was created using the snapping tool in ArcMap. Starting form the above point location and heading in a counter clockwise direction (as outlined in the Consent Decree 2000 documentation) extending the polygon boundaries beyond the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer. The new polygon feature was then commbined with the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer using the union tool from the geoprocessing wizard in Arc Map. The desired features were then selected, exported as a new shapefile, and reprojected from Michigan georef to Decimal Degrees to create the final Les Cheneaux Island Trap Net layer.The boundaries represented on consent decree maps are approximations based on the text contained in the 2000 Consent Decree. For legal descriptions of geographic extent or details pertaining to regulations for these representations refer to the original 2000 Consent Decree Document.
Facebook
TwitterThis specialized location dataset delivers detailed information about marina establishments. Maritime industry professionals, coastal planners, and tourism researchers can leverage precise location insights to understand maritime infrastructure, analyze recreational boating landscapes, and develop targeted strategies.
How Do We Create Polygons?
-All our polygons are manually crafted using advanced GIS tools like QGIS, ArcGIS, and similar applications. This involves leveraging aerial imagery, satellite data, and street-level views to ensure precision. -Beyond visual data, our expert GIS data engineers integrate venue layout/elevation plans sourced from official company websites to construct highly detailed polygons. This meticulous process ensures maximum accuracy and consistency. -We verify our polygons through multiple quality assurance checks, focusing on accuracy, relevance, and completeness.
What's More?
-Custom Polygon Creation: Our team can build polygons for any location or category based on your requirements. Whether it’s a new retail chain, transportation hub, or niche point of interest, we’ve got you covered. -Enhanced Customization: In addition to polygons, we capture critical details such as entry and exit points, parking areas, and adjacent pathways, adding greater context to your geospatial data. -Flexible Data Delivery Formats: We provide datasets in industry-standard GIS formats like WKT, GeoJSON, Shapefile, and GDB, making them compatible with various systems and tools. -Regular Data Updates: Stay ahead with our customizable refresh schedules, ensuring your polygon data is always up-to-date for evolving business needs.
Unlock the Power of POI and Geospatial Data
With our robust polygon datasets and point-of-interest data, you can: -Perform detailed market and location analyses to identify growth opportunities. -Pinpoint the ideal locations for your next store or business expansion. -Decode consumer behavior patterns using geospatial insights. -Execute location-based marketing campaigns for better ROI. -Gain an edge over competitors by leveraging geofencing and spatial intelligence.
Why Choose LocationsXYZ?
LocationsXYZ is trusted by leading brands to unlock actionable business insights with our accurate and comprehensive spatial data solutions. Join our growing network of successful clients who have scaled their operations with precise polygon and POI datasets. Request your free sample today and explore how we can help accelerate your business growth.
Facebook
TwitterFor purposes of this Decree only, the parties reserving the issue of the eastern boundary of the 1836 Treaty waters in Lake Huron, Grids 507 through 512, 606 through 611, 709, and those portions of grids 612, 613, 710, 711, and 810 which are north of a line from the mouth of the Thunder Bay River in a straight line northeast through the northeast corner of grid 711 to the international border. Regulations: Tribal commercial fishing by any method other than trap nets shall be prohibited except fishing for chubs with small mesh gill nets or small mesh trap nets. Trap net fishing in this zone shall be open only to Bay Mills and Sault Tribe trap net fishers. A total of four (4) trap net operations shall initially be authorized for this zone. Each trap net operation will be limited to twelve (12) trap nets within the zone. Additional operations may be authorized in the future by CORA based on data collected in previous years. Maps for general reference only: refer to text of Consent Decree 2000 for exact locations and provisions.Created a new point shapefile in ArcGIS 8.1. A point was located on the USGS Alpena county 1:24,000 DRG as outlined in the Consent Decree 2000 documentation. The point was generated at the mouth of the Thunder Bay River. We then created a new polygon shapefile in ArcGIS 8.1. The new pollygon layer was created using the snapping tool in ArcMap. Starting form the above point location and heading in a clockwise direction snapping to the vertices (as outlined in the Consent Decree 2000 documentation) of the MDNR (University of Michigan) Statistical Grid layer, extending the polygon boundaries beyond the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer, and finishing the sketch at the starting point. The new polygon feature was then commbined with the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer using the union tool from the geoprocessing wizard in Arc Map. The desired features were then selected, exported as a new shapefile, and reprojected from Michigan georef to Decimal Degrees to create the final Southern Lake Huron Trap Net Zone layer.The boundaries represented on consent decree maps are approximations based on the text contained in the 2000 Consent Decree. For legal descriptions of geographic extent or details pertaining to regulations for these representations refer to the original 2000 Consent Decree Document.
Facebook
TwitterThe following provisions for harbor closures shall apply to the area within one-half (0.5) mile of the break walls at the Hammond Bay Harbor of Refuge; provided, that in that portion of this closure that lies within the Bay Mills Small Boat Zone described as those portions of grids 505 and 506 which lie south of a line from Hammond Bay Harbor buoy to the northeast corner of grid 506. Regulations: The area within one-half (0.5) mile of the break walls at the Hammond Bay Harbor of Refuge will be closed January 1 through September 30. Maps for general reference only: refer to text of Consent Decree 2000 for exact locations and provisions.Created a new point shapefile in ArcGIS 8.1. A point was located on the USGS Presque Isle county 1:24,000 DRG as outlined in the Consent Decree 2000 documentation. The point was generated on the nautical light located at the northeast end of the northeast jetty. A 0.5 mile buffer was then generated from the point shapefile using the buffer wizard tool in Arc Map. This buffered point location was then commbined with the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer using the union tool from the geoprocessing wizard in Arc Map. The desired features were then selected, exported as a new shapefile, and reprojected from Michigan georef to Decimal Degrees to create the final Hammond Bay 0.5 mile Harbor Closure layer.The boundaries represented on consent decree maps are approximations based on the text contained in the 2000 Consent Decree. For legal descriptions of geographic extent or details pertaining to regulations for these representations refer to the original 2000 Consent Decree Document.
Facebook
TwitterThis dataset includes a point shapefile representing structural measurements taken from a study area near the South Kawishiwi Intrusion in the Duluth Complex, Minnesota and a line shapefile representing the surface traces of the structural measurements. The structural measurements point file consists of a compilation of data from multiple published and unpublished sources. The surface trace file was created from these point data using an ArcGIS toolbox 'surface trace' tool (Open-File Report 2019-1136). The surface trace lines represent the lateral extension, projected onto the ground surface, of a geologic feature represented by the structural measurements.
Facebook
TwitterSpider lines depict Euclidean distance-based routes that connect each pair of points. They are a useful tool for visualization. In landscape genetics this represents the isolation-by-distance hypothesis. Previously there were other 3rd party tools that achieved this on the Arcscripts website. Currently it appears that this functionality is only available with a Business Analyst license of ArcGIS. This tool make a few assumptions: 1. You wish to connect all pairs of points.2. You have a point shapefile.3. The point shapefile is in a projected coordinate system.4. The point shapefile has fields called "Easting" and "Northing" that represent the X and Y coordinates respectively. If these fields are not named this excatly then the tool will fail.5. You have a field that describes the name of the pairs of the site (point). Please do not use a geodatabase feature class.
Facebook
TwitterAttribution 3.0 (CC BY 3.0)https://creativecommons.org/licenses/by/3.0/
License information was derived automatically
An ArcGIS shapefile layer showing the extent of all extant and relic Adelie penguin (Pygoscelis adeliae) colonies at Whitney Point, Windmill Islands, February 2006. The field 'Status' describes each polygon as extant, relic or maximum. Extant refers to the area used by breeding birds in the summer 2005/06. Maximum refers to the historic maximal extent of the colony. Relic refers to any colony which was not occupied by any breeding pairs during 2005/06.
Positional accuracy is approx. 1-2 m, after accounting for dGPS errors and errors in identification of the boundaries of colonies. Mapping was conducted after the end of the breeding season, so boundaries were identified as the extent of nest pebbles/fresh faeces, and it was considered that they could be reliably identified to within 0.5m.
Data were acquired using a Trimble Pro XH differential GPS. This work was completed as part of ASAC project 1219 (ASAC_1219).
Also for this project, three aerial photographs of Whitney point showing the adelie penguin colonies and taken on 17 December 1990 were georeferenced.
These aerial photographs are film ANTC1219 run 54 frames 21 to 23.
Work on this project also utilised a Digital Elevation Model (DEM) created for Shirley Island. See the metadata record, 'A digital elevation model (DEM) and orthophoto of the Whitney Point area of the Windmill Islands, Antarctica' for more information (linked below).
Since the 2005/06 summer was a low-ice year the opportunity was also taken to survey with differential GPS a section of coastline about 230 metres long east of Whitney Point on Clark Peninsula. This section of coastline was ice free and accessible. The data was collected with differential GPS on 10 February 2006.
Facebook
TwitterTags Social system, socio-economic resources, justice, BES, Environmental Justice, Environmental disamentities, Zoning Board of Appeals Summary For use in the environmental injustices study of Baltimore relating to patterns of environmental disamenties in relation to low income/minority communities. Description This feature class layer is a point dataset of appeals to the Zoning Board of Appeals (ZBA) from 1938 to 1999 concerning identified environmental disamentities. The data was gathered from records from the Zoning Board of Appeals decisions since 1931 relating to environmental disamentities and to be used to examine environmental injustices involving low income/minority communities in Baltimore. To see if environmental injustices exist in Baltimore, this point layer will be overlayed with race/income data to determine if patterns of inequity exist. Points were placed manually using the associated addresses from the ZBA_master dataset. The ID number associated with each point is related to its appeal number from the Zoning Board of Appeals. Multiple points on the data layer have the same ZBA_ID number, making it a one-to-many relationship. This layer can be joined with the ZBA_master table using the "ZBA_point_relationship" and the field "ZBA_ID". Credits UVM Spatial Analysis Lab Use limitations None. There are no restrictions on the use of this dataset. The authors of this dataset make no representations of any kind, including but not limited to the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the data. Extent West -76.708848 East -76.527906 North 39.371642 South 39.199548 This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.
Facebook
TwitterThese data were collected under a cooperative agreement between the Massachusetts Office of Coastal Zone Management (CZM) and the U.S. Geological Survey (USGS), Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center (WHCMSC). Initiated in 2003, the primary objective of this program is to develop regional geologic framework information for the management of coastal and marine resources. Accurate data and maps of sea floor geology are important first steps toward protecting fish habitat, delineating marine resources, and assessing environmental changes due to natural or human impacts. The project is focused on the inshore waters of coastal Massachusetts, primarily in water depths of 5 to 30 meters (m) deep. Data collected for the mapping cooperative have been released in a series of USGS Open-File Reports (http://woodshole.er.usgs.gov/project-pages/coastal_mass/). The geophysical data were collected during a survey in 2013 during USGS Field Activity 2013-003-FA (http://cmgds.marine.usgs.gov/fan_info.php?fa=2013-003-FA) and cover approximately 185 square kilometers of the inner continental shelf.
Facebook
Twittersocial system, socio-economic resources, justice, BES, Environmental disamentities, Environmental Justice, Zoning Board of Appeals
Summary
For use in the environmental injustices study of Baltimore relating to patterns of environmental disamenties in relation to low income/minority communities.
Description
This feature class layer is a point dataset of authorizing ordinances from the Baltimore City Council and Mayor from 1930 until 1999 concerning identified environmental disamentities. The data was gathered from records from the City Council since 1930 relating to decisions concerning land-uses considered to be environmental disamentities and is to be used to examine environmental injustices involving low income/minority communities in Baltimore. To examine if environmental injustices exist in Baltimore, this point layer will be overlayed with race/income data to determine if patterns of inequity exist. Points were placed manually using the associated addresses from the Ordinance_master dataset and using ISTAR 2004 data in conjunction with Baltimore parcel data. The Ordinance_ID number associated with each point relates to its appeal number from the City Council. Multiple points on the data layer have the same Ordinance_ID. This point layer can be joined with the Ordinance_master data layer based on the field "Ordinance_ID" and using the relationship "Ordinance_point_relationship".
Credits
UVM Spatial Analysis Lab
Use limitations
None. There are no restrictions on the use of this dataset. The authors of this dataset make no representations of any kind, including but not limited to the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the data.
Extent
West -76.707701 East -76.526991
North 39.371885 South 39.200794
This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.
The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.
The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.
Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.
This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.
The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.
The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.
Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The dataset 'ds180_Chinook_pnts' is a product of the CalFish Adult Salmonid Abundance Database. Data in this shapefile are collected from point features, such as dams and hatcheries. Some escapement monitoring locations, such as spawning stock surveys, are logically represented by linear features. See the companion linear feature shapefile 'ds181_Chinook_ln' for information collected from stream reaches.
The CalFish Abundance Database contains a comprehensive collection of anadromous fisheries abundance information. Beginning in 1998, the Pacific States Marine Fisheries Commission, the California Department of Fish and Game, and the National Marine Fisheries Service, began a cooperative project aimed at collecting, archiving, and entering into standardized electronic formats, the wealth of information generated by fisheries resource management agencies and tribes throughout California.
The data format provides for sufficient detail to convey the relative accuracy of each population trend index record yet is simple and straight forward enough to be suited for public use. For those interested in more detail the database offers hyperlinks to digital copies of the original documents used to compile the information. In this way the database serves as an information hub directing the user to additional supporting information. This offers utility to field biologists and others interested in obtaining information for more in-depth analysis. Hyperlinks, built into the spatial data attribute tables used in the BIOS and CalFish I-map viewers, open the detailed index data archived in the on-line CalFish database application. The information can also be queried directly from the database via the CalFish Tabular Data Query. Once the detailed annual trend data are in view, another hyperlink opens a digital copy of the document used to compile each record.
During 2010, as a part of the Central Valley Chinook Comprehensive Monitoring Plan, the CalFish Salmonid Abundance Database was reorganized and updated. CalFish provides a central location for sharing Central Valley Chinook salmon escapement estimates and annual monitoring reports to all stakeholders, including the public. Annual Chinook salmon in-river escapement indices that were, in many cases, eight to ten years behind are now current though 2009. In some cases, multiple datasets were consolidated into a single, more comprehensive, dataset to more closely reflect how data are reported in the California Department of Fish and Game standard index, Grandtab.
Extensive data are currently available in the CalFish Abundance Database for California Chinook, coho, and steelhead. Major data categories include adult abundance population estimates, actual fish and/or carcass counts, counts of fish collected at dams, weirs, or traps, and redd counts. Harvest data has also been compiled for many streams.
This CalFish Abundance Database shapefile was generated from fully routed 1:100,000 hydrography. In a few cases streams had to be added to the hydrography dataset in order to provide a means to create shapefiles to represent abundance data associated with them. Streams added were digitized at no more than 1:24,000 scale based on stream line images portrayed in 1:24,000 Digital Raster Graphics (DRG).
The features in this layer represent the location for which abundance data records apply. In many cases there are multiple datasets associated with the same location, and so, features may overlap. Please view the associated datasets for detail regarding specific features. In CalFish these are accessed through the "link" field that is visible when performing an identify or query operation. A URL string is provided with each feature in the downloadable data which can also be used to access the underlying datasets.
The Chinook data that is available from the CalFish website is actually mirrored from the StreamNet website where the CalFish Abundance Database's tabular data is currently stored. Additional information about StreamNet may be downloaded at http://www.streamnet.org" STYLE="text-decoration:underline;">http://www.streamnet.org. Complete documentation for the StreamNet database may be accessed at http://www.streamnet.org/online-data/data_develop.html" STYLE="text-decoration:underline;">http://http://www.streamnet.org/def.html
Facebook
TwitterThe state of Tennessee is divided into 805 individual 7.5-minute topographic quadrangle maps. The Tennessee Department of Environment and Conservation (TDEC) maintains an archive of paper maps that were utilized for estimating groundwater well locations. Each well location was plotted by hand and marked with corresponding water well data. These hand-plotted locations represent the most accurate spatial information for each well but exist solely in paper format. To create the shapefile of the well location data for this data release, individual paper maps were scanned and georeferenced. From these georeferenced map images (GRI), the hand-plotted well locations were digitized into a shapefile of point data using ArcGIS Pro. The shapefile is contained in "TN_waterwell.zip," which contains locations for 8,826 points from the first 200 7.5-minute quadrangles in Tennessee (sorted alphabetically) from Adair 438NW through Harriman 123NE. While some spring locations are included in this dataset, it does not provide a comprehensive collection of spring data. Attribute data includes quad name, drawing number, and hand-written identification data that was transcribed from the topographic maps. Latitude and longitude coordinates (decimal degrees) were populated. Data projection is USA Contiguous Albers Equal Area Conic USGS (meters). A table of attribute data is included in this data release as "TN_waterwells_table.xlsx." Detailed descriptions of the attributes can be found in the accompanying metadata file named "TN_waterwells_metadata.xml."
Facebook
TwitterU.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
In September 2018, the USGS Woods Hole Coastal and Marine Science Center (WHCMSC), in collaboration with the US Army Corps of Engineers (USACE), conducted high-resolution geophysical mapping and sediment sampling to determine the distribution of historical mine tailings on the floor of Lake Superior. Large amounts of waste material from copper mining, locally known as “stamp sands”, were dumped into the lake in the early 20th century, with wide-reaching consequences that have continued into the present day. Mapping was focused offshore of the town of Gay on the Keweenaw Peninsula of Michigan, where ongoing erosion and re-deposition of the stamp sands has buried miles of native, white-sand beaches and is steadily encroaching south onto Buffalo Reef, a large area of cobble/boulder substrate that supports productive fisheries in the lake. The objectives of this cooperative mapping project are to develop a framework for scientific research and provide baseline information required f ...
Facebook
TwitterThe Geological Atlas of the Western Canada Sedimentary Basin was designed primarily as a reference volume documenting the subsurface geology of the Western Canada Sedimentary Basin. This GIS dataset is one of a collection of shapefiles representing part of Chapter 10 of the Atlas, Devonian Elk Point Group of the Western Canada Sedimentary Basin, Figure 20, Elk Point Structure. Shapefiles were produced from archived digital files created by the Alberta Geological Survey in the mid-1990s, and edited in 2005-06 to correct, attribute and consolidate the data into single files by feature type and by figure.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The CalFish Abundance Database contains a comprehensive collection of anadromous fisheries abundance information. Beginning in 1998, the Pacific States Marine Fisheries Commission, the California Department of Fish and Game, and the National Marine Fisheries Service, began a cooperative project aimed at collecting, archiving, and entering into standardized electronic formats, the wealth of information generated by fisheries resource management agencies and tribes throughout California.
Extensive data are currently available for chinook, coho, and steelhead. Major data categories include adult abundance population estimates, actual fish and/or carcass counts, counts of fish collected at dams, weirs, or traps, and redd counts. Harvest data has also been compiled for many streams.
This CalFish Abundance Database shapefile was generated from fully routed 1:100,000 hydrography. In a few cases streams had to be added to the hydrography dataset in order to provide a means to create shapefiles to represent abundance data associated with them. Streams added were digitized at no more than 1:24,000 scale based on stream line images portrayed in 1:24,000 Digital Raster Graphics (DRG).
These features represent abundance information resulting from counts at weirs, fish ladders, or other point-type monitoring protocols such as beach seining. The point features in this layer typically represent the location for which abundance data records apply. In many cases there are multiple datasets associated with the same point location, and so, point features overlap. Please view the associated datasets for detail regarding specific features. In CalFish these are accessed through the "link" field that is visible when performing an identify or query operation. A URL string is provided with each feature in the downloadable data which can also be used to access the underlying datasets.
The coho data that is available via the CalFish website is actually linked directly to the StreamNet website where the database's tabular data is currently stored. Additional information about StreamNet may be downloaded at http://www.streamnet.org" STYLE="text-decoration:underline;">http://www.streamnet.org. Complete documentation for the StreamNet database may be accessed at http://www.streamnet.org/online-data/data_develop.html" STYLE="text-decoration:underline;">http://http://www.streamnet.org/def.html
Facebook
TwitterDHSVM configurations require spatial information for each point included as an input time series: elevation (m), latitude (m; UTM), longitude (m, UTM). The steps required to calculate this information are outlined in this HydroShare resource which includes sample scripts to export the point shapefile table from ArcGIS, calculate the UTM values, generate tables of latitude, longitude, and elevation, and convert the tables into DHSVM text format in a list for the model configuration file. The point shapefiles for the 8 Chehalis subbasins are also compressed and available in this resource.
To run the model, the input file lists each grid cell in the following format (example for 1 point in a list).
Station Name 1 = data_46.53125_-123.28125
North Coordinate 1 = 5153114.279000
East Coordinate 1 = 478431.528300
Elevation 1 = 290
Station File 1 = /civil/shared/ecohydrology/christina/forcs_dhsvm/data_46.53125_-123.28125
Facebook
TwitterIndividual boundary polylines were created by first making a point shapefile of the line endpoints or a series of points, then converting the points to a polyline. The point/polyline conversion was done using XTools 'Make One Polyline from Points' tool. Point locations were based on latitude/longitude coordinates given in the technical report or geographic landmark (i.e. islands, points, state/international boundary lines, etc.). Points requiring an azimuth bearing were created in a projected view (UTM Zone 17 NAD27) using the Distance and Azimuth Tools v. 1.6 extension developed by Jenness Enterprises.The polyline shapefiles created in step 1 and an existing polyline shapefile of the international boundary were merged together using the ArcView GeoProcessing Wizard.The shapefile generated in step 2 was converted to a line coverage using the ArcToolbox Conversion Tools - Feature Class to Coverage.The line coverage topology was cleaned and updated using the ArcInfo Workstation CLEAN (dangle length and fuzzy tolerance both set to 0.001) and BUILD commands.The boundary line coverage and an existing Lake Erie shoreline shapefile (derived from ESRI 100k data) were merged together using the ArcView GeoProcessing Wizard.The shapefile generated in step 5 was converted to a line coverage using the ArcToolbox Conversion Tools - Feature Class to Coverage.Topology of the boundary/shoreline coverage was cleaned and updated using the ArcInfo Workstation CLEAN (dangle length and fuzzy tolerance both set to 0.00001) and BUILD commands. BUILD was done for both line and polygon topology.The polygon feature from the coverage generate in step 7 was converted to a shapefile using Theme\Convert to Shapefile in ArcView.