|99999||No access to foraging from the cell due to movement barrier(s)|
|Range of values|
|1||No barrier to piping plover chick movement.|
|Range of values|
|No movement cost (not a barrier)||Definition of binary value (1) indicating the absence of a movement barrier for piping plover chicks.|
|1||Indicates the presence of a section of foraging shoreline for piping plovers. Here, foraging shorelines are defined as low-energy and could include the shorelines of sound- or bay-side beaches, interior ponds, and ephemeral pools. Ocean shorelines were not considered low-energy foraging shorelines.|
The distance to foraging layer (RI14_DisMOSH.tif) identifies the least-cost path distance for a piping plover chick to travel from the center of each 5x5 m grid cell to low-energy foraging areas with moist substrates. The distance to foraging data were used within a Bayesian network to model the probability that a specific set of landscape characteristics would be associated with piping plover habitat.
The movement cost layer (RI14_Cost.tif) identifies barriers to the movement of piping plover chicks, with barriers including water, human development, and moderate to dense vegetation. Barriers were identified using orthoimagery captured in 2014 (see data sources below). The movement cost layer was used to calculate the least-cost path distance (RI14_DisMOSH.tif) to the nearest foraging area (RI14_MOSH_Shoreline.shp).
The foraging shorelines shapefile (RI14_MOSH_Shoreline.shp) delineates foraging shorelines with moist substrates for piping plovers. Foraging areas were determined from elevations measured in 2014 and orthoimagery captured in 2014. Here, foraging shorelines are defined as low-energy and could include the shorelines of sound- or bay-side beaches, interior ponds, and ephemeral pools. Ocean shorelines were not considered low-energy foraging shorelines. See Zeigler and others (2019) for additional details.
Are there legal restrictions on access or use of the data?
Use_Constraints:Public domain data from the U.S. Government are freely redistributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey (USGS) as the source of this information.
Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), and have been processed successfully on a computer system at the USGS, no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
|Data format:||This dataset contains a 32-bit GeoTIFF of cost distance, an 8-bit binary GeoTIFF of movement cost, and a polyline shapefile of the shorelines. Also included is the CSDGM metadata and the browse graphic. in format GeoTIFF (version ArcGIS 10.4) GeoTIFF, also includes Esri polyline shapefile, possibly provided in a ZIP compressed format Size: 499.9|
|Data format:||This dataset contains a 32-bit GeoTIFF of cost distance, an 8-bit binary GeoTIFF of movement cost, and a polyline shapefile of the shorelines. Also included is the CSDGM metadata and the browse graphic. in format Shapefile (version ArcGIS 10.4) Esri polyline shapefile Size: 0.031|
To utilize these data, the user must have software capable of reading shapefile format, and 32-bit GeoTIFF with associated values attribute table.