NOTE: Due to the size of this file, it can only be downloaded as a File Geodatabase.This statewide shapefile contains the freshwater surface water classifications for all named streams in North Carolina. This data was first uploaded on March 6, 2015 and originally pulled from BIMS in November 2014. To learn more about what classifications are, see the Classifications and Standards/Rule Review Branch website. Download this dataset from the DEQ Open Data PageThe Tile Layer for this Feature Layer is DWR Surface Water Classifications.Attributes:BIMS_INDEX: Index number BIMS_Names: Stream Name BIMS_Descr: Description of stream segment (from - to) BIMS_Class: Surface Water Classification BIMS_Date: Date the classification was given to that segment ClassURL: Link to the Classifications website that defines each classification Name: River Basin Contacts:Data Contact: Chris VentaloroLayer/Service Contact: Melanie Williams Updates: 05/24/2016: Changed the URL for the classifications page; fixed the Clear Creek (FBR) line segment; re-uploaded this as a new feature service with the ability to overwrite. 6/1/2017: Geometry for Index Numbers 18-(71) of the Cape Fear River and 18-88-1 of Walden Creek were missing from the feature service. The geometry was corrected with the existing file on local servers and the online feature service was overwritten. This feature layer can be found in the NC Surface Water Classification map application.

Interagency Wildland Fire Perimeter History (IFPH) Overview This national fire history perimeter data layer of conglomerated agency perimeters was developed in support of the WFDSS application and wildfire decision support. The layer encompasses the fire perimeter datasets of the USDA Forest Service, US Department of Interior Bureau of Land Management, Bureau of Indian Affairs, Fish and Wildlife Service, and National Park Service, the Alaska Interagency Fire Center, CalFire, and WFIGS History. Perimeters are included thru the 2024 fire season. Requirements for fire perimeter inclusion, such as minimum acreage requirements, are set by the contributing agencies. WFIGS, NPS and CALFIRE data now include Prescribed Burns. Data InputSeveral data sources were used in the development of this layer, links are provided where possible below. In addition, many agencies are now using WFIGS as their authoritative source, beginning in mid-2020.Alaska fire history (WFIGS pull for updates began 2022)USDA FS Regional Fire History Data (WFIGS pull for updates began 2024)BLM Fire Planning and Fuels (WFIGS pull for updates began 2020)National Park Service - Includes Prescribed Burns (WFIGS pull for updates began 2020)Fish and Wildlife Service (WFIGS pull for updates began 2024)Bureau of Indian Affairs (Incomplete, 2017-2018 from BIA, WFIGS pull for updates began 2020)CalFire FRAS - Includes Prescribed Burns (CALFIRE only source, non-fed fires)WFIGS - updates included since mid-2020, unless otherwise noted Data LimitationsFire perimeter data are often collected at the local level, and fire management agencies have differing guidelines for submitting fire perimeter data. Often data are collected by agencies only once annually. If you do not see your fire perimeters in this layer, they were not present in the sources used to create the layer at the time the data were submitted. A companion service for perimeters entered into the WFDSS application is also available, if a perimeter is found in the WFDSS service that is missing in this Agency Authoritative service or a perimeter is missing in both services, please contact the appropriate agency Fire GIS Contact listed in the table below.Attributes This dataset implements the NWCG Wildland Fire Perimeters (polygon) data standard.https://www.nwcg.gov/sites/default/files/stds/WildlandFirePerimeters_definition.pdfIRWINID - Primary key for linking to the IRWIN Incident dataset. The origin of this GUID is the wildland fire locations point data layer maintained by IrWIN. (This unique identifier may NOT replace the GeometryID core attribute) FORID - Unique identifier assigned to each incident record in the Fire Occurence Data Records system. (This unique identifier may NOT replace the GeometryID core attribute) INCIDENT - The name assigned to an incident; assigned by responsible land management unit. (IRWIN required). Officially recorded name. FIRE_YEAR (Alias) - Calendar year in which the fire started. Example: 2013. Value is of type integer (FIRE_YEAR_INT). AGENCY - Agency assigned for this fire - should be based on jurisdiction at origin. SOURCE - System/agency source of record from which the perimeter came. DATE_CUR - The last edit, update, or other valid date of this GIS Record. Example: mm/dd/yyyy. MAP_METHOD - Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality.GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; Digitized-Topo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; Other GIS_ACRES - GIS calculated acres within the fire perimeter. Not adjusted for unburned areas within the fire perimeter. Total should include 1 decimal place. (ArcGIS: Precision=10; Scale=1). Example: 23.9 UNQE_FIRE_ - Unique fire identifier is the Year-Unit Identifier-Local Incident Identifier (yyyy-SSXXX-xxxxxx). SS = State Code or International Code, XXX or XXXX = A code assigned to an organizational unit, xxxxx = Alphanumeric with hyphens or periods. The unit identifier portion corresponds to the POINT OF ORIGIN RESPONSIBLE AGENCY UNIT IDENTIFIER (POOResonsibleUnit) from the responsible unit’s corresponding fire report. Example: 2013-CORMP-000001 LOCAL_NUM - Local incident identifier (dispatch number). A number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year. Field is string to allow for leading zeros when the local incident identifier is less than 6 characters. (IRWIN required). Example: 123456. UNIT_ID - NWCG Unit Identifier of landowner/jurisdictional agency unit at the point of origin of a fire. (NFIRS ID should be used only when no NWCG Unit Identifier exists). Example: CORMP COMMENTS - Additional information describing the feature. Free Text.FEATURE_CA - Type of wildland fire polygon: Wildfire (represents final fire perimeter or last daily fire perimeter available) or Prescribed Fire or Unknown GEO_ID - Primary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature. Globally Unique Identifier (GUID). Cross-Walk from sources (GeoID) and other processing notesAK: GEOID = OBJECT ID of provided file geodatabase (4,781 Records thru 2021), other federal sources for AK data removed. No RX data included.CA: GEOID = OBJECT ID of downloaded file geodatabase (8,480 Records, federal fires removed, includes RX. Significant cleanup occurred between 2023 and 2024 data pulls resulting in fewer perimeters).FWS: GEOID = OBJECTID of service download combined history 2005-2021 (2,959 Records), includes RX.BIA: GEOID = "FireID" 2017/2018 data (382 records). No RX data included.NPS: GEOID = EVENT ID 15,237 records, includes RX. In 2024/2023 dataset was reduced by combining singlepart to multpart based on valid Irwin, FORID or Unique Fire IDs. RX data included.BLM: GEOID = GUID from BLM FPER (23,730 features). No RX data included.USFS: GEOID=GLOBALID from EDW records (48,569 features), includes RXWFIGS: GEOID=polySourceGlobalID (9724 records added or replaced agency record since mid-2020)Attempts to repair Unique Fire ID not made. Attempts to repair dates not made. Verified all IrWIN IDs and FODRIDs present via joins and cross checks to the respective dataset. Stripped leading and trailing spaces, fixed empty values to

This dataset was updated April, 2024.This ownership dataset was generated primarily from CPAD data, which already tracks the majority of ownership information in California. CPAD is utilized without any snapping or clipping to FRA/SRA/LRA. CPAD has some important data gaps, so additional data sources are used to supplement the CPAD data. Currently this includes the most currently available data from BIA, DOD, and FWS. Additional sources may be added in subsequent versions. Decision rules were developed to identify priority layers in areas of overlap.Starting in 2022, the ownership dataset was compiled using a new methodology. Previous versions attempted to match federal ownership boundaries to the FRA footprint, and used a manual process for checking and tracking Federal ownership changes within the FRA, with CPAD ownership information only being used for SRA and LRA lands. The manual portion of that process was proving difficult to maintain, and the new method (described below) was developed in order to decrease the manual workload, and increase accountability by using an automated process by which any final ownership designation could be traced back to a specific dataset.The current process for compiling the data sources includes: Clipping input datasets to the California boundary Filtering the FWS data on the Primary Interest field to exclude lands that are managed by but not owned by FWS (ex: Leases, Easements, etc) Supplementing the BIA Pacific Region Surface Trust lands data with the Western Region portion of the LAR dataset which extends into California. Filtering the BIA data on the Trust Status field to exclude areas that represent mineral rights only. Filtering the CPAD data on the Ownership Level field to exclude areas that are Privately owned (ex: HOAs) In the case of overlap, sources were prioritized as follows: FWS > BIA > CPAD > DOD As an exception to the above, DOD lands on FRA which overlapped with CPAD lands that were incorrectly coded as non-Federal were treated as an override, such that the DOD designation could win out over CPAD.In addition to this ownership dataset, a supplemental _source dataset is available which designates the source that was used to determine the ownership in this dataset.Data Sources: GreenInfo Network's California Protected Areas Database (CPAD2023a). https://www.calands.org/cpad/; https://www.calands.org/wp-content/uploads/2023/06/CPAD-2023a-Database-Manual.pdf US Fish and Wildlife Service FWSInterest dataset (updated December, 2023). https://gis-fws.opendata.arcgis.com/datasets/9c49bd03b8dc4b9188a8c84062792cff_0/explore Department of Defense Military Bases dataset (updated September 2023) https://catalog.data.gov/dataset/military-bases Bureau of Indian Affairs, Pacific Region, Surface Trust and Pacific Region Office (PRO) land boundaries data (2023) via John Mosley John.Mosley@bia.gov Bureau of Indian Affairs, Land Area Representations (LAR) and BIA Regions datasets (updated Oct 2019) https://biamaps.doi.gov/bogs/datadownload.htmlData Gaps & Changes:Known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. Additionally, any feedback received about missing or inaccurate data can be taken back to the appropriate source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.24_1: Input datasets this year included numerous changes since the previous version, particularly the CPAD and DOD inputs. Of particular note was the re-addition of Camp Pendleton to the DOD input dataset, which is reflected in this version of the ownership dataset. We were unable to obtain an updated input for tribral data, so the previous inputs was used for this version.23_1: A few discrepancies were discovered between data changes that occurred in CPAD when compared with parcel data. These issues will be taken to CPAD for clarification for future updates, but for ownership23_1 it reflects the data as it was coded in CPAD at the time. In addition, there was a change in the DOD input data between last year and this year, with the removal of Camp Pendleton. An inquiry was sent for clarification on this change, but for ownership23_1 it reflects the data per the DOD input dataset.22_1 : represents an initial version of ownership with a new methodology which was developed under a short timeframe. A comparison with previous versions of ownership highlighted the some data gaps with the current version. Some of these known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. In addition, any topological errors (like overlaps or gaps) that exist in the input datasets may thus carry over to the ownership dataset. Ideally, any feedback received about missing or inaccurate data can be taken back to the relevant source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.

This is a copy of another layer - see original source: https://www.arcgis.com/home/item.html?id=e02b85c0ea784ce7bd8add7ae3d293d0OverviewThe national fire history perimeter data layer of conglomerated Agency Authoratative perimeters was developed in support of the WFDSS application and wildfire decision support for the 2021 fire season. The layer encompasses the final fire perimeter datasets of the USDA Forest Service, US Department of Interior Bureau of Land Management, Bureau of Indian Affairs, Fish and Wildlife Service, and National Park Service, the Alaska Interagency Fire Center, CalFire, and WFIGS History. Perimeters are included thru the 2021 fire season. Requirements for fire perimeter inclusion, such as minimum acreage requirements, are set by the contributing agencies. WFIGS, NPS and CALFIRE data now include Prescribed Burns. Data InputSeveral data sources were used in the development of this layer:Alaska fire history USDA FS Regional Fire History Data BLM Fire Planning and Fuels National Park Service - Includes Prescribed Burns Fish and Wildlife ServiceBureau of Indian AffairsCalFire FRAS - Includes Prescribed BurnsWFIGS - BLM & BIA and other S&LData LimitationsFire perimeter data are often collected at the local level, and fire management agencies have differing guidelines for submitting fire perimeter data. Often data are collected by agencies only once annually. If you do not see your fire perimeters in this layer, they were not present in the sources used to create the layer at the time the data were submitted. A companion service for perimeters entered into the WFDSS application is also available, if a perimeter is found in the WFDSS service that is missing in this Agency Authoratative service or a perimeter is missing in both services, please contact the appropriate agency Fire GIS Contact listed in the table below.AttributesThis dataset implements the NWCG Wildland Fire Perimeters (polygon) data standard.https://www.nwcg.gov/sites/default/files/stds/WildlandFirePerimeters_definition.pdfIRWINID - Primary key for linking to the IRWIN Incident dataset. The origin of this GUID is the wildland fire locations point data layer. (This unique identifier may NOT replace the GeometryID core attribute)INCIDENT - The name assigned to an incident; assigned by responsible land management unit. (IRWIN required). Officially recorded name.FIRE_YEAR (Alias) - Calendar year in which the fire started. Example: 2013. Value is of type integer (FIRE_YEAR_INT).AGENCY - Agency assigned for this fire - should be based on jurisdiction at origin.SOURCE - System/agency source of record from which the perimeter came.DATE_CUR - The last edit, update, or other valid date of this GIS Record. Example: mm/dd/yyyy.MAP_METHOD - Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality.GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; Digitized-Topo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; OtherGIS_ACRES - GIS calculated acres within the fire perimeter. Not adjusted for unburned areas within the fire perimeter. Total should include 1 decimal place. (ArcGIS: Precision=10; Scale=1). Example: 23.9UNQE_FIRE_ - Unique fire identifier is the Year-Unit Identifier-Local Incident Identifier (yyyy-SSXXX-xxxxxx). SS = State Code or International Code, XXX or XXXX = A code assigned to an organizational unit, xxxxx = Alphanumeric with hyphens or periods. The unit identifier portion corresponds to the POINT OF ORIGIN RESPONSIBLE AGENCY UNIT IDENTIFIER (POOResonsibleUnit) from the responsible unit’s corresponding fire report. Example: 2013-CORMP-000001LOCAL_NUM - Local incident identifier (dispatch number). A number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year. Field is string to allow for leading zeros when the local incident identifier is less than 6 characters. (IRWIN required). Example: 123456.UNIT_ID - NWCG Unit Identifier of landowner/jurisdictional agency unit at the point of origin of a fire. (NFIRS ID should be used only when no NWCG Unit Identifier exists). Example: CORMPCOMMENTS - Additional information describing the feature. Free Text.FEATURE_CA - Type of wildland fire polygon: Wildfire (represents final fire perimeter or last daily fire perimeter available) or Prescribed Fire or UnknownGEO_ID - Primary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature. Globally Unique Identifier (GUID).Cross-Walk from sources (GeoID) and other processing notesAK: GEOID = OBJECT ID of provided file geodatabase (4580 Records thru 2021), other federal sources for AK data removed. CA: GEOID = OBJECT ID of downloaded file geodatabase (12776 Records, federal fires removed, includes RX)FWS: GEOID = OBJECTID of service download combined history 2005-2021 (2052 Records). Handful of WFIGS (11) fires added that were not in FWS record.BIA: GEOID = "FireID" 2017/2018 data (416 records) provided or WFDSS PID (415 records). An additional 917 fires from WFIGS were added, GEOID=GLOBALID in source.NPS: GEOID = EVENT ID (IRWINID or FRM_ID from FOD), 29,943 records includes RX.BLM: GEOID = GUID from BLM FPER and GLOBALID from WFIGS. Date Current = best available modify_date, create_date, fire_cntrl_dt or fire_dscvr_dt to reduce the number of 9999 entries in FireYear. Source FPER (25,389 features), WFIGS (5357 features)USFS: GEOID=GLOBALID in source, 46,574 features. Also fixed Date Current to best available date from perimeterdatetime, revdate, discoverydatetime, dbsourcedate to reduce number of 1899 entries in FireYear.Relevant Websites and ReferencesAlaska Fire Service: https://afs.ak.blm.gov/CALFIRE: https://frap.fire.ca.gov/mapping/gis-dataBIA - data prior to 2017 from WFDSS, 2017-2018 Agency Provided, 2019 and after WFIGSBLM: https://gis.blm.gov/arcgis/rest/services/fire/BLM_Natl_FirePerimeter/MapServerNPS: New data set provided from NPS Fire & Aviation GIS. cross checked against WFIGS for any missing perimetersFWS -https://services.arcgis.com/QVENGdaPbd4LUkLV/arcgis/rest/services/USFWS_Wildfire_History_gdb/FeatureServerUSFS - https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_FireOccurrenceAndPerimeter_01/MapServerAgency Fire GIS ContactsRD&A Data ManagerVACANTSusan McClendonWFM RD&A GIS Specialist208-258-4244send emailJill KuenziUSFS-NIFC208.387.5283send email Joseph KafkaBIA-NIFC208.387.5572send emailCameron TongierUSFWS-NIFC208.387.5712send emailSkip EdelNPS-NIFC303.969.2947send emailJulie OsterkampBLM-NIFC208.258.0083send email Jennifer L. Jenkins Alaska Fire Service 907.356.5587 send emailLayers

This is a publicly available map image service with limited GIS attributes. A downloadable version of this data is now available through the MDOT GIS Open Data Portal: Download MDOT SHA Right-of-Way Polygons (Open Data Portal) The following related versions of this data are available here:MDOT SHA Right-of-Way (Secured)Line dataFull attribute tableAccessible to only MDOT employees and contractors upon requestMDOT SHA Right-of-Way (Map Image Service)Read-only map serviceLine dataLimited attributes (quality level)Accessible to publicMDOT SHA Right-of-Way data is a composite layer of PSD field-collected survey sources, PSD in-house computations, traced PSD hardcopy materials, and historical Maryland Department of Planning (MDP) parcel boundaries.This data product was intended to replace MDOT SHA Planning Level Right-of-Way (Tax Map Legacy), which is an increasingly obsolete legacy product for MDOT SHA Right-of-Way information that in some areas remains the most comprehensive. For continuity, many MDP parcel boundaries found in MDOT SHA Planning Level Right-of-Way (Tax Map Legacy) have been incorporated into MDOT SHA Right-of-Way data with an "Estimated" quality level. Please see below for a description of the primary attribute.-----------------------------------------------------The polygons in this layer are divided into 318 arbitrary grid zones across the State of Maryland. Updates to the parent ROW boundary line data set [MDOT SHA Right-of-Way (Secured)] are made by grid and reflected in this polygon layer.For more information or to report errors in this data, please contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Purpose: This spatially-based information is typically used in allocation decisions, boundary definitions, planning processes and environmental monitoring, by internal and external stakeholders.Notes: Assessment Watersheds are mesoscale aquatic units designed to replace the 3rd order 1:50K watersheds. Assessment Watersheds are based on groupings of fundamental watersheds using FWA watershed code and local code, with a target size of between 2,000ha and 10,000ha.WMS GetCapabilities URL: DataBC also offers access to this data in OGC WMS format. WMS is useful when the map author does not require custom popups, styling, or analytic capabilities for the layer. ArcGIS Online authors may want to use WMS, instead of this ArcGIS Server layer, in the following scenarios: Where they want to use existing Data Custodian approved styling, and/or They only need simple identify and map rendering functionality.Copy the: WMS GetCapabilities URL to add this web item to an ArcGIS Online Map or Scene Viewer. In some cases, multiple Styles are listed in the GetCapabilities and can be added as WMS Custom parameters. For more information on how to use a WMS layer see - ESRI's OGC ArcGIS Online HelpBC Data Catalogue Metadata URL: https://catalogue.data.gov.bc.ca/dataset/97d8ef37-b8d2-4c3b-b772-6b25c1db13d0

This dataset is an ArcGIS Shapefile representing areas that Planning & Zoning has determined to be Stormwater Draininage Problem Areas for use in the Minor Subdivision Review Process. The specific area's were identified by Roger Blaylock, County Engineer, Road & Bridge Foreman for each Commission District, and data received from Roads & Bridges during the April 2006 100 Year Flood Event. The Digital DFRIM was appended to the layer to replace FEMA Q3 data in April 2009.

Current and historical rezoning information (to replace static "dumb" maps). Finished back to 1970.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

This feature layer provides digital tax parcels for the Organized Towns of the State of Maine. Within Maine, real property data is maintained by the government organization responsible for assessing and collecting property tax for a given location. Organized towns and townships maintain authoritative data for their communities and may voluntarily submit these data to the Maine GeoLibrary Parcel Project. "Maine Parcels Organized Towns Feature" and "Maine Parcels Organized Towns ADB" are the product of these voluntary submissions. Communities provide updates to the Maine GeoLibrary on a non-regular basis, which affects the currency of Maine GeoLibrary parcels data. Another resource for real property transaction data is the County Registry of Deeds, although organized town data should very closely match registry information, except in the case of in-process property conveyance transactions. In Unorganized Territories (defined as those regions of the state without a local government that assesses real property and collects property tax), the Maine Revenue Service is the authoritative source for parcel data. "Maine Parcels Unorganized Territory Feature" is the authoritative GIS data layer for the Unorganized Territories. However, it must always be used with auxiliary data obtained from the online resources of Maine Revenue Services (https://www.maine.gov/revenue/taxes/property-tax) to compile up-to-date parcel ownership information. Property maps are a fundamental base for many municipal activities. Although GIS parcel data cannot replace detailed ground surveys, the data can assist municipal officials with functions such as accurate property tax assessment, planning and zoning. Towns can link maps to an assessor's database and display local information, while town officials can show taxpayers how proposed development or changes in municipal services and regulations may affect the community. In many towns, parcel data also helps to provide public notices, plan bus routes, and carry out other municipal services.

This dataset contains municipality-submitted parcel data along with previously developed parcel data acquired through the Municipal Grants Project supported by the Maine Library of Geographic Information (Maine GeoLibrary). Grant recipient parcel data submissions were guided by standards presented to the Maine GeoLibrary Board on May 21, 2005, which are outlined in the "Standards for Digital Parcel Files" document available on the Maine GeoLibrary publications page (https://www.maine.gov/geolib/policies/standards.html). This dataset also contains municipal parcel data acquired through other sources; the data sources are identified (where available) by the field “FMSCORG”. Note: Join this feature layer with the "Maine Parcels Organized Towns ADB" table (https://maine.hub.arcgis.com/maps/maine::maine-parcels-organized-towns-feature/about?layer=1) for available ownership information. A date field, “FMUPDAT”, is attributed with the most recent update date for each individual parcel if available. The "FMUPDAT" field will not match the "Updated" value shown for the layer. "FMUPDAT" corresponds with the date of update for the individual data, while "Updated" corresponds with the date of update for the ArcGIS Online layer as a whole. Many parcels have not been updated in several years; use the "FMUPDAT" field to verify currency.

This data set is part of an ongoing project to consolidate interagency fire perimeter data. Currently only certified perimeters and new perimeters captured starting in 2021 are included. A process for loading additional perimeters is being evaluated.The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service includes perimeters for wildland fire incidents that meet the following criteria:Categorized in the IRWIN (Integrated Reporting of Wildland Fire Information) integration service as a Wildfire (WF) or Prescribed Fire (RX)Is Valid and not "quarantined" in IRWIN due to potential conflicts with other recordsAttribution of the source polygon is set to a Feature Access of Public, a Feature Status of Approved, and an Is Visible setting of YesPerimeters are not available for every incident. This data set is an ongoing project with the end goal of providing a national interagency fire history feature service of best-available perimeters.No "fall-off" rules are applied to this service. The date range for this service will extend from present day back indefinitely. Data prior to 2021 will be incomplete and incorporated as an ongoing project.Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed every 5 minutes. Changes in the perimeter source may take up to 15 minutes to display.Perimeters are pulled from multiple sources with rules in place to ensure the most current or most authoritative shape is used.Warning: Please refrain from repeatedly querying the service using a relative date range. This includes using the “(not) in the last” operators in a Web Map filter and any reference to CURRENT_TIMESTAMP. This type of query puts undue load on the service and may render it temporarily unavailable.Attributes and their definitions can be found below. More detail about the NWCG Wildland Fire Event Polygon standard can be found here.Attributes:poly_SourceOIDThe OBJECTID value of the source record in the source dataset providing the polygon.poly_IncidentNameThe incident name as stored in the polygon source record.poly_MapMethodThe mapping method with which the polygon was derived.poly_GISAcresThe acreage of the polygon as stored in the polygon source record.poly_CreateDateSystem generated date for the date time the source polygon record was created (stored in UTC).poly_DateCurrentSystem generated date for the date time the source polygon record was last edited (stored in UTC).poly_PolygonDateTimeRepresents the date time that the polygon data was captured.poly_IRWINIDIRWIN ID stored in the polygon record.poly_FORIDFORID stored in the polygon record.poly_Acres_AutoCalcSystem calculated acreage of the polygon (geodesic WGS84 acres).poly_SourceGlobalIDThe GlobalID value of the source record in the source dataset providing the polygon.poly_SourceThe source dataset providing the polygon.attr_SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.attr_ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency initial attack fire suppression expenditures. for A, B, C & D size class fires on FS lands.attr_ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.attr_ContainmentDateTimeThe date and time a wildfire was declared contained. attr_ControlDateTimeThe date and time a wildfire was declared under control.attr_CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.attr_IncidentSizeReported for a fire. The minimum size is 0.1.attr_DiscoveryAcresAn estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.attr_EstimatedCostToDateThe total estimated cost of the incident to date.attr_FinalAcresReported final acreage of incident.attr_FFReportApprovedByTitleThe title of the person that approved the final fire report for the incident.attr_FFReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.attr_FFReportApprovedDateThe date that the final fire report was approved for the incident.attr_FireBehaviorGeneralA general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography. attr_FireBehaviorGeneral1A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral2A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral3A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. attr_FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. attr_FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. attr_FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. attr_FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.attr_FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.attr_FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. attr_FireOutDateTimeThe date and time when a fire is declared out. attr_FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.attr_FireStrategyFullSuppPrcntIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.attr_FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.attr_FireStrategyPointZonePrcntIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.attr_FSJobCodeA code use to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode.attr_FSOverrideCodeA code used to indicate the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.attr_GACCA code that identifies one of the wildland fire geographic area coordination center at the point of origin for the incident.A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.attr_ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.attr_ICS209RptForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.attr_ICS209RptForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. attr_ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates, and even multiple finals (as determined by business rules).attr_IncidentManagementOrgThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.attr_IncidentNameThe name assigned to an incident.attr_IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. attr_IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category further breaks down the Event Kind into more specific event categories.attr_IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.attr_InitialLatitudeThe latitude location of the initial reported point of origin specified in decimal degrees.attr_InitialLongitudeThe longitude location of the initial reported point of origin specified in decimal degrees.attr_InitialResponseAcresAn estimate of acres burning at the time of initial response. More specifically when the IC arrives and performs initial size up. The

This Esri File GeoDatabase (FGDB) contains digital tax parcel data for Maine Organized Towns and includes the following: Parcels (feature layer); Parcels_ADB (table); and GEOCODES (table).Within Maine, real property data is maintained by the government organization responsible for assessing and collecting property tax for a given location. Organized towns and townships maintain authoritative data for their communities and may voluntarily submit these data to the Maine GeoLibrary Parcel Project. Maine Parcels Organized Towns and Maine Parcels Organized Towns ADB are the product of these voluntary submissions. Communities provide updates to the Maine GeoLibrary on a non-regular basis, which affects the currency of Maine GeoLibrary parcels data; some data are more than ten years old. Another resource for real property transaction data is the County Registry of Deeds, although organized town data should very closely match registry information, except in the case of in-process property conveyance transactions.In Unorganized Territories (defined as those regions of the state without a local government that assesses real property and collects property tax), the Maine Revenue Service is the authoritative source for parcel data. Maine Parcels Unorganized Territory is the authoritative GIS data layer for the Unorganized Territories. However, it must always be used with auxiliary data obtained from the online resources of the Maine Revenue Service to compile up-to-date parcel ownership information.Property maps are a fundamental base for many municipal activities. Although GIS parcel data cannot replace detailed ground surveys, the data can assist municipal officials with functions such as accurate property tax assessment, planning and zoning. Towns can link maps to an assessor's database and display local information, while town officials can show taxpayers how proposed development or changes in municipal services and regulations may affect the community. In many towns, parcel data also helps to provide public notices, plan bus routes, and carry out other municipal services.This dataset contains municipality-submitted parcel data along with previously developed parcel data acquired through the Municipal Grants Project supported by the Maine Library of Geographic Information (MLGI). Grant recipient parcel data submissions were guided by standards presented to the MLGI Board on May 21, 2005,outlined in "Standards for Digital Parcel Files".GEOCODES is a table that lists standardized names and unique identifiers for Maine minor civil divisions and reservations, which represents the first official Standard Geographic Code endorsed and adopted by the Governor of Maine, on July 1, 1971.

File-based data for download: http://rangeland.ntsg.umt.edu/data/rap/rap-derivatives/great-plains/woody-transitions/transitions-30m/great-plains-transitions-30-2019.tif This product provides a rapid screening tool for identifying the leading edge of vegetation transitions in Great Plains rangelands and serves as an early warning for the loss of intact rangelands to woody expansion. Alternative ecological states are incapable of coexisting in the same space at a given point in time (Uden et al. 2019). For example, a savanna represents co-dominance of grasses and trees, meaning that grass-tree functional groups relatively coexist in the same space over time. In contrast, grass-tree functional groups fail to coexist in many regions of the world and represent fundamental alternative states in those instances. Transitions from one state to another are known to exhibit strong spatial order (Roberts et al. 2019; Allen et al. 2016); therefore, functional groups that do not coexist should covary negatively in space. This data product maps the geographic boundaries between grassy and woody states at two scales. When the geographic location of these boundaries change over time, rangeland resilience is being eroded (Uden et al. 2019) and the system is increasingly vulnerable to being lost to woody expansion. This is represented in the data product when a signal is present in a given year, persistent over multiple years, and non-stationarity in its geographic location over time.For planning purposes, two scales were pulled from a multitude of scales in a multi-scale analysis (following Uden et al. 2019) and provided as woody transitions layers. The broad-scale layer is computed and visualized to represent the boundary of the Great Plains grasslands biome, with scale being a product of both moving window (i.e., kernel) dimension and pixel resolution (i.e., grain). The broad-scale layer was computed with a 139 x 139-pixel moving window algorithm at 240-meter resolution. A second, moderate-scale was computed and visualized for regional-scale planning and represents the general spatial boundaries between alternative grassy and woody ecological states at a more detailed resolution. The moderate-scale layer was computed with an 81 x 81-pixel moving window algorithm at 30-meter resolution. Increasingly negative spatial covariance values between grass and tree functional groups represent increasingly severe segregation of grass/tree functional groups in space. Fill value = NA/NoData; corresponds to developed areas, croplands, or water, as classified in the 2011 National Land Cover Database (Homer et al. 2015), or wetlands and their 60-m buffers, as delineated in the National Wetlands Inventory (U.S. Fish and Wildlife Service 2019).Data use and interpretation must follow guidelines set forth athttp://rangelands.app, Uden et al. (2019), and Allred et al. (2020).Reminders and limitations: Transition data are meant to be combined with RAP cover data and local expert knowledge to understand vegetation change and is not meant to replace those products.When mapping spatial covariance data, upper and lower values over which the color ramp is stretched influence the sensitivity of the early warning signal of vegetation change and the display of transition severity. Such optimization of images may be useful for mapping variability over different ranges of transition severity in different locations; however, users should be advised that these adjustments also affect the potential for false positives/negatives in spatial transition detection. Transition signals were computed for conservation planning at two scales and represent a subset of a more robust multi-scale analysis. Cross-scale considerations of transitions will elucidate patches of intact rangeland vegetation nested within broader regional patterns shown here. Product testing is underway on cross-scale products and outputs.Only one functional group combination from RAP data is present in this data. Alternative functional group combinations may provide additional insights into vegetation transitions at various scales.

EarthExplorerUse the USGS EarthExplorer (EE) to search, download, and order satellite images, aerial photographs, and cartographic products. In addition to data from the Landsat missions and a variety of other data providers, EE provides access to MODIS land data products from the NASA Terra and Aqua missions, and ASTER level-1B data products over the U.S. and Territories from the NASA ASTER mission. Registered users of EE have access to more features than guest users.Earth Explorer Distribution DownloadThe EarthExplorer user interface is an online search, discovery, and ordering tool developed by the United States Geological Survey (USGS). EarthExplorer supports the searching of satellite, aircraft, and other remote sensing inventories through interactive and textual-based query capabilities. Through the interface, users can identify search areas, datasets, and display metadata, browse and integrated visual services within the interface.The distributable version of EarthExplorer provides the basic software to provide this functionality. Users are responsible for verification of system recommendations for hosting the application on your own servers. By default, this version of our code is not hooked up to a data source so you will have to integrate the interface with your data. Integration options include service-based API's, databases, and anything else that stores data. To integrate with a data source simply replace the contents of the 'getDataset' and 'search' functions in the CWIC.php file.Distribution is being provided due to users requests for the codebase. The EarthExplorer source code is provided "As Is", without a warranty or support of any kind. The software is in the public domain; it is available to any government or private institution.The software code base is managed through the USGS Configuration Management Board. The software is managed through an automated configuration management tool that updates the code base when new major releases have been thoroughly reviewed and tested.Link: https://earthexplorer.usgs.gov/

Purpose: This data has been published to support the Waikato Regional Hazards Portal. Statement: River flood depth for a 1% annual exceedance probability (AEP) event, derived from 2D local flood modelling. To determine the potential flood depth, the flood level data was reclassified into flood depth above ground level (from LiDAR data) in meters. Data is presented as polygons which show flood depth classes (not values), and should be used for mapping purposes. Attribute information includes the year the modelling was completed (from ~2006 onwards). Models have incorporated the best available information at the time of their creation, generally including (but not always) LiDAR data, and flood event survey assessments. A climate change component is generally included in the modelling and will likely be based on the best available MfE guidance from the period of modelling. All flood depth information takes into account the presence of WRC-managed stopbanks and floodwalls, with the exception of Tararu and Te Puru (which have been modelled using a “stopbanks down” approach). The LiDAR data is converted to a grid which has limitation when assessing small stream channels and topographic features such as ridges. This may lead to minor discrepancies in water flows which may lead to limitations in defining flood extents. Internal drainage such as storm water systems, culverts, piping etc, are generally not included in the modelling. Depending on how the model is configured, they often only consider the main watercourse, so flooding of minor channels, tributaries, ponding and coastal inundation may not be represented by the flood extent. This information is not intended to replace more detailed hydrogeological and survey data required for Building Consents or Resource Consents. The information shown is current as of the time of modelling, including assumptions around climate change and hydrology etc. Note that this is a “live” dataset and further additions will be made as and when available and verified. WRC Natural Hazard Information Hierarchy:1. Property to local scaleInformation that is suitable to be used for property specific purposes, including within District Plans, or for: • risk assessments • resource or building consents • decisions that concern personal or public safety • the conduct of commercial business • insurance purposes • land information memorandum reports (LIMs) The information is based on detailed hazard modelling or hazards mapping that includes both current and future possible scenarios, along with the associated likelihoods and impacts. Users should make sure they are using the most appropriate natural hazards data available. Data held by other organisations may be better suited for property scale use or may be more up to date. Before using any of the Waikato Regional Council natural hazard data at property scale or for subdivision development purposes please contact the Waikato Regional Council Regional Resilience team for guidance. Further information on resource consenting is available here.WRC Metadata: HAZARD.sdeadmin.HAZ_MOD_LOCAL_FLOOD_DEPTH - HAZARDS - Regional Hazards Portal - GIS Layers Terms of Use: This work is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License.Should users wish to distribute or publish derivatives or modified versions of this data then they must seek a data use agreement through WRC first. See the Waikato Regional Hazards Portal Terms of use here Waikato Regional Hazards Portal - Terms of use | Waikato Regional Council.