Research/Metro/New York
Partial censusReviewed August 15, 2026

New York commercial building operations research

New York–Newark–Jersey City, NY–NJ MSA · CBSA 35620

BOUNDARY

OMB Bulletin 23-01 / July 2023 delineation

STATES

New York · New Jersey

Direct answer

Factum has completed a bounded Manhattan office-tax-lot reconciliation within the New York metropolitan area. The pinned screen produced 1,789 tax lots and joined to 1,974 City building-footprint records, but neither number is a count of verified physical buildings. The live official BUILDING table contains 1,083,024 features and its latest feature edit is August 7, 2026; no feature reports an edit after the August 13 target cutoff. The portal refreshed the published table on August 9, which is a separate system clock and not evidence of later feature edits. That narrows the drift risk but does not prove historical byte identity, deleted-row history, export ordering, checksum, or the missing 1,789-lot query contract.

Bounded source records1,789Not a building count
Graph mapped0Structured public-source records
Verified0Independent confirmation
Dispatch ready0Audited operational use
01

What the current denominator means

This Public Seed exposes a reproducible first layer for Manhattan only. It keeps tax lots, billing lots, base lots, BINs, footprint features, physical buildings, and campuses distinct. The official MapPLUTO 24v4 archive and NYC OTI Building_Historic_20241026.zip attachment are now pinned by public URLs and SHA-256 receipts. The 10,324,915-byte OTI ZIP contains 47,136 polygon and 47,136 point records. Exact archive analysis recovered the two multi-base-lot groups, while the pinned 1,789-cohort's 16 zero-match, 29 building-count-disagreement, and first-ten identifiers remain withheld until the prior query contract or target-era BUILDING companion snapshot is recovered.

1,789

Manhattan MapPLUTO office tax lots

MapPLUTO 26v1 records where LandUse equals 05 and BldgArea is at least 50,000 square feet; a tax lot is not automatically one physical building.

1,974

Joined NYC building-footprint features

OTI BUILDING features joined by billing BBL: 1,636 screened lots had one feature, 137 had multiple features, and 16 had none.

1,807

Current live PLUTO screen

Live PLUTO API count captured August 14, 2026 under the stated Manhattan LandUse 05 and BldgArea threshold. It is a later-vintage conflict and does not replace the pinned 1,789-lot cohort.

856,809

Recovered MapPLUTO 24v4 citywide records

Official archived shoreline-clipped MapPLUTO 24v4 records. The 289 MB archive has SHA-256 92e916f42d5740ea210fdd389103b2a4ebe142a52012789fd5832b2ce483cae3; 42,120 records are Manhattan BBLs. This artifact recovery does not reconstruct the missing 1,789-lot cohort.

47,136

Recovered 2024-10-26 historic-footprint polygons

Exact NYC OTI attachment Building_Historic_20241026.zip: 10,324,915 bytes, SHA-256 a2b92d0bef94ae3dd5107b17840e985d2d2cc8921651293ae1186f623649ab26, with 10 archived shapefile components and a matching 47,136-record point layer. This is a source artifact, not a physical-building denominator.

4,171

Live historical-footprint diagnostic rows

A bounded OTI BUILDING_HISTORIC query returned 4,171 Manhattan-prefixed rows across 2,948 distinct BASE_BBL values; 1,369 intersect the recovered 24v4 Manhattan BBLs. The live historical table includes later edits and is not the missing 2024-10-26 snapshot.

1,083,024

Current OTI BUILDING features

Live official BUILDING dataset 5zhs-2jue at the August 15, 2026 audit. Its row count matches the accepted August 13 capture and the latest reported feature edit is August 7, 2026; a direct query found zero rows edited after the August 13 target cutoff. This does not prove deleted-row history, export ordering, immutable bytes, a revision identifier, or a target-date checksum.

856,614

Recovered MapPLUTO 26v1 citywide records

Official May 2026 shoreline-clipped MapPLUTO shapefile: 152,395,906 bytes, SHA-256 84b213b86745c7daa4c75749ce7e9181633c834d70811280dbd9ea2045971876, EPSG:2263. This verifies the release artifact, not the withheld 1,789-lot selection contract.

37

Final BUILDING source-event-day features

Features carrying the August 7, 2026 maximum source-edit date, spread across 36 tax lots. Those lots have zero overlap with the 2,088 BBLs in DCP's PLUTO 26v1 change file and do not identify the withheld 1,789-lot cohort.

02

Questions this page answers

Compact answers are rendered in visible HTML and structured data so people and answer engines can retrieve the same claims and caveats.

01How many large Manhattan office buildings did Factum find?+

The bounded source screen returned 1,789 office-class tax lots, not 1,789 verified buildings. Those lots joined to 1,974 footprint features, including zero-match, multi-feature, base-lot, and placeholder exceptions that still require identity review.

02What is in the preliminary clean pool?+

After excluding zero-footprint lots, multi-footprint lots, MapPLUTO building-count disagreements, base-lot differences, multi-base-lot cases, and the placeholder triangle, 1,411 records remain in the strict preliminary pool. This is a research queue, not an accepted building count.

03Does this cover the full New York metro?+

No. This release covers one Manhattan source slice. The other counties and independent regional source layers remain to be enumerated and reconciled.

04Can these records be used for dispatch?+

No. Graph Mapped, Verified, and Dispatch Ready are separate states; this bounded metro slice has zero records in each state.

05Why does the current PLUTO count differ from the published reconciliation?+

The published reconciliation used a pinned 1,789-lot cohort. The live API returned 1,807 on August 14, 2026. Because the original exception and first-ten ID lists were not retained, Factum records the drift and will not substitute the newer cohort for the historical one.

06What did the latest recovery establish?+

The official MapPLUTO 24v4 archive and NYC OTI Building_Historic_20241026.zip attachment are reproducible and hash-verified. The recovered OTI archive contains 47,136 polygon and 47,136 point records. It also exposes two exact multi-base-lot groups, but it does not by itself reproduce the withheld 16 zero-match, 29 disagreement, or first-ten sets because their prior query contract is missing.

07Which multi-base-lot groups were recovered?+

BASE_BBL 1015480146 maps to MPLUTO_BBL 1015480046 and 1015480146 across DOITT_IDs 83808, 504375, 318342, and 58807. BASE_BBL 1018310002 maps to MPLUTO_BBLs 1018310002, 1018310003, and 1018310004 across DOITT_IDs 845002, 125124, and 277808. These are source relationships for review, not accepted building or parcel merges.

08Did the current BUILDING denominator recover the August 13 snapshot?+

No. The live official dataset has the same 1,083,024-row denominator and reports an August 9 update, but no immutable export hash, revision ticket, ordering receipt, or archived target-date object is public. Factum records it as a strong reproducible candidate, not exact retrospective recovery.

09Does the August 9 portal refresh mean building features changed after August 7?+

Not from the public evidence. August 9 is the Socrata table-publication clock; the latest feature-level edit remains August 7. The 37 features on that final event day occupy 36 lots and do not overlap the 2,088 BBLs in the PLUTO 26v1 change file.

04

Explicit unknowns

These are active research requirements—not footnotes to be smoothed over.

  1. 01Physical-building and campus identity for every tax-lot and footprint exception.
  2. 02Resolution of 16 screened tax lots with no joined footprint and 137 with multiple footprint features.
  3. 03Resolution of 29 MapPLUTO building-count disagreements and 248 base-lot differences; the two multi-base-lot source groups are now identified but not merged.
  4. 04Official-source enumeration and cross-source reconciliation outside Manhattan.
  5. 05Current ownership, management, operating rules, and dispatch-critical evidence for ranked building candidates.
  6. 06The exact BBL, BIN, and DOITT_ID lists for the pinned 16 zero-match, 29 building-count-disagreement, and preliminary first-ten groups.
  7. 07The prior query contract and target-era current-BUILDING companion snapshot needed to regenerate the withheld exception sets without mutable-data substitution.
  8. 08The exact retained current-BUILDING companion release needed for the pinned join remains unlocated. NYC Open Data's official BUILDING map metadata states that prior posted versions are retained and can be provided on request, but no specific requested release, byte object, denominator, or checksum has yet been accepted.
  9. 09Whether any of the 1,369 diagnostic 24v4-to-live-historical intersections belong to the missing pinned 1,789 cohort.
  10. 10The immutable August 13, 2026 BUILDING export bytes, target-date checksum, export format and ordering, revision identifier, and exact 1,789-lot predicate.
  11. 11Whether deletions, row ordering, geometry serialization, or export packaging changed despite the stable row count and absence of post-cutoff feature-edit timestamps.
05

Sources and scope

Public-page claims are limited to what the cited sources support. Source records, parcels, accounts, footprints, campuses, and physical buildings remain distinct identities until reconciled.

  1. 01
    NYC Department of City Planning — PLUTO and MapPLUTO

    New York City Department of City Planning · Supports: MapPLUTO 26v1 tax-lot fields and bounded Manhattan office screen

  2. 02
    NYC OpenData — Building Footprints

    New York City Office of Technology and Innovation · Supports: Citywide BUILDING feature denominator and footprint join

  3. 03
    NYC OpenData — current BUILDING map metadata

    New York City Office of Technology and Innovation · Supports: Official current BUILDING visualization metadata, its source dataset relationship, and the explicit statement that previously posted versions are retained and available by request; this is a recovery route, not the missing target release

  4. 04
    NYC Building Footprints metadata

    City of New York · Supports: FEATURE_CODE semantics, including code 1003 placeholder triangles

  5. 05
    NYC OpenData — PLUTO 26v1 API metadata

    New York City Department of City Planning · Supports: Current PLUTO release metadata and the August 14 live-count drift check

  6. 06
    NYC Department of Buildings — Get Building History

    New York City Department of Buildings · Supports: Official route for future BIS and DOB NOW property-history verification

  7. 07
    NYC Planning — MapPLUTO archive manifest

    New York City Department of City Planning · Supports: Official versioned archive index used to recover and hash-verify the MapPLUTO 24v4 shapefile

  8. 08
    NYC OpenData — BUILDING_HISTORIC metadata

    New York City Office of Technology and Innovation · Supports: Historic-footprint field semantics and the named Building_Historic_20241026.zip snapshot asset

  9. 09
    NYC OpenData — exact BUILDING_HISTORIC 2024-10-26 attachment

    New York City Office of Technology and Innovation · Supports: Exact public ZIP bytes, filename, attachment identity, checksum receipt, archive manifest, and 47,136-record polygon/point denominators

  10. 10
    NYC OpenData — BUILDING_HISTORIC historical versions

    New York City Office of Technology and Innovation · Supports: Official statement that previously posted versions are retained and can be provided upon request

  11. 11
    NYC OpenData — DOB Job Application Filings metadata

    New York City Department of Buildings · Supports: DOB filing-source borough, block, and lot semantics; filings are not a building-count replacement

  12. 12
    U.S. Census Bureau metropolitan delineation files

    Federal government · Supports: Canonical CBSA identity and boundary vintage

  13. 13
    NYC OpenData — BUILDING dataset 5zhs-2jue

    New York City Office of Technology and Innovation · Supports: Current 1,083,024-row denominator, schema, update timestamp and mutable-export boundary; metadata SHA-256 600e10aa723ba78016d3ead2314681d5c38db74f95cb23d6532cd8759de8e535

  14. 14
    NYC Planning — MapPLUTO 26v1 shoreline-clipped shapefile

    New York City Department of City Planning · Supports: Exact official May 2026 artifact, 856,614-feature denominator, EPSG:2263 CRS and SHA-256 receipt

  15. 15
    NYC OpenData — PLUTO Change File

    New York City Department of City Planning · Supports: PLUTO 26v1 change-file denominator and independent zero-overlap check against the 36 final BUILDING event-day lots