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. Data from thegSSURGO databasewas used to create this layer. To download ready-to-use project packages of useful soil data derived from the SSURGO dataset, please visit the USA SSURGO Downloader app. Dataset Summary Phenomenon Mapped:Soils of the United States and associated territoriesGeographic Extent:The 50 United States, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaCoordinate System:Web Mercator Auxiliary SphereVisible Scale:1:144,000 to 1:1,000Source:USDA Natural Resources Conservation Service Update Frequency:AnnualPublication Date:December 2024 What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS Online Add this layer to a map in the map viewer. The layer is limited to scales of approximately 1:144,000 or larger but avector tile layercreated from the same data can be used at smaller scales to produce awebmapthat displays across the full scale range. The layer or a map containing it can be used in an application.Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections and apply filters. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Change the layer’s style and filter the data. For example, you could set a filter forFarmland Class= "All areas are prime farmland" to create a map of only prime farmland.Add labels and set their propertiesCustomize the pop-upArcGIS Pro Add this layer to a 2d or 3d map. The same scale limit as Online applies in ProUse as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of theLiving Atlas of the Worldthat provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics. Data DictionaryAttributesKey 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 Symbol Map 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 Rating Legend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field. Project Scale Survey 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 Version Map 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 Mapunit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Mapunit 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 - Presence Rating for Manure and Food Processing Waste - Weighted Average Component 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 Key Component 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 -

The Viewshed analysis layer is used to identify visible areas. You specify the places you are interested in, either from a file or interactively, and the Viewshed service combines this with Esri-curated elevation data to create output polygons of visible areas. Some questions you can answer with the Viewshed task include:What areas can I see from this location? What areas can see me?Can I see the proposed wind farm?What areas can be seen from the proposed fire tower?The maximum number of input features is 1000.Viewshed has the following optional parameters:Maximum Distance: The maximum distance to calculate the viewshed.Maximum Distance Units: The units for the Maximum Distance parameter. The default is meters.DEM Resolution: The source elevation data; the default is 90m resolution SRTM. Other options include 30m, 24m, 10m, and Finest.Observer Height: The height above the surface of the observer. The default value of 1.75 meters is an average height of a person. If you are looking from an elevation location such as an observation tower or a tall building, use that height instead.Observer Height Units: The units for the Observer Height parameter. The default is meters.Surface Offset: The height above the surface of the object you are trying to see. The default value is 0. If you are trying to see buildings or wind turbines add their height here.Surface Offset Units: The units for the Surface Offset parameter. The default is meters.Generalize Viewshed Polygons: Determine if the viewshed polygons are to be generalized or not. The viewshed calculation is based upon a raster elevation model which creates a result with stair-stepped edges. To create a more pleasing appearance, and improve performance, the default behavior is to generalize the polygons. This generalization will not change the accuracy of the result for any location more than one half of the DEM's resolution.By default, this tool currently works worldwide between 60 degrees north and 56 degrees south based on the 3 arc-second (approximately 90 meter) resolution SRTM dataset. Depending upon the DEM resolution pick by the user, different data sources will be used by the tool. For 24m, tool will use global dataset WorldDEM4Ortho (excluding the counties of Azerbaijan, DR Congo and Ukraine) 0.8 arc-second (approximately 24 meter) from Airbus Defence and Space GmbH. For 30m, tool will use 1 arc-second resolution data in North America (Canada, United States, and Mexico) from the USGS National Elevation Dataset (NED), SRTM DEM-S dataset from Geoscience Australia in Australia and SRTM data between 60 degrees north and 56 degrees south in the remaining parts of the world (Africa, South America, most of Europe and continental Asia, the East Indies, New Zealand, and islands of the western Pacific). For 10m, tool will use 1/3 arc-second resolution data in the continental United States from USGS National Elevation Dataset (NED) and approximately 10 meter data covering Netherlands, Norway, Finland, Denmark, Austria, Spain, Japan Estonia, Latvia, Lithuania, Slovakia, Italy, Northern Ireland, Switzerland and Liechtenstein from various authoritative sources.To learn more, read the developer documentation for Viewshed or follow the Learn ArcGIS exercise called I Can See for Miles and Miles. To use this Geoprocessing service in ArcGIS Desktop 10.2.1 and higher, you can either connect to the Ready-to-Use Services, or create an ArcGIS Server connection. Connect to the Ready-to-Use Services by first signing in to your ArcGIS Online Organizational Account:Once you are signed in, the Ready-to-Use Services will appear in the Ready-to-Use Services folder or the Catalog window:If you would like to add a direct connection to the Elevation ArcGIS Server in ArcGIS for Desktop or ArcGIS Pro, use this URL to connect: https://elevation.arcgis.com/arcgis/services. You will also need to provide your account credentials. ArcGIS for Desktop:ArcGIS Pro:The ArcGIS help has additional information about how to do this:Learn how to make a ArcGIS Server Connection in ArcGIS Desktop. Learn more about using geoprocessing services in ArcGIS Desktop.This tool is part of a larger collection of elevation layers that you can use to perform a variety of mapping analysis tasks.

The NYC Department of City Planning's (DCP) Housing Database contains all NYC Department of Buildings (DOB) approved housing construction and demolition jobs filed or completed in NYC since January 1, 2010. It includes the three primary construction job types that add or remove residential units: new buildings, major alterations, and demolitions, and can be used to determine the change in legal housing units across time and space. Records in the Housing Database Project-Level Files are geocoded to the greatest level of precision possible, subject to numerous quality assurance and control checks, recoded for usability, and joined to other housing data sources relevant to city planners and analysts. Data are updated semiannually, at the end of the second and fourth quarters of each year. Please see DCP's annual Housing Production Snapshot summarizing findings from the 21Q4 data release "https://storymaps.arcgis.com/stories/1c9138dc24064b2e8142ff156345a719">here. Additional Housing and Economic analyses are also available. All previously released versions of this data are available at BYTES of the BIG APPLE - Archive.

The Wildland-Urban Interface (WUI) is the area where houses meet or intermingle with undeveloped wildland vegetation. This makes the WUI a focal area for human-environment conflicts such as wildland fires, habitat fragmentation, invasive species, and biodiversity decline. Using geographic information systems (GIS), we integrated U.S. Census and USGS National Land Cover Data, to map the Federal Register definition of WUI (Federal Register 66:751, 2001) for the conterminous United States from 1990-2020. These data are useful within a GIS for mapping and analysis at national, state, and local levels. Data are available as a geodatabase and include information such as housing densities for 1990, 2000, 2010, and 2020; wildland vegetation percentages for 1992, 2001, 2011, and 2019; as well as WUI classes in 1990, 2000, 2010, and 2020.This WUI feature class is separate from the WUI datasets maintained by individual forest unites, and it is not the authoritative source data of WUI for forest units. This dataset shows change over time in the WUI data up to 2020.Metadata and Downloads

Permit records from the City of Seattle permitting system for building permits that create or demolish housing units. Records begin from the beginning of the previous decade from the current quarter year.

The permits in this layer are those that have been completed. This data does not contain records for those permits that were issued but were not completed so are therefore not comparable to statistics that report permit issuance.

Each record represents the number of units added or demolished for each housing type in the project. Therefore a single building permit may appear multiple times if there are a mix of unit types in the project.

Housing unit types reflect the unit types regulated by the building codes and change through time. There has been no attempt to standardize these types and therefore reflect the unit types that existed at the time the permit was issued.

There may be multiple permits at any given address.

Permit records from the City of Seattle permitting system for building permits that create or demolish attached accessory dwelling units (AADU). Records begin in 1990 and are through the current year quarter.

The permits in this layer are those that have either been completed or are currently issued. This data does not contain records for those permits that were issued but were not completed so are therefore not comparable to statistics that report permit issuance.

Each record represents the number of units added or demolished for each housing type in the project. Therefore a single building permit may appear multiple times if there are a mix of unit types in the project.

Housing unit types reflect the unit types regulated by the building codes and change through time. There has been no attempt to standardize these types and therefore reflect the unit types that existed at the time the permit was issued. Unit types will be visible only for the time period they were in the code. For example, small efficiency dwelling units were not created in the code until 2016 and so will not appear as a type until that year.

There may be multiple permits at any given address.

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau across all standard and custom geographies at statewide summary level where applicable. For a deep dive into the data model including every specific metric, see the ACS 2017-2021 Data Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics. Find naming convention prefixes/suffixes, geography definitions and user notes below.Prefixes:NoneCountpPercentrRatemMedianaMean (average)tAggregate (total)chChange in absolute terms (value in t2 - value in t1)pchPercent change ((value in t2 - value in t1) / value in t1)chpChange in percent (percent in t2 - percent in t1)sSignificance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computedSuffixes:_e21Estimate from 2017-21 ACS_m21Margin of Error from 2017-21 ACS_e102006-10 ACS, re-estimated to 2020 geography_m10Margin of Error from 2006-10 ACS, re-estimated to 2020 geography_e10_21Change, 2010-21 (holding constant at 2020 geography)GeographiesAAA = Area Agency on Aging (12 geographic units formed from counties providing statewide coverage)ARC21 = Atlanta Regional Commission modeling area (21 counties merged to a single geographic unit)ARWDB7 = Atlanta Regional Workforce Development Board (7 counties merged to a single geographic unit)BeltLine (buffer)BeltLine Study (subareas)Census Tract (statewide)CFGA23 = Community Foundation for Greater Atlanta (23 counties merged to a single geographic unit)City (statewide)City of Atlanta Council Districts (City of Atlanta)City of Atlanta Neighborhood Planning Unit (City of Atlanta)City of Atlanta Neighborhood Planning Unit STV (3 NPUs merged to a single geographic unit within City of Atlanta)City of Atlanta Neighborhood Statistical Areas (City of Atlanta)City of Atlanta Neighborhood Statistical Areas E02E06 (2 NSAs merged to single geographic unit within City of Atlanta)County (statewide)Georgia House (statewide)Georgia Senate (statewide)MetroWater15 = Atlanta Metropolitan Water District (15 counties merged to a single geographic unit)Regional Commissions (statewide)SPARCC = Strong, Prosperous And Resilient Communities ChallengeState of Georgia (single geographic unit)Superdistrict (ARC region)US Congress (statewide)UWGA13 = United Way of Greater Atlanta (13 counties merged to a single geographic unit)WFF = Westside Future Fund (subarea of City of Atlanta)ZIP Code Tabulation Areas (statewide)The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2017-2021). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2017-2021Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the data manifest: https://garc.maps.arcgis.com/sharing/rest/content/items/34b9adfdcc294788ba9c70bf433bd4c1/data

Commonage GIS Dataset. Published by Department of Housing, Local Government and Heritage. Available under the license Creative Commons Attribution 4.0 (CC-BY-4.0).Commonage Framework Planning was a joint initiative between the National Parks and Wildlife Service and the Department of Agriculture and Food. Teams combining agricultural and ecological skills to assess the sustainable use of these areas have surveyed all known commonage areas in Ireland.

To date in excess of 4,400 plans have been prepared, covering more than 440,000 hectares. Where necessary, destocking (removal of some of the stock kept on commonage) was prescribed to ensure recovery of the vegetation. These plans have been implemented through REPS, AEOS and the NPWS Farm Plan Scheme, as relevant, from 1999 - 2012.

A commitment has been made to monitor the condition of commonages to demonstrate, in particular, that initiatives are delivering recovery in overgrazed areas and that undergrazing is not becoming a problem. Ireland also has obligations to monitor the state of SACs containing uplands and peatlands in non-commonage areas. This involves a reassessment of habitats in commonage areas, some of which were assessed as early as 1999, and also non-commonage areas.

Planning teams comprising both agriculturalists and environmentalists have been trained and re-surveys have been completed in commonage blocks in Counties Mayo, Galway, Cork, Kerry, Donegal, Sligo, Leitrim, Tipperary, Limerick and Louth between 2004 and 2010. Monitoring reports have been forwarded to the EU Commission highlighting the findings and trends. Additional survey work in 2007 focussed on Counties Mayo, Donegal and Kerry. In 2008, all commonage that had a destocking of greater than 50% were re-assessed.

In this context GIS files were set up to describe: - Destocking rates assigned to Agricultural Units - Habitat types and damage categories assigned to Agricultural Sub-Units and - Locations of Base-Stations and habitat types / damage categories recorded at these stations

A review of all the Commonage Framework Plans, setting sustainable stocking rates, will conclude in 2012 and will be communicated to all shareholders by the Department of Agriculture, Food and the Marine. This information is not contained here....

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana Mean (average)t Aggregate (total)ch Change in absolute terms (value in t2 - value in t1)pch Percent change ((value in t2 - value in t1) / value in t1)chp Change in percent (percent in t2 - percent in t1)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2015-2019). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

The NYC Department of City Plannings (DCP) Housing Database contains all NYC Department of Buildings (DOB) - approved housing construction and demolition jobs filed or completed in NYC since January 1, 2010. It includes all three construction job types that add or remove residential units: new buildings, major alterations, and demolitions, and can be used to determine the change in legal housing units across time and space. Records in the Housing Database are geocoded to the greatest level of precision possible, subject to numerous quality assurance and control checks, recoded for usability, and joined to other housing data sources relevant to city planners and analysts.

This data layer references data from a high-resolution tree canopy change-detection layer for Seattle, Washington. Tree canopy change was mapped by using remotely sensed data from two time periods (2016 and 2021). Tree canopy was assigned to three classes: 1) no change, 2) gain, and 3) loss. No change represents tree canopy that remained the same from one time period to the next. Gain represents tree canopy that increased or was newly added, from one time period to the next. Loss represents the tree canopy that was removed from one time period to the next. Mapping was carried out using an approach that integrated automated feature extraction with manual edits. Care was taken to ensure that changes to the tree canopy were due to actual change in the land cover as opposed to differences in the remotely sensed data stemming from lighting conditions or image parallax. Direct comparison was possible because land-cover maps from both time periods were created using object-based image analysis (OBIA) and included similar source datasets (LiDAR-derived surface models, multispectral imagery, and thematic GIS inputs). OBIA systems work by grouping pixels into meaningful objects based on their spectral and spatial properties, while taking into account boundaries imposed by existing vector datasets. Within the OBIA environment a rule-based expert system was designed to effectively mimic the process of manual image analysis by incorporating the elements of image interpretation (color/tone, texture, pattern, location, size, and shape) into the classification process. A series of morphological procedures were employed to ensure that the end product is both accurate and cartographically pleasing. No accuracy assessment was conducted, but the dataset was subjected to manual review and correction.University of Vermont Spatial Analysis Laboratory in collaboration with City of Seattle.This dataset consists of City of Seattle SDOT Urban Forestry Management Units which cover the following tree canopy categories: Existing tree canopy percent Possible tree canopy - vegetation percent Relative percent change Absolute percent changeFor more information, please see the 2021 Tree Canopy Assessment.

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana Mean (average)t Aggregate (total)ch Change in absolute terms (value in t2 - value in t1)pch Percent change ((value in t2 - value in t1) / value in t1)chp Change in percent (percent in t2 - percent in t1)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2015-2019). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana Mean (average)t Aggregate (total)ch Change in absolute terms (value in t2 - value in t1)pch Percent change ((value in t2 - value in t1) / value in t1)chp Change in percent (percent in t2 - percent in t1)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2015-2019). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana Mean (average)t Aggregate (total)ch Change in absolute terms (value in t2 - value in t1)pch Percent change ((value in t2 - value in t1) / value in t1)chp Change in percent (percent in t2 - percent in t1)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2015-2019). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana Mean (average)t Aggregate (total)ch Change in absolute terms (value in t2 - value in t1)pch Percent change ((value in t2 - value in t1) / value in t1)chp Change in percent (percent in t2 - percent in t1)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2015-2019). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana Mean (average)t Aggregate (total)ch Change in absolute terms (value in t2 - value in t1)pch Percent change ((value in t2 - value in t1) / value in t1)chp Change in percent (percent in t2 - percent in t1)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2015-2019). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana Mean (average)t Aggregate (total)ch Change in absolute terms (value in t2 - value in t1)pch Percent change ((value in t2 - value in t1) / value in t1)chp Change in percent (percent in t2 - percent in t1)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2015-2019). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana Mean (average)t Aggregate (total)ch Change in absolute terms (value in t2 - value in t1)pch Percent change ((value in t2 - value in t1) / value in t1)chp Change in percent (percent in t2 - percent in t1)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2015-2019). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

Landforms are large recognizable features such as mountains, hills and plains; they are an important determinant of ecological character, habitat definition and terrain analysis. Landforms are important to the distribution of life in natural systems and are the basis for opportunities in built systems, and therefore landforms play a useful role in all natural science fields of study and planning disciplines. Dataset SummaryPhenomenon Mapped: LandformsGeographic Extent: GlobalProjection: WGS 1984Mosaic Projection: Web Mercator Auxiliary SphereUnits: MetersCell Size: 231.91560581932 metersPixel Depth: 8-bit unsigned integerAnalysis: Restricted single source analysis. Maximum size of analysis is 30,000 x 30,000 pixels.Source: EsriPublication Date: May 2016ArcGIS Server URL: https://landscape7.arcgis.com/arcgis/ In February 2017, Esri updated the World Landforms - Improved Hammond Method service with two display functions: Ecological Land Units landform classes and Ecological Facets landform classes. This layer represents Ecological Facets landform classes. You can view the Ecological Land Units landform classes by choosing Image Display, and changing the Renderer. This layer was produced using the Improved Hammond Landform Classification Algorithm produced by Esri in 2016. This algorithm published and described by Karagulle et al. 2017: Modeling global Hammond landform regions from 250-m elevation data in Transactions in GIS. The algorithm, which is based on the most recent work in this area by Morgan, J. & Lesh, A. 2005: Developing Landform Maps Using Esri’s Model Builder., Esri converted Morgan’s model into a Python script and revised it to work on global 250-meter resolution GMTED2010 elevation data. Hammond’s landform classification characterizes regions rather than identifying individual features, thus, this layer contains sixteen classes of landforms:Nearly flat plains Smooth plains with some local relief Irregular plains with moderate relief Irregular plains with low hills Scattered moderate hills Scattered high hills Scattered low mountains Scattered high mountains Moderate hills High hills Tablelands with moderate relief Tablelands with considerable relief Tablelands with high relief Tablelands with very high relief Low mountains High mountains To produce these classes, Esri staff first projected the 250-meter resolution GMTED elevation data to the World Equidistant Cylindrical coordinate system. Each cell in this dataset was assigned three characteristics: slope based on 3-km neighborhood, relief based on 6 km neighborhood, and profile based on 6-km neighborhood. The last step was to overlay the combination of these three characteristics with areas that are exclusively plains. Slope is the percentage of the 3-km neighborhood occupied by gentle slope. Hammond specified 8% as the threshold for gentle slope. Slope is used to define how flat or steep the terrain is. Slope was classified into one of four classes: Percent of neighborhood over 8% of slopeSlope Classes0 - 20%40021% -50%30051% - 80%200>81% 100Local Relief is the difference between the maximum and minimum elevation within in the 6-km neighborhood. Local relief is used to define terrain how rugged or the complexity of the terrain"s texture. Relief was assigned one of six classes:Change in elevationRelief Class ID0 – 30 meters1031 meter – 90 meters2091 meter – 150 meters30151 meter – 300 meters40301 meter – 900 meters50>900 meters60The combination of slope and relief begin to define terrain as mountains, hills and plains. However, the difference between mountains or hills and tablelands cannot be distinguished using only these parameters. Profile is used to determine tableland areas. Profile identifies neighborhoods with upland and lowland areas, and calculates the percent area of gently sloping terrain within those upland and lowland areas. A 6-km circular neighborhood was used to calculate the profile parameter. Upland/lowland is determined by the difference between average local relief and elevation. In the 6-km neighborhood window, if the difference between maximum elevation and cell’s elevation is smaller than half of the local relief it’s an upland. If the difference between maximum elevation and cell’s elevation is larger than half of the local relief it’s a lowland. Profile was assigned one of five classes:Percent of neighborhood over 8% slope in upland or lowland areasProfile ClassLess than 50% gentle slope is in upland or lowland0More than 75% of gentle slope is in lowland150%-75% of gentle slope is in lowland250-75% of gentle slope is in upland3More than 75% of gentle slope is in upland4Early reviewers of the resulting classes noted one confusing outcome, which was that areas were classified as "plains with low mountains", or "plains with hills" were often mostly plains, and the hills or mountains were part of an adjacent set of exclusively identified hills or mountains. To address this areas that are exclusively plains were produced, and used to override these confusing areas. The hills and mountains within those areas were converted to their respective landform class. The combination of slope, relief and profile merged with the areas of plains, can be better understood using the following diagram, which uses the colors in this layer to show which classes are present and what parameter values produced them: What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop. Restricted single source analysis means this layer has size constraints for analysis and it is not recommended for use with other layers in multisource analysis. This layer is part of a larger collection of landscape layers that you can use to perform a wide variety of mapping and analysis tasks. The Living Atlas of the World provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics. Geonet is a good resource for learning more about landscape layers and the Living Atlas of the World. To get started see the Living Atlas Discussion Group. The Esri Insider Blog provides an introduction to the Ecophysiographic Mapping project.

Permit records from the City of Seattle permitting system for building permits that create or demolish housing units. Records begin in 1990 and are through the current year quarter.The permits in this layer are those that are currently issued. This data does not contain records for those permits that were issued but were not completed, cancelled or withdrawn.Each record represents the number of units added or demolished for each housing type in the project. Therefore a single building permit may appear multiple times if there are a mix of unit types in the project.Housing unit types reflect the unit types regulated by the building codes and change through time. There has been no attempt to standardize these types and therefore reflect the unit types that existed at the time the permit was issued.There may be multiple permits at any given address.