The 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. GIS Database 2002-2005: Project Size = 1,898 acres Fort Larned National Historic Site (including the Rut Site) = 705 acres 16 Map Classes 11 Vegetated 5 Non-vegetated Minimum Mapping Unit = ½ hectare is the program standard but this was modified at FOLS to ¼ acre. Total Size = 229 Polygons Average Polygon Size = 8.3 acres Overall Thematic Accuracy = 92% To produce the digital map, a combination of 1:8,500-scale (0.75 meter pixels) color infrared digital ortho-imagery acquired on October 26, 2005 by the Kansas Applied Remote Sensing Program and 1:12,000-scale true color ortho-rectified imagery acquired in 2005 by the U.S. Department of Agriculture - Farm Service Agency’s Aerial Photography Field Office, and all of the GPS referenced ground data were used to interpret the complex patterns of vegetation and land-use. In the end, 16 map units (11 vegetated and 5 land-use) were developed and directly cross-walked or matched to corresponding plant associations and land-use classes. All of the interpreted and remotely sensed data were converted to Geographic Information System (GIS) databases using ArcGIS© software. Draft maps were printed, field tested, reviewed and revised. One hundred and six accuracy assessment (AA) data points were collected in 2006 by KNSHI and used to determine the map’s accuracy. After final revisions, the accuracy assessment revealed an overall thematic accuracy of 92%.

The 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. Our final map product is a geographic information system (GIS) database of vegetation structure and composition across the Crater Lake National Park terrestrial landscape, including wetlands. The database includes photos we took at all relevé, validation, and accuracy assessment plots, as well as the plots that were done in the previous wetlands inventory. We conducted an accuracy assessment of the map by evaluating 698 stratified random accuracy assessment plots throughout the project area. We intersected these field data with the vegetation map, resulting in an overall thematic accuracy of 86.2 %. The accuracy of the Cliff, Scree & Rock Vegetation map unit was difficult to assess, as only 9% of this vegetation type was available for sampling due to lack of access. In addition, fires that occurred during the 2017 accuracy assessment field season affected our sample design and may have had a small influence on the accuracy. Our geodatabase contains the locations where particular associations are found at 600 relevé plots, 698 accuracy assessment plots, and 803 validation plots.

Quivira National Wildlife Refuge was established in 1955, and a detailed vegetation map was not available for management purposes. With the present development of a biological program and Comprehensive Conservation Plan (CCP), a baseline vegetation map of the refuge was identified as a necessity. Development of the vegetation map and associated report was a multi-step process. Aerial photography (NAIP, 2008) was used with eCognition to create polygons of different plant communities based on the likeness of surrounding pixels in the area. Prior to ground-truthing, the following activities were accomplished: training on vegetation mapping using GIS (previous experience and National Conservation Training Center course), creation of an vegetation association and alliance dichotomous key, development of a refuge plant key and identification skills, and preparation of maps for ground truthing. Once out in the field dominant plants were identified for appropriate vegetation alliance and association classification, plant specimens were collected for the refuge herbarium as necessary and additional observations and photos were gathered for the report. Over the course of the project, classification data was entered into a GIS and polygons were appropriately modified to create the final map. At Quivira, results found a total of 42 alliances and 43 associations.The most dominant plants throughout the refuge in 2008 based on canopy cover were saltgrass, plum, little bluestem and cottonwood. The number of alliances and associations found on the refuge show high species diversity.

This web map references the live tiled map service from the OpenStreetMap (OSM) project. OpenStreetMap (OSM) is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap server: https://www.OpenStreetMap.org. See that website for additional information about OpenStreetMap. It is made available as a basemap for GIS work in ESRI products under a Creative Commons Attribution-ShareAlike license. Tip: This service is one of the basemaps used in the ArcGIS.com map viewer. Simply click one of those links to launch the interactive application of your choice, and then choose Open Street Map from the Basemap control to start using this service. You'll also find this service in the Basemap gallery in ArcGIS Explorer Desktop and ArcGIS Desktop 10. Tip: Here are some well known locations as they appear in this web map, accessed by launching the web map with a URL that contains location parameters: Athens, Cairo, Jakarta, Moscow, Mumbai, Nairobi, Paris, Rio De Janeiro, Shanghai

The 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. James W. Sewall Company developed a complete GIS coverage for the park and revised the preliminary vegetation map classes to better match the results from the cluster analysis and NMS ordination. Polygons representing vegetation stands were digitized on-screen in ArcGIS 8.3, and later in ArcMap 9.1 and 9.2, using lines drawn on the acetate overlays, base layers of 1:8,000 CIR aerial photography, orthorectified photo composite image, and plot location and data. The minimum map unit used was 0.5 ha (1.24 ac). Stereo pairs were used to double check stand signatures during the digitizing process. Photo interpretation and polygon digitization extended outside the NPS boundary, especially where vegetation units were arbitrarily truncated by the boundary. Each polygon was attributed with the name of a vegetation map class or an Anderson Level II land use category based on plot data, field observations, aerial photography signatures, and topographic maps. Data fields identifying the USNVC association inclusions within the vegetation map class were attributed to the vegetation polygons in the shapefile. The GIS coverages and shapefiles were projected to Universal Transverse Mercator (UTM) Zone 19 North American Datum 1983 (NAD83). FGDC compliant metadata (FGDC 1998a) were created with the NPS-MP ESRI extension and included with the vegetation map shapefile. A photointerpretation key to the map classes for the 2006 draft vegetation map is included as Appendix A. The composite vegetation coverage was clipped to the NPS 2002 MIMA boundary shapefile for accuracy assessment (AA). After the 2006 vegetation map was completed, the thematic accuracy of this map was assessed.

This web map features a vector basemap of OpenStreetMap (OSM) data created and hosted by Esri. Esri produced this vector tile basemap in ArcGIS Pro from a live replica of OSM data, hosted by Esri, and rendered using a creative cartographic style emulating a blueprint technical drawing. The vector tiles are updated every few weeks with the latest OSM data. This vector basemap is freely available for any user or developer to build into their web map or web mapping apps.OpenStreetMap (OSM) is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site: www.OpenStreetMap.org. Esri is a supporter of the OSM project and is excited to make this new vector basemap available available to the OSM, GIS, and Developer communities.

ABSTRACT: The U.S. Geological Survey (USGS) Upper Midwest Environmental Sciences Center (UMESC) has produced the Vegetation Spatial Database Coverage (vegetation map) for the Acadia National Park Vegetation Mapping Project, USGS-NPS Vegetation Mapping Program (VMP). The vegetation map is of Acadia National Park (NP) and extended environs, providing 99,693 hectares (246,347 acres) of map data. Of this coverage, 52,872 hectares (130,650 acres) is non-vegetated ocean, bay, and estuary (53% of coverage). Acadia NP comprises 19,276 hectares (47,633 acres) of the total data coverage area (19%, 40% not counting ocean and estuary data). Over 7,120 polygons make up the coverage, each with map class description and, for vegetation classes, physiognomic feature information. The spatial database provides crosswalk information to all National Vegetation Classification System (NVCS) floristic and physiognomic levels, and to other established classification systems (NatureServe's U.S. Terrestrial Ecological System Classification, Maine Natural Community Classification, and the USGS Land Use and Land Cover Classification). This mapping project has identified 53 NVCS associations (vegetation communities) at Acadia National Park through analyses of vegetation sample data. These associations are represented in the map coverage with 33 map classes. With all vegetation types, land use classes, and park specific categories combined, 57 map classes define the ground features within the project area (58 classes including the class for no map data). Each polygon within the spatial database map is identified with one of these map classes. In addition, physiognomic modifiers are added to map classes representing vegetation to describe the vegetation structure within a polygon (density, pattern, and height). The spatial database was produced from the interpretation of spring 1997 1:15,840-scale color infrared aerial photographs. The standard minimum mapping unit (MMU) applied is 0.5 hectares (1.25 acres). The interpreted data were transferred and automated using base maps produced from USGS digital orthophoto quadrangles. The finished spatial database is a single seamless coverage, projected in Universal Transverse Mercator, Zone 19, with datum in North American Datum of 1983. The estimated overall thematic accuracy for vegetation map classes is 80%.

This web map shows the location of the “City in Time” project to experience the historical scenes in Hong Kong. It is a subset of the geo-referenced public facility data made available by the Culture, Sports and Tourism Bureau under the Government of Hong Kong Special Administrative Region (the “Government”) at https://portal.csdi.gov.hk ("CSDI Portal"). The source data is processed and converted to Esri File Geodatabase format and then uploaded to Esri’s ArcGIS Online platform for sharing and reference purpose. The objectives are to facilitate our Hong Kong ArcGIS Online users to use the data in a spatial ready format and save their data conversion effort. For details about the data, source format and terms of conditions of usage, please refer to the website of Hong Kong CSDI Portal at https://portal.csdi.gov.hk.

This dataset combines the work of several different projects to create a seamless data set for the contiguous United States. Data from four regional Gap Analysis Projects and the LANDFIRE project were combined to make this dataset. In the northwestern United States (Idaho, Oregon, Montana, Washington and Wyoming) data in this map came from the Northwest Gap Analysis Project. In the southwestern United States (Colorado, Arizona, Nevada, New Mexico, and Utah) data used in this map came from the Southwest Gap Analysis Project. The data for Alabama, Florida, Georgia, Kentucky, North Carolina, South Carolina, Mississippi, Tennessee, and Virginia came from the Southeast Gap Analysis Project and the California data was generated by the updated California Gap land cover project. The Hawaii Gap Analysis project provided the data for Hawaii. In areas of the county (central U.S., Northeast, Alaska) that have not yet been covered by a regional Gap Analysis Project, data from the Landfire project was used. Similarities in the methods used by these projects made possible the combining of the data they derived into one seamless coverage. They all used multi-season satellite imagery (Landsat ETM+) from 1999-2001 in conjunction with digital elevation model (DEM) derived datasets (e.g. elevation, landform) to model natural and semi-natural vegetation. Vegetation classes were drawn from NatureServe's Ecological System Classification (Comer et al. 2003) or classes developed by the Hawaii Gap project. Additionally, all of the projects included land use classes that were employed to describe areas where natural vegetation has been altered. In many areas of the country these classes were derived from the National Land Cover Dataset (NLCD). For the majority of classes and, in most areas of the country, a decision tree classifier was used to discriminate ecological system types. In some areas of the country, more manual techniques were used to discriminate small patch systems and systems not distinguishable through topography. The data contains multiple levels of thematic detail. At the most detailed level natural vegetation is represented by NatureServe's Ecological System classification (or in Hawaii the Hawaii GAP classification). These most detailed classifications have been crosswalked to the five highest levels of the National Vegetation Classification (NVC), Class, Subclass, Formation, Division and Macrogroup. This crosswalk allows users to display and analyze the data at different levels of thematic resolution. Developed areas, or areas dominated by introduced species, timber harvest, or water are represented by other classes, collectively refered to as land use classes; these land use classes occur at each of the thematic levels. Raster data in both ArcGIS Grid and ERDAS Imagine format is available for download at http://gis1.usgs.gov/csas/gap/viewer/land_cover/Map.aspx Six layer files are included in the download packages to assist the user in displaying the data at each of the Thematic levels in ArcGIS. In adition to the raster datasets the data is available in Web Mapping Services (WMS) format for each of the six NVC classification levels (Class, Subclass, Formation, Division, Macrogroup, Ecological System) at the following links. http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Class_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Subclass_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Formation_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Division_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_NVC_Macrogroup_Landuse/MapServer http://gis1.usgs.gov/arcgis/rest/services/gap/GAP_Land_Cover_Ecological_Systems_Landuse/MapServer

http://www.openstreetmap.org/images/osm_logo.png" alt=""> OpenStreetMap (openstreetmap.org) is a global collaborative mapping project, which offers maps and map data released with an open license, encouraging free re-use and re-distribution. The data is created by a large community of volunteers who use a variety of simple on-the-ground surveying techniques, and wiki-syle editing tools to collaborate as they create the maps, in a process which is open to everyone. The project originated in London, and an active community of mappers and developers are based here. Mapping work in London is ongoing (and you can help!) but the coverage is already good enough for many uses.

Browse the map of London on OpenStreetMap.org

Downloads:

The whole of England updated daily:

• england.osm.bz2 ~185M - .osm formatted raw XML data (compressed)
• england.shp.zip ~156M - ESRI shapefiles

For more details of downloads available from OpenStreetMap, including downloading the whole planet, see 'planet.osm' on the wiki.

Data access APIs:

Download small areas of the map by bounding-box. For example this URL requests the data around Trafalgar Square:
http://api.openstreetmap.org/api/0.6/map?bbox=-0.13062,51.5065,-0.12557,51.50969

Data filtered by "tag". For example this URL returns all elements in London tagged shop=supermarket:
http://www.informationfreeway.org/api/0.6/*[shop=supermarket][bbox=-0.48,51.30,0.21,51.70]

The .osm format

The format of the data is a raw XML represention of all the elements making up the map. OpenStreetMap is composed of interconnected "nodes" and "ways" (and sometimes "relations") each with a set of name=value pairs called "tags". These classify and describe properties of the elements, and ultimately influence how they get drawn on the map. To understand more about tags, and different ways of working with this data format refer to the following pages on the OpenStreetMap wiki.

• .osm - About the raw XML data format of OpenStreetMap
• Downloading data - More details of the API and extract download options
• Xapi - The extended api for filtering by tag
• Map Features - A list of tags, and what map features they represent
• Converting map data between formats - catalogue of tools for converting from .osm to other formats

Simple embedded maps

Rather than working with raw map data, you may prefer to embed maps from OpenStreetMap on your website with a simple bit of javascript. You can also present overlays of other data, in a manner very similar to working with google maps. In fact you can even use the google maps API to do this. See OSM on your own website for details and links to various javascript map libraries.

Help build the map!

The OpenStreetMap project aims to attract large numbers of contributors who all chip in a little bit to help build the map. Although the map editing tools take a little while to learn, they are designed to be as simple as possible, so that everyone can get involved. This project offers an exciting means of allowing local London communities to take ownership of their part of the map.

Read about how to Get Involved and see the London page for details of OpenStreetMap community events.

The 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. To produce the digital map, a combination of 1:12,000-scale ortho imagery acquired in 2003, 2004, and 2005 and all of the GPS-referenced ground data were used to interpret the complex patterns of vegetation and land-use. All imagery was acquired from the U.S. Department of Agriculture - Farm Service Agency’s Aerial Photography Field Office and the National Agriculture Imagery Program. In the end, 32 map units (13 vegetated and 19 land-use) were developed and directly cross-walked or matched to corresponding plant associations and land-use classes. All of the interpreted and remotely sensed data were converted to Geographic Information System (GIS) databases using ArcGIS© software. Draft maps were printed, field tested, reviewed, and revised. One hundred-twenty four accuracy assessment (AA) data points were collected in 2006 and used to determine the map’s accuracy. After final revisions, the accuracy assessment revealed an overall thematic accuracy of 89%. Project Size = 6,784 acres San Antonio Missions National Historical Park = 844 acres Map Classes = 32 13 Vegetated 19 Non-vegetated Minimum Mapping Unit = ½ hectare is the program standard but this was modified at SAAN to ¼ acre. Total Size = 1,122 Polygons Average Polygon Size = 6 acres Overall Thematic Accuracy = 89%

Interactive GIS Mapping Tool – Urgent Drinking Water Needs (UDWN) Web Map in California

Use Constraints:

This mapping tool is for reference and guidance purposes only and is not a binding legal document to be used for legal determinations. The data provided may contain errors, inconsistencies, or may not in all cases appropriately represent the current status of Urgent Drinking Water Needs project locations. The data in this map are subject to change at any time and should not be used as the sole source for decision making. By using this data, the user acknowledges all limitations of the data and agrees to accept all errors stemming from its use. The Urgent Drinking Water Needs map does not provide the locations of individual households that were provided funding through grant agreements with non-profit organizations.

Description:

This map displays Urgent Drinking Water Needs due to drought, contamination, or other eligible emergencies. This includes projects approved for funding from July 1, 2014 to November 18, 2022, including both active and completed projects. The data comes from the State Water Resources Control Board (SWRCB) Cleanup and Abatement Account’s (CAA) project database and was exported on November 18, 2022. The map contains four layers: UDWN_Projects, UDWN_Summary_by_county, CA_Assembly_Districts_WEB, and CA_Senate_Districts_WEB.

The attributes for each project in the UDWN_Projects layer include the recipient of grant funding (grantee), community served, type of project, grant amount, funding program, date the project was approved, date the project was completed, Disadvantaged Community status, Small Disadvantaged Community status, the public water system number, status of the project (Active or Completed), and the state fiscal year in which the project was approved.

How to Use the Interactive Mapping Tool:When the map loads, it displays the state of California, UDWN Project locations, and California county boundaries. The “About” tab is located on the left-hand side of the map and displays instructions for using the map. The next tab display pre-set filters, the legend, and a layer list. Clicking on the “Legend” tab in the menu will show the legend of the map. Projects that appear as blue dots are still active, while projects that appear as red dots have already been completed.Note: Layers that show CA Assembly and Senate Districts were created by the Sierra Nevada Conservancy (SNC). These layers must be toggled on in the layers list to be seen. To view information about a specific project, click on a project location. A pop-up box will appear with the following information: (a) county name, (b) community served, (c) type of project, (d) approved funding amount, (e) approval date, and (f) status. To view information about the total funding and number of projects in a county, click within a county boundary and a pop up will appear.Use the pre-set filters to filter projects by status, fiscal year, funding program, county, assembly district, and/or senate district using the drop-down menu. The filters can be toggled on or off using the switches on the right side of the menu. To create a custom filter, click the filter icon at the bottom of the preset filter menu and enter the desired parameters. For one parameter, click “add expression” to create a custom filter. For more than one, click “add set” to create a custom filter.To export and download filtered data, open the Attribute Table located at the bottom of the map, click the “Options” drop down menu, select “Export all to CSV” from the drop-down menu, and download the desired information.

Map Layers:UDWN_Projects – This layer shows all active or completed UDWN projects from July 1, 2014 to November 18, 2022. Active projects are represented with blue dots while completed projects are represented with red dots. The attributes in this layer include what county the project is in, the community served, the type of project, approved funding amount, approval date, and status.UDWN_Summary_by_county – This layer shows the boundary lines for all the counties in California. The attributes in this layer include the total number of projects and total funding approved in that county since July 1, 2014. CA_Assembly_Districts_WEB – This layer shows the boundary lines for all the assembly districts in California. It is owned and maintained by the Sierra Nevada Conservancy (SNC) and boundaries may not be accurate. CA_Senate_Districts_WEB – This layer shows the boundary lines for all the senate districts in California. It is owned and maintained by the Sierra Nevada Conservancy (SNC) and boundaries may not be accurate.

Informational Pop-up Box:County – California county where the project is locatedCommunity Served – California community that is benefiting from UDWN funding Type of Project – Project type, which can include bottled water, consolidation, hauled water, pilot study, POU, pump, tank, treatment, and well Approved Funding Amount – Amount of money in U.S. dollars approved for the projectApproval Date – Date that the project was approved for fundingStatus – Current status of the project (active or closed)Date Created:

Data created on November 18, 2022 and valid up to this date.

Sources:

Urgent Drinking Water Needs data was exported from the CAA Database.

The Sierra Nevada Conservancy (SNC) created the California Senate and Assembly layers.

Points of Contact:

Christina Raynard is the creator and owner of this layer. Christina.raynard@waterboards.ca.gov (State Water Resources Control Board, Division of Financial Assistance)

Terms of Use

No special restrictions or limitations on using the item’s content have been provided.

This data layer is part of a collection of GIS data created for the Okanagan Mainstem Floodplain Mapping Project. Notes below apply to the entire project data set.***Download Size is 12.5 GBGeneral Notes1. Please refer to the Disclaimer further below.2. Please review the associated project reports before using the floodplain maps: Northwest Hydraulic Consultants Ltd. (NHC). 2020. ‘Okanagan Mainstem Floodplain Mapping Project’. Report prepared for the Okanagan Basin Water Board (OBWB). 31 March 2020. NHC project number 3004430. Northwest Hydraulic Consultants Ltd. (NHC). 2021. ‘Okanagan Mainstem Floodplain Mapping Project – Development of CGVD1928 Floodplain Mapping’. Letter report prepared for the Okanagan Basin Water Board (OBWB). 30 March 2021. NHC project number 3006034.Northwest Hydraulic Consultants Ltd. (NHC). 2022. ‘Supplemental to the Okanagan Mainstem Floodplain Mapping Project – Current Operations Flood Construction Levels for Okanagan and Wood-Kalamalka Lakes’. Report prepared for the Okanagan Basin Water Board (OBWB). Final. 16 August 2022. NHC project number 3006613.3. These floodplain mapping layers delineate flood inundation extents under the specific flood events. Tributaries are not included in mapping.4. The mapped inundation is based on the calculated water level. Freeboard, wind effects, and wave effects have been added to the calculated water level where noted.5. Where noted, a freeboard allowance of 0.6 m has been added to the calculated flood water level. It has been added to account for local variations in water level and uncertainty in the underlying data and modelling.6. Where noted, the FCL (or COFCL) included in lake mapping layers includes an allowance for wind setup and wave runup based on co-occurrence of the seasonal 200-year wind event. The wind and wave effects extend 40 m shoreward to delineate the expected limit of wave effects. Beyond this limit the FCL (or COFCL) is based on inundation of the flood event without wave effects. Wave effects have been calculated based on generalized shoreline profile and roughness for each shoreline reach. Site specific runup analysis by a Qualified Registrant may be warranted to refine the generalized wave effects shown, which could increase or decrease the FCL (or COFCL) by as much as a metre.7. Underlying hydraulic analysis assumes channel and shoreline geometry is stationary. Erosion, deposition, degradation, and aggradation are expected to occur and may alter actual observed flood levels and extents. Obstructions, such as log-jams, local storm water inflows or other land drainage, groundwater, or tributary flows may cause flood levels to exceed those indicated on the maps.8. The Okanagan floodplain is subject to persistent ponding due to poor drainage. Persistent ponding is not covered by the flood inundation mapping.9. For flood level maps (water level and inundation extents):a. Layers for each flood scenario describe inundation extents, water surface elevations, and depths.b. The calculated water level has been extended perpendicular to flow across the floodplain; thus mapping inundation of isolated areas regardless of likelihood of inundation; whether it be from dike failure, seepage, or local inflows. Distant isolated areas may be conservatively mapped as inundated. Site specific judgement by a Qualified Professional is required to determine validity of isolated inundation.c. Filtering was used to remove isolated areas smaller than 100 m2. Holes in the inundation extent with areas less than 100 m2 were also removed. Isolated areas larger than 100 m2 are included in GIS data layers and are shown on maps if they are within 40 metres of direct inundation or within 40 metres of other retained polygons.d. Okanagan Dam breach, dam overtopping, or overtopping and breaching of Penticton Beach were not modelled. Inundation downstream of the Okanagan Dam on the left bank floodplain is based on river modelling with the assumption that Okanagan Lake levels will not overtop Lakeshore Drive and adjacent high ground. For the design flood scenarios, inundation mapping on the right bank of the Okanagan River from the Okanagan Dam downstream to the Highway 97 bridge and Burnaby Avenue is based on additional lake and river modelling. For other flood scenarios, river and lake inundation has been mapped separately and has not been integrated on the right bank. Inundation mapping on the right bank is based on river modelling as far as the most upstream modelled river cross section.10. For flood hazard maps (depth and velocity):a. Layers describe flood water depths and velocities. Depths and velocities are based on the maximum values from three modelled scenarios: all dikes removed, left bank dikes removed, and right bank dikes removed. Depths do not include freeboard.b. All hazard layers were modelled with the same parameters and boundary conditions as the design flood.11. Flood modelling and mapping is based on a digital elevation model (DEM) with the following coordinate system and datum specifications: Universal Transverse Mercator Zone 11-N (UTM Zone 11-N), North American Datum 1983 Canadian Spatial Reference System epoch 2002.0 (NAD83 CSRS (2002.0)), Canadian Geodetic Vertical Datum 2013 (CGVD2013), Canadian Gravimetric Geoid model of 2013 (CGG2013). FCL values are presented on the maps in both CGVD2013 and CGVD1928 vertical datums. CGVD1928 values are based on the following specifications: NAD83 CSRS (2002.0), CGVD1928, Height Transformation version 2.0 epoch 1997 (HTv2.0 (1997)). COFCL and COFCL values are presented only in CGVD2013.12. The accuracy of simulated flood levels is limited by the reliability and extent of water level, flow, and climatic data. The accuracy of the floodplain extents is limited by the accuracy of the design flood flow, the hydraulic model, and the digital surface representation of local topography. Localized areas above or below the mapped inundation maybe generalized. Therefore, floodplain maps should be considered an administrative tool that indicates flood elevations and floodplain boundaries for a designated flood. A qualified professional is to be consulted for site-specific engineering analysis.13. Industry best practices were followed to generate the floodplain maps. However, actual flood levels and extents may vary from those shown. OBWB and NHC do not assume any liability for variations of flood levels and extents from that shown.Data Sources Design flood events are based on hydrologic modelling of the Okanagan River watershed. The hydraulic response is based on a combination of 1D and 2D numerical models developed by NHC using HEC-RAS software, and NHC SWAN models. The hydraulic models are calibrated to the 2017 flood event and validated to the 2018 flood event; due to limits on data availability the hydrologic model is calibrated using data from 1980-2010. The digital elevation model (DEM) used to develop the model and mapping is based on Lidar data collected from March to November 2018 and provided by Emergency Management BC (EMBC), channel survey conducted by WSP in March, April, and June 2019, and additional survey data. See accompanying report for details NHC (2020).DisclaimerThis document has been prepared by Northwest Hydraulic Consultants Ltd. for the benefit of Okanagan Basin Water Board, Regional District of North Okanagan, Regional District of Central Okanagan, Regional District of Okanagan-Similkameen, Okanagan Nation Alliance for specific application to the Okanagan Mainstem Floodplain Mapping Project, Okanagan Valley, British Columbia, Canada (Ellison, Wood, Kalamalka, Okanagan, Skaha, Vaseux, and Osoyoos lakes and Okanagan River from Okanagan Lake to Osoyoos Lake). The information and data contained herein represent Northwest Hydraulic Consultants Ltd. best professional judgment in light of the knowledge and information available to Northwest Hydraulic Consultants Ltd. at the time of preparation, and was prepared in accordance with generally accepted engineering practices.Except as required by law, this document and the information and data contained herein are to be treated as confidential and may be used and relied upon only by Okanagan Basin Water Board, Regional District of North Okanagan, Regional District of Central Okanagan, Regional District of Okanagan-Similkameen, Okanagan Nation Alliance, its officers and employees. Northwest Hydraulic Consultants Ltd. denies any liability whatsoever to other parties who may obtain access to this document for any injury, loss or damage suffered by such parties arising from their use of, or reliance upon, this report or any of its contents.Data Layer List and Descriptions<!--· River / Lake Model Boundary -River / Lake Model Boundary (NHC): Boundary between Okanagan River and Okanagan Lake modelling and mapping areas for design and flood mapping.Recommended Design Flood (gates open): Ellison, Skaha, Vaseux, and Osoyoos lakeso Lake Shoreline Flood Construction Level (FCL) Zone – Recommended Design Flood with Freeboard and Wave Effect (NHC): Zone defined based on approximate shoreline and the wave breaking boundary plus a buffer; FCLs defined by zone along shoreline; shoreline FCLs take precedence over lake inundation FCLs.o Lake Flood Construction Level (FCL) Zone (Inundation Extent) – Recommended Design Flood with Freeboard (NHC): Design flood inundation extent with freeboard. Design event varies by lake, plus wind setup, plus mid-century climate change; plus freeboard 0.6m.o Lake Inundation Extent – Recommended Design Flood without Freeboard (NHC): Design flood inundation extent without freeboard. Design event varies by lake, plus wind setup, plus mid-century climate change.o Depth Grids§ Ellison Lake Depth – Recommended Design without Freeboard (NHC): ELLISON LAKE: 200-YEAR MID-CENTURY. Design flood depth

THIS MAP IS NOT AUTHORITATIVE. SEE TERMS OF USE BELOW.This web map was developed by the National Oceanic and Atmospheric Administration’s (NOAA) Office for Coastal Management and is featured in the U.S. Great Lakes Collaborative Benthic Habitat Mapping Common Operating Dashboard in support of the Collaborative Benthic Habitat Mapping in the Nearshore Waters of the Great Lakes Basin Project. This multi-year, multi-agency project is funded through the Great Lakes Restoration Initiative (GLRI) and focuses on new bathymetric data (airborne lidar and vessel based sonar) acquisition, validation, and benthic habitat characterization mapping of the nearshore waters (0-80 meters) in the U.S. Great Lakes. This project also contributes to the regional Lakebed 2030 campaign, which aims to have high-density bathymetric data available for the entirety of the Great Lakes by 2030. This web map contains data layers reflecting the current status of bathy data coverage in the nearshore (0-80 meters) of the U.S. Great Lakes, including acquisition (lidar and multibeam sonar), ground-truthing/validation, and benthic habitat mapping and characterization. Acquisition layers include coverage areas that have been acquired and are available for public use (green) as well as those that have been acquired, but are not yet available or are still in progress (orange). The nearshore water depth layers (0-25 and 25-80 meters) were created using the National Centers for Environmental Information (NCEI) Great Lakes Bathymetry (3-second resolution) grid extracts. The 0 to 25 meter nearshore water depth layer represents areas where bathymetric lidar data acquisition could ideally be conducted, depending on water condition and turbidity. The 25 to 80 meter layer shows locations where acoustic data acquisition can occur. The acquired data values are all in sq. km and were created by merging and dissolving all publicly available bathy lidar and multibeam sonar coverage polygons into single layer and erasing from the nearshore water depth layers (0-25, 25-80, and 0-80 meters). All polygon layers were clipped using the USGS Great Lakes subbasin polygon shapefile and the U.S./Canada boundary from the International Boundary Commission (version 1.3 from 2018). All data originally projected in the following coordinate system: EPSG:3175, NAD 1983 Great Lakes and St Lawrence Albers.This map will continue to be updated as new information is made available.See below for information on additional data layers. Source Data for Bathy Coverage Layers - Acquired/Available:Topobathy and Bathy Lidar (NOAA's Data Access Viewer: https://coast.noaa.gov/dataviewer/#/; U.S. Interagency Elevation Inventory (USIEI): https://coast.noaa.gov/inventory/). Multibeam Sonar (National Centers for Environmental Information (NCEI) Bathymetric Data Viewer: https://www.ncei.noaa.gov/maps/bathymetry/; NOAA's Data Access Viewer: https://coast.noaa.gov/dataviewer/#/; U.S. Interagency Elevation Inventory (USIEI): https://coast.noaa.gov/inventory/; USGS ScienceBaseCatalog: https://www.sciencebase.gov/catalog/item/656e229bd34e7ca10833f950)Source Data for Bathy Coverage Layers - GLRI AOIs (2020-2024):Acquisition: NOAA Office for Coastal ManagementValidation/CMECS Characterizations: NOAA National Centers for Coastal Ocean Science (NCCOS)Source Data for Bathy Coverage Layers - In Progress and Planned:NOAA Office of Coast Survey Plans: https://gis.charttools.noaa.gov/arcgis/rest/services/Hydrographic_Services/Planned_Survey_Areas/MapServer/0NOAA Office for Coastal ManagementSource Data for Nearshore Water Depths:NOAA's National Centers for Environmental Information (NCEI) Great Lakes Bathymetry (3-second resolution) grid extracts: https://www.ncei.noaa.gov/maps/grid-extract/Source Data for Spatial Prioritization Layers:Great Lakes Spatial Priorities Study Results Jun 2021. https://gis.charttools.noaa.gov/arcgis/rest/services/IOCM/GreatLakes_SPS_Results_Jun_2021/MapServerMapping priorities within the proposed Wisconsin Lake Michigan National Marine Sanctuary (2018). https://gis.ngdc.noaa.gov/arcgis/rest/services/nccos/BiogeographicAssessments_WILMPrioritizationResults/MapServerThunder Bay National Marine Sanctuary Spatial Prioritization Results (2020). https://gis.ngdc.noaa.gov/arcgis/rest/services/nccos/BiogeographicAssessments_TBNMSPrioritizationResults/MapServerSource Data for Supplemental Data Layers:International Boundary Commission U.S./Canada Boundary (version 1.3 from 2018): https://www.internationalboundarycommission.org/en/maps-coordinates/coordinates.phpNational Oceanic and Atmospheric Administration (NOAA) HydroHealth 2018 Survey: https://wrecks.nauticalcharts.noaa.gov/arcgis/rest/services/Hydrographic_Services/HydroHealth_2018/ImageServerNational Oceanic and Atmospheric Administration (NOAA) Lake Ontario National Marine Sanctuary Boundary: https://sanctuaries.noaa.gov/library/imast_gis.htmlNational Oceanic and Atmospheric Administration (NOAA) Marine Protected Areas (MPA) Inventory 2023-2024: https://www.fisheries.noaa.gov/inport/item/69506National Oceanic and Atmospheric Administration (NOAA) National Marine Sanctuary Program Boundaries (2021): https://services2.arcgis.com/C8EMgrsFcRFL6LrL/arcgis/rest/services/ONMS_2021_Boundaries/FeatureServerNational Oceanic and Atmospheric Administration (NOAA) U.S. Bathymetry Gap Analysis: https://noaa.maps.arcgis.com/home/item.html?id=4d7d925fc96d47d9ace970dd5040df0aU.S. Environment Protection Agency (EPA) Areas of Concern: https://services.arcgis.com/cJ9YHowT8TU7DUyn/arcgis/rest/services/epa_areas_of_concern_glahf_viewlayer/FeatureServerU.S. Geological Survey (USGS) Great Lakes Subbasins: https://www.sciencebase.gov/catalog/item/530f8a0ee4b0e7e46bd300dd Latest update: February 20, 2025

Area-wide modeled near-surface temperature for 3-4 pm on July 27, 2020, based on temperature and humidity data collected for a one-day heat mapping project conducted by King County, Seattle Public Utilities, and the City of Seattle. Data collected on July 27, 2020 in partnership with project volunteers and CAPA Strategies. Data analysis and maps produced by CAPA strategies. This predictive temperature model was created from multi-band land cover rasters from Sentinel-2 satellite and raw heat data from sensor SD cards using the 70:30 holdout method.Heat maps also available for 6-7 am and 7-8 pm. Results can be viewed using this ArcGIS web app viewer. More information on the project available in Heat Watch Report for Seattle & King County. Contact CAPA Strategies for questions on the data, maps, and data analysis methods.

The financially constrained element of Visualize 2045 identifies all the regionally significant capital improvements to the region’s highway and transit systems that transportation agencies expect to make and to be able to afford through 2045.For more information on Visualize 2045, visit https://www.mwcog.org/visualize2045/.To view the web map, visit https://www.mwcog.org/maps/map-listing/visualize-2045-project-map/.* NOTE: the online map shows projects in the current version of the plan (2022 update); this data download is for the 2018 update to the plan.Adding GIS Data to ArcMap from a Map Package:To load the .mpk file if saved locally: From Windows Explorer1. Browse to the location of the .mpk file. 2. Double-click the file to launch ArcMap and unpack all the data in the package. From ArcCatalog1. Browse to the location of the .mpk file. 2. Right-click the file, and select Unpack. This action launches ArcMap and unpacks the data in the package. The process is the same if you are using ArcCatalog from within ArcMap.Note: The .mpk file cannot be opened within ArcMap.Regardless of where the .mpk file is stored originally, the data within the map package when unpacked saves on your hard drive in the Documents and Settings folder:C:\Documents_and_Settings\MyDocuments\ArcGIS\Packages*.gdb

The 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.

The interpreted polygons were manually transferred to overlays that were registered to the base maps. Map unit attributes and appropriate physiognomic modifier codes were added to a second overlay. The overlays were subsequently rechecked for accuracy. Each overlay of transferred data was scanned using a large format sheet fed scanner at a resolution of 400 dots per inch. The resulting Tagged Image File Format (TIFF) images were then converted to a grid using ArcInfo (Version 7.2.1 Patch 2, Environmental Systems Research Institute, Redlands, California). For data produced with the DOQ base maps, the converted grid was projected to UTM Zone 15 using North American Datum of 1983 (NAD83).

The purpose of the Global Map is to accurately describe the present status of the global environment in international cooperation of respective National Mapping Organisations (NMOs) of the world. The Landcover, Vegetation Percentage Tree Cover and Elevation imagery have been developed by using satellite imagery with cooperation between participating NMOs and supporting stakeholders.

This map includes shoreline change data for the state of Massachusetts hosted by the Massachusetts Office of Coastal Zone Management.The active data layer in this map is Massachusetts Shoreline Change Transect (1970-2014) with short-term shoreline change rates. To view long-term rates, open map in Map Viewer to turn on layer.The Massachusetts Office of Coastal Zone Management launched the Shoreline Change Project in 1989 to identify erosion-prone areas of the coast. The shoreline position and change rate are used to inform management decisions regarding the erosion of coastal resources. In 2001, a shoreline from 1994 was added to calculate both long- and short-term shoreline change rates along ocean-facing sections of the Massachusetts coast. In 2013, two oceanfront shorelines for Massachusetts were added using 2008-9 color aerial orthoimagery and 2007 topographic lidar datasets obtained from the National Oceanic and Atmospheric Administration's Ocean Service, Coastal Services Center. In 2018 two new mean high water (MHW) shorelines for Massachusetts were extracted from lidar collected between 2010 and 2014 (described below). 2018 addition shoreline 1The North Shore and South Coast uses 2010 lidar data collected by the U.S. Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise. The South Shore and Outer Cape uses 2011 lidar data collected by the U.S. Geological Survey's (USGS) National Geospatial Program Office. Nantucket and Martha’s Vineyard uses 2012 lidar data collected by the USACE (post Sandy)from a 2012 USACE Post Sandy Topographic lidar survey. 2018 addition shoreline 2The North Shore, Boston, South Shore, Cape Cod Bay, Outer Cape, South Cape, Nantucket, Martha’s Vineyard, and the South Coast (around Buzzards Bay to the Rhode Island Border) is from 2013-14 lidar data collected by the (USGS) Coastal and Marine Geology Program. This 2018 update of the rate of shoreline change in Massachusetts includes two types of rates. Some of the rates include a proxy-datum bias correction, this is indicated in the filename with “PDB”. The rates that do not account for this correction have “NB” in their file names. The proxy-datum bias is applied because in some areas a proxy shoreline (like a High Water Line shoreline) has a bias when compared to a datum shoreline (like a Mean High Water shoreline). In areas where it exists, this bias should be accounted for when calculating rates using a mix of proxy and datum shorelines. This issue is explained further in Ruggiero and List (2009) and in the process steps of the metadata associated with the rates. This release includes both long-term (~150 years) and short term (~30 years) rates. Files associated with the long-term rates have “LT” in their names, files associated with short-term rates have “ST” in their names.