As part of the NJOGIS effort to develop a statewide composite of parcel datasets, parcels sharing boundaries with municipal boundaries were modified to be coincident to the municipal boundaries data developed in 2008 by NJOGIS and adopted by GIS users throughout the state. Parcel boundaries that cross municipal boundaries were also modified to properly align at and across the municipal boundary. Three additional attribute fields were added to the attribute table to help note changes that occurred as a result of this process. They include a field to store the original size of the parcel before editing, a field to store the percentage change in area size, and a field to code parcels that were significantly altered in size and/or shape. After parcel geometry edits were completed, the area percentage change was calculated by comparing the size of the original area to the modified area using the following calculation, ([Shape_Area] / [OriginalAREA]) *100. Each parcel with a value below 90 percent and above 110 percent was considered significant and reviewed more closely against 2007/2008 orthophotography and municipal tax maps to determine if the parcel modification was appropriate. If, upon further inspection, the parcel modification was not consistent with the dimensions or acreage values shown on tax maps and/or orthophotography, the parcel (and neighboring parcels, if necessary) was again modified to minimize the size and/or shape distortion of the polygon. After additional editing, the area change was recalculated. If the recalculated change was still outside of the acceptable distortion level, the parcel was given a production code with an explanation for why the shape and/or area of the parcel was altered to a significant degree. Definitions for the production codes were given to each data steward to assist in their review of the data. The three additional attribute fields added to the attribute table to help note changes were deleted before final delivery of the dataset to the data steward and NJOGIS.
Updates to records for the following counties were deployed in a new statewide parcel feature class with minimal attributes. Atlantic County Burlington County Camden County Cape May County Monmouth County Morris County Somerset County Hunterdon County South Brunswick Township Middlesex County Warren County Ocean County
In a continuing effort to improve parcels data quality, NJOGIS and several county partners coordinated work to identify and fix duplicate PAMS_PIN records. Most duplicates were related to condominium qualifier codes. A much smaller proportion were due to incorrect data input and/or duplicate block and lot numbers on tax maps.
By August 2011 additional corrections received as updated parcel layers from stewards as listed below: Atlantic County, Bergen County, Burlington County, Camden County, Gloucester County, Hudson County, Hunterdon County, Mercer County, Monmouth County, Ocean County, Passaic County, Salem County, Sussex County, Union, and Warren County, and the following municipalities: Newark, East Brunswick Township and South Brunswick Township. September 2011: Cape May County updates. January 2012: Cumberland County update incorporates a significant revision developed for the county in 2010 using updated tax map information. It was reconciled with the 2009 NJOGIS normalized parcels dataset. The modifications affected Salem County. February 2012: Burlington County updates. See details at https://njgin.state.nj.us/oit/gis/NJ_NJGINExplorer/docs/parcelAnnounce.pdf
A new composite statewide feature class was created by appending the latest feature class for each county or municipality into a new feature class structure. The attribute "PIN_NODUP" was filled as described below. The new structure included all previous attributes and some additional MOD-IV attributes. As of end of June 2013 corrections received as updated parcel layers from stewards as listed below were included: Cumberland County Monmouth County City of Newark - March 13, 2012 Mercer County ( MUN_CODE only) to reflect the upcoming merger between Princeton Borough and Princeton Township in January 2013. - December 11, 2012 Cape May County - March 26, 2013 Ocean County - April 11, 2013 Camden County - May 20, 2013 Hudson County - May 24, 2013 Bergen County - June 20, 2013 Burlington County - June 26, 2013 See details at https://njgin.state.nj.us/oit/gis/NJ_NJGINExplorer/docs/parcelAnnounce.pdf. Appropriate values for PIN_NODUP were calculated for the composite feature class from PAMS_PIN by using the following queries in sqlplus: UPDATE Cad_parcel_mod4 SET DUP = 'y' WHERE pams_pin in (select pams_pin from Cad_parcel_mod4 group by pams_pin having ( count(pams_pin) > 1)); UPDATE Cad_parcel_mod4 SET DUP = 'n' WHERE pams_pin in (select pams_pin from Cad_parcel_mod4 group by pams_pin having ( count(pams_pin) = 1)); At this point, contents were checked by query to make sure all records were filled appropriately. UPDATE Cad_parcel_mod4 SET PIN_NODUP = 'XXXNLL' WHERE DUP = 'y'; UPDATE Cad_parcel_mod4 SET PIN_NODUP = PAMS_PIN WHERE DUP = 'n'; Note that PIN_NODUP was set to dummy value XXXNLL for those records with non-uniqe PIN values.
Parcels and MOD-IV data for Essex County, and updated data for Middlesex County, Princeton Borough and Princeton Township, were processed to create a feature class with the same attributes as Cad_parcel_mod4. The statewide feature class was updated by deleting records for Middlesex County and the Princetons, and appending updates including records for Princeton. Then the following fields were indexed: PAMS_PIN PCL_MUN PCL_BLOCK PCL_LOT PCL_QCODE PIN_NODUP COUNTY CD_CODE
Tax List records from the statewide table released in May, 2014 were received June 5, 2014, as raw data from the Taxation Team of NJOIT which collected source information from the MOD-IV system. The csv file was loaded into an Oracle database by EDS staff. They then created a table for use by GIS, including processing of Lot, Block, and Qualifier code fields to format needed for GIS Parcel Identification Number, and creating the GIS_PIN. Because of the degree of variation in assessor entries to the block, lot, and qualifier fields in MOD-IV, processing those entries into the correct format is a non-trivial task and required examining and correcting for a number of different formats. EDS also processed a number of the MOD-IV content fields into more GIS user - friendly formats, requested by NJOGIS. The final contents are described in Entity and Attribute Information. For 2014, changes were made to the MOD-IV table including the number of fields and some data types. For example LAST_YR_TX was converted to a text field with contents in US dollars and cents, and the format was changed for field entries in BLOCK, LOT, AND QUALIFIER. The processed table was copied to NJOGIS enterprise geodatabase, and examined for quality. Eight records with duplicate GIS_PIN values were researched and four of them corrected, resulting in a table with unique values for this attribute (as designed).
An Oracle/ArcSDE view was created by joining MOD-IV 2014 table to the 2014 parcel composite layer. SDE view was exported to File Geodatabase feature class. Please note that there are some added fields compared to previous versions of the expanded feature class, and for a few fields the format of the contents have changed (see previous process step for 2014 MOD-IV data.) The following fields are indexed on the feature class once it has been transferred to a geodatabase: PAMS_PIN PCL_MUN PCLBLOCK PCLLOT PCLQCODE PIN_NODUP CD_CODE PROP_CLASS COUNTY MUN_NAME LAND_VAL IMPRVT_VAL NET_VALUE CALC_ACRE The following script was used for the view: sdetable -i 5156 -s abbott43.oit.state.nj.us \ -u gis -p xxx -o create_view \ -T CAD_PARCEL_MOD4_V \ -t "GIS.Cad_parcel,GIS.Cad_mod4" \ -c "Cad_parcel.OBJECTID,Cad_parcel.PAMS_PIN,\ Cad_parcel.MUN,Cad_parcel.BLOCK,Cad_parcel.LOT,\ Cad_parcel.QCODE,\ Cad_parcel.LASTUPDATE,Cad_parcel.PIN_NODUP,\ Cad_parcel.SHAPE,\ Cad_mod4.GIS_PIN,Cad_mod4.CD_CODE,\ Cad_mod4.PROP_CLASS,\ Cad_mod4.COUNTY,Cad_mod4.MUN_NAME,\ Cad_mod4.PROP_LOC,\ Cad_mod4.OWNER_NAME,\ Cad_mod4.ST_ADDRESS,Cad_mod4.CITY_STATE,\ Cad_mod4.ZIP_CODE,\ Cad_mod4.LAND_VAL,Cad_mod4.IMPRVT_VAL,\ Cad_mod4.NET_VALUE,Cad_mod4.LAST_YR_TX,\ Cad_mod4.BLDG_DESC,Cad_mod4.LAND_DESC,\ Cad_mod4.CALC_ACRE,Cad_mod4.ADD_LOTS1,\ Cad_mod4.ADD_LOTS2,Cad_mod4.FAC_NAME,\ Cad_mod4.PROP_USE,Cad_mod4.BLDG_CLASS,Cad_mod4.DEED_BOOK,\ Cad_mod4.DEED_PAGE,Cad_mod4.DEED_DATE,Cad_mod4.YR_CONSTR,\ Cad_mod4.SALES_CODE,Cad_mod4.SALE_PRICE,Cad_mod4.DWELL,\ Cad_mod4.COMM_DWELL,Cad_mod4.OLD_PROPID,\ Cad_mod4.ZIP5,Cad_mod4.ZIP_PLUS4" \ -a "OBJECTID,PAMS_PIN,PCL_MUN,PCL_BLOCK,PCL_LOT,PCL_QCODE,PCL_LASTUPD,\ PIN_NODUP,SHAPE,GIS_PIN,CD_CODE,PROP_CLASS,COUNTY,MUN_NAME,PROP_LOC,\ OWNER_NAME,ST_ADDRESS,CITY_STATE,ZIP_CODE,LAND_VAL,\ IMPRVT_VAL,NET_VALUE,LAST_YR_TX,BLDG_DESCR,LAND_DESCR,CALC_ACRE,\ ADD_LOTS1,ADD_LOTS2,FAC_NAME,PROP_USE,BLDG_CLASS,DEED_BOOK,DEED_PAGE,DEED_DATE,\ YR_CONSTR,SALES_CODE,SALE_PRICE,DWELL,COMM_DWELL,OLD_PROPID,\ ZIP5,ZIP_PLUS4" \ -w "(Cad_parcel.PIN_NODUP = Cad_mod4.GIS_PIN(+))"
Metadata were edited extensively and imported. Inapplicable details from previous publication processing were eliminated, and updates reflecting the data were added.
New Statewide composite feature class was complied from the latest individual county parcel datasets on file with NJOGIS. 2012 City of Newark parcel dataset was used, since it was more complete than the latest Essex County parcel information for Newark. The same Oracle/SDE View described in process step 8 was still used to join the revised 2014 statewide parcel composite to the 2014 MOD-IV table. SDE view was exported to File Geodatabase feature class. The following fields are indexed on the feature class once it has been transferred to a geodatabase: PAMS_PIN PCL_MUN PCLBLOCK PCLLOT PCLQCODE PIN_NODUP CD_CODE PROP_CLASS COUNTY MUN_NAME LAND_VAL IMPRVT_VAL NET_VALUE CALC_ACRE
The parcels for Burlington County (City of Beverly only), Essex County, Passaic County, Salem County (certain parcels only), and Union County were removed and replaced with updated parcels from file geodatabases. Details are as follows: Burlington County - The previous parcels for Beverly City were removed by NJOGIS and all parcels were replaced with updated parcels from Burlington County GIS. This replacement was needed due to citywide block and lot re-numbering from a newly approved set of tax maps for the city. Topology was validated and any errors were corrected. Essex County - The Essex parcels were edge matched with the Passaic and Union County parcels by the NJOGIS using Essex County tax maps, property deed info from the Passaic and Union County Clerks and Passaic and Union County municipal tax maps. 2012 NJ orthophotography was used as a base the help with this edge matching process. City of Newark parcels were imported into Essex County parcels by NJOGIS and edge matched with Essex, Passaic, and Union parcels as described above. Several large areas of parcel shift of +/- 4' were fixed by NJOGIS as part of this process. Topology (parcel gaps & overlaps) was set up and validate for the entire parcel dataset. Any topology errors were corrected by NJOGIS. An attribute analyis was performed for the entire parcel dataset. This analysis included looking for duplicate PAMS_PIN values and PAMS_PIN vaues that did not match the concatenation of the MUN, BLOCK, LOT & QCODE fields. NJOGIS corrected as many of these errors as possible. Analysis report was created to send to the county parcel steward that shows the parcel to MOD-IV and MOD-IV to parcel match rate info for each town in the county, listings of the parcel and MOD-IV records that do not have a matching parcel, remaining duplicate PAMS_PIN values, remaining PAMS_PIN values that do not match the concatenation of the MUN, BLOCK, LOT & QCODE fields, listing of MOD-IV records with a QUALIFIER field value that do have a matching parcel (along with match rates for each town in the county). Passaic County - The Passaic parcels were edge matched with the Essex County parcels by the NJOGIS using property deed info from the Passaic County Clerk and municipal tax maps. 2012 NJ orthophotography was used as a base the help with this edge matching process. Topology (parcel gaps & overlaps) was set up and validate for the entire parcel dataset. Any topology errors were corrected by NJOGIS. An attribute analyis was performed for the entire parcel dataset. This analysis included looking for duplicate PAMS_PIN values and PAMS_PIN vaues that did not match the concatenation of the MUN, BLOCK, LOT & QCODE fields. NJOGIS corrected as many of these errors as possible. Analysis report was created to send to the county parcel steward that shows the parcel to MOD-IV and MOD-IV to parcel match rate info for each town in the county, listings of the parcel and MOD-IV records that do not have a matching parcel, remaining duplicate PAMS_PIN values, remaining PAMS_PIN values that do not match the concatenation of the MUN, BLOCK, LOT & QCODE fields, listing of MOD-IV records with a QUALIFIER field value that do have a matching parcel (along with match rates for each town in the county). Salem County - Parcels were adjusted to coincide with the revised municipal boundaries for Upper Pittsgrove Township, Pittsgrove Township, and Elmer Borough. Municpal boundary revisions were based on the Anthony Farm Green Acres Survey (Block 2 Lots 49 & 56) in Elmer Borough. Union County - The Union parcels were edge matched with the Essex County parcels by the NJOGIS using property deed info from the Union County Clerk and municipal tax maps. 2012 NJ orthophotography was used as a base the help with this edge matching process. Topology (parcel gaps & overlaps) was set up and validate for the entire parcel dataset. Any topology errors were corrected by NJOGIS. An attribute analyis was performed for the entire parcel dataset. This analysis included looking for duplicate PAMS_PIN values and PAMS_PIN vaues that did not match the concatenation of the MUN, BLOCK, LOT & QCODE fields. NJOGIS corrected as many of these errors as possible. Analysis report was created to send to the county parcel steward that shows the parcel to MOD-IV and MOD-IV to parcel match rate info for each town in the county, listings of the parcel and MOD-IV records that do not have a matching parcel, remaining duplicate PAMS_PIN values, remaining PAMS_PIN values that do not match the concatenation of the MUN, BLOCK, LOT & QCODE fields, listing of MOD-IV records with a QUALIFIER field value that do have a matching parcel (along with match rates for each town in the county).
Added unique value primary key field (PCL_GUID). The value in this field will never change during the lifetime of the parcel. The value in PCL_GUID field was populated for all parcel records using the ArcGIS Field Calculator and applying the following Python Script: def ID(): import uuid return str(uuid.uuid4()) # Calculates 36-character GUID values, without curly braces # Be sure to set parser=Python in field calculator window PCL_GUID = ID() After the script was run, the Find Identical Tool was run to make sure all records had a unique value. No duplicate values were found for any of the parcel records.
Essex County - All Verona Township parcels were updated with the current block and lot numbers from the tax maps that were approved by the Division of Taxation in 2015. Re-numbering was completed using an Microsoft Excel crosswalk spreadsheet supplied by the municipal Tax Assessor. Monmouth County - Existing parcels for Asbury Park, Bradley Beach Borough, and Neptune Township were replaced with municipal parcels based on digital tax maps for each town. Asbury Park and Neptune Township had recently undergone town wide block and lot renumbering, so the existing parcels did not correspond to the MOD-IV database. As part of this replacement process, each of the three town's parcels were edge matched with the existing county parcels and each other. Parcels along the boundary that span the boundary, but are assessed in one town only, were merged and represented as one parcel. Any missing subdivisions, parcel mergers, or condos in the surrounding towns that were found during the edge matching process, were added. Morris County - All block, lot numbers, adn QCODE values for Kinnelon Borough were updated to reflect the current block, lot, and QCODE values on the 2015 tax maps. This was completed using a spatial join of the current Kinnelon Borough parcel shapefile from Morris County to the existing parcels. Where the spatial join did not properly conflate the block, lot, and QCODE values, the information was manually updated in the Morris County parcels. Where possible lot mergers and subdivisions were also completed from the municipal tax maps. The final match rate for Kinnelon Borough between parcels and MOD-IV is now over 99%. Union County - The Block, Lot, and QCODE values for evey parcel in Mountainside Borough were updated to match the current MOD-IV data. The values in the OLD_PROP_ID field in the MOD-IV were used to determine new Block, Lot, and QCODE values for the parcels. Upon completion, 100% of the parcels had a matching MOD-IV record and more than 99% of the MOD-IV records had a matching parcel. The Mountainside parcels were also edge matched with the adjacent municipalities. All parcels along the municipal boundary that spanned the boundary were merged into one parcel if they were fully assessed in only one town. Any missing subdivisions, parcel mergers, or missing condos, that were discovered during the edge matching or parcel re-numbering processes, were added.
Somerset County Submitted Updates Parcels from Montgomery Township and Franklin Township are mainatained by each municipality. Data from both municipalities are directly incorporated into the county parcel dataset. Using the MOD-IV data, unmatched parcels are investiagted for discrepancies and errors. Errors or required updates are corrected by Somerset County. QA/QC proceedurs are run by Somerset County to find and correct discrepancies in the PAMS_PIN, BLOCK, LOT AND QCODE fields. New subdivisions are added to parcels using digital CAD files or filed subdivision plats. ArcMap COGO tools are used to perform updates.
The parcels for the following Monmouth County municipalities were replaced with tax map based municipal parcels: Ocean Township Marlboro Township Eatontown Borough Manasquan Borough Prior to incorporating the municipal parcels, QA/QC checks were run against the muncipal parcel data. The checks included the following steps: Topology - The following topology rules were applied and data were validated against these rules. Any parcel errors were corrected or marked as exceptions where appropriate. Gaps for rights-of-way were marked as exceptions: Parcels must be covered by county polygon Parcels must be covered by a municipality Parcels must not overlap Parcels must not have gaps Edge Matching - Parcels were edge matched at county and municipal boundaries using the tax maps and filed legal documents where required. 2015 NJ orthophotos were used as the base map for this process. All parcels that span a municipal or county boundary, but are only assessed in one municipality, were merged info one parcel based on the muncipality where they are assessed per the MOD-IV database. Attribute Validation - The following steps were used to validate parcel attributes: Verified and corrected the PAMS_PIN field against the MUN, BLOCK, LOT and QCODE. NJOGIS checked the MUN, BLOCK and LOT fields for missing values. Verified and corrected records with duplicate PAMS_PIN values. There are a small number of records where the duplicate values could not be corrected at this time. All QCODE records with a NULL value were replaced with a zero-length string value (blank).
Somerset County NJOGIS Ran QA/QC processes on the submitted parcel data Topology Rules Parcels must be covered by county polygon Parcels must be covered by a municipality Parcels must not overlap Parcels must not have gaps All ROW gaps marked as exceptions. All parcel “crop circles” (parcels representing the house on a farm) marked as exceptions. Gaps and overlaps resolved based on best judgement, context clues and tax maps. Edge Matching Edge matched parcels along county boundary first, then between municipal boundaries in Somerset County. To do this, we looked at adjacent parcels across boundaries and called out areas where we thought they should line up. We then looked at varies sources like NJ aerial imagery, MOD-IV and tax maps for further information. Parcels spanning the boundary were merged based on where they are assessed according to the MOD-IV. Attribute Validation 1. Verified and corrected the PAMS_PIN field against the MUN, BLOCK, LOT and QCODE. 2. We checked the MUN, BLOCK and LOT fields for missing values. 3. Verified and corrected records with duplicate PAMS_PIN values. There are a small number of records where the duplicate values could not be corrected at this time. 4. All QCODE records with a NULL value were replaced with a zero-length string value (blank). 5. For farmland asessed parcels the non-QFARM and QFARM ploygons were reversed. The QFARM value was assigned to the non-FARM circular polygon. Queries were run and where found these values were properly reversed.
Metadata revised to correct formatting errors, rearrange selected information, and add distribution formats.
Statewide parcel composite was re-generated with a join to the MOD-IV data for the 2017 tax year. Processing model was used to create the joined parcel and MOD-IV feature class, using the PIN_NODUP field. Using this method, any parcels with a duplicate PAMS_PIN value were excluded from joining with the MOD-IV data.
The following county parcels were edge matched with adjacent counties that were recently updated. Monmouth County Union County Morris County Bergen County Atlantic County Any parcels from at a county boundary that are fully assessed in one county only were merged into one parcel that spans the county boundary.
Middlesex County Ocean County Burlington County Camden County Mercer County Hunterdon County Salem County Hudson County NJOGIS Ran QA/QC processes on the submitted parcel data. Topology Rules Parcels must be covered by county polygon Parcels must be covered by a municipality Parcels must not overlap Parcels must not have gaps All ROW gaps marked as exceptions. All parcel “crop circles” (parcels representing the house on a farm) marked as exceptions. Gaps and overlaps resolved based on best judgement, context clues and tax maps. Edge Matching Edge matched parcels along county boundary first, then between municipal boundaries in Somerset County. To do this, we looked at adjacent parcels across boundaries and called out areas where we thought they should line up. We then looked at varies sources like NJ aerial imagery, MOD-IV and tax maps for further information. Parcels spanning the boundary were merged based on where they are assessed according to the MOD-IV. Attribute Validation 1. Verified and corrected the PAMS_PIN field against the MUN, BLOCK, LOT and QCODE. 2. We checked the MUN, BLOCK and LOT fields for missing values. 3. Verified and corrected records with duplicate PAMS_PIN values. There are a small number of records where the duplicate values could not be corrected at this time. 4. All QCODE records with a NULL value were replaced with a zero-length string value (blank). 5. For farmland asessed parcels the non-QFARM and QFARM ploygons were reversed. The QFARM value was assigned to the non-FARM circular polygon. Queries were run and where found these values were properly reversed.
Statewide parcel composite was re-generated with a join to the MOD-IV data for the 2018 tax year. Processing model was used to create the joined parcel and MOD-IV feature class, using the PIN_NODUP field. Using this method, any parcels with a duplicate PAMS_PIN value were excluded from joining with the MOD-IV data. All of the MOD-IV records for Vernon Township, Sussex County were exluded from joining with the parcels due to block and lot renumbering for new tax maps. The current parcels for Sussex County do not yet reflect the new block and lot numbers, but the MOD-IV data has already been updated with the new block and lot numbers.
Metadata were edited to provide corrections, improved wording to Overview sections, and updated contact information. No changes were made to the data. Preliminary edits were made by Doug Schleifer, Manager, NJOGIS.
Sussex County - Vernon Township Revised block and lot numbers from the new Vernon Township Tax Maps, approved the NJ Department of Treasury, Tax Map Division on 02/11/2019, were incorporated using parcel data obtained from Sussex County in January, 2020. These updated parcels do not include the tax map based parcel geometry prepared by Spatial Data Logic. The revised geometry will be incorporated during the next overall Sussex County parcel update.
Essex County-Irvington Township Block 183 Lots 9.01 - 9.04 - In the Essex County parcels the parcels were attributed starting with lot 9.01 from south to north. Per the Irvington tax maps, lot 9.01 is actually located at the north end and then run sequentially south. Lot numbers were revised by NJOGIS to correspond to the tax maps. Address points also had to be properly revised and reloacted.
Monmouth County-Millstone Township Block 7 Lots 4, 4.01 and 5.03 - Per the request of the parcels owner, NJOGIS reviewed parcels per Millstone Township tax maps. Lot 5.03 was merged into lot 4.01 back in 2002. NJOGIS merged parcels amd adjusted lots 4 and 4.01 to more accurately represnt the tax maps. Lot 7.03 also had to be slightly adjusted to maintain topology.
Cumberland County NJOGIS ran QA/QC processes on the submitted parcel data Topology Rules Parcels must be covered by county polygon Parcels must be covered by a municipality Parcels must not overlap Parcels must not have gaps All ROW gaps marked as exceptions. All parcel “crop circles” (parcels representing the house on a farm) marked as exceptions. Gaps and overlaps resolved based on best judgement, context clues and tax maps. Edge Matching Edge matched parcels along county boundary first, then between municipal boundaries in Cumberland County. To do this, we looked at adjacent parcels across boundaries and called out areas where we thought they should line up. We then looked at varies sources like NJ aerial imagery, and tax maps for further information. Parcels spanning the boundary were merged based on where they are assessed according to the . Attribute Validation 1. Verified and corrected the PAMS_PIN field against the MUN, BLOCK, LOT and QCODE. 2. We checked the MUN, BLOCK and LOT fields for missing values. 3. Verified and corrected records with duplicate PAMS_PIN values. There are a small number of records where the duplicate values could not be corrected at this time. 4. All QCODE records with a NULL value were replaced with a zero-length string value (blank). 5. For farmland asessed parcels in Vineland, the non-QFARM and QFARM ploygons were reversed. The QFARM value was assigned to the non-FARM circular polygon. Queries were run and where found these values were properly reversed.
Atlantic County Cape May County During Cumberland County parcels edge matching process, some parcels in the above adjacent counties were adjusted along the county boundary.
NJOGIS requested the latest Parcel data from the following Counties: Bergen, Passiac, Sussex, Union and Montclair Township in Essex County And performed the following QA/QC processes on the submitted parcel data. Topology Rules for Spatial data include: -Parcels must be covered by county polygon -Parcels must be covered by a municipality -Parcels must not overlap -Parcels must not have gaps Parcel gap and overlap errors resolved based on best judgement, context clues, and tax maps. 1Integrate software used to identify and correct polygon geometries such as kickbacks, multipart geometries, and spikes. Where applicable, parcel edge matching occurred along municipal boundaries within the County and along County boundary with neighboring County parcel data. Sources for verification included NJ aerial imagery, municipal tax maps, and Mod IV tax records. Parcel geometries split across municipal boundaries were merged into a single polygon if Land Value was 0 for one polygon according to Mod IV tax records.
Block and Lot numbers revised to the new Highland Park Borough Tax Maps, approved by the NJ Department of Treasury, Tax Map Division, using parcel data obtained from Middlesex County in July, 2021.
Statewide parcel composite was re-generated with a join to the MOD-IV data for the 2020 tax year. Processing model was used to create the joined parcel and MOD-IV feature class, using the PIN_NODUP field. Using this method, any parcels with a duplicate PAMS_PIN value were excluded from joining with the MOD-IV data. In compliance with the provisions and protections afforded the personally identifiable information of certain persons, as enacted by P.L. 2020, c. 125, OGIS has redacted owner names from this database.
NJOGIS requested the latest Parcel data from the following Counties: Burlington, Cape May, Mercer And performed the following QA/QC processes on the submitted parcel data. Topology Rules for Spatial data include: -Parcels must be covered by county polygon -Parcels must be covered by a municipality -Parcels must not overlap -Parcels must not have gaps Parcel gap and overlap errors resolved based on best judgement, context clues, and tax maps. 1Integrate software used to identify and correct polygon geometries such as kickbacks, multipart geometries, and spikes. Where applicable, parcel edge matching occurred along municipal boundaries within the County and along County boundary with neighboring County parcel data. Sources for verification included NJ aerial imagery, municipal tax maps, and Mod IV tax records. Parcel geometries split across municipal boundaries were merged into a single polygon if Land Value was 0 for one polygon according to Mod IV tax records.
Parcels in the following tax blocks, located in Hamilton Township - Atlantic County, were recreated to align with Statewide aerial imagery and other Statewide datasets, such as road centerlines and address points. Information contained on the municipal tax maps were used to as the primary source to update parcel boundaries in Blocks 1132.18, 1132.29 – 1132.33, and portions of 1132.01. The boundaries of approximately 430 parcels were updated during this effort.
NJOGIS requested the latest Parcel data from the following Counties: Camden, Gloucester, Morris, Ocean, Salem, Warren And performed the following QA/QC processes on the submitted parcel data. Topology Rules for Spatial data include: -Parcels must be covered by county polygon -Parcels must be covered by a municipality -Parcels must not overlap -Parcels must not have gaps Parcel gap and overlap errors resolved based on best judgement, context clues, and tax maps. 1Integrate software used to identify and correct polygon geometries such as kickbacks, multipart geometries, and spikes. Where applicable, parcel edge matching occurred along municipal boundaries within the County and along County boundary with neighboring County parcel data. Sources for verification included NJ aerial imagery, municipal tax maps, and Mod IV tax records. Parcel geometries split across municipal boundaries were merged into a single polygon if Land Value was $0 for one of the polygons, with both having the same landowner, according to Mod IV tax records. Statewide parcel composite was re-generated with a join to the MOD-IV data for the 2021 tax year. Processing models were used to create the joined parcel and MOD-IV feature classes, using the PIN_NODUP field. Using this method, any parcels with a duplicate PAMS_PIN value were excluded from joining with the MOD-IV data. In compliance with the provisions and protections afforded the personally identifiable information of certain persons, as enacted by P.L. 2020, c. 125, OGIS has redacted owner names from this database.
All parcels within Edison Township were replaced with data created from new tax maps, approved by the NJ Department of Treasury, Tax Map Division, and obtained from Middlesex County in October 2022. Parcels resulting from the digital tax maps also included new tax Block and Lot numbers. Parcels adjustments and edge matching along the boundary with Union County.
Statewide parcel composite was re-generated with a join to the MOD-IV data for the 2021 tax year. Processing model was used to create the joined parcel and MOD-IV feature class, using the PIN_NODUP field. Using this method, any parcels with a duplicate PAMS_PIN value were excluded from joining with the MOD-IV data. In compliance with the provisions and protections afforded the personally identifiable information of certain persons, as enacted by P.L. 2020, c. 125, OGIS has redacted owner names from this database.
All parcels within Elizabeth Township were replaced with data created from new tax maps, approved by the NJ Department of Treasury, Tax Map Division, and obtained from Union County in September 2023. Parcels resulting from the digital tax maps also included new tax Block and Lot numbers. Parcels adjustments and edge matching occured along the boundary with neighboring municipalities within Union County and along the Essex County boundary.
NJOGIS requested the latest Parcel data from the following Counties: Atlantic, Essex, Somerset And performed the following QA/QC processes on the submitted parcel data. Topology Rules for Spatial data include: -Parcels must be covered by county polygon -Parcels must be covered by a municipality -Parcels must not overlap -Parcels must not have gaps Parcel gap and overlap errors resolved based on best judgement, context clues, and tax maps. 1Integrate software used to identify and correct polygon geometries such as kickbacks, multipart geometries, and spikes. Where applicable, parcel edge matching occurred along municipal boundaries within the County and along County boundary with neighboring County parcel data. Sources for verification included NJ aerial imagery, municipal tax maps, and Mod IV tax records. Parcel geometries split across municipal boundaries were merged into a single polygon if Land Value was 0 for one polygon according to Mod IV tax records.
Statewide parcel composite was re-generated with a join to the MOD-IV data for the 2022 tax year. Processing model was used to create the joined parcel and MOD-IV feature class, using the PIN_NODUP field. Using this method, any parcels with a duplicate PAMS_PIN value were excluded from joining with the MOD-IV data. In compliance with the provisions and protections afforded the personally identifiable information of certain persons, as enacted by P.L. 2020, c. 125, OGIS has redacted owner names from this database.
NJOGIS requested the latest Parcel data from the following Counties: Cumberland, Hudson, Middlesex, Somerset At the request of the municipality, parcels for Marlboro Township in Monmouth County were replaced with a more current dataset. The following QA/QC processes were performed on the submitted parcel data. Topology Rules for Spatial data include: -Parcels must be covered by county polygon -Parcels must be covered by a municipality -Parcels must not overlap -Parcels must not have gaps Parcel gap and overlap errors resolved based on best judgement, context clues, and tax maps. 1Integrate software used to identify and correct polygon geometries such as kickbacks, multipart geometries, and spikes. Where applicable, parcel edge matching occurred along municipal boundaries within the County and along County boundary with neighboring County parcel data. Sources for verification included NJ aerial imagery, municipal tax maps, and Mod IV tax records. Parcel geometries split across municipal boundaries were merged into a single polygon if Land Value was 0 for one polygon according to Mod IV tax records.
Tax parcel boundary polygons, with attribute information joined from MOD-IV. PAMS_PIN provides a foreign key to property tax system records from MOD-IV or PAMS. By definition this identifier should be unique, but in practice it is not. PIN_NODUP, established by querying for unique values of PAMS_PIN, is used for a unique foreign key to MOD-IV data.