The Digital Geomorphic-GIS Map of Gulf Islands National Seashore (5-meter accuracy and 1-foot resolution 2006-2007 mapping), Mississippi and Florida is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (guis_geomorphology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (guis_geomorphology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (guis_geomorphology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (guis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (guis_geomorphology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (guis_geomorphology_metadata_faq.pdf). Please read the guis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (guis_geomorphology_metadata.txt or guis_geomorphology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:26,000 and United States National Map Accuracy Standards features are within (horizontally) 13.2 meters or 43.3 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

A web map used to visualize available digital parcel data for Organized Towns and Unorganized Territories throughout the state of Maine. Individual towns submit parcel data on a voluntary basis; the data are compiled by the Maine Office of GIS for dissemination by the Maine GeoLibrary, and where available, the web map also includes assessor data contained in the Parcels_ADB related table.This web map is intended for use within the Maine Geoparcel Viewer Application; it is not intended for use as a standalone web map.Within Maine, real property data is maintained by the government organization responsible for assessing and collecting property tax for a given location. Organized towns and townships maintain authoritative data for their communities and may voluntarily submit these data to the Maine GeoLibrary Parcel Project. Maine Parcels Organized Towns and Maine Parcels Organized Towns ADB are the product of these voluntary submissions. Communities provide updates to the Maine GeoLibrary on a non-regular basis, sometimes many years apart, which affects the currency of Maine GeoLibrary parcels data. Another resource for real property transaction data is the County Registry of Deeds, although organized town data should very closely match registry information, except in the case of in-process property conveyance transactions.

The Cumberland County GIS Data Viewer provides the general public with parcel, zoning, hydrology, soils, utilities and topographic data. You can search for a specific address, street name, parcel number (PIN), or by the owner's name.

A web map used to access tax parcel, boundary, ownership, acreage, survey, zoning and tax information. Errors and Omissions Do Exist.The information provided is for reference only and subject to independent verification. User assumes all responsibility for its use.https://www.fayette-co-oh.com/Fayette County ProfileFayette County is a county located in the U.S. state of Ohio. Its county seat is Washington Court House. Fayette County was formed on March 1, 1810 from portions of Highland County and Ross County. It was named after Marie-Joseph Motier, Marquis de La Fayette, a French general and politician who took the side of the Colonials during the American Revolutionary War and who played an important role in the French Revolution.Fayette County is a part of the Virginia Military survey, which was reserved in 1783, to be allotted to Virginia soldiers. This district includes the entire counties of Adams, Brown, Clermont, Clinton, Highland, Fayette, Madison and Union; and a portion of the counties of Scioto, Pike, Ross, Pickaway, Franklin, Delaware, Marion, Hardin, Logan, Champaign, Clarke, Greene, Warren and Hamilton.Fayette County was formed January 19, 1810 (took effect March 1st) from Ross and Highland counties. Beginning at the southwest corner of Pickaway, running north “with the line of said county to the corner of Madison; thence west with the line of said Madison county to the line of Greene county; thence south with the line of Greene county to the southeast corner thereof; thence east five miles; thence south to the line of Highland county; thence east with said line to Paint Creek; thence in a straight line to the beginning.” All the lower portion was taken from Highland and the upper from Ross.The first portion of land entered within the territory of what is now Fayette county, was a part of original surveys Nos. 243 and 772, lying partly in Clinton county. The first survey lying wholly within Fayette county was No. 463, in what is now Madison township, surveyed for Thomas Overton by John O’Bannon June 30, 1776.The original townships were Jefferson, Greene, Wayne, Madison, Paint and Union. Concord township was formed in April 1818, from Greene. Marion township was formed in June, 1840 from Madison. Perry township was formed June 4, 1845, from Wayne and Greene. Jasper township was formed from Jefferson and Concord December 2, 1845.Washington C.H. was laid out originally on a part of entry 757, which contained 1200 acres and belonged to Benjamin Temple, of Logan county, Kentucky, who donated 150 acres to Fayette county, on condition that it be used as the site of the county seat. The deed of conveyance was made December 1, 1810, by Thomas S. Hind, attorney for Temple, to Robert Stewart, who was appointed by the legislature as director for the town of Washington. The town was laid off some time between December 1, 1810, and February 26, 1811, the latter being the date of the record of the town plat.Bloomingburg (originally called New Lexington) was laid out in 1815, by Solomon Bowers, and originally contained 34 and ¾ acres. On March 4, 1816, Bowers laid out and added twenty more lots. The name of the town was later changed to Bloomingburg by act of the legislature. The town was incorporated by act of the legislature, February 5, 1847.Jeffersonville was laid out March 1, 1831, by Walter B. Write and Chipman Robinson, on 100 acres of land belonging to them, they started selling the lots at $5 each. The town incorporated March 17, 1838. The first house was erected by Robert Wyley.The first railroad, now the C. & M. V., was completed in 1852; the second, now the Detroit Southern, in 1875; the third, now the C.H. & D. in 1879; and the fourth, now the B. & O. S. W., in 1884.The first permanent settler (probably) was a Mr. Wolf who settled in what is now Wayne township, in about the year 1796. - Circa 1886 - Map of Fayette County, Ohio. Issued by the Fayette County Record.

These parcel boundaries represent legal descriptions of property ownership, as recorded in various public documents in the local jurisdiction. The boundaries are intended for cartographic use and spatial analysis only, and not for use as legal descriptions or property surveys. Tax parcel boundaries have not been edge-matched across municipal boundaries.

All of the ERS mapping applications, such as the Food Environment Atlas and the Food Access Research Atlas, use map services developed and hosted by ERS as the source for their map content. These map services are open and freely available for use outside of the ERS map applications. Developers can include ERS maps in applications through the use of the map service REST API, and desktop GIS users can use the maps by connecting to the map server directly.

{{description}}

This viewer was created for the Arkansas GIS Office to aid staff as well as County personnel in quickly locating information related to tax parcels.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.

Vector polygon map data of property parcels from Harris County, Texas containing 1,410,276 features.

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

Available for viewing and sharing in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

This layer contains polygons that split the City of Cambridge into 286 city blocks. Each block boundary is associated with an Assessors map, and a group of parcels. Each individual parcel has a map and lot associated to it. The 'map' refers to one of these blocks, the 'lot' is the tax parcel within the block. Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription PCIX_NO type: Stringwidth: 6precision: 0 Block number

BSIZE_MAP_SCALE type: Integerwidth: 4precision: 10

BSIZE_INCH_TO_FOOT type: Integerwidth: 4precision: 10

DSIZE_MAP_SCALE type: Integerwidth: 4precision: 10

DSIZE_INCH_TO_FOOT type: Integerwidth: 4precision: 10

ROTATION type: Doublewidth: 8precision: 38

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).

DCGIS is an interactive map that provides increased functionality for advanced users as well as access to about 150 layers of GIS data, including parcel information, contour lines, aerial photography, county park amenities, park trails, bikeways, county road construction, roundabouts, floodplains and more. It allows you to create a map at any scale you wish.
The Interactive GIS Map is intended for use on any device - mobile or desktop - with high speed access.

This countywide composite of parcels (cadastral) data for Monmouth County represents digitized property boundaries that were developed from best available local and municipal tax maps data. The normalized parcels data are compatible with the New Jersey Department of Treasury MOD-IV system currently used by tax assessors. Stewardship and maintenance of the data continue under the purview of the Monmouth County GIS Office as well as local municipal tax authorities. Parcel attributes were normalized to a standard structure, specified in the New Jersey GIS Parcel Mapping Standard, to store parcel information and provide a PIN (parcel identification number) field common to the PIN that was to be stored in the PAMS (Property Assessment Management System) database to replace the MOD-IV database. Please note that this parcel dataset is not intended for use as tax maps nor for legal purposes. The dataset is intended to provide reasonable representations of parcel boundaries primarily for planning purposes and cartographic representation. Please note cautions when performing a join with this dataset and MOD-IV property records, specifically regarding duplicate and erroneous records. All records may not be provided for in the parcels data or MOD-IV (Tax List Search) tables because of how the data and tables are constructed, or for temporal mismatches. MOD-IV provides for the uniform preparation, maintenance, presentation and storage of property tax information required by the Constitution of the State of New Jersey, New Jersey Statutes and rules promulgated by the Director of Taxation. MOD-IV maintains and updates all assessment records, and produces all statutorily required tax lists. These lists account for all parcels of real property as delineated and identified on each municipality's official tax map, as well as taxable values and descriptive data for each parcel.

© GIS Office, Monmouth County Planning Board, New Jersey.

The Digital Geologic-GIS Map of Fayette County, Pennsylvania is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (faco_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (faco_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (faco_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (fone_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (fone_frhi_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (faco_geology_metadata_faq.pdf). Please read the fone_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Pennsylvania Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (faco_geology_metadata.txt or faco_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:50,000 and United States National Map Accuracy Standards features are within (horizontally) 25.4 meters or 83.3 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Webmap of Allegheny municipalities and parcel data. Zoom for a clickable parcel map with owner name, property photograph, and link to the County Real Estate website for property sales information.

The Digital Geologic-GIS Map of the Austin Quadrangle, Kentucky is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (aust_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (aust_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (aust_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (maca_abli_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (maca_abli_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (aust_geology_metadata_faq.pdf). Please read the maca_abli_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (aust_geology_metadata.txt or aust_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

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)

Statewide Property Inventory started in 1989 per legislation 11011.15, to begin a pro-active approach to managing the State’s Real Property assets in a computerized format. Having the information in an electronic format makes it available to top level decision-makers considering options for the best use of these assets. The Statewide Property Inventory is mandated to capture detailed information on the following: land owned and leased by the state, structures owned and leased by the state, property the state leases to the private sector. Statewide Property Inventory was established in 1988 by legislative mandate. Leases were added in 2004 by executive order. Data is updated annually by the agencies. Point of Contact: Any questions should be referred to the SPIWeb@dgs.ca.gov

This map data layer represents the GIS Map Panel Boundaries for the City of Bloomington, Indiana. The GIS Map Panel Boundaries data layer was created as a reference grid for the GIS map data. The grid tiles are 3000' by 2000' and cover a total of 86.3 square miles of central Monroe County in Indiana. The panel tiles are located arbitrary to any geographic features