tochiterra.

JAPAN, BEYOND THE USUAL LISTINGS

One map.
More of Japan.

Homes and hidden akiya. A mountainside forest. A hotel, a local business, a boat. The source plan for bringing them together in TochiTerra.

01 / SOURCE DIRECTORY

A wider view of what's out there.

Download source catalog ↓

Catalog updated October 30, 2026 (Honolulu). It now covers 56 source entries, including portal partners, local akiya discovery, forest-property and boat marketplaces, the official broker-license lookup and an MLIT open-data snapshot. Each entry includes coverage, evidence and its next access step. Most live listing sources still need a source-specific review or agreement.

Loading source directory…

Coverage labels describe potential inventory, not today's listing counts. Directories and MLIT price/context data are identified separately. Several large sites limited research access; those entries explicitly retain their verification gaps.

02 / FIREBASE INTEGRATION PLAN

Fresh listings. A traceable source.

Proposed · not running

Two incremental passes at 09:00 and 21:00 Japan time (02:00 and 14:00 Honolulu). Initial collection is a separate, paced backfill; routine runs fetch changes within each source's permitted limits.

  1. 01

    Schedule & queue

    Cloud Scheduler triggers Firebase Functions. Cloud Tasks splits work by approved source, category and region.

  2. 02

    Collect & normalize

    Source-specific adapters read permitted feeds or pages, validate yen prices and record source IDs, timestamps and location precision.

  3. 03

    Store & reconcile

    Firestore keeps source offers, matched assets and change history. Failures stay visible; a failed fetch never means “sold.”

  4. 04

    Serve the map

    A bounded search API returns approved listings and clusters for the visible map area. USD values use the same dated exchange rate.

Proposed Firestore collections and launch sequence

sourcesAccess state, coverage, adapter version, permitted URLs, limits and feed configuration references.

sourceOffersStable source ID, original price, transaction type, observations and status history.

assetsCanonical property or vessel, subtypes, location precision, measurements and duplicate-match evidence.

publicListingsSanitized, approved map/search records; no raw private owner data or internal crawl details.

ingestionRuns / tasksProgress, retries, complete/partial coverage, counts and parser failures.

exchangeRates / priceHistoryDated reference rates and original-currency price changes; USD remains a computed estimate.

Firestore Enterprise settings are recorded for Tokyo, but cloud synchronization and public map listeners have not completed setup. The local SQLite collectors are active on demand; Jimoty and the three large portals are enabled. The current parallel pass includes 285 sources with configured collectors. Three directory entries are discovery-only and the real-estate data library needs an API key.

Platform references: scheduled functions · task queues · geographic queries. Final queries, indexes and SDK choices depend on the selected Firestore edition.

03 / MAP BEHAVIOR

A different kind of treasure.
The same clear map.

Planned multi-select layers: homes, land, commercial, hotels & ryokan, forests, farmland, businesses and boats. Akiya is also a feature filter, so a vacant house keeps its house category.

Color shows the current USD price band. Hover or tap reveals price, property type and source freshness. Text labels, icons and a legend make the meaning readable without relying on color alone.