List of cities, zip codes and counties in Missouri

Easy to navigate and search for property information. Features a large map area and a printable property card. It also includes additional map features such as streets, lakes and parks.

We are a repository of historical King County government records, which are open to public view. Over three hundred collections comprising over 18,000 cubic feet, some dating back to 1853, serve as a permanent source of information about activities, programs, and decisions of County agencies and elected officials. Our records are in many formats, including paper, photographs, maps, and audio-visual materials. They include legislative records - County Commissioner's resolutions (1853-1968) and County Council ordinances and motions (1969-1999), a special collection of over 6,000 County documents, pre-charter legislation, administration and policy decisions, early road and bridge establishment and inspection records and records and policies from former County Executives. Some King County government records are also held by the Puget Sound Regional Branch of the Washington State Archives, which began collecting materials before the establishment of the King County Archives program in 1990.

Search Parcels and Addresses Parcel Data has a link to the Pickaway County Auditor's CAMA data for Property Searches

Any Questions Please Contact Pickaway County GIS Dept. Pickaway County GIS Dept 124 W Franklin St. Circleville, Ohio 43113 Phone: 740-474-5823 Email: jgillow@pickawaycountyohio.gov

A polygon index of recorded plats within Stark County, Ohio. A plat is a legally-recorded document that shows land divisions. This index includes all types of plats and is not limited to allotment subdivisions (this layer replaces the Allotment layer previously used within our organization). The most common document type included in this index is a subdivision plat, which are referred to as allotments in Stark County. It also includes, but is not limited to replats, annexations, and street dedications. This layer is updated and maintained by the Stark County Auditor Office (SCAO) Tax Map Department. It is by no means complete and is updated as new plats become available to the Tax Map Department. Where available, the attribute table includes a "Subdivision Link", which allows the downloading of an archived folder containing a digital copy of the document(s). There are also links (where available) to the Auditor's and Recorder's sites. Where links are not available, use the record volumes/pages or the instrument number to locate the documents through the Stark County Recorder's Search Records site.

County assessor's online applications for searching and rviewing data about parcels and proprties.

Most documents recorded on or after August 1, 1991 are available online. Documents that were recorded prior to August 1, 1991 are on microfilm and are only available from the King County Archives. If you do not find a marriage license on our site, you may want to check Washington State Digital Archives.

Search results are based on the indexing standards used at the time the document was recorded and indexing standards change over time. If you do not find a document on your first try, please adjust your search criteria. Results load one page at a time to ensure the fastest response time, so any sorting or filtering you do on one page of results need to be re-applied to each page of results you view.

Review our frequently asked questions for a list of document types that are not viewable online.

This dataset contains data on all Real Property parcels that have sold since 2013 in Allegheny County, PA. Before doing any market analysis on property sales, check the sales validation codes. Many property "sales" are not considered a valid representation of the true market value of the property. For example, when multiple lots are together on one deed with one price they are generally coded as invalid ("H") because the sale price for each parcel ID number indicates the total price paid for a group of parcels, not just for one parcel. See the Sales Validation Codes Dictionary for a complete explanation of valid and invalid sale codes. Sales Transactions Disclaimer: Sales information is provided from the Allegheny County Department of Administrative Services, Real Estate Division. Content and validation codes are subject to change. Please review the Data Dictionary for details on included fields before each use. Property owners are not required by law to record a deed at the time of sale. Consequently the assessment system may not contain a complete sales history for every property and every sale. You may do a deed search at http://www.alleghenycounty.us/re/index.aspx directly for the most updated information. Note: Ordinance 3478-07 prohibits public access to search assessment records by owner name. It was signed by the Chief Executive in 2007.

Context

There is no story behind this data.

These are just supplementary datasets which I plan on using for plotting county wise data on maps.. (in particular for using with my kernel : https://www.kaggle.com/stansilas/maps-are-beautiful-unemployment-is-not/)
As that data set didn't have the info I needed for plotting an interactive map using highcharter .

Content

Since I noticed that most demographic datasets here on Kaggle, either have state code, state name, or county name + state name but not all of it i.e county name, fips code, state name + state code.

Using these two datasets one can get any combination of state county codes etc.

States.csv has State name + code
US counties.csv has county wise data.

Acknowledgements

Picture : https://unsplash.com/search/usa-states?photo=-RO2DFPl7wE
Counties : https://www.census.gov/geo/reference/codes/cou.html
State :

Inspiration

Not Applicable.

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

Abstract (en): This data collection is a compendium of data for all counties in the United States for the period 1944 to 1977. The data provide diverse information such as local government activities, population estimates and characteristics, and housing unit descriptors. Also included is information on local government revenues, property taxes, capital outlay, debts, expenditures on education, highways, public welfare, health and hospitals, and police, as well as information on births, deaths, schooling, labor force, employment, family income, family characteristics, electoral votes, and housing characteristics. Additional variables provide information on manufacturing, retail and wholesale trade, banking, mineral industries, farm population, agriculture, crime, and weather. Users may also be interested in the related data collection, COUNTY AND CITY DATA BOOK [UNITED STATES] CONSOLIDATED FILE: CITY DATA, 1944-1977 (ICPSR 7735). ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Created variable labels and/or value labels.; Checked for undocumented or out-of-range codes.. Individual states, the District of Columbia, and counties or county equivalents for which data were published in the County and City Data Books, in the entire United States in the period 1947-1977. Smallest Geographic Unit: county 2012-09-18 The data have been checked and corrected for inconsistencies, and have been reformatted to one record per case. SAS, SPSS, and Stata setup files have been updated. SPSS and Stata system files and a SAS transport (CPORT) file have been added to the collection. The codebook has been updated.2008-04-01 SAS, SPSS, and Stata setup files have been added to this data collection. record abstractsThis data file includes both state and county records. Records for counties in each state are listed immediately following the state record. All records have the same structure, and the identifier for each record includes both state and the county codes. In the state records, the county code is listed as 000.

This dataset is updated nightly. For extended information about Lobbyist Activities in Cook County IL, visit the Cook County Clerk's Lobbyist search: http://lobbyist.cookcountyclerk.com/Public/SearchHome.aspx

Parcel Viewer makes searching for King County parcel information easy. You can search by address, search by parcel number, or you can just zoom in on the map and click on a parcel. Once a parcel is selected, you will get direct links to the King County Assessor’s eReal Property report and the Districts and Development Conditions report.

Below is a quick rundown of the tools available in the web map! The first new thing you may notice is the ability to search from in the splash window that appears. This hopefully reduces the number of clicks people will need to get to their information. There's the same search bar in the upper left once you click out of the splash screen. The Query tool has existed in this form on the sub-maps, but now it is here with all the layers. I want to highlight "Search by Legal Description" as a nifty way to find parcels associated with a specific subdivision. I also want to highlight the "find tax parcels/addresses within specified distance" queries. Those let you select every tax parcel or address within a feature you draw (a point, line, or polygon). This is good for finding what properties within a distance need to be notified of something. That can then be exported as an Excel table (csv). This can also help you identify whether something falls within certain setbacks. The Basemaps is the same as it was before. I haven't gotten the Virginia Geographic Information Network imagery from 2017 and 2021 to successfully appear here, but you can find that in the map layers at the bottom. We have a lot of data layers! I currently have the default as every group expanded out, so you can scroll and see all the layers, but you can go through and click to collapse any groups you don't want expanded. Okay, the select tool is super cool, and lets you really dive into some fun GIS attribute querying! As an example, you can select all the FEMA Flood Zones that are AO, then select all the tax parcels that are affected by (intersect) those AO zones! These results can also be exported into an Excel table. A great deal of GIS analysis is possible just using Select by Attributes and Select by Location, so this tool really ramps up the power of the web map so it can do some of what the desktop GIS software can do! Continuing our tour of the tools, we come to the coordinates tool. This one also existed already in the sub-maps, but is now with all the layers. Unfortunately, the tool is a little annoying, and won't retain my defaults. You have to click the little plus sign target thing, then you can click on the map to get the coordinates. The coordinate system defaults to WGS 1984 Web Mercator (the same thing Google Maps uses), but much of our data uses NAD 1983 State Plane Virginia South, so you can click the dropdown arrow to the right to select either one. Exciting news related to this: in 2026 they are releasing the new coordinate system on which they've been working! It should make the data in GIS more closely align with features in reality, but you will not need to change any of the ways you interact with the data. The next tool is the Elevation Profile tool. It's very nifty! You can draw a profile to see how the elevation changes, and as you move your cursor along the graph, it shows where along your transect you are! It helps explain some of the floodplain and sea level rise boundaries. You know the measure tool well, but this one retains the defaults in feet and acres, which is very exciting! No more having to change the units every time you want to measure (unless you want other than feet and acres). The draw tool is our penultimate stop on the tour! It is largely the same as what existed on the old public web map, so I shan't delve into it here. When you draw a feature now though, it appears in the layers tab (until you close the map), which can let you toggle the drawing on and off to work with what is beneath it. It can help as you plan in where you might want to put new constructions. The print tool is also largely the same, but I've been finding the tool in this new Experience Builder format is less buggy than the one in the retired Web App Builder that made the old Public Web Map.

The U.S. Climate Risk Projections by County, 2040-2049 data set contains a projection for 2040-2049 risk for the entire contiguous U.S. at the county level with a novel climate risk index integrating multiple hazards, exposures and vulnerabilities. Multiple hazards such as weather and climate are characterized as a frequency of heat wave, cold spells, drought, and heavy precipitation events along with anomalies of temperature and precipitation using high resolution (4 km) downscaled climate projections. Exposure is characterized by projections of population, infrastructure, and built surfaces prone to multiple hazards including sea level rise and storm surges. Vulnerability is characterized by projections of demographic groups most sensitive to climate hazards. This approach can guide planners in targeting counties at most risk and where adaptation strategies to reduce exposure or protect vulnerable populations might be best applied.

The King County Groundwater Protection Program maintains a database of groundwater wells, water quality and water level sampling data. Users may search the database using Quick or Advanced Search OR use King County Groundwater iMap map set. The viewer provides a searchable map interface for locating groundwater well data.

This dataset is designed to represent and identify the property boundaries in Lexington-Fayette County. The original dataset was created in late 1990's by a third party that converted existing paper maps to digital GIS files. The data has since been updated by georeferencing recorded plats for corrections and new additions. In cases where the plats do not appear accurate, aerial photos are utilized in attempt to properly locate the property lines. The only except for this process are changes to highway right-of-way in which calls are run from deeds. The geometry of this data is not of survey quality and should not be used for survey purposes. The data is intended for general reference purposes only.As part of the basemap data layers, the parcel boundary map layer is an integral part of the Lexington Fayette-Urban County Government Geographic Information System. Basemap data layers are accessed by personnel in most LFUCG divisions for basic applications such as viewing, querying, and map output production. More advanced user applications may focus on thematic mapping, summarization of data by geography, or planning purposes (including defining boundaries, managing assets and facilities, integrating attribute databases with geographic features, spatial analysis, and presentation output).

The Real Property Records Search allows the user to obtain ownership information as of January 1, value of improvements and land, photo of improvement, sales information for the last three (3) years, view the tax bill and GIS Mapping information associated with a parcel.Disclaimer: Data presented on the Tax Administration Records Search website is extracted from actual public records. Users are hereby notified that the aforementioned public primary information sources should be consulted for verification of the information contained on this website. While our department has made every effort to use the most current and accurate data, the County of Durham and software companies assume no legal responsibility for the information contained in the Tax Administration Records Search website. Please direct any questions or comments about the data displayed here to tax_assessor@dconc.gov.

Observations and subtle shifts of vegetation communities in Lake Erie have USGS researchers concerned about the potential for Grass Carp to alter these vegetation communities. Broad-scale surveys of vegetation using remote sensing and GIS mapping, coupled with on-the-ground samples in key locations will permit assessment of the effect Grass Carp may have already had on aquatic vegetation communities and establish baseline conditions for assessing future effects. Existing aerial imagery was used with object-based image analysis to detect and map aquatic vegetation in the eastern basin of Lake Erie.

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