Dallas commercial building operations research
Dallas–Fort Worth–Arlington, TX MSA · CBSA 19100
OMB Bulletin 23-01 / July 2023 delineation
STATESTexas
Factum recovered and hash-verified the exact 31-account multi-point manifest, but it has not produced a physical-building count for the Dallas–Fort Worth metro. The manifest contains 31 LF-delimited AccountIDs, is 558 bytes, and has SHA-256 f44b1c2dc59cdde627ff1b701c37550400cdf834a8ded1746ba654a3fcb3db14. The separate 12-row bridge-exception manifest is not present in the canonical artifacts and was not reconstructed. DCAD and City references define appraisal-account, taxable-object, parcel and point-layer fields, but do not equate City AccountID, ParcelID, BldgID or UnitID with one physical building.
What the current denominator means
This Public Seed preserves a material source-control conflict instead of silently normalizing it. The canonical workspace copy of the 193,225,378-byte DCAD certified ZIP hashes to 452ac437b6989a0b3e0cae17e8d509261a1f7f5e058975d3481f1087f6d6f7cb, while a separate control receipt declares the same byte length with SHA-256 0909b3c1f6d31c81b47fb9cc8bd1be0b0d48a7b1df5214443365909e8bee7768; byte identity is unresolved. The archive documentation says commercial accounts may contain multiple taxable objects, including separate improvements such as a hotel and garage, and uses TAX_OBJ_ID rather than TAXABLE_OBJECT_ID. Current City layers separately expose appraisal account points and parcel rows; none is a building count.
Dallas Tax Account Points rows
Official City open-data rows for Dallas and a one-mile buffer; rows are account-point records, not physical buildings.
Distinct non-null account IDs
Distinct ACCOUNTID values in the current account-point layer; an appraisal account is not automatically one parcel or one building.
Repeated-account candidates
Accounts with more than one current source row. Of these, 586 have more than one distinct geometry and require identity review.
Recovered Dallas-situs exception accounts
Exact bounded gap list recovered from the accepted source contract; its account-point replay produced 430 features, with 272 one-row accounts and 31 multi-row accounts. These are appraisal/account-point records, not physical buildings.
Unresolved multi-point account cases
The exact sorted LF manifest is durably recovered as a 558-byte artifact with SHA-256 f44b1c2dc59cdde627ff1b701c37550400cdf834a8ded1746ba654a3fcb3db14. All 31 replay with more than one distinct point geometry; none has an accepted physical-building resolution.
Current appraisal-year 2026 account points
Official City of Dallas Tax Account Points query where AppraisalYr equals 2026. Of these, 328,649 also carry CityJuris DALLAS. These are account-point rows, not parcels or physical buildings.
Current appraisal-year 2026 parcel rows
Official City Tax Parcels rows where AppraisalYear equals 2026. They contain 463,976 distinct ACCT values and 467,449 distinct GIS_ACCT values; none is accepted as a physical-building denominator.
DCAD 2026 certified archive members
One official certified ZIP contains four reference files and fourteen CSV tables. The archive is an evidence package, not a denominator; no bulk row counts or identities were promoted from its CSV content in this audit.
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 Dallas buildings did Factum find?+
Factum has not accepted a large-building count. The public numbers on this page describe appraisal objects, accounts, and account-point rows, which can have one-to-many relationships with parcels and buildings.
02Why do some Dallas accounts have multiple points?+
The current layer has 668 account IDs with repeated rows; 586 have more than one distinct geometry. That is an identity-review signal, not proof of multiple buildings or a campus.
03Does this cover the full Dallas–Fort Worth metro?+
No. The appraisal source is Dallas County and the account-point layer is limited to Dallas plus a one-mile buffer. The other ten counties require separate official enumeration.
04Can these records be used for dispatch?+
No. This bounded metro slice has zero Graph Mapped, Verified, or Dispatch Ready records.
05Were the historical Dallas exception identifiers recovered?+
Partly. The exact 303-account screen and 31-account multi-point manifest are durably preserved, including the 31-manifest's byte count and SHA-256. The separate 12-row bridge-exception manifest, its identifiers and its generating predicate were not found, so no reconstruction or physical-building inference was attempted.
06Does the City BldgID field identify one physical building?+
Not from the public evidence available. The official Tax Account Points schema places BldgID beside AccountID, ParcelID and UnitID, but does not define its uniqueness, persistence or relationship to a building footprint. Factum therefore uses it only as a candidate field and accepts no building merge from it.
07What did the current Dallas source replay establish?+
The official layer returned 576,829 total rows, 518,389 appraisal-year 2026 rows, and 328,649 rows additionally scoped to CityJuris DALLAS. Those reproducible denominators improve source control, but the public metadata still does not define BldgID or resolve the 12 bridge exceptions, so no identity merge or state promotion occurred.
08Do the current DCAD download products resolve the City key fields?+
They clarify the appraisal grain but do not resolve the City keys. The recovered certified archive defines ACCOUNT_NUM and GIS_PARCEL_ID as appraisal account or parcel identifiers and TAX_OBJ_ID as a taxable-object identifier; commercial accounts can have multiple taxable objects. Its references do not define the City's BldgID or prove any one-to-one physical-building relationship, so no building key is accepted.
09What was recovered from the 2026 certified DCAD package?+
The 193,225,378-byte canonical workspace ZIP passed integrity checks and contains 18 members: four reference documents and fourteen CSV tables. Its local SHA-256 is 452ac437b6989a0b3e0cae17e8d509261a1f7f5e058975d3481f1087f6d6f7cb, while a separate control receipt declares the same byte length with SHA-256 0909b3c1f6d31c81b47fb9cc8bd1be0b0d48a7b1df5214443365909e8bee7768. The filename carries July 23 while the product page labels certification July 24, 2026; both the date-label and hash conflicts remain explicit.
Explicit unknowns
These are active research requirements—not footnotes to be smoothed over.
- 01The authoritative physical-building identity for all 31 recovered multi-point account cases.
- 02The exact relationship between the 12 COM_DETAIL-to-TAXABLE_OBJECT bridge exceptions and any physical building.
- 03The uniqueness, persistence, source-system meaning and physical-building semantics of the public Tax Account Points BldgID field.
- 04Parcel, building, and campus identity for the broader 586 current multi-geometry account candidates.
- 05Official enumeration and reconciliation for the other ten CBSA counties.
- 06Current ownership, management, operating rules, and dispatch-critical evidence for candidate buildings.
- 07Authoritative Tax Account Points field definitions or an official crosswalk that establishes whether BldgID, UnitID, AccountID and ParcelID map to physical buildings, appraisal improvements, units or another source grain.
- 08A versioned or archived City/DCAD source capable of replaying the target historical moment; the public Tax Account Points service declares no versioning, archiving, or historic-moment query support.
- 09An authoritative crosswalk between the DCAD certified archive's ACCOUNT_NUM, GIS_PARCEL_ID and TAX_OBJ_ID fields and the City's AccountID, ParcelID, BldgID and UnitID fields.
- 10Why two 193,225,378-byte retrievals of the named certified archive have different SHA-256 receipts; both remain source-time evidence until DCAD provides immutable release identifiers or checksums.
- 11The exact 12-row bridge-exception manifest, its identifiers, predicate and source receipt.
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.
- 01Dallas Central Appraisal District — Data Products ↗
Dallas Central Appraisal District · Supports: Certified appraisal-product provenance, July 2026 release context, archive receipt and included reference-document contract
- 02Dallas Central Appraisal District — 2026 certified archive ↗
Dallas Central Appraisal District · Supports: Exact official ZIP bytes, 18-member manifest, integrity check and SHA-256 receipt
- 03Dallas Central Appraisal District — GIS Data Products ↗
Dallas Central Appraisal District · Supports: Official historic parcel-package families and parcel-to-appraisal joining guidance; package bytes were not recovered in the latest pass
- 04City of Dallas Open Data — Tax Account Points ↗
City of Dallas · Supports: Account-point denominator, fields, geographic scope, and repeated-account partition
- 05City of Dallas GIS — Tax Account Points REST schema ↗
City of Dallas GIS · Supports: Official point geometry and co-located AccountID, ParcelID, AppraisalYr, BldgID and UnitID fields; public metadata does not establish BldgID as a unique physical-building key
- 06City of Dallas Open Data — Tax Parcels ↗
City of Dallas · Supports: Official parcel-layer reconciliation path
- 07U.S. Census Bureau metropolitan delineation files ↗
Federal government · Supports: Canonical CBSA identity and boundary vintage
- 08Dallas Central Appraisal District — parcel geometry join guide ↗
Dallas Central Appraisal District · Supports: Official ACCOUNT_NUM and GIS_PARCEL_ID semantics and parcel-to-account one-to-many relationship; does not equate them to City BldgID
- 09City of Dallas GIS — Tax Parcels REST schema ↗
City of Dallas GIS · Supports: Current 500,142-row parcel-layer denominator, account/parcel/unit field inventory and absence of public relationship classes, versioning and historic-moment replay
Public change history
Only meaningful, accepted public deltas appear here. The current record above remains canonical.
Dallas
Dallas entered Factum's public metro research library with 576829 bounded source records, 9 attributable sources and its denominator limits kept explicit.