Rockfish Conservation Areas (RCAs) are closed areas for west coast groundfish fisheries and for some fisheries that may incidentally take groundfish as bycatch. The RCA boundary line is a connection of a series of GPS coordinates published in federal regulations (See 50 CFR 660.71-660.74) that are intended to approximate underwater depth contours. RCA boundaries are used in groundfish regulations to avoid interactions with certain groundfish species of concern and may change between seasons and Recreational Fishing Management Areas. The process of digitizing these boundary lines is as follows: 30, 40, 50, 100, and 150fm waypoint .csv files were downloaded from NOAA’s West Coast Groundfish Closed Areas website https://res1wwwd-o-tfisheriesd-o-tnoaad-o-tgov.vcapture.xyz/west-coast/sustainable-fisheries/west-coast-groundfish-closed-areas and imported into ArcGIS Pro. Each point feature was clipped to ocean waters offshore of California and merged together. “Fathom” was added as a field to each shapefile and populated with the corresponding depth in fathoms. Boundary lines for each shapefile (30, 40, 50, 100, and 150 fm) were created using the “Points to line” tool. Line Field: “area_name”. Attribute Source: Start Point. Transfer Fields: FID, area_name, Fathom. Attributes: area_name: Unique name field displaying depth and location. Fathom: Approximate depth in fathoms of contour line. Region: Describes which of the five groundfish management zones the section of the contour line is in.

Download In State Plane Projection Here The 2024 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2024 Tax Year.This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcGIS Pro (specifically the Parcel Fabric), and those with access to ArcGIS Pro, which is necessary to view or manipulate the data.Casual users can find the standalone Tax Parcel Boundary Data here and Parcel Attribute Data here. Update Frequency: This dataset is updated on a yearly basis.

Abstract Landslides are damaging and deadly, and they occur in every U.S. state. However, our current ability to understand landslide hazards at the national scale is limited, in part because spatial data on landslide occurrence across the U.S. varies greatly in quality, accessibility, and extent. Landslide inventories are typically collected and maintained by different agencies and institutions, usually within specific jurisdictional boundaries, and often with varied objectives and information attributes or even in disparate formats. The purpose of this data release is to provide an openly accessible, centralized map of existing information about landslide occurrence across the entire U.S. This data release is an update of previous versions 1 (Jones and others, 2019) and 2 (Belair and others, 2022). Changes relative to version 2 are summarized in us_ls_v3_changes.txt. It provides an integrated database of the landslides from these inventories (refer to US_Landslide_v3_gpkg) with a selection of uniform attributes, including links to the original digital inventory files (whenever available) (“Inv_URL”). The data release includes digital inventories created by both USGS and non-USGS authors. The original inventory is denoted by an abbreviation in the “Inventory” attribute. The full citation for each abbreviation can be found in us_ls_v3_references.csv. The date of the landslide event is included as a minimum and maximum (“Date_Min” and “Date_Max”) to accommodate events that happen within a range of dates. The date value is inherently difficult to interpret or discern due to the nature of landsliding, where some landslides move for long periods of time or move intermittently, and some areas can exhibit multiple landslide events. To preserve the constituent inventories as much as possible, we include all entries even if they are not considered landslides, such as “gullies” or “avalanche chutes.” We include a landslide type attribute when that information is available (“LS_Type”). The landslide classification system used in the original inventories is not always known or stated in the metadata, but many mapping entities use the schema from Cruden and Varnes (1996) or the updated schema from Hungr and others (2014). Given the wide range of landslide information sources in this data compilation, we provide an attribute to assess the relative confidence in the characterization of the _location and extent of each landslide (entry) (“Confidence”). The confidence level reflects the resolution and quality of input data, as well as the method used for identification and mapping. This confidence does not reflect a formal accuracy assessment of field attributes. Relative to the previous data releases (version 1 and 2), this update (v3) includes more inventories, updated confidence rules, a new landslide type attribute, a new unique identifier (“USGS_ID”), new machine-readable date fields, and an ancillary database containing all fields from the original inventories (refer to US_Landslide_v3_ancillary). Please contact gs-haz_landslides_inventory@usgs.gov for more information on how to contribute additional inventories to this community effort. When possible, please cite the constituent inventories as well as this data release. This data release includes: (1) a landslide point file and polygon file in multiple forms (US_Landslide_v3_gpkg, US_Landslide_v3_shp, US_Landslide_v3_csv), (2) an ancillary database with original fields (US_Landslide_v3_ancillary), (3) a spreadsheet that summarizes the confidence rules, their justification, and any extra analyses (us_ls_v3_analyses.csv), (4) a summary file of the changes made between version 2 and version 3 (us_ls_v3_changes.txt), (5) a file containing the references of the constituent inventories (us_ls_v3_references.csv), (6) and a readme (README.txt). Disclaimer: Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Data fields Field Names Definitions USGS_ID Unique USGS identifier for each landslide entry. Date_Min Minimum possible date of landslide occurrence. If date is known to the day, Date_Min will have a value while Date_Max is empty. Time zone is assumed to be local, except for Inventories ‘USGS Earthquake-Triggered Ground Failure’ and ‘USGS Seismogenic Mass Movements’ which are in UTC. Date_Max Maximum possible date of landslide occurrence. If date is known to the day, Date_Max will be empty while Date_Min has a value. Time zone is assumed to be local, except for Inventories ‘USGS Earthquake-Triggered Ground Failure’ and ‘USGS Seismogenic Mass Movements’ which are in UTC. Fatalities Number of fatalities caused by landslide event. Confidence Confidence in landslide (entry) extent, nature, and _location. LS_Type Landslide (entry) type. Classification schema of original inventories is often not specified. Inventory Name of original source inventory. Inv_URL URL or link to original source inventory. Info_Source Information source or sub-layer from original source inventory. Notes Unformatted notes field, includes additional information. Lat_N Latitude of point or polygon centroid in WGS 1984 Lon_W Longitude of point or polygon centroid in WGS 1984 Confidence attributes Confidence Definitions 1 Possible landslide (feature) in the area 2 Probable landslide (feature) in the area 3 Likely landslide (feature) at or near this _location 5 Moderate confidence in extent or nature of landslide (feature) at this _location 8 High confidence in extent or nature of landslide (feature) References Belair, G.M., Jones, E.S., Slaughter, S.L., and Mirus, B.B., 2022, Landslide Inventories across the United States version 2: U.S. Geological Survey data release, https://doi.org/10.5066/P9FZUX6N. Cruden, D.M. and Varnes, D.J., 1996, Landslide Types and Processes, in Turner, K.A. and Schuster R. L., eds., Landslides Investigation and Mitigation: Transportation Research Board, U.S. National Research Council Special Report 247, U.S. National Academy of Sciences, Chapter 3, p. 36-75. ESRI, 2023, ArcGIS Pro (Version 3.1.3), Redlands, CA: Environmental Systems Research Institute, Retrieved from https://www.esri.com/en-us/arcgis/products/arcgis-pro/resources. Hungr, O., Leroueil, S., and Picarelli, L., 2014, The Varnes classification of landslide types, an update, Landslides, 11(2), p. 167-194, https://doi.org/10.1007/s10346-013-0436-y. Jones, E.S., Mirus, B.B, Schmitt, R.G., Baum, R.L., Burns, W.J., Crawford, M., Godt, J.W., Kirschbaum, D.B., Lancaster, J.T., Lindsey, K.O., McCoy, K.E., Slaughter, S., and Stanley, T.A., 2019, Landslide Inventories across the United States: U.S. Geological Survey data release, https://doi.org/10.5066/P9E2A37P. Python Software Foundation, 2023, Python Language Reference, version 3.9, Retrieved from http://www.python.org. QGIS.org, 2022, QGIS Geographic Information System (Version 3.28.4-Firenze), QGIS Association, Retrieved from http://www.qgis.org.

Do not share this map Publicly!This template is for ACTIVE INCIDENTS only. For training, please use the Training template (found here). This workflow uses one template web map and contains all layers of the National Incident Feature Service in a single service (Unlike the standard template which splits features into Edit, View, and Repair services). It is for teams looking for a simple approach to ArcGIS Online implementation. All features are visible; editing is enabled for points, lines, and polygons and disabled for the IR layers [Workflow LINK]; contains the National Incident Feature Service layers: NWCG approved Event schema.This template web map is provided for quick deployment. Listed next are the steps to implement this Standard Workflow:1) Open this web map template in Map Viewer2) Do a Save As (Click Save and select Save As)3) Zoom to your fire area and add bookmarks4) Look for a red triangle polygon with your fire's attributes - do either of these: a. Use this polygon as a start for your incident and modify as needed b. Copy the attributes (most importantly, the IRWIN ID) into a new polygon and delete the triangle (delete in ArcMap or Pro)5) Create a display filter on features to only show features related to your incident (Optional).6) Create a new Photo Point Layer (Content > Create > Feature Layer > From Existing > #TEMPLATE - PhotoPoint). Add this to your web map and remove default PhotoPoint Layer7) Share with your Mobile Editing group8) Add necessary incident personnel to the Mobile Editing group9) Make available for Viewers:a. Save out a second version of this map and disable editing on all the layers except Photo Points.b. Share this version with the Viewing group.10) To track and manage suppression repair needs use the Suppression Repair Add-on

The 2023 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2023 Tax Year.This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcGIS Pro (specifically the Parcel Fabric), and those with access to ArcGIS Pro, which is necessary to view or manipulate the data.Casual users can find the standalone Tax Parcel Boundary Data here and Parcel Attribute Data here. Update Frequency: This dataset is updated on a yearly basis.

Reason for SelectionProtected natural areas in urban environments provide urban residents a nearby place to connect with nature and offer refugia for some species. Because beaches in Puerto Rico and the U.S. Virgin Islands are open to the public, beaches also provide important outdoor recreation opportunities for urban residents, so we include beaches as parks in this indicator.Input DataSoutheast Blueprint 2023 subregions: CaribbeanSoutheast Blueprint 2023 extentNational Oceanic and Atmospheric Administration (NOAA) National Centers for Environmental Information (NCEI) Coastal Relief Model, accessed 11-22-2022Protected Areas Database of the United States (PAD-US) 3.0: VI, PR, and Marine Combined Fee EasementPuerto Rico Protected Natural Areas 2018 (December 2018 update): Terrestrial and marine protected areas (PACAT2018_areas_protegidasPR_TERRESTRES_07052019.shp, PACAT2018_areas_protegidasPR_MARINAS_07052019.shp) 2020 Census Urban Areas from the Census Bureau’s urban-rural classification; download the data, read more about how urban areas were redefined following the 2020 censusOpenStreetMap data “multipolygons” layer, accessed 3-14-2023A polygon from this dataset is considered a park if the “leisure” tag attribute is either “park” or “nature_reserve”, and considered a beach if the value in the “natural” tag attribute is “beach”. OpenStreetMap describes leisure areas as “places people go in their spare time” and natural areas as “a wide variety of physical geography, geological and landcover features”. Data were downloaded in .pbf format and translated ton an ESRI shapefile using R code. OpenStreetMap® is open data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF). Additional credit to OSM contributors. Read more on the OSM copyright page. TNC Lands - Public Layer, accessed 3-8-2023U.S. Virgin Islands beaches layer (separate vector layers for St. Croix, St. Thomas, and St. John) provided by Joe Dwyer with Lynker/the NOAA Caribbean Climate Adaptation Program on 3-3-2023 (contact jdwyer@lynker.com for more information)Mapping StepsMost mapping steps were completed using QGIS (v 3.22) Graphical Modeler.Fix geometry errors in the PAD-US PR data using Fix Geometry. This must be done before any analysis is possible.Merge the terrestrial PR and VI PAD-US layers.Use the NOAA coastal relief model to restrict marine parks (marine polygons from PAD-US and Puerto Rico Protected Natural Areas) to areas shallower than 10 m in depth. The deep offshore areas of marine parks do not meet the intent of this indicator to capture nearby opportunities for urban residents to connect with nature.Merge into one layer the resulting shallow marine parks from marine PAD-US and the Puerto Rico Protected Natural Areas along with the combined terrestrial PAD-US parks, OpenStreetMap, TNC Lands, and USVI beaches. Omit from the Puerto Rico Protected Areas layer the “Zona de Conservación del Carso”, which has some policy protections and conservation incentives but is not formally protected.Fix geometry errors in the resulting merged layer using Fix Geometry.Intersect the resulting fixed file with the Caribbean Blueprint subregion.Process all multipart polygons to single parts (referred to in Arc software as an “explode”). This helps the indicator capture, as much as possible, the discrete units of a protected area that serve urban residents.Clip the Census urban area to the Caribbean Blueprint subregion.Select all polygons that intersect the Census urban extent within 1.2 miles (1,931 m). The 1.2 mi threshold is consistent with the average walking trip on a summer day (U.S. DOT 2002) used to define the walking distance threshold used in the greenways and trails indicator. Note: this is further than the 0.5 mi distance used in the continental version of the indicator. We extended it to capture East Bay and Point Udall based on feedback from the local conservation community about the importance of the park for outdoor recreation.Dissolve all the park polygons that were selected in the previous step.Process all multipart polygons to single parts (“explode”) again.Add a unique ID to the selected parks. This value will be used to join the parks to their buffers.Create a 1.2 mi (1,931 m) buffer ring around each park using the multiring buffer plugin in QGIS. Ensure that “dissolve buffers” is disabled so that a single 1.2 mi buffer is created for each park.Assess the amount of overlap between the buffered park and the Census urban area using overlap analysis. This step is necessary to identify parks that do not intersect the urban area, but which lie within an urban matrix. This step creates a table that is joined back to the park polygons using the UniqueID.Remove parks that had ≤2% overlap with the urban areas when buffered. This excludes mostly non-urban parks that do not meet the intent of this indicator to capture parks that provide nearby access for urban residents. Note: In the continental version of this indicator, we used a threshold of 10%. In the Caribbean version, we lowered this to 2% in order to capture small parks that dropped out of the indicator when we extended the buffer distance to 1.2 miles.Calculate the GIS acres of each remaining park unit using the Add Geometry Attributes function.Join the buffer attribute table to the previously selected parks, retaining only the parks that exceeded the 2% urban area overlap threshold while buffered. Buffer the selected parks by 15 m. Buffering prevents very small parks and narrow beaches from being left out of the indicator when the polygons are converted to raster.Reclassify the polygons into 7 classes, seen in the final indicator values below. These thresholds were informed by park classification guidelines from the National Recreation and Park Association, which classify neighborhood parks as 5-10 acres, community parks as 30-50 acres, and large urban parks as optimally 75+ acres (Mertes and Hall 1995).Export the final vector file to a shapefile and import to ArcGIS Pro.Convert the resulting polygons to raster using the ArcPy Polygon to Raster function. Assign values to the pixels in the resulting raster based on the polygon class sizes of the contiguous park areas.Clip to the Caribbean Blueprint 2023 subregion.As a final step, clip to the spatial extent of Southeast Blueprint 2023. Note: For more details on the mapping steps, code used to create this layer is available in the Southeast Blueprint Data Download under > 6_Code. Final indicator valuesIndicator values are assigned as follows:6 = 75+ acre urban park5 = >50 to <75 acre urban park4 = 30 to <50 acre urban park3 = 10 to <30 acre urban park2 = 5 to <10 acre urban park1 = <5 acre urban park0 = Not identified as an urban parkKnown IssuesThis indicator does not include park amenities that influence how well the park serves people and should not be the only tool used for parks and recreation planning. Park standards should be determined at a local level to account for various community issues, values, needs, and available resources. This indicator includes some protected areas that are not open to the public and not typically thought of as “parks”, like mitigation lands, private easements, and private golf courses. While we experimented with excluding them using the public access attribute in PAD, due to numerous inaccuracies, this inadvertently removed protected lands that are known to be publicly accessible. As a result, we erred on the side of including the non-publicly accessible lands.This indicator includes parks and beaches from OpenStreetMap, which is a crowdsourced dataset. While members of the OpenStreetMap community often verify map features to check for accuracy and completeness, there is the potential for spatial errors (e.g., misrepresenting the boundary of a park) or incorrect tags (e.g., labelling an area as a park that is not actually a park). However, using a crowdsourced dataset gives on-the-ground experts, Blueprint users, and community members the power to fix errors and add new parks to improve the accuracy and coverage of this indicator in the future.Other Things to Keep in MindThis indicator calculates the area of each park using the park polygons from the source data. However, simply converting those park polygons to raster results in some small parks and narrow beaches being left out of the indicator. To capture those areas, we buffered parks and beaches by 15 m and applied the original area calculation to the larger buffered polygon, so as not to inflate the area by including the buffer. As a result, when the buffered polygons are rasterized, the final indicator has some areas of adjacent pixels that receive different scores. While these pixels may appear to be part of one contiguous park or suite of parks, they are scored differently because the park polygons themselves are not actually contiguous. The Caribbean version of this indicator uses a slightly different methodology than the continental Southeast version. It includes parks within a 1.2 mi distance from the Census urban area, compared to 0.5 mi in the continental Southeast. We extended it to capture East Bay and Point Udall based on feedback from the local conservation community about the importance of the park for outdoor recreation. Similarly, this indicator uses a 2% threshold of overlap between buffered parks and the Census urban areas, compared to a 10% threshold in the continental Southeast. This helped capture small parks that dropped out of the indicator when we extended the buffer distance to 1.2 miles. Finally, the Caribbean version does not use the impervious surface cutoff applied in the continental Southeast because the landcover data available in the Caribbean does not assess percent impervious in a comparable way.Disclaimer: Comparing with Older Indicator VersionsThere are numerous problems with using Southeast Blueprint