Attribute mapping

job_number

• Mapped from dob_jobapplications jobnumber
• 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.

job_type

• Mapped from dob_jobapplications jobtype.
  • A1 to Alteration
  • DM to Demolition
  • NB to New Building
• Administrative records are removed based on this field in combination with job_description.
• DOB's type category for the job application. 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).

For more information see https://www1.nyc.gov/site/buildings/homeowner/permits.page.

resid_flag

• 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.

nonres_flag

• 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_inactive

• Dependent on date_complete, job_status, date_lastupdt
• A job can only be inactive if date_complete is NULL
• A job is set to inactive for:

1. All jobs with a status of 9. Withdrawn
2. Jobs with a status of Filed Application, Approved Application, OR Permitted for Construction AND date_lastupdt is 3 or more years before the vintage date.
3. If 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.

job_status

• Dependent on on job_type, co_latest_certtype, classa_complt_pct, classa_complt_diff, classa_net, x_withdrawal, and date fields

• if the withdrawn flag as a value of W, C THEN 9. Withdrawn
• when it's a NB or A1 and the CO is a Temporary CO AND less than 80% of the units are completed for a building with 20 or more - units THEN 4. Partially - Completed Construction
• date_complete IS NOT NULL THEN 5. Completed Construction
• date_statusr IS NOT NULL THEN 3. Permitted for Construction
• date_permittd IS NOT NULL THEN 3. Permitted for Construction
• date_statusp IS NOT NULL THEN 2. Approved Application
• assigned IS NOT NULL THEN 1. Filed Application
• date_statusd IS NOT NULL THEN 1. Filed Application
• paid IS NOT NULL THEN 1. Filed Application
• date_filed IS NOT NULL THEN 1. Filed Application

complete_year

• Dependent on date_complete.
• The year of date_complete.

complete_qrtr

• Dependent on date_complete.
• The quarter of the year of date_complete.

permit_year

• Dependent on date_permittd.
• The year of date_permittd.

permit_qrtr

• Dependent on date_permittd.
• The quarter of the year of date_permittd.

classa_init

• Mapped from dob_jobapplications existingdwellingunits
• Set to 0 for New Buildings

classa_prop

• Mapped from dob_jobapplications proposeddwellingunits
• Set to 0 for Demolitions

classa_net

• Dependent on classa_init and classa_prop
• The difference between classa_init and classa_prop

units_co

• Mapped from dob_cofos numofdwellingunits

classa_hnyaff

• Mapped from hpd_hny_units_by_building all_counted_units
• The sum of all_counted_units for HNY records associated with the job

hotel_init, hotel_prop, otherb_init, and otherb_prop

• All are directly from the manual research table.

boro, bin, bbl

address_numbr, address_st, address

• The address information for the record from Geosupport; however, if Geosupport did not return any information then this is the address information from the housenumber and streetname in dob_jobapplications.

occ_initial

• Mapped from dob_jobapplications existingoccupancy and translated using the lookup table

occ_proposed

• Mapped from dob_jobapplications proposedoccupancy and translated using the lookup table

job_desc

• Mapped from dob_jobapplications jobdescription.
• Administrative records are removed based on this field in combination with job_type.
• Test records are removed based on this field.

date_filed

• Mapped from dob_jobapplications prefilingdate

date_statusd

• Mapped from dob_jobapplications fullypaid

date_statusp

• Mapped from dob_jobapplications approved

date_permittd

• The earliest issuancedate from dob_permitissuance

date_statusx

• Mapped from dob_jobapplications signoffdate

date_lastupdt

• Mapped from dob_jobapplications latestactiondate

date_complete

• Mapped from the earliest effectivedate from dob_cofos for NBs and Alts
• Mapped from date_permitted for DM IF date_statusx IS NOT NULL

zoningdist1, zoningdist2, zoningdist3, specialdist1, specialdist2, landmark, zsf_init, zsf_prop, bldg_class, desc_other

• Mapped from dob_jobapplications zoningdist1, zoningdist2, zoningdist3, specialdistrict1, specialdistrict2, landmarked, existingzoningsqft, proposedzoningsqft, buildingclass, otherdesc

stories_init

• Mapped from dob_jobapplications existingnumstories for only A1 and DM job types
• '0' is replaced with NULL

stories_prop

• Mapped from dob_jobapplications proposednumstories for only A1 and NB job types
• '0' is replaced with NULL

height_init

• Mapped from dob_jobapplications existingheight for only A1 and DM job types
• '0' is replaced with NULL

height_prop

• Mapped from dob_jobapplications proposedheight for only A1 and NB job types
• '0' is replaced with NULL

constructnsf

• Mapped from dob_jobapplications totalconstructionfloorarea

enlargement

• Mapped from dob_jobapplications 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

• Mapped from dob_jobapplications enlargementsqfootage

costestimate

• Mapped from dob_jobapplications initialcost

loftboardcert

• Mapped from dob_jobapplications loftboard

edesignation

• Mapped from dob_jobapplications littlee
• WHEN littlee = 'Y' or 'H' then edesignation = 'Yes'

curbcut and tracthomes

• Mapped from dob_jobapplications curbcut and cluster

ownership

• Mapped from dob_jobapplications cityowned, ownertype, and nonprofit
• The three input values are translated into a single value using this lookup table

owner_name

• Mapped from dob_jobapplications ownerfirstname and ownerlastname

owner_biznm, owner_address, owner_zipcode, and owner_phone

• Mapped from dob_jobapplications ownerbusinessname, ownerhousestreetname, zip, and ownerphone

pluto_*, pluto_firm07, and pluto_pfirm15

• All of these fields are mapped from dcp_mappluto, which is the clipped version of MapPLUTO, by joining on the geo_bbl to the PLUTO bbl

cenblock2010, bctcb2010, bct2010, nta2010, ntaname2010, puma2010, comunitydist, councildist, schoolsubdist, schoolcommnty, schoolelmntry, schoolmiddle, firecompany, firebattalion, firedivision, policeprecnct

• All of these fields come from Geosupport if the address returns a value and the record is not in TPAD; otherwise, the value is generated from a spatial join.

latitude and longitude

• The latitude and longitude value are assigned in the following order:

1. DoITT building footprints point using dob_bin as a join_key (BIN DOB buildingfootprints or BIN DOB buildingfootprints (historical))
2. DoITT building footprints point using geo_bin as a join_key
3. 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)

geomsource

• Dependent on latitude and longitude
• Describes how point geometry was created
  • 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

hny_id

• Mapped from hpd_hny_units_by_building project_id and building_id

hny_jobrelate

• Dependent on how many HNY jobs match to one DOB job, and vice versa

version

• The version of the database