Field dictionary

This page lists every field JMAD tracks on a building, its type, and where it typically comes from. For how a value is chosen when sources disagree, see provenance and precedence.

Every field below is nullable at the building level: JMAD publishes what it has and leaves the rest out rather than guessing. assetTypes, addressJa, and footprintM2 are the only fields required to publish a page at all — a building needs at least one asset type.

Naming

Asset types

A building can serve more than one use at once — a tower that is office above and retail at street level is both. assetTypes is therefore a repeated field, sitting beside aliases at the top level of a page rather than inside fields, and each entry carries its own provenance.

"assetTypes": [
  {
    "value": "office",
    "category": "office",
    "tier": "free",
    "provenance": { "source": "jreit", "...": "..." }
  },
  {
    "value": "retail",
    "category": "retail",
    "tier": "free",
    "provenance": { "source": "osm", "...": "..." }
  }
]

value is the source's own wording, passed through: OSM's building=* tag (office, apartments, retail, …), PLATEAU's bldg:usage code mapped onto that same vocabulary, or a disclosure's 用途 column read into an asset class. JMAD does not enforce a closed list on value. OSM's generic tag value yes is dropped rather than published as a type, as are PLATEAU code 461 (“unknown”) and any unlisted code.

category is JMAD's own coarse classification of that value, and it is what makes the list meaningful across sources that name the same use differently. One category appears at most once per building: if OSM says apartments and a J-REIT disclosure says residential, that is one residential use worded two ways, not two uses, so a single entry is published carrying the higher-precedence source's wording. Two entries mean two genuinely different uses.

A value outside this table publishes with category: null and groups under itself, so an unrecognised tag is never silently merged into a use it does not belong to.

Because a category is a use rather than a disagreement, asset types are not counted in conflictsFlagged. Two sources naming two different uses is the normal case, not a conflict to resolve.

Location

Physical attributes

Institutional disclosures

These nullable fields, together with completionMonth and structure above, are available in building JSON, API and MCP responses, building pages and Markdown twins. Current disclosed values use the free tier. Coverage is limited to records matched to an existing building using a unique name plus address or coordinate evidence.

A REIT holding can be a partial interest or a complex with multiple buildings. Financial amounts describe the disclosed holding and must not be interpreted as a valuation of the entire building without reading the source. Unmatched and ambiguous records are not attached to building pages. Missing values remain null.

Ownership and design

Certifications

Join keys

Geometry

footprint and centroid are geometry fields, not plain values, but they carry the same provenance shape as everything else.

Polygon calculations subtract interior rings from footprint area. Point containment excludes hole interiors and includes outer and hole boundaries, matching ST_Covers boundary semantics. Overlap handles concave polygons and sums disconnected intersection parts; it divides intersection area by the smaller input area.

Calculations use GeoJSON WGS84 longitude/latitude and a local planar approximation in metres with a spherical Earth radius of 6,371,000 m. Area uses the first outer vertex's latitude; overlap projects both polygons into one local coordinate system. These are building-scale calculations, not survey-grade geodesic measurements. centroid is the average of the outer ring's vertices, not an area-weighted centroid; JMAD uses it to place the building during location resolution.

The footprint schema still accepts Polygon, not MultiPolygon. Preserving disjoint input parts through loaders, storage, and public responses is tracked separately in JMA-53.

Venues

A building can host more than one venue: tenants, shops, a named floor. Venue fields live on their own record, joined to the building by ID.

What is deliberately not a building field

Transaction prices from MLIT's 不動産情報ライブラリ are not published on a building. MLIT anonymizes every transaction to a prefecture, city, district (地区名, a town such as 岩本町) and quarter, with no building name, street number or identifier of any kind. Attaching one to a building would assert a link that was never observed, so these records are stored separately and used only for area-level context.

Sources, history and counters

Every page also carries three summary blocks rather than raw fields:

丸ビル's page, for example, would show heightM in its conflicts count, because Wikidata's 179.2 m and OSM's 18 m disagree. See data lifecycle for how history entries accumulate over time and areas and coverage for how coverage is measured per field across an area.