This feature class is updated every business day using Python scripts and the WellNet database. Please disregard the "Date Updated" field as it does not keep in sync with DWR's internal enterprise geodatabase updates. The NDWR's water monitoring database contains information related to sites for groundwater measurements. These data are used by NDWR to assess the condition of the groundwater and surface water systems over time and are available to the public on NDWR’s website. Groundwater measurement sites are chosen based on physical location and access considerations, permit terms, and to maximize the distribution of measurement points in a given basin.Groundwater monitoring sites are typically chosen based on spatial location, access, and period of record considerations. When possible NDWR tries to have a distribution of monitoring locations within a given hydrographic area. The entity who does the monitoring depends on the site – for example, some mines have well fields where they collect data and submit those data to NDWR as a condition of their monitoring plan – and some sites are monitored by NDWR staff annually or more frequently. While people can volunteer to have their well monitored, more often the NDWR staff who measure water levels recommend an additional site or staff in the office recommend alternate sites. The Chief of the Hydrology Section will review the recommendations and make a final decision on adding/changing a site. This dataset is updated every business day from a non-spatial SQL Server database using lat/long coordinates to display location. This feature class participates in a relationship class with a groundwater measure table joined using the sitename field. This dataset contains both active and inactive sites. Measurement data is provided by reporting agencies and by regular site visits from NDWR staff. For website access, please see the Water Levels site at water.nv.gov/WaterLevelData.aspx

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 -

An updated Permit Data Model that includes relationships between the component feature classes. The Dissolved Use Impacts (SDOT.V_SU_PERMIT_USE_IMPACT_DISS) feature class is derived from dissolving the Use Impacts (SDOT.V_SU_PERMIT_USE_IMPACTS) feature class by Permit Number. The Impacts feature class is the Use Impact street line segments that are associated with any give Permit point (V_SU_PERMITS). The relationships connect the Permit points to the Dissolved Use Impacts and then the Dissolved Use Impacts to the component Use Impacts. This data model allows you to see all impacted street line segments associated with any given Permit easily, while also being able to drill down to any specific Use Impact for a given Permit. Service is constructed for use in the Right of Way Map. Data set to Nightly Refresh. Any Questions or Concerns contact the SDOT Street Use Data and GIS Team: Craig Moore/Bryan Bommersbach

Level 3 Parcel Data Standard Compliant parcel boundaries for West Tisbury, MA. A 1-M relationship class exists from the parcels to the Assess table and from parcels to the Building table. The building table is an additional table (not part of the Level 3 Standard). Building info was provided by the Town assessor in late early 2020. The building table only provides info for one building on the parcel. Which building (i.e. oldest, newest, etc) is unknown. Use data with caution.

MassGIS Level 3 Parcel Data: Data Fiscal Year: Aquinnah 2019, Chilmark 2021, Edgartown 2021, Gosnold 2015, Oak Bluffs 2021, Tisbury 2021, West Tisbury 2021.Building Info Table: Acquired by MVC from Town Assessors in FY20.Downloaded from MassGIS,, this polygon file represents the parcel bounds for the 7 towns in Dukes County MA (Aquinnah, Chilmark, Edgartown, Godnold, Oak Bluffs, Tisbury, West Tisbury). Each town has their own parcel data consultant and then the data are forwarded to MassGIS for final processing. All data comply with the MassGIS Level 3 Parcel Data Standard. This file geodatabase only includes the TaxPar feature class and Assess table for each town. All TaxPar feature classes were appended into one feature class (Parcels_duk) by the MVC.Each assess table is utilized in that town's respective relationship join (1 to Many) for linking the parcel polygon to the related record(s) in the Assess table. The Assess Table contains info about ownership and assessed values. This is not a detailed building table. If there are multiple owners associated with a property, then the Assess table will have multiple records for that property/parcel (such as for condo parcels).Each building table is utilized in that town's respective relationship join (1 to Many) for linking the parcel polygon to the related record(s) in the Bldg table. The Bldg (building) table contains info about each building on the parcel (such as number of bedrooms, number of bathrooms, the living area square footage, etc.). NOTES of CAUTION: The Living Area Square Footage may not represent the exact same thing in each town. As a generalization, Living Area is interior space that is heated. Regarding West Tisbury, their building table only contains info for one building on the parcel. It is uncertain at this time if the info is the most recent, most primary, or some kind of summarization where multiple buildings on a parcel exist.The field of [assess_mYB] represents the Minimum/Earliest Year Built for any building on the parcel and is appended to the TaxPar feature class based on an analysis of the info provided in the building table. This field [assess_mYB] is utilized in the Historic Structures App found in ArcGIS OnLine.

River invertebrate data, survey metrics & taxa data joined to Sites data via relationship class in ArcGIS Pro

Data Model Schema, Feature Attributes, Relationship Classes, Field Domains (Version 2, 2019)

View Layer of the published relationship class of fish stocking events by the UDWR between 1979 and 2023.View Layer symbology was configured and editability disabled.Feature layer(s) with a relationship class created with the 'DWR_Fish_Stocking_1979_2023'' table via the DWR_WATER_ID field.'UDWRStreams' and 'UDWRLakes' layers lasted updated on 01/29/2025.Fish stocking data was exported from the Microsoft Access stocking database, which is located at S:\DWR\FISH\Historic Stocking. Stocking records through 2023 are included.Spatial representation of the locations, quantity, and type of fish species stocked by the UDWR from 1979 to 2023.

The file geodatabase was obtained by the State Water Resources Control Board and was clipped to the North Coast Region, Region 1. Fields were added to the layers within the geodatabase, which include Impairment, Temperature, and Sedimentation. The Impairment field that was added shows the specific impairment the feature was listed under the Clean Water Act Section 303(d). The Temperature and Sedimentation fields were added to show whether the specific feature was listed under one of these impairments. Relationship class was created within the Lines and Polygon layers to further inform the user on listings and impairments. Point of Contact: Lance Le, Water Resource Control Engineer in the Planning and Watershed Stewardship Division in The North Coast Regional Water Quality Control Board. Email: Lance.Le@Waterboards.ca.govDisclaimer: This data information can change at anytime and should only be used as a general reference.

Level 3 Parcel Data Standard Compliant parcel boundaries for Tisbury, MA. A 1-M relationship class exists from the parcels to the Assess table and from parcels to the Building table.The building table is an additional table (not part of the Level 3 Standard). Building info was provided by the Town assessor in late 2019/early 2020.

River invertebrate data, survey metrics & taxa data joined to Sites data via relationship class in ArcGIS Pro

Level 3 Parcel Data Standard Compliant parcel boundaries for Chilmark, MA. A 1-M relationship class exists from the parcels to the Assess table and from parcels to the Building table. The building table is an additional table (not part of the Level 3 Standard). Building info was provided by the Town assessor in late early 2020.

An accurate depiction of the spatial distribution of habitat types within California is required for a variety of legislatively-mandated government functions. The California Department of Forestry and Fire Protection's CALFIRE Fire and Resource Assessment Program (FRAP), in cooperation with California Department of Fish and Wildlife VegCamp program and extensive use of USDA Forest Service Region 5 Remote Sensing Laboratory (RSL) data, has compiled the "best available" land cover data available for California into a single comprehensive statewide data set. The data span a period from approximately 1990+. Typically the most current, detailed and consistent data were collected for various regions of the state. Decision rules were developed that controlled which layers were given priority in areas of overlap. Cross-walks were used to compile the various sources into the common classification scheme, the California Wildlife Habitat Relationships (CWHR) system. This service depicts the WHRTYPE description from the fveg dataset (Wildlife Habitat Relationship classes). The full dataset can be downloaded in raster format here: GIS Mapping and Data Analytics | CAL FIRE The service represents the latest release of the data, and is updated when a new version is released. Currently it represents fveg22_1.

This feature class represents the petitioned water master plan areas that have been introduced in previous years through cycle amendments within Baltimore County. Unlike the WHisMasterPlan feature class, this feature class does not distinguish between different cycle amendment petitions and only reflects the most current water master plan designation.The water master plan geodatabase includes a feature data set (WaterMasterPlan) containing three feature classes: WCurMasterPlan, WaterCombined and WHisMasterPlan. The feature classes participate in a topology (tWaterMasterPlan). The WCurMasterPlan feature class represents the petitions for the current cycle. The WaterCombined represents the current master plan designation within the county. The WHisMasterPlan contains all of the petitions areas from all cycles. The geodatabase includes relationship classes that associate related table containing information on assessments, councilmanic districts, election districts, lineage (feature level metadata), plan map, recommendations and zoning designations.

Sixty-seven maps from Indian Land Cessions in the United States, compiled by Charles C. Royce and published as the second part of the two-part Eighteenth Annual Report of the Bureau of American Ethnology to the Secretary of the Smithsonian Institution, 1896-1897 have been scanned, georeferenced in JPEG2000 format, and digitized to create this feature class of cession maps. The mapped cessions and reservations included in the 67 maps correspond to entries in the Schedule of Indian Land Cessions, indicating the number and location of each cession by or reservation for the Indian tribes from the organization of the Federal Government to and including 1894, together with descriptions of the tracts so ceded or reserved, the date of the treaty, law or executive order governing the same, the name of the tribe or tribes affected thereby, and historical data and references bearing thereon, as set forth in the subtitle of the Schedule. Go to this URL for full metadata: https://data.fs.usda.gov/geodata/edw/edw_resources/meta/S_USA.TRIBALCEDEDLANDS.xml Each Royce map was georeferenced against one or more of the following USGS 1:2,000,000 National Atlas Feature Classes contained in \NatlAtlas_USGS.gdb: cities_2mm, hydro_ln_2mm, hydro_pl_2mm, plss_2mm, states_2mm. Cessions were digitized as a file geodatabase (GDB) polygon feature class, projected as NAD83 USA_Contiguous_Lambert_Conformal_Conic, which is the same projection used to georeference the maps. The feature class was later reprojected to WGS 1984 Web Mercator (auxiliary sphere) to optimize it for the Tribal Connections Map Viewer. Polygon boundaries were digitized as to not deviate from the drawn polygon edge to the extent that space could be seen between the digitized polygon and the mapped polygon at a viewable scale. Topology was maintained between coincident edges of adjacent polygons. The cession map number assigned by Royce was entered into the feature class as a field attribute. The Map Cession ID serves as the link referencing relationship classes and joining additional attribute information to 752 polygon features, to include the following: 1. Data transcribed from Royce's Schedule of Indian Land Cessions: a. Date(s), in the case of treaties, the date the treaty was signed, not the date of the proclamation; b. Tribe(s), the tribal name(s) used in the treaty and/or the Schedule; and c. Map Name(s), the name of the map(s) on which a cession number appears; 2. URLs for the corresponding entry in the Schedule of Indian Land Cessions (Internet Archive) for each unique combination of a Date and reference to a Map Cession ID (historical references in the Schedule are included); 3. URLs for the corresponding treaty text, including the treaties catalogued by Charles J. Kappler in Indian Affairs: Laws and Treaties (HathiTrust Digital Library), executive order or other federal statute (Library of Congress and University of Georgia) identified in each entry with a reference to a Map Cession ID or IDs; 4. URLs for the image of the Royce map(s) (Library of Congress) on which a given cession number appears; 5. The name(s) of the Indian tribe or tribes related to each mapped cession, including the name as it appeared in the Schedule or the corresponding primary text, as well as the name of the present-day Indian tribe or tribes; and 6. The present-day states and counties included wholly or partially within a Map Cession boundary. During the 2017-2018 revision of the attribute data, it was noted that 7 of the Cession Map IDs are missing spatial representation in the Feature Class. The missing data is associated with the following Cession Map IDs: 47 (Illinois 1), 65 (Tennessee and Bordering States), 128 (Georgia), 129 (Georgia), 130 (Georgia), 543 (Indian Territory 3), and 690 (Iowa 2), which will be updated in the future. This dataset revises and expands the dataset published in 2015 by the U.S. Forest Service and made available through the Tribal Connections viewer, the Forest Service Geodata Clearinghouse, and Data.gov. The 2018 dataset is a result of collaboration between the Department of Agriculture, U.S. Forest Service, Office of Tribal Relations (OTR); the Department of the Interior, National Park Service, National NAGPRA Program; the U.S. Environmental Protection Agency, Office of International and Tribal Affairs, American Indian Environmental Office; and Dr. Claudio Saunt of the University of Georgia. The Forest Service and Dr. Saunt independently digitized and georeferenced the Royce cession maps and developed online map viewers to display Native American land cessions and reservations. Dr. Saunt subsequently undertook additional research to link Schedule entries, treaty texts, federal statutes and executive orders to cession and reservation polygons, which he agreed to share with the U.S. Forest Service. OTR revised the data, linking the Schedule entries, treaty texts, federal statues and executive orders to all 1,172 entries in the attribute table. The 2018 dataset has incorporated data made available by the National NAGPRA Program, specifically the Indian tribe or tribes related to each mapped cession, including the name as it appeared in the Schedule or the corresponding primary text and the name of the present-day Indian tribe or tribes, as well as the present-day states and counties included wholly or partially within a Map Cession boundary. This data replaces in its entirety the National NAGPRA data included in the dataset published in 2015. The 2015 dataset incorporated data presented in state tables compiled from the Schedule of Indian Land Cessions by the National NAGPRA Program. In recent years the National NAGPRA Program has been working to ensure the accuracy of this data, including the reevaluation of the present-day Indian tribes and the provision of references for their determinations. Changes made by the OTR have not been reviewed or approved by the National NAGPRA Program. The Forest Service will continue to collaborate with other federal agencies and work to improve the accuracy of the data included in this dataset. Errors identified since the dataset was published in 2015 have been corrected, and we request that you notify us of any additional errors we may have missed or that have been introduced. Please contact Rebecca Hill, Policy Analyst, U.S. Forest Service, Office of Tribal Relations, at rebeccahill@fs.usda.gov with any questions or concerns with regard to the data included in this dataset.

This feature class represents the petitioned sewer master plan areas that have been introduced in previous years through cycle amendments within Baltimore County. Unlike the SHisMasterPlan feature class, this feature class does not distinguish between different cycle amendment petitions and only reflects the most current sewer master plan designation.The sewer master plan geodatabase includes a feature data set (sewerMasterPlan) containing three feature classes: SCurMasterPlan, sewerCombined and SHisMasterPlan. The feature classes participate in a topology (tsewerMasterPlan). The SCurMasterPlan feature class represents the petitions for the current cycle. The sewerCombined represents the current master plan designation within the county. The SHisMasterPlan contains all of the petitions areas from all cycles. The geodatabase includes relationship classes that associate related table containing information on assessments, councilmanic districts, election districts, lineage (feature level metadata), plan map, recommendations and zoning designations.

Level 3 Parcel Data Standard Compliant parcel boundaries for Edgartown, MA. A 1-M relationship class exists from the parcels to the Assess table and from parcels to the Building table.The building table is an additional table (not part of the Level 3 Standard). Building info was provided by the Town assessor in late 2019/early 2020.

Level 3 Parcel Data Standard Compliant parcel boundaries for Oak Bluffs, MA. A 1-M relationship class exists from the parcels to the Assess table and from parcels to the Building table.The building table is an additional table (not part of the Level 3 Standard). Building info was provided by the Town assessor in late 2019/early 2020.

The primary purpose of this feature class is use by the City of Puyallup Public Works Water Division for field locations and fire hydrant data tracking. This feature class is also used by City of Puyallup staff to check the availability of fire hydrants in relationship to other City projects. The feature class may also be used by individuals wanting to learn the location of the fire hydrants within the City of Puyallup and within the Fruitland Mutual Water and Tacoma Water Incorporated area. City of Puyallup will not be maintaining the fire hydrant locations that exist outside of the City of Puyallup water service area limit.

Point feature class and related table containing the Precise Surveys measurement time series. Measurements include elevations, Northings and Eastings, distances, and point-to-point measurements. Northing and Easting measurements are in CA State Plane Coordinate systems, Elevations measurements are provided in NAVD88 or NGVD29. This dataset is for data exploration only. These measurements and point locations are not considered survey-grade since there may be nuances such as epochs, adjustments, and measurement methods that are not fully reflected in the GIS data. These values are not considered authoritative values and should not be used in-lieu of actual surveyed values provided by a licensed land surveyor. Related data and time series are stored in a table connected to the point feature class via a relationship class. There may be multiple table entries and time series associated to a single mark. Data was assembled through an import of Excel tables and import of mark locations in ArcGIS Pro. Records were edited by DOE, Geomatics, GDSS to resolve any non-unique mark names. This dataset was last updated 4/2024.