This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2018, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

Elevation datasets in New Jersey have been collected over several years as several discrete projects. Each project covers a geographic area, which is a subsection of the entire state, and has differing specifications based on the available technology at the time and project budget. The geographic extent of one project may overlap that of a neighboring project. Each of the 18 projects contains deliverable products such as LAS (Lidar point cloud) files, unclassified/classified, tiled to cover project area; relevant metadata records or documents, most adhering to the Federal Geographic Data Committee’s (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM); tiling index feature class or shapefile; flights lines feature class or shapefile; Digital Elevation Model in image format or Esri grid format; other derivative data products such as contour lines feature class or shapefile.

This feature class (shapefile) consists of point locations of public, private, and charter schools including pre-schools, day care facilities, adult and vocational schools in New Jersey, with minimal attributes. Most of the public schools were initially located in 2003 by the New Jersey Department of Environmental Protection, and were checked in 2007-2016 by the NJ Office of Geographic Information Systems (OGIS), other organizations and volunteers. Charter schools were located in 2011 and checked through 2016 by OGIS against the 2016 NJ Department of Education table of public schools that also lists charter schools.Private schools were located initially in 2010, and updated later in 2014 only for Somerset County using the spatial data provided by Somerset County GIS team. The present data set is the result of checking and updating the previous locations by processing the tabular data that were acquired from NJDOE in August, 2016.

© Most of the public school records were derived from 2003 data sets created by the New Jersey Department of Environmental Protection. Special acknowledgements are to people of the following organizations who made a significant contribution to school location verification process: Seth Hackman (NJDEP), Salem county GIS; Morris County GIS; Atlantic County GIS; Cape May County GIS; DVRPC; Hunterdon County GIS; Somerset County GIS; Warren County Prosecutor's Office; Westfield Engineering; WFS (for Mercer, Middlesex, Burlington and Camden Co.) ; Monmouth GIS; voluneers and state employees who made site visits on their own time: Charles Colvard, Dominic Juliano, Matt Lawson, Richard Rabinowitz, Amy J. Ferdinand, Rebecca French-Mesch.

This layer is a component of Sites and Facilities.

This layer is a component of Water.

© BGIS, NJDEP

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. The BG boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

NOTE: This metadata file contains information for Flowlines delineated for NJ from 2002 color infrared (CIR) imagery with attributes extracted from the National Hydrography Dataset (NHD). Digitizing of this data was initially done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). Conflation of USGS 1:24,000 High resolution NHD attributes was done by Data Enhancement Services, LLC (DES) partnered with Civil Solutions. This statewide conflation of NHD High resolution information was completed in 2010. All QA/QC was done by NJDEP, Bureau of GIS and USGS. This represents a subset of the statewide extract for NJ dated August 25, 2010.

Please note that this file is large, ~550 MB, and may take a substantial amount of time to download especially on slower internet connections.Shapefile (NJ State Plane NAD 1983) download: Click "Open" or Click hereFile Geodatabase (NJ State Plane NAD 1983) download: Click hereThis data represents a "generalized" version of the 2012 LULC. To improve the performance of the web applications displaying the 2012 land use data, it was necessary to create a new simplified layer that included only the minimum number of polygons and attributes needed to represent the 2012 land use conditions. The 2012 LU/LC data set is the fifth in a series of land use mapping efforts that was begun in 1986. Revisions and additions to the initial baseline layer were done in subsequent years from imagery captured in 1995/97, 2002, 2007 and 2012. This present 2012 update was created by comparing the 2007 LU/LC layer from NJDEP's Geographic Information Systems (GIS) database to 2012 color infrared (CIR) imagery and delineating and coding areas of change. Work for this data set was done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). LU/LC changes were captured by adding new line work and attribute data for the 2012 land use directly to the base data layer. All 2007 LU/LC polygons and attribute fields remain in this data set, so change analysis for the period 2007-2012 can be undertaken from this one layer. The classification system used was a modified Anderson et al., classification system. An impervious surface (IS) code was also assigned to each LU/LC polygon based on the percentage of impervious surface within each polygon as of 2007. Minimum mapping unit (MMU) is 1 acre. ADVISORY: This metadata file contains information for the 2012 Land Use/Land Cover (LU/LC) data sets, which were mapped by USGS Subbasin (HU8). There are additional reference documents listed in this file under Supplemental Information which should also be examined by users of these data sets. As stated in this metadata record's Use Constraints section, NJDEP makes no representations of any kind, including, but not limited to, the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the digital data layers furnished hereunder. NJDEP assumes no responsibility to maintain them in any manner or form. By downloading this data, user agrees to the data use constraints listed within this metadata record.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. School Districts are single-purpose administrative units within which local officials provide public educational services for the area's residents. The Census Bureau obtains the boundaries, names, local education agency codes, grade ranges, and school district levels for school districts from State officials for the primary purpose of providing the U.S. Department of Education with estimates of the number of children in poverty within each school district. This information serves as the basis for the Department of Education to determine the annual allocation of Title I funding to States and school districts. TIGER/Line Shapefiles include separate shapefiles for elementary, secondary and unified school districts. The school district boundaries are those in effect for the 2021-2022 school year, i.e., in operation as of January 1, 2022.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. School Districts are single-purpose administrative units within which local officials provide public educational services for the area's residents. The Census Bureau obtains the boundaries, names, local education agency codes, grade ranges, and school district levels for school districts from State officials for the primary purpose of providing the U.S. Department of Education with estimates of the number of children in poverty within each school district. This information serves as the basis for the Department of Education to determine the annual allocation of Title I funding to states and school districts. The TIGER/Line Shapefiles include separate shapefiles for elementary, secondary and unified school districts. The school district boundaries are those in effect for the 2021-2022 school year, i.e., in operation as of January 1, 2022.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. School Districts are single-purpose administrative units within which local officials provide public educational services for the area's residents. The Census Bureau obtains the boundaries, names, local education agency codes, grade ranges, and school district levels for school districts from State officials for the primary purpose of providing the U.S. Department of Education with estimates of the number of children in poverty within each school district. This information serves as the basis for the Department of Education to determine the annual allocation of Title I funding to states and school districts. The TIGER/Line Shapefiles include separate shapefiles for elementary, secondary and unified school districts. The school district boundaries are those in effect for the 2021-2022 school year, i.e., in operation as of January 1, 2022.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. The BG boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

Please note that this file is large, ~450 MB, and may take a substantial amount of time to download especially on slower internet connections.Shapefile (NJ State Plane NAD 1983) download: Click "Open" or Click hereFile Geodatabase (NJ State Plane NAD 1983) download: Click hereThis data represents a "generalized" version of the 2007 LULC. To improve the performance of the web applications displaying the 2002 land use data, it was necessary to create a new simplified layer that included only the minimum number of polygons and attributes needed to represent the 2002 land use conditions. The 2007 LU/LC data set is the fourth in a series of land use mapping efforts that was begun in 1986. Revisions and additions to the initial baseline layer were done in subsequent years from imagery captured in 1995/97, 2002 and 2007. This present 2007 update was created by comparing the 2002 LU/LC layer from NJ DEP's Geographical Information Systems (GIS) database to 2007 color infrared (CIR) imagery and delineating and coding areas of change. Work for this data set was done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). LU/LC changes were captured by adding new line work and attribute data for the 2007 land use directly to the base data layer. All 2002 LU/LC polygons and attribute fields remain in this data set, so change analysis for the period 2002-2007 can be undertaken from this one layer. The classification system used was a modified Anderson et al., classification system. An impervious surface (IS) code was also assigned to each LU/LC polygon based on the percentage of impervious surface within each polygon as of 2007. Minimum mapping unit (MMU) is 1 acre. ADVISORY: This metadata file contains information for the 2007Land Use/Land Cover (LU/LC) data sets, which were mapped by Watershed Management Area (WMA). There are additional reference documents listed in this file under Supplemental Information which should also be examined by users of these data sets. As stated in this metadata record's Use Constraints section, NJDEP makes no representations of any kind, including, but not limited to, the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the digital data layers furnished hereunder. NJDEP assumes no responsibility to maintain them in any manner or form. By downloading this data, user agrees to the data use constraints listed within this metadata record.

Please note that this file is large, ~150 MB, and may take a substantial amount of time to download especially on slower internet connections.Shapefile (NJ State Plane NAD 1983) download: Click "Open" or Click hereThis data was created by combining two separate data sets, the land use/land cover layer from the Integrated Terrain Unit Maps (ITUM) for this county and the freshwater wetlands (FWW) layer generated under the New Jersey Freshwater Wetlands Mapping Program. The Arc/INFO LULC coverage has been converted to an ArcView shapefile for distribution. The ITUM land use/land cover was photo interpreted from 1986 color infrared (CIR) 1:58000 aerial photos, and delineated using a modified Anderson et al. 1976, classification system to 1:24000 rectified photo-basemaps. These basemaps complied with National Map Accuracy Standards (NMAS) as individual quadrangles but were not produced from a sophisticated aero-triangulation photogrammetric solution. Minimum mapping unit = 2.5 acres. The ITUM land use/land cover was integrated with three other sources (soils, USGS floodprone areas, and 1906 Atlas Sheet Geology) based on coincident features. The four data layers have subsequently been split out into four separate themes for distribution and use. Beginning in 1998, the NJDEP does not support the data as a single integrated ITUM theme but rather as four separate themes. Freshwater wetlands delineations were made on 1986 orthophoto quarterquad basemaps (1:12000) by photo interpretation of 1986 CIR photos. The classification system used was a modified Cowardin system (Cowardin, et al., 1979). All freshwater wetland polygons greater than 1 acre in area and all linear freshwater wetland features greater than 10 feet in width were mapped. The 1986 quarterquad basemaps meet NMAS and are orthophotos.

Historical shoreline surveys were conducted by the National Ocean Service (NOS), dating back to the early 1800s. The maps resulting from these surveys, often called t-sheets, provide a reference of historical shoreline position that can be compared to modern data to identify shoreline change. The t-sheets are stored at the National Archives and many have been scanned by the National Oceanic and Atmospheric Administration (NOAA) and are available on the NOAA Shoreline Web site (http://www.shoreline.noaa.gov/data/datasheets/t-sheets.html). While some scanned t-sheets were georeferenced and digitized by NOAA, still others remain as non-georeferenced raster files (http://nosimagery.noaa.gov/images/shoreline_surveys/survey_scans/NOAA_Shoreline_Survey_Scans.html). New_Jersey_1839_75_Digitized_Shoreline.zip features a digitized historic shoreline for the New Jersey coastline from 1839 to 1875. The data were scanned by NOAA, but were not georeferenced. The t-sheets included in this data release are: T-121 (1839), T-119 Part 1 (1841), T-1084 (1868), T-1166 (1870), T-1333 (1871), T-1315a (1872), T-1371 (1874), T-1407 (1875). Digital files were georeferenced, corrected to a modern datum, and shorelines digitized to provide a vector polyline depicting the historical shoreline position. All shorelines, including the foreshore, backshore, mainland and island shorelines were delineated and digitized for each survey using ArcMap 10.3.1. These shorelines were digitized for use in long-term shoreline and wetland analyses for Hurricane Sandy wetland physical change assessment.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Congressional districts are the 435 areas from which people are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the states based on census population counts, each state is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The 118th Congress is seated from January 2023 through December 2024. In Connecticut, Illinois, and New Hampshire, the Redistricting Data Program (RDP) participant did not define the CDs to cover all of the state or state equivalent area. In these areas with no CDs defined, the code "ZZ" has been assigned, which is treated as a single CD for purposes of data presentation. The TIGER/Line shapefiles for the District of Columbia, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands) each contain a single record for the non-voting delegate district in these areas. The boundaries of all other congressional districts reflect information provided to the Census Bureau by the states by August 31, 2022.

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.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Census Bureau includes landmarks in the MTDB for locating special features and to help enumerators during field operations. Some of the more common landmark types include area landmarks such as airports, cemeteries, parks, schools, andchurches and other religious institutions. The Census Bureau added landmark features to MTDB on an as-needed basis andmade no attempt to ensure that all instances of a particular feature were included. The presence or absence of a landmark such as a hospital or prison does not mean that the living quarters associated with that landmark were geocoded to that census tabulation block or excluded from the census enumeration. The Area Landmark Shapefile does not include military installations or water bodies because they each appear in their own separate shapefiles, MIL.shp and AREAWATER.shp respectively.