This vector tile layer is designed to support exporting small volumes of basemap tiles for offline use. The content of this layer is equivalent to World Terrain Reference map. This layer provides a detailed basemap for the world symbolized with populated places, and admin area boundary lines. The minimal features and styling is designed to draw attention to your thematic content. It is designed for use with World Terrain Base and shaded relief for added content. See World Terrain Reference for more details.Use this MapThis vector tile service supporting this layer will enable you to export a small number of tiles in a single request. This layer is not intended to be used to display live map tiles for use in a web map or web mapping application. To display map tiles, please use World Terrain Reference.Service Information for DevelopersTo export tiles for World Terrain Reference (for Export), you must use the instance of the World_Basemap_Export_v2 service hosted on basemaps.arcgis.com referenced by this layer (see URL in Contents below), which has the Export Tiles operation enabled. This layer is optimized to minimize the size of the download for offline use. Due to this optimization, there are small differences between this layer and the display optimized World_Basemap_v2 service. This layer is intended to support export of basemap tiles for offline use in ArcGIS applications and other applications built with an ArcGIS Runtime SDK.

These are the main layers that were used in the mapping and analysis for the Santa Monica Mountains Local Coastal Plan, which was adopted by the Board of Supervisors on August 26, 2014, and certified by the California Coastal Commission on October 10, 2014. Below are some links to important documents and web mapping applications, as well as a link to the actual GIS data:

Plan Website – This has links to the actual plan, maps, and a link to our online web mapping application known as SMMLCP-NET. Click here for website. Online Web Mapping Application – This is the online web mapping application that shows all the layers associated with the plan. These are the same layers that are available for download below. Click here for the web mapping application. GIS Layers – This is a link to the GIS layers in the form of an ArcGIS Map Package, click here (LINK TO FOLLOW SOON) for ArcGIS Map Package (version 10.3). Also, included are layers in shapefile format. Those are included below.

Below is a list of the GIS Layers provided (shapefile format):

Recreation (Zipped - 5 MB - click here)

Coastal Zone Campground Trails (2012 National Park Service) Backbone Trail Class III Bike Route – Existing Class III Bike Route – Proposed

Scenic Resources (Zipped - 3 MB - click here)

Significant Ridgeline State-Designated Scenic Highway State-Designated Scenic Highway 200-foot buffer Scenic Route Scenic Route 200-foot buffer Scenic Element

Biological Resources (Zipped - 45 MB - click here)

National Hydrography Dataset – Streams H2 Habitat (High Scrutiny) H1 Habitat H1 Habitat 100-foot buffer H1 Habitat Quiet Zone H2 Habitat H3 Habitat

Hazards (Zipped - 8 MB - click here)

FEMA Flood Zone (100-year flood plain) Liquefaction Zone (Earthquake-Induced Liquefaction Potential) Landslide Area (Earthquake-Induced Landslide Potential) Fire Hazard and Responsibility Area

Zoning and Land Use (Zipped - 13 MB - click here)

Malibu LCP – LUP (1986) Malibu LCP – Zoning (1986) Land Use Policy Zoning

Other Layers (Zipped - 38 MB - click here)

Coastal Commission Appeal Jurisdiction Community Names Santa Monica Mountains (SMM) Coastal Zone Boundary Pepperdine University Long Range Development Plan (LRDP) Rural Village

Contact the L.A. County Dept. of Regional Planning's GIS Section if you have questions. Send to our email.

This vector tile layer is designed to support exporting small volumes of basemap tiles for offline use. The content of this layer is equivalent to World Navigation Map (Dark). This layer includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries featuring a custom dark mode navigation map style. See World Navigation Map (Dark) for more details.Use this MapThis vector tile service supporting this layer will enable you to export a small number of tiles in a single request. This layer is not intended to be used to display live map tiles for use in a web map or web mapping application. To display map tiles, please use World Navigation Map (Dark).Service Information for DevelopersTo export tiles for World Navigation Map (Dark Mode - for Export), you must use the instance of the World_Basemap_Export_v2 service hosted on basemaps.arcgis.com referenced by this layer (see URL in Contents below), which has the Export Tiles operation enabled. This layer is optimized to minimize the size of the download for offline use. Due to this optimization, there are small differences between this layer and the display optimized World_Basemap_v2 service. This layer is intended to support export of basemap tiles for offline use in ArcGIS applications and other applications built with an ArcGIS Runtime SDK.

This is a tiled collection of the 3D Elevation Program (3DEP) and is one meter resolution. The 3DEP data holdings serve as the elevation layer of The National Map, and provide foundational elevation information for earth science studies and mapping applications in the United States. Scientists and resource managers use 3DEP data for hydrologic modeling, resource monitoring, mapping and visualization, and many other applications. The elevations in this DEM represent the topographic bare-earth surface. USGS standard one-meter DEMs are produced exclusively from high resolution light detection and ranging (lidar) source data of one-meter or higher resolution. One-meter DEM surfaces are seamless within collection projects, but, not necessarily seamless across projects. The spatial reference used for tiles of the one-meter DEM within the conterminous United States (CONUS) is Universal Transverse Mercator (UTM) in units of meters, and in conformance with the North American Datum of 1983 ...

This webmap is a subset of Global Landcover 1992 - 2020 Image Layer. You can access the source data from here. This layer is a time series of the annual ESA CCI (Climate Change Initiative) land cover maps of the world. ESA has produced land cover maps for the years 1992-2020. These are available at the European Space Agency Climate Change Initiative website.Time Extent: 1992-2020Cell Size: 300 meterSource Type: ThematicPixel Type: 8 Bit UnsignedData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: GlobalSource: ESA Climate Change InitiativeUpdate Cycle: Annual until 2020, no updates thereafterWhat can you do with this layer?This layer may be added to ArcGIS Online maps and applications and shown in a time series to watch a "time lapse" view of land cover change since 1992 for any part of the world. The same behavior exists when the layer is added to ArcGIS Pro.In addition to displaying all layers in a series, this layer may be queried so that only one year is displayed in a map. This layer can be used in analysis. For example, the layer may be added to ArcGIS Pro with a query set to display just one year. Then, an area count of land cover types may be produced for a feature dataset using the zonal statistics tool. Statistics may be compared with the statistics from other years to show a trend.To sum up area by land cover using this service, or any other analysis, be sure to use an equal area projection, such as Albers or Equal Earth.Different Classifications Available to MapFive processing templates are included in this layer. The processing templates may be used to display a smaller set of land cover classes.Cartographic Renderer (Default Template)Displays all ESA CCI land cover classes.*Forested lands TemplateThe forested lands template shows only forested lands (classes 50-90).Urban Lands TemplateThe urban lands template shows only urban areas (class 190).Converted Lands TemplateThe converted lands template shows only urban lands and lands converted to agriculture (classes 10-40 and 190).Simplified RendererDisplays the map in ten simple classes which match the ten simplified classes used in 2050 Land Cover projections from Clark University.Any of these variables can be displayed or analyzed by selecting their processing template. In ArcGIS Online, select the Image Display Options on the layer. Then pull down the list of variables from the Renderer options. Click Apply and Close. In ArcGIS Pro, go into the Layer Properties. Select Processing Templates from the left hand menu. From the Processing Template pull down menu, select the variable to display.Using TimeBy default, the map will display as a time series animation, one year per frame. A time slider will appear when you add this layer to your map. To see the most current data, move the time slider until you see the most current year.In addition to displaying the past quarter century of land cover maps as an animation, this time series can also display just one year of data by use of a definition query. For a step by step example using ArcGIS Pro on how to display just one year of this layer, as well as to compare one year to another, see the blog called Calculating Impervious Surface Change.Hierarchical ClassificationLand cover types are defined using the land cover classification (LCCS) developed by the United Nations, FAO. It is designed to be as compatible as possible with other products, namely GLCC2000, GlobCover 2005 and 2009.This is a heirarchical classification system. For example, class 60 means "closed to open" canopy broadleaved deciduous tree cover. But in some places a more specific type of broadleaved deciduous tree cover may be available. In that case, a more specific code 61 or 62 may be used which specifies "open" (61) or "closed" (62) cover.Land Cover ProcessingTo provide consistency over time, these maps are produced from baseline land cover maps, and are revised for changes each year depending on the best available satellite data from each period in time. These revisions were made from AVHRR 1km time series from 1992 to 1999, SPOT-VGT time series between 1999 and 2013, and PROBA-V data for years 2013, 2014 and 2015. When MERIS FR or PROBA-V time series are available, changes detected at 1 km are re-mapped at 300 m. The last step consists in back- and up-dating the 10-year baseline LC map to produce the 24 annual LC maps from 1992 to 2015.Source dataThe datasets behind this layer were extracted from NetCDF files and TIFF files produced by ESA. Years 1992-2015 were acquired from ESA CCI LC version 2.0.7 in TIFF format, and years 2016-2018 were acquired from version 2.1.1 in NetCDF format. These are downloadable from ESA with an account, after agreeing to their terms of use. https://maps.elie.ucl.ac.be/CCI/viewer/download.phpCitationESA. Land Cover CCI Product User Guide Version 2. Tech. Rep. (2017). Available at: maps.elie.ucl.ac.be/CCI/viewer/download/ESACCI-LC-Ph2-PUGv2_2.0.pdfMore technical documentation on the source datasets is available here:https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-land-cover?tab=doc*Index of all classes in this layer:10 Cropland, rainfed11 Herbaceous cover12 Tree or shrub cover20 Cropland, irrigated or post-flooding30 Mosaic cropland (>50%) / natural vegetation (tree, shrub, herbaceous cover) (<50%)40 Mosaic natural vegetation (tree, shrub, herbaceous cover) (>50%) / cropland (<50%)50 Tree cover, broadleaved, evergreen, closed to open (>15%)60 Tree cover, broadleaved, deciduous, closed to open (>15%)61 Tree cover, broadleaved, deciduous, closed (>40%)62 Tree cover, broadleaved, deciduous, open (15-40%)70 Tree cover, needleleaved, evergreen, closed to open (>15%)71 Tree cover, needleleaved, evergreen, closed (>40%)72 Tree cover, needleleaved, evergreen, open (15-40%)80 Tree cover, needleleaved, deciduous, closed to open (>15%)81 Tree cover, needleleaved, deciduous, closed (>40%)82 Tree cover, needleleaved, deciduous, open (15-40%)90 Tree cover, mixed leaf type (broadleaved and needleleaved)100 Mosaic tree and shrub (>50%) / herbaceous cover (<50%)110 Mosaic herbaceous cover (>50%) / tree and shrub (<50%)120 Shrubland121 Shrubland evergreen122 Shrubland deciduous130 Grassland140 Lichens and mosses150 Sparse vegetation (tree, shrub, herbaceous cover) (<15%)151 Sparse tree (<15%)152 Sparse shrub (<15%)153 Sparse herbaceous cover (<15%)160 Tree cover, flooded, fresh or brakish water170 Tree cover, flooded, saline water180 Shrub or herbaceous cover, flooded, fresh/saline/brakish water190 Urban areas200 Bare areas201 Consolidated bare areas202 Unconsolidated bare areas210 Water bodies

This eelgrass layer includes the maximum extent of eelgrass beds that have been surveyed in the San Francisco Bay shown in green. It was created by merging the Bay-wide eelgrass surveys conducted by Merkel & Associates, Inc. (Merkel) in 2003, 2009, 2014, and a Richardson Bay survey conducted by Merkel in 2019. Merkel has granted permission for public use of these data. These eelgrass surveys represent the best available data on comprehensive eelgrass extent throughout San Francisco Bay in 2021 and are developed using a combination of acoustic and aerial surveys and site-specific ground truthing. This layer may be used as a reference to determine potential direct and indirect impacts to eelgrass habitat from dredging projects. These data do not replace the need for site-specific eelgrass surveys.Data from the 2003, 2009, and 2014 eelgrass surveys and associated Merkel reports which include information on mapping methodology are available for download on the San Francisco Estuary Institute’s (SFEI) website. Methods for creating this layer are as follows:Downloaded the Merkel Baywide Eelgrass Surveys for 2003, 2009, and 2014 from SFEI and combined into a single layer. Obtained original Richardson Bay 2019 eelgrass survey data from Merkel. Loaded all layers into ArcGIS Pro © ESRI and re-projected all data to the NAD 1983 UTM Zone 10N coordinate system. Ran union of both the SFEI and Richardson Bay 2019 layers. Merged features to create one single attribute table for eelgrass cover from all survey years. Removed extraneous columns in the attribute table, recalculated area fields based on new extent, and applied symbology.

FEMA provides access to the National Flood Hazards Layer (NFHL) through web mapping services. The maps depict effective flood hazard information and supporting data. The primary flood hazard classification is indicated in the Flood Hazard Zones layer.The NFHL layers include:Flood hazard zones and labelsRiver Miles MarkersCross-sections and coastal transects and their labelsLetter of Map Revision (LOMR) boundaries and case numbersFlood Insurance Rate Map (FIRM) boundaries, labels and effective datesCoastal Barrier Resources System (CBRS) and Otherwise Protected Area (OPA) unitsCommunity boundaries and namesLeveesHydraulic and flood control structuresProfile and coastal transect baselinesLimit of Moderate Wave Action(LiMWA)Not all effective Flood Insurance Rate Maps (FIRM) have GIS data available. To view a list of available county and single-jurisdiction flood study data in GIS format and check the status of the NFHL GIS services, please visit the NFHL Status Page.Preliminary & Pending National Flood Hazard LayersThe Preliminary and Pending NFHL dataset represents the current pre-effective flood data for the country. These layers are updated as new preliminary and pending data becomes available, and data is removed from these layers as it becomes effective.For more information, please visit FEMA's website.To download map panels or GIS Data, go to: NFHL on FEMA GeoPlatform.Preliminary & Pending DataPreliminary data are for review and guidance purposes only. By viewing preliminary data and maps, the user acknowledges that the information provided is preliminary and subject to change. Preliminary data are not final and are presented in this national layer as the best information available at this time. Additionally, preliminary data cannot be used to rate flood insurance policies or enforce the Federal mandatory purchase requirement. FEMA will remove preliminary data once pending data are available.Pending data are for early awareness of upcoming changes to regulatory flood map information. Until the data becomes effective, when it will appear in FEMA's National Flood Hazard Layer (NFHL), the data should not be used to rate flood insurance policies or enforce the Federal mandatory purchase requirement. FEMA will remove pending data once effective data are available.To better understand Preliminary data please see the View Your Community's Preliminary Flood Hazard Data webpage.FEMA GeoPlatformFEMA's GIS flood map services are available through FEMAs GeoPlatform, an ArcGIS Online portal containing a variety of FEMA-related data.To view the NFHL on the FEMA GeoPlatform go to NFHL on FEMA GeoPlatform.To view the Preliminary and Pending national layers on the FEMA Geoplatform go to FEMA's Preliminary & Pending National Flood Hazard Layer.Technical InformationFlood hazard and supporting data are developed using specifications for horizontal control consistent with 1:12,000–scale mapping. If you plan to display maps from the NFHL with other map data for official purposes, ensure that the other information meets FEMA’s standards for map accuracy.The minimum horizontal positional accuracy for base map hydrographic and transportation features used with the NFHL is the NSSDA radial accuracy of 38 feet. United States Geological Survey (USGS) imagery and map services that meet this standard can be found by visiting the Knowledge Sharing Site (KSS) for Base Map Standards (420). Other base map standards can be found at https://riskmapportal.msc.fema.gov/kss/MapChanges/default.aspx. You will need a username and password to access this information.The NFHL data are from FEMA’s FIRM databases. New data are added continually. The NFHL also contains map changes to FIRM data made by LOMRs.The NFHL is stored in North American Datum of 1983, Geodetic Reference System 80 coordinate system, though many of the NFHL GIS web services support the Web Mercator Sphere projection commonly used in web mapping applications.Organization & DisplayThe NFHL is organized into many data layers. The layers display information at map scales appropriate for the data. A layer indicating the availability of NFHL data is displayed at map scales smaller than 1:250,000, regional overviews at map scales between 1:250,000 and 1:50,000, and detailed flood hazard maps at map scales of 1:50,000 and larger. The "Scalehint" item in the Capabilities file for the Web Map Service encodes the scale range for a layer.In addition, there are non-NFHL datasets provided in the GIS web services, such as information about the availability of flood data and maps, the national map panel scheme, and point locations for LOMA and LOMR-Fs. The LOMA are positioned less accurately than are the NFHL data.Layers in the public NFHL GIS services:Use the numbers shown below when referencing layers by number.0. NFHL Availability1. LOMRs2. LOMAs3. FIRM Panels4. Base Index5. PLSS6. Toplogical Low Confidence Areas7. River Mile Markers8. Datum Conversion Points9. Coastal Gages10. Gages11. Nodes12. High Water Marks13. Station Start Points14. Cross-Sections15. Coastal Transects16. Base Flood Elevations17. Profile Baselines18. Transect Baselines19. Limit of Moderate Wave Action20. Water Lines21. Coastal Barrier Resources System Area22. Political Jurisdictions23. Levees24. General Structures25. Primary Frontal Dunes26. Hydrologic Reaches27. Flood Hazard Boundaries28. Flood Hazard Zones29. Submittal Information30. Alluvial Fans31. Subbasins32. Water Areas

This layer is a subset of Global Landcover 1992- 2020 Layer. This layer is a time series of the annual ESA CCI (Climate Change Initiative) land cover maps of the world. ESA has produced land cover maps for the years 1992-2020. These are available at the European Space Agency Climate Change Initiative website.Time Extent: 1992-2020Cell Size: 300 meterSource Type: ThematicPixel Type: 8 Bit UnsignedData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: GlobalSource: ESA Climate Change InitiativeUpdate Cycle: Annual until 2020, no updates thereafterWhat can you do with this layer?This layer may be added to ArcGIS Online maps and applications and shown in a time series to watch a "time lapse" view of land cover change since 1992 for any part of the world. The same behavior exists when the layer is added to ArcGIS Pro.In addition to displaying all layers in a series, this layer may be queried so that only one year is displayed in a map. This layer can be used in analysis. For example, the layer may be added to ArcGIS Pro with a query set to display just one year. Then, an area count of land cover types may be produced for a feature dataset using the zonal statistics tool. Statistics may be compared with the statistics from other years to show a trend.To sum up area by land cover using this service, or any other analysis, be sure to use an equal area projection, such as Albers or Equal Earth.Different Classifications Available to MapFive processing templates are included in this layer. The processing templates may be used to display a smaller set of land cover classes.Cartographic Renderer (Default Template)Displays all ESA CCI land cover classes.*Forested lands TemplateThe forested lands template shows only forested lands (classes 50-90).Urban Lands TemplateThe urban lands template shows only urban areas (class 190).Converted Lands TemplateThe converted lands template shows only urban lands and lands converted to agriculture (classes 10-40 and 190).Simplified RendererDisplays the map in ten simple classes which match the ten simplified classes used in 2050 Land Cover projections from Clark University.Any of these variables can be displayed or analyzed by selecting their processing template. In ArcGIS Online, select the Image Display Options on the layer. Then pull down the list of variables from the Renderer options. Click Apply and Close. In ArcGIS Pro, go into the Layer Properties. Select Processing Templates from the left hand menu. From the Processing Template pull down menu, select the variable to display.Using TimeBy default, the map will display as a time series animation, one year per frame. A time slider will appear when you add this layer to your map. To see the most current data, move the time slider until you see the most current year.In addition to displaying the past quarter century of land cover maps as an animation, this time series can also display just one year of data by use of a definition query. For a step by step example using ArcGIS Pro on how to display just one year of this layer, as well as to compare one year to another, see the blog called Calculating Impervious Surface Change.Hierarchical ClassificationLand cover types are defined using the land cover classification (LCCS) developed by the United Nations, FAO. It is designed to be as compatible as possible with other products, namely GLCC2000, GlobCover 2005 and 2009.This is a heirarchical classification system. For example, class 60 means "closed to open" canopy broadleaved deciduous tree cover. But in some places a more specific type of broadleaved deciduous tree cover may be available. In that case, a more specific code 61 or 62 may be used which specifies "open" (61) or "closed" (62) cover.Land Cover ProcessingTo provide consistency over time, these maps are produced from baseline land cover maps, and are revised for changes each year depending on the best available satellite data from each period in time. These revisions were made from AVHRR 1km time series from 1992 to 1999, SPOT-VGT time series between 1999 and 2013, and PROBA-V data for years 2013, 2014 and 2015. When MERIS FR or PROBA-V time series are available, changes detected at 1 km are re-mapped at 300 m. The last step consists in back- and up-dating the 10-year baseline LC map to produce the 24 annual LC maps from 1992 to 2015.Source dataThe datasets behind this layer were extracted from NetCDF files and TIFF files produced by ESA. Years 1992-2015 were acquired from ESA CCI LC version 2.0.7 in TIFF format, and years 2016-2018 were acquired from version 2.1.1 in NetCDF format. These are downloadable from ESA with an account, after agreeing to their terms of use. https://maps.elie.ucl.ac.be/CCI/viewer/download.phpCitationESA. Land Cover CCI Product User Guide Version 2. Tech. Rep. (2017). Available at: maps.elie.ucl.ac.be/CCI/viewer/download/ESACCI-LC-Ph2-PUGv2_2.0.pdfMore technical documentation on the source datasets is available here:https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-land-cover?tab=doc*Index of all classes in this layer:10 Cropland, rainfed11 Herbaceous cover12 Tree or shrub cover20 Cropland, irrigated or post-flooding30 Mosaic cropland (>50%) / natural vegetation (tree, shrub, herbaceous cover) (<50%)40 Mosaic natural vegetation (tree, shrub, herbaceous cover) (>50%) / cropland (<50%)50 Tree cover, broadleaved, evergreen, closed to open (>15%)60 Tree cover, broadleaved, deciduous, closed to open (>15%)61 Tree cover, broadleaved, deciduous, closed (>40%)62 Tree cover, broadleaved, deciduous, open (15-40%)70 Tree cover, needleleaved, evergreen, closed to open (>15%)71 Tree cover, needleleaved, evergreen, closed (>40%)72 Tree cover, needleleaved, evergreen, open (15-40%)80 Tree cover, needleleaved, deciduous, closed to open (>15%)81 Tree cover, needleleaved, deciduous, closed (>40%)82 Tree cover, needleleaved, deciduous, open (15-40%)90 Tree cover, mixed leaf type (broadleaved and needleleaved)100 Mosaic tree and shrub (>50%) / herbaceous cover (<50%)110 Mosaic herbaceous cover (>50%) / tree and shrub (<50%)120 Shrubland121 Shrubland evergreen122 Shrubland deciduous130 Grassland140 Lichens and mosses150 Sparse vegetation (tree, shrub, herbaceous cover) (<15%)151 Sparse tree (<15%)152 Sparse shrub (<15%)153 Sparse herbaceous cover (<15%)160 Tree cover, flooded, fresh or brakish water170 Tree cover, flooded, saline water180 Shrub or herbaceous cover, flooded, fresh/saline/brakish water190 Urban areas200 Bare areas201 Consolidated bare areas202 Unconsolidated bare areas210 Water bodies

The National Flood Hazard Layer (NFHL) is a geospatial database that contains current effective flood hazard data. FEMA provides the flood hazard data to support the National Flood Insurance Program. You can use the information to better understand your level of flood risk and type of flooding.The NFHL is made from effective flood maps and Letters of Map Change (LOMC) delivered to communities. NFHL digital data covers over 90 percent of the U.S. population. New and revised data is being added continuously. If you need information for areas not covered by the NFHL data, there may be other FEMA products which provide coverage for those areas.In the NFHL Viewer, you can use the address search or map navigation to locate an area of interest and the NFHL Print Tool to download and print a full Flood Insurance Rate Map (FIRM) or FIRMette (a smaller, printable version of a FIRM) where modernized data exists. Technical GIS users can also utilize a series of dedicated GIS web services that allow the NFHL database to be incorporated into websites and GIS applications. For more information on available services, go to the NFHL GIS Services User Guide.You can also use the address search on the FEMA Flood Map Service Center (MSC) to view the NFHL data or download a FIRMette. Using the “Search All Products” on the MSC, you can download the NFHL data for a County or State in a GIS file format. This data can be used in most GIS applications to perform spatial analyses and for integration into custom maps and reports. To do so, you will need GIS or mapping software that can read data in shapefile format.FEMA also offers a download of a KMZ (keyhole markup file zipped) file, which overlays the data in Google Earth™. For more information on using the data in Google Earth™, please see Using the National Flood Hazard Layer Web Map Service (WMS) in Google Earth™.

This feature layer provides all OPM collected data at the tract level.------The Connecticut Broadband Availability and Adoption Maps were created to help citizens and policymakers understand the strengths and weaknesses of broadband infrastructure in the state. Data is aggregated to the block, tract, and town (county subdivision) levels and includes counts of locations classified as unserved, underserved, and served as well as whether they meet the state goal of 1000Mbps/100Mbps. This application splits its visualizations into block, tract, and town layers for both unserved locations and progress to the state goal.

This map uses OPM collected availability and adoption data.

As of 2023, OPM collected availability data was submitted by internet service providers pursuant to PA 21-159 and processed by the GIS Office in the Office of Policy and Management, cleaned, and matched to the CostQuest location fabric.

Metadata:

All feature layers, maps, and datasets including OPM's internal broadband availability data follows the same basic schema with additional fields added in some case for convenience.

Fields named no service, unserved, underserved, served, and GigC are counts of locations where a particular level of broadband service is provided, No service locations are those where there is no reported service at all. Unserved locations are locations where there is a provider offering wireline service, but not at or above 25 Mbps download and 3 Mbps upload. Underserved locations are locations where at least one provider offers wireline service of 25 Mbps download and 3 Mbps upload, but there is no provider offering wireline service of 100 Mbps download and 20 Mbps upload. Served locations are locations where there is wireline service of at least 100 Mbps download and 20 Mbps upload. GigC denotes the count of locations that have service at 1000 Mbps download and 100 Mbps upload. Accordingly, total locations is equal to the sum of no service, unserved, underserved, served, and "GigC" locations. Availability also includes fields for average download and upload speeds. These are calculated at the relevant level of census geography based on the maximum for all locations.

The final field included in all availability data is the provider list.

OPM collected adoption data:

OPM collected adoption data uses many of the same naming conventions as the availability data, but there are some notable differences.

Fields named unserved_Sub, underserved_Sub, served_Sub, and GigC _Sub are counts of subscriptions where a particular level of broadband service is currently subscribed to, Unserved subscriptions are subscriptions that do not meet the standard of 25 Mbps download and 3 Mbps upload. Underserved subscriptions are subscriptions with speeds of 25 Mbps download and 3 Mbps upload, but not meeting 100 Mbps download and 20 Mbps upload. Served subscriptions are subscriptions where speeds are between 100 Mbps download and 20 Mbps upload and 1000 Mbps download and 100 Mbps upload. GigC denotes the count of locations that have a subscription at 1000 Mbps download and 100 Mbps upload or higher. For subscription data these locations are NOT included in the "served" field as this does not directly apply to FCC use of the terms.

Please note that, due to the large size, the Informational Freshwater Wetland Mapping layer cannot be download in shapefile format.The Informational Freshwater Wetland Mapping layer is only intended to be used for informational purposes in identifying the general location and extent of freshwater wetland areas of any size throughout the state. Informational Freshwater Wetland Mapping is not regulatory.The Freshwater Wetlands Act changed in 2022 such that wetlands greater than 12.4 acres in size are regulated regardless of their mapping status. In addition to larger wetlands, the Freshwater Wetlands Act regulates smaller wetlands of “unusual importance” if they meet one of eleven criteria described in the law and regulation. While maps contained on the Environmental Resource Mapper provide information on the potential locations of wetlands, the only definitive way to determine if a particular parcel or property contains regulated wetlands outside the Adirondack Park is to request a jurisdictional determination through DEC’s website (https://dec.ny.gov/nature/waterbodies/wetlands/freshwater-wetlands-program).The Freshwater Wetlands Act regulates most development activities located in the wetland or within a regulated “adjacent area.” This adjacent area is a minimum of 100 feet but may be extended for a limited number of particularly sensitive wetlands. Not all activities in and near wetlands are regulated. There are many exempt activities that landowners may undertake without permits. However, if you are not sure of which activities require permits near New York State regulated wetlands, please contact your regional DEC office.Wetlands are classified from Class I (which provide the most benefits) to Class IV (which provide fewer benefits). The classification is based on the work that wetlands do, such as storing flood water and providing wildlife habitat. The system for classifying wetlands is contained in regulation (6 NYCRR Part 664) and the classification of individual wetlands is determined as part of the jurisdictional determination process.For additional information on NYS Freshwater Wetlands, see DEC"s website (https://dec.ny.gov/nature/waterbodies/wetlands/freshwater-wetlands-program).For information on wetlands inside the Adirondack Park, please contact the Adirondack Park Agency.For information on wetlands regulated under federal law, please contact the United State Army Corps of Engineers.Contact for this DataDFW, Bureau of Ecosystem Health625 BroadwayAlbany, NY 12233Phone: 518-402-8920fw.ecohealth@dec.ny.gov

The USGS National Hydrography Dataset (NHD) Downloadable Data Collection from The National Map (TNM) is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. For additional information on NHD, go to https://www.usgs.gov/core-science-systems/ngp/national-hydrography.

DWR was the steward for NHD and Watershed Boundary Dataset (WBD) in California. We worked with other organizations to edit and improve NHD and WBD, using the business rules for California. California's NHD improvements were sent to USGS for incorporation into the national database. The most up-to-date products are accessible from the USGS website. Please note that the California portion of the National Hydrography Dataset is appropriate for use at the 1:24,000 scale.

For additional derivative products and resources, including the major features in geopackage format, please go to this page: https://data.cnra.ca.gov/dataset/nhd-major-features Archives of previous statewide extracts of the NHD going back to 2018 may be found at https://data.cnra.ca.gov/dataset/nhd-archive.

In September 2022, USGS officially notified DWR that the NHD would become static as USGS resources will be devoted to the transition to the new 3D Hydrography Program (3DHP). 3DHP will consist of LiDAR-derived hydrography at a higher resolution than NHD. Upon completion, 3DHP data will be easier to maintain, based on a modern data model and architecture, and better meet the requirements of users that were documented in the Hydrography Requirements and Benefits Study (2016). The initial releases of 3DHP will be the NHD data cross-walked into the 3DHP data model. It will take several years for the 3DHP to be built out for California. Please refer to the resources on this page for more information.

The FINAL,STATIC version of the National Hydrography Dataset for California was published for download by USGS on December 27, 2023. This dataset can no longer be edited by the state stewards.

The first public release of the 3D Hydrography Program map service may be accessed at https://hydro.nationalmap.gov/arcgis/rest/services/3DHP_all/MapServer.

Questions about the California stewardship of these datasets may be directed to nhd_stewardship@water.ca.gov.

This feature layer includes all data available at the block level - no adoption data is available at this level.-------The Connecticut Broadband Availability and Adoption Maps were created to help citizens and policymakers understand the strengths and weaknesses of broadband infrastructure in the state. Data is aggregated to the block, tract, and town (county subdivision) levels and includes counts of locations classified as unserved, underserved, and served as well as whether they meet the state goal of 1000Mbps/100Mbps. This application splits its visualizations into block, tract, and town layers for both unserved locations and progress to the state goal.

This map uses OPM collected availability and adoption data.

As of 2023, OPM collected availability data was submitted by internet service providers pursuant to PA 21-159 and processed by the GIS Office in the Office of Policy and Management, cleaned, and matched to the CostQuest location fabric.

Metadata:

All feature layers, maps, and datasets including OPM's internal broadband availability data follows the same basic schema with additional fields added in some case for convenience.

Fields named no service, unserved, underserved, served, and GigC are counts of locations where a particular level of broadband service is provided, No service locations are those where there is no reported service at all. Unserved locations are locations where there is a provider offering wireline service, but not at or above 25 Mbps download and 3 Mbps upload. Underserved locations are locations where at least one provider offers wireline service of 25 Mbps download and 3 Mbps upload, but there is no provider offering wireline service of 100 Mbps download and 20 Mbps upload. Served locations are locations where there is wireline service of at least 100 Mbps download and 20 Mbps upload. GigC denotes the count of locations that have service at 1000 Mbps download and 100 Mbps upload. Accordingly, total locations is equal to the sum of no service, unserved, underserved, served, and "GigC" locations. Availability also includes fields for average download and upload speeds. These are calculated at the relevant level of census geography based on the maximum for all locations.

The final field included in all availability data is the provider list.

OPM collected adoption data:

OPM collected adoption data uses many of the same naming conventions as the availability data, but there are some notable differences.

Fields named unserved_Sub, underserved_Sub, served_Sub, and GigC _Sub are counts of subscriptions where a particular level of broadband service is currently subscribed to, Unserved subscriptions are subscriptions that do not meet the standard of 25 Mbps download and 3 Mbps upload. Underserved subscriptions are subscriptions with speeds of 25 Mbps download and 3 Mbps upload, but not meeting 100 Mbps download and 20 Mbps upload. Served subscriptions are subscriptions where speeds are between 100 Mbps download and 20 Mbps upload and 1000 Mbps download and 100 Mbps upload. GigC denotes the count of locations that have a subscription at 1000 Mbps download and 100 Mbps upload or higher. For subscription data these locations are NOT included in the "served" field as this does not directly apply to FCC use of the terms.

Public view of the parcel layer. This view is limited to only the attributes that can be seen by the general public.The data table includes the following fields: Shape Type (Shape), Shape.STArea() (Shape_Area), Shape.STLength() (Shape_Area), Name (APN), Created By Record (CreatedbyR), Retired By Record (RetiredbyR), Stated Area, Stated Area Unit (StatedAr_1), Calculated Area (Calculated), Misclose Ratio (MiscloseRa), Misclose Distance (MiscloseDi), Is Seed (IsSeed), Created By (created_us), Created Date (created_da), Modified By (last_edite), Modified Date (last_edi_1), Validation Status (VALIDATION), APN Dashed (APN_Dashed), Map Page (Map_Page), Municipality (Municipali), FloorOrder, HideThere are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.

The Digital Geologic-GIS Map of Gettysburg National Military Park, Pennsylvania is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (gett_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (gett_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (gett_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (gett_eise_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (gett_eise_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (gett_geology_metadata_faq.pdf). Please read the gett_eise_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (gett_geology_metadata.txt or gett_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The Digital Geologic-GIS Map of the Yellowstone National Park and Vicinity, Wyoming, Montana and Idaho is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (yell_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (yell_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (yell_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (yell_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (yell_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (yell_geology_metadata_faq.pdf). Please read the yell_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and Montana Bureau of Mines and Geology. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (yell_geology_metadata.txt or yell_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 63.5 meters or 208.3 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Data obtained from Greg's Cable Map and available for use under GNU GENERAL PUBLIC LICENSE. For more information see Greg's Cable Map website.

This hosted feature layer has been published in RI State Plane Feet NAD 83.Statewide flood hazard areas compiled from county-based Digital Flood Insurance Rate Map (DFIRM) databases for Rhode Island. The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. TheDFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA), and in this case redistributed by the Rhode Island Geographic Information System (RIGIS) at the request of the Rhode Island Emergency Management Agency.This dataset provides the user with information on the flood risk hazard zones throughout the state of Rhode Island. Note: the above summary is a slightly modified version adapted from source metadata records provided by FEMA. To provide the user with information on the statewide flood risk based on information provided by the Federal Emergency Management Agency (FEMA) in the DFIRM databases created specifically for the five counties of Rhode Island (Bristol, Kent, Newport, Providence, and Washington). This dataset provides information on the likelihood that a flood may occur at a given location in the state. The files and information used to create this dataset were originally provided to the Rhode Island Emergency Management Agency (RIEMA) by FEMA.This information was in the form of DFIRM databases for each of the five RI counties. This information was then redistributed by RIGIS at the request of RIEMA. The information provided by this data is only a subset of the information available in the original DFIRM databases located on the RIGIS website. For a specific county's complete DFIRM database, please visit the RIGIS website and download the appropriate DFIRM database. This metadata record is specific to this dataset and only contains information relevant to this dataset as provided by FEMA the original DFIRM metadata records. These can be found and referenced in the /DOCUMENT folder that is downloaded as part of a DFIRM package for a specific Rhode Island county. Another valuable source of documentation is FEMA's "Guidelines and Specifications for Flood Hazard Mapping Partners". It is currently available online at https://www.fema.gov/guidelines-and-standards-flood-risk-analysis-and-mapping. The Guide offers a tremendous amount of information regarding how DFIRM data are created, and detailed information about the individual files that constitute a DFIRM database.