<?xml version="1.0" encoding="UTF-8" standalone="no"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Department of Information Technology and Telecommunications</origin>
<pubdate>11/2013</pubdate>
<title Sync="TRUE">BLDG.BUILDING</title>
<geoform Sync="TRUE">vector digital data</geoform>
<serinfo>
<sername>Building Footprint</sername>
</serinfo>
<pubinfo>
<pubplace>City of New York</pubplace>
<publish>Department of Information Technology and Telecommunications</publish>
</pubinfo>
<onlink Sync="FALSE">withheld</onlink>
<ftname Sync="TRUE">BLDG.BUILDING</ftname>
</citeinfo>
</citation>
<descript>
<abstract>Building footprints represent the perimeter extent of buildings.</abstract>
<purpose>Use of the data is for analytic and cartographic purposes.</purpose>
<supplinf>
The buildings data was collected using the following capture rules:

Collect all buildings &gt;500 sq. feet and taller than 12 feet.  Buildings with &lt;12 feet height but with BIN should be captured.

Buildings with BIN but &lt;500 sq. feet will be captured.

Buildings with flat roofs will be captured on roof outline, capturing the largest outline (excluding overhangs, awnings, construction features, etc.).

Buildings with pitched roofs will be captured on the building footprint.

 

Carports, when attached to main building, will be included in the outline.

Do not collect interior divisions (use existing building layer and BIN as guide).

Do not collect temporary trailers, tents, or roofs at gas stations (over pumps). 

Use parcel data and BIN as guidance for collection.  Where the parcel data indicates that a building should be two or more geometries AND there is NO physical indication, split the building using the parcel lines.   Where the parcel data indicates that a building should be two or more geometries AND there is a physical indication, split the building using the physical indications.  In cases where geometry previously existed in the legacy data, populate all resulting geometries with the original BIN (BINs will be duplicated in these cases).

 

Do NOT collect roofs (overhang) to gas stations, unless connected to building.

 

Do NOT collect movable jet bridge for access to aircraft.

 

Do NOT collect awnings, scaffolds, or sidewalk sheds.

 

Collect all garages, regardless of size, that can be identified as such, and driveways (paved or unpaved) that store one or more cars.  

Special care should be applied to ensure sheds are not to be confused with garages.  Oftentimes, driveways do lead to sheds, so not all structures at a terminating driveway are considered to be garages.  Sheds are not to be captured.

 

Use Parcel layer to place garages within parcel or at parcel boundary  check for special cases where parcel boundary clearly crosses garage.  In these cases, either split the garage using physical features, or use the property line where there is no distinguishing physical feature.

Do NOT collect small tool or storage sheds in backyards which have no visible car access.  In cases where there is no BIN for the garage, a dummy BIN (1000000, 2000000, etc. for each of the Boroughs, see LION manuals pdf) will be populated.
</supplinf>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>11/2013</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>In work</progress>
<update>Quarterly</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-74.257061</westbc>
<eastbc Sync="TRUE">-73.699273</eastbc>
<northbc Sync="TRUE">40.915087</northbc>
<southbc Sync="TRUE">40.498294</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">913201.635195</leftbc>
<rightbc Sync="TRUE">1067367.179226</rightbc>
<bottombc Sync="TRUE">120960.257473</bottombc>
<topbc Sync="TRUE">272669.070853</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekey>Buildings, Building footprint, BIN, Structure</themekey>
</theme>
</keywords>
<accconst>Limited to City, State and Federal entities and consultants working on specific projects for City, State and Federal entities. Requires a signed license agreement with DoITT.</accconst>
<useconst>Not to be distributed beyond the licensee or for projects not specified in the license (Non government entities only).</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>NYC Department of Information Technology and Telecommunications, Citywide GIS</cntorg>
<cntper>Colin Reilly</cntper>
</cntorgp>
<cntpos>Director</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2 Metrotech Center, 4th Floor</address>
<city>Booklyn</city>
<state>NY</state>
<postal>11201</postal>
<country>USA</country>
</cntaddr>
<cntvoice>718-403-8394</cntvoice>
<cntfax>718-403-8591</cntfax>
<cntemail>creilly@doitt.nyc.gov</cntemail>
</cntinfo>
</ptcontac>
<secinfo>
<secclass>Restricted</secclass>
</secinfo>
<native Sync="FALSE">ESRI ArcCatalog 9.3.1.4000</native>
<crossref>
<citeinfo>
<origin>NYC Depatment of Information Technology and Telecommunications, GIS Division</origin>
<pubdate>11/2013</pubdate>
<title>Building Footprint</title>
<serinfo>
<sername>Building Footprint</sername>
</serinfo>
<pubinfo>
<pubplace>City of New York</pubplace>
<publish>NYC Depatment of Information Technology and Telecommunications, GIS Division</publish>
</pubinfo>
</citeinfo>
</crossref>
<natvform Sync="FALSE">Feature Class</natvform>
</idinfo>
<dataqual>
<logic>
The buildings data was collected using the following capture rules:

Collect all buildings &gt;500 sq. feet and taller than 12 feet.  Buildings with &lt;12 feet height but with BIN should be captured.

Buildings with BIN but &lt;500 sq. feet will be captured.

Buildings with flat roofs will be captured on roof outline, capturing the largest outline (excluding overhangs, awnings, construction features, etc.).

Buildings with pitched roofs will be captured on the building footprint.

 

Carports, when attached to main building, will be included in the outline.

Do not collect interior divisions (use existing building layer and BIN as guide).

Do not collect temporary trailers, tents, or roofs at gas stations (over pumps). 

Use parcel data and BIN as guidance for collection.  Where the parcel data indicates that a building should be two or more geometries AND there is NO physical indication, split the building using the parcel lines.   Where the parcel data indicates that a building should be two or more geometries AND there is a physical indication, split the building using the physical indications.  In cases where geometry previously existed in the legacy data, populate all resulting geometries with the original BIN (BINs will be duplicated in these cases).

 

Do NOT collect roofs (overhang) to gas stations, unless connected to building.

 

Do NOT collect movable jet bridge for access to aircraft.

 

Do NOT collect awnings, scaffolds, or sidewalk sheds.

 

Collect all garages, regardless of size, that can be identified as such, and driveways (paved or unpaved) that store one or more cars.  

Special care should be applied to ensure sheds are not to be confused with garages.  Oftentimes, driveways do lead to sheds, so not all structures at a terminating driveway are considered to be garages.  Sheds are not to be captured.

 

Use Parcel layer to place garages within parcel or at parcel boundary  check for special cases where parcel boundary clearly crosses garage.  In these cases, either split the garage using physical features, or use the property line where there is no distinguishing physical feature.

Do NOT collect small tool or storage sheds in backyards which have no visible car access.  In cases where there is no BIN for the garage, a dummy BIN (1000000, 2000000, etc. for each of the Boroughs, see LION manuals pdf) will be populated.
</logic>
<posacc>
<horizpa>
<horizpar>
All the NYCMap data was aerotriangulated and stereo-compiled to meet ASPRS Class 1 horizontal mapping standards and ASPRS vertical Class 2 accuracy specifications.  The mapping standards deal with Root Mean Square (RMS) calculations that states if a random number of clearly identifiable surveyed ground control points throughout the project were compared to the mapped features, the RMS of the points would not exceed 2'. In layman's terms,  95% of the data is accurate to +/- 2'.
Estimated accuracy: 95% of the data is accurate to +/- 2 feet
How this value was determined: 
95% of the data is accurate to +/- 2 feet
</horizpar>
</horizpa>
</posacc>
<lineage>
<procstep>
<procdesc Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<procdate Sync="TRUE">20130409</procdate>
<proctime Sync="TRUE">15282000</proctime>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="FortTotten">
<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.000328</absres>
<ordres Sync="TRUE">0.000328</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_York_Long_Island_FIPS_3104_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="FortTotten">
<enttyp>
<enttypl Sync="TRUE">FortTotten</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</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>BIN</attrlabl>
<attrdef>Building identification number. Asssigned by City Planning</attrdef>
<attalias Sync="TRUE">BIN</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>DOITT_ID</attrlabl>
<attalias Sync="TRUE">DOITT_ID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>DOITT ID</attrdef>
</attr>
<attr>
<attrlabl>NAME</attrlabl>
<attrdef>Building name (limited to commonly known names)</attrdef>
<attalias Sync="TRUE">NAME</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">CNSTRCT_YR</attrlabl>
<attalias Sync="FALSE">CONSTRUCTION_YEAR</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The year construction of the building was completed. If the year of construction is an estimate, it is indicated in the "BuiltCode" field with an E code.

Source: Department of Finance - Real Property Assessment Database (RPAD).</attrdef>
</attr>
<attr>
<attrlabl Sync="TRUE">LSTMODDATE</attrlabl>
<attalias Sync="FALSE">LAST_MODIFY_DATE</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The date the record was last modified.</attrdef>
</attr>
<attr>
<attrlabl Sync="TRUE">LSTSTATYPE</attrlabl>
<attalias Sync="FALSE">LAST_STATUS_TYPE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">254</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>LAST STATUS TYPE</attrdef>
</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">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">HEIGHTROOF</attrlabl>
<attalias Sync="FALSE">HEIGHT_ROOF</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Building Height is calculated as the difference from the building elevation from the Elevation point feature class and the elevation in the interpolated TIN model. This value then is the height of the roof above the ground elevation, NOT its height above sea level.</attrdef>
</attr>
<attr>
<attrlabl Sync="TRUE">FEAT_CODE</attrlabl>
<attalias Sync="FALSE">FEATURE_CODE</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Type of Building. 

List of values: 
2100 = Building 
5100 = Building Under Construction 
5110 = Garage</attrdef>
</attr>
<attr>
<attrlabl Sync="TRUE">GROUNDELEV</attrlabl>
<attalias Sync="FALSE">GROUND_ELEVATION</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Lowest Elevation at the building ground level. Calculated from LiDAR or photogrammetrically using the methodology outlined below.

Methodology:
Building Centroids: Generate centroids (imaginary center point) for the building polygons on completion of the building data update according to 2010 photography. These points will be used for the extraction of elevation value from 2010 LiDAR Bare-earth and 2007/08 Contour surfaces and populate as "GROUND ELEVATION" attribute for the "BUILDING_FOOTPRINT" feature class.
LiDAR - Bare-earth Surface: Import the City supplied bare-earth LiDAR data (.las) to the LiDAR processing software and overlay the updated building polygons data. Remove any points which fall inside the building polygon to eliminate anomalous points inside the building polygon.  Generate a Digital Terrain Model (DTM) from the cleaned LiDAR bare-earth points using interpolation algorithms to develop a continuous surface/TIN based on the elevation attribute. Then convert the TIN surface to GRID at 10ft pixel resolution.

2007/08 Contour Surface: Generate Digital Terrain Model (DTM)/TIN from 2007/08 contour data according to the elevation value using interpolation algorithms. Convert the TIN surface to GRID at 10ft pixel resolution.

Elevation Attribute Calculation: Centroids developed for the buildings will be overlaid on the LiDAR Bare-earth surface and the Contour-derived surface. Elevation value at the point of intersection will be extracted and populated as "LiDAR Ground Elevation" and "Contour Ground Elevation" attributes respectively. Delta between these two values will be calculated and analyzed.

	1) If delta is &lt;2 ft, the "LiDAR Ground Elevation" value derived from LiDAR Bare-earth surface will be populated to respective "Building Footprint" features class as "GROUND ELEVATION" attribute.

	2) If delta is &gt;2ft, respective buildings will be reviewed manually through photogrammetric approach and the ground elevation value will be collected.
		a. If a building is on a flat terrain, then the elevation at the outer edge of the building will be populated as "GROUND ELEVATION" attribute.
		b. If a building is on a sloping terrain, low and high terrain adjacent to the building will be reviewed photogrammetrically by a photogrammetrist. An appropriate ground elevation value along the building footprint edge near to the centroid at the visible ground will be collected and populated as "GROUND ELEVATION" attribute.
			i. In order to support the visual inspection of the terrain, the photogrammetrist will display the 2008 contour data and review the elevation.
			ii. Measure the correct ground elevations from the visible outer edges of the building and assign the correct value which is suitable for contour data.
			iii. If the ground elevations are not matching the contour data, assign the nearest ground elevation from the centroid of the building irrespective of high/low/average values.

	3) Buildings which are updated or newly collected, the ground elevation value will be derived from photogrammetric approach as described in point 2a and 2b, the value will be populated as the "GROUND ELEVATION" attribute provided the elevation difference is more than 2ft between LiDAR and contour surfaces. Otherwise, the elevation from LiDAR surface will be populated.</attrdef>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE_AREA</attrlabl>
<attalias Sync="TRUE">Shape_Area</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Area of feature in internal units squared.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Department of Information Technology and Telecommunications</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2 Metrotech Center, 4th Floor</address>
<city>Brooklyn</city>
<state>NY</state>
<postal>11201</postal>
<country>USA</country>
</cntaddr>
<cntemail>spatialdatarequest@doitt.nyc.gov</cntemail>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<stdorder>
<digform>
<digtinfo>
<transize>189</transize>
</digtinfo>
</digform>
</stdorder>
</distinfo>
<metainfo>
<metd Sync="TRUE">20131113</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>NYC Depatment of Information Technology and Telecommunication, GIS Division</cntorg>
<cntper>Colin Reilly</cntper>
</cntorgp>
<cntpos>Director</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2 Metrotech Center, 4th Floor</address>
<city>Brooklyn</city>
<state>NY</state>
<postal>11201</postal>
<country>USA</country>
</cntaddr>
<cntvoice>718-403-8394</cntvoice>
<cntfax>718-403-8591</cntfax>
<cntemail>creilly@doitt.nyc.gov</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>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
<langmeta Sync="TRUE">en</langmeta>
</metainfo>
<Esri>
<CreaDate>20170127</CreaDate>
<CreaTime>11201300</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20180930</SyncDate>
<SyncTime>00531600</SyncTime>
<ModDate>20180930</ModDate>
<ModTime>00531600</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">FortTotten</itemName>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">913201.635195</westBL>
<eastBL Sync="TRUE">1067367.179226</eastBL>
<southBL Sync="TRUE">120960.257473</southBL>
<northBL Sync="TRUE">272669.070853</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<itemSize Sync="TRUE">206.761</itemSize>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_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/2.2.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_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;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,984250.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-74.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,40.66666666666666],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,41.03333333333333],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,40.16666666666666],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2263]]&lt;/WKT&gt;&lt;XOrigin&gt;-120039300&lt;/XOrigin&gt;&lt;YOrigin&gt;-96540300&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121918&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102718&lt;/WKID&gt;&lt;LatestWKID&gt;2263&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>FGDC</ArcGISProfile>
</Esri>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 12.2.1.12813</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">FortTotten</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
<citRespParty>
<rpOrgName>City of New York, Department of Information Technology and Telecommunications</rpOrgName>
<rpIndName>GIS Division</rpIndName>
<role>
<RoleCd value="005"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>2 Metrotech Center, 4th Floor</delPoint>
<city>Brooklyn</city>
<adminArea>NY</adminArea>
<postCode>11201</postCode>
<eMailAdd>spatialdatarequest@doitt.nyc.gov</eMailAdd>
<country>US</country>
</cntAddress>
</rpCntInfo>
</citRespParty>
<date>
<pubDate>2018-09-21T18:30:20</pubDate>
</date>
<datasetSeries>
<seriesName>Building Footprint</seriesName>
</datasetSeries>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="FALSE">-74.257061</westBL>
<eastBL Sync="FALSE">-73.699273</eastBL>
<northBL Sync="FALSE">40.915087</northBL>
<southBL Sync="FALSE">40.498294</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-74.257061</westBL>
<eastBL Sync="TRUE">-73.699273</eastBL>
<northBL Sync="TRUE">40.915087</northBL>
<southBL Sync="TRUE">40.498294</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
<idPurp>Use of the data is for analytic and cartographic purposes.</idPurp>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Building footprints represent the perimeter extent of buildings.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<searchKeys>
<keyword>Buildings</keyword>
<keyword>Building footprint</keyword>
<keyword>BIN</keyword>
<keyword>Structure</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Open Data policies and restrictions apply. See Terms of Use (http://www.nyc.gov/html/data/terms.html).&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<themeKeys>
<keyword>Buildings, Building footprint, BIN, Structure</keyword>
</themeKeys>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<suppInfo>The buildings data was collected using the following capture rules:


Collect all buildings &gt;400 sq. feet and taller than 12 feet.  Buildings with &lt;12 feet height but with BIN should be captured.
 
Buildings with BIN but &lt;400 sq. feet will be captured.
 
Buildings with flat roofs will be captured on roof outline, capturing the largest outline (excluding overhangs, awnings, construction features, etc.).
 
Buildings with pitched roofs will be captured on the building footprint.
 
Carports, when attached to main building, will be included in the outline.
 
Do not collect interior divisions (use existing building layer and BIN as guide).
 
Do not collect temporary trailers, tents, or roofs at gas stations (over pumps). 
 
Use parcel data and BIN as guidance for collection.  Where the parcel data indicates that a building should be two or more geometries AND there is NO physical indication, split the building using the parcel lines.   Where the parcel data indicates that a building should be two or more geometries AND there is a physical indication, split the building using the physical indications.  In cases where geometry previously existed in the legacy data, populate all resulting geometries with the original BIN (BINs will be duplicated in these cases).
 
Do NOT collect roofs (overhang) to gas stations, unless connected to building.
  
Do NOT collect movable jet bridge for access to aircraft.
  
Do NOT collect awnings, scaffolds, or sidewalk sheds.
 
Collect all garages, regardless of size, that can be identified as such, and driveways (paved or unpaved) that store one or more cars.  
 
Special care should be applied to ensure sheds are not to be confused with garages.  Oftentimes, driveways do lead to sheds, so not all structures at a terminating driveway are considered to be garages.  Sheds are not to be captured.
  
Use Parcel layer to place garages within parcel or at parcel boundary  check for special cases where parcel boundary clearly crosses garage.  In these cases, either split the garage using physical features, or use the property line where there is no distinguishing physical feature.
 
Do NOT collect small tool or storage sheds in backyards which have no visible car access.  In cases where there is no BIN for the garage, a dummy BIN (1000000, 2000000, etc. for each of the Boroughs, see LION manuals pdf) will be populated
</suppInfo>
<idPoC>
<rpIndName>Colin Reilly</rpIndName>
<rpOrgName>NYC Depatment of Information Technology and Telecommunication, GIS Division</rpOrgName>
<rpPosName>Director</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>2 Metrotech Center, 4th Floor</delPoint>
<city>Brooklyn</city>
<adminArea>NY</adminArea>
<postCode>11201</postCode>
<eMailAdd>creilly@doitt.nyc.gov</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">718-403-8394</voiceNum>
<faxNum>718-403-8591</faxNum>
</cntPhone>
</rpCntInfo>
<displayName>Colin Reilly</displayName>
<role>
<RoleCd value="010"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="006"/>
</maintFreq>
<maintCont>
<rpOrgName>City of New York, Department of Information Technology and Telecommunications</rpOrgName>
<rpIndName>GIS Division</rpIndName>
<role>
<RoleCd value="005"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>2 Metrotech Center, 4th Floor</delPoint>
<city>Brooklyn</city>
<adminArea>NY</adminArea>
<postCode>11201</postCode>
<eMailAdd>spatialdatarequest@doitt.nyc.gov</eMailAdd>
<country>US</country>
</cntAddress>
</rpCntInfo>
<displayName>GIS Division</displayName>
</maintCont>
</resMaint>
<idStatus>
<ProgCd value="004"/>
</idStatus>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-74.257061</westBL>
<eastBL Sync="TRUE">-73.699273</eastBL>
<northBL Sync="TRUE">40.915087</northBL>
<southBL Sync="TRUE">40.498294</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="017"/>
</tpCat>
<idCredit/>
</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>
<protocol Sync="TRUE"/>
</onLineSrc>
</distorTran>
</distributor>
<distFormat>
<formatName>File GeoDatabase</formatName>
</distFormat>
<distFormat>
<formatName>Shapefile</formatName>
</distFormat>
<distTranOps>
<transSize Sync="TRUE">206.761</transSize>
</distTranOps>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2263">NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">5.3(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="FortTotten">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdDateSt Sync="FALSE">20170314</mdDateSt>
<mdContact>
<rpIndName>Colin Reilly</rpIndName>
<rpOrgName>NYC Depatment of Information Technology and Telecommunication, GIS Division</rpOrgName>
<rpPosName>Director</rpPosName>
<rpCntInfo>
<cntAddress addressType="physical">
<delPoint>2 Metrotech Center, 4th Floor</delPoint>
<city>Brooklyn</city>
<adminArea>NY</adminArea>
<postCode>11201</postCode>
<eMailAdd>creilly@doitt.nyc.gov</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum tddtty="">718-403-8394</voiceNum>
<faxNum>718-403-8591</faxNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</mdContact>
<mdMaint>
<maintFreq>
<MaintFreqCd value="006"/>
</maintFreq>
</mdMaint>
<dqInfo>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>Estimated positional accuracy: 95% of the data is accurate to +/- 2 feet

All the NYCMap data was aerotriangulated and stereo-compiled to meet ASPRS Class 1 horizontal mapping standards and ASPRS vertical Class 2 accuracy specifications.  The mapping standards deal with Root Mean Square (RMS) calculations that states if a random number of clearly identifiable surveyed ground control points throughout the project were compared to the mapped features, the RMS of the points would not exceed 2'. In layman's terms,  95% of the data is accurate to +/- 2'.
</measDesc>
</report>
</dqInfo>
</metadata>