CityMETER

Google Research — Open Buildings — CityMETER names Open Buildings directly, so this is an external source rather than GD Catalog lineage.

Use it to compare building intensity, gross floor area, height and floors at summary level—not as a building register or verified footprint for every structure.

Department of Lands — Project, permit, developer, title-document and plot fields match the official land-allotment permit dataset.

Monthly nationwide coverage; this card uses the land-allotment part of the package.

Use it for permit history and project distribution. A permit does not prove completion, current availability or occupancy.

ONEP — Project, owner, report type, document, approval date, category and location fields match Smart EIA.

Nationwide projects since 1992; the live API changes, so the card avoids a frozen total.

CityMETER is a curated, geocoded snapshot. Approval does not prove construction, operation or current compliance.

Department of Agricultural Extension production registry family (candidate) — The field family resembles DOAE production registries, but CityMETER's 2025–2026 monthly grain and taxonomy have not been reconciled to one exact package.

Use as provisional crop-area and output context until the exact resource, taxonomy and coverage are reconciled.

Department of Lands / Treasury Department — Combines parcel location and area from the Department of Lands with official Treasury appraisal values.

Versioned, transformed parcel layer; appraisal update dates vary by province.

Useful for screening and reference checks before parcel due diligence; it does not prove ownership, encumbrances or transaction price.

Private listing layer — public lineage not yet verified — No exact government-dataset lineage was verified for the land asking-price layer.

This is an asking-price signal, not a closing price. Verify source, collection date, duplicate handling and outlier treatment before comparison.

Public source lineage not yet verified — No public package or manifest currently reconciles apartment-rent records to a repeatable source.

Treat it as a sampled rent-range signal, not the whole market or current rent for every building.

Treasury Department — Project/building schema and appraisal values align with the official condominium valuation dataset; CityMETER is a transformed snapshot.

The source states a four-year cycle; the inspected resource was updated 14 Aug 2024.

Use it as an official value baseline before market comparison; appraisal is neither listing nor latest transaction price.

Private asking-price layer + candidate Treasury benchmark — The appraisal benchmark is official, but condo/building IDs and the ETL join to private listings have not been fully evidenced.

Use the gap as an exploratory signal; project-level use requires duplicate, unit and join-method checks.

Private listing layer — public lineage not yet verified — No public source manifest yet states coverage, vintage or deduplication rules for detached-house listings.

Price and land size help screen the market, but these are asking prices and sampling may vary by area.

Private listing layer — public lineage not yet verified — No public manifest yet documents townhouse listing coverage, date, duplicates or outlier treatment.

Listing counts and percentiles show supply and asking ranges, not sales volume or closing prices.

LivingInsider / private listings — CityMETER names LivingInsider directly, so this is not GD Catalog lineage.

Rent, yield and investment scores are listing-derived; verify assumptions, costs, vacancy and duplicates before decisions.

Department of Business Development — Uses the legal-entity register and new/dissolution events; CityMETER is a curated, geocoded subset.

CityMETER snapshot: Apr 2024–Apr 2025; verify each resource title rather than inferring event type from package ID alone.

Legal registration status is not actual opening or closure, and registered capital is not investment, revenue or employment.

Revenue Department — Records were reconciled by legal-entity number, branch code, name and address against the VAT operator register.

Monthly source; CityMETER is a transformed snapshot.

CityMETER uses an enriched, geocoded 50,000-branch subset. Registered address is not proof of operation at that point and does not cover every business.

Industrial factory register (high-confidence candidate) — The field fingerprint matches the factory register, but factory-ID reconciliation or an ETL source manifest is still missing.

Use the factory, worker, capital and machinery measures exploratorily until definitions, units and registry coverage are confirmed.

Commercial inventory — public lineage not yet verified — The office-building and asking-rent inventory did not match the official building packages reviewed.

The evidenced scope is Bangkok. Prices are asking rents, not contracted rent or occupancy.

Private place/review source — public lineage not yet verified — Ratings, price bands and density did not align with the government restaurant registers reviewed.

Use as competitive context, not demand, customer count or independently verified quality; collection date and coverage are required for comparison.

Commercial inventory — no matching government package verified — GLA, GFA, tenant count and market segment did not match the government datasets reviewed.

Use to compare retail structure in the sample; unequal field coverage means it should not be presented as market totals.

Tourism Authority of Thailand — Accommodation (candidate) — The field signature closely resembles TAT Accommodation, but hotel and room totals have not been reconciled to the same snapshot.

Use supply, asking-rate and seasonality as an initial comparison—not as occupancy, bookings or hotel revenue.

Ministry of Tourism and Sports / Tourism Authority of Thailand — Demand reconciles to the official MOTS workbook after unit conversion; activities and attractions use official TAT channels.

Year–month–province grain; exact values reconcile to the official workbook, not every byte of the frozen GD JSON.

Compare visitors, receipts, seasonality, activities and attractions. Visitor counts are not unique people and figures may be revised.

No official package yet matches the displayed fuel mix — The DOEB package reviewed did not contain the same EV, LPG, NGV and fuel-availability mix shown by CityMETER.

Use as provisional automotive-service context until station definition, effective date and multi-fuel counting are verified.

Department of Land Transport — February 2026 values were reconciled at year, month, vehicle type, make, model and count level.

Monthly national statistics; CityMETER shows Jan 2020–Feb 2026.

This is first-registration statistics, not the active fleet, travel behaviour or where vehicles operate.

CityMETER derived model — This is a derived road-network model rather than an atomic GD Catalog dataset.

Dead-end and intersection measures are diagnostic signals—not location quality, accessibility, traffic or a good/bad verdict.

Current/7-day traffic feed — public source contract not yet verified — The current and seven-day feed did not match the static OTP studies reviewed, and no public SLA was found.

Use only with timestamp and feed status visible; delayed or unavailable data does not mean free-flow traffic.

CityMETER derived / LLM-assisted contextual layer — This is a contextual synthesis across several signals, not one exact GD Catalog dataset.

Use it to frame questions, prioritise places and plan field validation; do not treat behavioural descriptions as facts without evidence and a boundary crosswalk.

Bureau of Registration Administration, Department of Provincial Administration — Monthly age, sex and area dimensions align with DOPA statistics for people listed in house registration.

The official download covers 2013–Jul 2026 and can reach village level; always show the reference month.

Use for age-structure planning, but call it registered population—not daytime, resident or live population.

Ministry of Education (candidate) — Owner, grain and schema align with the school dataset, but school-code/name/year records have not been reconciled.

School, student, teacher and ratio measures describe service context—not quality, access or spare capacity.

Department of Local Administration — The backend owner confirmed DLA localincome; fields and local-authority grain align. No exact central GD Catalog package was found.

Verified CityMETER lineage covers 2017–2024; a 2025 resource was added later to the catalogue.

Compare own-source, allocated, grant and total revenue. Per-capita/area metrics are CityMETER calculations and are not service quality.

Composite layer — no single matching package verified — CityMETER combines agency and workforce categories, but no public manifest separates the owner and release of each component.

Counts, contacts and workforce describe service structure—not availability, quality or eligibility.

GISTDA disaster layers (candidate) — CityMETER uses annual observed extents for 2011–2024, while the located recurrence/risk package covers 2011–2023 and produces a different output.

Use for recurrent history—not current conditions, a forecast or a statutory risk determination.

GISTDA flood boundary (candidate) — Geometry may come from GISTDA, but endpoint, resource, vintage and exposure-overlay transformation remain unverified.

Read the observation date before the word ‘latest’; uncoloured areas are not automatically safe and a snapshot is not live conditions.

Department of Water Resources forecast layer; exact public package not yet verified — Forecast runs and depth output did not match the historical-risk packages reviewed in GD Catalog.

Show run time, method, model and limits. A forecast is not an observation, guarantee or emergency instruction.

Google Flood Forecasting — CityMETER identifies the Google provider/model, so this is not GD Catalog lineage.

Use as a 24-hour monitoring signal with experimental status and run time—not confirmation of an event or travel advice.

TMD event feed with RUGON / USGS — Located GD records are station inventories or annual aggregates at a different grain from CityMETER's event/sensor view, so lineage is not counted.

Read station location, MMI, acceleration and update time together; freshness must always remain visible.

NASA VIIRS / FIRMS — The field fingerprint points to NASA VIIRS/FIRMS rather than a GD Catalog dataset.

CityMETER's unit still needs confirmation as hotspot, burned area or incident, so counts should not be turned into risk conclusions.

Department of Disaster Prevention and Mitigation — Event–area/village grain, 2014–2024 period and impact fields match the official village disaster-event statistics.

Annual CSVs for 2014–2024; latest verified data year is 2024.

Use for historical impact comparison and follow-up; one event may span several rows and the data is neither forecast nor current conditions.

Thai PBS / ThaiHelp case reports — Core case reports come from event-reporting sources rather than a GD Catalog dataset.

Use as a 24–27 Nov 2025 event archive for sequence and context—not as a reusable flood layer or complete impact assessment.

BMA Building Inspection Dashboard — exact record lineage not yet verified — Attribution points to the BMA dashboard, but no repeatable package or record reconciliation was found.

Use to understand post-event follow-up workflow—not as structural certification, a sensor network or a current inventory of every building.