GL_LAKE_ONTARIO_2023_GLRI_UNIQUE_SITES Points

This feature class is housed within the Lake Ontario 2023 ESI Geodatabase but is maintained outside of the traditional NOAA ESI Structure. Vector points in this data set represent unique restoration sites managed by the Great Lakes Restoration Initiative (GLRI). An abbreviated spreadsheet for the GLRI restoration sites is provided on page xvii of the Lake Ontario 2023 ESI atlas introductory pages. For full GLRI project information, please refer to the spreadsheet available at https://www.glri.us/projects.

The study area includes the United States portion of Lake Ontario, covering the islands in New York: Association Island, Bass Island, Calf Island, Carl Island, Cherry Island, Eagle Island, Fox Island, Galloo Islands, Grenadier Island, Horse Island, Hoveys Island, Six Point Town, and Stony Island. Major Lake Ontario bays mapped include: Black River Bay, Blind Sodus Bay, Braddock Bay, Chaumont Bay, Guffin Bay, Irondequoit Bay, Henderson Bay, Little Sodus Bay, Mexico Bay, Port Bay, Sawyer Bay, and Sodus Bay.

The ESI data are intended to provide baseline environmental data for oil spill planning and response. The Clean Water Act with amendments by the Oil Pollution Act of 1990 requires response plans for immediate and effective protection of sensitive resources. The ESI data may be appropriate for many other coastal management efforts, though the original intent should be kept in mind. The Great Lakes Restoration Initiative (GLRI) project sites were added to the Lake Ontario ESI for awareness of past, current, and potentially future restoration efforts within the Great Lakes.

[THIS FIELD IS FOR INTERNAL NOTES AS NEEDED. IT WILL NOT BE VIEWABLE IN THE PUBLIC METADATA RECORD.]

Prepared by Research Planning, Inc, Columbia, South Carolina for the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Emergency Response Division, Seattle, Washington.

Data content is considered static once published. However, if issues with the Geodatabase linkages or table contents are identified, the Geodatabase and/or the associated Map Document may be updated. Assure most current data is being used by downloading from https://response.restoration.noaa.gov/esi_download and/or comparing modification dates provided at this site.

The associated table is GLRI_UPDATED. The Feature ID in this dataset relates to the Feature ID in GLRI_UDPATED as well as the ID on the abbreviated spreadsheet (found on page xvii of the Lake Ontario 2023 ESI atlas introductory pages). Additionally, a unique, atlas-specific feature ID (Lake Ontario, LO%) was created for each project at each point location.

Although these data have been processed and used successfully on a computer system at the National Oceanic and Atmospheric Administration (NOAA), no warranty, expressed or implied, is made by NOAA regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty. NOAA warrants the delivery of this product in computer-readable format. If problems are encountered in downloading the ESI data or with file corruption, contact NOAA (see Distributor).

These data represent a snapshot in time and temporal changes may have occurred. The data are not intended to include all biological or human-use resources present in an area; they focus on species and resources particularly sensitive to oiling. In the event of a spill, they should be used for a first assessment only. The data providers are the experts with regard to individual resources. They should be contacted to confirm if more current data exist or if in-depth information is needed about a particular resource.

This reflects the extent of all features included in the Great Lakes Lake Ontario 2023 ESI Geodatabase study region. The bounding box for this particular feature class may vary depending on occurrences identified and mapped.

Data can be accessed by downloading the zipped ArcGIS geodatabase from the Download URL (see Distribution Information). Questions can be directed to the ESI Program Manager (Point Of Contact).

None

DO NOT USE MAPS FOR NAVIGATIONAL PURPOSES. Management boundaries are not to be considered legal boundaries. Edges may have been altered for cartographic processes. Note that the ESI database should not be used to the exclusion of other pertinent data or information held by state or federal agencies or other organizations. Likewise, information contained in the database cannot be used in place of consultations with environmental, natural resource, and cultural resource agencies, or in place of field surveys. Recognize that the information contained in the ESI database represents known concentration areas or occurrences of natural, cultural, and human-use resources, but does not necessarily represent the full distribution or range of each species or resource. This is particularly important to recognize when considering potential impacts to protected resources, such as endangered species, wetlands, etc. Besides the above warnings, there are no use constraints on these data. Acknowledgment of the originators, publishers, contributors, and sources listed would be appreciated in products derived from these data.

None

None

The software packages used to develop the atlas are Environmental Systems Research Institute's ArcGIS for Desktop(R), ArcPro(R), and SQL SERVER(R). The hardware configuration is PC's with Microsoft Windows Operating System.

A multi-stage error checking process is used to verify both attribute accuracy and logical consistency throughout data production. The process includes a standardized data entry methodology, data review by in-house and external resource experts, a final Quality Assurance/Quality Control (QA/QC) process, and multiple automated logical consistency checks. For a more detailed evaluation of source data attribute accuracy, check the sources listed in the Lineage section.

A multi-stage error checking process, described in the above Attribute Accuracy Report, is used to verify both attribute accuracy and logical consistency throughout data production. This process includes multiple automated logical consistency checks that test the files for missing or duplicate data, rules for proper coding, GIS topological consistencies, and SQL SERVER(R) to ArcGIS(R) consistencies. A final review is made by the GIS manager, before the complete Geodatabase and metadata are created. After the data are delivered to NOAA, they are again subjected to several consistency checks, and processed into the final delivery format.