<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Burlington County Department of Information Technology</origin>
<pubdate>20100720</pubdate>
<title Sync="FALSE">TaxParcel</title>
<geoform Sync="TRUE">vector digital data</geoform>
<pubinfo>
<pubplace>Mount Holly, New Jersey</pubplace>
<publish>Burlington County Department of Information Technology</publish>
</pubinfo>
<onlink Sync="FALSE">withheld</onlink>
<ftname Sync="FALSE">TaxParcel</ftname>
</citeinfo>
</citation>
<descript>
<abstract>This GIS data set contains parcels created by the Burlington County Department of Information Technology (BCDIT) and the New Jersey Pinelands Comission (NJPC) for Burlington County, New Jersey.
The BCDIT data consist of parcels mapped on municipal tax maps for the non-Pinelands portion of Burlington County. This includes the following townships outside of the Pinelands: Beverly City, Bordentown City, Bordentown Township, Burlington City, Burlington Township, Chesterfield, Cinnaminson, Delanco, Delran, Eastampton, Edgewater Park, Florence, Fieldsboro, Hainesport, Lumberton, Mansfield, Maple Shade, Moorestown, Mount Holly, Mount Laurel, Palmyra, Pemberton Borough, Riverton, Riverside, Springfield, Westampton and Willingboro. This also includes the non-Pinelands portions of the following towns: Evesham, Medford, New Hanover, Pemberton Township, Southampton and Wrightstown. The original data were developed in-house between 1996-2000. Between 2000-2008 the data were updated in-house in various years on a municipality by municipality basis. In 2009 the Mount Laurel data were updated by a consultant working for the township.
The NJPC data consist of parcels mapped on municipal tax maps within the New Jersey Pinelands area. The municipalities include Bass River Twp, Evesham Twp, Medford Twp, Medford Lakes Twp, New Hanover Twp, North Hanover Twp, Pemberton Twp, Shamong Twp, Southampton Twp, Springfield Twp, Tabernacle Twp, Washington Twp and Woodland Twp.
The original data, created in 2001, were a compilation of parcel data acquired from municipal and county sources and parcel data created for the NJPC by BAE Systems ADR for those areas where parcels data did not exist. The data were updated in 2006 and 2009. During the 2009 update Bass River Twp was developed in-house and integrated into the NJPC data set.
The 2009, the NJPC parcels were integrated into the BCDIT countywide data set during the New Jersey Office of Information Technology, Office of GIS Parcels Normalization Project to develop a statewide composite of parcel data sets.</abstract>
<purpose>
This dataset serves as part of the foundation of Burlington County's continuing spatial data network and will help form a resource from which many County organizations can draw benefit. Such benefits include Megan's Law Notification mapping, Farmland and Open Space assessments, maps for trials, property specific wetland and soil analysis, geocoding of animal shelter intakes and other address based information, planning and incorporation into the County's Pictometry Online application.
This parcel data set provides the NJPC with the spatial property information data needed for regional land use analysis with respect to land acquisition proposals, management area changes, rezoning, letters of interpretation, density transfers, enforcement issues, Long Term Economic Monitoring (LTEM) and watershed analysis. The data set also serves as the base for various other GIS layers such as zoning and management area data.
</purpose>
<supplinf>
Metadata for the source data from Burlington County that was used to create the original parcels is available as separate html files and MS Word documents, and contains details regarding the construction of the parcels on a municipality by municipality basis. A table containing MOD4 ownership information may be included in the geodatabase or can be requested separately.
In order to use this table with the parcels data, perform a Join or Relate using the NEWGISID or similar attribute containing a parcel identification number (PIN).
This dataset was created using scanned mylar taxmaps and does not represent all of the current blocks and lots in the Pinelands Area. Until tax data and parcel geometry are created in a real time fashion all parcel data layers will be dated.
Although this data set does not contain property assessment information, each parcel contains an attribute named PIN (Parcel Identification Number) which uniquely identifies the parcel. The PIN field can be used to join to the MOD4 database that is prepared by the Department of the Treasury, Office of Taxation.
</supplinf>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<mdattim>
<sngdate>
<caldate>2001</caldate>
</sngdate>
<sngdate>
<caldate>2006</caldate>
</sngdate>
<sngdate>
<caldate>20091203</caldate>
</sngdate>
<sngdate>
<caldate>20100222</caldate>
</sngdate>
<sngdate>
<caldate>20100720</caldate>
</sngdate>
<sngdate>
<caldate>20110216</caldate>
</sngdate>
</mdattim>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-75.057454</westbc>
<eastbc Sync="TRUE">-74.388666</eastbc>
<northbc Sync="TRUE">40.183299</northbc>
<southbc Sync="TRUE">39.542223</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">336377.406250</leftbc>
<rightbc Sync="TRUE">523229.912811</rightbc>
<bottombc Sync="TRUE">258654.739709</bottombc>
<topbc Sync="TRUE">491682.999863</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>ISO 19115 Category</themekt>
<themekey>planningCadastre</themekey>
</theme>
<theme>
<themekt>NJGIN</themekt>
<themekey>njfw_cadastral</themekey>
</theme>
<theme>
<themekt>None</themekt>
<themekey>municipal</themekey>
<themekey>municipality</themekey>
<themekey>municipalities</themekey>
<themekey>county</themekey>
<themekey>parcel</themekey>
<themekey>parcels</themekey>
<themekey>lot</themekey>
<themekey>lots</themekey>
<themekey>block</themekey>
<themekey>blocks</themekey>
<themekey>boundary</themekey>
<themekey>boundaries</themekey>
<themekey>tax</themekey>
<themekey>assessment</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Bass River Township</placekey>
<placekey>Beverly</placekey>
<placekey>Bordentown</placekey>
<placekey>Bordentown Township</placekey>
<placekey>Burlington</placekey>
<placekey>Burlington Township</placekey>
<placekey>Chesterfield Township</placekey>
<placekey>Cinnaminson Township</placekey>
<placekey>Delanco Township</placekey>
<placekey>Delran Township</placekey>
<placekey>Easthampton Township</placekey>
<placekey>Edgewater Park Township</placekey>
<placekey>Evesham Township</placekey>
<placekey>Fieldsboro Borough</placekey>
<placekey>Florence Township</placekey>
<placekey>Hainesport Township</placekey>
<placekey>Lumberton Township</placekey>
<placekey>Mansfield Township</placekey>
<placekey>Maple Shade Township</placekey>
<placekey>Medford Lakes Borough</placekey>
<placekey>Medford Township</placekey>
<placekey>Moorestown Township</placekey>
<placekey>Mount Holly Township</placekey>
<placekey>Mount Laurel Township</placekey>
<placekey>New Hanover Township</placekey>
<placekey>North Hanover Township</placekey>
<placekey>Palmyra Borough</placekey>
<placekey>Pemberton Borough</placekey>
<placekey>Pemberton Township</placekey>
<placekey>Riverside Township</placekey>
<placekey>Riverton Borough</placekey>
<placekey>Shamong Township</placekey>
<placekey>Southampton Township</placekey>
<placekey>Springfield Township</placekey>
<placekey>Tabernacle Township</placekey>
<placekey>Washington Township</placekey>
<placekey>Westhampton Township</placekey>
<placekey>Willingboro Township</placekey>
<placekey>Woodland Township</placekey>
<placekey>Wrightstown Borough</placekey>
<placekey>Burlington County</placekey>
<placekey>New Jersey</placekey>
<placekey>NJ</placekey>
<placekey>USA</placekey>
</place>
<temporal>
<tempkt>None</tempkt>
<tempkey>2001</tempkey>
<tempkey>2006</tempkey>
<tempkey>2009</tempkey>
<tempkey>2010</tempkey>
</temporal>
</keywords>
<accconst>none</accconst>
<useconst>For all data contained herein, Burlington County makes no representations of any kind, including but not limited to 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. Burlington County assumes no responsibility to maintain the digital data layers in any manner or form. Recipients of digital files are not entitled to any file revisions, updates, corrections or new releases. Burlington County shall not be liable for any loss of profits or consequential damages, or claims against the User by third parties. The data set is provided, as is, without warranty of any kind and the user is responsible for understanding the accuracy limitations of all digital data provided herein, as documented in the accompanying Metadata files. Users agree to hold Burlington County, New Jersey and all their employees, and agents harmless from any claim, suit, or proceeding arising out of the use of the data in accordance with this agreement, including indemnification of Burlington County and the State of New Jersey for reasonable expenses incurred in defending such claims. By using data provided herein, the user acknowledges the terms and conditions have been read and that the user is bound by these criteria.</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Burlington County Department of Information Technology</cntorg>
<cntper>Merrilee J. Torres</cntper>
</cntorgp>
<cntpos>GIS Specialist</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>PO Box 6000, 49 Rancocas Road</address>
<city>Mount Holly</city>
<state>NJ</state>
<postal>08060</postal>
<country>USA</country>
</cntaddr>
<cntvoice>609-702-7067</cntvoice>
<cntfax>609-265-3721</cntfax>
<cntemail>mtorres@co.burlington.nj.us</cntemail>
</cntinfo>
</ptcontac>
<datacred>New Jersey Pinelands Commission - Bass River Twp, Evesham Twp, Medford Twp, Medford Lakes Twp, New Hanover Twp, North Hanover Twp, Pemberton Twp, Shamong Twp, Southampton Twp, Springfield Twp, Tabernacle Twp, Washington Twp and Woodland Twp</datacred>
<secinfo>
<secsys>NJGIN</secsys>
<secclass>public</secclass>
<sechandl>no special handling required</sechandl>
</secinfo>
<native Sync="FALSE">ESRI ArcCatalog 9.3.1.1850</native>
<crossref>
<citeinfo>
<origin>New Jersey Pinelands Commission</origin>
<pubdate>200811</pubdate>
<title>NJ Pinelands Parcel Data Set</title>
<edition>Third</edition>
<geoform>vector digital data</geoform>
<pubinfo>
<pubplace>New Lisbon, New Jersey</pubplace>
<publish>New Jersey Pinelands Commission</publish>
</pubinfo>
</citeinfo>
</crossref>
<natvform Sync="FALSE">Feature Class</natvform>
</idinfo>
<dataqual>
<attracc>
<attraccr>
Parcels that existed in 2001 were acquired from their respective municipalities. Each table was manually checked for errors of omission and commission. All null records were removed from the table using ArcInfo 7.x.
Those parcels created by BAE Systems ADR were checked using "Dog Creek" software, an automated error correction and reporting software used to check for inconsistencies in the attribute information.
</attraccr>
</attracc>
<logic>The NJPC 2001 data layer topology was originally created and checked using the clean command in ArcInfo. Currently, all polygons are coincident except where street rights-of-way separate parcel boundaries. All topology is checked using the ArcGIS topology tool/editor using the rules, "Must not have gaps and Must not overlap."
For the BCDIT data set, four topology rules were used to test the boundary and area feature classes. The rule 'Must not have dangles' was set to ensure a dangle-free boundary feature class. The rule 'Must not intersect or touch interior' was added to ensure that lines in the boundary feature class do not overlap and lines connect to one another only at the endpoint. The rule ' Must be covered by the boundary of' was added to ensure that lines in the boundary feature class are covered by the boundaries of polygons in the area feature class. This rule avoided extraneous lines in the tax parcels. The last rule ' Boundary must be covered by' was applied to the area feature class to ensure that there was a corresponding line in the boundary feature class to each polygon boundary. The boundary and area feature classes were validated against these rules to build topology.</logic>
<complete>Data complete as per available tax maps. Due to the fact that real-time tax maps are non-existent, their is a time lag between the parcels that have been digitized and those that have recently been subdivided, re-subdivided, consolidated, or corrected. Until tax parcels are updated in a real time fashion, this data layer can be considered complete.</complete>
<posacc>
<horizpa>
<horizpar>
Parcels that existed in 2001 that were acquired from their respective municipalities were QAQC'd by their respective owners and details on those processes are available from those entities. However, the NJPC spot checked these data for errors using 2002 DVRPC BW Orthophotos.
For those parcels created by BAE Systems ADR:
The scanned mylar taxmaps were registered with the New Jersey Department of Transportation street centerline layer as adjusted to 200 scale aerial photography. RMS errors were recorded in spreadsheets and ranged from .01 to 11. Variability in error was directly related to the degree of development that existed on the tax maps. More control points for registration existed on those maps that had multiple roads and many parcels. As a result, urban area maps had lower RMS error values where more rural area maps had higher RMS error values.
</horizpar>
<qhorizpa>
<horizpae>The accuracy of the data set depends on the RMS value of each individual tax map. A single value to represent horizontal accuracy can not be determined due to varying RMS errors.</horizpae>
</qhorizpa>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>BAE SYSTEMS ADR for the Delaware Valley Regional Planning Commission</origin>
<pubdate>2001</pubdate>
<title>DVRPC Digital Orthogonal 1:2400 Black and White Aerial Photographs</title>
<geoform>raster digital data</geoform>
<pubinfo>
<pubplace>Philadelphia, Pennsylvania</pubplace>
<publish>Delaware Valley Regional Planning Commission</publish>
</pubinfo>
<othercit>Black and White Orthophotos at 1:2400 scale from Delaware Valley Regional Planning Commission were used to check road centerline data and adjusted if necessary</othercit>
</citeinfo>
</srccite>
<srcscale>2400</srcscale>
<typesrc>CD-ROM</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>2000</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>DVRPC 2000 Orthophotos</srccitea>
<srccontr>Black and White Orthophotos from Delaware Valley Regional Planning Commission</srccontr>
</srcinfo>
<procstep>
<procdesc>
In 2001 parcel data existed for Evsham Twp, Medford Twp, Medford Lakes Twp, New Hanover Twp, North Hanover Twp, Pemberton Twp, Shamong Twp, Southampton Twp, Springfield Twp, Tabernacle Twp, Washington Twp and Woodland Twp. Data sets were acquired from these municipalities and edgematched by the New Jersey Pineland Commission (NJPC) GIS Lab using the following base data: NJDOT Roads 1995; 2000 DVRPC B/W Aerial Photos. In some cases lots had to be increased or reduced in size for edgematching to work. In these cases, a best "guess" approach was used along with the previously mentioned base layers. However, all original data were copied and placed into individual data sets, by municipality, so that the original linework could be reviewed by staff if a discrepancy occured.
For those municipalities where parcel data did not exist NJPC hired BAE Systems ADR to digitize the missing parcels. The methodology is as follows:
1995 NJDOT road centerlines data were adjusted to match the 1:2400 scale black and white digital orthophotos. An additional field was added to the road centerline attribute table with road width values. Road width values were derived from annotation on the scanned mylar taxmaps. Using these values, road buffering was executed. The mylar taxmaps were registered to match block faces and road intersections of the road buffers. RMS errors were recorded. Digitization of these tax maps, data capture, and mosaicing was done in AutoCad. All linework was edgematched to complete a final municipal parcel data set. The line work was then compared to the 2000 B/W Aerials and slight adjustments were made to correct error. The CAD layer was then converted to an ArcInfo 7.x coverage.
Municipality code, block, sub-block, lot and sub-lot were added to the attribute table. The qualifier information on each tax map was not recorded in the geometry due to absence of information and inconsistencies in the annotation on the tax maps. These fields were then concatenated to create a unique Parcel Identification Number (PIN).
</procdesc>
<procdate>2001</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>New Jersey Pinelands Commission</cntorg>
</cntorgp>
<cntvoice>609-894-7300</cntvoice>
<cntfax>609-894-7330</cntfax>
<cntemail>info@njpines.state.nj.us</cntemail>
<hours>9:00-5:00</hours>
<cntinst>Email Public Programs office using contact email. Requests will be sent to the GIS Lab.</cntinst>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
In 2006 the NJPC updated the 2001 data set in-house using Western Technologies registered and rectified (RR) tax maps. In addition to the RR maps, Western Technologies provided a Parcel Change Detection (PCD) shapefile that identified parcels that had their geometry modified between 2001 and 2006. Heads-up digitizing was used to make the parcel geometry changes using the RR taxmaps and the PCD shapefile as base layers. This process was used on all of the municipalities in the Pinelands using ESRI ArcEditor 9.1.
</procdesc>
<procdate>2007</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>New Jersey Pinelands Commission</cntorg>
</cntorgp>
<cntvoice>609-894-7300</cntvoice>
<cntfax>609-894-7330</cntfax>
<cntemail>info@njpines.state.nj.us</cntemail>
<hours>9:00-5:00</hours>
<cntinst>Email Public Programs office using contact email. Requests will be sent to the GIS Lab.</cntinst>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
As part of the New Jersey Office of Information Technology, Office of GIS (OGIS) effort to develop a statewide composite of parcel data sets, parcels sharing boundaries with municipal boundaries were modified to be coincident to the municipal boundaries data developed in 2008 by OGIS 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 data set to the data steward and OGIS.
</procdesc>
<procdate>2009</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Civil Solutions</cntorg>
<cntper>Stephen Eckhardt</cntper>
</cntorgp>
<cntpos>GIS Client Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>800 S White Horse Pike, PO Box 579</address>
<city>Hammonton</city>
<state>NJ</state>
<postal>08037-2019</postal>
<country>USA</country>
</cntaddr>
<cntvoice>(800) 924-0482</cntvoice>
<cntfax>(609) 704-8011</cntfax>
<cntemail>seckh@arh-us.com</cntemail>
<hours>8-5</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
201020 Burlington County added several fields to make the dataset compatible with the original dataset and projects used by Burlington County including: NEWGISID, PARCELTYPE, CALCACREAGE, TAX_ACRE, ALT_ID, PINECODE, MUNITAXDISTRICT, ADD_BLOCK, ADD_LOT
Not all are currently populated.
</procdesc>
<procdate>20100222</procdate>
</procstep>
<procstep>
<procdesc>
Burlington County downloaded the edgematched parcels from NJGIN in 201001. In order to make the dataset compatible with Burlington County's previous parcel projects and to support upcoming projects several fields were added and poplulated. These include NEWGISID, PARCELTYPE, CALCACREAGE, TAX_ACRE, ALT_ID, PINECODE, MUNITAXDISTRICT, ADD_BLOCK, ADD_LOT, TAXSHEET, XCOORD, YCOORD, LONGITUDE, LATITUDE, ENVELOPME, XMIN, YMIN, XMAX, YMAX, XMIN_LL, YMIN_LL, XMAX_LL, YMAX_LL, ENVL_LL.
In 201004 several corrections were made to the Alt_id values.
</procdesc>
<procdate>20100511</procdate>
</procstep>
<procstep>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>County of Burlington, NJ</cntorg>
<cntper>Merrilee Torres</cntper>
</cntorgp>
<cntpos>GIS Specialist 1</cntpos>
<cntvoice>709-702-7067</cntvoice>
<cntfax>609-265-3721</cntfax>
<cntemail>mtorres@co.burlington.nj.us</cntemail>
<hours>8-5</hours>
<cntaddr>
<address>PO Box 6000</address>
<address>49 Rancocas Rd</address>
<addrtype>mailing and physical address</addrtype>
<city>Mount Holly</city>
<state>NJ</state>
<postal>08060</postal>
<country>USA</country>
</cntaddr>
</cntinfo>
</proccont>
<procdesc>For the original data BCDIT created in1996-2000 and updates performed before 2003, BCDIT scanned original tax sheet mylars &amp; vellums that were produced by township engineer &amp; certified by NJ Department of Taxation. These scans were then gridded to the NJ Stateplane NAD83 coordinate system and then warped to the created grid using road intersection coordinates either collected with GPS or taken from various digital orthophotography sources depending on the actual year the data were created. All work was accomplished in ArcInfo Workstation 7x or 8x. This process used Rectif.aml, an AML developed by ESRI and BCDIT &amp; RMS errors were recorded. The digital orthophotography sources include 1991 grayscale orthophotos from Mark Hurd, 1995 false color infrared orthophotos from New Jersey Department of Environmental Protection and 2000 grayscale orthophotos from the Delaware Valley Regional Planning Commission.
Lots were then heads up digitized as a line coverage in ArcInfo Workstation and, once the sheet was completely digitized, a polygon coverage was built from the lines. Parcels were overlaid on the digital orthophotography and road centerlines and adjusted to these sources as needed. Road centerline source data consisted of ETAK roads prior to 1998 and subsequent to 1998 BCDIT's in-house GPS road centerlines were used.
Parcels were stored as separate ArcInfo coverages for each municipality. For updates, subdivision plans for the township were obtained from the Burlington County Clerk's Office and used to supplement tax maps in cases where the new lots were not present on the municipal tax map.
Municipalities were updated in the following years: 2001- Bordentown City &amp; Township, Burlington City &amp; Township, Chesterfield, Florence, Lumberton, Mansfield, New Hanover, North Hanover, Palmyra, Pemberton Boro, Riverside, Southamton, &amp; Springfield. 2002- Cinnaminson, Eastampton, Edgewater Park, Hainesport, Maple Shade, Mount Holly, Shamong, Tabernacle,Woodland &amp; Wrightstown. 2003- Bass River, Evesham, Medford Township, Mount Laurel &amp; Westampton. </procdesc>
<procsv>ArcInfo 7x</procsv>
<procdate>1995-2003</procdate>
</procstep>
<srcinfo>
<typesrc>CD-ROM</typesrc>
<srccitea>1991 Orthos</srccitea>
<srccontr>Mark Hurd</srccontr>
</srcinfo>
<srcinfo>
<typesrc>CD-ROM</typesrc>
<srccitea>1995/1997 NJDEP orthophotos</srccitea>
<srccontr>New Jersey Department of Environmental Protection</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Chesterfield Township 2007 CAD data from Environmental Resolutions</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Burlington Township 2007 CAD data from Alaimo Group </srccontr>
</srcinfo>
<srcinfo>
<srccontr>2005 CAD data from Environmental Resolutions</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Delanco Township 2005 CAD data and shapefile from Birdsall Engineering</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Delran Township 2006 CAD data from Pennoni Associates </srccontr>
</srcinfo>
<srcinfo>
<srccontr>Florence Township 2008 CAD data from Dante Guzzi Engineering</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Medford Township 2003 shapefile from Environmental Resolutions; 2008 shapefile from Environmental Resolutions</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Moorestown Township 2000 CAD data from Pennoni Associates; 2007 georeferenced CAD data from Remington and Vernick Engineers</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Mount Laurel Township 2003 CAD data from Alaimo Group; 2009 shapefile updated by Remington and Vernick</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Pemberton Borough 2006 CAD data from Alaimo Group</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Pemberton Township 2001 shapefile created by Civil Solutions</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Southampton Township 2006 CAD data from Alaimo Group</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Springfield Township 2007 CAD data from Lippincott and Jacobs</srccontr>
</srcinfo>
<srcinfo>
<srccontr>Willingboro Township 1998 CAD data from Lord Anderson Worrell and Barnett; 2006 CAD data from Remington and Vernick Engineers</srccontr>
</srcinfo>
<srcinfo>
<srcscale>2400</srcscale>
<srccitea>2002 High Resolution Orthoimagery </srccitea>
<srccontr>State of NJ, Office of Information Technology, Office of GIS</srccontr>
</srcinfo>
<srcinfo>
<srcscale>2400</srcscale>
<srccitea>2005 High Resolution Orthoimagery </srccitea>
<srccontr>Delaware Valley Regional Planning Commission</srccontr>
</srcinfo>
<srcinfo>
<srcscale>2400</srcscale>
<srccitea>2007 High Resolution Orthoimagery </srccitea>
<srccontr>State of NJ, Office of Information Technology, Office of GIS</srccontr>
</srcinfo>
<procstep>
<proccont>
<cntinfo>
<cntaddr>
<address>PO Box 6000</address>
<addrtype>mailing and physical address</addrtype>
<address>49 Rancocas Rd</address>
<city>Mount Holly</city>
<state>NJ</state>
<postal>08060</postal>
<country>USA</country>
</cntaddr>
<cntorgp>
<cntorg>County of Burlington, NJ</cntorg>
<cntper>Merrilee Torres</cntper>
</cntorgp>
<cntpos>GIS Specialist 1</cntpos>
<cntvoice>709-702-7067</cntvoice>
<cntfax>609-265-3721</cntfax>
<cntemail>mtorres@co.burlington.nj.us</cntemail>
</cntinfo>
</proccont>
<procdesc>In 2003 the BCDIT ArcInfo coverage polygons were loaded into a single feature class in an SDE feature dataset. The ArcInfo coverage lines were loaded into another feature class in the same feature dataset. Topology was built specifying the following rules: no overlaps between polygons, polygon boundaries must be covered by lines, &amp; lines must be covered by boundary of polygons. Since parcels were not edgematched at township borders, overlaps between townships were marked as exceptions. In general, updates were accomplished as follows: MOD4 data was downloaded for a specific township from the County tax assessor system and put in a dbf format. This table was exported to the geodatabase. The geodatabase table was joined to the attribute table of the polygon feature class using the NEWGISID as a common identifier. Parcels without matching records in the MOD4 were investigated for changes/subdivisions. MOD4 records which could not be matched to a parcel in the existing feature class were investigated as possible new lots. The current tax map engineers for the township were contacted and any relevant digital spatial information was obtained such as shapefiles, or CAD files. If no digital data was available, the necessary tax maps were borrowed and scanned unless the engineer was able to provide scans of the tax maps themselves. Scanned tax maps and CAD data with no spatial reference were georeferenced in ArcMap using the most recent available aerials, Burlington County's GPS roads and additional GPS points if needed.
When scanned tax maps were the source, the parcel lines were heads-up digitized from the georeferenced tax map and then built into parcel polygons. When CAD data was the source, the parcel lines were exported to a shapefile and copied/pasted into the parcel line feature class and then built as polygons. Shapefiles were usually georeferenced polygons which were added to the parcel polygon feature class. Topology was validated against four topology rules. New/modified lots were then coded with appropriate values for NEWGISID, ALT_ID, BLOCK and LOT values, based on current MOD4 data and tax maps. The BCDIT maintains a database of all major subdivision submitted to the County since 1999 as well as minor subdivision applications to the County Planning Board. For each township this database was consulted and the pertinent subdivision maps obtained from the County Clerk and scanned. New properties on the subdivision maps were processed using the same methodology as the tax maps (see above).
2003 - Evesham, Medford &amp; Mount Laurel, Westampton. 2005- Delanco, Fieldsboro, &amp; Washington. 2006- Beverly, Delran, Lumberton, Pemberton Borough, Pemberton Township, Riverton, Southampton &amp; Willingboro. 2007- Burlington City, Burlington Township, Chesterfield, Medford Lakes, Moorestown, Palmyra, Riverside, Springfield.
2008- Florence, Medford. </procdesc>
<procsv>ArcGIS 8x &amp; 9x</procsv>
<procdate>2003-2009</procdate>
</procstep>
<procstep>
<procdesc>Identified and corrected errors in Mount Laurel Twp, Block 301.20 &amp; 301.21 which were incorrectly entered as 301.2 (558 parcels)</procdesc>
<procsv>ArcGIS 9.3.1</procsv>
<srcused>withheld</srcused>
<procdate>20101026</procdate>
</procstep>
<srcinfo>
<srccontr>North Hanover Township CAD data and PDFs of tax maps from Remington &amp; Vernick Engineers</srccontr>
</srcinfo>
<procstep>
<procdesc>2011 updates by County of Burlington, GIS were as follows: August 2011, North Hanover Township was updated using CAD data and PDFs of tax maps obtained from Remington &amp; Vernick Engineers. The PDFs were converted to Tif files. Both CAD and Tiffs were georeferenced to 2010 aerial photography from the Delaware Valley Regional Planning Commission and parcels were updated accordingly. Any parcels that could not be matched to a MOD4 record were investigated as were all MOD4 records that did not have a corresponding parcel.</procdesc>
<procsv>ArcGIS 10</procsv>
<procdate>201108</procdate>
<proccont>
<cntinfo>
<cntaddr>
<address>49 Rancocas Rd, Rm 111</address>
<addrtype>mailing and physical address</addrtype>
<address>PO Box 6000</address>
<city>Mount Holly</city>
<state>NJ</state>
<postal>08060</postal>
</cntaddr>
<cntorgp>
<cntorg>County of Burlington</cntorg>
<cntper>Merrilee Torres</cntper>
</cntorgp>
<cntpos>GIS Specialist 1</cntpos>
<cntvoice>609-702-7067</cntvoice>
<cntfax>609-265-3721</cntfax>
<cntemail>mtorres@co.burlington.nj.us</cntemail>
</cntinfo>
</proccont>
<srcused>withheld</srcused>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="Burlco_ROSI">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<coordrep>
<absres Sync="TRUE">0.000034</absres>
<ordres Sync="TRUE">0.000034</ordres>
</coordrep>
<plandu Sync="TRUE">survey feet</plandu>
</planci>
</planar>
<geodetic>
<horizdn Sync="TRUE">North American Datum of 1983</horizdn>
<ellips Sync="TRUE">Geodetic Reference System 80</ellips>
<semiaxis Sync="TRUE">6378137.000000</semiaxis>
<denflat Sync="TRUE">298.257222</denflat>
</geodetic>
<cordsysn>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet</projcsn>
</cordsysn>
</horizsys>
<vertdef>
<altsys>
<altres Sync="TRUE">1.000000</altres>
<altenc Sync="TRUE">Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed Name="Burlco_ROSI">
<enttyp>
<enttypl Sync="FALSE">Burlco_ROSI</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID_1</attrlabl>
<attalias Sync="TRUE">OBJECTID_1</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>OBJECTID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>PAMS_PIN</attrlabl>
<attrdef>State's unique identifier: concatenation of county code, municipal code, block, lot and qualifier</attrdef>
<attalias Sync="TRUE">PAMS_PIN</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">38</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>MUN</attrlabl>
<attrdef>Municipal code</attrdef>
<attalias Sync="TRUE">MUN</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">CALCACREAG</attrlabl>
<attalias Sync="TRUE">CALCACREAG</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>BLOCK</attrlabl>
<attrdef>Tax block number</attrdef>
<attalias Sync="TRUE">BLOCK</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>LOT</attrlabl>
<attrdef>Tax lot number</attrdef>
<attalias Sync="TRUE">LOT</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">MUNITAXDIS</attrlabl>
<attalias Sync="TRUE">MUNITAXDIS</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>NEWGISID</attrlabl>
<attrdef>Join/Relate field for use with MOD4 tables. Concatenation of municipal code, block and lot. This field is not unique- it represents the MOD4 record used by tax assessors for the property. This MOD4 record may reference more than one lot in the case of additional lots</attrdef>
<attalias Sync="TRUE">NEWGISID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ALT_ID</attrlabl>
<attrdef>Unique identifier for each lot: Concatenation of county code, municipal code-block-lot-(&amp; Qualifier for condos only)</attrdef>
<attalias Sync="TRUE">ALT_ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ADD_BLOCK</attrlabl>
<attrdef>Tax Block number for lots that are additional lots to lot referenced in NEWGISID (only populated if the blocks differ)</attrdef>
<attalias Sync="TRUE">ADD_BLOCK</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ADD_LOT</attrlabl>
<attrdef>Tax Lot number for lots that are additional lots to lot referenced in NEWGISID (only populated if it is an add_lot)</attrdef>
<attalias Sync="TRUE">ADD_LOT</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Property</attrlabl>
<attalias Sync="TRUE">Property</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Type_preserved</attrlabl>
<attalias Sync="TRUE">Type_preserved</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Closed</attrlabl>
<attalias Sync="TRUE">Closed</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">36</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Funds</attrlabl>
<attalias Sync="TRUE">Funds</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">40</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Source</attrlabl>
<attalias Sync="TRUE">Source</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Key_Code</attrlabl>
<attalias Sync="TRUE">Key_code</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Comments</attrlabl>
<attalias Sync="TRUE">Comments</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Dev_Stat</attrlabl>
<attalias Sync="TRUE">Dev_Stat</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape.STArea()</attrlabl>
<attalias Sync="TRUE">Shape.STArea()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape.STLength()</attrlabl>
<attalias Sync="TRUE">Shape.STLength()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Burlington County Department of Information Technology</cntorg>
<cntper>Merrilee J. Torres</cntper>
</cntorgp>
<cntpos>GIS Specialist</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>PO Box 6000, 49 Rancocas Road</address>
<city>Mount Holly</city>
<state>NJ</state>
<postal>08060</postal>
<country>USA</country>
</cntaddr>
<cntvoice>609-702-7067</cntvoice>
<cntfax>609-265-3721</cntfax>
<cntemail>mtorres@co.burlington.nj.us</cntemail>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<stdorder>
<digform>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>https://njgin.state.nj.us/NJ_NJGINExplorer/DataDownloads.jsp</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>none</fees>
</stdorder>
<availabl>
<timeinfo>
<sngdate>
<caldate>201007</caldate>
</sngdate>
</timeinfo>
</availabl>
</distinfo>
<metainfo>
<metd Sync="TRUE">20120201</metd>
<metrd>20100720</metrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Burlington County Department of Information Technology</cntorg>
<cntper>Merrilee J. Torres</cntper>
</cntorgp>
<cntpos>GIS Specialist</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>PO Box 6000, 49 Rancocas Roa</address>
<city>Mount Holly</city>
<state>NJ</state>
<postal>08060</postal>
<country>USA</country>
</cntaddr>
<cntvoice>609-702-7067</cntvoice>
<cntfax>609-265-3721</cntfax>
<cntemail>mtorres@co.burlington.nj.us</cntemail>
</cntinfo>
</metc>
<metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
<mettc Sync="TRUE">local time</mettc>
<metac>none</metac>
<metuc>none</metuc>
<metsi>
<metscs>NJGIN</metscs>
<metsc>Public</metsc>
<metshd>no special handling required</metshd>
</metsi>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
<langmeta Sync="TRUE">en</langmeta>
</metainfo>
<Esri>
<CreaDate>20151218</CreaDate>
<CreaTime>10190400</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20160504</SyncDate>
<SyncTime>20392300</SyncTime>
<ModDate>20160504</ModDate>
<ModTime>20392300</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">Burlco_ROSI</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">336377.406250</westBL>
<eastBL Sync="TRUE">523229.912811</eastBL>
<southBL Sync="TRUE">258654.739709</southBL>
<northBL Sync="TRUE">491682.999863</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<itemSize Sync="TRUE">0.000</itemSize>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet</projcsn>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.3'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,492125.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-74.5],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9999],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,38.83333333333334],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,3424]]&lt;/WKT&gt;&lt;XOrigin&gt;-17954599.999964181&lt;/XOrigin&gt;&lt;YOrigin&gt;-46918099.999935396&lt;/YOrigin&gt;&lt;XYScale&gt;29765.70015766584&lt;/XYScale&gt;&lt;ZOrigin&gt;0&lt;/ZOrigin&gt;&lt;ZScale&gt;1&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;0.00026876572557086936&lt;/XYTolerance&gt;&lt;ZTolerance&gt;2&lt;/ZTolerance&gt;&lt;MTolerance&gt;2&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102711&lt;/WKID&gt;&lt;LatestWKID&gt;3424&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
</coordRef>
</DataProperties>
<ArcGISFormat>1.0</ArcGISFormat>
</Esri>
<dataIdInfo>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.3.1.4959</envirDesc>
<dataLang>
<languageCode Sync="TRUE" country="US" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">Burlco_ROSI</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-75.057454</westBL>
<eastBL Sync="TRUE">-74.388666</eastBL>
<northBL Sync="TRUE">40.183299</northBL>
<southBL Sync="TRUE">39.542223</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-75.057454</westBL>
<eastBL Sync="TRUE">-74.388666</eastBL>
<northBL Sync="TRUE">40.183299</northBL>
<southBL Sync="TRUE">39.542223</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-75.057454</westBL>
<eastBL Sync="TRUE">-74.388666</eastBL>
<northBL Sync="TRUE">40.183299</northBL>
<southBL Sync="TRUE">39.542223</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-75.057454</westBL>
<eastBL Sync="TRUE">-74.388666</eastBL>
<northBL Sync="TRUE">40.183299</northBL>
<southBL Sync="TRUE">39.542223</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-75.057454</westBL>
<eastBL Sync="TRUE">-74.388666</eastBL>
<northBL Sync="TRUE">40.183299</northBL>
<southBL Sync="TRUE">39.542223</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
<descKeys>
<thesaName uuidref="723f6998-058e-11dc-8314-0800200c9a66"/>
<keyword Sync="TRUE">002</keyword>
</descKeys>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName>
<mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<distInfo>
<distributor>
<distorTran>
<onLineSrc>
<orDesc Sync="TRUE">002</orDesc>
<linkage Sync="FALSE">withheld</linkage>
</onLineSrc>
</distorTran>
<distorFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distFormat>
<distTranOps>
<transSize Sync="TRUE">0.000</transSize>
</distTranOps>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="3424" value="3424">NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.6.2</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="Burlco_ROSI">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdDateSt Sync="TRUE">20160504</mdDateSt>
</metadata>
