The hachure cartographic technique sketches downhill lines along bands of equal elevation to create a topographic effect. This is a rather vintage technique, giving way in the digital age to hillshading. But, shoot, there is just something wonderful about a hachured map. It has a wonderful textural quality and effectively and efficiently conveys topographic aspect and slope. This style is in a manner in keeping with that retro hand-drawn aesthetic, with inky colors, wavy-hand linework, and grainy sketchy downhill strokes.The hachures themselves are available in a few flavors ranging from simple sketched contour lines to densely packed hachures for an almost fur-like surface. Eh, why not? Also available are a handful of tuft-like point features and a few vintage polygon fills like parchment and foxed atlas paper.Let your inner cARRRRRRtographer run wild.Thanks to cartographer Jared Fischer, of the Dept. of the Interior, for his collaboration and inspiration along the way.Find more, larger, examples here.Happy Hachure Mapping! John Nelson

Raster functions are operations that apply processing directly to raster dataset pixels. The raster functions supplied here are the same operations applied to the 3 ft. DEM-related web services from NC OneMap (Aspect, Hillshade, Shaded Elevation, Shaded Relief, Slope, and raster contours for 1 foot, 2 feet, 4 feet, 20 feet, and 100 feet). The downloaded functions can be used in ArcGIS products.

These could be helpful if there is a need to use an NC OneMap DEM-derivative elevation product in a disconnected environment, an instance where web service use is not practical. The county-based DEMs can be downloaded and the raster functions applied in ArcGIS Pro, for use in an offline environment.

In the downloaded raster functions ZIP file are XML files for:

 Aspect
 Hillshade
 Shaded Elevation
 Shaded Relief
 Slope
 Raster Contours for intervals: 1 ft., 2 ft., 4 ft., 20 ft., 100 ft.

Information on using raster functions in ArcGIS Pro can be found here.

This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.

The goal of this project is to create a map of the planet Mars, by using ESRI software. For this, a 3D project was developed using ArcGIS Pro, considering a global scene, to be published in an online platform. All the various data from Mars will be available in a single website, where everyone can visualize and interact. The Red Planet has been studied for many decades and this year marks the launch of a new rover, Mars2020, which will happen on the 17th of July. This new rover will be continuing the on-going work of the Curiosity Rover, launched in 2012. The main objective for these rovers is to determine if Mars could have supported life, by studying its water, climate and geology. Currently, the only operational rover in Mars is Curiosity and with that in mind, this project will have a strong focus on the path taken by this rover, during almost 8 years of exploration. In the web application, the user will be able to see the course taken by Curiosity in Mars’ Gale Crater, from its landing until January 2020. The map highlights several points of interest, such as the location after each year passed on MarsEarth year and every kilometer, which can be interacted with as well as browse through photos taken at each of the locations, through a pop-up window. Additionally, the application also supports global data of Mars. The two main pieces, used as basemaps, are the global imagery, with a pixel size of 925 meters and the Digital Elevation Model (DEM), with 200 meters per pixel. The DEM represents the topography of Mars and was also used to develop Relief and Slope Maps. Furthermore, the application also includes data regarding the geology of the planet and nomenclature to identify regions, areas of interest and craters of Mars. This project wouldn’t have been possible without NASA’s open-source philosophy, working alongside other entities, such as the European Space Agency, the International Astronomical Union and the Working Group for Planetary System Nomenclature. All the data related to Imagery, DEM raster files, Mars geology and nomenclature was obtained on USGS Astrogeology Science Center database. Finally, the data related to the Curiosity Rover was obtained on the portal of The Planetary Society. Working with global datasets means working with very large files, so selecting the right approach is crucial and there isn’t much margin for experiments. In fact, a wrong step means losing several hours of computing time. All the data that was downloaded came in Mars Coordinate Reference Systems (CRS) and luckily, ESRI handles that format well. This not only allowed the development of accurate analysis of the planet, but also modelling the data around a globe. One limitation, however, is that ESRI only has the celestial body for planet Earth, so this meant that the Mars imagery and elevation was wrapped around Earth. ArcGIS Pro allows CRS transformation on the fly, but rendering times were not efficient, so the workaround was to project all data into WGS84. The slope map and respective reclassification and hillshading was developed in the original CRS. This process was done twice: one globally and another considering the Gale Crater. The results show that the crater’s slope characteristics are quite different from the global panorama of Mars. The crater has a depression that is approximately 5000 meters deep, but at the top it’s possible to identify an elevation of 750 meters, according to the altitude system of Mars. These discrepancies in a relatively small area result in very high slope values. Globally, 88% of the area has slopes less than 2 degrees, while in the Gale Crater this value is only 36%. Slopes between 2 and 10 degrees represent almost 60% of the area of the crater. On the other hand, they only represent 10% of the area globally. A considerable area with more than 10 degrees of slope can also be found within the crater, but globally the value is less than 1%. By combining Curiosity’s track path with the DEM, a profile graph of the path was obtained. It is possible to observe that Curiosity landed in a flat area and has been exploring in a “steady path”. However, in the last few years (since the 12th km), the rover has been more adventurous and is starting to climb the crater. In the last 10 km of its journey, Curiosity “climbed” around 300 meters, whereas in the first 11 km it never went above 100 meters. With the data processed in the WGS84 system, all was ready to start modelling Mars, which was firstly done in ArcGIS Pro. When the data was loaded, symbology and pop-ups configured, the project was exported to ArcGIS Online. Both the imagery and elevation layer were exported as “hosted tile service”. This was a key step, since keeping the same level of detail online and offline would have a steep increase in imagery size, to hundreds of Terabytes, thus a lot of work was put into balancing tile cache size and the intended quality of imagery. For the remaining data, it was a straight-forward step, exporting these files as vectors. Once all the data was in the Online Portal, a Global Web Scene was developed. This is an on-going project with an outlook to develop the global scene into an application with ESRI’s AppBuilder, allowing the addition of more information. In the future, there is also interest to increment the displayed data, like adding the paths taken by other rovers in the past, alongside detailed imagery of other areas beyond the Gale Crater. Finally, with 2021 being the year when the new rover Mars2020 will land on the Red Planet, we might be looking into adding it to this project.https://arcg.is/KuS4r

scripts.zip

arcgisTools.atbx: terrainDerivatives: make terrain derivatives from digital terrain model (Band 1 = TPI (50 m radius circle), Band 2 = square root of slope, Band 3 = TPI (annulus), Band 4 = hillshade, Band 5 = multidirectional hillshades, Band 6 = slopeshade). rasterizeFeatures: convert vector polygons to raster masks (1 = feature, 0 = background).

makeChips.R: R function to break terrain derivatives and chips into image chips of a defined size. makeTerrainDerivatives.R: R function to generated 6-band terrain derivatives from digital terrain data (same as ArcGIS Pro tool). merge_logs.R: R script to merge training logs into a single file. predictToExtents.ipynb: Python notebook to use trained model to predict to new data. trainExperiments.ipynb: Python notebook used to train semantic segmentation models using PyTorch and the Segmentation Models package. assessmentExperiments.ipynb: Python code to generate assessment metrics using PyTorch and the torchmetrics library. graphs_results.R: R code to make graphs with ggplot2 to summarize results. makeChipsList.R: R code to generate lists of chips in a directory. makeMasks.R: R function to make raster masks from vector data (same as rasterizeFeatures ArcGIS Pro tool).

terraceDL.zip

dems: LiDAR DTM data partitioned into training, testing, and validation datasets based on HUC8 watershed boundaries. Original DTM data were provided by the Iowa BMP mapping project: https://www.gis.iastate.edu/BMPs. extents: extents of the training, testing, and validation areas as defined by HUC 8 watershed boundaries. vectors: vector features representing agricultural terraces and partitioned into separate training, testing, and validation datasets. Original digitized features were provided by the Iowa BMP Mapping Project: https://www.gis.iastate.edu/BMPs.

The Topography Toolbox has been updated and expanded for ArcGIS Pro. Tools calculate:McCune and Keon (2002) Heat Load IndexSlope Position ClassificationTopographic Convergence/Wetness IndexTopographic Position IndexMultiscale Topographic Position IndexHeight Above Nearest DrainageHeight Above RiverVector Ruggedness MeasureLocalized Vector Ruggedness MeasureWind Exposure/Shelter IndexHypsometric Integral

The land base of the Pacific Northwest includes large areas that could support hardwoods or a hardwood component. Often, however, site index, the most commonly used measure of a site's potential productivity, is not available for red alder as other species occupy the site. In order to make site-specific management decisions, the suitability for red alder production can be assessed by geographic and topographic position, soil moisture and aeration during the growing season, and soil fertility and physical condition (Harrington 1986). The difficulty of weighing these physical factors to determine site suitability appears to be a major impediment to the establishment of red alder plantations. Additionally, forest managers are lacking a planning tool that would consider red alder in the landscape for long term management plans. To assist forest managers in their planning and site selection efforts, we developed a GIS-based Red Alder Site Suitability Model based on physical criteria identified by Harrington (1986) as most influential on the productivity of red alder. The major components of the model are elevation, topographic position, slope, aspect, soil type, and soil depth. The model was implemented in a GIS (ESRI ArcPro v.3.0) raster environment with topographic position, slope, aspect, and elevation derived from a 10-meter digital elevation model (DEM), using lidar data where available. Topographic position class of valley, lower slope, flat slope, middle slope, upper slope, or ridgetop was derived from the topographic position index (TPI) using standard deviation thresholds as described by Weiss (2001). The soil texture and depth were derived from Washington DNR’s corporate soil data layer. Each pixel was then classified and assigned one of four suitability categories: High, Medium, Low, and No Potential. Because of the level of spatial detail of the model, forest managers can assess the potential of red alder management on any given site, such as planned timber harvest. Additionally, the model can be used at a larger scale, i.e. planning for future product diversification in a watershed.The model has been cursorily field-verified on existing red alder plantations and compared with locations and site index of natural red alder stands for DNR's forest inventory system. Initial results indicate that the model is accurate in identifying sites with potential for intensive red alder management. Local knowledge will still be an important factor in the application of the model. Frost pockets or areas susceptible to other physical damage such as ice damage (i.e. within the east wind drafts of the Columbia River Gorge) are not identified in by this model. The usefulness of this model will be determined by the experience of the field staff over time. References:Harrington, Constance A. 1986. A method of site quality evaluation for red alder. Gen. Tech. Rep. PNW-GTR-192. Portland, OR: U.S. Department of Agriculture, Forest Service, Pacific Northwest Research Station. 22 p. https://doi.org/10.2737/PNW-GTR-192Weiss, A. 2001. Topographic position and landforms analysis. In Poster presentation, ESRI user conference, San Diego, CA (Vol. 200). http://www.jennessent.com/downloads/tpi-poster-tnc_18x22.pdf

scripts.zip

arcgisTools.atbx: terrainDerivatives: make terrain derivatives from digital terrain model (Band 1 = TPI (50 m radius circle), Band 2 = square root of slope, Band 3 = TPI (annulus), Band 4 = hillshade, Band 5 = multidirectional hillshades, Band 6 = slopeshade). rasterizeFeatures: convert vector polygons to raster masks (1 = feature, 0 = background).

makeChips.R: R function to break terrain derivatives and chips into image chips of a defined size. makeTerrainDerivatives.R: R function to generated 6-band terrain derivatives from digital terrain data (same as ArcGIS Pro tool). merge_logs.R: R script to merge training logs into a single file. predictToExtents.ipynb: Python notebook to use trained model to predict to new data. trainExperiments.ipynb: Python notebook used to train semantic segmentation models using PyTorch and the Segmentation Models package. assessmentExperiments.ipynb: Python code to generate assessment metrics using PyTorch and the torchmetrics library. graphs_results.R: R code to make graphs with ggplot2 to summarize results. makeChipsList.R: R code to generate lists of chips in a directory. makeMasks.R: R function to make raster masks from vector data (same as rasterizeFeatures ArcGIS Pro tool).

vfillDL.zip

dems: LiDAR DTM data partitioned into training, three testing, and two validation datasets. Original DTM data were obtained from 3DEP (https://www.usgs.gov/3d-elevation-program) and the WV GIS Technical Center (https://wvgis.wvu.edu/) . extents: extents of the training, testing, and validation areas. These extents were defined by the researchers. vectors: vector features representing valley fills and partitioned into separate training, testing, and validation datasets. Extents were created by the researchers.

The Terrain Ruggedness Index (TRI) is used to express the amount of elevation difference between adjacent cells of a DEM. This raster function template is used to generate a visual representation of the TRI with your elevation data. The results are interpreted as follows:0-80m is considered to represent a level terrain surface81-116m represents a nearly level surface117-161m represents a slightly rugged surface162-239m represents an intermediately rugged surface240-497m represents a moderately rugged surface498-958m represents a highly rugged surface959-4367m represents an extremely rugged surfaceWhen to use this raster function templateThe main value of this measurement is that it gives a relatively accurate view of the vertical change taking place in the terrain model from cell to cell. The TRI provides data on the relative change in height of the hillslope (rise), such as the side of a canyon.How to use this raster function templateIn ArcGIS Pro, search ArcGIS Living Atlas for raster function templates to apply them to your imagery layer. You can also download the raster function template, attach it to a mosaic dataset, and publish it as an image service. The output is a visual TRI representation of your imagery. This index supports elevation data.References:Raster functionsApplicable geographiesThe index is a standard index which is designed to work globally.

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 -