Web App. Use the tabs provided to discover information about map features and capabilities. Link to Metadata. A variety of searches can be performed to find the parcel of interest. Use the Query Tool to build searches. Click Apply button at the bottom of the tool.Query by Name (Last First) (e.g. Bond James)Query by Address (e.g. 41 S Central)Query by Locator number (e.g. 21J411046)Search results will be listed under the Results tab. Click on a parcel in the list to zoom to that parcel. Click on the parcel in the map and scroll through the pop-up to see more information about the parcel. Click the ellipse in the Results tab or in the pop-up to view information in a table. Attribute information can be exported to CSV file. Build a custom Filter to select and map properties by opening the Parcels attribute table:1. Click the arrow tab at the bottom middle of the map to expand the attribute table window2. Click on the Parcels tab3. Check off Filter by map extent4. Open Options>Filter5. Build expressions as needed to filter by owner name or other variables6. Select the needed records from the returned list7. Click Zoom to which will zoom to the selected recordsPlease note that as the map zooms out detailed layers, such as the parcel boundaries will not display.In addition to Search capabilities, the following tools are provided:MeasureThe measure tool provides the capabilities to draw a point, line, or polygon on the map and specify the unit of measurement.DrawThe draw tool provides the capabilities to draw a point, line, or polygon on the map as graphics. PrintThe print tool exports the map to either a PDF or image file. Click Settings button to configure map or remove legend.Map navigation using mouse and keyboard:Drag to panSHIFT + CTRL + Drag to zoom outMouse Scroll Forward to zoom inMouse Scroll Backward to zoom outUse Arrow keys to pan+ key to zoom in a level- key to zoom out a levelDouble Click to Zoom inFAQsHow to select a parcel: Click on a parcel in the map, or use Query Tool to search for parcel by owner, address or parcel id.How to select more than one parcel: Go to Select Tool and choose options on Select button.How to clear selected parcel(s): Go to Select Tool and click Clear.

The published representation of real property areas, combined with assessing and tax information from CAMA and Tax systems, and organized for consumption in desktop and web applications. This feature class contains redundant geometry in cases where there are multiple condominium units on a given tax parcel.

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.

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.

Web map specifically for linking the Property Detail Lookup Tool to the lot geometry in East Baton Rouge Parish, Louisiana.

These boundaries are for planning purposes only and are not survey grade. For the most up-to-date assessing info, please contact the Town's Assessor. The respective Fiscal Year of publication is provided in the parcel pop-up info window. Years may vary from town to town.The parcels from each town on Martha's Vineyard are included in this web map. The map must be zoomed in far enough before the parcels will display on the map. The data are served out from MassGIS. All parcel data comply with the MassGIS Level 3 Parcel Data Standard.Each Town in Dukes County hires their own parcel data consultant to maintain their GIS parcel file. In most cases, this is done once a year. At the time of data compilation, the town Assessor exports a standard info file from their database which gets associated with each digital parcel. The Town's consultant pulls the parcel bounds and assessing info table into a spatial geodatabase which is then forwarded to MassGIS. MassGIS completes a few additional data management tasks and then serves out the data through their ArcGIS OnLine organizational website.The Martha's Vineyard Commission (MVC) then pulls that parcel data feature class into this web map and sets a few things such as visibility zoom extents and how the data display in the pop-up. The MVC does not edit these data in any way.Building Info Note: If there are multiple buildings on a parcel, the building info provided is only for one building on the parcel. Which building (i.e. largest, smallest, newest, oldest) is unknown. Parcels with Multiple Owners (i.e. Condo): If there are multiple owners on one parcel, when clicking on the pop-up you'll see the option to cycle through several records worth of assessing info.Understanding the Attributes: See the MassGIS Level 3 Parcel Data website for details.

MassGIS' standardized ("Level 3") property tax parcel mapping data set was 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. Standardization of assessor parcel mapping is complete for all 351 Massachusetts' cities and towns. MassGIS is now incorporating updates from municipalities into the database. This hosted feature layer is exported from MassGIS' internal database of the feature class GISDATA.L3_TAXPAR_POLY_ASSESS, which links L3_TAXPAR_POLY and L3_ASSESS. The export includes the expression: (POLY_TYPE IN ('FEE', 'TAX')) OR (POLY_TYPE IN ('ROW', 'PRIV_ROW', 'RAIL_ROW', 'WATER') AND PROP_ID IS NOT NULL) It contains several fields from GISDATA.L3_ASSESS and stacked polygons where multiple assessor records link to a parcel. It contains features that do not have an associated record in GISDATA.L3_ASSESS, except for rights of way and water bodies. ROWs and water bodies with a non-null PROP_ID are included. The data in this feature layer is used for the popups in the Massachusetts Interactive Property Map. See full data descriptionA hosted tile layer will draw very quickly at map scale of 1:18,056 (level 15) to 1:564 (level 20).

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.

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

The Florida TIITF Land Records Spatial Index is a document based GIS layer to be displayed as a map comprised of polygons and attributes representing parcels described in deeds, leases, easements and other instruments archived in the Title Archives of the Division of State Lands, Department of Environmental Protection for the Florida Board of Trustees of the Internal Improvement Trust Fund (TIITF). The polygons represent parcels described in the archived TIITF land record documents; this is not a tax map or a representation of current ownership. The data includes acquisitions, dispositions and encumbrances. Selecting a parcel on the map may return information about several different documents associated with that parcel through out the history of State land transactions involving that parcel.

This dataset represents real property information within a parcel of land in the City of Baltimore. The data dictionary for this dataset can be accessed by visiting the following link.: Data Dictionary For Real Property Information | Open Baltimore (baltimorecity.gov). Data is updated on a weekly basis. To leave feedback or ask a question about this dataset, please fill out the following form: Real Property Information feedback form.

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)

This lookup tool has been developed to provide quick access to the property information stored in the City-Parish GIS database. Users can search by Address, Subdivision Name, Business Name, North American Industry Classification System (NAICS) Code, or Lot Identification Number to find detailed information about property. Enter the required information in one of the search fields as shown in the example below each field. Next, click the button adjacent to the search criteria, and the search results will be displayed beneath the lookup tools in tabular format. Clicking on one of the search result records will invoke a new window with details about the property. The property details may then be printed and/or exported to a comma-separated values (CSV) file.

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)

The Parcel 2008 feature contains tax parcel polygons for the 2008 property tax assessment at the County. This feature reflects tax parcel polygons as they existed from 1/1/2008 through 12/31/2008. Each parcel is uniquely identified with a Property Index Number (PIN).

File Geodatabase - Click hereShapefile - Click hereThis dataset contains current parcel boundaries and related attributes for approximately 2.4 million parcels maintained by the Los Angeles County Assessor (updated monthly on the second of every month). Due to the size of the data, it is only available for download as a zipped file geodatabase or shapefile at this time. For additional annual assessment roll history and attribute metadata descriptions, please visit the L.A. County Open Data Portal and search for Assessor. To better understand individual data elements, or to interactively view individual parcel information, please visit the Assessor’s Portal. A public-facing parcel map cache can be accessed here (updated weekly): https://public.gis.lacounty.gov/public/rest/services/LACounty_Cache/LACounty_Parcel/MapServer/0All inquiries should be directed to the Mapping & GIS Services Section, LA County Office of the Assessor at gisinfo@assessor.lacounty.gov

Gives property, or parcel, ownership together with value information, which ensures fair assessment of Boston taxable and non-taxable property of all types and classifications. To preserve their integrity, the identifiers PID, CM_ID, GIS_ID, ZIPCODE, and MAIL_ZIPCODE all are marked with an underscore ("_") as the last character.

Year-specific documentation for the FY2008 through FY2013 files is not currently available, but the format of those files is equivalent to that described in the FY2014 documentation.

This layer represents parcel polygon geometries from the Assessor's Office Parcel Fabric. This layer is updated whenever edits in the tax_parcels and non_taxables layers of the Parcel Fabric are edited. Please sort the Last_Modified field descending for the latest update.

This parcels dataset is a spatial representation of tax lots for Gloucester County, New Jersey that have been extracted from the NJ statewide parcels composite by the NJ Office of Information Technology, Office of GIS (NJOGIS). Parcels at county boundaries have been modified to correspond with the NJ county boundaries and the parcels in adjacent counties.Each parcel contains a field named PAMS_PIN based on a concatenation of the county/municipality code, block number, lot number and qualification code. Using the PAMS_PIN, the dataset can be joined to the MOD-IV database table that contains supplementary attribute information regarding lot ownership and characteristics. Due to irregularities in the data development process, duplicate PAMS_PIN values exist in the parcel records. Users should avoid joining MOD-IV database table records to all parcel records with duplicate PAMS_PINs because of uncertainty regarding whether the MOD-IV records will join to the correct parcel records. There are also parcel records with unique PAMS_PIN values for which there are no corresponding records in the MOD-IV database tables. This is mostly due to the way data are organized in the MOD-IV database.The polygons delineated in the dataset do not represent legal boundaries and should not be used to provide a legal determination of land ownership. Parcels are not survey data and should not be used as such.The MOD-IV system provides for 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 the Division of Taxation. MOD-IV maintains and updates all assessment records and produces all statutorily required tax lists for property tax bills. This list accounts 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. Tax List records were received as raw data from the Taxation Team of NJOIT which collected source information from municipal tax assessors and created the statewide table. This table was subsequently processed for ease of use with NJ tax parcel spatial data and split into an individual table for each county.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

Internal view of the parcel layer. This view contains all the attributes that can be seen by County employees.There are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.SFAP & CFAP DISCLAIMER: Per the California Code, RTC 606. some legal parcels may have been combined for assessment purposes (CFAP) or separated for assessment purposes (SFAP) into multiple parcels for a variety of tax assessment reasons. SFAP and CFAP parcels are assigned their own APN number and primarily result from a parcel being split by a tax rate area boundary, due to a recorded land use lease, or by request of the property owner. Assessor parcel (APN) maps reflect when parcels have been separated or combined for assessment purposes, and are one legal entity. The goal of the GIS parcel fabric data is to distinguish the SFAP and CFAP parcel configurations from the legal configurations, to convey the legal parcel configurations. This workflow is in progress. Please be advised that while we endeavor to restore SFAP and CFAP parcels back to their legal configurations in the primary parcel fabric layer, SFAP and CFAP parcels may be distributed throughout the dataset. Parcels that have been restored to their legal configurations, do not reflect the SFAP or CFAP parcel configurations that correspond to the current property tax delineations. We intend for parcel reports and parcel data to capture when a parcel has been separated or combined for assessment purposes, however in some cases, information may not be available in GIS for the SFAP/CFAP status of a parcel configuration shown. For help or questions regarding a parcel’s SFAP/CFAP status, or property survey data, please visit Napa County’s Surveying Services or Property Mapping Information. For more information you can visit our website: When a Parcel is Not a Parcel | Napa County, CA