In the United States, the federal government manages lands in significant parts of the country. These lands include 193 million acres managed by the US Forest Service in the nation's 154 National Forests and 20 National Grasslands, Bureau of Land Management lands that cover 247 million acres in Alaska and the Western United States, 150 million acres managed for wildlife conservation by the US Fish and Wildlife Service, 84 million acres of National Parks and other lands managed by the National Park Service and over 30 million acres managed by the Department of Defense. The Bureau of Reclamation manages a much smaller land base than the other agencies included in this layer but plays a critical role in managing the country's water resources.The agencies included in this layer are:Bureau of Land ManagementBureau of ReclamationDepartment of DefenseNational Park ServiceUS Fish and Wildlife ServiceUS Forest ServiceDataset SummaryPhenomenon Mapped: United States lands managed by six federal agencies Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana Islands. The layer also includes National Monuments and Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Visible Scale: The data is visible at all scales but draws best at scales greater than 1:2,000,000Source: BLM, DoD, USFS, USFWS, NPS, PADUS 2.1Publication Date: Various - Esri compiled and published this layer in May 2022. See individual agency views for data vintage.There are six layer views available that were created from this service. Each layer uses a filter to extract an individual agency from the service. For more information about the layer views or how to use them in your own project, follow these links:USA Bureau of Land Management LandsUSA Bureau of Reclamation LandsUSA Department of Defense LandsUSA National Park Service LandsUSA Fish and Wildlife Service LandsUSA Forest Service LandsWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "federal lands" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "federal lands" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shapefile or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

The US National Park Service manages 84.4 million acres that include the United States" 63 national parks, many national monuments, and other conservation and historical properties. These lands range from the 13 million acre Wrangell-St. Elias National Park and Preserve in Alaska to the 0.02 acre Thaddeus Kosciuszko National Memorial in Pennsylvania.Dataset SummaryPhenomenon Mapped: Administrative boundaries of U.S. National Park Service landsGeographic Extent: 50 United States, District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana IslandsData Coordinate System: WGS 1984Visible Scale: The data is visible at all scalesSource: NPS Administrative Boundaries of National Park System Units layerPublication Date: April, 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Park Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "national park service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "national park service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.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.

The U.S. Defense Department oversees the USA"s armed forces and manages over 30 million acres of land. With over 2.8 million service members and civilian employees the department is the world"s largest employer.Dataset SummaryPhenomenon Mapped: Lands managed by the U.S. Department of DefenseGeographic Extent: United States, Guam, Puerto RicoData Coordinate System: WGS 1984Visible Scale: The data is visible at all scalesSource: DOD Military Installations Ranges and Training Areas layer. Publication Date: May 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Department of Defense lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "department of defense" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "department of defense" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.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.

The US Forest Service manages 193 million acres including the nation's 154 National Forests and 20 National Grasslands. These lands provide a wide variety of recreational opportunities, protect sources of clean water, and supply timber and forage.Dataset SummaryPhenomenon Mapped: United States lands managed by the US Forest ServiceGeographic Extent: Contiguous United States, Alaska, and Puerto RicoVisible Scale: The data is visible at all scales.Source: USFS Surface Ownership ParcelsPublication Date: May 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Forest Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "forest service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "forest service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in ProThe data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage..This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.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.

Click to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site2/rest/services/Public_Forest_Practices/WADNR_PUBLIC_FP_Water_Type/MapServer/4For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The DNR Forest Practices Wetlands Geographic Information System (GIS) Layer is based on the National Wetlands Inventory (NWI). In cooperation with the Washington State Department of Ecology, DNR Forest Practices developed a systematic reclassification of the original USFWS wetlands codes into WAC 222-16-035 types. The reclassification was done in 1995 according to the Forest Practice Rules in place at the time. The WAC's for defining wetlands are 222-16-035 and 222-16-050.The DNR Forest Practices Wetlands Geographic Information System (GIS) Layer is based on the National Wetlands Inventory (NWI). In cooperation with the Washington State Department of Ecology, DNR Forest Practices developed a systematic reclassification of the original USFWS wetlands codes into WAC 222-16-035 types. The reclassification was done in 1995 according to the Forest Practice Rules in place at the time. The WAC's for defining wetlands are 222-16-035 and 222-16-050.It is intended that these data be only a first step in determining whether or not wetland issues have been or need to be addressed in an area. The DNR Forest Practices Division and the Department of Ecology strongly supports the additional use of hydric soils (from the GIS soils layer) to add weight to the call of 'wetland'. Reports from the Department of Ecology indicate that these data may substantially underestimate the extent of forested wetlands. Various studies show the NWI data is 25-80% accurate in forested areas. Most of these data were collected from stereopaired aerial photos at a scale of 1:58,000. The stated accuracy is that of a 1:24,000 map, or plus or minus 40 feet. In addition, some parts of the state have data that are 30 years old and only a small percentage have been field checked. Thus, for regulatory purposes, the user should not rely solely on these data. On-the-ground checking must accompany any regulatory call based on these data.The reclassification is based on the USFWS FWS_CODE. The FWS_CODE is a concatenation of three subcomponents: Wetland system, class, and water regime. Forest Practices further divided the components into system, subsystem, class, subclass, water regime, special modifiers, xclass, subxclass, and xsystem. The last three items (xsomething) are for wetland areas which do not easily lend themselves to one class alone. The resulting classification system uses two fields: WLND_CLASS and WLND_TYPE. WLND_CLASS indicates whether the polygon is a forested wetland (F), open water (O), or a vegetated wetland (W). WLND_TYPE, indicates whether the wetland is a type A (1), type B (2), or a generic wetland (3) that doesn't fit the categories for A or B type wetlands. WLND_TYPE = 0 (zero) is used where WLND_CLASS = O (letter "O").

The wetland polygon is classified as F, forested wetland; O, open water; or W, vegetated wetland depending on the following FWS_CODE categories: F O W --------------------------------------------------- Forested Open Vegetated Wetland Water Wetland --------------------------------------------PFO* POW PUB5 E2FO PRB* PML2 PUB1-4 PEM* PAB* L2US5 PUS1-4 L2EM2 PFL* PSS* L1RB* PML1 L1UB*
L1AB* L1OW L2RB* L2UB* L2AB* L2RS* L2US1-4 L2OW

• indicates inclusion of the subcategory (ie. PEM* includes PEM1F, PEM1FB, etc.).

DNR FOREST PRACTICES WETLANDS DATASET ON FPARS Internet Mapping Website: The FPARS Resource Map and Water Type Map display Forested, Type A, Type B, and "other" wetlands. Open water polygons are not displayed on the FPARS Resource Map and Water Type Map in an attempt to minimize clutter. The following code combinations are found in the DNR Forest Practices wetlands dataset:

WLND_CLASS WLND_TYPE wetland polygon classification F 3 Forested wetland as defined in WAC 222-16-035 O 0 *NWI open water (not displayed on FPARS Resource or Water Type Maps) W 1 Type A Wetland as defined in WAC 222-16-035 W 2 Type B Wetland as defined in WAC 222-16-035 W 3 other wetland

• NWI open water polygons are indicated by WLND_CLASS = O and WLND_TYPE = 0. Open water is used in the USFWS and WAC 222-16-035 classification system. These open water polygons are not included in the FPARS Resource Map and Water Type Map views of this dataset in an attempt to minimize clutter on the FPARS maps.

Soil is the foundation of life on earth. More living things by weight live in the soil than upon it. It determines what crops we can grow, what structures we can build, what forests can take root.This layer contains the physical soil variable percent clay (clay).Within the subset of soil that is smaller than 2mm in size, also known as the fine earth portion, clay is defined as particles that are smaller than 0.002mm, making them only visible in an electron microscope. Clay soils contain low amounts of air, and water drains through them very slowly.This layer is a general, medium scale global predictive soil layer suitable for global mapping and decision support. In many places samples of soils do not exist so this map represents a prediction of what is most likely in that location. The predictions are made in six depth ranges by soilgrids.org, funded by ISRIC based in Wageningen, Netherlands.Each 250m pixel contains a value predicted for that area by soilgrids.org from best available data worldwide. Data for percent clay are provided at six depth ranges from the surface to 2 meters below the surface. Each variable and depth range may be accessed in the layer's multidimensional properties.Dataset SummaryPhenomenon Mapped: Proportion of clay particles (< 0.002 mm) in the fine earth fraction in g/100g (%)Cell Size: 250 metersPixel Type: 32 bit float, converted from online data that is 16 Bit Unsigned IntegerCoordinate System: Web Mercator Auxiliary Sphere, projected via nearest neighbor from goode's homolosine land (250m)Extent: World land area except AntarcticaVisible Scale: All scales are visibleNumber of Columns and Rows: 160300, 100498Source: Soilgrids.orgPublication Date: May 2020Data from the soilgrids.org mean predictions for clay were used to create this layer. You may access the percent clay in one of six depth ranges. To select one choose the depth variable in the multidimensional selector in your map client.Mean depth (cm)Actual depth range of data-2.50-5cm depth range-105-15cm depth range-22.515-30cm depth range-4530-60cm depth range-8060-100cm depth range-150100-200cm depth rangeWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map: In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "world soils soilgrids" in the search box and browse to the layer. Select the layer then click Add to Map. In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "world soils soilgrids" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions or create your own to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.Online you can filter the layer to show subsets of the data using the filter button and the layer's built-in raster functions.This layer is part of the Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.More information about soilgrids layersAnswers to many questions may be found at soilgrids.org (ISRIC) frequently asked questions (faq) page about the data.To make this layer, Esri reprojected the expected value of ISRIC soil grids from soilgrids' source projection (goode's land WKID 54052) to web mercator projection, nearest neighbor, to facilitate online mapping. The resolution in web mercator projection is the same as the original projection, 250m. But keep in mind that the original dataset has been reprojected to make this web mercator version.This multidimensional soil collection serves the mean or expected value for each soil variable as calculated by soilgrids.org. For all other distributions of the soil variable, be sure to download the data directly from soilgrids.org. The data are available in VRT format and may be converted to other image formats within ArcGIS Pro.Accessing this layer's companion uncertainty layerBecause data quality varies worldwide, the uncertainty of the predicted value varies worldwide. A companion uncertainty layer exists for this layer which you can use to qualify the values you see in this map for analysis. Choose a variable and depth in the multidimensional settings of your map client to access the companion uncertainty layer.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Purpose: This is the 2019 Hurricanes Crowdsourced Photos Public Feature Layer View. This is a live publicly accessible layer for the Crowdsource Story Map accessible here: This layer cannot be edited, it is view only. ShareHidden Field: 0 = Needs Review, 1 = Already Reviewed, 2 = Hidden (not available in this public view).Audience: GIS Staff and Technologists who would like to add this layer to their own web maps and apps. If you need access to this layer in other formats, see the Open Data link. Please send us an email at triage@publicsafetygis.org to tell us if you are going to use this layer and if you have any questions or need assistance with this layer.Need to download the photos? See this technical support article.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

This feature layer provides access to OpenStreetMap (OSM) buildings data for Africa, which is updated every 1 minute with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM polygon (closed way) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. This feature layer view includes building features defined as a query against the hosted feature layer (i.e. building is not blank).In OSM, a building is a man-made structure with a roof, standing more or less permanently in one place. These features are identified with a building tag. There are thousands of different tag values for building used in the OSM database. In this feature layer, unique symbols are used for several of the most popular building types, while lesser used types are grouped in an "other" category.Zoom in to large scales (e.g. Streets level or 1:10k scale) to see the building features display. You can click on a feature to get the name of the building (if available). The name of the building will display by default at large scales (e.g. Street level of 1:5k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this buildings layer displaying just one or two building types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. building is apartments), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers (e.g. parks) that are ready to use, but not for every type of building.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.

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

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpageunder LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherSalt Lake County Tax Exempt codes below:AE - Airport - ExemptCC - Commercial Common AreaCE - Conservation EasementCM - CemeteryEC - Exempt CharitableEE - Exempt EducationER - Exempt ReligiousGB - GreenbeltHE - Homeowners Assoc ExemptIL - In LieuIR - Irrigation CompanyMC - Master CardOE - Owner ExemptPE - Part ExemptPR - Pro-RatedPT - Privilege TaxPY - Privilege Tax on a YieldSA - State AssessedSC - State and Cnty AssessedSE - Special - ExemptSU - Salt Lake - Utah CntyTD - Divided Tax DistrictUI - Undivided_Interest TAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialSalt Lake County Property Class codes below:R - Residential / CondoC - CommercialI - IndustrialRE - RecreationalA - AgriculturalMH - Multi HousingMore information about the PROP_CLASS and PROP_TYPE for Salt Lake County can be found at http://slco.org/assessor/new/queryproptyp.cfmPROP_TYPE (expected) Text 100 - Single Family Res.,Townhome, CondoPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Soil is the foundation of life on earth. More living things by weight live in the soil than upon it. It determines what crops we can grow, what structures we can build, what forests can take root.This layer contains the chemical soil variable nitrogen (nitrogen).Nitrogen is an essential nutrient for sustaining life on Earth. Nitrogen is a core component of amino acids, which are the building blocks of proteins, and of nucleic acids, which are the building blocks of genetic material (RNA and DNA).This layer is a general, medium scale global predictive soil layer suitable for global mapping and decision support. In many places samples of soils do not exist so this map represents a prediction of what is most likely in that location. The predictions are made in six depth ranges by soilgrids.org, funded by ISRIC based in Wageningen, Netherlands.Each 250m pixel contains a value predicted for that area by soilgrids.org from best available data worldwide. Data for nitrogen are provided at six depth ranges from the surface to 2 meters below the surface. Each variable and depth range may be accessed in the layer's multidimensional properties.Dataset SummaryPhenomenon Mapped: Total nitrogen (N) in g/kgCell Size: 250 metersPixel Type: 32 bit float, converted from online data that is 16 Bit Unsigned IntegerCoordinate System: Web Mercator Auxiliary Sphere, projected via nearest neighbor from goode's homolosine land (250m)Extent: World land area except AntarcticaVisible Scale: All scales are visibleNumber of Columns and Rows: 160300, 100498Source: Soilgrids.orgPublication Date: May 2020Data from the soilgrids.org mean predictions for nitrogen were used to create this layer. You may access nitrogen values in one of six depth ranges. To select one choose the depth variable in the multidimensional selector in your map client.Mean depth (cm)Actual depth range of data-2.50-5cm depth range-105-15cm depth range-22.515-30cm depth range-4530-60cm depth range-8060-100cm depth range-150100-200cm depth rangeWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map: In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "world soils soilgrids" in the search box and browse to the layer. Select the layer then click Add to Map. In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "world soils soilgrids" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions or create your own to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.Online you can filter the layer to show subsets of the data using the filter button and the layer's built-in raster functions.This layer is part of the Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.More information about soilgrids layersAnswers to many questions may be found at soilgrids.org (ISRIC) frequently asked questions (faq) page about the data.To make this layer, Esri reprojected the expected value of ISRIC soil grids from soilgrids' source projection (goode's land WKID 54052) to web mercator projection, nearest neighbor, to facilitate online mapping. The resolution in web mercator projection is the same as the original projection, 250m. But keep in mind that the original dataset has been reprojected to make this web mercator version.This multidimensional soil collection serves the mean or expected value for each soil variable as calculated by soilgrids.org. For all other distributions of the soil variable, be sure to download the data directly from soilgrids.org. The data are available in VRT format and may be converted to other image formats within ArcGIS Pro.Accessing this layer's companion uncertainty layerBecause data quality varies worldwide, the uncertainty of the predicted value varies worldwide. A companion uncertainty layer exists for this layer which you can use to qualify the values you see in this map for analysis. Choose a variable and depth in the multidimensional settings of your map client to access the companion uncertainty layer.

The US Fish and Wildlife Service manages the United States" 573 National Wildlife Refuges and thousands of small wetlands and other special management areas. These lands cover more than 150 million acres that protect fish, wildlife, plants, and their habitats.Dataset SummaryPhenomenon Mapped: United States lands managed by the US Fish and Wildlife ServiceGeographic Extent: 50 United States plus Puerto Rico, the US Virgin Islands, Guam, and the Northern Mariana Islands. The layer also includes Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Data Coordinate System: WGS 1984Visible Scale: The data is visible at all scales.Source: USFWS Interest Simplified layerPublication Date: January 2024This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Fish and Wildlife Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "fish and wildlife service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "fish and wildlife service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.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.

Purpose: This is an ArcGIS Pro template that GIS Specialists can use to identify vulnerable populations and special needs infrastructure most at risk to flooding events.How does it work?Determine and understand the Place Vulnerability (based on Cutter et al. 1997) and the Special Needs Infrastructure for an area of interest based on Special Flood Hazard Zones, Social Vulnerability Index, and the distribution of its Population and Housing units. The final product will be charts of the data distribution and a Hosted Feature Layer. See this Story Map example for a more detailed explanation.This uses the FEMA National Flood Hazard Layer as an input (although you can substitute your own flood hazard data), check availability for your County before beginning the Task: FEMA NFHL ViewerThe solution consists of several tasks that allow you to:Select an area of interest for your Place Vulnerability Analysis. Select a Hazard that may occur within your area of interest.Select the Social Vulnerability Index (SVI) features contained within your area of interest using the CDC’s Social Vulnerability Index (SVI) – 2016 overall SVI layer at the census tract level in the map.Determine and understand the Social Vulnerability Index for the hazard zones identified within you area of interest.Identify the Special Needs Infrastructure features located within the hazard zones identified within you area of interest.Share your data to ArcGIS Online as a Hosted Feature Layer.FIRST STEPS:Create a folder C:\GIS\ if you do not already have this folder created. (This is a suggested step as the ArcGIS Pro Tasks does not appear to keep relative paths)Download the ZIP file.Extract the ZIP file and save it to the C:\GIS\ location on your computer. Open the PlaceVulnerabilityAnalysis.aprx file.Once the Project file (.aprx) opens, we suggest the following setup to easily view the Tasks instructions, the Map and its Contents, and the Databases (.gdb) from the Catalog pane.The following public web map is included as a Template in the ArcGIS Pro solution file: Place Vulnerability Template Web MapNote 1:As this is a beta version, please take note of some pain points:Data input and output locations may need to be manually populated from the related workspaces (.gdb) or the tools may fail to run. Make sure to unzip/extract the file to the C:\GIS\ location on your computer to avoid issues.Switching from one step to the next may not be totally seamless yet.If you are experiencing any issues with the Flood Hazard Zones service provided, or if the data is not available for your area of interest, you can also download your Flood Hazard Zones data from the FEMA Flood Map Service Center. In the search, use the FEMA ID. Once downloaded, save the data in your project folder and use it as an input.Note 2:In this task, the default hazard being used are the National Flood Hazard Zones. If you would like to use a different hazard, you will need to add the new hazard layer to the map and update all query expressions accordingly.For questions, bug reports, or new requirements contact pdoherty@publicsafetygis.org

Soil is the foundation of life on earth. More living things by weight live in the soil than upon it. It determines what crops we can grow, what structures we can build, what forests can take root.This layer contains the chemical soil variable organic carbon density (ocd) which measures carbon mass in proportion to volume of soil (mass divided by volume.)From Agriculture Victoria: Soil carbon provides a source of nutrients through mineralisation, helps to aggregate soil particles (structure) to provide resilience to physical degradation, increases microbial activity, increases water storage and availability to plants, and protects soil from erosion.This layer is a general, medium scale global predictive soil layer suitable for global mapping and decision support. In many places samples of soils do not exist so this map represents a prediction of what is most likely in that location. The predictions are made in six depth ranges by soilgrids.org, funded by ISRIC based in Wageningen, Netherlands.Each 250m pixel contains a value predicted for that area by soilgrids.org from best available data worldwide. Data for organic carbon density are provided at six depth ranges from the surface to 2 meters below the surface. Each variable and depth range may be accessed in the layer's multidimensional properties.Dataset SummaryPhenomenon Mapped: Organic carbon density in kg/m³Cell Size: 250 metersPixel Type: 32 bit float, converted from online data that is 16 Bit Unsigned IntegerCoordinate System: Web Mercator Auxiliary Sphere, projected via nearest neighbor from goode's homolosine land (250m)Extent: World land area except AntarcticaVisible Scale: All scales are visibleNumber of Columns and Rows: 160300, 100498Source: Soilgrids.orgPublication Date: May 2020Data from the soilgrids.org mean predictions for ocd were used to create this layer. You may access organic carbon density values in one of six depth ranges. To select one choose the depth variable in the multidimensional selector in your map client.Mean depth (cm)Actual depth range of data-2.50-5cm depth range-105-15cm depth range-22.515-30cm depth range-4530-60cm depth range-8060-100cm depth range-150100-200cm depth rangeWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map: In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "world soils soilgrids" in the search box and browse to the layer. Select the layer then click Add to Map. In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "world soils soilgrids" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions or create your own to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.Online you can filter the layer to show subsets of the data using the filter button and the layer's built-in raster functions.This layer is part of the Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.More information about soilgrids layersAnswers to many questions may be found at soilgrids.org (ISRIC) frequently asked questions (faq) page about the data.To make this layer, Esri reprojected the expected value of ISRIC soil grids from soilgrids' source projection (goode's land WKID 54052) to web mercator projection, nearest neighbor, to facilitate online mapping. The resolution in web mercator projection is the same as the original projection, 250m. But keep in mind that the original dataset has been reprojected to make this web mercator version.This multidimensional soil collection serves the mean or expected value for each soil variable as calculated by soilgrids.org. For all other distributions of the soil variable, be sure to download the data directly from soilgrids.org. The data are available in VRT format and may be converted to other image formats within ArcGIS Pro.Accessing this layer's companion uncertainty layerBecause data quality varies worldwide, the uncertainty of the predicted value varies worldwide. A companion uncertainty layer exists for this layer which you can use to qualify the values you see in this map for analysis. Choose a variable and depth in the multidimensional settings of your map client to access the companion uncertainty layer.

The gSSURGO dataset provides detailed soil survey mapping in raster format with ready-to-map attributes organized in statewide tiles for desktop GIS. gSSURGO is derived from the official Soil Survey Geographic (SSURGO) Database. SSURGO generally has the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes and are derived from properties and characteristics stored in the National Soil Information System (NASIS).

The gSSURGO data were prepared by merging the traditional vector-based SSURGO digital map data and tabular data into statewide extents, adding a statewide gridded map layer derived from the vector layer, and adding a new value-added look up table (valu) containing ready-to-map attributes. The gridded map layer is in an ArcGIS file geodatabase in raster format, thus it has the capacity to store significantly more data and greater spatial extents than the traditional SSURGO product. The raster map data have a 10-meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link the raster cells and polygons to attribute tables.

For more information, see the gSSURGO webpage: https://www.nrcs.usda.gov/resources/data-and-reports/description-of-gridded-soil-survey-geographic-gssurgo-database

One-eighth of the United States (247.3 million acres) is managed by the Bureau of Land Management. As part of the Department of the Interior, the agency oversees the 30 million acre National Landscape Conservation System, a collection of lands that includes 221 wilderness areas, 23 national monuments and 636 other protected areas. Bureau of Land Management Lands contain over 63,000 oil and gas wells and provide forage for over 18,000 grazing permit holders on 155 million acres of land. Dataset SummaryPhenomenon Mapped: United States lands managed by the Bureau of Land ManagementGeographic Extent: Contiguous United States and AlaskaData Coordinate System: WGS 1984Visible Scale: The data is visible at all scales but draws best at scales larger than 1:2,000,000.Source: BLM Surface Management Agency layer, Rasterized by Esri from features May 2025.Publication Date: December 2024This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Bureau of Land Management lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "bureau of land management" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "bureau of land management" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.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.

This feature layer provides access to OpenStreetMap (OSM) shops data for Asia, which is updated every 5 minutes with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM point (node) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. This feature layer view includes shop features defined as a query against the hosted feature layer (i.e. shop is not blank).In OSM, a shop is a place selling retail products or services, such as a supermarket, bakery, or florist. These features are identified with a shop tag. There are thousands of different tag values for shop used in the OSM database. In this feature layer, unique symbols are used for several of the most popular shop types, while lesser used types are grouped in an "other" category.Zoom in to large scales (e.g. Neighborhood level or 1:80k scale) to see the shop features display. You can click on the feature to get the name of the shop. The name of the shop will display by default at very large scales (e.g. Building level of 1:2k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this shop layer displaying just one or two shop types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. shop is jewelry), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers (e.g. supermarket or convenience shop) that are ready to use, but not for every type of shop.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.