FOR PLAT MAPS AND OTHER LAND DOCUMENTS, PLEASE VISIT THE COUNTY CLERK’S OFFICIAL RECORDS SEARCH: HTTPS://BEXAR.TX.PUBLICSEARCH.US.The Bexar County GIS Team does not have purview over plat maps and other land records. Please visit the Bexar County Clerk’s Official Records Search.

Minnesota's original public land survey plat maps were created between 1848 and 1907 during the first government land survey of the state by the U.S. Surveyor General's Office. This collection of more than 3,600 maps includes later General Land Office (GLO) and Bureau of Land Management maps up through 2001. Scanned images of the maps are available in several digital formats and most have been georeferenced.

The survey plat maps, and the accompanying survey field notes, serve as the fundamental legal records for real estate in Minnesota; all property titles and descriptions stem from them. They also are an essential resource for surveyors and provide a record of the state's physical geography prior to European settlement. Finally, they testify to many years of hard work by the surveying community, often under very challenging conditions.

The deteriorating physical condition of the older maps (drawn on paper, linen, and other similar materials) and the need to provide wider public access to the maps, made handling the original records increasingly impractical. To meet this challenge, the Office of the Secretary of State (SOS), the State Archives of the Minnesota Historical Society (MHS), the Minnesota Department of Transportation (MnDOT), MnGeo and the Minnesota Association of County Surveyors collaborated in a digitization project which produced high quality (800 dpi), 24-bit color images of the maps in standard TIFF, JPEG and PDF formats - nearly 1.5 terabytes of data. Funding was provided by MnDOT.

In 2010-11, most of the JPEG plat map images were georeferenced. The intent was to locate the plat images to coincide with statewide geographic data without appreciably altering (warping) the image. This increases the value of the images in mapping software where they can be used as a background layer.

This ownership dataset utilizes a methodology that results in a federal ownership extent that matches the Federal Responsibility Areas (FRA) footprint from CAL FIRE's State Responsibility Areas for Fire Protection (SRA) data. FRA lands are snapped to county parcel data, thus federal ownership areas will also be snapped. Since SRA Fees were first implemented in 2011, CAL FIRE has devoted significant resources to improve the quality of SRA data. This includes comparing SRA data to data from other federal, state, and local agencies, an annual comparison to county assessor roll files, and a formal SRA review process that includes input from CAL FIRE Units. As a result, FRA lands provide a solid basis as the footprint for federal lands in California (except in the southeastern desert area). The methodology for federal lands involves:

Parcels and Land Ownership dataset current as of 2010. Parcel map was generated based on DeKalb County street centerline, ROW from DeKalb tax map, building structure and DeKalb tax map..

To access parcel information:Enter an address or zoom in by using the +/- tools or your mouse scroll wheel. Parcels will draw when zoomed in.Click on a parcel to display a popup with information about that parcel.Click the "Basemap" button to display background aerial imagery.From the "Layers" button you can turn map features on and off.Complete Help (PDF)Parcel Legend:Full Map LegendAbout this ViewerThis viewer displays land property boundaries from assessor parcel maps across Massachusetts. Each parcel is linked to selected descriptive information from assessor databases. Data for all 351 cities and towns are the standardized "Level 3" tax parcels served by MassGIS. More details ...Read about and download parcel dataUpdatesV 1.1: Added 'Layers' tab. (2018)V 1.2: Reformatted popup to use HTML table for columns and made address larger. (Jan 2019)V 1.3: Added 'Download Parcel Data by City/Town' option to list of layers. This box is checked off by default but when activated a user can identify anywhere and download data for that entire city/town, except Boston. (March 14, 2019)V 1.4: Data for Boston is included in the "Level 3" standardized parcels layer. (August 10, 2020)V 1.4 MassGIS, EOTSS 2021

This dataset was updated April, 2024.This ownership dataset was generated primarily from CPAD data, which already tracks the majority of ownership information in California. CPAD is utilized without any snapping or clipping to FRA/SRA/LRA. CPAD has some important data gaps, so additional data sources are used to supplement the CPAD data. Currently this includes the most currently available data from BIA, DOD, and FWS. Additional sources may be added in subsequent versions. Decision rules were developed to identify priority layers in areas of overlap.Starting in 2022, the ownership dataset was compiled using a new methodology. Previous versions attempted to match federal ownership boundaries to the FRA footprint, and used a manual process for checking and tracking Federal ownership changes within the FRA, with CPAD ownership information only being used for SRA and LRA lands. The manual portion of that process was proving difficult to maintain, and the new method (described below) was developed in order to decrease the manual workload, and increase accountability by using an automated process by which any final ownership designation could be traced back to a specific dataset.The current process for compiling the data sources includes: Clipping input datasets to the California boundary Filtering the FWS data on the Primary Interest field to exclude lands that are managed by but not owned by FWS (ex: Leases, Easements, etc) Supplementing the BIA Pacific Region Surface Trust lands data with the Western Region portion of the LAR dataset which extends into California. Filtering the BIA data on the Trust Status field to exclude areas that represent mineral rights only. Filtering the CPAD data on the Ownership Level field to exclude areas that are Privately owned (ex: HOAs) In the case of overlap, sources were prioritized as follows: FWS > BIA > CPAD > DOD As an exception to the above, DOD lands on FRA which overlapped with CPAD lands that were incorrectly coded as non-Federal were treated as an override, such that the DOD designation could win out over CPAD.In addition to this ownership dataset, a supplemental _source dataset is available which designates the source that was used to determine the ownership in this dataset.Data Sources: GreenInfo Network's California Protected Areas Database (CPAD2023a). https://www.calands.org/cpad/; https://www.calands.org/wp-content/uploads/2023/06/CPAD-2023a-Database-Manual.pdf US Fish and Wildlife Service FWSInterest dataset (updated December, 2023). https://gis-fws.opendata.arcgis.com/datasets/9c49bd03b8dc4b9188a8c84062792cff_0/explore Department of Defense Military Bases dataset (updated September 2023) https://catalog.data.gov/dataset/military-bases Bureau of Indian Affairs, Pacific Region, Surface Trust and Pacific Region Office (PRO) land boundaries data (2023) via John Mosley John.Mosley@bia.gov Bureau of Indian Affairs, Land Area Representations (LAR) and BIA Regions datasets (updated Oct 2019) https://biamaps.doi.gov/bogs/datadownload.htmlData Gaps & Changes:Known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. Additionally, any feedback received about missing or inaccurate data can be taken back to the appropriate source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.24_1: Input datasets this year included numerous changes since the previous version, particularly the CPAD and DOD inputs. Of particular note was the re-addition of Camp Pendleton to the DOD input dataset, which is reflected in this version of the ownership dataset. We were unable to obtain an updated input for tribral data, so the previous inputs was used for this version.23_1: A few discrepancies were discovered between data changes that occurred in CPAD when compared with parcel data. These issues will be taken to CPAD for clarification for future updates, but for ownership23_1 it reflects the data as it was coded in CPAD at the time. In addition, there was a change in the DOD input data between last year and this year, with the removal of Camp Pendleton. An inquiry was sent for clarification on this change, but for ownership23_1 it reflects the data per the DOD input dataset.22_1 : represents an initial version of ownership with a new methodology which was developed under a short timeframe. A comparison with previous versions of ownership highlighted the some data gaps with the current version. Some of these known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. In addition, any topological errors (like overlaps or gaps) that exist in the input datasets may thus carry over to the ownership dataset. Ideally, any feedback received about missing or inaccurate data can be taken back to the relevant source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.

MassGIS' standardized assessors’ parcel mapping data set contains property (land lot) boundaries and database information from each community's assessor.The data were developed through a competitive procurement funded by MassGIS. Each community in the Commonwealth was bid on by one or more vendors and the unit of work awarded was a city or town. The specification for this work was Level 3 of the MassGIS Digital Parcel Standard.This map service contains three feature classes and one table.Feature service also available.See the datalayer page for full details.

[Metadata] Description: Detailed Government Landownership in the State of Hawaii as of 2022: County, Federal, State, and State DHHL Lands (by TMK parcel)

This dataset includes high quality (800 Dots Per Inch - DPI), 24 bit color images of Minnesota's original Public Land Survey (PLS) plats created during the first government land survey of the state from 1848 to 1907. Currently housed at the Office of the Secretary of State, these plats were created by the U.S. Surveyor General's Office. This collection of more than 3,600 maps also includes later General Land Office (GLO) and the Bureau of Land Management (BLM) maps - up to the year 2001.

Minnesota's survey plat maps serve as the fundamental legal records for real estate in the state; all property titles and descriptions stem from them. They also serve as an essential resource for surveyors and as an analytical tool for the state's physical geography prior to European settlement. Finally, they serve as a testimony to years and years of hard work by the surveying community, often under challenging conditions.

In recent years the deteriorating physical condition of the older maps and the needs of technologically more sophisticated researchers, who require access to the maps, have made handling the original paper records increasingly less practical. To meet this challenge, the Office of the Secretary of State, the State Archives of the Minnesota Historical Society, the Minnesota Department of Transportation, MnGeo (formerly the Land Management Information Center - LMIC) and the Minnesota Association of County Surveyors collaborated in a digitization project which produced images of the maps in standard TIFF, JPEG and PDF formats - nearly 1.5 terabytes worth of data. Funding was provided by the Minnesota Department of Transportation.

An area depicting ownership parcels of the surface estate. Each surface ownership parcel is tied to a particular legal transaction. The same individual or organization may currently own many parcels that may or may not have been acquired through the same legal transaction. Therefore, they are captured as separate entities rather than merged together. This is in contrast to Basic Ownership, in which the surface ownership parcels having the same owner are merged together. Basic Ownership provides the general user with the Forest Service versus non-Forest Service view of land ownership within National Forest boundaries. Surface Ownership provides the land status user with a current snapshot of ownership within National Forest boundaries. Metadata

Donation sent to the University of Idaho Library Government Documents Librarian a CD containing General Land Office maps on it. A readme file on the CD contains this information:"I obtained the attached GLO maps from Mitch Price at River Design Group who obtained them from another source. These maps apparently do not have a date, I assume it was stripped off when they were rectified. These maps show the Great Northern Rail line, it arrived in Bonners Ferry in 1892. The Spokane International Railroad (Union Pacific purchased this line) built a bridge across the Kootenai R. in 1906." "I am a bit puzzled on the map dates, the Kootenai River Master Plan indicated these maps are 1862-65 but they also show the Great Northern Rail line but not the Spokane International Railroad which seems to place them somewhere between 1892 - 1906 unless perhaps they were revised at a later date."Gary Barton USGS Tacoma, WA 253-552-1613 officegbarton@usgs.gov

OSA web map to view State of Colorado property data

Web map for City Properties and Facilities in support of the Land & Building Management System

This Image Service of Maryland Property Data allows for the manipulation of the display properties of the Statewide Tax Maps dataset. This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/ImageServer

To access the tax lot layer you will need to contact the county Assessor's office. ORMAP is a statewide digital cadastral base map that is publicly accessible, continually maintained, supports the Oregon property tax system, supports a multi-purpose land information system, strives to comply with appropriate state and national standards, and will continue to be improved over time.

This data provides the geographic location for parcel boundary lines within the jurisdiction of the Carteret County, NC and is based on recorded surveys and deeds. This dataset is maintained by the Carteret County GIS Division. Data is updated on an as needed basis. The description for each field name in the layer is included below.FieldAliasMeaningPIN15Parcel NumberTax Parcel ID Number (PIN4+ PIN5)ROLL_TYPERoll TypeRoll type of property (regularly taxed property or tax-exempt)GISMOTHERMother ParcelMother ParcelGISMAPNUMPIN1First 4 digits of PIN15MAPNAMPIN2PIN1 + 2 digitsGISBLOCKPIN3Digits 7 and 8 of PIN15GISPINPIN4PIN2 +PIN3GISPDOTPIN5Digit numbers 9 to 12 of PIN15CONDO_Condo unit #Condo numberGISPRIDOld Tax IDOld parcel number style based on prior mapping system before NC GRID system mapsOWNERTax Owner 1Tax parcel ownerOWNER2Tax Owner 2Secondary tax parcel ownerSITE_HOUSESite House #Site Address House NumberSITE_DIRSite DirSite Address Street directionalSITE_STSite StreetSite Address Street NameSITE_STTYPSite Street TypeSite Address Street Suffix (e.g., Dr., St., etc.)SITE_APTNOSite AptSite Address UnitSITE_CITYSite CitySite Address City/CommunityPropertyAddressPhysical AddressProperty AddressMAIL_ADDRESS1Mailing address and streetConcatenated mailing addressMAIL_ADDRESS2Mailing unitSecondary mailing addressMAIL_CITYMailing cityMailing address CityMAIL_STATEMailing stateMailing address StateMAIL_ZI4Mailing Zip4Mailing address Zip Code + 4MAIL_ZI5Mailing Zip5Mailing address Zip CodeFullMailingAddressFull Mailing AddressFull mailing address concatenatedDBOOKDeed BookDeed book containing the most recent deed to the propertyDPAGEDeed PageDeed page containing the most recent deed to the propertyDDATEDeed Dateunformatted most recent deed date for the propertyDeedDate_2Formatted Deed DateFormatted most recent deed date for the propertyMapBookPlat Map BookMap BookMapPagePlat Map PageMap PagePLATBOOKPlat BookRecorded Plat BookPLATPAGEPlat PageRecorded Plat PageLEGAL_DESCParcel Legal DescriptionLegal descriptionLegalAcresLegal Acres (new)Deeded or platted acresDeededAcresLegal AcresAcres from recorded deedsCalculatedLandUnitsTaxed AcresTaxed land acreageGISacresCalculated AcresCalculated GIS acresGISacres2Calculated Acres (new)Calculated GIS acresLandCodeTax Land Category CodeLand CodeLandCodeDescriptionTax Land Category DescriptionLand Code DescriptionMUNICIPALITYMunicipality/ETJIf parcel is within the corporate limits or ETJTOWNSHIPTownshipTownship codeRESCUE_DISTTax Rescue DistrictTax rescue district that the parcel is withinFIRE_DISTTax Fire DistrictTax fire district that the parcel is withinJurisdictionTax District CodeTax District CodeNBHDNeighborhood CodeNeighborhood codeNeighborhoodNameNeighborhood NameNeighborhood code descriptionBuildingCount# BuildingsNumber of buildings within the propertyY_BLT_HOUSEYear Built HouseYear house was builtBLT_CONDOYear Built CondoYear condo was builtTOT_SQ_FTTotal Sq FootTotal square footage of structure on propertyHtdSqFtHeated Sq FootHeated square footages of structure on the propertyBldgModelBuilding ModelBuilding ModelBEDROOMS# Bedrooms# BedroomsBATHROOMS# Bathrooms# BathroomsBldgUseBuilding UseBuilding UseConditionBuilding ConditionBuilding ConditionDwellingStyleDescriptionDwelling DescriptionDwelling style descriptionExWllDes1Exterior wall 1Exterior wall type 1 descriptionExWllDes2Exterior wall 2Exterior wall type 2 descriptionExWllTyp1Exterior wall 1 codeExterior wall type 1ExWllTyp2Exterior wall 2 codeExterior wall type 2FondDes1Foundation Description Foundation type 1 descriptionFondTyp1Foundation Description CodeFoundation type 1RCovDes1Roof # 1 Covering DescriptionRoof covering type 1 descriptionRCovDes2Roof # 2 CoveringDescriptionRoof covering type 2 descriptionRCovTyp1Roof # 1 CodeRoof covering type 1RCovTyp2Roof # 2 CodeRoof covering type 2RStrDes1Roof Structure DescriptionRoof structure type 1 descriptionRStrTyp1Roof Structure CodeRoof structure type 1GradeBuilding GradeTax gradeGradeAndCDUBuilding Grade & ConditionBuilding Grade & ConditionHeatDes1Heating/Cooling TypeHeating type 1 descriptionHeatTyp1Heating/Cooling CodeHeating type 1FireplaceCountFireplacesFireplacesSTRUC_VALStructure ValueValue of structure(s) on the propertyLAND_VALUETax Land ValueValue of the land on the propertyOTHER_VALOther Structures ValueOther value of the propertyTotal_EMVTotal Estimated Market ValueTotal estimated tax valueSaleImprovedorVacantSALE_PRICEVacant or Improved SaleRecorded Sale PriceVacant of Improved SaleRecorded sale priceSaleDateRecorded Sale DateRecorded sale dateSubdivision_NameSubdivision NameSubdivision NameSubdivision_Platbk_pagSubdivision Plat Book/PakeSubdivision Plat Book and PageCommissioner_DistrictCommissioner District #Commissioner"s DistrictCommissioner_Name1Commissioner NameCommissioner"s NameCommissioner_InfoCommissioner LinkLink to Commissioner"s contact info Elementary_SchoolElementary DistrictElementary school name/districtMiddle_SchoolMiddle School DistrictMiddle School name/districtHigh_SchoolHigh School DistrictHigh school name/districtIsImprovedProperty ImprovedBuilt on = 1, Vacant = 0IsQualifiedQualified SaleQualified = 1, Not Qualified = 0Use_codeTax Use CodeLand use codeUse_descTax Use Code DescriptionLand use descriptionPerm_De1Permit # 1 DescriptionPermit #1 descriptionPerm_De2Permit # 2 DescriptionPermit #2 descriptionPerm_Is1Permit # 1 Issue DatePermit #1 issue datePerm_Is2Permit # 2 Issue DatePermit #2 issue datePerm_N1Permit # 1 NumberPermit #1Perm_N2Permit #2 NumberPermit #2Perm_Ty1Permit # 1 TypePermit #1 typePerm_Ty2Permit # 2 TypePermit #2 typeACTL_DA1Permit #1 Completion DatePermit #1 - actual completion dateACTL_DA2Permit #2 Completion DatePermit #2 - actual completion dateReviewedDateTax Office Review DateDate ReviewedNoise_lvlBogue Air Field Noise LevelNoise level zones surrounding military air basesRisk_levelBogue Landing Risk LevelRisk level for military air plane accident potential within the AICUZ zonesaicuzBogue Air Field AICUZAir Installation Compatible Use Zone - planning zones pertaining to military air bases and the surrounding real estateOBJECTIDOBJECTIDESRI default unique IDSHAPEShapeESRI default fieldSHAPE.STArea()Shape AreaESRI default fieldSHAPE.STLength()Shape PerimeterESRI default field

The Geographic Information Systems (GIS) Unit falls under the purview of the County of Santa Cruz Information Services Department. The GIS Unit serves all County departments and external customers and provides data on land, features and people of Santa Cruz County. Santa Cruz County encompasses 4 cities and approximately 265,000 people. This coverage can be used for basic applications such as viewing, querying and map output production, or to provide a basemap to support graphical overlays and analyses of geospatial data.

Web App. Parcel map displaying Age of Housing, Residential Appraised Value and Land Use in St. Louis County, Missouri. Link to Metadata.

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