Problem

Saved places pile up in Google Maps as a flat, unstructured list — useful for dropping a pin, useless for planning a trip around it. Tabiji turns that raw location data into something structured: a plan you can route, order and reason about.

Approach

Tabiji ingests Google Maps saved-place exports and normalises them into a single itinerary model. Rather than treating each saved place as a loose bookmark, the data model gives it a structured home — the same normalised schema covering routes, filming locations, food logs and inventory. It’s built on Next.js with Supabase behind it and the Google Maps API supplying the location layer.

What it does

Ingests Google Maps saved-place exports
Normalises them into one itinerary model
Structures routes, filming locations, food logs and inventory
Keeps location-aware trip data in a single schema

Status

Pre-launch. The core is the ingestion path and the normalised itinerary model that sits under it — not yet publicly launched.