3 datasets found
  1. a

    North Complex

    • nifc.hub.arcgis.com
    Updated Sep 30, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Interagency Fire Center (2020). North Complex [Dataset]. https://nifc.hub.arcgis.com/maps/5ec1eea9e74c40b7951639a1a452a35b
    Explore at:
    Dataset updated
    Sep 30, 2020
    Dataset authored and provided by
    National Interagency Fire Center
    Area covered
    Description

    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

  2. BLM Natl WesternUS GRSG Sagebrush Focal Areas

    • catalog.data.gov
    • gimi9.com
    Updated Nov 11, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bureau of Land Management (2025). BLM Natl WesternUS GRSG Sagebrush Focal Areas [Dataset]. https://catalog.data.gov/dataset/blm-natl-westernus-grsg-sagebrush-focal-areas-87219
    Explore at:
    Dataset updated
    Nov 11, 2025
    Dataset provided by
    Bureau of Land Managementhttp://www.blm.gov/
    Description

    This dataset is a modified version of the FWS developed data depicting “Highly Important Landscapes”, as outlined in Memorandum FWS/AES/058711 and provided to the Wildlife Habitat Spatial analysis Lab on October 29th 2014. Other names and acronyms used to refer to this dataset have included: Areas of Significance (AoSs - name of GIS data set provided by FWS), Strongholds (FWS), and Sagebrush Focal Areas (SFAs - BLM). The BLM will refer to these data as Sagebrush Focal Areas (SFAs). Data were provided as a series of ArcGIS map packages which, when extracted, contained several datasets each. Based on the recommendation of the FWS Geographer/Ecologist (email communication, see data originator for contact information) the dataset called “Outiline_AreasofSignificance” was utilized as the source for subsequent analysis and refinement. Metadata was not provided by the FWS for this dataset. For detailed information regarding the dataset’s creation refer to Memorandum FWS/AES/058711 or contact the FWS directly. Several operations and modifications were made to this source data, as outlined in the “Description” and “Process Step” sections of this metadata file. Generally: The source data was named by the Wildlife Habitat Spatial Analysis Lab to identify polygons as described (but not identified in the GIS) in the FWS memorandum. The Nevada/California EIS modified portions within their decision space in concert with local FWS personnel and provided the modified data back to the Wildlife Habitat Spatial Analysis Lab. Gaps around Nevada State borders, introduced by the NVCA edits, were then closed as was a large gap between the southern Idaho & southeast Oregon present in the original dataset. Features with an area below 40 acres were then identified and, based on FWS guidance, either removed or retained. Finally, guidance from BLM WO resulted in the removal of additional areas, primarily non-habitat with BLM surface or subsurface management authority. Data were then provided to each EIS for use in FEIS development. Based on guidance from WO, SFAs were to be limited to BLM decision space (surface/sub-surface management areas) within PHMA. Each EIS was asked to provide the limited SFA dataset back to the National Operations Center to ensure consistent representation and analysis. Returned SFA data, modified by each individual EIS, was then consolidated at the BLM’s National Operations Center retaining the three standardized fields contained in this dataset.Several Modifications from the original FWS dataset have been made. Below is a summary of each modification.1. The data as received from FWS: 16,514,163 acres & 1 record.2. Edited to name SFAs by Wildlife Habitat Spatial Analysis Lab:Upon receipt of the “Outiline_AreasofSignificance” dataset from the FWS, a copy was made and the one existing & unnamed record was exploded in an edit session within ArcMap. A text field, “AoS_Name”, was added. Using the maps provided with Memorandum FWS/AES/058711, polygons were manually selected and the “AoS_Name” field was calculated to match the names as illustrated. Once all polygons in the exploded dataset were appropriately named, the dataset was dissolved, resulting in one record representing each of the seven SFAs identified in the memorandum.3. The NVCA EIS made modifications in concert with local FWS staff. Metadata and detailed change descriptions were not returned with the modified data. Contact Leisa Wesch, GIS Specialist, BLM Nevada State Office, 775-861-6421, lwesch@blm.gov, for details.4. Once the data was returned to the Wildlife Habitat Spatial Analysis Lab from the NVCA EIS, gaps surrounding the State of NV were closed. These gaps were introduced by the NVCA edits, exacerbated by them, or existed in the data as provided by the FWS. The gap closing was performed in an edit session by either extending each polygon towards each other or by creating a new polygon, which covered the gap, and merging it with the existing features. In addition to the gaps around state boundaries, a large area between the S. Idaho and S.E. Oregon SFAs was filled in. To accomplish this, ADPP habitat (current as of January 2015) and BLM GSSP SMA data were used to create a new polygon representing PHMA and BLM management that connected the two existing SFAs.5. In an effort to simplify the FWS dataset, features whose areas were less than 40 acres were identified and FWS was consulted for guidance on possible removal. To do so, features from #4 above were exploded once again in an ArcMap edit session. Features whose areas were less than forty acres were selected and exported (770 total features). This dataset was provided to the FWS and then returned with specific guidance on inclusion/exclusion via email by Lara Juliusson (lara_juliusson@fws.gov). The specific guidance was:a. Remove all features whose area is less than 10 acresb. Remove features identified as slivers (the thinness ratio was calculated and slivers identified by Lara Juliusson according to https://tereshenkov.wordpress.com/2014/04/08/fighting-sliver-polygons-in-arcgis-thinness-ratio/) and whose area was less than 20 acres.c. Remove features with areas less than 20 acres NOT identified as slivers and NOT adjacent to other features.d. Keep the remainder of features identified as less than 40 acres.To accomplish “a” and “b”, above, a simple selection was applied to the dataset representing features less than 40 acres. The select by location tool was used, set to select identical, to select these features from the dataset created in step 4 above. The records count was confirmed as matching between the two data sets and then these features were deleted. To accomplish “c” above, a field (“AdjacentSH”, added by FWS but not calculated) was calculated to identify features touching or intersecting other features. A series of selections was used: first to select records 6. Based on direction from the BLM Washington Office, the portion of the Upper Missouri River Breaks National Monument (UMRBNM) that was included in the FWS SFA dataset was removed. The BLM NOC GSSP NLCS dataset was used to erase these areas from #5 above. Resulting sliver polygons were also removed and geometry was repaired.7. In addition to removing UMRBNM, the BLM Washington Office also directed the removal of Non-ADPP habitat within the SFAs, on BLM managed lands, falling outside of Designated Wilderness’ & Wilderness Study Areas. An exception was the retention of the Donkey Hills ACEC and adjacent BLM lands. The BLM NOC GSSP NLCS datasets were used in conjunction with a dataset containing all ADPP habitat, BLM SMA and BLM sub-surface management unioned into one file to identify and delete these areas.8. The resulting dataset, after steps 2 – 8 above were completed, was dissolved to the SFA name field yielding this feature class with one record per SFA area.9. Data were provided to each EIS for use in FEIS allocation decision data development.10. Data were subset to BLM decision space (surface/sub-surface) within PHMA by each EIS and returned to the NOC.11. Due to variations in field names and values, three standardized fields were created and calculated by the NOC:a. SFA Name – The name of the SFA.b. Subsurface – Binary “Yes” or “No” to indicated federal subsurface estate.c. SMA – Represents BLM, USFS, other federal and non-federal surface management 12. The consolidated data (with standardized field names and values) were dissolved on the three fields illustrated above and geometry was repaired, resulting in this dataset.

  3. a

    Stormwater Modeling Impervious Land Cover Type

    • hub.arcgis.com
    • data-cityofmadison.opendata.arcgis.com
    Updated Feb 6, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Madison Map Data (2017). Stormwater Modeling Impervious Land Cover Type [Dataset]. https://hub.arcgis.com/datasets/2ed52d3fe98740a787c67c9c6af3d0a2
    Explore at:
    Dataset updated
    Feb 6, 2017
    Dataset authored and provided by
    City of Madison Map Data
    Area covered
    Description

    Task4_ImperviousUpdate2022 - this feature class represents the complete set of impervious features created by the GeoTREE Center. The 2020 project used a multi-step geoprocessing workflow to import data from various sources provided by the City of Madison and then through visual interpretation and digitizing of features. The basic original process was to use a variety of semi-automated and manual geoprocessing to pull/create polygon features from a variety of feature classes provided by the City of Madison at the beginning of the project. These feature classes included curb lines (Curb_Line_Rd), bike/ped paths (Bike_Ped_Paths), buildings (Building_Footprint_DaneCo and SWU_ImperviousAreas), and water body areas (HydroPoly_RFPArea). After building these inherited polygons into this feature class the majority of the work in this project was digitizing impervious features in this feature class based on the Subtype schema associated with the source_area field in this feature class. That schema can be seen below:0 Flat Roof1 Sloped Roof2 Parking3 Unpaved Parking4 Sidewalks5 Driveways6 Water Body Areas7 Streets8 Alleys9 Playground10 Other Impervious Areas11 Landscaped Areas12 Undeveloped Areas13 Other Pervious Areas14 Isolated AreasAll original digitizing was done with 2018 imagery from https://gisimg.cityofmadison.com/arcgis/services/ImageServices/2018_CITY_COLOR/ImageServer. Descriptions of fields is below:source_area - this is the main field as required by the original RFP and in which the above subytpe schema was set up. When GeoTREE Center workers were editing they would choose from the subtype choices and create or edit polygons. GeometryFrom - this field will hold a value indicating the feature class that the original polygon was inherited from (e.g.. HydroPoly_RFPArea). It is still possible that a GeoTREE Center worker would have manually edited the polygons with a value in here although most of these geometries likely are directly inherited from the feature class indicated. The polygons with a value of Bike_Ped_Paths buffered' went through a process of buffering the original line features based on a width attribute and then were manually edited by GeoTREE Center workers as needed. The polygons with Curb_Line_RD with GeoTREE Edits in GeometryFrom field wrere the result of a multiple step geoprocessing workflow to translate the lines into polygons with significant manually editiing by GeoTREE Center workers. source_area_int - the integer value stored in source_area field source_area_desc - the source area descriptionIn 2022 the GeoTREE Center used imagery indicated below to visually inspect and digitize newly developed polygon features as well as to find changes in the built environment and to delete/edit/create new features as needed. The GeometryFrom column has a value of 'UNI GeoTREE Created 2022' the feature was created during this 2022 round of digitizing. https://gisimg.cityofmadison.com/arcgis/services/ImageServices/2020_CITY_COLOR_WEBMERC/ImageServerhttps://dcimapapps.countyofdane.com/arcgisimg/services/ColorOrtho6Inch2020WEB/ImageServer

  4. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
National Interagency Fire Center (2020). North Complex [Dataset]. https://nifc.hub.arcgis.com/maps/5ec1eea9e74c40b7951639a1a452a35b

North Complex

Explore at:
Dataset updated
Sep 30, 2020
Dataset authored and provided by
National Interagency Fire Center
Area covered
Description

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

Search
Clear search
Close search
Google apps
Main menu