This ArcGIS Online hosted feature service displays perimeters from the National Incident Feature Service (NIFS) that meet ALL of the following criteria:

Author: Titus, Maxwell (mtitus@esri.com)Last Updated: 3/4/2025Intended Environment: ArcGIS ProPurpose: This Notebook was designed to automate updates for Hosted Feature Services hosted in ArcGIS Online (or ArcGIS Portal) from ArcGIS Pro and a spatial join of two live datasets.Description: This Notebook was designed to automate updates for Hosted Feature Services hosted in ArcGIS Online (or ArcGIS Portal) from ArcGIS Pro. An associated ArcGIS Dashboard would then reflect these updates. Specifically, this Notebook would:First, pull two datasets - National Weather Updates and Public Schools - from the Living Atlas and add them to an ArcGIS Pro map.Then, the Notebook would perform a spatial join on two layers to give Public Schools features information on whether they fell within an ongoing weather event or alert. Next, the Notebook would truncate the Hosted Feature Service in ArcGIS Online - that is, delete all the data - and then append the new data to the Hosted Feature ServiceAssociated Resources: This Notebook was used as part of the demo for FedGIS 2025. Below are the associated resources:Living Atlas Layer: NWS National Weather Events and AlertsLiving Atlas Layer: U.S. Public SchoolsArcGIS Demo Dashboard: Demo Impacted Schools Weather DashboardUpdatable Hosted Feature Service: HIFLD Public Schools with Event DataNotebook Requirements: This Notebook has the following requirements:This notebook requires ArcPy and is meant for use in ArcGIS Pro. However, it could be adjusted to work with Notebooks in ArcGIS Online or ArcGIS Portal with the advanced runtime.If running from ArcGIS Pro, connect ArcGIS Pro to the ArcGIS Online or ArcGIS Portal environment.Lastly, the user should have editable access to the hosted feature service to update.

MRGP NewsIf you already have an ArcGIS named user, join the MRGP Group. Doing so allows you complete the permit requirements under your organization's umbrella. As a group member you get access to the all the MRGP items without having to log-in and log-out. If you don’t have an ArcGIS member account please contact Chad McGann (MRGP Program Lead) at 802-636-7239 or your Regional Planning Commission’s Transportation Planner. April 9, 2025. Conditional logic in webform for the newly published Open Drainage Survey was not calculating properly leading to some records with "Undetermined" status and priority. Records have been rescored and survey was republished with corrective logic. Field App version not impacted.March 11, 2025. The Road Erosion Inventory Survey123 questions for Open Drainage Roads are being streamlined to make assessments faster. Coming April 1st, the survey will be changed to only ask if there is erosion depending on if the corresponding practice type is failing. This aims at using erosion as an indicator to measure the success of each of the four Open Drainage road elements to handle stormwater: crown, berm, drainage, turnout.March 29, 2023. For MRGP permitting, Lyndonville Village (GEOID 5041950) has merged with Lyndonville Town (GEOID 5000541725). 121 segments and 14 outlets have been updated to reflect the administrative change. December 8, 2023. The Open Drainage Road Inventory survey has been updated for the 2024 field season. We added and modified a few notes for clarification and corrected an issue with users submitting incomplete surveys. See FAQ section below for how to delete the old survey and download the new one. The app will notify you there's an update, and execute it, but we've experienced select-one questions with duplicate entries.November 29, 2023. The Closed Drainage Road Inventory survey has been updated for the 2024 field season. There's a new outlet status option called "Not accessible" and conditional follow-up question. This has been added to support MS4 requirements. See FAQ section below for how to delete the old survey and download the new one. The app will notify you there's an update and execute it for you but we've experienced select-one questions with duplicate entries. Reporter for MRGPThe Reporter for MRGP doesn't require you to download any apps to complete an inventory; all you need is an internet connection and web browser. The Reporter includes culverts and bridges from VTCULVERTS, town highways from Vtrans, current status for MRGP segments and outlets and second cycle progress. The Reporter is a great way to submit work completed to meet the MRGP standards. MRGP Fieldworker SolutionStep 1: Download the free mobile appsFor fieldworkers to collect and submit data to VT DEC, two free apps are required: ArcGIS Field Maps and Survey123. ArcGIS Field Maps is used first to locate the segment or outlet for inventory, and Survey123, for completing the Road Erosion Inventory.• You can download ArcGIS Fields Maps and Survey123 from the Google Play Store.• You can download ArcGIS Field Maps and Survey123 from Apple Store.Step 2: Sign into the mobile appYou will need appropriate credentials to access fieldworker solution, Please contact your Regional Planning Commission’s Transportation Planner or Chad McGann (MRGP Program Lead) at 802-636-7239.Open Field Maps, select ‘ArcGIS Online’ as shown below, and enter the user name and password. The credential is saved unless you sign out. Step 3: Open the MRGP Mobile MapIf you’re working in an area that has a reliable data connection (e.g. LTE or 4G), open the map below by selecting it.Step 4: Select a road segment or outlet for inventoryUsing your location, highlighted in red below, select the segment or outlet you need to inventory, and select 'Update Road Segment Status' from the pop-up to launch Survey123.

Step 5: Complete the Road Erosion Inventory and submit inventory to DECSelecting 'Update Road Segment Status' opens Survey123, downloads the relevant survey and pre-populates the REI with important information for reporting to DEC. You will have to enter the same username and password to access the REI forms. The credential is saved unless you sign out of Survey123.Complete the survey using the appropriate supplement below and submit the assessment directly to VT DEC.Paved Roads with Catch Basin SupplementPaved and Gravel Roads with Drainage Ditches Supplement

Step 6: Repeat!Go back to the ArcGIS Field Maps and select the next segment for inventory and repeat steps 1-5.

If you have question related to inventory protocol reach out to Chad McGann, MRGP Program Lead, at chad.mcgann@vermont.gov, 802-636-7396.If you have questions about implementing the mobile data collection piece please contact Ryan Knox, ADS-ANR IT, at ryan.knox@vermont.gov, (802) 793-0297

How do I update a survey when a new one is available?While the Survey123 app will notify you and update it for you, we've experienced some select-one questions having duplicate choices. It's a best practice to delete the old survey and download the new one. See this document for step-by-step instructions.I already have an ArcGIS member account with my organization, can I use it to complete MRGP inventories?Yes! The MRGP solution is shared within an ArcGIS Group that allows outside organizations. Click "join this group" and send an request to the ANR GIS team. This will allow you complete MRGP requirements for the REI and stay logged into your organization. Win-win situation for us both!AGOL Group: https://www.arcgis.com/home/group.html?id=027e1696b97a48c4bc50cbb931de992d#overviewThe location where I'm doing inventory does not have data coverage (LTE or 4G). What can I do?ArcGIS Field Maps allows you take map areas offline when you think there will be spotty or no data coverage. I made a video to demonstrate the steps for taking map areas offline - https://youtu.be/ScpQnenDp7wSurvey123 operates offline by default but you need to download the survey. My recommendation is to test the fieldworker solution (Steps 1-5) before you go into the field but don't submit the test survey.How do remove an offline area and create a new one? Check out this how-to document for instructions. Delete and Download Offline AreaWhere can I download the Road Erosion Scoring shown on the the Atlas? You can download the scoring for both outlets and road segments through the VT Open Geodata Portal.https://geodata.vermont.gov/search?q=mrgpHow do I use my own map for launching the official MRGP REI survey form? You can use the following custom url for launching Survey123, open the REI and prepopulate answers in the form. More information is here. TIP: add what's below directly in the HTML view of the popup not the link as described in the post I provided.

Segments (lines):Update Road Segment StatusOutlets (points):Update Outlet Status

How do I save my name and organization information used in subsequent surveys? Watch this short video or execute the steps below:

Open Survey123 and open a blank REI form (Collect button) Note: it's important to open a blank form so you don't save the same segment id for all your surveys Fill-in your 'Name' and 'Organization' and clear the 'Date of Assessment field' (x button). Using the favorites menu in the top-right corner you can use the current state of your survey to 'Set as favorite answers.' Close survey and 'Save this survey in Drafts.' Use Collector to launch survey from selected feature (segment or outlet). Using the favorites menu again, 'Paste answers from favorite.

What if the map doesn't have the outlet or road segment I need to inventory for the MRGP? Go Directly to Survey123 and complete the appropriate Road Erosion Inventory and submit the data to DEC. The survey includes a Geopoint (location) that we can use to determine where you completed the inventory.

Where can I view the Road Erosion Inventories completed with Survey123? Use the web map below to view second cycle inventories completed with Survey123. The first cycle inventories can be downloaded below. First cycle inventories are those collected 2018-2022.Web map - Completed Road Erosion Inventories for MRGPWhere can I download the 2020-2022 data collected with Survey123?Road Segments (lines) - https://anrmaps.vermont.gov/websites/MRGP/MRGP2020_segments.zipOutlets (points) - https://anrmaps.vermont.gov/websites/MRGP/MRGP2020_outlets.zipWhere can I download the 2019 data collected with Survey123?

Road Segments (lines) -

Input Data

NOAA Continuously Updated Shoreline Product (CUSP), accessed 1-11-2023; read a 1-page factsheet about CUSP; view and download CUSP data in the NOAA Shoreline Data Explorer (to download, select “Download CUSP by Region” and select Southeast Caribbean)
Southeast Blueprint 2023 subregions: Caribbean

Mapping Steps

Make a copy of the Southeast Caribbean CUSP feature line dataset and reproject it to ESPG 5070.
For the big island of Puerto Rico, special steps were required to deal with CUSP shorelines that did not connect across large rivers.
  Add and calculate a field to use to dissolve the lines.
    Dissolve the lines using the dissolve function, which reveals where there are gaps in the shoreline.
    Use the integrate tool to snap together nearby nodes, using a tolerance of 8 m. This connects the disconnected lines on the big island of Puerto Rico.
    Convert these modified shorelines to a polygon.
    Add and calculate a dissolve field, then dissolve using the dissolve tool. This is necessary because interior waterbodies on the big island of Puerto Rico also have shorelines in the CUSP data. This step produces a layer where inland waterbodies are included as a part of the island where they occur.
    From the resulting layer, select the big island of Puerto Rico and create a separate polygon feature layer from it. This extracts a modified shoreline boundary for the big island of Puerto Rico only. We don’t want to use the modified shorelines created above for other islands that didn’t have an issue of disconnected shoreline segments near large rivers.

Go back to the original Caribbean CUSP lines and convert them to polygons.
Add a dissolve field and dissolve using the dissolve tool. This produces a layer where all inland waterbodies are included as a part of the island where they occur.
From the island boundaries derived from the original CUSP data, remove the polygons that overlap with the big island of Puerto Rico derived from the modified CUSP data. This produces a layer representing all U.S. Caribbean islands except the big island of Puerto Rico.
Merge the modified big island of Puerto Rico layer with the layer for all other islands.
Create and populate a field that has unique IDs for all islands.
Convert the island polygon to a raster using the ArcPy Feature to Raster function. This makes a raster that correctly represents the interior of the islands. However, because the Feature to Raster function for polygons works differently than the Line to Raster function, the shoreline doesn’t perfectly match the result we get when we convert the CUSP lines to a raster. 
Because the Caribbean coastal shoreline condition indicator is created from the CUSP lines, we need the shorelines to match exactly. To reconcile this, go back to the original Caribbean CUSP line data and use the Feature to Raster function again, this time converting the lines to a raster. 
Use the ArcPy Cell Statistics “MAXIMUM” function to combine the two rasters above (one created from the CUSP lines and one created from the CUSP-derived polygons).
Export the raster that represents the extent of Caribbean islands.
Use the Region Group function to give unique values to each island.
Reclassify to make 3 island size classes. The big island of Puerto Rico is the only island in the highest class. The medium island class contains the following islands: Isla Mona, Isla de Vieques, Isla de Culebra, St. Thomas, St. John, and St. Croix. All other islands were put in the smaller class. All other non-island pixels in the Caribbean were given a value of marine.

Note: For more details on the mapping steps, code used to create this layer is available in the Southeast Blueprint 2023 Data Download or Caribbean-only Southeast Blueprint 2023 Data Download under > 6_Code. Literature Cited National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, National Geodetic Survey. NOAA Continually Updated Shoreline Product (CUSP): Southeast Caribbean. [https://coast.noaa.gov/digitalcoast/data/cusp.html].

This data has been clipped from the USA Critical Habitat layer on ArcGIS Living Atlas of the World. It is intended for Esri tutorial purposes only and may not reflect the current state of critical habitat. Use the USA Critical Habitat layer for authoritative data.In the United States, species in danger of extinction are protected by the Endangered Species Act. As part of these protections, the US Fish and Wildlife Service can designate critical habitat. Activities that are carried out, authorized, or funded by the federal government that are likely to adversely modify or destroy critical habitat are generally prohibited by the Endangered Species Act.Because the Endangered Species Act prohibits federal actions that degrade critical habitat, limitations may be placed on land management and other projects. Proposed federal actions that may adversely modify or destroy critical habitat require that the agency or private entity proposing the action consult with the appropriate regulatory agency (US Fish and Wildlife Service or the National Oceanic and Atmospheric Administration).The consultation and permitting process often relies heavily on GIS to organize, analyze, and display key information. This layer provides the information necessary to begin a landscape assessment of the distribution of critical habitat.Dataset SummaryPhenomenon Mapped: Critical Habitat for Threatened and Endangered species. Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, the US Virgin Islands, Guam, and the Northern Mariana IslandsVisible Scale: The data is visible at all scales but draws best at scales larger than 1: 2,000,000Source: U.S. Fish and Wildlife ServicePublication Date: June 14, 2019This layer displays critical habitat data (June 14, 2019) from the U.S. Fish and Wildlife Service (USFWS). The service contains 2 layers, lines and polygons, which correspond to the two shape files included in the original data. The source data for this layer are available here. Esri modified the attributes of these data to facilitate their use. A Species Type field was added and populated denoting the taxonomic group of each species and a field was added to link to the USFWS species profile for each species. The scientific and common name fields were edited to standardize capitalization and remove special characters. Several fields that did not contain data were removed. Attributes included in this layer are: Common NameScientific NameSpecies TypeSpecies CodePopulation CodeCritical Habitat Status - Final or ProposedFederal Register Publication Citation - The pop-ups for this field are pre-configured to link to the Federal Register search page for this value.Federal Register Publication DateListing Status - Threatened, Endangered, Proposed Threatened, or Proposed EndangeredLink to USFWS Species ProfileWhat can you do with this layer? This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop.The feature service is symbolized on the status of the critical habitat for each species. In ArcGIS Online you can change symbology.The data can also be filtered. For example selecting common name as the field and northern spotted owl as the value in the filter will return a map displaying only northern spotted owl critical habitat.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of the description page.This layer is part of the Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.

↑ Click Add to Favorites under the thumbnail for easy access to the service in Pro.This service is for use during INCIDENT response. This service is not for training purposes. Please use the Training Feature Service for training purposes (found here).Not for use in Mobile Data CollectionUse the Mobile Edit Service for web maps.Access the Structure Triage GISS Edit Service here.This service is for GISS use in ArcGIS Pro. Delete is enabled on this service. The service is used by all incidents simultaneously – care should be taken to not impact other incident data. For more information on using the GISS Edit service, please see the GISS Workflow site.

Reason for Selection Large areas of intact natural habitat are favorable for conservation of numerous species, including reptiles and amphibians, birds, and large mammals. The Esri Green Infrastructure data covers the entire United States and has been used in other broad-scale conservation planning efforts, so using this existing data helps align the Blueprint with other conservation efforts and reduce duplication of effort. We chose to use “Core Size (acres)” as the metric for this indicator. Other evaluation attributes included in this index, such as the default “Core Score”, were less suitable because they were calculated using inputs that are duplicative of other indicators.Input Data2021 National Land Cover Database (NLCD)Southeast Blueprint 2024 extentEsri’s Intact Habitat Cores 2023, accessed 2-16-2024: Core Size (Acres); to download, select “Open in ArcGIS Desktop” and make a local copy. According to Esri’s data description for the 2023 intact habitat cores update: “This layer represents modeled Intact Habitat Cores, or minimally disturbed natural areas at least 100 acres in size and greater than 200 meters wide. Esri created these data following a methodology outlined by the Green Infrastructure Center Inc. These data were generated using 2019 National Land Cover Data. Cores were derived from all “natural” landcover classes and excluded all “developed” and “agricultural” classes including crop, hay and pasture lands. The resulting cores were tested for size and width requirements (at least 100 acres in size and greater than 200 meters wide) and then converted into unique polygons.”Mapping StepsConvert the Esri Intact Habitat Cores 2023 polygons to a 30 m raster using the values in the “Acres” field. We used the feature layer map service as the input in the Polygon to Raster function in the code.Reclassify the above raster into 4 classes, seen in the final indicator values below.Use NLCD to remove zero values in deep marine areas, which are outside the scope of this terrestrial indicator. Use a conditional statement to assign NoData to any area with a pixel value >0 in the NLCD.As a final step, clip to the spatial extent of Southeast Blueprint 2024. 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:3 = Large core (>10,000 acres)2 = Medium core (>1,000-10,000 acres)1 = Small core (>100–1,000 acres) 0 = Not a coreKnown IssuesThe core analysis for this indicator is based on the 2019 NLCD, not the more recent 2021 NLCD. Esri has shared the scripts and input data used to create this layer, which may also help update this indicator in the future.Even small dirt roads serve as hard boundaries for habitat cores. While this makes sense for some species, this indicator likely underestimates the effective size of the patch for some more mobile animals.Waterbodies like reservoirs are also considered part of habitat cores, so this layer likely overestimates the effective size of the habitat core for most species.Many intact habitat cores have a speckling of small altered areas inside of them. In some cases, like in areas of west TX with concentrated oil wells, there can be many alterations in a gridded pattern across the entire core. This indicator underestimates the cumulative impacts of interior alterations—especially when the small altered footprints are densely packed in a grid within a habitat core.Disclaimer: Comparing with Older Indicator Versions There are numerous problems with using Southeast Blueprint indicators for change analysis. Please consult Blueprint staff if you would like to do this (email hilary_morris@fws.gov).Literature CitedEsri Green Infrastructure Center. Data Description: Detailed Description and Methodology for Intact Habitat Cores. PDF. Last updated June 30, 2023. [https://nation.maps.arcgis.com/home/item.html?id=047d9b05e0c842b1b126bc0767acfd5e]. Esri Green Infrastructure Center, Inc. 2023. Intact Habitat Cores (2023). [https://www.arcgis.com/home/item.html?id=b404b86a079a48049cb50272df23267a].

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

This data provides an overview of native amphibian restoration sites in the Sierra Nevada. Following High Mountain Lakes surveys, fish were manually removed at some high elevation lake sites. Removals of non-native trout were done at sites with mountain yellow-legged frogs or with frogs nearby. Fish removal is done without the use of chemicals, using monofilament gill nets and electrofishing. Gill nets catch adult and juvenile fish. Electrofishing is used primarily as a way to remove fish from small tributary streams and fry (less than 70mm) from shallow areas. Current literature has shown that mountain yellow-legged frog populations can rebound quickly after trout removal. Frog population counts at CDFW sites support this finding. The restoration data, along with the related high mountain lakes amphibian, fish and fisheries project data sets represent biological surveys conducted at a series of lakes in the Sierra Nevada ranging from Plumas County in the north to Tulare County in the south. During High Mountain Lake (HML) surveys, Sierra Nevada lentic waters were surveyed for fish, frogs, habitats, stream barriers to fish movement and presence of fairy shrimp. Lakes with fish were surveyed using monofilament gill nets. Amphibians were detected and documented based on direct observation. Contact Sarah Mussulman (916) 358-2838 for additional survey protocol detail and a description of methods. As part of the development of the biological data sets, researchers created a detailed coverage of lakes for (ostensibly) all known lentic water bodies in California above 5000’ elevation. Lake features were digitized from USGS 1:24000 quadrangles and assigned a unique identifying number. High Mountain Lakes (HML) surveys were performed in the Sierra Nevada starting in 2001 and use these unique ID numbers to reference waterbodies. WHAT EACH RECORD REPRESENTS: Each record represents a lake where CDFW has begun removing fish to benefit a population of mountain yellow-legged frogs. The majority of lakes in this dataset are currently fishless; a handful are active fish removal sites.

In addition to displaying earthquakes by magnitude, this service also provide earthquake impact details. Impact is measured by population as well as models for economic and fatality loss. For more details, see: PAGER Alerts. Consumption Best Practices:As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cache-able relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment.When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cache-able. Update Frequency: Events are updated as frequently as every 5 minutes and are available up to 30 days with the following exceptions:Events with a Magnitude LESS than 4.5 are retained for 7 daysEvents with a Significance value, "sig" field, of 600 or higher are retained for 90 days In addition to event points, ShakeMaps are also provided. These have been dissolved by Shake Intensity to reduce the Layer Complexity.The specific layers provided in this service have been Time Enabled and include:Events by Magnitude: The event’s seismic magnitude value.Contains PAGER Alert Level: USGS PAGER (Prompt Assessment of Global Earthquakes for Response) system provides an automated impact level assignment that estimates fatality and economic loss.Contains Significance Level: An event’s significance is determined by factors like magnitude, max MMI, ‘felt’ reports, and estimated impact.Shake Intensity: The Instrumental Intensity or Modified Mercalli Intensity (MMI) for available events. For field terms and technical details, see: ComCat Documentation Alternate SymbologiesVisit the Classic USGS Feature Layer item for a Rainbow view of Shakemap features. RevisionsSep 16, 2025: Exposed ‘UniqueId’ field in Shake Intensity Polygon layer.Sep 14, 2025: Upgrade to Layer data update workflow, to improve reliability and scalability.Aug 14, 2024: Added a default Minimum scale suppression of 1:6,000,000 on Shake Intensity layer. Jul 11, 2024: Updated event popup, setting "Tsunami Warning" text to "Alert Possible" when flag is present. Also included hyperlink to tsunami warning center. Feb 13, 2024: Updated feed logic to remove Superseded events This map is provided for informational purposes and is not monitored 24/7 for accuracy and currency. Always refer to USGS source for official guidance. If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

Three feature layers of Unites States internal state boundaries at different scales: 1:500K, 1:5M, and 1:20M. These layers are intended for use as a cartographic product. It is up to the user to determine which layer is most appropriate for their map.Derived from 2019 US Census Bureau Cartographic Boundary Files for state boundaries using ArcGIS Pro 2.4.3. Process:Original files were downloaded from US Census for the three different scales.Polygons were then converted to lines using the Polygon-to-Line tool.To remove the coastlines, all rows not having a LEFT_FID or RIGHT_FID attribute equal to -1 were then exported to a new geodatabase feature class.The geodatabase was zipped and uploaded to ArcGIS Online.For more information on Cartographic Boundary Files visit https://www.census.gov/programs-surveys/geography/technical-documentation/naming-convention/cartographic-boundary-file.html and https://www.census.gov/geographies/mapping-files/time-series/geo/cartographic-boundary.html.Created by Ryan Davis (RDavis9@cdc.gov) on behalf of CDC/ATSDR/DTHHS/GRASP.

Feature service for Hub annotations. DO NOT DELETE THIS SERVICE. It stores the public annotations (comments) for all Hub items in your organization.

Three feature layers of Unites States internal state boundaries at different scales: 1:500K, 1:5M, and 1:20M. These layers are intended for use as a cartographic product. It is up to the user to determine which layer is most appropriate for their map.Derived from 2019 US Census Bureau Cartographic Boundary Files for state boundaries using ArcGIS Pro 2.4.3. Process:Original files were downloaded from US Census for the three different scales.Polygons were then converted to lines using the Polygon-to-Line tool.To remove the coastlines, all rows not having a LEFT_FID or RIGHT_FID attribute equal to -1 were then exported to a new geodatabase feature class.The geodatabase was zipped and uploaded to ArcGIS Online.For more information on Cartographic Boundary Files visit https://www.census.gov/programs-surveys/geography/technical-documentation/naming-convention/cartographic-boundary-file.html and https://www.census.gov/geographies/mapping-files/time-series/geo/cartographic-boundary.html.Created by Ryan Davis (RDavis9@cdc.gov) on behalf of CDC/ATSDR/DTHHS/GRASP.

This feature class is updated every business day using Python scripts and the TCID databases. Please disregard the "Date Updated" field as it does not keep in sync with DWR's internal enterprise geodatabase updates.A Water Right change is a transaction that either adds or removes water from the original water right. The dataset covers surface water rights in the Fernley and Fallon areas of Nevada. This change layer does not show where water is used if the manner of use is converted from irrigation to another manner of use such as commercial, wildlife, or municipal. Some examples of water right changes are boundary lines to delineate where water can be used, how much water can be used, and manner of use.The dataset is used to track water right changes over time and to update the water righted dataset which shows the result of the place of use for water rights. Representation:The OnOff field indicates if a change added or removed water to a specific area. The Action Date field indicates when the change took place.The Map Used field identifies which map record was used to generate the place of use area (polygon).Date of Creation – 2015This dataset is updated whenever there is a change to a water right within the Newlands Mapping Project. The water right place of use change is plotted to add or remove acreage from an existing water right.

Sec. 368 Corridor Label: Depicts names of designated Section 368 Energy CorridorsSec. 368 Corridor Milepost: This layer depicts milepost point locations along the designated (per the requirements of Section 368 of the Energy Policy Act of 2005) as West-wide energy corridor centerlines in Bureau of Land Management and U.S. Forest Service Records of Decision in connection with the final Programmatic Environmental Impact Statement, Designation of Energy Corridors on Federal Land in the 11 Western States, November 2008. It is intended only as a means to describe locations along the designated corridors. Gaps in the corridor centerlines exist where federal land is not present and there are no designated corridors in these locations, however the gap distances are accounted for in the mileposting, and some mileposts exist in the gaps for continuity in the referencing system.Sec. 368 Designated Corridor - Current: This layer depicts areas which have been designated (per the requirements of Section 368 of the Energy Policy Act of 2005) as West-wide energy corridors in Bureau of Land Management and U.S. Forest Service management plans in connection with the final Programmatic Environmental Impact Statement, Designation of Energy Corridors on Federal Land in the 11Western States, November 2008 and the subsequent Records of Decision.Sec. 368 Designated Corridor - Historic: This layer depicts areas which have been Prohibited from Designation or Revised (per the requirements of Section 368 of the Energy Policy Act of 2005) as West-wide energy corridors in Bureau of Land Management and U.S. Forest Service management plans in connection with the final Programmatic Environmental Impact Statement, Designation of Energy Corridors on Federal Land in the 11Western States, November 2008 and the subsequent Records of Decision.Sec. 368 Designated Corridor Centerline: This layer depicts lines which have been designated (per the requirements of Section 368 of the Energy Policy Act of 2005) as West-wide energy corridor centerlines in Bureau of Land Management and U.S. Forest Service management plans in connection with the final Programmatic Environmental Impact Statement, Designation of Energy Corridors on Federal Land in the 11Western States, November 2008, and the subsequent Records of Decision. Each segment is also attributed with starting and ending mileposts.Regional Review Boundary: Regional review boundaries for Section 368 Energy Corridor reviews.Transmission Line (Wyoming BLM): This feature class contains existing above-ground transmission line geometry across the state of Wyoming. It was digitized from the 2015 NAIP aerial imagery dataset, and was checked for content against the Wyoming Infrastructure Authority data (via NREX) and Platts database data supplied by the BLM National Operations Center. This feature class will continue to be updated on an annual basis in correlation with the BLM's aviation hazards map products revision schedule.Legacy Locally Designated Corridor Area: The dataset consists of locally designated corridors. The dataset was created by combining corridors from multiple BLM sources. Datasets:Existing utility corridors on Kingman Field Office lands (received 9/3/14) Utah corridors (received 9/11/14)Designated BLM utility corridors in Montana (received 9/3/14)Utility corridors as identified by the Resource Management Plan on land managed by the USDOI Bureau of Land Management in the San Luis Valley in SouthCentral Colorado (received 5/14/09)Utility Corridors for the BLM California Desert District (received 7/10/09)Utility corridors in Nevada identified in various land use plans (received 9/3/14) Corridors in Nevada (received 11/3/08)Corridors in the Southern Nevada District Office (received 10/26/16) ROW Corridor designated in Gunnison RMP (received 10/20/2017)Text and map-based descriptions of corridors to remove in Arizona (received 11/8/2017)Legacy Locally Designated Corridor Centerline: This map is designed to display the utility corridors identified in various land use plans. It is a line coverage where lines are assigned labels of existing (some utility in the corridor) corridor, a designated (no utility using the corridor yet) corridor.BLM Solar Energy Zone: This dataset represents Solar Energy Zones available for utility-grade solar energy development under the Bureau of Land Management's Solar Energy Program Western Solar Plan. For details and definitions, see the website at http://blmsolar.anl.gov/sez/.BLM Solar Energy Zone Labels: This feature class was developed to represent Solar Energy Zones as part of the Bureau of Land Management's Solar Energy Program Western Solar Plan.BLM AZ Renewable Energy Dev. Areas: BLM RDEP ROD data. Restoration Design Energy Project Record of Decision, January 2013. This represents the REDA data based upon known resources listed in the ROD Table 2-1, Areas with Known Sensitive Resources (Eliminated from REDA Consideration), known at the time of January 2013. The REDAs may be changed in the future based upon changes in sensitive resources or further analysis and site specific analysis and new baseline data. RDEP decisions are only BLM-administered lands.Bureau of Land Management, Arizona State Office, in conjunction with Environmental Management and Planning Solutions, Incorporated (EMPSi).BLM DRECP Development Focus Area (DFA): This feature class represents Development Focus Areas (DFAs) in the Desert Renewable Energy Conservation Plan (DRECP) Region.BLM DRECP Variance Land: This feature class represents Variance Process Lands in the DRECP.WGA Western Renewable Energy Zone: Depicts renewable energy zone points centered in "geographic areas with at least 1,500 MW of high quality renewable energy within a 100 mile radius", as developed by the Western Governors'Association and U.S. Department of Energy in June 2009. Methodology used to create the dataare described in the WGA report: "Western Renewable Energy Zones - Phase 1Report: Mapping concentrated, high quality resources to meet demand in the WesternInterconnection's distant markets." June 2009.