The ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) Project Package includes all of the layers that are in the NTIA Permitting and Environmental Information Application as well as the APPEIT Tool which will allow users to input a project area and determine what layers from the application overlap with it. An overview of the project package and the APPEIT tool is provided below. User instructions on how to use the tool are available here. Instructions now include how to customize the tool by adding your own data. A video explaining how to use the Project Package is also available here. Project Package OverviewThis map package includes all of the layers from the NTIA Permitting and Environmental Information Application. The layers included are all feature services from various Federal and State agencies. The map package was created with ArcGIS Pro 3.4.0. The map package was created to allow users easy access to all feature services including symbology. The map package will allow users to avoid downloading datasets individually and easily incorporate into their own GIS system. The map package includes three maps.1. Permitting and Environmental Information Application Layers for GIS Analysis - This map includes all of the map tabs shown in the application, except State Data which is provided in another tab. This map includes feature services that can be used for analysis with other project layers such as a route or project area. 2. Permitting and Environmental Information Application Layers – For Reference Only - This map includes layers that cannot be used for analysis since they are either imagery or tile layers.3. State Data - Reference Only - This map includes all relevant state data that is shown in the application.The NTIA Permitting and Environmental Information Application was created to help with your permitting planning and environmental review preparation efforts by providing access to multiple maps from publicly available sources, including federal review, permitting, and resource agencies. The application should be used for informational purposes only and is intended solely to assist users with preliminary identification of areas that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements. Multiple maps are provided in the application which are created from public sources. This application does not have an exhaustive list of everything you need for permitting or environmental review for a project but is an initial starting point to see what might be required.APPEIT Tool OverviewThe Department of Commerce’s National Telecommunications and Information Administration (NTIA) is providing the ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) to help federal broadband grant recipients and subgrantees identify permits and environmental factors as they plan routes for their broadband deployments. Identifying permit requirements early, initiating pre-application coordination with permitting agencies, and avoiding environmental impacts help drive successful infrastructure projects. NTIA’s public release of the APPEIT tool supports government-wide efforts to improve permitting and explore how online and digital technologies can promote efficient environmental reviews. This Esri ArcGIS Pro tool is included in the map package and was created to support permitting, planning, and environmental review preparation efforts by providing access to data layers from publicly available sources, including federal review, permitting, and resource agencies. An SOP on how to use the tool is available here. For the full list of APPEIT layers, see Appendix Table 1 in the SOP. The tool is comprised of an ArcGIS Pro Project containing a custom ArcGIS Toolbox tool, linked web map shared by the NTIA’s National Broadband Map (NBAM), a report template, and a Tasks item to guide users through using the tool. This ArcGIS Pro project and its contents (maps and data) are consolidated into this (.ppkx) project file. To use APPEIT, users will input a project area boundary or project route line in a shapefile or feature class format. The tool will return as a CSV and PDF report that lists any federal layers from the ArcGIS Pro Permitting and Environmental Information Web Map that intersect the project. Users may only input a single project area or line at a time; multiple projects or project segments will need to be screened separately. For project route lines, users are required to specify a buffer distance. The buffer distance that is used for broadband projects should be determined by the area of anticipated impact and should generally not exceed 500 feet. For example, the State of Maryland recommends a 100-foot buffer for broadband permitting. The tool restricts buffers to two miles to ensure relevant results. DisclaimerThis document is intended solely to assist federal broadband grant recipients and subgrantees in better understanding Infrastructure Investment and Jobs Act (IIJA) broadband grant programs and the requirements set forth in the Notice of Funding Opportunity (NOFO) for this program. This document does not and is not intended to supersede, modify, or otherwise alter applicable statutory or regulatory requirements, the terms and conditions of the award, or the specific application requirements set forth in the NOFO. In all cases, statutory and regulatory mandates, the terms and conditions of the award, the requirements set forth in the NOFO, and follow-on policies and guidance, shall prevail over any inconsistencies contained in this document. NTIA’s ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) should be used for informational purposes only and is intended solely to assist users with preliminary identification of broadband deployments that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements. The tool is not an exhaustive or complete resource and does not and is not intended to substitute for, supersede, modify, or otherwise alter any applicable statutory or regulatory requirements, or the specific application requirements set forth in any NTIA NOFO, Terms and Conditions, or Special Award Condition. In all cases, statutory and regulatory mandates, and the requirements set forth in NTIA grant documents, shall prevail over any inconsistencies contained in these templates. The tool relies on publicly available data available on the websites of other federal, state, local, and Tribal agencies, and in some instances, private organizations and research institutions. Layers identified with a double asterisk include information relevant to determining if an “extraordinary circumstance” may warrant more detailed environmental review when a categorical exclusion may otherwise apply. While NTIA continues to make amendments to its websites to comply with Section 508, NTIA cannot ensure Section 508 compliance of federal and non-federal websites or resources users may access from links on NTIA websites. All data is presented “as is,” “as available” for informational purposes. NTIA does not warrant the accuracy, adequacy, or completeness of this information and expressly disclaims liability for any errors or omissions. Please e-mail NTIAanalytics@ntia.gov with any questions.

In 2007, the California Ocean Protection Council initiated the California Seafloor Mapping Program (CSMP), designed to create a comprehensive seafloor map of high-resolution bathymetry, marine benthic habitats, and geology within California’s State Waters. The program supports a large number of coastal-zone- and ocean-management issues, including the California Marine Life Protection Act (MLPA) (California Department of Fish and Wildlife, 2008), which requires information about the distribution of ecosystems as part of the design and proposal process for the establishment of Marine Protected Areas. A focus of CSMP is to map California’s State Waters with consistent methods at a consistent scale. The CSMP approach is to create highly detailed seafloor maps through collection, integration, interpretation, and visualization of swath sonar data (the undersea equivalent of satellite remote-sensing data in terrestrial mapping), acoustic backscatter, seafloor video, seafloor photography, high-resolution seismic-reflection profiles, and bottom-sediment sampling data. The map products display seafloor morphology and character, identify potential marine benthic habitats, and illustrate both the surficial seafloor geology and shallow (to about 100 m) subsurface geology. It is emphasized that the more interpretive habitat and geology data rely on the integration of multiple, new high-resolution datasets and that mapping at small scales would not be possible without such data. This approach and CSMP planning is based in part on recommendations of the Marine Mapping Planning Workshop (Kvitek and others, 2006), attended by coastal and marine managers and scientists from around the state. That workshop established geographic priorities for a coastal mapping project and identified the need for coverage of “lands” from the shore strand line (defined as Mean Higher High Water; MHHW) out to the 3-nautical-mile (5.6-km) limit of California’s State Waters. Unfortunately, surveying the zone from MHHW out to 10-m water depth is not consistently possible using ship-based surveying methods, owing to sea state (for example, waves, wind, or currents), kelp coverage, and shallow rock outcrops. Accordingly, some of the data presented in this series commonly do not cover the zone from the shore out to 10-m depth. This data is part of a series of online U.S. Geological Survey (USGS) publications, each of which includes several map sheets, some explanatory text, and a descriptive pamphlet. Each map sheet is published as a PDF file. Geographic information system (GIS) files that contain both ESRI ArcGIS raster grids (for example, bathymetry, seafloor character) and geotiffs (for example, shaded relief) are also included for each publication. For those who do not own the full suite of ESRI GIS and mapping software, the data can be read using ESRI ArcReader, a free viewer that is available at http://www.esri.com/software/arcgis/arcreader/index.html (last accessed September 20, 2013). The California Seafloor Mapping Program is a collaborative venture between numerous different federal and state agencies, academia, and the private sector. CSMP partners include the California Coastal Conservancy, the California Ocean Protection Council, the California Department of Fish and Wildlife, the California Geological Survey, California State University at Monterey Bay’s Seafloor Mapping Lab, Moss Landing Marine Laboratories Center for Habitat Studies, Fugro Pelagos, Pacific Gas and Electric Company, National Oceanic and Atmospheric Administration (NOAA, including National Ocean Service–Office of Coast Surveys, National Marine Sanctuaries, and National Marine Fisheries Service), U.S. Army Corps of Engineers, the Bureau of Ocean Energy Management, the National Park Service, and the U.S. Geological Survey. These web services for the Offshore of Point Conception map area includes data layers that are associated to GIS and map sheets available from the USGS CSMP web page at https://walrus.wr.usgs.gov/mapping/csmp/index.html. Each published CSMP map area includes a data catalog of geographic information system (GIS) files; map sheets that contain explanatory text; and an associated descriptive pamphlet. This web service represents the available data layers for this map area. Data was combined from different sonar surveys to generate a comprehensive high-resolution bathymetry and acoustic-backscatter coverage of the map area. These data reveal a range of physiographic including exposed bedrock outcrops, large fields of sand waves, as well as many human impacts on the seafloor. To validate geological and biological interpretations of the sonar data, the U.S. Geological Survey towed a camera sled over specific offshore locations, collecting both video and photographic imagery; these “ground-truth” surveying data are available from the CSMP Video and Photograph Portal at https://doi.org/10.5066/F7J1015K. The “seafloor character” data layer shows classifications of the seafloor on the basis of depth, slope, rugosity (ruggedness), and backscatter intensity and which is further informed by the ground-truth-survey imagery. The “potential habitats” polygons are delineated on the basis of substrate type, geomorphology, seafloor process, or other attributes that may provide a habitat for a specific species or assemblage of organisms. Representative seismic-reflection profile data from the map area is also include and provides information on the subsurface stratigraphy and structure of the map area. The distribution and thickness of young sediment (deposited over the past about 21,000 years, during the most recent sea-level rise) is interpreted on the basis of the seismic-reflection data. The geologic polygons merge onshore geologic mapping (compiled from existing maps by the California Geological Survey) and new offshore geologic mapping that is based on integration of high-resolution bathymetry and backscatter imagery seafloor-sediment and rock samplesdigital camera and video imagery, and high-resolution seismic-reflection profiles. The information provided by the map sheets, pamphlet, and data catalog has a broad range of applications. High-resolution bathymetry, acoustic backscatter, ground-truth-surveying imagery, and habitat mapping all contribute to habitat characterization and ecosystem-based management by providing essential data for delineation of marine protected areas and ecosystem restoration. Many of the maps provide high-resolution baselines that will be critical for monitoring environmental change associated with climate change, coastal development, or other forcings. High-resolution bathymetry is a critical component for modeling coastal flooding caused by storms and tsunamis, as well as inundation associated with longer term sea-level rise. Seismic-reflection and bathymetric data help characterize earthquake and tsunami sources, critical for natural-hazard assessments of coastal zones. Information on sediment distribution and thickness is essential to the understanding of local and regional sediment transport, as well as the development of regional sediment-management plans. In addition, siting of any new offshore infrastructure (for example, pipelines, cables, or renewable-energy facilities) will depend on high-resolution mapping. Finally, this mapping will both stimulate and enable new scientific research and also raise public awareness of, and education about, coastal environments and issues. Web services were created using an ArcGIS service definition file. The ArcGIS REST service and OGC WMS service include all Offshore of Point Conception map area data layers. Data layers are symbolized as shown on the associated map sheets.

In the United States, the federal government manages lands in significant parts of the country. These lands include 193 million acres managed by the US Forest Service in the nation's 154 National Forests and 20 National Grasslands, Bureau of Land Management lands that cover 247 million acres in Alaska and the Western United States, 150 million acres managed for wildlife conservation by the US Fish and Wildlife Service, 84 million acres of National Parks and other lands managed by the National Park Service and over 30 million acres managed by the Department of Defense. The Bureau of Reclamation manages a much smaller land base than the other agencies included in this layer but plays a critical role in managing the country's water resources.The agencies included in this layer are:Bureau of Land ManagementBureau of ReclamationDepartment of DefenseNational Park ServiceUS Fish and Wildlife ServiceUS Forest ServiceDataset SummaryPhenomenon Mapped: United States lands managed by six federal agencies Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana Islands. The layer also includes National Monuments and Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Visible Scale: The data is visible at all scales but draws best at scales greater than 1:2,000,000Source: BLM, DoD, USFS, USFWS, NPS, PADUS 2.1Publication Date: Various - Esri compiled and published this layer in May 2022. See individual agency views for data vintage.There are six layer views available that were created from this service. Each layer uses a filter to extract an individual agency from the service. For more information about the layer views or how to use them in your own project, follow these links:USA Bureau of Land Management LandsUSA Bureau of Reclamation LandsUSA Department of Defense LandsUSA National Park Service LandsUSA Fish and Wildlife Service LandsUSA Forest Service LandsWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "federal lands" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "federal lands" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shapefile or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

The Open Basemap Streets map style provides a detailed basemap symbolized in a street map style, emphasizing the road network and urban landscape. The style provides unique capabilities for customization and high-resolution display. This comprehensive map includes highways, major and minor roads, railways, water features, cities, parks, landmarks, building footprints, administrative boundaries, and map labels. The Open Basemap vector tile layer,updated each month with the latest version of Overture data, presents global data that has been processed and hosted by Esri.Esri created the tile layer using data from the Overture Maps Foundation(OMF) which is supported by Meta, Microsoft, Amazon, TomTom, Esri and other members. Overture includes data from many sources, including OpenStreetMap (OSM). Overture Maps is a collaborative project to create reliable, easy-to-use, and interoperable open map data. Member companies work to bring together the best available open datasets, and the resulting data can be downloaded from Microsoft Azure or Amazon S3. Esri is a member of the OMF project and is excited to make this style available to the ArcGIS user community. Customize this StyleTo ensure optimal map display and minimize potential disruptions, it is highly recommended to utilize the original Open Basemap tile layer as provided. The Esri style(s) may be updated during monthly releases due to changes in the Overture Map Foundation data schema. Customizing or creating a copy of the Open Basemap tile layer can result in inconsistencies in map display and potential breaking changes. If customization is essential, you may need to implement additional updates to maintain alignment with the most current data schema. Use this MapThis map is designed to be used as a basemap layer or reference layer in a web map. You can add this layer to a web map and save as your own map. If you would like to use this map as a basemap layer in a web map, you may use the vector basemap Open Basemap (Streets) web map.Explore the Open Basemaps group for more maps and layers.

County Disaster Declaration detailed declaration records developed from FEMA Historic Disasters Declaration by County 1964 - 2013 for NSGIC resiliency project.NSGIC Data Citation:This project uses existing FEMA data resources that are the authoritative sources of information on this topic, including geospatial data files and open data APIs that were used to access available FEMA Federally-declared Natural Disaster data in the United States available from 1964 to 2014 (through 2013).To support our mapping needs, NSGIC downloaded a snapshot of FEMA data and published our own data Service Definitions and Feature Layers on NSGIC’s ArcGIS Online Mapping Platform to create the unfiltered Feature Layer Services we needed to support our mapping needs of the FEMA Federally Declared Disaster data.Note: These original data sources reflect a variety of inconsistencies and completeness is data collection, as well as changing definitions and priorities in FEMA’s disaster declaration information collection since record-keeping began in 1964. The original data was not modified.To publish the new Feature Layers on ArcGIS Online, NSGIC joined the FEMA Natural Disaster data with an Esri US County polygon shapefile with county population and demographic attributes from the U.S. Census Bureau’s American Community Survey. NSGIC added the 2010 and 2015 population estimates from the Census Bureau’s American Community Survey to relate the impacts of every declared natural disaster to current time frame.A significant portion of the available attribute data is not displayed in the NSGIC interactive maps, but is accessible through the site by experienced users.More recent data may be available from the original sourcesFEMA Data Citation:Data for this project was downloaded from FEMA in April 2016 and reflects the data available at that time using the available APIs.This product uses the Federal Emergency Management Agency’s API, but is not endorsed by FEMA.FEMA cannot verify the quality and/or timeliness of any data or any analysis derived therefrom after the data has been retrieved from FEMA.gov.NSGIC Data Citation:This project uses existing FEMA data resources that are the authoritative sources of information on this topic, including geospatial data files and open data APIs that were used to access available FEMA Federally-declared Natural Disaster data in the United States available from 1964 to 2014 (through 2013).To support our mapping needs, NSGIC downloaded a snapshot of FEMA data and published our own data Service Definitions and Feature Layers on NSGIC’s ArcGIS Online Mapping Platform to create the unfiltered Feature Layer Services we needed to support our mapping needs of the FEMA Federally Declared Disaster data.Note: These original data sources reflect a variety of inconsistencies and completeness is data collection, as well as changing definitions and priorities in FEMA’s disaster declaration information collection since record-keeping began in 1964. The original data was not modified.To publish the new Feature Layers on ArcGIS Online, NSGIC joined the FEMA Natural Disaster data with an Esri US County polygon shapefile and included the available county population and demographic attributes from the U.S. Census Bureau’s American Community Survey. A significant portion of the available attribute data is not displayed in the NSGIC interactive maps, but is accessible through the site by experienced users.More recent data may be available from the original sourcesFEMA Data Citation:Data for this project was downloaded from FEMA in April 2016 and reflects the data available at that time using the available APIs.This product uses the Federal Emergency Management Agency’s API, but is not endorsed by FEMA.FEMA cannot verify the quality and/or timeliness of any data or any analysis derived therefrom after the data has been retrieved from FEMA.gov.

Land cover describes the surface of the earth. This time-enabled service of the National Land Cover Database groups land cover into 20 classes based on a modified Anderson Level II classification system. Classes include vegetation type, development density, and agricultural use. Areas of water, ice and snow and barren lands are also identified.The National Land Cover Database products are created through a cooperative project conducted by the Multi-Resolution Land Characteristics Consortium (MRLC). The MRLC Consortium is a partnership of federal agencies, consisting of the U.S. Geological Survey, the National Oceanic and Atmospheric Administration, the U.S. Environmental Protection Agency, the U.S. Department of Agriculture, the U.S. Forest Service, the National Park Service, the U.S. Fish and Wildlife Service, the Bureau of Land Management and the USDA Natural Resources Conservation Service.Time Extent: 2001, 2004, 2006, 2008, 2011, 2013, 2016, 2019, and 2021 for the conterminous United States. The layer displays land cover for Alaska for the years 2001, 2011, and 2016. For Puerto Rico there is only data for 2001. For Hawaii, Esri reclassed land cover data from NOAA Office for Coastal Management, C-CAP into NLCD codes. These reclassed C-CAP data were available for Hawaii for the years 2001, 2005, and 2011. Hawaii C-CAP land cover in its original form can be used in your maps by adding the Hawaii CCAP Land Cover layer directly from the Living Atlas.Units: (Thematic dataset)Cell Size: 30m Source Type: Thematic Pixel Type: Unsigned 8 bitData Projection: North America Albers Equal Area Conic (102008)Mosaic Projection: North America Albers Equal Area Conic (102008)Extent: 50 US States, District of Columbia, Puerto RicoSource: National Land Cover DatabasePublication date: June 30, 2023Time SeriesThis layer is served as a time series. To display a particular year of land cover data, select the year of interest with the time slider in your map client. You may also use the time slider to play the service as an animation. We recommend a one year time interval when displaying the series. If you would like a particular year of data to use in analysis, be sure to use the analysis renderer along with the time slider to choose a valid year.North America Albers ProjectionThis layer is served in North America Albers projection. Albers is an equal area projection, and this allows users of this service to accurately calculate acreage without additional data preparation steps. This also means it takes a tiny bit longer to project on the fly into Web Mercator projection, if that is the destination projection of the service.Processing TemplatesCartographic Renderer - The default. Land cover drawn with Esri symbols. Each year's land cover data is displayed in the time series until there is a newer year of data available.Cartographic Renderer (saturated) - This renderer has the same symbols as the cartographic renderer, but the colors are extra saturated so a transparency may be applied to the layer. This renderer is useful for land cover over a basemap or relief. MRLC Cartographic Renderer - Cartographic renderer using the land cover symbols as issued by NLCD (the same symbols as is on the dataset when you download them from MRLC).Analytic Renderer - Use this in analysis. The time series is restricted by the analytic template to display a raster in only the year the land cover raster is valid. In a cartographic renderer, land cover data is displayed until a new year of data is available so that it plays well in a time series. In the analytic renderer, data is displayed for only the year it is valid. The analytic renderer won't look good in a time series animation, but in analysis this renderer will make sure you only use data for its appropriate year.Simplified Renderer - NLCD reclassified into 10 broad classes. These broad classes may be easier to use in some applications or maps.Forest Renderer - Cartographic renderer which only displays the three forest classes, deciduous, coniferous, and mixed forest.Developed Renderer - Cartographic renderer which only displays the four developed classes, developed open space plus low, medium, and high intensity development classes.Hawaii data has a different sourceMRLC redirects users interested in land cover data for Hawaii to a NOAA product called C-CAP or Coastal Change Analysis Program Regional Land Cover. This C-CAP land cover data was available for Hawaii for the years 2001, 2005, and 2011 at the time of the latest update of this layer. The USA NLCD Land Cover layer reclasses C-CAP land cover codes into NLCD land cover codes for display and analysis, although it may be beneficial for analytical purposes to use the original C-CAP data, which has finer resolution and untranslated land cover codes. The C-CAP land cover data for Hawaii is served as its own 2.4m resolution land cover layer in the Living Atlas.Because it's a different original data source than the rest of NLCD, different years for Hawaii may not be able to be compared in the same way different years for the other states can. But the same method was used to produce each year of this C-CAP derived land cover to make this layer. Note: Because there was no C-CAP data for Kaho'olawe Island in 2011, 2005 data were used for that island.The land cover is projected into the same projection and cellsize as the rest of the layer, using nearest neighbor method, then it is reclassed to approximate the NLCD codes. The following is the reclass table used to make Hawaii C-CAP data closely match the NLCD classification scheme:C-CAP code,NLCD code0,01,02,243,234,225,216,827,818,719,4110,4211,4312,5213,9014,9015,9516,9017,9018,9519,3120,3121,1122,1123,1124,025,12USA NLCD Land Cover service classes with corresponding index number (raster value):11. Open Water - areas of open water, generally with less than 25% cover of vegetation or soil.12. Perennial Ice/Snow - areas characterized by a perennial cover of ice and/or snow, generally greater than 25% of total cover.21. Developed, Open Space - areas with a mixture of some constructed materials, but mostly vegetation in the form of lawn grasses. Impervious surfaces account for less than 20% of total cover. These areas most commonly include large-lot single-family housing units, parks, golf courses, and vegetation planted in developed settings for recreation, erosion control, or aesthetic purposes.22. Developed, Low Intensity - areas with a mixture of constructed materials and vegetation. Impervious surfaces account for 20% to 49% percent of total cover. These areas most commonly include single-family housing units.23. Developed, Medium Intensity - areas with a mixture of constructed materials and vegetation. Impervious surfaces account for 50% to 79% of the total cover. These areas most commonly include single-family housing units.24. Developed High Intensity - highly developed areas where people reside or work in high numbers. Examples include apartment complexes, row houses and commercial/industrial. Impervious surfaces account for 80% to 100% of the total cover.31. Barren Land (Rock/Sand/Clay) - areas of bedrock, desert pavement, scarps, talus, slides, volcanic material, glacial debris, sand dunes, strip mines, gravel pits and other accumulations of earthen material. Generally, vegetation accounts for less than 15% of total cover.41. Deciduous Forest - areas dominated by trees generally greater than 5 meters tall, and greater than 20% of total vegetation cover. More than 75% of the tree species shed foliage simultaneously in response to seasonal change.42. Evergreen Forest - areas dominated by trees generally greater than 5 meters tall, and greater than 20% of total vegetation cover. More than 75% of the tree species maintain their leaves all year. Canopy is never without green foliage.43. Mixed Forest - areas dominated by trees generally greater than 5 meters tall, and greater than 20% of total vegetation cover. Neither deciduous nor evergreen species are greater than 75% of total tree cover. 51. Dwarf Scrub - Alaska only areas dominated by shrubs less than 20 centimeters tall with shrub canopy typically greater than 20% of total vegetation. This type is often co-associated with grasses, sedges, herbs, and non-vascular vegetation.52. Shrub/Scrub - areas dominated by shrubs; less than 5 meters tall with shrub canopy typically greater than 20% of total vegetation. This class includes true shrubs, young trees in an early successional stage or trees stunted from environmental conditions.71. Grassland/Herbaceous - areas dominated by gramanoid or herbaceous vegetation, generally greater than 80% of total vegetation. These areas are not subject to intensive management such as tilling, but can be utilized for grazing.72. Sedge/Herbaceous - Alaska only areas dominated by sedges and forbs, generally greater than 80% of total vegetation. This type can occur with significant other grasses or other grass like plants, and includes sedge tundra, and sedge tussock tundra.73. Lichens - Alaska only areas dominated by fruticose or foliose lichens generally greater than 80% of total vegetation.74. Moss - Alaska only areas dominated by mosses, generally greater than 80% of total vegetation.Planted/Cultivated 81. Pasture/Hay - areas of grasses, legumes, or grass-legume mixtures planted for livestock grazing or the production of seed or hay crops, typically on a perennial cycle. Pasture/hay vegetation accounts for greater than 20% of total vegetation.82. Cultivated Crops - areas used for the production of annual crops, such as corn, soybeans, vegetables, tobacco, and cotton, and also perennial woody crops such as orchards and vineyards. Crop vegetation accounts for greater than 20% of total vegetation. This class also includes all land being actively tilled.90. Woody Wetlands - areas where forest or shrubland vegetation accounts for greater than 20% of vegetative cover and the soil or

NSGIC Data Citation:This project uses existing FEMA data resources that are the authoritative sources of information on this topic, including geospatial data files and open data APIs that were used to access available FEMA Federally-declared Natural Disaster data in the United States available from 1964 to 2014 (through 2013).To support our mapping needs, NSGIC downloaded a snapshot of FEMA data and published our own data Service Definitions and Feature Layers on NSGIC’s ArcGIS Online Mapping Platform to create the unfiltered Feature Layer Services we needed to support our mapping needs of the FEMA Federally Declared Disaster data.Note: These original data sources reflect a variety of inconsistencies and completeness is data collection, as well as changing definitions and priorities in FEMA’s disaster declaration information collection since record-keeping began in 1964. The original data was not modified.To publish the new Feature Layers on ArcGIS Online, NSGIC joined the FEMA Natural Disaster data with an Esri US County polygon shapefile with county population and demographic attributes from the U.S. Census Bureau’s American Community Survey. NSGIC added the 2010 and 2015 population estimates from the Census Bureau’s American Community Survey to relate the impacts of every declared natural disaster to current time frame.A significant portion of the available attribute data is not displayed in the NSGIC interactive maps, but is accessible through the site by experienced users.More recent data may be available from the original sourcesFEMA Data Citation:Data for this project was downloaded from FEMA in April 2016 and reflects the data available at that time using the available APIs.This product uses the Federal Emergency Management Agency’s API, but is not endorsed by FEMA.FEMA cannot verify the quality and/or timeliness of any data or any analysis derived therefrom after the data has been retrieved from FEMA.gov.NSGIC Data Citation:This project uses existing FEMA data resources that are the authoritative sources of information on this topic, including geospatial data files and open data APIs that were used to access available FEMA Federally-declared Natural Disaster data in the United States available from 1964 to 2014 (through 2013).To support our mapping needs, NSGIC downloaded a snapshot of FEMA data and published our own data Service Definitions and Feature Layers on NSGIC’s ArcGIS Online Mapping Platform to create the unfiltered Feature Layer Services we needed to support our mapping needs of the FEMA Federally Declared Disaster data.Note: These original data sources reflect a variety of inconsistencies and completeness is data collection, as well as changing definitions and priorities in FEMA’s disaster declaration information collection since record-keeping began in 1964. The original data was not modified.To publish the new Feature Layers on ArcGIS Online, NSGIC joined the FEMA Natural Disaster data with an Esri US County polygon shapefile and included the available county population and demographic attributes from the U.S. Census Bureau’s American Community Survey. A significant portion of the available attribute data is not displayed in the NSGIC interactive maps, but is accessible through the site by experienced users.More recent data may be available from the original sourcesFEMA Data Citation:Data for this project was downloaded from FEMA in April 2016 and reflects the data available at that time using the available APIs.This product uses the Federal Emergency Management Agency’s API, but is not endorsed by FEMA.FEMA cannot verify the quality and/or timeliness of any data or any analysis derived therefrom after the data has been retrieved from FEMA.gov.

NSGIC Data Citation:This project uses existing FEMA data resources that are the authoritative sources of information on this topic, including geospatial data files and open data APIs that were used to access available FEMA Federally-declared Natural Disaster data in the United States available from 1964 to 2014 (through 2013).To support our mapping needs, NSGIC downloaded a snapshot of FEMA data and published our own data Service Definitions and Feature Layers on NSGIC’s ArcGIS Online Mapping Platform to create the unfiltered Feature Layer Services we needed to support our mapping needs of the FEMA Federally Declared Disaster data.Note: These original data sources reflect a variety of inconsistencies and completeness is data collection, as well as changing definitions and priorities in FEMA’s disaster declaration information collection since record-keeping began in 1964. The original data was not modified.To publish the new Feature Layers on ArcGIS Online, NSGIC joined the FEMA Natural Disaster data with an Esri US County polygon shapefile with county population and demographic attributes from the U.S. Census Bureau’s American Community Survey. NSGIC added the 2010 and 2015 population estimates from the Census Bureau’s American Community Survey to relate the impacts of every declared natural disaster to current time frame.A significant portion of the available attribute data is not displayed in the NSGIC interactive maps, but is accessible through the site by experienced users.More recent data may be available from the original sourcesFEMA Data Citation:Data for this project was downloaded from FEMA in April 2016 and reflects the data available at that time using the available APIs.This product uses the Federal Emergency Management Agency’s API, but is not endorsed by FEMA.FEMA cannot verify the quality and/or timeliness of any data or any analysis derived therefrom after the data has been retrieved from FEMA.gov.NSGIC Data Citation:This project uses existing FEMA data resources that are the authoritative sources of information on this topic, including geospatial data files and open data APIs that were used to access available FEMA Federally-declared Natural Disaster data in the United States available from 1964 to 2014 (through 2013).To support our mapping needs, NSGIC downloaded a snapshot of FEMA data and published our own data Service Definitions and Feature Layers on NSGIC’s ArcGIS Online Mapping Platform to create the unfiltered Feature Layer Services we needed to support our mapping needs of the FEMA Federally Declared Disaster data.Note: These original data sources reflect a variety of inconsistencies and completeness is data collection, as well as changing definitions and priorities in FEMA’s disaster declaration information collection since record-keeping began in 1964. The original data was not modified.To publish the new Feature Layers on ArcGIS Online, NSGIC joined the FEMA Natural Disaster data with an Esri US County polygon shapefile and included the available county population and demographic attributes from the U.S. Census Bureau’s American Community Survey. A significant portion of the available attribute data is not displayed in the NSGIC interactive maps, but is accessible through the site by experienced users.More recent data may be available from the original sourcesFEMA Data Citation:Data for this project was downloaded from FEMA in April 2016 and reflects the data available at that time using the available APIs.This product uses the Federal Emergency Management Agency’s API, but is not endorsed by FEMA.FEMA cannot verify the quality and/or timeliness of any data or any analysis derived therefrom after the data has been retrieved from FEMA.gov.

This submission is from a master's group thesis project at The Bren School of Environmental Science & Management at the University of California, Santa Barbara, and contains the final written report and associated datasets. The graduate student researchers who completed this project include: Meghan Fletcher, Alyssa Kibbe, Grace Kumaishi, Anna Talken, and Nikole Vannest.

The California landscape has been fragmented by urban development, infrastructure, and agriculture. Maintaining connectivity between areas of wildlife habitat is important for the viability of many long-ranging species, such as the mountain lion (Puma concolor). Mountain lion populations are highly susceptible to habitat fragmentation, and face reduced access to resources and decreased genetic diversity. This study explores the habitat connectivity between the Jack and Laura Dangermond Preserve (JLDP), a 24,460 acre protected property owned by The Nature Conservancy (TNC), and neighboring protected areas to identify potential pathways of movement for mountain lions along the Central and Southern California coast. In this project, we: 1) determine regional connectivity and least cost paths between core habitats by modeling suitable mountain lion habitat, 2) estimate mountain lion habitat use and movement on JLDP by performing a site-level suitability and corridor analysis and 3) create a short film focused on highlighting our research, the role that JLDP plays in conservation, and the importance of habitat connectivity. The results of our project show that JLDP contains suitable habitat for mountain lions and may play a positive role in coastal connectivity. When considering the connectivity between JLDP and other regional protected areas, our analyses indicate that urbanized coastal regions act as barriers to mountain lions and contain pinch points that channelize movement. These results can guide TNC in developing management strategies for protecting mountain lions on JLDP and in the surrounding region.

Analyses were conducted using ArcGIS, Google Earth Engine, MaxENT, Circuitscape, and Omniscape. The project began in April 2021 and ended in June 2022. Methods Data was collected from open source data acquired using Google Earth Engine and Esri ArcOnline from the following sources: NASA, USGS, JPL-CalTech, Conservation Science Partners, CalFish, US Census and CalFire. It was processed using Esri ArcMap, ArcGIS Pro, Maxent, Omniscape via Jupyter Notebook and the Linkage Mapper Toolkit within ArcMap.

This App includes 3,141 summary records by U.S. County for all Federal disaster declarations between 1964 and 2013. The initial map display shows the All Incidents later, but there are 12 Additional layers users can display showing the county declaration summary data by Incident Type (Fire, Flood, Tornado, etc...]. Click on an disaster declaration highlighted on the map and a custom pop-up attribute display will show you the disaster declaration information and census population estimates for reference. This App also includes a number of map tools to help visualize and analyze the data. NSGIC Data Citation:This project uses existing FEMA data resources that are the authoritative sources of information on this topic, including geospatial data files and open data APIs that were used to access available FEMA Federally-declared Natural Disaster data in the United States available from 1964 to 2014 (through 2013).To support our mapping needs, NSGIC downloaded a snapshot of FEMA data and published our own data Service Definitions and Feature Layers on NSGIC’s ArcGIS Online Mapping Platform to create the unfiltered Feature Layer Services we needed to support our mapping needs of the FEMA Federally Declared Disaster data.Note: These original data sources reflect a variety of inconsistencies and completeness is data collection, as well as changing definitions and priorities in FEMA’s disaster declaration information collection since record-keeping began in 1964. The original data was not modified.To publish the new Feature Layers on ArcGIS Online, NSGIC joined the FEMA Natural Disaster data with an Esri US County polygon shapefile with county population and demographic attributes from the U.S. Census Bureau’s American Community Survey. NSGIC added the 2010 and 2015 population estimates from the Census Bureau’s American Community Survey to relate the impacts of every declared natural disaster to current time frame.A significant portion of the available attribute data is not displayed in the NSGIC interactive maps, but is accessible through the site by experienced users.More recent data may be available from the original sourcesFEMA Data Citation:Data for this project was downloaded from FEMA in April 2016 and reflects the data available at that time using the available APIs.This product uses the Federal Emergency Management Agency’s API, but is not endorsed by FEMA.FEMA cannot verify the quality and/or timeliness of any data or any analysis derived therefrom after the data has been retrieved from FEMA.gov.

In the United States, the federal government manages approximately 28% of the land in the United States. Most federal lands are west of the Mississippi River, where almost half of the land by area is managed by the federal government. Federal lands include 193 million acres managed by the US Forest Service in 154 National Forests and 20 National Grasslands, Bureau of Land Management lands that cover 247 million acres in Alaska and the Western United States, 150 million acres managed for wildlife conservation by the US Fish and Wildlife Service, 84 million acres of National Parks and other lands managed by the National Park Service, and over 30 million acres managed by the Department of Defense. The Bureau of Reclamation manages a much smaller land base than the other agencies included in this layer but plays a critical role in managing the country's water resources. The agencies included in this layer are:Bureau of Land ManagementDepartment of DefenseNational Park ServiceUS Fish and Wildlife ServiceUS Forest ServiceDataset SummaryPhenomenon Mapped: United States federal lands managed by six federal agenciesGeographic Extent: 50 United States and the District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana Islands. The layer also includes National Monuments and Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Data Coordinate System: WGS 1984Visible Scale: The data is visible at all scales but draws best at scales greater than 1:2,000,000Source: BLM, DOD, USFS, USFWS, NPS, PADUS 3.0Publication Date: Various - Esri compiled and published this layer in May 2025. See individual agency views for data vintage.There are six layer views available that were created from this service. Each layer uses a filter to extract an individual agency from the service. For more information about the layer views or how to use them in your own project, follow these links:USA Bureau of Land Management LandsUSA Department of Defense LandsUSA National Park Service LandsUSA Fish and Wildlife Service LandsUSA Forest Service LandsWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "federal lands" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "federal lands" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shapefile or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

ParkServe® includes a comprehensive standardized database of local parks in nearly 14,000 cities, towns and communities. Census designated urban areas were used to define where to collect and create local data for cities, towns and communities. For each city, town and community, geographic boundaries were obtained from the US Census 2010 Places geospatial dataset and associated population estimates are derived from ESRI’s 2018 Demographic Forecasts. The ParkServe® team attempted to contact each city, town and community with a request for their parks data. If no GIS data was provided, the ParkServe® team created GIS data for the place based on available resources, such as park information from municipal websites, GIS data available from counties and states, and satellite imagery.Cities, towns and communities were then emailed a link to view the park data compiled in their area to verify the boundaries and attributes of the parks in the database through our custom web-based ParkReviewer™ application.ParkServe® Data InclusionProperty eligibility criteria for ParkServe®:- Publicly-owned local, state, and national parks- School parks with a joint-use agreement with the local government. Considering the scale of the project, only the joint-use agreements collected through ParkScore® were used.- Privately-owned parks that are managed for full public useExamples of property types not included in ParkServe®:- Golf courses- CemeteriesFor field descriptions, see: https://www.tpl.org/parkserve/downloads

OPEN Data View service. The Wildland Fire Risk Assessment project was developed by the National Park Service's Fire and Aviation Management program as a response to the devastating 2011 wildfire season. This project developed a consistent assessment method that has been applied to NPS units nationwide regardless of variations in climate, fuels, and topography.The assessment, based on Firewise® assessment forms, evaluates access, surrounding environment, construction design and materials, and resources available to protect facilities from wildland fire. The data collected during the assessment process can be used for:Identifying, planning, prioritizing and tracking fuels treatments at unit, regional and national levels, and Developing incident response plans for facilities and communities within NPS units.The original spatial data for the assessments comes from a variety of sources including the NPS Buildings Enterprise Dataset, WFDSS, NPMap Edits, manually digitized points using Esri basemaps as a reference at various scales, and GPS collection using a multitude of consumer and professional grade GPS devices. The facilities that have been assessed and assigned a facility risk rating have been ground-truthed and field verified. (In some rare occasions, facilities have been verified during remote assessments. Those that have been remotely assessed are marked as such). The resulting data is stored in a centralized geodatabase, and this publicly available feature layer allows the user to view that data.The NPS Facilities feature layer includes the following layers and related tables:Facility - A facility is defined by the NPS as an asset that the NPS desires to track and manage as a distinct identifiable entity. In the case of wildland fire risk assessments, a facility is most often a structure but in special instances, a park unit may wish to identify and assess other at-risk features such as a historic wooden bridge or an interpretive display. The facilities are assessed based on access, the surrounding environment, construction design, and protection resources and limitations, resulting in a numerical score and risk adjective rating for each facility. These ratings designate the likelihood of ignition during a wildland fire. The facilities are symbolized by their respective risk rating.Community - A community is a group of five or more facilities, a majority of which are within 600 feet of each other, that share common access and protection attributes. The community concept was developed to facilitate data collection and entry in areas with multiple facilities and where it made sense to apply treatments and tactics at a scale larger than individual facilities. Most of the community polygons are created using models in ArcMap, but some may have been created or edited in the field using a Trimble GPS unit. *The NPS Facilities layer is updated continually as new wildfire risk assessments are conducted and the Wildland Fire Risk Assessment project progresses. The assessment data contained here is the most current data available.*More information about the NPS Wildland Fire Risk Assessment Project, and the NPS Facilities data itself, can be found at the New Wildland Fire Risk Assessments website. This site provides information on the data collection process, additional ways to access the data, and how to conduct assessments yourself (for both NPS and non-NPS facilities).FACILITY ATTRIBUTES
Unit_ID NWCG Unit ID, Two letter state code and three letter unit abbreviation, for example UTZIP for Zion National Park in Utah.

Fire_Bldg_ID User maintained unique ID for Facility layer.

Building ID Unique Id from the NPS Enterprise Buildings dataset.

FMSS ID Unique ID for the facility in the NPS FMSS database.

Community ID Unique ID linking facility to a community

Assess Scale Indicates if the facility is part of a community/ will be included in a community assessment. Communities are pre-defined by regional GIS staff and visible in this map as a blue perimeter.
Answer "Yes" if you are adding a facility point within a predefined community.

Common Name Name of the structure. In most cases, the name comes from the NPS FMSS database.

Map Label Numerical label used for mapping purposes.

Owner Indicates who owns the structure being assessed.

Facilty Type Indicates the facility type OR if the facility has been REMOVED, DESTROYED, has NO WILDLAND RISK, is PRIVATE - NO SURVEY REQUIRED or DOES NOT REQUIRE A SURVEY (because it is planned for removal).

Facility Use What is the primary use of the facility?

Building Occupied Is the building occupied?

Community Name Name of the community the facility is located within, if any.

Field Crew Field crew completing the assessment.

Last Site Visit Date Date which the facility was visited and assessment data reviewed/updated.

Location General location within the unit – may use FMUs, watersheds, or other identifier. One location may contain multiple communities and individual facilities. Locations are used to filter data for reports and map products.

PrimaryAccess Primary method of accessing the facility.

IngressEgress Number of routes into and away from the facility.

AccessWidth Width of the road or driveway used to access the facility.

AccessCond Grade and surface material of the road or driveway used to access the facility.

BridgeCond Condition, based on load limits and construction.

Turnaround Describes how close can a fire apparatus drive to the facility and once there, whether it can turnaround.

BldgNum Is the facility clearly signed or numbered?

FuelLoad Fuel loading within 300 ft of the facility (see appendix D of the Wildfire Risk Assessment User Guide)

FuelType Predominant fuel type within 300 ft of the facility.

DefensibleSpace Amount of defensible space around the facility, see criteria for evaluating defensible space in the Wildfire Risk Assessment User Guide.

Topography Predominant slope within 300 ft of facility.

RoofMat Roofing material used on the facility.

SidingMat Siding material used on the facility.

Foundation Describes the facility’s foundation.

Fencing Indicates presence of any wooden attachments, fencing, decking, pergola, etc. and fuels clearance around those attachments.

Firewood Firewood distance from facility.

Propane Inidicates if a propane tank exists within 200 feet of a structure and if there is any fuels clearance around the propane tank(s).

Hazmat List of hazmat existing on the site.

WaterSupply Water supply available to the facility.

OverheadHaz Identifies the presence of overhead hazards that will limit aerial firefighting efforts.

SafetyZone Identifies the presence of any potential safety zones.

SZRadius Radius of any potential safety zones.

Obstacles Additional obstacles, not already included in assessment, that will limit firefighting efforts- to include items such as UXO, hazmat,etc. If there are additional obstacles, be sure to comment in Assessment Comments or Tactic descriptions where appropriate.

TriageCategory Refer to IRPG for descriptions of each category. This information will be displayed in the NIFS Structure Triage layer for incident response.

Score Sum of attribute values for all assessment elements including access, environment, structure and protection portions of the assessment.

Rating Wildland fire risk rating based on score. Ratings are No Wildland Risk, Low, Moderate and High. Rating indicates likelihood if facility igniting if a wildland fire occurs.

ProtectionLevel Inidcates structures which are priority for protection during a wildfire. For Alaska Region data, indicates identified protection level for structure. For lower 48, enter ‘Unknown’ unless specified by local unit.

ProtLevelApprovalName Name of person who designated Protection Level

ProtLevelApprovalDate Date Protection Level Designated

ResourcesOfConcern Indicates if it is necessary to contact park staff before engaging in suppression activities because special resources (natural, cultural, historic) of concern are present?

AssessComments Explain any aspects of the assessment that require extra detail.

RegionCode NPS Region Code - AKR, IMR, NER, NCR, MWR, PWR or SER

UnitCode

NPS Unit Code

ReasonIncluded Why is the point in the dataset – NPS owned, Treatment Planning, Protection Responsibility, Planning (other than treatments). Intent of the dataset is to document wildfire risk for NPS owned structures. Other structures or facilities may be included at the discretion of the unit's fire management staff.

Restriction How can the data be shared – Unrestricted, Restricted - No Third Party Release, Restricted – Originating Agency Concurrence, Restricted – Affected Cultural Group Concurrence, Restricted - No Release, Unknown. Only unrestricted data is included in this dataset.

Local_ID Field which can be used to store unique ids linking back to any local datasets.

RevisitInterval How many years will it take for the fuels to change significantly enough to change the score and rating for this facility?

IsVisited Use this field to keep track of what you have done during a field session. Filter on this field to see what has been assessed and what still needs visited during a field data collection session.

DeleteThis Users enter yes if this is this a duplicate or was no facility found.
If you know the facility was REMOVED or DESTROYED, go back to Facility Type and enter that information there.

Data_Source

FirewiseZone1 List of treatments needed to

This layer shows which parts of the United States and Puerto Rico fall within ten minutes' walk of one or more grocery stores. It is estimated that 20% of U.S. population live within a 10 minute walk of a grocery store, and 92% of the population live within a 10 minute drive of a grocery store. The layer is suitable for looking at access at a neighborhood scale. When you add this layer to your web map, along with the drivable access layer and the SafeGraph grocery store layer, it becomes easier to spot grocery stores that sit within a highly populated area, and grocery stores that sit in a shopping center far away from populated areas. Add the Census block points layer to show a popup with the count of stores within 10 minutes' walk and drive. This view of a city begins to hint at the question: how many people have each type of access to grocery stores? And, what if they are unable to walk a mile regularly, or do not own a car? How to Use This Layer in a Web MapUse this layer in a web map to introduce the concepts of access to grocery stores in your city or town. This is the kind of map where people will want to look up their home or work address to validate what the map is saying. See this example web map which you can use in your projects, storymaps, apps and dashboards. The layer was built with that use in mind. Many maps of access use straight-line, as-the-crow-flies distance, which ignores real-world barriers to walkability like rivers, lakes, interstates and other characteristics of the built environment. Block analysis using a network data set and Origin-Destination analysis factors these barriers in, resulting in a more realistic depiction of access. Lastly, this layer can serve as backdrop to other community resources, like food banks, farmers markets (example), and transit (example). Add a transit layer to immediately gauge its impact on the population's grocery access. You can also use this map to see how it relates to communities of concern. Add a layer of any block group or tract demographics, such as Percent Senior Population (examples), or Percent of Households with Access to 0 Vehicles (examples). The layer is a useful visual resource for helping community leaders, business and government leaders see their town from the perspective of its residents, and begin asking questions about how their community could be improved. Data sourcesPopulation data is from the 2010 U.S. Census blocks. Each census block has a count of stores within a 10 minute walk, and a count of stores within a ten minute drive. Census blocks known to be unpopulated are given a score of 0. The layer is available as a hosted feature layer. Grocery store locations are from SafeGraph, reflecting what was in the data as of October 2020. Access to the layer was obtained from the SafeGraph offering in ArcGIS Marketplace. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it already has the necessary attributes on each street segment to identify which streets are considered walkable, and supports a wide variety of driving parameters. The walkable access layer and drivable access layers are rasters, whose colors were chosen to allow the drivable access layer to serve as backdrop to the walkable access layer. Data PreparationArcGIS Network Analyst was used to set up a network street layer for analysis. ArcGIS StreetMap Premium was installed to a local hard drive and selected in the Origin-Destination workflow as the network data source. This allows the origins (Census block centroids) and destinations (SafeGraph grocery stores) to be connected to that network, to allow origin-destination analysis. The Census blocks layer contains the centroid of each Census block. The data allows a simple popup to be created. This layer's block figures can be summarized further, to tract, county and state levels. The SafeGraph grocery store locations were created by querying the SafeGraph source layer based on primary NAICS code. After connecting to the layer in ArcGIS Pro, a definition query was set to only show records with NAICS code 445110 as an initial screening. The layer was exported to a local disk drive for further definition query refinement, to eliminate any records that were obviously not grocery stores. The final layer used in the analysis had approximately 53,600 records. In this map, this layer is included as a vector tile layer. Methodology Every census block in the U.S. was assigned two access scores, whose numbers are simply how many grocery stores are within a 10 minute walk and a 10 minute drive of that census block. Every census block has a score of 0 (no stores), 1, 2 or more stores. The count of accessible stores was determined using Origin-Destination Analysis in ArcGIS Network Analyst, in ArcGIS Pro. A set of Tools in this ArcGIS Pro package allow a similar analysis to be conducted for any city or other area. The Tools step through the data prep and analysis steps. Download the Pro package, open it and substitute your own layers for Origins and Destinations. Parcel centroids are a suggested option for Origins, for example. Origin-Destination analysis was configured, using ArcGIS StreetMap Premium as the network data source. Census block centroids with population greater than zero were used as the Origins, and grocery store locations were used as the Destinations. A cutoff of 10 minutes was used with the Walk Time option. Only one restriction was applied to the street network: Walkable, which means Interstates and other non-walkable street segments were treated appropriately. You see the results in the map: wherever freeway overpasses and underpasses are present near a grocery store, the walkable area extends across/through that pass, but not along the freeway. A cutoff of 10 minutes was used with the Drive Time option. The default restrictions were applied to the street network, which means a typical vehicle's access to all types of roads was factored in. The results for each analysis were captured in the Lines layer, which shows which origins are within the cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle). The Lines layer was then summarized by census block ID to capture the Maximum value of the Destination_Rank field. A census block within 10 minutes of 3 stores would have 3 records in the Lines layer, but only one value in the summarized table, with a MAX_Destination_Rank field value of 3. This is the number of stores accessible to that census block in the 10 minutes measured, for walking and driving. These data were joined to the block centroids layer and given unique names. At this point, all blocks with zero population or null values in the MAX_Destination_Rank fields were given a store count of 0, to help the next step. Walkable and Drivable areas are calculated into a raster layer, using Nearest Neighbor geoprocessing tool on the count of stores within a 10 minute walk, and a count of stores within a ten minute drive, respectively. This tool uses a 200 meter grid and interpolates the values between each census block. A census tracts layer containing all water polygons "erased" from the census tract boundaries was used as an environment setting, to help constrain interpolation into/across bodies of water. The same layer use used to "shoreline" the Nearest Neighbor results, to eliminate any interpolation into the ocean or Great Lakes. This helped but was not perfect. Notes and LimitationsThe map provides a baseline for discussing access to grocery stores in a city. It does not presume local population has the desire or means to walk or drive to obtain groceries. It does not take elevation gain or loss into account. It does not factor time of day nor weather, seasons, or other variables that affect a person's commute choices. Walking and driving are just two ways people get to a grocery store. Some people ride a bike, others take public transit, have groceries delivered, or rely on a friend with a vehicle. Thank you to Melinda Morang on the Network Analyst team for guidance and suggestions at key moments along the way; to Emily Meriam for reviewing the previous version of this map and creating new color palettes and marker symbols specific to this project. Additional ReadingThe methods by which access to food is measured and reported have improved in the past decade or so, as has the uses of such measurements. Some relevant papers and articles are provided below as a starting point. Measuring Food Insecurity Using the Food Abundance Index: Implications for Economic, Health and Social Well-BeingHow to Identify Food Deserts: Measuring Physical and Economic Access to Supermarkets in King County, WashingtonAccess to Affordable and Nutritious Food: Measuring and Understanding Food Deserts and Their ConsequencesDifferent Measures of Food Access Inform Different SolutionsThe time cost of access to food – Distance to the grocery store as measured in minutes

Description based on the metadata provided by the WMDs.NWFWMD: Watershed Delineation for NWFWMD. Custodian - Danny Layfield.The Northwest Florida Water Management District maintains the following GIS Data Dictionary as a public service, by granting the public and government agencies access to the Districts GIS data.Data is provided on an "as is" basis. In no event will the District or its staff be liable for any direct, indirect, incidental, special, consequential, or other damages, including loss of profit, arising out of the use of these data even if the District has been advised of the possibility of such damages.The spatial datasets are provided as zipped (.zip) ESRI shapefiles or geodatabases. The data are provided in UTM Zone 16N / NAD 83, map units metershttp://www.nwfwmd.state.fl.us/data-publications/gis-mapping/gis-data-directorySRWMD: Hydrography basin major. USGS24"SBAS" was orginally created by USGS as part of a cooperative effort between the USGS and DEP to create a statewide basin or watershed map. SRWMD has modified and added some watersheds because of local knowledge and needs of the District. A number of items have also been added to the coverage. Surfacewater watersheds are topographic land features which contain a unique hydrologic area of surface drainage. Suwannee River Water Management has choosen to call this a watershed map instead of a basin map as previously called. These spatial data sets provide SRWMD and other government agencies with a consolidated resource for watershed information at various levels of geographic extent. The data sets are intended to support watershed analysis, planning, permitting, regulatory, and other functions at SRWMD. They have been edited and modified by the District to reflect better information available at the regional level, and to better meet the specific needs of the GIS users at SRWMD. A guide to the Watershed coverage is available from SRWMD at md_lib/basins/items.doc. A spreadsheet that expains the attribution of both the polygon and arc attribute tables is also located at md_lib/basins/sbas_items.doc. Additional information about the original watershed maps created by USGS is available from the following sources: U.S. Geological Survey, 1994. Metadata for Hydrologic units maps of the Conterminous United States, 1:250,000-scale (nominal), ARC/INFO format. < http://water.usgs.gov/lookup/getspatial?/huc250k> U.S. Geological Survey, 1990. Land Use and Land Cover Digital Data from 1:250,000- and 1:100,000-Scale Maps. Data Users Guide 4, 33 pp, Reston, Virginia. U.S. Environmental Protection Agency, 1996. Metadata for Hydrologic Unit Boundaries of the Conterminous United States, 1:250,000-scale (nominal), ARC/INFO Format, < http://www.epa.gov/nsdi/projects/catunit.htm>Note: This data was created by the Suwannee River Water Management District (SRWMD) to be used for planning purposes only. SRWMD shall not be held liable for any injury or damage caused by the use of data distributed as a public records request regardless of their use or application. SRWMD does not guarantee the accuracy, or suitability for any use of these data, and no warranty is expressed or implied. In no event will the SRWMD, its staff, or the contributing agencies be liable for any direct, indirect, incidental, special, consequential or other damages, including loss of profit, arising from the use of these data, even if the District has been advised of the possibility of such damages. Users of this data should therefore do so at their own risk. For more information please contact the SRWMD at 386-362-1001.http://www.srwmd.state.fl.us/index.aspx?NID=319SJRWMD: This coverage was originally created in September 2000 by GIS staff in the Resource Management Dept. It was created in Arc/Info, using the SJRWMD surface water drainage basins layer as a guideline. The swbasins were combined and shifted in places, to delineate ecology based areas for regulatory mitigation review. The changes came from a Board-appointed Advisory Committee and were approved by the Board and adopted by rule.The coverage corresponds to the basin boundaries found in the ERP Applicant's Handbook in Figure 12.2.8-1 and Appendix M. This is a special layer created specifically for regulatory purposes; it is distinct from the standard SJRWMD Surface Water Drainage Basins Layer. This layer mitig basin reg is to delineate ecologically based areas for regulatory mitigation review. This data reflects all Mitigation Basin changes approved by the Governing Board and effective as of November 5, 2008.For more information contact St. Johns River Water Management District 386-312-2314.http://floridaswater.com/gisdevelopment/docs/themes.htmlSWFWMD: This layer illustrates the extent of Comprehensive Watershed Management (CWM) watershed boundaries in the Southwest Florida Water Management District. This layer should be used for cartographic and resource management purposes.Watershed boundaries used in the Comprehensive Watershed Management (CWM) program. These boundaries were derived from the DBASINS coverage.These data were not collected under the supervision of a licensed Professional Surveyor and Mapper. Use of these data requires a general understanding of GIS.The data are being provided on an 'as is' basis. The District specifically disclaims any warranty, expressed or implied, including, but not limited to, the implied warranties or merchantability and fitness for a particular use. The entire risk as to quality and performance is with the user. In no event will the District or its staff be liable for any direct, indirect, incidental, special, consequential, or other damages, including loss of profit, arising out of the use of these data even if the District has been advised of the possibility of such damages. All data are intended for resource management use.For more information contact the Southwest Florida Water Management District (352) 796-7211. https://www.swfwmd.state.fl.us/data/gis/layer_library/category/physical_sparseSFWMD: Recreation of Figure 4.4.1 in Volume IV Basis of Review. 1989 Basins and Cumulative Impact Basins (fka Watersheds).For more information contact the South Florida Water Management District (561) 686-8800.http://www.sfwmd.gov/gisapps/sfwmdxwebdc/dataview.asp?

This layer shows which parts of the United States and Puerto Rico fall within ten minutes" walk of one or more grocery stores. It is estimated that 20% of U.S. population live within a 10 minute walk of a grocery store, and 92% of the population live within a 10 minute drive of a grocery store. The layer is suitable for looking at access at a neighborhood scale. When you add this layer to your web map, along with the drivable access layer and the SafeGraph grocery store layer, it becomes easier to spot grocery stores that sit within a highly populated area, and grocery stores that sit in a shopping center far away from populated areas. Add the Census block points layer to show a popup with the count of stores within 10 minutes" walk and drive. This view of a city begins to hint at the question: how many people have each type of access to grocery stores? And, what if they are unable to walk a mile regularly, or don"t own a car? How to Use This Layer in a Web MapUse this layer in a web map to introduce the concepts of access to grocery stores in your city or town. This is the kind of map where people will want to look up their home or work address to validate what the map is saying. See this example web map which you can use in your projects, storymaps, apps and dashboards. The layer was built with that use in mind. Many maps of access use straight-line, as-the-crow-flies distance, which ignores real-world barriers to walkability like rivers, lakes, interstates and other characteristics of the built environment. Block analysis using a network data set and Origin-Destination analysis factors these barriers in, resulting in a more realistic depiction of access. Lastly, this layer can serve as backdrop to other community resources, like food banks, farmers markets (example), and transit (example). Add a transit layer to immediately gauge its impact on the population"s grocery access. You can also use this map to see how it relates to communities of concern. Add a layer of any block group or tract demographics, such as Percent Senior Population (examples), or Percent of Households with Access to 0 Vehicles (examples). The layer is a useful visual resource for helping community leaders, business and government leaders see their town from the perspective of its residents, and begin asking questions about how their community could be improved. Data sourcesPopulation data is from the 2010 U.S. Census blocks. Each census block has a count of stores within a 10 minute walk, and a count of stores within a ten minute drive. Census blocks known to be unpopulated are given a score of 0. The layer is available as a hosted feature layer. Grocery store locations are from SafeGraph, reflecting what was in the data as of October 2020. Access to the layer was obtained from the SafeGraph offering in ArcGIS Marketplace. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it already has the necessary attributes on each street segment to identify which streets are considered walkable, and supports a wide variety of driving parameters. The walkable access layer and drivable access layers are rasters, whose colors were chosen to allow the drivable access layer to serve as backdrop to the walkable access layer. Data PreparationArcGIS Network Analyst was used to set up a network street layer for analysis. ArcGIS StreetMap Premium was installed to a local hard drive and selected in the Origin-Destination workflow as the network data source. This allows the origins (Census block centroids) and destinations (SafeGraph grocery stores) to be connected to that network, to allow origin-destination analysis. The Census blocks layer contains the centroid of each Census block. The data allows a simple popup to be created. This layer"s block figures can be summarized further, to tract, county and state levels. The SafeGraph grocery store locations were created by querying the SafeGraph source layer based on primary NAICS code. After connecting to the layer in ArcGIS Pro, a definition query was set to only show records with NAICS code 445110 as an initial screening. The layer was exported to a local disk drive for further definition query refinement, to eliminate any records that were obviously not grocery stores. The final layer used in the analysis had approximately 53,600 records. In this map, this layer is included as a vector tile layer. Methodology Every census block in the U.S. was assigned two access scores, whose numbers are simply how many grocery stores are within a 10 minute walk and a 10 minute drive of that census block. Every census block has a score of 0 (no stores), 1, 2 or more stores. The count of accessible stores was determined using Origin-Destination Analysis in ArcGIS Network Analyst, in ArcGIS Pro. A set of Tools in this ArcGIS Pro package allow a similar analysis to be conducted for any city or other area. The Tools step through the data prep and analysis steps. Download the Pro package, open it and substitute your own layers for Origins and Destinations. Parcel centroids are a suggested option for Origins, for example. Origin-Destination analysis was configured, using ArcGIS StreetMap Premium as the network data source. Census block centroids with population greater than zero were used as the Origins, and grocery store locations were used as the Destinations. A cutoff of 10 minutes was used with the Walk Time option. Only one restriction was applied to the street network: Walkable, which means Interstates and other non-walkable street segments were treated appropriately. You see the results in the map: wherever freeway overpasses and underpasses are present near a grocery store, the walkable area extends across/through that pass, but not along the freeway. A cutoff of 10 minutes was used with the Drive Time option. The default restrictions were applied to the street network, which means a typical vehicle"s access to all types of roads was factored in. The results for each analysis were captured in the Lines layer, which shows which origins are within the cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle). The Lines layer was then summarized by census block ID to capture the Maximum value of the Destination_Rank field. A census block within 10 minutes of 3 stores would have 3 records in the Lines layer, but only one value in the summarized table, with a MAX_Destination_Rank field value of 3. This is the number of stores accessible to that census block in the 10 minutes measured, for walking and driving. These data were joined to the block centroids layer and given unique names. At this point, all blocks with zero population or null values in the MAX_Destination_Rank fields were given a store count of 0, to help the next step. Walkable and Drivable areas are calculated into a raster layer, using Nearest Neighbor geoprocessing tool on the count of stores within a 10 minute walk, and a count of stores within a ten minute drive, respectively. This tool uses a 200 meter grid and interpolates the values between each census block. A census tracts layer containing all water polygons "erased" from the census tract boundaries was used as an environment setting, to help constrain interpolation into/across bodies of water. The same layer use used to "shoreline" the Nearest Neighbor results, to eliminate any interpolation into the ocean or Great Lakes. This helped but was not perfect. Notes and LimitationsThe map provides a baseline for discussing access to grocery stores in a city. It does not presume local population has the desire or means to walk or drive to obtain groceries. It does not take elevation gain or loss into account. It does not factor time of day nor weather, seasons, or other variables that affect a person"s commute choices. Walking and driving are just two ways people get to a grocery store. Some people ride a bike, others take public transit, have groceries delivered, or rely on a friend with a vehicle. Thank you to Melinda Morang on the Network Analyst team for guidance and suggestions at key moments along the way; to Emily Meriam for reviewing the previous version of this map and creating new color palettes and marker symbols specific to this project. Additional ReadingThe methods by which access to food is measured and reported have improved in the past decade or so, as has the uses of such measurements. Some relevant papers and articles are provided below as a starting point. Measuring Food Insecurity Using the Food Abundance Index: Implications for Economic, Health and Social Well-BeingHow to Identify Food Deserts: Measuring Physical and Economic Access to Supermarkets in King County, WashingtonAccess to Affordable and Nutritious Food: Measuring and Understanding Food Deserts and Their ConsequencesDifferent Measures of Food Access Inform Different SolutionsThe time cost of access to food – Distance to the grocery store as measured in minutes