Important Note: This item is in mature support as of February 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. This layer displays change in pixels of the Sentinel-2 10m Land Use/Land Cover product developed by Esri, Impact Observatory, and Microsoft. Available years to compare with 2021 are 2018, 2019 and 2020. By default, the layer shows all comparisons together, in effect showing what changed 2018-2021. But the layer may be changed to show one of three specific pairs of years, 2018-2021, 2019-2021, or 2020-2021.Showing just one pair of years in ArcGIS Online Map ViewerTo show just one pair of years in ArcGIS Online Map viewer, create a filter. 1. Click the filter button. 2. Next, click add expression. 3. In the expression dialogue, specify a pair of years with the ProductName attribute. Use the following example in your expression dialogue to show only places that changed between 2020 and 2021:ProductNameis2020-2021By default, places that do not change appear as a transparent symbol in ArcGIS Pro. But in ArcGIS Online Map Viewer, a transparent symbol may need to be set for these places after a filter is chosen. To do this:4. Click the styles button. 5. Under unique values click style options. 6. Click the symbol next to No Change at the bottom of the legend. 7. Click the slider next to "enable fill" to turn the symbol off.Showing just one pair of years in ArcGIS ProTo show just one pair of years in ArcGIS Pro, choose one of the layer's processing templates to single out a particular pair of years. The processing template applies a definition query that works in ArcGIS Pro. 1. To choose a processing template, right click the layer in the table of contents for ArcGIS Pro and choose properties. 2. In the dialogue that comes up, choose the tab that says processing templates. 3. On the right where it says processing template, choose the pair of years you would like to display. The processing template will stay applied for any analysis you may want to perform as well.How the change layer was created, combining LULC classes from two yearsImpact Observatory, Esri, and Microsoft used artificial intelligence to classify the world in 10 Land Use/Land Cover (LULC) classes for the years 2017-2021. Mosaics serve the following sets of change rasters in a single global layer: Change between 2018 and 2021Change between 2019 and 2021Change between 2020 and 2021To make this change layer, Esri used an arithmetic operation combining the cells from a source year and 2021 to make a change index value. ((from year * 16) + to year) In the example of the change between 2020 and 2021, the from year (2020) was multiplied by 16, then added to the to year (2021). Then the combined number is served as an index in an 8 bit unsigned mosaic with an attribute table which describes what changed or did not change in that timeframe. Variable mapped: Change in land cover between 2018, 2019, or 2020 and 2021 Data Projection: Universal Transverse Mercator (UTM)Mosaic Projection: WGS84Extent: GlobalSource imagery: Sentinel-2Cell Size: 10m (0.00008983152098239751 degrees)Type: ThematicSource: Esri Inc.Publication date: January 2022What can you do with this layer?Global LULC maps provide information on conservation planning, food security, and hydrologic modeling, among other things. This dataset can be used to visualize land cover anywhere on Earth. This layer can also be used in analyses that require land cover input. For example, the Zonal Statistics tools allow a user to understand the composition of a specified area by reporting the total estimates for each of the classes. Land Cover processingThis map was produced by a deep learning model trained using over 5 billion hand-labeled Sentinel-2 pixels, sampled from over 20,000 sites distributed across all major biomes of the world. The underlying deep learning model uses 6 bands of Sentinel-2 surface reflectance data: visible blue, green, red, near infrared, and two shortwave infrared bands. To create the final map, the model is run on multiple dates of imagery throughout the year, and the outputs are composited into a final representative map. Processing platformSentinel-2 L2A/B data was accessed via Microsoft’s Planetary Computer and scaled using Microsoft Azure Batch.Class definitions1. WaterAreas where water was predominantly present throughout the year; may not cover areas with sporadic or ephemeral water; contains little to no sparse vegetation, no rock outcrop nor built up features like docks; examples: rivers, ponds, lakes, oceans, flooded salt plains.2. TreesAny significant clustering of tall (~15-m or higher) dense vegetation, typically with a closed or dense canopy; examples: wooded vegetation,
clusters of dense tall vegetation within savannas, plantations, swamp or mangroves (dense/tall vegetation with ephemeral water or canopy too thick to detect water underneath).4. Flooded vegetationAreas of any type of vegetation with obvious intermixing of water throughout a majority of the year; seasonally flooded area that is a mix of grass/shrub/trees/bare ground; examples: flooded mangroves, emergent vegetation, rice paddies and other heavily irrigated and inundated agriculture.5. CropsHuman planted/plotted cereals, grasses, and crops not at tree height; examples: corn, wheat, soy, fallow plots of structured land.7. Built AreaHuman made structures; major road and rail networks; large homogenous impervious surfaces including parking structures, office buildings and residential housing; examples: houses, dense villages / towns / cities, paved roads, asphalt.8. Bare groundAreas of rock or soil with very sparse to no vegetation for the entire year; large areas of sand and deserts with no to little vegetation; examples: exposed rock or soil, desert and sand dunes, dry salt flats/pans, dried lake beds, mines.9. Snow/IceLarge homogenous areas of permanent snow or ice, typically only in mountain areas or highest latitudes; examples: glaciers, permanent snowpack, snow fields. 10. CloudsNo land cover information due to persistent cloud cover.11. Rangeland Open areas covered in homogenous grasses with little to no taller vegetation; wild cereals and grasses with no obvious human plotting (i.e., not a plotted field); examples: natural meadows and fields with sparse to no tree cover, open savanna with few to no trees, parks/golf courses/lawns, pastures. Mix of small clusters of plants or single plants dispersed on a landscape that shows exposed soil or rock; scrub-filled clearings within dense forests that are clearly not taller than trees; examples: moderate to sparse cover of bushes, shrubs and tufts of grass, savannas with very sparse grasses, trees or other plants.CitationKarra, Kontgis, et al. “Global land use/land cover with Sentinel-2 and deep learning.” IGARSS 2021-2021 IEEE International Geoscience and Remote Sensing Symposium. IEEE, 2021.AcknowledgementsTraining data for this project makes use of the National Geographic Society Dynamic World training dataset, produced for the Dynamic World Project by National Geographic Society in partnership with Google and the World Resources Institute.For questions please email environment@esri.com

These data depict the western United States Map Unit areas as defined by the USDA NRCS. Each Map Unit area contains information on a variety of soil properties and interpretations. The raster is to be joined to the .csv file by the field "mukey." We keep the raster and csv separate to preserve the full attribute names in the csv that would be truncated if attached to the raster. Once joined, the raster can be classified or analyzed by the columns which depict the properties and interpretations. It is important to note that each property has a corresponding component percent column to indicate how much of the map unit has the dominant property provided. For example, if the property "AASHTO Group Classification (Surface) 0 to 1cm" is recorded as "A-1" for a map unit, a user should also refer to the component percent field for this property (in this case 75). This means that an estimated 75% of the map unit has a "A-1" AASHTO group classification and that "A-1" is the dominant group. The property in the column is the dominant component, and so the other 25% of this map unit is comprised of other AASHTO Group Classifications. This raster attribute table was generated from the "Map Soil Properties and Interpretations" tool within the gSSURGO Mapping Toolset in the Soil Data Management Toolbox for ArcGIS™ User Guide Version 4.0 (https://www.nrcs.usda.gov/wps/PA_NRCSConsumption/download?cid=nrcseprd362255&ext=pdf) from GSSURGO that used their Map Unit Raster as the input feature (https://gdg.sc.egov.usda.gov/). The FY2018 Gridded SSURGO Map Unit Raster was created for use in national, regional, and state-wide resource planning and analysis of soils data. These data were created with guidance from the USDA NRCS. The fields named "*COMPPCT_R" can exceed 100% for some map units. The NRCS personnel are aware of and working on fixing this issue. Take caution when interpreting these areas, as they are the result of some data duplication in the master gSSURGO database. The data are considered valuable and required for timely science needs, and thus are released with this known error. The USDA NRCS are developing a data release which will replace this item when it is available. For the most up to date ssurgo releases that do not include the custom fields as this release does, see https://www.nrcs.usda.gov/wps/portal/nrcs/detail/soils/home/?cid=nrcs142p2_053628#tools For additional definitions, see https://www.nrcs.usda.gov/wps/portal/nrcs/detail/soils/survey/geo/?cid=nrcs142p2_053627.

This layer displays change in pixels of the Sentinel-2 10m Land Use/Land Cover product developed by Esri, Impact Observatory, and Microsoft. Available years to compare with 2021 are 2018, 2019 and 2020.By default, the layer shows all comparisons together, in effect showing what changed 2018-2021. But the layer may be changed to show one of three specific pairs of years, 2018-2021, 2019-2021, or 2020-2021.Showing just one pair of years in ArcGIS Online Map ViewerTo show just one pair of years in ArcGIS Online Map viewer, create a filter.1. Click the filter button.2. Next, click add expression.3. In the expression dialogue, specify a pair of years with the ProductName attribute. Use the following example in your expression dialogue to show only places that changed between 2020 and 2021:ProductNameis2020-2021By default, places that do not change appear as a transparent symbol in ArcGIS Pro. But in ArcGIS Online Map Viewer, a transparent symbol may need to be set for these places after a filter is chosen. To do this:4. Click the styles button.5. Under unique values click style options.6. Click the symbol next to No Change at the bottom of the legend.7. Click the slider next to "enable fill" to turn the symbol off.Showing just one pair of years in ArcGIS ProTo show just one pair of years in ArcGIS Pro, choose one of the layer's processing templates to single out a particular pair of years. The processing template applies a definition query that works in ArcGIS Pro.1. To choose a processing template, right click the layer in the table of contents for ArcGIS Pro and choose properties.2. In the dialogue that comes up, choose the tab that says processing templates.3. On the right where it says processing template, choose the pair of years you would like to display.The processing template will stay applied for any analysis you may want to perform as well.How the change layer was created, combining LULC classes from two yearsImpact Observatory, Esri, and Microsoft used artificial intelligence to classify the world in 10 Land Use/Land Cover (LULC) classes for the years 2017-2021. Mosaics serve the following sets of change rasters in a single global layer:Change between 2018 and 2021Change between 2019 and 2021Change between 2020 and 2021To make this change layer, Esri used an arithmetic operation combining the cells from a source year and 2021 to make a change index value. ((from year * 16) + to year) In the example of the change between 2020 and 2021, the from year (2020) was multiplied by 16, then added to the to year (2021). Then the combined number is served as an index in an 8 bit unsigned mosaic with an attribute table which describes what changed or did not change in that timeframe.Variable mapped: Change in land cover between 2018, 2019, or 2020 and 2021Data Projection: Universal Transverse Mercator (UTM)Mosaic Projection: WGS84Extent: GlobalSource imagery: Sentinel-2Cell Size: 10m (0.00008983152098239751 degrees)Type: ThematicSource: Esri Inc.Publication date: January 2022What can you do with this layer?Global LULC maps provide information on conservation planning, food security, and hydrologic modeling, among other things. This dataset can be used to visualize land cover anywhere on Earth. This layer can also be used in analyses that require land cover input. For example, the Zonal Statistics tools allow a user to understand the composition of a specified area by reporting the total estimates for each of the classes.Land Cover processingThis map was produced by a deep learning model trained using over 5 billion hand-labeled Sentinel-2 pixels, sampled from over 20,000 sites distributed across all major biomes of the world. The underlying deep learning model uses 6 bands of Sentinel-2 surface reflectance data: visible blue, green, red, near infrared, and two shortwave infrared bands. To create the final map, the model is run on multiple dates of imagery throughout the year, and the outputs are composited into a final representative map.Processing platformSentinel-2 L2A/B data was accessed via Microsoft’s Planetary Computer and scaled using Microsoft Azure Batch.Class definitions1. WaterAreas where water was predominantly present throughout the year; may not cover areas with sporadic or ephemeral water; contains little to no sparse vegetation, no rock outcrop nor built up features like docks; examples: rivers, ponds, lakes, oceans, flooded salt plains.2. TreesAny significant clustering of tall (~15-m or higher) dense vegetation, typically with a closed or dense canopy; examples: wooded vegetation, clusters of dense tall vegetation within savannas, plantations, swamp or mangroves (dense/tall vegetation with ephemeral water or canopy too thick to detect water underneath).4. Flooded vegetationAreas of any type of vegetation with obvious intermixing of water throughout a majority of the year; seasonally flooded area that is a mix of grass/shrub/trees/bare ground; examples: flooded mangroves, emergent vegetation, rice paddies and other heavily irrigated and inundated agriculture.5. CropsHuman planted/plotted cereals, grasses, and crops not at tree height; examples: corn, wheat, soy, fallow plots of structured land.7. Built AreaHuman made structures; major road and rail networks; large homogenous impervious surfaces including parking structures, office buildings and residential housing; examples: houses, dense villages / towns / cities, paved roads, asphalt.8. Bare groundAreas of rock or soil with very sparse to no vegetation for the entire year; large areas of sand and deserts with no to little vegetation; examples: exposed rock or soil, desert and sand dunes, dry salt flats/pans, dried lake beds, mines.9. Snow/IceLarge homogenous areas of permanent snow or ice, typically only in mountain areas or highest latitudes; examples: glaciers, permanent snowpack, snow fields. 10. CloudsNo land cover information due to persistent cloud cover.11. RangelandOpen areas covered in homogenous grasses with little to no taller vegetation; wild cereals and grasses with no obvious human plotting (i.e., not a plotted field); examples: natural meadows and fields with sparse to no tree cover, open savanna with few to no trees, parks/golf courses/lawns, pastures. Mix of small clusters of plants or single plants dispersed on a landscape that shows exposed soil or rock; scrub-filled clearings within dense forests that are clearly not taller than trees; examples: moderate to sparse cover of bushes, shrubs and tufts of grass, savannas with very sparse grasses, trees or other plants.CitationKarra, Kontgis, et al. “Global land use/land cover with Sentinel-2 and deep learning.” IGARSS 2021-2021 IEEE International Geoscience and Remote Sensing Symposium. IEEE, 2021.AcknowledgementsTraining data for this project makes use of the National Geographic Society Dynamic World training dataset, produced for the Dynamic World Project by National Geographic Society in partnership with Google and the World Resources Institute.For questions please email environment@esri.com

This application provides users with detailed information on hunting opportunities available on Department of Conservation and Recreation (DCR), Division of Water Supply Protection (DWSP) land in central Massachusetts. This is comprised of multiple pages that provide information (as text) and two interactive maps. The first interactive map is the Hunting Map, which provides all of the information a hunter might need to plan a successful hunt. The information in this map provides a comprehensive look at where hunting is allowed, the permits required, and the locations of features like fields and stone walls (and more!). The second interactive map is the Harvest Map, which provides hunters with information on deer harvested as part of the Quabbin Controlled Deer Hunts since 2010; this map is included for interest and informational purposes only. Learn more about each map below. For accessible PDF versions of this information, please select from one of the following options:Full Public Access Plan (PDF)Public Access Summary (PDF)Hunting Map InformationThis interactive map highlights hunting opportunities on DCR-DWSP land in central Massachusetts. The key data layers to this map are:Waterfowl Hunting Opportunities - a collection of points highlighting various waterbodies within the DWSP watersheds where waterfowl hunting is or is not allowed. For waterbodies that allow hunting, detailed information on exactly what is or is not allowed is provided in the feature pop-up, or in the attribute table record. Each feature pop-up also tells the user if trapping is allowed at a waterbody.Gates for Parking and Access - this layer shows the point locations of gates that can be used for parking or access onto DWSP lands. Depending on the type of point selected, the user will be provided with information on the number of parking spots available, a word of caution and (when available) photo(s) of the location. DCR-DWSP Lands by Permit Type - this polygon layer shows DWSP property boundaries and indicates if (and what type) of hunting is allowed in a certain area. These serve as a backdrop to all other data presented within the map. Click on a feature for more information, or review the attribute table to see what activities are allowed. Many layers in this map have a visibility constraint placed on them, and will only appear in the map as the user zooms in closer to an area. This helps ensure the map does not become cluttered when viewed at the full map extent. This map also contains numerous reference layers which provide important contextual information, such as the locations of marked intersections with labels for intersection number, locations of road and trails (with name and basic information on trail markings), locations of portable toilets, locations of Wildlife Management Areas (WMAs), hydrography, such as streams with names labeled, wetlands and lakes/ponds with names labeled and town boundaries. A group layer provides a collection of layers specifically relevant to the Quabbin Controlled Deer Hunts and includes: road barriers, marked intersections, hunt check-in locations, moose survey stations, deer check stations, and special road access.Together, this information provides a comprehensive map detailing where hunting and trapping is allowed within the DWSP watersheds and what specific hunting and trapping activities are allowed at each location. This map can help users plan a successful visit to DWSP property. When accessed through the ArcGIS Online Map Viewer, each layer's attribute table can be accessed, providing data in an alternative format. This map is also compatible with ArcGIS Field Maps and can be downloaded to "go offline", enabling a user access to the downloaded portion of the map when there is no cell service. Harvest Map InformationDeer Harvested by Weight - a collection of points showing where deer have been harvested during the Quabbin Controlled Deer Hunt within the Quabbin Reservoir Watershed. These points are symbolized to differentiate between male (dark blue circles with a light blue outline) and female (light red diamonds with a dark maroon outline) deer. DCR-DWSP Lands by Permit Type - this polygon layer shows DWSP property boundaries and indicates the type of permit required to hunt in any given area. This layer is configured to display four types of features; areas where a 5-Year Access Permit is required is shown in dark teal, areas where a Two-Day Deer Controlled Hunt Permit is required are shown in light orange, areas where a Deer Shotgun Season Controlled Hunt Permit is required are shown in bright yellow with dark yellow dots, and No Hunting Allowed areas are shown in a dark red. Click on a feature for more information, or review the attribute table to see what activities are allowed.Many layers in this map have a visibility constraint placed on them, and will only appear in the map as the user zooms in closer to an area. This helps ensure the map does not become cluttered when viewed at the full map extent. As you zoom in, these references features will appear. They provide important contextual information, such as the locations of marked intersections with labels for intersection number, locations of road and trails, hydrography, such as streams with names labeled, wetlands and lakes/ponds with names labeled.Together, this information provides a comprehensive map detailing where deer have been harvested within the Quabbin Reservoir Watershed. This map is designed for deer hunters and may help them plan where to hunt in the watershed. When accessed through the ArcGIS Online Map Viewer, each layer's attribute table can be accessed, providing data in an alternative format. This map is best used through the DCR-DWSP Hunting Map's Harvest Map page.

Soil map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations.Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals.Dataset SummaryPhenomenon Mapped: Ready-to-use project packages with over 170 attributes derived from the SSURGO dataset, split up by HUC8s. Geographic Extent: The dataset covers the 48 contiguous United States plus Hawaii and portions of Alaska. Map packages are available for Puerto Rico and the US Virgin Islands. A project package for US Island Territories and associated states of the Pacific Ocean can be downloaded by clicking one of the included areas in the map. The Pacific Project Package includes: Guam, the Marshall Islands, the Northern Marianas Islands, Palau, the Federated States of Micronesia, and American Samoa.Source: Natural Resources Conservation ServiceUpdate Frequency: AnnualPublication Date: December 2024Link to source metadata*Not all areas within SSURGO have completed soil surveys and many attributes have areas with no data.The soil data in the packages is also available as a feature layer in the ArcGIS Living Atlas of the World.AttributesKey fields from nine commonly used SSURGO tables were compiled to create the 173 attribute fields in this layer. Some fields were joined directly to the SSURGO Map Unit polygon feature class while others required summarization and other processing to create a 1:1 relationship between the attributes and polygons prior to joining the tables. Attributes of this layer are listed below in their order of occurrence in the attribute table and are organized by the SSURGO table they originated from and the processing methods used on them.Map Unit Polygon Feature Class Attribute TableThe fields in this table are from the attribute table of the Map Unit polygon feature class which provides the geographic extent of the map units.Area SymbolSpatial VersionMap Unit SymbolMap Unit TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the table using the Map Unit Key field.Map Unit NameMap Unit KindFarmland ClassInterpretive FocusIntensity of MappingIowa Corn Suitability RatingLegend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field.Project ScaleSurvey Area Catalog TableThe fields in this table have a 1:1 relationship with the polygons and were joined to the Map Unit table using the Survey Area Catalog Key and Legend Key fields.Survey Area VersionTabular VersionMap Unit Aggregated Attribute TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the Map Unit attribute table using the Map Unit Key field.Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Map Unit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Map Unit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - PresenceRating for Manure and Food Processing Waste - Weighted AverageComponent Table – Dominant ComponentMap units have one or more components. To create a 1:1 join component data must be summarized by map unit. For these fields a custom script was used to select the component with the highest value for the Component Percentage Representative Value field (comppct_r). Ties were broken with the Slope Representative Value field (slope_r). Components with lower average slope were selected as dominant. If both soil order and slope were tied, the first value in the table was selected.Component Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoff ClassSoil loss tolerance factorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionHydric RatingAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic ClassTaxonomic OrderTaxonomic SuborderGreat GroupSubgroupParticle SizeParticle Size ModCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoist SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilCalifornia Storie IndexComponent KeyComponent Table – Weighted AverageMap units may have one or more soil components. To create a 1:1 join, data from the Component table must be summarized by map unit. For these fields a custom script was used to calculate an average value for each map unit weighted by the Component Percentage Representative Value field (comppct_r).Slope Gradient - Low ValueSlope Gradient - Representative ValueSlope Gradient - High ValueSlope Length USLE - Low ValueSlope Length USLE - Representative ValueSlope Length USLE - High ValueElevation - Low ValueElevation - Representative ValueElevation - High ValueAlbedo - Low ValueAlbedo - Representative ValueAlbedo - High ValueMean Annual Air Temperature - Low ValueMean Annual Air Temperature - Representative ValueMean Annual Air Temperature - High ValueMean Annual Precipitation - Low ValueMean Annual Precipitation - Representative ValueMean Annual Precipitation - High ValueRelative Effective Annual Precipitation - Low ValueRelative Effective Annual Precipitation - Representative ValueRelative Effective Annual Precipitation - High ValueDays between Last and First Frost - Low ValueDays between Last and First Frost - Representative ValueDays between Last and First Frost - High ValueRange Forage Annual Potential Production - Low ValueRange Forage Annual Potential Production - Representative ValueRange Forage Annual Potential Production - High ValueInitial Subsidence - Low ValueInitial Subsidence - Representative ValueInitial Subsidence - High ValueTotal Subsidence - Low ValueTotal Subsidence - Representative ValueTotal Subsidence - High ValueCrop Productivity IndexEsri SymbologyThis field was created to provide symbology based on the Taxonomic Order field (taxorder). Because some map units have a null value for soil order, a custom script was used to populate this field using the Component Name (compname) and Map Unit Name (muname) fields. This field was created using the dominant soil order of each map unit.Esri SymbologyHorizon TableEach map unit polygon has one or more components and each component has one or more layers known as horizons. To incorporate this field from the Horizon table into the attributes for this layer, a custom script was used to first calculate the mean value weighted by thickness of the horizon for each component and then a mean value of components weighted by the Component Percentage Representative Value field for each map unit. K-Factor Rock FreeEsri Soil OrderThese fields were calculated from the Component table using a model that included the Pivot Table Tool, the Summarize Tool and a custom script. The first 11 fields provide the sum of Component Percentage Representative Value for each soil order for each map unit. The Soil Order Dominant Condition field was calculated by selecting the highest value in the preceding 11 soil order fields. In the case of tied values the component with the lowest average slope value (slope_r) was selected. If both soil order and slope were tied

Web App. Use the tabs provided to discover information about map features and capabilities. Link to Metadata. A variety of searches can be performed to find the parcel of interest. Use the Query Tool to build searches. Click Apply button at the bottom of the tool.Query by Name (Last First) (e.g. Bond James)Query by Address (e.g. 41 S Central)Query by Locator number (e.g. 21J411046)Search results will be listed under the Results tab. Click on a parcel in the list to zoom to that parcel. Click on the parcel in the map and scroll through the pop-up to see more information about the parcel. Click the ellipse in the Results tab or in the pop-up to view information in a table. Attribute information can be exported to CSV file. Build a custom Filter to select and map properties by opening the Parcels attribute table:1. Click the arrow tab at the bottom middle of the map to expand the attribute table window2. Click on the Parcels tab3. Check off Filter by map extent4. Open Options>Filter5. Build expressions as needed to filter by owner name or other variables6. Select the needed records from the returned list7. Click Zoom to which will zoom to the selected recordsPlease note that as the map zooms out detailed layers, such as the parcel boundaries will not display.In addition to Search capabilities, the following tools are provided:MeasureThe measure tool provides the capabilities to draw a point, line, or polygon on the map and specify the unit of measurement.DrawThe draw tool provides the capabilities to draw a point, line, or polygon on the map as graphics. PrintThe print tool exports the map to either a PDF or image file. Click Settings button to configure map or remove legend.Map navigation using mouse and keyboard:Drag to panSHIFT + CTRL + Drag to zoom outMouse Scroll Forward to zoom inMouse Scroll Backward to zoom outUse Arrow keys to pan+ key to zoom in a level- key to zoom out a levelDouble Click to Zoom inFAQsHow to select a parcel: Click on a parcel in the map, or use Query Tool to search for parcel by owner, address or parcel id.How to select more than one parcel: Go to Select Tool and choose options on Select button.How to clear selected parcel(s): Go to Select Tool and click Clear.

California Department of Transportation (Caltrans), Division of Transportation Planning, Aeronautics Program provided airport layout drawings with estimated digitized airport property or fence lines with Google Pro images background.Caltrans Division of Research, Innovation and System Information (DRISI) GIS office digitized the airport boundary lines with Bing Maps Aerial background and built the boundary lines into a GIS polygon feature class.Generally, Airport Layout Plans do not show complete connected property or fence lines. In many cases the boundary lines were interpreted among the property and fence lines with our best judgment. The airport general information derived from FAA Airport Master Record and Reports with their URL are included in the attribute table.Airport boundary data is intended for general reference and does not represent official airport property boundary determinations.

The CDFW Owned and Operated Lands and Conservation Easements dataset is a subset of the CDFW Lands dataset. It contains lands owned (fee title), some operated (wildlife areas, ecological reserves, and public/fishing access properties that are leases/agreements with other agencies that may be publicly accessible) and conservation easements held by CDFW. CDFW Owned and Operated Lands and Conservation Easements replaces the prior dataset, DFG Owned and Operated Lands, which included only fee title lands and some operated lands (wildlife areas, ecological reserves, and public/fishing access properties that are leases/agreements with other agencies and that may be publicly accessible). This is a generalized version dataset that has a shorter attribute table than the original and also has been dissolved based on the fields included. Please note that some lands may not be accessible due to the protection of resources and habitat. It is recommended that users contact the appropriate regional office for access information and consult regulations for CDFW lands in Sections 550, 550.1, 551, 552, 630 and 702. The CDFW Lands dataset is a digitized geographical inventory of selected lands owned and/or administered by the California Department of Fish and Wildlife. Properties such as ecological reserves, wildlife areas, undesignated lands containing biological resource values, public and fishing access lands, and CDFW fish hatcheries are among those lands included in this inventory. Types of properties owned or administered by CDFW which may not be included in this dataset are parcels less than 1 acre in size, such as fishing piers, fish spawning grounds, fish barriers, and other minor parcels. Physical boundaries of individual parcels are determined by the descriptions contained in legal documents and assessor parcel maps relating to that parcel. The approximate parcel boundaries are drawn onto U.S. Geological Survey 7.5'-series topographic maps, then digitized and attributed before being added to the dataset. In some cases, assessor parcel or best available datasets are used to digitize the boundary. Using parcel data to adjust the boundaries is a work in progress and will be incorporated in the future. Township, range, and section lines were based on the U.S. Geological Survey 7.5' series topographic maps (1:24,000 - scale). In some areas, the boundaries will not align with the Bureau of Land Management's Public Lands Survey System (PLSS). See the "SOURCE" field for data used to digitize boundary.

This parcels dataset is a spatial representation of tax lots for Union County, New Jersey that have been extracted from the NJ statewide parcels composite by the NJ Office of Information Technology, Office of GIS (NJOGIS). Parcels at county boundaries have been modified to correspond with the NJ county boundaries and the parcels in adjacent counties.Each parcel contains a field named PAMS_PIN based on a concatenation of the county/municipality code, block number, lot number and qualification code. Using the PAMS_PIN, the dataset can be joined to the MOD-IV database table that contains supplementary attribute information regarding lot ownership and characteristics. Due to irregularities in the data development process, duplicate PAMS_PIN values exist in the parcel records. Users should avoid joining MOD-IV database table records to all parcel records with duplicate PAMS_PINs because of uncertainty regarding whether the MOD-IV records will join to the correct parcel records. There are also parcel records with unique PAMS_PIN values for which there are no corresponding records in the MOD-IV database tables. This is mostly due to the way data are organized in the MOD-IV database.The polygons delineated in the dataset do not represent legal boundaries and should not be used to provide a legal determination of land ownership. Parcels are not survey data and should not be used as such.The MOD-IV system provides for uniform preparation, maintenance, presentation and storage of property tax information required by the Constitution of the State of New Jersey, New Jersey Statutes and rules promulgated by the Director of the Division of Taxation. MOD-IV maintains and updates all assessment records and produces all statutorily required tax lists for property tax bills. This list accounts for all parcels of real property as delineated and identified on each municipality's official tax map, as well as taxable values and descriptive data for each parcel. Tax List records were received as raw data from the Taxation Team of NJOIT which collected source information from municipal tax assessors and created the statewide table. This table was subsequently processed for ease of use with NJ tax parcel spatial data and split into an individual table for each county.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

The CDFW Owned and Operated Lands and Conservation Easements dataset is a subset of the CDFW Lands dataset. It contains lands owned (fee title), some operated (wildlife areas, ecological reserves, and public/fishing access properties that are leases/agreements with other agencies that may be publicly accessible) and conservation easements held by CDFW. CDFW Owned and Operated Lands and Conservation Easements replaces the prior dataset, DFG Owned and Operated Lands, which included only fee title lands and some operated lands (wildlife areas, ecological reserves, and public/fishing access properties that are leases/agreements with other agencies and that may be publicly accessible). This is a generalized version dataset that has a shorter attribute table than the original and also has been dissolved based on the fields included. Please note that some lands may not be accessible due to the protection of resources and habitat. It is recommended that users contact the appropriate regional office for access information and consult regulations for CDFW lands in Sections 550, 550.1, 551, 552, 630 and 702. For information on public use regulations on Department lands, please refer to the Public Uses on State and Federal Lands section of the Waterfowl, Upland Game, and Public Use Regulations booklet for both statewide and property-specific regulations https://wildlife.ca.gov/Regulations. All visitors are responsible for knowing and following the general and property-specific regulations.The CDFW Lands dataset is a digitized geographical inventory of selected lands owned and/or administered by the California Department of Fish and Wildlife. Properties such as ecological reserves, wildlife areas, undesignated lands containing biological resource values, public and fishing access lands, and CDFW fish hatcheries are among those lands included in this inventory. Types of properties owned or administered by CDFW which may not be included in this dataset are parcels less than 1 acre in size, such as fishing piers, fish spawning grounds, fish barriers, and other minor parcels. Physical boundaries of individual parcels are determined by the descriptions contained in legal documents and assessor parcel maps relating to that parcel. The approximate parcel boundaries are drawn onto U.S. Geological Survey 7.5'-series topographic maps, then digitized and attributed before being added to the dataset. In some cases, assessor parcel or best available datasets are used to digitize the boundary. Using parcel data to adjust the boundaries is a work in progress and will be incorporated in the future. Township, range, and section lines were based on the U.S. Geological Survey 7.5' series topographic maps (1:24,000 - scale). In some areas, the boundaries will not align with the Bureau of Land Management's Public Lands Survey System (PLSS). See the "SOURCE" field for data used to digitize boundary.

This parcels polygons feature class represents current city parcels within the City of Los Angeles. It shares topology with the Landbase parcel lines feature class. 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, ownership and land record information. The legal boundaries are determined on the ground by license surveyors in the State of California, and by recorded documents from the Los Angeles County Recorder's office and the City Clerk's office of the City of Los Angeles. Parcel and ownership information are available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the landbase parcels is entered into attributes. Principal attributes include:PIN and PIND: represents the unique auto-generated parcel identifier and key to related features and tables. This field is related to the LA_LEGAL, LA_APN and LA_HSE_NBR tables. PIN contains spaces and PIND replaces those spaces with a dash (-).LA_LEGAL - Table attributes containing legal description. Principal attributes include the following:TRACT: The subdivision tract number as recorded by the County of Los AngelesMAP_REF: Identifies the subdivision map book reference as recorded by the County of Los Angeles.LOT: The subdivision lot number as recorded by the County of Los Angeles.ENG_DIST: The four engineering Districts (W=Westla, C=Central, V= Valley and H=Harbor).CNCL_DIST: Council Districts 1-15 of the City of Los Angeles. OUTLA means parcel is outside the City.LA_APN- Table attributes containing County of Los Angeles Assessors information. Principal attributes include the following:BPP: The Book, Page and Parcel from the Los Angeles County Assessors office. SITUS*: Address for the property.LA_HSE_NBR - Table attributes containing housenumber information. Principal attributes include the following:HSE_ID: Unique id of each housenumber record.HSE_NBR: housenumber numerical valueSTR_*: Official housenumber addressFor a complete list of attribute values, please refer to Landbase_parcel_polygons_data_dictionary.Landbase parcels polygons data layer was created in geographical information systems (GIS) software to display the location of the right of way. The parcels polygons layer delineates the right of way from Landbase parcels lots. The parcels polygons layer is a feature class in the LACityLandbaseData.gdb Geodatabase dataset. The layer consists of spatial data as a polygon feature class and attribute data for the features. The area inside a polygon feature is a parcel lot. The area outside of the parcel polygon feature is the right of way. Several polygon features are adjacent, sharing one line between two polygons. For each parcel, there is a unique identifier in the PIND and PIN fields. The only difference is PIND has a dash and PIN does not. The types of edits include new subdivisions and lot cuts. Associated legal information about the landbase parcels lots is entered into attributes. The landbase parcels layer is vital to other City of LA Departments, by supporting property and land record operations and identifying legal information for City of Los Angeles. The landbase parcels polygons are inherited from a database originally created by the City's Survey and Mapping Division. Parcel information should only be added to the Landbase Parcels layer if documentation exists, such as a Deed or a Plan approved by the City Council. When seeking the definitive description of real property, consult the recorded Deed or Plan.List of Fields:ID: A unique numeric identifier of the polygon. The ID value is the last part of the PIN field value.ASSETID: User-defined feature autonumber.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral grid index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers. An A-map is the smallest grid in the index map and is used when there is a large amount of spatial information in the map display. There are more parcel lines and annotation than can fit in the B-map, and thus, an A-map is used. There are 4 A-maps in a B-map. In areas where parcel lines and annotation can fit comfortably in an index map, a B-map is used. The B-maps are at a scale of 100 feet, and A-maps are at a scale of 50 feet.OBJECTID: Internal feature number.BPPMAP_REFTRACTBLOCKMODLOTARBCNCL_DIST: LA City Council District. Values: • (numbers 1-15) - Current City Council Member for that District can be found on the mapping website http://navigatela.lacity.org/navigatela, click Council Districts layer name, under Boundaries layer group.SHAPE: Feature geometry.BOOKPAGEPARCELPIND: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. The D in the field name PIND, means "dash", and there is a dash between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • H - Harbor Engineering District. • C - Central Engineering District. • V - Valley Engineering District. • W - West LA Engineering District.PIN: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. There are spaces between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.

Dataset description-br /- This dataset is a recalculation of the Copernicus 2015 high resolution layer (HRL) of imperviousness density data (IMD) at different spatial/territorial scales for the case studies of Barcelona and Milan. The selected spatial/territorial scales are the following: * a) Barcelona city boundaries * b) Barcelona metropolitan area, Àrea Metropolitana de Barcelona (AMB) * c) Barcelona greater city (Urban Atlas) * d) Barcelona functional urban area (Urban Atlas) * e) Milan city boundaries * f) Milan metropolitan area, Piano Intercomunale Milanese (PIM) * g) Milan greater city (Urban Atlas) * h) Milan functional urban area (Urban Atlas)-br /- In each of the spatial/territorial scales listed above, the number of 20x20mt cells corresponding to each of the 101 values of imperviousness (0-100% soil sealing: 0% means fully non-sealed area; 100% means fully sealed area) is provided, as well as the converted measure into squared kilometres (km2). -br /- -br /- -br /- Dataset composition-br /- The dataset is provided in .csv format and is composed of: -br /- _IMD15_BCN_MI_Sources.csv_: Information on data sources -br /- _IMD15_BCN.csv_: This file refers to the 2015 high resolution layer of imperviousness density (IMD) for the selected territorial/spatial scales in Barcelona: * a) Barcelona city boundaries (label: bcn_city) * b) Barcelona metropolitan area, Àrea metropolitana de Barcelona (AMB) (label: bcn_amb) * c) Barcelona greater city (Urban Atlas) (label: bcn_grc) * d) Barcelona functional urban area (Urban Atlas) (label: bcn_fua)-br /- _IMD15_MI.csv_: This file refers to the 2015 high resolution layer of imperviousness density (IMD) for the selected territorial/spatial scales in Milan: * e) Milan city boundaries (label: mi_city) * f) Milan metropolitan area, Piano intercomunale milanese (PIM) (label: mi_pim) * g) Milan greater city (Urban Atlas) (label: mi_grc) * h) Milan functional urban area (Urban Atlas) (label: mi_fua)-br /- _IMD15_BCN_MI.mpk_: the shareable project in Esri ArcGIS format including the HRL IMD data in raster format for each of the territorial boundaries as specified in letter a)-h). -br /- Regarding the territorial scale as per letter f), the list of municipalities included in the Milan metropolitan area in 2016 was provided to me in 2016 from a person working at the PIM. -br /- In the IMD15_BCN.csv and IMD15_MI.csv, the following columns are included: * Level: the territorial level as defined above (a)-d) for Barcelona and e)-h) for Milan); * Value: the 101 values of imperviousness density expressed as a percentage of soil sealing (0-100%: 0% means fully non-sealed area; 100% means fully sealed area); * Count: the number of 20x20mt cells corresponding to a certain percentage of soil sealing or imperviousness; * Km2: the conversion of the 20x20mt cells into squared kilometres (km2) to facilitate the use of the dataset.-br /- -br /- -br /- Further information on the Dataset-br /- This dataset is the result of a combination between different databases of different types and that have been downloaded from different sources. Below, I describe the main steps in data management that resulted in the production of the dataset in an Esri ArcGIS (ArcMap, Version 10.7) project.-br /- 1. The high resolution layer (HRL) of the imperviousness density data (IMD) for 2015 has been downloaded from the official website of Copernicus. At the time of producing the dataset (April/May 2021), the 2018 version of the IMD HRL database was not yet validated, so the 2015 version was chosen instead. The type of this dataset is raster. 2. For both Barcelona and Milan, shapefiles of their administrative boundaries have been downloaded from official sources, i.e. the ISTAT (Italian National Statistical Institute) and the ICGC (Catalan Institute for Cartography and Geology). These files have been reprojected to match the IMD HRL projection, i.e. ETRS 1989 LAEA. 3. Urban Atlas (UA) boundaries for the Greater Cities (GRC) and Functional Urban Areas (FUA) of Barcelona and Milan have been checked and reconstructed in Esri ArcGIS from the administrative boundaries files by using a Eurostat correspondence table. This is because at the time of the dataset creation (April/May 2021), the 2018 Urban Atlas shapefiles for these two cities were not fully updated or validated on the Copernicus Urban Atlas website. Therefore, I had to re-create the GRC and FUA boundaries by using the Eurostat correspondence table as an alternative (but still official) data source. The use of the Eurostat correspondence table with the codes and names of municipalities was also useful to detect discrepancies, basically stemming from changes in municipality names and codes and that created inconsistent spatial features. When detected, these discrepancies have been checked with the ISTAT and ICGC offices in charge of producing Urban Atlas data before the final GRC and FUA boundaries were defined.-br /- Steps 2) and 3) were the most time consuming, because they required other tools to be used in Esri ArcGIS, like spatial joins and geoprocessing tools for shapefiles (in particular dissolve and area re-calculator in editing sessions) for each of the spatial/territorial scales as indicated in letters a)-h). -br /- Once the databases for both Barcelona and Milan as described in points 2) and 3) were ready (uploaded in Esri ArcGIS, reprojected and their correctness checked), they have been ‘crossed’ (i.e. clipped) with the IMD HRL as described in point 1) and a specific raster for each territorial level has been calculated. The procedure in Esri ArcGIS was the following: * Clipping: Arctoolbox - Data management tools - Raster - Raster Processing - Clip. The ‘input’ file is the HRL IMD raster file as described in point 1) and the ‘output’ file is each of the spatial/territorial files. The option "Use Input Features for Clipping Geometry (optional)” was selected for each of the clipping. * Delete and create raster attribute table: Once the clipping has been done, the raster has to be recalculated first through Arctoolbox - Data management tools - Raster - Raster properties - Delete Raster Attribute Table and then through Arctoolbox - Data management tools - Raster - Raster properties - Build Raster Attribute Table; the "overwrite" option has been selected. -br /- -br /- Other tools used for the raster files in Esri ArcGIS have been the spatial analyst tools (in particular, Zonal - Zonal Statistics). As an additional check, the colour scheme of each of the newly created raster for each of the spatial/territorial attributes as per letters a)-h) above has been changed to check the consistency of its overlay with the original HRL IMD file. However, a perfect match between the shapefiles as per letters a)-h) and the raster files could not be achieved since the raster files are composed of 20x20mt cells.-br /- The newly created attribute tables of each of the raster files have been exported and saved as .txt files. These .txt files have then been copied in the excel corresponding to the final published dataset.

This dataset contains polygons representing individual taxed parcels or individual tax-exempt parcels tracked for taxing purposes. It also contains polygons representing the locations of multiple tax properties. In the case of multiple tax properties, several parcel polygons may be stacked on top of one another. These are multiple tax parcels that cannot be delineated on a two-dimensional map, including both taxed and tax-exempt parcels. The parcels are represented with identical geometries but have different parcel IDs and associated tax attributes. The PID field contains the property ID number for each parcel.Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/County%20Tax%20Parcels.pdf

© This dataset is compiled monthly by the Hennepin County GIS Office from parcel geometry that is created and maintained by the Hennepin County Resident and Real Estate Services Survey Division and tax attributes extracted from the Hennepin County Real Estate Services property tax information system.

In late September 2017, intense precipitation associated with Hurricane Maria caused extensive landsliding across Puerto Rico. Much of the Las Marias municipality in central-western Puerto Rico was severely impacted by landslides., Landslide density in this region was mapped as greater than 25 landslides/km2 (Bessette-Kirton et al., 2019). In order to better understand the controlling variables of landslide occurrence and runout in this region, two 2.5-km2 study areas were selected and all landslides within were manually mapped in detail using remote-sensing data. Included in the data release are five separate shapefiles: geographic areas representing the mapping extent of the four distinct areas (map areas, filename: map_areas), initiation location polygons (source areas, filename: SourceArea), polygons of the entire impacted area consisting of source, transport, and deposition (affected areas, filename: AffectArea), points on the furthest upslope extent of the landslide source areas (headscarp point, filename: HSPoint), and lines reflecting the approximate travel paths from the furthest upslope extent to the furthest downslope extent of the landslides (runout lines, filename: RunoutLine). These shapefiles contain qualitative attributes interpreted from the aerial imagery (such as geomorphic setting and impact of human activity) and qualitative attributes extracted from the geospatial data (such as source area length, width, and depth), as well as attributes extracted from other sources (such as geology and soil properties). A table detailing each attribute, attribute abbreviations, the possible choices for each attribute, and a short description of each attribute is provided as a table in the file labeled AttributeDescription.docx. The headscarp point shapefile attribute tables contain closest distance between headscarp and paved road (road_d_m; road data from U.S. Census Bureau, 2015). The runout line shapefile attribute table reflects if the landslide was considered independently unmappable past a road or river (term_drain), the horizontal length of the runout (length_m), the fall height from the headscarp to termination (h_m), the ratio of fall height to runout length (hlratio), distance to nearest paved road (road_d_m), and the watershed area upslope from the upper end of the runout line (wtrshd_m2). All quantitative metrics were calculated using tools available in ESRI ArcMap v. 10.6. The source area shapefile attribute table reflects general source area vegetation (vegetat) and land use (land_use), whether the slide significantly disaggregated during movement (flow), the failure mode (failmode), if the slide was a reactivation of a previous one (reactivate), if the landslide directly impacted the occurrence of another slide (ls_complex), the proportion of source material that left the source area (sourc_evac), the state of the remaining material (remaining), the curvature of the source area (sourc_curv), potential human impact on landslide occurrence (human_caus), potential landslide impact on human society (human_effc), if a building exists within 10 meters of the source area (buildng10m), if a road exists within 50 meters of the source area (road50m), the planimetric area of the source area (area_m2), the dimension of the source area perpendicular to the direction of motion (width_m), the dimension of the source area parallel to the direction of motion (length_m), the geologic formation of the source area (FMATN; from Bawiec, W.J., 1998), the soil type of the source area (MUNAME; from Acevido, G., 2020), the root-zone (0-100 cm deep) soil moisture estimated by the NASA SMAP mission for 9:30 am Atlantic Standard Time on 21 September 2017 (the day after Hurricane MarÃa) (smap; NASA, 2017), the average precipitation amount in the source area for the duration of the hurricane (pptn_mm; from Ramos-Scharrón, C.E., and Arima, E., 2019), the source area mean slope (mn_slp_d), the source area median slope (mdn_slp_d), the average depth change of material from the source area after the landslide (mn_dpth_m), the median depth change of material from the source area after the landslide (mdn_dpt_m), the sum of the volumetric change of material in the source area after the landslide (ldr_sm_m3), the major geomorphic landform of the source (maj_ldfrm), and the landcover of the source area (PRGAP_CL; from Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004). The affected area shapefile attribute table reflects the general affected area vegetation type (vegetat), the major geomorphic landform on which the landslide occurred (maj_ldfrm), whether the slide disaggregated during movement (flow), the general land use (land_use), the planimetric area of the affected area (area_m2), the dominant geologic formation of the affected area (FMATN; from Bawiec, W.J., 1998), the dominant soil type of the affected area (MUNAME; from Acevido, G., 2020), the sum of the volumetric change of material in all the contributing source areas for the affected area (Sum_ldr_sm), the average volumetric change of material in all the contributing source areas for the affected area (Avg_ldr_sm), if the landslide was considered independently unmappable past a road or river (term_drain), the number of contributing source areas to the affected area (num_srce), and the dominant landcover of the affected area (PRGAP_CL; from Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004). Mapping was conducted using aerial imagery collected between 9-15 October 2017 at 25-cm resolution (Quantum Spatial, Inc., 2017), a 1-m-resolution pre-event lidar digital elevation model (DEM) (U.S. Geological Survey, 2018), and a 1-m-resolution post-event lidar DEM (U.S. Geological Survey, 2020). In order to accurately determine the extent of the mapped landslides and to verify the georeferencing of the aerial imagery, aerial photographs were overlain with each DEM as well as a pre- and post-event lidar difference (2016-2018), and corrections were made as needed. Additional data sources described in the AttributeDescription document and metadata were used to extract spatial data once mapping was complete and results were appended to the shapefile attribute tables. Data in this release are provided as ArcGIS point (HSPoint), line (RunoutLine), and polygon (AffectArea and SourceArea) feature class files. Bessette-Kirton, E.K., Cerovski-Darriau, C., Schulz, W.H., Coe, J.A., Kean, J.W., Godt, J.W, Thomas, M.A., and Hughes, K. Stephen, 2019, Landslides Triggered by Hurricane Maria: Assessment of an Extreme Event in Puerto Rico: GSA Today, v. 29, doi:10.1130/GSATG383A.1 U.S. Census Bureau, 2015, 2015 TIGER/Line Shapefiles, State, Puerto Rico, primary and secondary roads State-based Shapefile: United States Census Bureau, accessed September 12, 2019, at http://www2.census.gov/geo/tiger/TIGER2015/ PRISECROADS/tl_2015_72_prisecroads.zip. Bawiec, W.J., 1998, Geology, geochemistry, geophysics, mineral occurrences and mineral resource assessment for the Commonwealth of Puerto Rico: U.S. Geological Survey Open-File Report 98-38, https://pubs.usgs.gov/of/1998/of98-038/ (accessed May 2020). Acevido, G., 2020, Soil Survey of Arecibo Area of Norther Puerto Rico: United States Department of Agriculture, Soil Conservation Service. National Aeronautics and Space Administration [NASA], 2017, SMAP L4 Global 3-hourly 9 km EASE-Grid Surface and Root Zone Soil Moisture Analysis Update, Version 4: National Snow & Ice Data Center web page, accessed September 12, 2019, at https://nsidc.org/data/SPL4SMAU/versions/4. Ramos-Scharrón, C.E., and Arima, E., 2019, Hurricane MarÃa’s precipitation signature in Puerto Rico—A conceivable presage of rains to come: Scientific Reports, v. 9, no. 1, article no. 15612, accessed February 28, 2020, at https://doi.org/10.1038/ s41598-019-52198-2. Homer, C. C. Huang, L. Yang, B. Wylie and M. Coan, 2004, Development of a 2001 National Landcover Database for the United States: Photogrammetric Engineering and Remote Sensing, Vol. 70, No. 7, July 2004, pp. 829-840. Quantum Spatial, Inc., 2017, FEMA PR Imagery: https://s3.amazonaws.com/fema-cap-imagery/Others/Maria (accessed October 2017). U.S. Geological Survey, 2018, USGS NED Original Product Resolution PR Puerto Rico 2015: http://nationalmap.gov/elevation.html (accessed October 2018). U.S. Geological Survey, 2020, USGS NED Original Product Resolution PR Puerto Rico 2018: http://nationalmap.gov/elevation.html (accessed June 2020). Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government

This layer contains address point features which are used for geocoding addresses and property identification numbers. Data attributes include property addresses and property identification numbers. Addresses are stored in both parsed and concatenated fields.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/Address%20Points.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data. General questions about this data set, including errors, omissions, corrections and/or updates should be directed to the Hennepin County GIS Office at 612-596-9484.

© This data set was created by Hennepin County Resident and Real Estate Services Survey Division, and modified by the Hennepin County GIS office.

Nonresidential gross floor area at a parcel level within Fairfax County as of the VALID_TO date in the attribute table. Information for tax-exempt institutional properties is incomplete. For methodology and a data dictionary please view the IPLS data dictionary

Dataset contains the ZIP code boundaries inside of Hennepin County. Non-taxing polygons for Zip code areas are defined using parcel attributes of property mailing address. The field NAME_TXT contains the ZIP Code number for each polygon.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/Zipcodes.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data. General questions about this dataset, including errors, omissions, corrections and/or updates should be directed to the Survey Division, Resident and Real Estate Services Department, Hennepin County at 612-348-3131.

© This data set is maintained by Hennepin County Resident and Real Estate Services Survey Division. This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

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 parcels dataset is a spatial representation of tax lots for Gloucester County, New Jersey that have been extracted from the NJ statewide parcels composite by the NJ Office of Information Technology, Office of GIS (NJOGIS). Parcels at county boundaries have been modified to correspond with the NJ county boundaries and the parcels in adjacent counties.Each parcel contains a field named PAMS_PIN based on a concatenation of the county/municipality code, block number, lot number and qualification code. Using the PAMS_PIN, the dataset can be joined to the MOD-IV database table that contains supplementary attribute information regarding lot ownership and characteristics. Due to irregularities in the data development process, duplicate PAMS_PIN values exist in the parcel records. Users should avoid joining MOD-IV database table records to all parcel records with duplicate PAMS_PINs because of uncertainty regarding whether the MOD-IV records will join to the correct parcel records. There are also parcel records with unique PAMS_PIN values for which there are no corresponding records in the MOD-IV database tables. This is mostly due to the way data are organized in the MOD-IV database.The polygons delineated in the dataset do not represent legal boundaries and should not be used to provide a legal determination of land ownership. Parcels are not survey data and should not be used as such.The MOD-IV system provides for uniform preparation, maintenance, presentation and storage of property tax information required by the Constitution of the State of New Jersey, New Jersey Statutes and rules promulgated by the Director of the Division of Taxation. MOD-IV maintains and updates all assessment records and produces all statutorily required tax lists for property tax bills. This list accounts for all parcels of real property as delineated and identified on each municipality's official tax map, as well as taxable values and descriptive data for each parcel. Tax List records were received as raw data from the Taxation Team of NJOIT which collected source information from municipal tax assessors and created the statewide table. This table was subsequently processed for ease of use with NJ tax parcel spatial data and split into an individual table for each county.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.