A boundary within which National Forest System land parcels have management or use limits placed on them by the Forest Service. Examples include: Archaeological Area, Research Natural Area, and Scenic Area.

The National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territoriesGeographic Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSUpdate Frequency: AnnualPublication Date: July 2022This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not. Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map.Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS 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.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

An area depicting National Forest System land parcels that have management or use limits placed on them by legal authority. Examples are: National Recreation Area, National Monument, and National Game Refuge. Metadata

The Residential Schools Locations Dataset in Geodatabase format (IRS_Locations.gbd) contains a feature layer "IRS_Locations" that contains the locations (latitude and longitude) of Residential Schools and student hostels operated by the federal government in Canada. All the residential schools and hostels that are listed in the Residential Schools Settlement Agreement are included in this dataset, as well as several Industrial schools and residential schools that were not part of the IRRSA. This version of the dataset doesn’t include the five schools under the Newfoundland and Labrador Residential Schools Settlement Agreement. The original school location data was created by the Truth and Reconciliation Commission, and was provided to the researcher (Rosa Orlandini) by the National Centre for Truth and Reconciliation in April 2017. The dataset was created by Rosa Orlandini, and builds upon and enhances the previous work of the Truth and Reconcilation Commission, Morgan Hite (creator of the Atlas of Indian Residential Schools in Canada that was produced for the Tk'emlups First Nation and Justice for Day Scholar's Initiative, and Stephanie Pyne (project lead for the Residential Schools Interactive Map). Each individual school location in this dataset is attributed either to RSIM, Morgan Hite, NCTR or Rosa Orlandini. Many schools/hostels had several locations throughout the history of the institution. If the school/hostel moved from its’ original location to another property, then the school is considered to have two unique locations in this dataset,the original location and the new location. For example, Lejac Indian Residential School had two locations while it was operating, Stuart Lake and Fraser Lake. If a new school building was constructed on the same property as the original school building, it isn't considered to be a new location, as is the case of Girouard Indian Residential School.When the precise location is known, the coordinates of the main building are provided, and when the precise location of the building isn’t known, an approximate location is provided. For each residential school institution location, the following information is provided: official names, alternative name, dates of operation, religious affiliation, latitude and longitude coordinates, community location, Indigenous community name, contributor (of the location coordinates), school/institution photo (when available), location point precision, type of school (hostel or residential school) and list of references used to determine the location of the main buildings or sites. Access Instructions: there are 47 files in this data package. Please download the entire data package by selecting all the 47 files and click on download. Two files will be downloaded, IRS_Locations.gbd.zip and IRS_LocFields.csv. Uncompress the IRS_Locations.gbd.zip. Use QGIS, ArcGIS Pro, and ArcMap to open the feature layer IRS_Locations that is contained within the IRS_Locations.gbd data package. The feature layer is in WGS 1984 coordinate system. There is also detailed file level metadata included in this feature layer file. The IRS_locations.csv provides the full description of the fields and codes used in this dataset.

Analysis of ‘Survey parcels described by metes and bounds (Feature Layer)’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/5052d7ad-1bc6-4575-a3ec-eed07f886098 on 11 February 2022.

--- Dataset description provided by original source is as follows ---

A depiction of a survey parcel described by a metes and bounds description. Examples include: land lots, housing subdivision lots, mineral surveys, and homestead entry surveys. Metadata

--- Original source retains full ownership of the source dataset ---

Context

CIFAR-10 features collected from VGG19 model at 85% test accuracy. Consists of features from all 19 layers of 10,000 test images. Each layer has its own directory. Inside each layer directory, the features are stored per batch with filename started from 1 to (in current case) 5 with batch size of 2,000 images.

Image dataset is from version 1. Refer to this dataset to get the image, the label and the filename. Concatenate batch files in an ascending manner to get index to index relation between the image and the feature.

Extracted from notebook version 10.

Content

16 feature layer directories (conv1_1, conv1_2, ..., conv5_4) and 3 classifier layer directories (lin1, lin2, and lin3). Each layer directory consists of saved files 1 to 5 in serialized NumPy using Python pickle. The file with 2,000 batch size has shape of [2000, dim1, dim2, dim3] for feature layers or [2000, dim1] for classifier layers.

Example for feature layer: conv1_1 (2000, 64, 32, 32) conv1_2 (2000, 64, 32, 32) conv2_1 (2000, 128, 16, 16) conv2_2 (2000, 128, 16, 16) conv3_1 (2000, 256, 8, 8) conv3_2 (2000, 256, 8, 8) conv3_3 (2000, 256, 8, 8) conv3_4 (2000, 256, 8, 8) conv4_1 (2000, 512, 4, 4) conv4_2 (2000, 512, 4, 4) conv4_3 (2000, 512, 4, 4) conv4_4 (2000, 512, 4, 4) conv5_1 (2000, 512, 2, 2) conv5_2 (2000, 512, 2, 2) conv5_3 (2000, 512, 2, 2) conv5_4 (2000, 512, 2, 2)

Example for classifier layer: lin1 (2000, 4096) lin2 (2000, 4096) lin3 (2000, 10)

A depiction of a survey parcel described by a metes and bounds description. Examples include: land lots, housing subdivision lots, mineral surveys, and homestead entry surveys. Metadata

Analysis of ‘Survey parcels described by metes and bounds (Feature Layer)’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/35672639-db40-4e82-921a-6661e844621f on 28 January 2022.

--- Dataset description provided by original source is as follows ---

A depiction of a survey parcel described by a metes and bounds description. Examples include: land lots, housing subdivision lots, mineral surveys, and homestead entry surveys. Metadata

--- Original source retains full ownership of the source dataset ---

The geospatial data reflected in the protected area layer mostly pertain to natural and wilderness areas where development of utility-scale renewable energy is prohibited and were heavily based on RETI 1.0 blackout areas.1 The protected area layer is distinguished for solar PV technology by the BLM greater sage grouse habitat management area which provides separate exclusion areas for the different technology types. Tables 1 and 2 below lists the data sources and precise selection query for each dataset, if applicable, that make up the protected area layer.Table 1: Datasets used in the Protected Area Layer Dataset Example Designations Citation or hyperlink PAD-US (CBI Edition) National Parks, GAP Status 1 and 2, State Parks, Open Spaces, Natural Areas “PAD-US (CBI Edition) Version 2.1b, California”. Conservation Biology Institute. 2016. https://databasin.org/datasets/64538491f43e42ba83e26b849f2cad28. Conservation Easements California Conservation Easement Database (CCED), 2022a. 2022. www.CALands.org. Accessed December 2022. Inventoried Roadless Areas “Inventoried Roadless Areas.” US Forest Service. Dec 12, 2022. https://www.fs.usda.gov/detail/roadless/2001roadlessrule/maps/?cid=stelprdb5382437 BLM National Landscape Conservation System Wilderness Areas, Wilderness Study Areas, National Monuments, National Conservation Lands, Conservation Lands of the California Desert, Scenic Rivers https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-wilderness-areas https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-wilderness-study-areas https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-national-monuments-nca-forest-reserves-other-poly/ Greater Sage Grouse Habitat Conservation Areas (BLM) For solar technology: BLM_Managm IN (‘PHMA’, ‘GHMA’, ‘OHMA’) For wind technology: BLMP_Managm = ‘PHMA’ “Nevada and Northeastern California Greater Sage-Grouse Approved Resource Management Plan Amendment.” US Department of the Interior Bureau of Land Management Nevada State Office. 2015. https://eplanning.blm.gov/public_projects/lup/103343/143707/176908/NVCA_Approved_RMP_Amendment.pdf Other BLM Protected Areas Areas of Critical Environmental Concern (ACECs), Recreation Areas (SRMA, ERMA, OHV Designated Areas), including Vinagre Wash Special Recreation Management Area, National Scenic Areas, including Alabama Hills National Scenic Area https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-off-highway-vehicle-designations

The establishment of a BES Multi-User Geodatabase (BES-MUG) allows for the storage, management, and distribution of geospatial data associated with the Baltimore Ecosystem Study. At present, BES data is distributed over the internet via the BES website. While having geospatial data available for download is a vast improvement over having the data housed at individual research institutions, it still suffers from some limitations. BES-MUG overcomes these limitations; improving the quality of the geospatial data available to BES researches, thereby leading to more informed decision-making.

   BES-MUG builds on Environmental Systems Research Institute's (ESRI) ArcGIS and ArcSDE technology. ESRI was selected because its geospatial software offers robust capabilities. ArcGIS is implemented agency-wide within the USDA and is the predominant geospatial software package used by collaborating institutions.


   Commercially available enterprise database packages (DB2, Oracle, SQL) provide an efficient means to store, manage, and share large datasets. However, standard database capabilities are limited with respect to geographic datasets because they lack the ability to deal with complex spatial relationships. By using ESRI's ArcSDE (Spatial Database Engine) in conjunction with database software, geospatial data can be handled much more effectively through the implementation of the Geodatabase model. Through ArcSDE and the Geodatabase model the database's capabilities are expanded, allowing for multiuser editing, intelligent feature types, and the establishment of rules and relationships. ArcSDE also allows users to connect to the database using ArcGIS software without being burdened by the intricacies of the database itself.


   For an example of how BES-MUG will help improve the quality and timeless of BES geospatial data consider a census block group layer that is in need of updating. Rather than the researcher downloading the dataset, editing it, and resubmitting to through ORS, access rules will allow the authorized user to edit the dataset over the network. Established rules will ensure that the attribute and topological integrity is maintained, so that key fields are not left blank and that the block group boundaries stay within tract boundaries. Metadata will automatically be updated showing who edited the dataset and when they did in the event any questions arise.


   Currently, a functioning prototype Multi-User Database has been developed for BES at the University of Vermont Spatial Analysis Lab, using Arc SDE and IBM's DB2 Enterprise Database as a back end architecture. This database, which is currently only accessible to those on the UVM campus network, will shortly be migrated to a Linux server where it will be accessible for database connections over the Internet. Passwords can then be handed out to all interested researchers on the project, who will be able to make a database connection through the Geographic Information Systems software interface on their desktop computer. 


   This database will include a very large number of thematic layers. Those layers are currently divided into biophysical, socio-economic and imagery categories. Biophysical includes data on topography, soils, forest cover, habitat areas, hydrology and toxics. Socio-economics includes political and administrative boundaries, transportation and infrastructure networks, property data, census data, household survey data, parks, protected areas, land use/land cover, zoning, public health and historic land use change. Imagery includes a variety of aerial and satellite imagery.


   See the readme: http://96.56.36.108/geodatabase_SAL/readme.txt


   See the file listing: http://96.56.36.108/geodatabase_SAL/diroutput.txt

The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses. For more information on the NHDPlus dataset see the NHDPlus v2 User Guide.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territories not including Alaska.Geographic Extent: The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: EPA and USGSUpdate Frequency: There is new new data since this 2019 version, so no updates planned in the futurePublication Date: March 13, 2019Prior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, On or Off Network (flowlines only), Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute. Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map. Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class. Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS 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.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

Jurisdictional Unit, 2022-05-21. For use with WFDSS, IFTDSS, IRWIN, and InFORM.This is a feature service which provides Identify and Copy Feature capabilities. If fast-drawing at coarse zoom levels is a requirement, consider using the tile (map) service layer located at https://nifc.maps.arcgis.com/home/item.html?id=3b2c5daad00742cd9f9b676c09d03d13.OverviewThe Jurisdictional Agencies dataset is developed as a national land management geospatial layer, focused on representing wildland fire jurisdictional responsibility, for interagency wildland fire applications, including WFDSS (Wildland Fire Decision Support System), IFTDSS (Interagency Fuels Treatment Decision Support System), IRWIN (Interagency Reporting of Wildland Fire Information), and InFORM (Interagency Fire Occurrence Reporting Modules). It is intended to provide federal wildland fire jurisdictional boundaries on a national scale. The agency and unit names are an indication of the primary manager name and unit name, respectively, recognizing that:There may be multiple owner names.Jurisdiction may be held jointly by agencies at different levels of government (ie State and Local), especially on private lands, Some owner names may be blocked for security reasons.Some jurisdictions may not allow the distribution of owner names. Private ownerships are shown in this layer with JurisdictionalUnitIdentifier=null,JurisdictionalUnitAgency=null, JurisdictionalUnitKind=null, and LandownerKind="Private", LandownerCategory="Private". All land inside the US country boundary is covered by a polygon.Jurisdiction for privately owned land varies widely depending on state, county, or local laws and ordinances, fire workload, and other factors, and is not available in a national dataset in most cases.For publicly held lands the agency name is the surface managing agency, such as Bureau of Land Management, United States Forest Service, etc. The unit name refers to the descriptive name of the polygon (i.e. Northern California District, Boise National Forest, etc.).These data are used to automatically populate fields on the WFDSS Incident Information page.This data layer implements the NWCG Jurisdictional Unit Polygon Geospatial Data Layer Standard.Relevant NWCG Definitions and StandardsUnit2. A generic term that represents an organizational entity that only has meaning when it is contextualized by a descriptor, e.g. jurisdictional.Definition Extension: When referring to an organizational entity, a unit refers to the smallest area or lowest level. Higher levels of an organization (region, agency, department, etc) can be derived from a unit based on organization hierarchy.Unit, JurisdictionalThe governmental entity having overall land and resource management responsibility for a specific geographical area as provided by law.Definition Extension: 1) Ultimately responsible for the fire report to account for statistical fire occurrence; 2) Responsible for setting fire management objectives; 3) Jurisdiction cannot be re-assigned by agreement; 4) The nature and extent of the incident determines jurisdiction (for example, Wildfire vs. All Hazard); 5) Responsible for signing a Delegation of Authority to the Incident Commander.See also: Unit, Protecting; LandownerUnit IdentifierThis data standard specifies the standard format and rules for Unit Identifier, a code used within the wildland fire community to uniquely identify a particular government organizational unit.Landowner Kind & CategoryThis data standard provides a two-tier classification (kind and category) of landownership. Attribute Fields JurisdictionalAgencyKind Describes the type of unit Jurisdiction using the NWCG Landowner Kind data standard. There are two valid values: Federal, and Other. A value may not be populated for all polygons.JurisdictionalAgencyCategoryDescribes the type of unit Jurisdiction using the NWCG Landowner Category data standard. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State. A value may not be populated for all polygons.JurisdictionalUnitNameThe name of the Jurisdictional Unit. Where an NWCG Unit ID exists for a polygon, this is the name used in the Name field from the NWCG Unit ID database. Where no NWCG Unit ID exists, this is the “Unit Name” or other specific, descriptive unit name field from the source dataset. A value is populated for all polygons.JurisdictionalUnitIDWhere it could be determined, this is the NWCG Standard Unit Identifier (Unit ID). Where it is unknown, the value is ‘Null’. Null Unit IDs can occur because a unit may not have a Unit ID, or because one could not be reliably determined from the source data. Not every land ownership has an NWCG Unit ID. Unit ID assignment rules are available from the Unit ID standard, linked above.LandownerKindThe landowner category value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. There are three valid values: Federal, Private, or Other.LandownerCategoryThe landowner kind value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State, Private.DataSourceThe database from which the polygon originated. Be as specific as possible, identify the geodatabase name and feature class in which the polygon originated.SecondaryDataSourceIf the Data Source is an aggregation from other sources, use this field to specify the source that supplied data to the aggregation. For example, if Data Source is "PAD-US 2.1", then for a USDA Forest Service polygon, the Secondary Data Source would be "USDA FS Automated Lands Program (ALP)". For a BLM polygon in the same dataset, Secondary Source would be "Surface Management Agency (SMA)."SourceUniqueIDIdentifier (GUID or ObjectID) in the data source. Used to trace the polygon back to its authoritative source.MapMethod:Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality. MapMethod will be Mixed Method by default for this layer as the data are from mixed sources. Valid Values include: GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; DigitizedTopo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; Phone/Tablet; OtherDateCurrentThe last edit, update, of this GIS record. Date should follow the assigned NWCG Date Time data standard, using 24 hour clock, YYYY-MM-DDhh.mm.ssZ, ISO8601 Standard.CommentsAdditional information describing the feature. GeometryIDPrimary 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.JurisdictionalUnitID_sansUSNWCG Unit ID with the "US" characters removed from the beginning. Provided for backwards compatibility.JoinMethodAdditional information on how the polygon was matched information in the NWCG Unit ID database.LocalNameLocalName for the polygon provided from PADUS or other source.LegendJurisdictionalAgencyJurisdictional Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.LegendLandownerAgencyLandowner Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.DataSourceYearYear that the source data for the polygon were acquired.Data InputThis dataset is based on an aggregation of 4 spatial data sources: Protected Areas Database US (PAD-US 2.1), data from Bureau of Indian Affairs regional offices, the BLM Alaska Fire Service/State of Alaska, and Census Block-Group Geometry. NWCG Unit ID and Agency Kind/Category data are tabular and sourced from UnitIDActive.txt, in the WFMI Unit ID application (https://wfmi.nifc.gov/unit_id/Publish.html). Areas of with unknown Landowner Kind/Category and Jurisdictional Agency Kind/Category are assigned LandownerKind and LandownerCategory values of "Private" by use of the non-water polygons from the Census Block-Group geometry.PAD-US 2.1:This dataset is based in large part on the USGS Protected Areas Database of the United States - PAD-US 2.`. PAD-US is a compilation of authoritative protected areas data between agencies and organizations that ultimately results in a comprehensive and accurate inventory of protected areas for the United States to meet a variety of needs (e.g. conservation, recreation, public health, transportation, energy siting, ecological, or watershed assessments and planning). Extensive documentation on PAD-US processes and data sources is available.How these data were aggregated:Boundaries, and their descriptors, available in spatial databases (i.e. shapefiles or geodatabase feature classes) from land management agencies are the desired and primary data sources in PAD-US. If these authoritative sources are unavailable, or the agency recommends another source, data may be incorporated by other aggregators such as non-governmental organizations. Data sources are tracked for each record in the PAD-US geodatabase (see below).BIA and Tribal Data:BIA and Tribal land management data are not available in PAD-US. As such, data were aggregated from BIA regional offices. These data date from 2012 and were substantially updated in 2022. Indian Trust Land affiliated with Tribes, Reservations, or BIA Agencies: These data are not considered the system of record and are not intended to be used as such. The Bureau of Indian Affairs (BIA), Branch of Wildland Fire Management (BWFM) is not the originator of these data. The

Historical FiresLast updated on 06/17/2022OverviewThe 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 perimeters in 2021.https://nifc.maps.arcgis.com/home/item.html?id=098ebc8e561143389ca3d42be3707caaFWS -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 email

The Marine Mammal Surveys Mapping Application feature service provides access to data collected in the Mariana Archipelago by the Protected Species Division of the Pacific Island Fisheries Science Center. Included are 2010-2014 cetacean survey tracklines, species sighted, locations where biopsy samples were collected and locations for satellite tag deployments.

Athough MassGIS has served trails information from the Department of Conservation and Recreation (DCR) for many years, this new Trails layer is MassGIS’ first attempt at a statewide, multi-sourced dataset. This layer was created from two primary sources, DCR Trails and the Metropolitan Area Planning Council’s (MAPC) Trailmap. Additionally, a few other trail networks were added from OpenStreetMap (OSM), municipalities, and conservation organizations, but the amount of information from these sources is relatively small.This trails dataset was created for use in the State 9-1-1 Department’s mapping application Response Assist and is intended to assist telecommunicators with lost hikers as well as potentially responding to emergencies within remote areas. Because the layer is primarily being used by 9-1-1, it was decided to focus on those trails found in wilderness areas and used as hiking trails. This resulted in the omission of many arcs from the source data. Examples of these include cart paths on golf courses, the network of paved paths on school campuses, sidewalks, and many other arcs that could functionally serve as trails but were in relatively open and developed areas.Updated with linework from OpenStreetMap in summer 2023 and published on November 14, 2023.See full metadata.Map service also available.

This dataset provides soil active layer characteristics from nine locations across Alaska. Soil samples were collected in 2016 except for one site which was sampled in 2018. Soil cores were collected from each site using a steel barrel and plastic sample tube attached to a hand drill. At the majority of sites, samples were taken from each end of three 30-m transects (i.e. samples collected at the 0 m and 30 m location of each transect). The entire thawed horizon (active layer) was sampled where possible, and the length of cores varies among sites. Cores were kept frozen until analysis in the lab. Samples were sectioned by horizon (organic and mineral), and the organic horizon was split into subsections so that no section was longer than approximately 10 cm. Coarse roots were removed, dried and weighed. Soils were measured for gravimetric water content, percent soil organic matter (SOM), pH, and bulk density. Locations were selected to investigate fire disturbance, to span the range of permafrost regions from continuous to sporadic, and to cover vegetation types from boreal forests, tussock tundra, upland willow/herbaceous scrub, and lowland fen and wet tundra sites across Alaska. The data are provided in comma-separated values (CSV) format.

This layer contains information for locating past and present legal city boundaries within Los Angeles County. The Los Angeles County Department of Public Works provides the most current shapefiles representing city annexations and city boundaries on the Los Angeles County GIS Data Portal. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California. Numerous records are freely available at the Land Records Information website, hosted by the Department of Public Works.Principal Attributes:NO: The row number in the attribute table of the PDF Annexation Maps. (See Below)

ANNEX_No: These values are only used for the City of Los Angeles and Long Beach.

NAME: The official annexation name.

TYPE: Indicates the legal action.

A - represents an Annexation to that city. D - represents a Detachment from that city. V - is used to indicate the annexation was void or withdrawn before an effective date could be declared. 33 - Some older city annexation maps indicate a city boundary declared 'as of February 8, 1933'.

ANNEX_AREA: is the land area annexed or detached, in square miles, per the recorded legal description.

TOTAL_AREA: is the cumulative total land area for each city, arranged chronologically.

SHADE: is used by some of our cartographers to store the color used on printed maps.

INDEXNO: is a matching field used for retrieving documents from our department's document management system.

STATE (Secretary of State): Date filed with the Secretary of State. These are not available for earlier annexations and are Null.

COUNTY (County Recorder): Date filed with the County Recorder. These are not available for earlier annexations and are Null.

EFFECTIVE (Effective Date): The effective date of the annexation or detachment.

CITY: The city to which the annexation or detachment took place.

URL: This text field contains hyperlinks for viewing city annexation documents. See the ArcGIS Help for using the Hyperlink Tool.

FEAT_TYPE: contains the type of feature each polygon represents:

Land - Use this value for your definition query if you want to see only land features on your map. Pier - This value is used for polygons representing piers along the coastline. One example is the Santa Monica Pier. Breakwater - This value is used for polygons representing man-made barriers that protect the harbors. Water - This value is used for polygons representing navigable waters inside the harbors and marinas. 3NM Buffer - Per the Submerged Lands Act, the seaward boundaries of coastal cities and unincorporated county areas are three nautical miles from the coastline. (A nautical mile is 1,852 meters, or about 6,076 feet.) Annexation Maps by City (PDF)Large format, high quality wall maps are available for each of the 88 cities in Los Angeles County in PDF format.Agoura HillsHermosa BeachNorwalkAlhambraHidden HillsPalmdaleArcadiaHuntington ParkPalos Verdes EstatesArtesiaIndustryParamountAvalonInglewoodPasadenaAzusaIrwindalePico RiveraBaldwin ParkLa Canada FlintridgePomonaBellLa Habra HeightsRancho Palos VerdesBell GardensLa MiradaRedondo BeachBellflowerLa PuenteRolling HillsBeverly HillsLa VerneRolling Hills EstatesBradburyLakewoodRosemeadBurbankLancasterSan DimasCalabasasLawndaleSan FernandoCarsonLomitaSan GabrielCerritosLong BeachSan MarinoClaremontLos Angeles IndexSanta ClaritaCommerceLos Angeles Map 1Santa Fe SpringsComptonLos Angeles Map 2Santa MonicaCovinaLos Angeles Map 3Sierra MadreCudahyLos Angeles Map 4Signal HillCulver CityLos Angeles Map 5South El MonteDiamond BarLos Angeles Map 6South GateDowneyLos Angeles Map 7South PasadenaDuarteLos Angeles Map 8Temple CityEl MonteLynwoodTorranceEl SegundoMalibuVernonGardenaManhattan BeachWalnutGlendaleMaywoodWest CovinaGlendoraMonroviaWest HollywoodHawaiian GardensMontebelloWestlake VillageHawthorneMonterey ParkWhittier

Important Note: This item is in mature support as of September 2023 and will be retired in December 2025. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version.The USGS Protected Areas Database of the United States (PAD-US) is the official inventory of public parks and other protected open space. The spatial data in PAD-US represents public lands held in trust by thousands of national, state and regional/local governments, as well as non-profit conservation organizations.GAP 1 and 2 areas are primarily managed for biodiversity, GAP 3 are managed for multiple uses including conservation and extraction, GAP 4 no known mandate for biodiversity protection. Provides a general overview of protection status including management designations. PAD-US is published by the U.S. Geological Survey (USGS) Science Analytics and Synthesis (SAS), Gap Analysis Project (GAP). GAP produces data and tools that help meet critical national challenges such as biodiversity conservation, recreation, public health, climate change adaptation, and infrastructure investment. See the GAP webpage for more information about GAP and other GAP data including species and land cover.The USGS Protected Areas Database of the United States (PAD-US) classifies lands into four GAP Status classes:GAP Status 1 - Areas managed for biodiversity where natural disturbances are allowed to proceedGAP Status 2 - Areas managed for biodiversity where natural disturbance is suppressedGAP Status 3 - Areas protected from land cover conversion but subject to extractive uses such as logging and miningGAP Status 4 - Areas with no known mandate for protectionIn the United States, areas that are protected from development and managed for biodiversity conservation include Wilderness Areas, National Parks, National Wildlife Refuges, and Wild & Scenic Rivers. Understanding the geographic distribution of these protected areas and their level of protection is an important part of landscape-scale planning. Dataset SummaryPhenomenon Mapped: Areas protected from development and managed to maintain biodiversity Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, the US Virgin Islands, the Northern Mariana Islands and other Pacific Ocean IslandsVisible Scale: 1:1,000,000 and largerSource: USGS Science Analytics and Synthesis (SAS), Gap Analysis Project (GAP) PAD-US version 3.0Publication Date: July 2022Attributes included in this layer are: CategoryOwner TypeOwner NameLocal OwnerManager TypeManager NameLocal ManagerDesignation TypeLocal DesignationUnit NameLocal NameSourcePublic AccessGAP Status - Status 1, 2, or 3GAP Status DescriptionInternational Union for Conservation of Nature (IUCN) Description - I: Strict Nature Reserve, II: National Park, III: Natural Monument or Feature, IV: Habitat/Species Management Area, V: Protected Landscape/Seascape, VI: Protected area with sustainable use of natural resources, Other conservation area, UnassignedDate of EstablishmentThe source data for this layer are available here. What can you do with this Feature Layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. The layer or a map containing it can be used in an application.Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections and apply filters. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Change the layer’s style and filter the data. For example, you could set a filter for Gap Status Code = 3 to create a map of only the GAP Status 3 areas.Add labels and set their propertiesCustomize the pop-upArcGIS ProAdd this layer to a 2d or 3d map. The same scale limit as Online applies in ProUse as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class. Note that many features in the PAD-US database overlap. For example wilderness area designations overlap US Forest Service and other federal lands. Any analysis should take this into consideration. An imagery layer created from the same data set can be used for geoprocessing analysis with larger extents and eliminates some of the complications arising from overlapping polygons.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis 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.

Aiming at the problem that the SSD algorithm does not fully extract the feature information contained in each feature layer, as well as the feature information is easily lost during the sampling process, which makes the feature expression ineffective and leads to insufficient performance in small target detection. In this paper, AMT-SSD is proposed, a small target detection algorithm that incorporates the multi-branch stacking and new sampling transition module of the attention mechanism. In this algorithm, the composite attention mechanism is utilized to improve the correlation of features of the samples to be detected in terms of spatial and channels, and the efficiency of the algorithm; secondly, multi-branch stacking module is used to extract multi-size features for each feature layer, and different sizes of convolution kernels are utilized in parallel to fully extract their features and improve the expression of features; meanwhile, during the sampling process, the problem of missing features is solved by applying inverse subpixel convolution in the new sampling transition module. Experimentally, the AMT-SSD algorithm achieves 84.6% and 53.4% mAP metrics on the PASCAL VOC dataset and MS COCO dataset, respectively. This indicates that the AMT-SSD algorithm can effectively extract feature information that is beneficial to detection samples, and also performs well in reducing feature loss, which is effective for the algorithm to improve the algorithm on small targets.