Where the user is right now: address, coordinates, their local time, how old the fix is, which trip they are on and day N of it, and how far from home. Read this before saying anything about where they are.

The chronological list of stays over a period: every stop with start, end and duration, the trip it belongs to, and the place. Use it to reconstruct a day, a week or a trip in order.

Cities over a period, with time in each, how many separate times they were there, and which days. Use for 'which cities did I go to last spring'.

Countries over a period: separate trips there, time spent, distinct days, and the cities inside each. Pass country for one of them ('how many times have I been to Japan').

The places they spend time in, most time first: address, city, what the source calls the place, how many stops and how many hours. Use for 'where do I actually spend my time' or to find an address.

Trips, newest first: name, dates, nights, countries, cities, how far from home, and who was along. A trip is a run of nights outside the country they live in or over 100 km from it. Names edited by hand are kept.

One trip in full: the day-by-day country and city, every stay, the journeys with mode and distance, the people tagged on it, and the note. Identify it by slug, by name, or by a date inside it.

The link between trips and a people graph, both ways. Pass person for the trips shared with them, trip for everyone tagged on it, neither for every tagged pairing. Needs the optional people bridge.

One date end to end: where they woke up, every stay in order, the journeys between them with mode and distance, the trip it belongs to, and how far from home. Use for 'what did I do on the 8th'.

How much they moved over a period: kilometres by mode, number of flights and the longest, days away from home against days at home, countries and cities touched.

The extremes: highest point, fastest, farthest from home, the four compass records, longest trip, most cities in a day, longest flight. Each carries the window it was measured over, which is not the same for all of them.

Where they have lived and when. Home is a timeline, not a point, so anything home-relative has to read this rather than assume one address.

What the archive actually holds, table by table, with the span each source covers and every gap of two weeks or more. Check this before concluding someone was never somewhere: 'no record' and 'was not there' are different answers.

Read-only SELECT for questions the other tools do not shape. Tables: location_visits(started_at, ended_at, start_offset_m, place_id, semantic_type), location_activities(started_at, ended_at, mode, distance_m, start_lat, start_lon, end_lat, end_lon), location_places(id, lat, lon, address, label, city, admin, country, country_code, tz), location_pings, location_raw_positions(altitude_m, speed_ms), location_trips. Views: location_v_stays (the history spine), location_m_day_home (one row per day with the anchor place and km from home), location_v_records, location_v_home_periods. With the people bridge installed: location_trip_people, location_v_trip_people, people_v_trips.