This parcels dataset is a spatial representation of tax lots for Essex 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.
Digital data from VG12-3, Gale, M., Kim. J., and Ruksznis, A., 2012, Bedrock Geologic Map of the essex Junction Quadrangle: Vermont Geological Survey Open File Report VG12-3, scale 1:24,000. Bedrock geologic map data at a scale of 1:24,000 depicts types of bedrock underlying unconsolidated materials in Vermont. Data is created by mapping on the ground using standard geologic pace and compass techniques and/or GPS on a USGS 1:24000 topographic base map. Data may be organized by town, quadrangle or watershed. Each data bundle may include point, line and polygon data and some or all of the following: 1) contacts (lithogic contacts), 2) fault_brittle, 3) fault_ductile, 4) fault_thrust, 5) fault_bed_plane (bedding plane thrust), 6) bedding, 7) bedding_graded (graded bedding) 8) bedding_overturn (overturned bedding), 9) bedding_select (selected points for published map), 10) foliation_n1, n2, n3 etc (foliation data), 11) outcrop (exposed outcrops), 12) field_station (outcrop and data collection point), 13) fold_axis, 14) axial_plane, 15) lamprophyre, 16) water_well_log (water well driller information), 16) linear_int (intersection lineation), 17) linear_str (stretching lineation) 18) x_section_line (line of cross-section), and photolinear (lineaments identified from air photos). Other feature classes may be included with each data bundle. (https://dec.vermont.gov/geological-survey/publication-gis/ofr).
View the Tax Parcels in Essex County, as well as relevant features like soil use, land cover, and conservation easements!
Network of vector points representing the elevation of Essex County with a point density of 40metres, to which is a suitable density for ortho-rectification purposes.
This data set contains the sea floor topographic contours, sun-illuminated topographic imagery, and backscatter intensity generated from a multibeam sonar survey of the Stellwagen Bank National Marine Sanctuary region off Boston, Massachusetts, an area of approximately 1100 square nautical miles. The Stellwagen Bank NMS Mapping Project is designed to provide detailed maps of the Stellwagen Bank region's environments and habitats and the first complete multibeam topographic and sea floor characterization maps of a significant region of the shallow EEZ. Data were collected on four cruises over a two year period from the fall of 1994 to the fall of 1996. The surveys were conducted aboard the Candian Hydrographic Service vessel Frederick G. Creed, a SWATH (Small Waterplane Twin Hull) ship that surveys at speeds of 16 knots. The multibeam data were collected utilizing a Simrad Subsea EM 1000 Multibeam Echo Sounder (95 kHz) that is permanently installed in the hull of the Creed.
This is a polygon GIS data layer showing the location and extent of various sidescan, multibeam and swath bathymetry surveys conducted by the USGS, Coastal and Marine Geology Program. Outlines of individual mosaic areas were combined to create one comprehensive layer that could be used to illustrate areas surveyed by USGS/CMGP seafloor mapping programs.
This preliminary experimental lithogeochemical map shows the distribution of rock types in the Virginia and Maryland parts of the Chesapeake Bay watershed. The map was produced digitally by classifying geologic-map units according to composition, mineralogy, and texture; rather than by age and stratigraphic relationships as shown on traditional geologic maps. This map differs from most lithologic maps in that the lithogeochemical unit classification distinguishes those rock units having key water-reactive minerals that may induce acid neutralization, or reduction, of hosted water at the weathering interface. The validity of these rock units, however, is independent of water chemistry, because the rock units are derived from geologic maps and rock descriptions. Areas of high soil carbon content, and sulfide metal deposits are also shown. Water-reactive minerals and their weathering reactions yield five lithogeochemical unit classes: 1) carbonate rock and calcareous rocks and sediments, the most acid-neutralizing; 2)carbonaceous-sulfidic rocks and sediments, oxygen-depleting and reducing; 3) quartzofeldspathic rocks and siliciclastic sediments, relatively weakly reactive with water; 4) mafic silicate rocks/sediments, oxygen consuming and high solute-load delivering; and, 5) the rarer calcareous-sulfidic (carbonaceous) rocks, neutralizing and reducing. Earlier studies in some parts of the map area have related solute loads in ground and stream waters to some aspects of bedrock lithology. More recent preliminary tests of relationships between four of the classes of mapped lithogeochemical units and ground water chemistry, in the Mid-Atlantic area using this map, have focused on and verified the nitrate-reducing and acid-neutralizing properties of some bedrock and unconsolidated aquifer rock types. Sulfide mineral deposits and their mine-tailings effects on waters are beginning to be studied by others. Additional testing of relationships among the lithogeochemical units and aspects of ground and surface water chemistry could help to refine the lithogeochemical classification, and this map. The testing could also improve the usefulness of the map for assessing aquifer reactivity and the transport properties of reactive contaminants such as acid rain, and nitrate from agricultural sources, in the Chesapeake Bay watershed.
The Washington DC Area geologic map database (DCDB) provides geologic map information of areas to the NW, W, and SW of Washington, DC to various professionals and private citizens who have uses for geologic data. Digital, geographically referenced, geologic data is more versatile than traditional hard copy maps, and facilitates the examination of relationships between numerous aspects of the geology and other types of data such as: land-use data, vegetation characteristics, surface water flow and chemistry, and various types of remotely sensed images. The DCDB was created by combining Arc/Info coverages, designing a Microsoft (MS) Access database, and populating this database. Proposed improvements to the DCDB include the addition of more geochemical, structural, and hydrologic data.
Unvegetated to vegetated marsh ratio (UVVR) in the Plum Island Estuary and Parker River (PIEPR) salt marsh complex was computed based on conceptual marsh units defined by Defne and Ganju (2018). UVVR was calculated based on U.S. Department of Agriculture National Agriculture Imagery Program (NAIP) 1-meter resolution imagery. Through scientific efforts initiated with the Hurricane Sandy Science Plan, the U.S. Geological Survey has been expanding national assessment of coastal change hazards and forecast products to coastal wetlands, including the Plum Island Estuary and Parker River salt marsh complex, with the intent of providing Federal, State, and local managers with tools to estimate the vulnerability and ecosystem service potential of these wetlands. For this purpose, the response and resilience of coastal wetlands to physical factors need to be assessed in terms of the ensuing change to their vulnerability and ecosystem services. UVVR is planned to be an underlying parameter in the synthesis of these factors.
This is a seven-category land-cover map of Essex, Massachusetts. The seven categories are: bare soil, coniferous trees, decidous trees, grass, impervious surface, water, and wetlands. Note: Complete metadata is available within the downloaded zip file. This metadata can be viewed with ESRI ArcGIS software, and can be exported to FGDC and ISO metadata formats.
These data were created as part of the National Oceanic and Atmospheric Administration Office for Coastal Management's efforts to create an online mapping viewer called the Sea Level Rise and Coastal Flooding Impacts Viewer. It depicts potential sea level rise and its associated impacts on the nation's coastal areas. The purpose of the mapping viewer is to provide coastal managers and scientists with a preliminary look at sea level rise (slr) and coastal flooding impacts. The viewer is a screening-level tool that uses nationally consistent data sets and analyses. Data and maps provided can be used at several scales to help gauge trends and prioritize actions for different scenarios. The Sea Level Rise and Coastal Flooding Impacts Viewer may be accessed at: http://www.coast.noaa.gov/slr This metadata record describes the digital elevation model (DEM), which is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Sea Level Rise and Coastal Flooding Impacts Viewer described above. This DEM includes the best available data known to exist at the time of DEM creation that met project specifications, for mainland Virginia, this includes portions of the following counties: Alexandria, Arlington, Charles City, Chesapeake, Essex, Fairfax, Falls Church, Franklin City, Fredericksburg City, Gloucester, Hampton, Isle of Wight, James City, King and Queen, King George, King William, Lancaster, Mathews, Middlesex, New Kent, Newport News, Norfolk, Northumberland, Poquoson City, Portsmouth, Prince George, Prince William, Richmond, Southampton, Stafford, Suffolk, Surry, Sussex, Virginia Beach, Westmoreland, Williamsburg, and York. This DEM also includes the District of Columbia. The DEM is derived from the following lidar: 1. New Kent, Charles City, Prince George Counties 2012 FEMA Middle Counties VA Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/Middle_Counties/Metadata/Project_Report/Dewberry_ProjectReport_MiddleCounties.pdf Additional coverage provided by the Virginia Base Map Program (VBMP). This data is a digital terrain model initially generated by the Center for Geospatial Technology (CGIT) for the Virginia Geographic Information Network (VGIN) using the mass points and break lines from 2002 VBMP aerial photography. 2. King William County 2011 FEMA King William County VA Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/KingWilliamCo/KingWilliam_Metadata/Dewberry_ProjectReport_KingWilliam.pdf Additional coverage provided by the Virginia Base Map Program (VBMP). This data is a digital terrain model initially generated by the Center for Geospatial Technology (CGIT) for the Virginia Geographic Information Network (VGIN) using the mass points and break lines from 2002 VBMP aerial photography. 3. Hampton and Portsmouth Cities 2011 FEMA Virginia Southern Cities Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/SouthernCities/SouthernCities_Metadata/Dewberry_ProjectReport_SouthernCities.pdf 4. Franklin City and Southampton County 2011 FEMA Virginia Counties South Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/VA_Counties_South/SouthernCo_Metadata/Dewberry_ProjectReport_Southampton.pdf 5. Fredericksburg City and Essex, King George, Prince William, Richmond, Stafford, Westmoreland Counties 2011 FEMA Virginia Counties North Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/VA_Counties_North/NorthernCo_Metadata/Dewberry_ProjectReport_NorthernCounties.pdf 6. Northumberland, Middlesex, Lancaster, King and Queen, Gloucester, Mathews, James City, Williamsburg, Surry, Isle of Wight, Suffolk Counties 2010/2011 USGS Eleven County Coastal VA Lidar This data may be downloaded from the William and Mary Center for Geospatial Analysis: http://www.wm.edu/as/cga/VALIDAR/ The project report for this data may be accessed at: http://gisfiles.wm.edu/files/lidar/a11county/Metadata/PROJECT_REPORT/Final%20Project%20Report%20for%20USGS%20Virginia%20LiDAR_01312011.pdf Additional coverage for Surry and King and Queen counties provided by the Virginia Base Map Program (VBMP). This data is a digital terrain model initially generated by the Center for Geospatial Technology (CGIT) for the Virginia Geographic Information Network (VGIN) using the mass points and break lines from 2002 VBMP aerial photography. 7. Alexandria, Arlington, and Falls Church Counties 2008 NGA Capital Region Lidar The lidar data is not publicly available, the data was provided by the State of Virginia as bare earth DEMs. 8. Fairfax County 2008 NGA Capital Region Lidar The lidar data is not publicly available, the data was provided by the State of Virginia as bare earth DEMs. 2012 FEMA Virginia Lidar This data may be downloaded from USGS EarthExplorer at: http://earthexplorer.usgs.gov/ 9. York, Poquoson City, Newport News, Norfolk, Chesapeake, Virginia Beach, and Sussex Counties Data provided by the Virginia Base Map Program (VBMP). This data is a digital terrain model initially generated by the Center for Geospatial Technology (CGIT) for the Virginia Geographic Information Network (VGIN) using the mass points and break lines from 2002 VBMP aerial photography. 2010 US Army Corps of Engineers (USACE) Lidar This data may be downloaded at: http://www.coast.noaa.gov/dataviewer/index.html?action=advsearch&qType=in&qFld=ID&qVal=1132 The metadata for this data may be accessed at: http://coast.noaa.gov/dataviewer/webfiles/metadata/usace2010_va_template.html 10.District of Columbia Washington, DC and Environs, 2008, 1/9 Arc second National Elevation Dataset (NED) This data may be downloaded at: http://viewer.nationalmap.gov/viewer/ Hydrographic breaklines were delineated from LiDAR intensity imagery generated from the LiDAR datasets. The DEM is hydro flattened such that water elevations are less than or equal to 0 meters. The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 10 meters.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
See full Data Guide here. This layer includes polygon features that depict protected open space for towns of the Protected Open Space Mapping (POSM) project, which is administered by the Connecticut Department of Energy and Environmental Protection, Land Acquisition and Management. Only parcels that meet the criteria of protected open space as defined in the POSM project are in this layer. Protected open space is defined as: (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non-facility-based outdoor recreation, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities. Includes protected open space data for the towns of Andover, Ansonia, Ashford, Avon, Beacon Falls, Canaan, Clinton, Berlin, Bethany, Bethel, Bethlehem, Bloomfield, Bridgewater, Bolton, Brookfield, Brooklyn, Canterbury, Canton, Chaplin, Cheshire, Colchester, Colebrook, Columbia, Cornwall, Coventry, Cromwell, Danbury, Derby, East Granby, East Haddam, East Hampton, East Hartford, East Windsor, Eastford, Ellington, Enfield, Essex, Farmington, Franklin, Glastonbury, Goshen, Granby, Griswold, Groton, Guilford, Haddam, Hampton, Hartford, Hebron, Kent, Killingworth, Lebanon, Ledyard, Lisbon, Litchfield, Madison, Manchester, Mansfield, Marlborough, Meriden, Middlebury, Middlefield, Middletown, Monroe, Montville, Morris, New Britain, New Canaan, New Fairfield, New Milford, New Hartford, Newington, Newtown, Norfolk, North, Norwich, Preston, Ridgefield, Shelton, Stonington, Oxford, Plainfield, Plainville, Pomfret, Portland, Prospect, Putnam, Redding, Rocky Hill, Roxbury, Salem, Salisbury, Scotland, Seymour, Sharon, Sherman, Simsbury, Somers, South Windsor, Southbury, Southington, Sprague, Sterling, Suffield, Thomaston, Thompson, Tolland, Torrington, Union, Vernon, Wallingford, Windham, Warren, Washington, Waterbury, Watertown, West Hartford, Westbrook, Weston, Wethersfield, Willington, Wilton, Windsor, Windsor Locks, Wolcott, Woodbridge, Woodbury, and Woodstock. Additional towns are added to this list as they are completed. The layer is based on information from various sources collected and compiled during the period from March 2005 through the present. These sources include but are not limited to municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions as of the date of research at each city or town hall. The Protected Open Space layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town Assessor's lot numbering system, and system-defined (automatically generated) fields. The Protected Open Space layer has an accompanying table containing more detailed information about each feature (parcel). This table is called Protected Open Space Dat, and can be joined to Protected Open Space in ArcMap using the parcel ID (PAR_ID) field. Detailed information in the Protected Open Space Data attribute table includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the unique parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, and acreage. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygons that represent the best available locational information, and are "best fit" to the land base available for each.
The Connecticut Department of Environmental Protection's (CTDEP) Permanently Protected Open Space Phase Mapping Project Phase 1 (Protected Open Space Phase1) layer includes permanently protected open space parcels in towns in Phase 1 that meet the CTDEP's definition for this project, the Permanently Protected Open Space Mapping (CT POSM) Project. The CTDEP defines permanently protected open space as (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non facility-based outdoor recreations, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities.
Towns in Phase 1 of the CT POSM project are situated along the CT coast and portions of the Thames River and are the following: Branford, Bridgeport, Chester, Clinton, Darien, Deep River, East Haven, East Lyme, Essex, Fairfield, Greenwich, Groton, Guilford, Hamden, Ledyard, Lyme, Madison, Milford, Montville, New Haven, New London, North Branford, North Haven, Norwalk, Norwich, Old Lyme, Old Saybrook, Orange, Preston, Shelton, Stamford, Stonington, Stratford, Waterford, West Haven, Westbrook, Westport.
For the purposes of the project a number of categories or classifications of open space have also been created. These include: Land Trust, Land Trust with buidlings, Private, Private with buildings, Utility Company, Utility Company with buildings, Federal, State, Municipal, Municipal with buildings, Conservation easement, and non-DEP State land. The layer is based on information from various sources collected and compiled during the period from August 2002 trhough October 2003. These sources include municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions on the date of research at each city or town hall.
The Protected Open Space Phase1 layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town's Assessor lot numbering system, and system-defined (automatically generated) fields. In addition, the Protected_Open_Space_Phase1 layer has an accompanying table containing more detailed information about each parcel's collection, standardization and storage. This table is called Protected Open Space Phase1 Data and can be joined to Protected Open Space Phase1 in ArcMap using the parcel ID (PAR_ID) field. Detailed information includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the project-specific parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, acreage collected during site reconaissance and the data source. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygon feature type that represent the best available locational information, i.e. "best fit" to the land base available for each.
Phase 1 of the Protected Open Space Mapping (POSM) Project was accomplished by a contractor using only a querying process to identify open space. The contractor obtained assessor's data from the various towns and created programs to cull open space parcels strictly by query processes. We have found many errors and omissions in the data, but at this point in the project we cannot revisit all the coastal towns. Therefore, this data is being sent with a disclaimer for accuracy. You are welcome to use it but not to publish it. Please note that we do not include any water company parcels despite them being listed as part of our criteria because we must first obtain written clarification and clearance from the U.S. Department of Homeland Security.
We have since changed our data collection method for Phase 2 of this project. DEP staff now visit each town hall and thoroughly research the land records. The project is expected to be complete by 2010.
August 2025
April 2022
Zoning districts for Essex Junction, Vermont. Data corresponds to the regulations adopted by the City of Essex, effective February 26, 2025Please see the Essex Junction Regulations for the zoning and subdivision document(s).Overlay District(s) found under separate file.
Here is a brief description of each of the field names LegalDescr: the legal description of the parcelZoning: The zoning code for the parcel. Note: there are slight differences in zoning codes within the Town of Tappahannock compared to the rest of the county.TotalParc: Total Parcel Value as appraised in the Commissioner of the RevenueTotalImp: The value of all the improvements in the parcel, as appraised in the Commissioner of the RevenueTotalLand: The value of the land in the parcel, as appraised in the Commissioner of the RevenueLegalAcre: Legal AcreageGISAcres: The acreage as calculated in ArcGIS Pro’s Calculate Geometry toolOwnerName: This is the name of the first owner listed. CoOwner_Fi: This is the name of the second owner listed.Address: This is the 9-1-1 address for the property. If no 9-1-1 address has been assigned, the property will have an address of 0 Road Name. If multiple addresses are on the property, only one of them is listed here.PrimaryUse: This is a designation of whether data is Residential (R), Vacant (V), Commercial (C), or has a Mobile Home (T), as well as an indication of the relative size of the property.TaxJoinGIS: This field enables the parcel data to work with Vision's web map (which you can access from the property card) TaxLookup: This field has all spaces removed to allow for easy searching of parcels within the webmapWebLink: This navigates to the property data card in Vision, the data portal for the Commissioner of the Revenue. The home page for that portal is https://gis.vgsi.com/essexva/Search.aspxPID: This is a number that is one of the ways data can be searched in Vision. GISJoin: This is a field that has the leading and trailing spaces removed to enable the joining of data within GISTaxLabel: This field has only one space between each portion of the tax map to allow for more convenient labelling on the map Notes: Any special information needed for the parcel, including whether a parcel is split zoned or in the Historic Overlay Zone. Mailing Add: The street address portion of the mailing address for the property ownerMailingCit: The city portion of the mailing address for the property ownerMailingSta: The state portion of the mailing address for the property ownerMailingZip: The zip code of the mailing address for the property owner
Not seeing a result you expected?
Learn how you can add new datasets to our index.
This parcels dataset is a spatial representation of tax lots for Essex 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.