Data Dictionary

Job_Number

• Longform Name: DOB Job Number
• Old Name: job_number
• Description: The DOB job application number assigned when the applicant begins the application. This is the unique identifier for the application submitted to the Department of Buildings (DOB). It may contain several work types, and more work types may be added as the application review and the work continues. It is a 9-digit number where the first digit indicates the borough where the building is located.
• How it is created: These values are mapped from the dob_jobapplications field jobnumber

Job_Type

• Longform Name: DOB Job Type
• Old Name: job_type
• Description: DOB's type category for the job application. More information is available here. The following types are included in this database:
  • New Building (NB): an application to build a new structure. “NB” cannot be selected if any existing building elements are to remain—for example a part of an old foundation, a portion of a façade that will be incorporated into the construction, etc.
  • Alteration Type I (A1): a major alteration that will change the use, egress, or occupancy of the building.
  • Demolition (DM): an application to fully or partially demolish an existing building. Note that many demolition permits are only for partial demolitions and for garages (these are also captured).
• How it is created:
  • Mapped from dob_jobapplications field jobtype as follows:
    • A1 to Alteration
    • DM to Demolition
    • NB to New Building
  • Administrative records are removed based on this field in combination with job_description.

Residflag

• Longform Name: Residential Flag
• Old Name: occ_category
• Description: This field is used to identify jobs in buildings containing residential uses. A value of "residential" indicates that the job affects residential units in some way through new construction, alteration, or demolition. Only those jobs with a value of "residential" are included in the housing database. Manual research was conducted at DCP to help ensure that all work on buildings with residences receive this flag, though some records may remain misclassified.
• How it is created:
  • This field is dependent on hotel_init, hotel_prop, otherb_init, otherb_prop, classa_init, and classa_prop.
  • If any of the dependent fields are not NULL, then the job is flagged as being residential.
  • Manual research adds/removes this flag as necessary

Nonresflag

• Longform Name: Non-residential Flag
• Old Name: *NEW*
• Description: This field is used to identify jobs in buildings containing non-residential uses. A value of "non-residential" indicates that the job affects some use type beyond residential, including commercial, industrial, or community facility uses. Mixed-use buildings will have values in both the Resid_Flag and Nonresid_Flag, since they contain both residential and nonresidential uses, but having flags in both of those columns does not necessarily mean that it is a mixed-use development since the flags do not distinguish between the initial and proposed uses in the building.
• How it is created:
  • This field is dependent on job_description, occ_initial, occ_proposed, and resid_flag
  • nonresid_flag is true if:
    1. job_description has one of these keywords OR
    2. occ_initial or occ_proposed are one of these categories. OR
    3. resid_flag IS NULL

Job_Inactv

• Longform Name: Job Inactive
• Old Name: x_inactive
• Description: This field is used to identify job applications that are likely inactive, either because the job is withdrawn, is a duplicate of another job, or the application has stalled for three or more years. Records flagged as inactive should be excluded in most analyses of incomplete jobs since they are extremely unlikely to ever reach completion. Note that this definition is probability based and therefore can not capture all permits that may eventually become inactive.
• How it is created:
  • This field is dependent on date_complete, job_status, date_lastupdt
  • A job can only be inactive if date_complete is NULL
  • Possible values:
    • Inactive: Withdrawn: The job status is 9. Withdrawn
    • Inactive: Stalled: A job has a status of Filed Application, Approved Application, OR Permitted for Construction AND date_lastupdt is 3 or more years before the vintage date.
    • Inactive: Duplicate: A job with a status that is Filed Application, Approved Application, OR Permitted for Construction MATCHES with a job that has a status of either 4. Partially Completed Construction OR 5. Completed Construction ON the following fields:
      • classa_init (where units are NOT NULL) AND
      • classa_prop (where units are NOT NULL) AND
      • address AND
      • job_type AND
      • the date_lastupdt of the incomplete job is before the date_lastupdt of the complete job.
    • NULL: Not inactive
    • Note, job_inactive can also get set to Inactive: Duplicate through manual research

Job_Status

• Longform Name: DOB Job Status
• Old Name: status
• Description: DCP recode of DOB's status label. This describes the status of the job at the date of the data vintage. For example, a job marked as "3. Permitted" was at that status as of June 30, 2020 if using version 20Q2 of the DCP Developments Database. More details on each DOB status is available here. Jobs typically move through status A through X over time as they reach certain approval milestones:
  • 1. Filed: job application is at status A - G at the time of publication. Application submitted, but review is not yet in progress.
  • 2. Plan Examination: application is at status H - P. Plan examination is in progress but not yet approved.
  • 3. Permitted: application is at status Q and R and may begin construction.
  • 4. Partial Complete: application at status U and X, and CO issued for NB or A1 job type, and the CO is a Temporary CO AND less than 80% of the units are completed for a building with 20 or more units.
  • 5. Complete: For new buildings and alterations, application is at status U and X, or a CO has been issued. For demolitions, the application is at status X. DCP has decided to mark demolitions as complete when they reach status X, but list the completion date as equal to status Q because this is likely when the building must be vacated, and it appears that many buildings are physically demolished some time before receiving sign off (status X).
  • 9. Withdrawn: application is at status 3. The application has been withdrawn by the applicant.
• How it is created:
  • This field is dependent on on job_type, co_latest_certtype, classa_complt_pct, classa_complt_diff, classa_net, x_withdrawal, and the date fields

Compltyear

• Longform Name: Completed Year
• Old Name: *NEW*
• Description: Year the job was completed. For new buildings and alterations, this is defined as the year of the first certificate of occupancy issuance. For demolitions, this is the year that the demolition was permitted (reached status Q).
• How it is created:
  • Dependent on date_complete, this field is the year of date_complete

Compltqrtr

• Longform Name: Completed Quarter
• Old Name: *NEW*
• Description: The year and quarter a job was completed. Follows the same logic as Complete_Year
• How it is created:
  • Dependent on date_complete, this field is the year-quarter of date_complete

Permityear

• Longform Name: Permitted Year
• Old Name: *NEW*
• Description: Year the job was permitted. For all job types, this is defined as the status Q year.
• How it is created:
  • Dependent on date_permittd, this field is the year of date_permittd

Permitqrtr

• Longform Name: Permitted Quarter
• Old Name: *NEW*
• Description: The year and quarter the job was permitted. For all job types, this is defined as the status Q quarter.
• How it is created:
  • Dependent on date_permittd, this field is the year-quarter of date_permittd

Classainit

• Longform Name: Units Class A Initial
• Old Name: units_init
• Description: Number of units that initially existed in the building at the time of the job application, as reported by the applicant. This field is edited by DCP to only count Class A units, which are units in houses or apartment buildings intended for long-term residential use (greater than 30 days), and typically do not require the use of shared kitchens and bathrooms. The definition of Class A and other unit types is available here.
• How it is created:
  • Mapped from the dob_jobapplications field existingdwellingunits
  • Set to 0 for New Buildings
  • If resid_flag is NULL after manual corrections get applied, this field gets set to NULL

Classaprop

• Longform Name: Units Class A Proposed
• Old Name: units_prop
• Description: Number of units proposed in the job application after the proposed work has been completed, as reported by the applicant and edited by DCP to count only Class A units.
• How it is created:
  • Mapped from the dob_jobapplications field proposeddwellingunits
  • Set to 0 for Demolitions
  • If resid_flag is NULL after manual corrections get applied, this field gets set to NULL

Classanet

• Longform Name: Units Class A Net Change
• Old Name: units_net
• Description: Net change in Class A unit count between the number of units existing at the time of application and the number of units proposed.
• How it is created:
  • Dependent on classa_init and classa_prop
  • The difference between classa_init and classa_prop
  • If resid_flag is NULL after manual corrections get applied, this field gets set to NULL

ClassaHNY

• Longform Name: Units Affordable in Housing NY
• Old Name: affordable_units
• Description: The total number of affordable units that are in the proposed building, counted towards the Housing New York plan.
• How it is created:
  • Mapped from hpd_hny_units_by_building field all_counted_units
  • This is sum of all_counted_units for HNY records associated with the job

HotelInit

• Longform Name: Units Hotel Initial
• Old Name: *NEW*
• Description: Number of hotel units that initially existed in the building at the time of the job application, as determined through DCP research. Note that hotel units are a subtype of Class B units which are typically occupied as for-profit businesses for short-term (less than 30 days), full-service lodging.
• How it is created:
  • This field is programatically set to 0 if the job_type is 'New Building'. All other values come directly from the manual research table.
  • If resid_flag is NULL after manual corrections get applied, this field gets set to NULL

HotelProp

• Longform Name: Units Hotel Proposed
• Old Name: *NEW*
• Description: Number of hotel units proposed in the job application after the proposed work has been completed, as determined through DCP research.
• How it is created:
  • This field is programatically set to 0 if the job_type is 'Demolition'. All other values come directly from the manual research table.
  • If resid_flag is NULL after manual corrections get applied, this field gets set to NULL

OtherBInit

• Longform Name: Units Other B Initial
• Old Name: *NEW*
• Description: Number of Class B units (excluding hotel units) that initially existed in the building at the time of the job application, as determined through DCP research. Other Class B units include all dwellings that are not Class A units or hotels, and may include single room occupancy units, dormitories, certain kinds of supportive housing and assisted living, homeless shelters, convents and monasteries, among many other forms of temporary lodging or lodging with communal kitchens or bathrooms. The definition of Class B and other unit types is available here.
• How it is created:
  • This field is programatically set to 0 if the job_type is 'New Building'. All other values come directly from the manual research table.
  • If resid_flag is NULL after manual corrections get applied, this field gets set to NULL

OtherBProp

• Longform Name: Units Other B Proposed
• Old Name: *NEW*
• Description: Number of Class B units (excluding hotel units) proposed in the job application after the proposed work has been completed, as determined through DCP research.
• How it is created:
  • This field is programatically set to 0 if the job_type is 'Demolition'. All other values come directly from the manual research table.
  • If resid_flag is NULL after manual corrections get applied, this field gets set to NULL

Units_CO

• Longform Name: Units on CO
• Old Name: units_complete
• Description: Number of dwelling units provided on the temporary or final certificates of occupancy. This unit count may include Class A units in addition to Class B units and hotel units.
• How it is created:
  • Mapped from dob_cofos field numofdwellingunits

Boro

• Longform Name: Borough
• Old Name: boro
• Description: The NYC borough where the proposed work will take place.

BIN

• Longform Name: BIN
• Old Name: bin
• Description: Building Identification Number (BIN) supplied by Geosupport.

BBL

• Longform Name: BBL
• Old Name: bbl
• Description: Borough-Block-Lot tax ID number of the parcel where the proposed work will take place.

AddressNum

• Longform Name: Street Number
• Old Name: address_house
• Description: The house number for the building where the proposed work will take place.
• How it is created:
  • This is the house number returned by Geosupport during geocoding. If, however, Geosupport did not return address information, then this is the housenumber from dob_jobapplications.

AddressSt

• Longform Name: Street Name
• Old Name: address_street
• Description: The street name for the building where the proposed work will take place.
• How it is created:
  • This is the street name returned by Geosupport during geocoding. If, however, Geosupport did not return address information, then this is the streetname from dob_jobapplications.

Address

• Longform Name: Address
• Old Name: address
• Description: Concatenated street number and street name for the building where the proposed work will take place.
• How it is created:
  • This is a concatenation of the house number and street name returned by Geosupport during geocoding. If, however, Geosupport did not return address information, then this is the concatenation of housenumber and streetname from dob_jobapplications.

Occ_Init

• Longform Name: Occupancy Initial
• Old Name: occ_init
• Description: Description of the existing occupancy type at the time of the job application. This indicates what a site was used for before the proposed job. It is a more descriptive recode of the occupancy code that the applicant submitted to DOB as the initial occupancy type of the building. Note that the applicant may only choose one occupancy code, even in a building containing multiple uses, so this code is only able to describe one of many possible uses.
• How it is created:
  • This field is mapped from the dob_jobapplications field existingoccupancy and translated using the lookup table
  • If job_type is 'New Building', this field gets set to 'Empty Site'

Occ_Prop

• Longform Name: Occupancy Proposed
• Old Name: occ_prop
• Description: Description of the proposed occupancy type at the time of the job application. This indicates what a site will be used for after the proposed job is complete. It is a more descriptive recode of the occupancy code that the applicant submitted to DOB as the proposed occupancy type of the building. Note that the applicant may only choose one occupancy code, even in a building containing multiple uses, so this code is only able to describe one of many possible uses.
• How it is created:
  • This field is mapped from the dob_jobapplications field proposedoccupancy and translated using the lookup table
  • If job_type is 'Demolition', this field gets set to 'Empty Site'

Bldg_Class

• Longform Name: Building Class
• Old Name: *NEW*
• Description:
• How it is created:
  • This field is mapped from the dob_jobapplications field buildingclass

Job_Desc

• Longform Name: DOB Job Description
• Old Name: job_description
• Description: The general description of the work being applied for. This field is free text, and is filled out by the applicant.
• How it is created and used:
  • This field is mapped from the dob_jobapplications field jobdescription.
  • Administrative records, or jobs with no actual construction work, are removed based on this field in combination with job_type.
  • Test records are removed based on this field.

Desc_Other

• Longform Name: Other Description
• Old Name: *NEW*
• Description:
• How it is created:
  • This field is mapped from the dob_jobapplications field otherdesc

Date_Filed

• Longform Name: Date Filed (Status A)
• Old Name: status_a
• Description: Date of job status A (pre-filing application). This is the first step in the process for all job applications. The job application # is assigned at this status. This occurs when the applicant submits any part of the application (even a single form), in person or electronically.
• How it is created:
  • This field is mapped from the dob_jobapplications field prefilingdate

Date_StatusD

• Longform Name: Status D
• Old Name: status_d
• Description: Date of job status D (completed application on file). This is when all data entry is complete and payments have been made.
• How it is created:
  • This field is mapped from the dob_jobapplications field fullypaid

Date_StatusP

• Longform Name: Status P
• Old Name: status_p
• Description: Date of job status P (plan examination approval). This is when the entire job has been approved by the plan examiner. The applicant can now apply for a permit.
• How it is created:
  • This field is mapped from the dob_jobapplications field approved

Date_Permittd

• Longform Name: Date Permitted (Status Q)
• Old Name: status_q
• Description: Date of job status Q (first partial permit issuance). This is when construction work may begin. This field should be used for identifying the number of permits approved in a given year.
• How it is created:
  • This field is mapped from the earliest date in the dob_permitissuance field issuancedate

Date_StatusR

• Longform Name: Status R
• Old Name: status_r
• Description: Date of job status R (full permit issuance). This is when all necessary permits have been approved for a job.
• How it is created:
  • This field is mapped from

Date_StatusX

• Longform Name: Status X
• Old Name: status_x
• Description: Date of job status X (job completion). For new buildings and alterations, date of earliest certificate of occupancy issuance (date_complete) is more reliable in determining completion date.
• How it is created:
  • This field is mapped from the dob_jobapplications field signoffdate

Date_LastUpdt

• Longform Name: Date Last Status
• Old Name: status_date
• Description: The date of the last update to the DOB record for the job filing.
• How it is created:
  • This field is mapped from the dob_jobapplications field latestactiondate

Date_Complete

• Longform Name: Date Completed (First CO)
• Old Name: co_earliest_effectivedate
• Description: DCP's best estimate of completion date for all jobs. For new buildings and alterations, date complete is equal to the date of the earliest certificate of occupancy. For demolitions, date complete is equal to status Q (permit issued), since demolitions do not receive certificates of occupancy. Blank indicates no certificate of occupancy has been issued. Typically, a building can be considered complete at this stage. Large buildings with many units may have units receiving certificates of occupancy over a longer period of time.
• How it is created:
  • This field depends on job_type, date_permitted, and date_statusx
  • For New Buildings and Alterations, this field is mapped from the earliest effectivedate from dob_cofos
  • For Demolitions, this field is mapped from date_permitted for as long as date_statusx IS NOT NULL

ZoningDist1

• Longform Name: Zoning District 1
• Old Name: *NEW*
• Description: The primary zoning district of the tax lot per the applicant at time of application. For more information see http://www1.nyc.gov/site/planning/zoning/about-zoning.page.
• How it is created:
  • This field is the dob_jobapplications field zoningdist1

ZoningDist2

• Longform Name: Zoning District 2
• Old Name: *NEW*
• Description: The secondary zoning district of the tax lot per the applicant at time of application.
• How it is created:
  • This field is the dob_jobapplications field zoningdist2

ZoningDist3

• Longform Name: Zoning District 3
• Old Name: *NEW*
• Description: The tertiary zoning district of the tax lot per the applicant at time of application.
• How it is created:
  • This field is the dob_jobapplications field zoningdist3

SpecialDist1

• Longform Name: Special District 1
• Old Name: *NEW*
• Description: The primary special zoning district of the tax lot per the applicant at time of application. Other zoning designations may appear in this field, such as industrial business zones (IBZ), mandatory inclusionary housing (MIH) areas, or other zoning designations. This field is provided by the applicant, and is likely inconsistent.
• How it is created:
  • This field is mapped from the dob_jobapplications field specialdistrict1

SpecialDist2

• Longform Name: Special District 2
• Old Name: *NEW*
• Description: The secondary special zoning district of the tax lot per the applicant at time of application.
• How it is created:
  • This field is mapped from the dob_jobapplications field specialdistrict2

Landmark

• Longform Name: Landmark
• Old Name: *NEW*
• Description: Indicates that the building has been designated as a landmark building by the Landmarks Preservation Commission.
• How it is created:
  • This field is mapped from the dob_jobapplications field landmarked

ZSF_Init

• Longform Name: Existing Zoning Sqft
• Old Name: *NEW*
• Description:
• How it is created:
  • This field is mapped from the dob_jobapplications field existingzoningsqft

ZSF_Prop

• Longform Name: Proposed Zoning Sqft
• Old Name: *NEW*
• Description:
• How it is created:
  • This field is mapped from the dob_jobapplications field proposedzoningsqft

Stories_Init

• Longform Name: Floors Initial
• Old Name: stories_init
• Description: The existing number of stories/floors in the building, as reported by the applicant.
• How it is created:
  • This field depends on job_type
  • This field is mapped from the dob_jobapplications field existingnumstories if the record is an Alteration or Demolition
  • Values of '0' are replaced with NULL

Stories_Prop

• Longform Name: Floors Proposed
• Old Name: stories_prop
• Description: The number of stories/floors in the building after the work is done, as reported by the applicant.
• How it is created:
  • This field depends on job_type
  • This field is mapped from the dob_jobapplications field proposednumstories if the record is an Alteration or New Building
  • Values of '0' are replaced with NULL

Height_Init

• Longform Name: Height Initial
• Old Name: *NEW*
• Description: The height of the existing building in feet, as reported by the applicant.
• How it is created:
  • This field depends on job_type
  • This field is mapped from the dob_jobapplications field existingheight if the record is an Alteration or Demolition
  • Values of '0' are replaced with NULL

Height_Prop

• Longform Name: Height Proposed
• Old Name: *NEW*
• Description: The proposed height of the building in feet after the proposed work has been completed, as reported by the applicant.
• How it is created:
  • This field depends on job_type
  • This field is mapped from the dob_jobapplications field proposednumstories if the record is an Alteration or Demolition
  • Values of '0' are replaced with NULL

ZoningSF_Init

• Longform Name: Zoning SqFt Initial
• Old Name: zoningsft_init
• Description: The total zoning floor area for the existing building, if any, as reported by the applicant.
• How it is created:

ZoningSF_Prop

• Longform Name: Zoning SqFt Proposed
• Old Name: zoningsft_prop
• Description: The total zoning floor area for the building after the proposed work is completed, as reported by the applicant.
• How it is created:

ConstructnSF

• Longform Name: Total Construction SqFt
• Old Name: *NEW*
• Description: The square footage of the floor area of the construction, as reported by the applicant.
• How it is created:
  • This field is mapped from the dob_jobapplications field totalconstructionfloorarea

Enlargement

• Longform Name: Enlargement Type
• Old Name: *NEW*
• Description: This indicates if the work to be done under the application will result in a horizontal and/or vertical enlargement, as reported by the applicant. Values include: Horizontal, Vertical, Horizontal and Vertical, [blank].
• How it is created:
  • This field is mapped from the dob_jobapplications fields horizontalenlrgmt and verticalenlrgmt
    • When horizontalenlrgmt = 'Y' AND verticalenlrgmt <> 'Y' then 'Horizontal'
    • When horizontalenlrgmt <> 'Y' AND verticalenlrgmt = 'Y' then 'Vertical'
    • When horizontalenlrgmt = 'Y' AND verticalenlrgmt = 'Y' then 'Horizontal and Vertical'

EnlargementSF

• Longform Name: Enlargement SqFt
• Old Name: *NEW*
• Description: The additional square footage added by the construction enlargement, if any, as reported by the applicant.
• How it is created:
  • This field is mapped from dob_jobapplications field enlargementsqfootage

CostEstimate

• Longform Name: Cost Estimate
• Old Name: *NEW*
• Description: Dollar amount that indicates the applicant's estimate for how much the job will cost.
• How it is created:
  • This field is mapped from dob_jobapplications field initialcost

LoftBoardCert

• Longform Name: Loft Board Certification
• Old Name: *NEW*
• Description: Indicates that the job application involves a interim multiple dwelling (IMD) building. A loft board certificate is required for alteration of a registered IMD building. Check the Loft Board website for a list of IMD buildings or the BIS property Profile for LOFT designation.
• How it is created:
  • This field is mapped from dob_jobapplications field loftboard

eDesignation

• Longform Name: e-Designation
• Old Name: *NEW*
• Description: Indicates whether or not the lot is designated with an “E” on the Zoning Maps of the City of New York for potential hazardous material contamination, air and/or noise quality impacts. Little “E” or RD Site: Anytime there is an environmental cleanup in the City of New York, the location is identified as “E” on DCP zoning maps. The Department of Environmental Protection must approve proposed work to ensure that the work satisfies environmental requirements.
• How it is created:
  • This field is mapped from dob_jobapplications field littlee
  • WHEN littlee = 'Y' or 'H' then edesignation = 'Yes'

CurbCut

• Longform Name: Curb Cut
• Old Name: *NEW*
• Description: Indicates that the job application includes curb cut work. An angled drop cut to the curb in the roadway, street, public right of way, or similar, which provides access to the zoning or tax lot.
• How it is created:
  • This field is mapped from dob_jobapplications field curbcut

TractHomes

• Longform Name: Tract Homes
• Old Name: *NEW*
• Description: This indicates that a job filing is part of a housing development where all of the buildings will be built exactly the same way. There is a main job folder with all of the paperwork and plans. This was a common practice when there was a development boom, but is not common anymore.
• How it is created:
  • This field is mapped from dob_jobapplications field cluster

Ownership

• Longform Name: Ownership Type
• Old Name: *NEW*
• Description: This indicates whether the property is government owned, the ownership structure, and non-profit status, as reported by the applicant and recoded by DCP.
• How it is created:
  • This field is mapped from dob_jobapplications fields cityowned, ownertype, and nonprofit
  • The three input values are translated into a single value using this lookup table

Owner_FirstNm

• Longform Name: Owner First Name
• Old Name: *NEW*
• Description: The first name of the building owner, as reported by the applicant.
• How it is created:
  • This field is mapped from dob_jobapplications field ownerfirstname

Owner_LastNm

• Longform Name: Owner Last Name
• Old Name: *NEW*
• Description: The last name of the building owner, as reported by the applicant.
• How it is created:
  • This field is mapped from dob_jobapplications field ownerlastname

Owner_BizNm

• Longform Name: Owner Business Name
• Old Name: *NEW*
• Description: The business name of the building owner, as reported by the applicant.
• How it is created:
  • This field is mapped from dob_jobapplications field ownerbusinessname

Owner_Address

• Longform Name: Owner Address
• Old Name: *NEW*
• Description: The house number and street for the building owner's address, as reported by the applicant.
• How it is created:
  • This field is mapped from dob_jobapplications field ownerhousestreetname

Owner_ZipCode

• Longform Name: Owner Zip Code
• Old Name: *NEW*
• Description: The zip code for the building owner's address, as reported by the applicant.
• How it is created:
  • This field is mapped from dob_jobapplications field zip

Owner_Phone

• Longform Name: Owner Phone Number
• Old Name: *NEW*
• Description: The phone number for the building owner, as reported by the applicant.
• How it is created:
  • This field is mapped from dob_jobapplications field ownerphone

PLUTO_UnitRes

• Longform Name: PLUTO Units Residential
• Old Name: *NEW*
• Description: Per MapPLUTO, the sum of residential units in all buildings on the tax lot. If there are no residential units in the tax lot the field is zero.Hotels/motels, nursing homes and SROs do not have residential units, but boarding houses do. Basement units for building superintendents are counted as a residential unit. Update of residential units triggered when a DOB permit is issued. Field Name: TOTALUNITS.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_BldgSF

• Longform Name: PLUTO Building SqFt
• Old Name: *NEW*
• Description: Per MapPLUTO, the total gross area in square feet, except for condominium measurements, which come from the Condo Declaration and are net square footage not gross.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_ComSF

• Longform Name: PLUTO Commercial SqFt
• Old Name: *NEW*
• Description: Per MapPLUTO, an estimate of the exterior dimensions of the portion of the structure(s) allocated for commercial use.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_OffcSF

• Longform Name: PLUTO Office SqFt
• Old Name: *NEW*
• Description: Per MapPLUTO, an estimate of the exterior dimensions of the portion of the structure(s) allocated for office use.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_RetlSF

• Longform Name: PLUTO Retail SqFt
• Old Name: *NEW*
• Description: Per MapPLUTO, an estimate of the exterior dimensions of the portion of the structure(s) allocated for retail use.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_ResSF

• Longform Name: PLUTO Residential SqFt
• Old Name: *NEW*
• Description: Per MapPLUTO, an estimate of the exterior dimensions of the portion of the structure(s) allocated for residential use.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_YrBuilt

• Longform Name: PLUTO Year Built
• Old Name: *NEW*
• Description: Per MapPLUTO, the year construction of the building was completed. Note the DCP HED has found this to be untrue.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_YrAlt1

• Longform Name: PLUTO Most Recent Alteration Year
• Old Name: *NEW*
• Description: Per MapPLUTO, if a building has only been altered once, YEAR ALTERED 1 is the date that alteration began.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_YrAlt2

• Longform Name: PLUTO Second Most Recent Alteration Year
• Old Name: *NEW*
• Description: Per MapPLUTO, if a building has only been altered once, this field is blank.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_Histdst

• Longform Name: PLUTO Historic District
• Old Name: *NEW*
• Description: Per MapPLUTO, the name of the Historic District as designated by the New York City Landmarks Preservation Commission.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_Landmk

• Longform Name: PLUTO Landmark
• Old Name: *NEW*
• Description: Per MapPLUTO, the name of an individual landmark, landmark site( e.g. Richmondtown Restoration) or an interior landmark, as designated by the New York City Landmarks Preservation Commission
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_BldgCls

• Longform Name: PLUTO Building Class
• Old Name: *NEW*
• Description: Per MapPLUTO, a code describing the major use of structures on the tax lot.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_LandUse

• Longform Name: PLUTO Land Use
• Old Name: *NEW*
• Description: Per MapPLUTO, a code for the tax lot's land use category. The Department of City Planning has created 11 land use categories and assigns each BUILDING CLASS to the most appropriate land use category.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_Owner

• Longform Name: PLUTO Owner Name
• Old Name: *NEW*
• Description: Per MapPLUTO, the name of the tax lot owner.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_OwnType

• Longform Name: PLUTO Ownership Type
• Old Name: *NEW*
• Description: Per MapPLUTO, a code indicating type of ownership for the tax lot.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_Condo

• Longform Name: PLUTO Condominium Number
• Old Name: *NEW*
• Description: Per MapPLUTO, the condominium number assigned to the complex. Condominium numbers are unique within a borough.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_Bldgs

• Longform Name: PLUTO Number of Buildings
• Old Name: *NEW*
• Description: Per MapPLUTO, the number of buildings on the tax lot. Extensions are not counted as separate buildings.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_Floors

• Longform Name: PLUTO Number of Floors
• Old Name: *NEW*
• Description: Per MapPLUTO, the number of full and partial stories starting from the ground floor, for the tallest building on the tax lot.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_Version

• Longform Name: Version of PLUTO
• Old Name: *NEW*
• Description: The version number of MapPLUTO joined to the Developments Database.

CenBlock2010

• Longform Name: FIPS Census Block 2010
• Old Name: *NEW*
• Description: Census Block FIPS code.
• How it is created:
  • This is a reformatted version of bctcb2010 that uses county FIPS instead of one-digit borough code.

BCTCB2010

• Longform Name: BCTCB 2010
• Old Name: *NEW*
• Description: The Borough - Census Tract - Census Block code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with Census Block boundaries.

BCT2010

• Longform Name: BCT 2010
• Old Name: *NEW*
• Description: The Borough - Census Tract code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with Census Tract boundaries.

NTA2010

• Longform Name: NTA 2010
• Old Name: *NEW*
• Description: Neighborhood Tabulation Area (NTA) code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with NTA boundaries.

NTAName2010

• Longform Name: NTA Name 2010
• Old Name: *NEW*
• Description: Neighborhood Tabulation Area (NTA) descriptive name.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with NTA boundaries.

PUMA2010

• Longform Name: PUMA 2010
• Old Name: *NEW*
• Description: Public Use Microdata Area (PUMA) code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with PUMA boundaries.

ComunityDist

• Longform Name: Community District
• Old Name: *NEW*
• Description: NYC Community District code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with community district boundaries.

CouncilDist

• Longform Name: Council District
• Old Name: *NEW*
• Description: NYC Council District code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with council district boundaries.

SchoolSubDist

• Longform Name: School Subdistrict
• Old Name: *NEW*
• Description: NYC School Subdistrict code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with school subdistrict boundaries.

SchoolCommnty

• Longform Name: Community School District
• Old Name: *NEW*
• Description: NYC Community School District code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with community school district boundaries.

SchoolElmntry

• Longform Name: Elementary School Zone
• Old Name: *NEW*
• Description: NYC Elementary School Zone code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with elementary school zone boundaries.

SchoolMiddle

• Longform Name: Middle School Zone
• Old Name: *NEW*
• Description: NYC Middle School Zone code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with middle school zone boundaries.

FireCompany

• Longform Name: Fire Company
• Old Name: *NEW*
• Description: NYC Fire Company code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with fire company boundaries.

FireBattalion

• Longform Name: Fire Battalion
• Old Name: *NEW*
• Description: NYC Fire Battalion code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with fire battalion boundaries.

FireDivision

• Longform Name: Fire Division
• Old Name: *NEW*
• Description: NYC Fire Division code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with fire division boundaries.

PolicePrecnct

• Longform Name: Police Precinct
• Old Name: *NEW*
• Description: NYC Police Precinct code.
• How it is created:
  • This field comes from Geosupport, as long as the address returns a value and the record is not in TPAD. Otherwise, the value is generated from a spatial join with police precinct boundaries.

DEPDrainArea

• Longform Name: DEP Drainage Planning Area
• Old Name: *NEW*
• Description: NYC Dept. of Environmental Protection (DEP) Drainage Planning Area code.
• How it is created:

DEPPumpStatn

• Longform Name: DEP Pump Station
• Old Name: *NEW*
• Description: NYC Dept. of Environmental Protection (DEP) Pump Station code.
• How it is created:

PLUTO_FIRM07

• Longform Name: PLUTO FIRM 2007
• Old Name: *NEW*
• Description: A value of 1 means that some portion of the tax lot falls within the 1% annual chance floodplain as determined by FEMA’s 2007 Flood Insurance Rate Map. Note that buildings on the tax lot may or may not be in the portion of the tax lot that is within the 1% annual chance floodplain.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

PLUTO_PFIRM15

• Longform Name: PLUTO PFIRM 2015
• Old Name: *NEW*
• Description: A value of 1 means that some portion of the tax lot falls within the 1% annual chance floodplain as determined by FEMA’s 2015 Preliminary Flood Insurance Rate Map. Note that buildings on the tax lot may or may not be in the portion of the tax lot that is within the 1% annual chance floodplain.
• How it is created:
  • This field is mapped from dcp_mappluto which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

Latitude

• Longform Name: Latitude
• Old Name: latitude
• Description: Latitude in WGS84 / SRID:4326
• How it is created:
  • The latitude and longitude value are assigned in the following order. The associated geomsource values are in parentheses:
    1. DoITT building footprints center point using dob_bin as a join_key (BIN DOB buildingfootprints or BIN DOB buildingfootprints (historical))
    2. DoITT building footprints center point using geo_bin as a join_key
    3. Returned from GeoSupport 1B function (Lat/Lon DCP, Lat/Lon geosupport)
    4. BBL centroid from shoreline clipped MapPLUTO using dob_bbl as a join_key (BBL DOB MapPLUTO)
    5. latitude and longitude from dob_jobapplications (Lat/Lon DOB)

Longitude

• Longform Name: Longitude
• Old Name: longitude
• Description: Longitude in WGS84 / SRID:4326
• How it is created: See the description in latitude above

GeomSource

• Longform Name: Geography Source
• Old Name: x_geomsource
• Description: Source of the geographic coordinates for the record.
• How it is created:
  • This field is dependent on latitude and longitude
  • It is assigned as follows:
    • BIN DOB buildingfootprints: Geometry is the centroid of the DOITT building footprint that has the same BIN as the DOB job BIN
    • BIN DCP geosupport: Geometry is the centroid of the DOITT building footprint that has the same BIN as the BIN returned by Geosupport
    • Lat/Lon geosupport: Geometry is created from the latitude and longitude values returned by Geosupport
    • BBL DOB MapPLUTO: Geometry is the centroid of the Mappluto lot that has the same BBL as the DOB job BBL
    • BIN DOB buildingfootprints (historical): Geometry is the centroid of the historical DOITT building footprint that has the same BIN as the DOB job BIN
    • Lat/Lon DOB: Geometry is created from the latitude and longitude values in the DOB source data
    • Lat/Lon DCP: Geometry is created from latitude and longitude provided in the manual corrections file

DCPEditFields

• Longform Name: DCP Edit Fields
• Old Name: x_reason
• Description: List of fields that were edited by DCP. This only lists fields where original DOB source data was overwritten by DCP, and doesn't include fields where DCP recodes data as part of the standard methodology.
• How it is created:
  • Whenever a field is altered by a manual correction (as opposed to the programatic logic described in this Data Dictionary), the field name gets added to dcpeditfields

HNY_ID

• Longform Name: Housing New York ID
• Old Name: hny_id
• Description: nan
• How it is created:
  • This field is mapped from the hpd_hny_units_by_building fields project_id and building_id

HNY_JobRelate

• Longform Name: Housing NY to Job Join Relationship
• Old Name: hny_to_job_relat
• Description: nan
• How it is created:
  • This field describes how many HNY jobs match to DOB jobs. See the HNY workflow documentation for more information about how records are matched.
    • one_to_one: a HNY job matched to a single record in the developments database
    • many_to_one: multiple HNY jobs matched to a single record in the developments database
    • one_to_many: one HNY job matched to a multiple records in the developments database
    • many_to_many: multiple HNY jobs matched to a multiple records in the developments database

Version

• Longform Name: Version
• Old Name: *NEW*
• Description: Version of the Developments Database.