I maintain Dawarich, which imports all of these formats, so I've spent more time than I'd like reading Google's location JSON. Here's everything I know about what's inside your export — every field, every quirk, every format Google has shipped over the years.

Three formats, one mess​

Google has shipped three different export formats over the years. Which one you get depends on when you exported, how you exported, and seemingly what mood their servers were in that day. Some people get one, some get all three. So the first thing is figuring out what you're dealing with.

Here's the quick version:

• Records.json — Raw GPS pings. Every location reading your phone ever reported. The oldest and most common format from Google Takeout.
• Semantic Location History — Monthly JSON files with Google's interpretation of your movements. Place visits, activity segments, confidence scores. Structured and readable, but heavily processed.
• Phone Takeout format — The newer format you get when exporting directly from Google Maps on your phone. Contains semanticSegments, rawSignals, and userLocationProfile. Same data, completely different structure. Because consistency is apparently optional at Google.

Let's go through each one, field by field.

Format 1: Records.json​

This is the big one. A single JSON file containing every raw GPS ping Google ever collected from your devices. I've seen people with Records.json files north of 500MB, spanning a decade of tracking. It's a flat array of location objects wrapped in a locations key.

Here's what a typical entry looks like:

{
  "locations": [
    {
      "latitudeE7": 533690550,
      "longitudeE7": 836950010,
      "accuracy": 22,
      "altitude": 150,
      "verticalAccuracy": 10,
      "heading": 270,
      "velocity": 15,
      "source": "WIFI",
      "deviceTag": 1184882232,
      "platformType": "ANDROID",
      "batteryCharging": true,
      "timestamp": "2024-06-15T14:21:29.460Z",
      "activity": [
        {
          "timestampMs": "1718460089460",
          "activity": [
            { "type": "STILL", "confidence": 100 }
          ]
        }
      ]
    }
  ]
}

Now let's go through every field.

latitudeE7, longitudeE7​

Your coordinates, stored as integers in "E7" format. Divide by 10,000,000 (10⁷) to get actual decimal degrees.

So latitudeE7: 533690550 means latitude 53.3690550. And longitudeE7: 836950010 means longitude 83.6950010.

Why E7? Because integers are faster to process and compare than floating-point numbers, and seven decimal places gives you about 1.1 centimeter precision — way more than any phone GPS can actually deliver. It's an engineering decision that makes sense at Google's scale but makes your export files annoying to read by eye.

timestamp / timestampMs​

When the location was recorded. Google has used two different formats over the years:

• timestamp — ISO 8601 string like "2024-06-15T14:21:29.460Z". The newer format. Sometimes it's a Unix timestamp in seconds as a string, sometimes milliseconds as a string. Google is not consistent here.
• timestampMs — Unix timestamp in milliseconds, stored as a string (not a number, because JavaScript has integer precision issues at these magnitudes). "1718460089460" means June 15, 2024 at 14:21:29 UTC.

Older exports tend to have timestampMs. Newer ones have timestamp. Some entries have both.

accuracy​

Horizontal accuracy in meters. How confident the device was about the location reading. Lower is better.

• accuracy: 3-10 — GPS lock, outdoors, good conditions. Your reading is within a few meters of reality.
• accuracy: 15-50 — Mixed GPS/WiFi positioning. Good enough for street-level accuracy.
• accuracy: 100-200 — WiFi-only or cell tower positioning. You're probably in the right neighborhood.
• accuracy: 1000+ — Cell tower triangulation only. Could be off by a kilometer. Google still recorded it.

This field is important because it tells you how trustworthy each data point is. A point with accuracy of 18,000 meters is essentially useless for precise location tracking — but Google saved it anyway.

altitude​

Elevation above sea level in meters, as reported by the device. This comes from the phone's barometer or GPS altitude estimate.

GPS altitude is notoriously inaccurate — it can easily be off by 10-30 meters because GPS satellites are optimized for horizontal positioning. Phone barometers are more accurate for relative changes (like climbing stairs) but need calibration for absolute altitude.

Not every location entry has this field. It depends on whether the device's sensors provided it.

verticalAccuracy​

The estimated accuracy of the altitude reading, in meters. Same concept as accuracy but for the vertical dimension. If altitude is 150 and verticalAccuracy is 10, the true altitude is likely between 140 and 160 meters.

This field appears less frequently than altitude itself.

heading​

The direction the device was moving, in degrees from true north (0-360). 0 is north, 90 is east, 180 is south, 270 is west.

Only present when the device was actually moving and had a reliable heading reading. Static readings won't have this field.

velocity​

Speed in meters per second at the time of recording. Multiply by 3.6 to get km/h, or by 2.237 for mph.

So velocity: 15 means roughly 54 km/h — probably driving in a city. Like heading, this is only present when the device detected movement.

source​

Where the location reading came from. Values I've seen in the wild:

• "GPS" — Satellite positioning. The gold standard for outdoor locations.
• "WIFI" — WiFi access point triangulation. Common indoors.
• "CELL" — Cell tower triangulation. Least accurate but works everywhere with signal.
• "UNKNOWN" — Google doesn't know or won't say. Early exports tend to have a lot of these.

This tells you a lot about the quality of individual data points. A GPS reading with accuracy: 5 is very reliable. An UNKNOWN reading with accuracy: 18000 is barely useful.

deviceTag​

A numeric identifier for which device recorded this location. It's a hash, not a human-readable device name. If you used multiple phones over the years, you'll see different deviceTag values.

Google doesn't include a mapping from deviceTag to device names in the export. So if you want to know which device produced which points, you'd have to correlate based on time periods and cross-reference with your account's device history.

platformType​

The operating system of the device. Values include "ANDROID" and "IOS". Pretty self-explanatory.

batteryCharging​

A boolean (true/false) indicating whether the device was plugged in when the location was recorded. Might seem like an odd thing to track, but it's useful for Google's algorithms — a phone that's been charging at the same location for 8 hours is probably at home, not in transit.

activity​

This is the most complex field in Records.json. It's an array of activity recognition snapshots, each with its own timestamp and a list of probable activity types with confidence scores.

"activity": [
  {
    "timestampMs": "1718460089460",
    "activity": [
      { "type": "STILL", "confidence": 100 },
      { "type": "IN_VEHICLE", "confidence": 2 },
      { "type": "ON_FOOT", "confidence": 1 },
      { "type": "WALKING", "confidence": 1 }
    ]
  }
]

The type values come from Android's Activity Recognition API:

• STILL — Not moving
• ON_FOOT — Walking or running (generic)
• WALKING — Walking specifically
• RUNNING — Running specifically
• ON_BICYCLE — Cycling
• IN_VEHICLE — In a motorized vehicle (car, bus, train — it doesn't distinguish)
• IN_ROAD_VEHICLE — More specific: in a car/bus
• IN_RAIL_VEHICLE — On a train or subway
• TILTING — Device orientation changed
• UNKNOWN — Couldn't determine

The confidence is a percentage (0-100). Multiple activities can have non-zero confidence — the device is essentially saying "I'm 70% sure you're in a vehicle, 20% sure you're on foot, 10% no idea."

The activity timestamp is separate from the location timestamp because activity recognition runs on a different schedule than GPS readings. Sometimes you'll see activity data without a corresponding location update, or vice versa.

Format 2: Semantic Location History​

These are monthly JSON files, organized in folders by year: Semantic Location History/2024/2024_MARCH.json. Instead of raw GPS pings, these contain Google's interpreted version of your movements — place visits and activity segments.

The top-level structure:

{
  "timelineObjects": [
    { "activitySegment": { ... } },
    { "placeVisit": { ... } },
    { "activitySegment": { ... } },
    ...
  ]
}

The timelineObjects array alternates between two types: activity segments (you were moving) and place visits (you were stationary at a known location). Let's look at each.

activitySegment​

An activity segment represents a period of movement from one location to another.

{
  "activitySegment": {
    "startLocation": {
      "latitudeE7": 533407440,
      "longitudeE7": 837026901,
      "accuracyMetres": 25
    },
    "endLocation": {
      "latitudeE7": 533519706,
      "longitudeE7": 837596359,
      "accuracyMetres": 30
    },
    "duration": {
      "startTimestamp": "2024-03-15T07:05:14.222Z",
      "endTimestamp": "2024-03-15T07:11:13.214Z"
    },
    "distance": 3853,
    "confidence": "LOW",
    "activities": [
      { "activityType": "IN_VEHICLE", "probability": 0.0 },
      { "activityType": "WALKING", "probability": 0.0 },
      { "activityType": "CYCLING", "probability": 0.0 }
    ],
    "waypointPath": {
      "waypoints": [
        { "latE7": 533410301, "lngE7": 837051010 },
        { "latE7": 533519706, "lngE7": 837596359 }
      ],
      "source": "BACKFILLED",
      "distanceMeters": 4877.0,
      "travelMode": "DRIVE",
      "confidence": 1.0
    },
    "editConfirmationStatus": "NOT_CONFIRMED"
  }
}

startLocation / endLocation — Where the movement began and ended. Same E7 coordinate format as Records.json, with an accuracyMetres field.

duration — startTimestamp and endTimestamp define the time window. Can be ISO 8601 strings or millisecond timestamps (startTimestampMs), depending on export age.

distance — Total distance in meters, as estimated by Google.

confidence — How confident Google is about this segment. Values: HIGH, MEDIUM, LOW. A LOW confidence segment means Google is guessing about your movement. BACKFILLED segments (see waypointPath.source) are particularly unreliable — Google is reconstructing movement it didn't actually track in real time.

activities — An array of possible transportation modes with probability scores. The activityType values are the same as in Records.json (WALKING, CYCLING, IN_VEHICLE, etc.). The probability values are floats from 0.0 to 1.0. Annoyingly, you'll often see all probabilities at 0.0 — Google knows you moved but can't determine how.

waypointPath — The actual route taken, as a series of coordinate waypoints.

• waypoints — Array of intermediate positions (note: uses latE7/lngE7, not latitudeE7/longitudeE7 — because consistency).
• source — Where the path data came from. "BACKFILLED" means Google reconstructed it after the fact, not from real-time tracking.
• distanceMeters — Total path distance.
• travelMode — Google's best guess: "WALK", "DRIVE", "CYCLE", etc. Note these are different strings from the activityType values — "DRIVE" here vs. "IN_VEHICLE" in activities.
• confidence — A float from 0.0 to 1.0 for the travel mode classification.

editConfirmationStatus — Whether you manually confirmed or edited this segment in Google Maps. Values: "NOT_CONFIRMED", "CONFIRMED". Most entries will be NOT_CONFIRMED because most people never edited their Timeline.

placeVisit​

A place visit represents a period where you were stationary at a known location.

{
  "placeVisit": {
    "location": {
      "latitudeE7": 533690550,
      "longitudeE7": 836950010,
      "placeId": "ChIJN1t_tDeuEmsRUsoyG83frY4",
      "address": "123 Main Street, Anytown",
      "name": "Joe's Coffee",
      "semanticType": "TYPE_CAFE",
      "accuracyMetres": 15
    },
    "duration": {
      "startTimestamp": "2024-03-15T07:11:13.214Z",
      "endTimestamp": "2024-03-15T08:25:17.226Z"
    },
    "placeConfidence": "HIGH_CONFIDENCE",
    "otherCandidateLocations": [
      {
        "latitudeE7": 533691200,
        "longitudeE7": 836948800,
        "placeId": "ChIJABC...",
        "address": "125 Main Street, Anytown",
        "name": "Corner Bookshop",
        "semanticType": "TYPE_SHOPPING",
        "accuracyMetres": 20
      }
    ],
    "editConfirmationStatus": "NOT_CONFIRMED"
  }
}

location — The place Google thinks you visited.

• placeId — A Google Maps place identifier. Useful if you want to look up the place on Google Maps.
• address — Human-readable address. Not always present.
• name — Business or place name, if known. Not always present.
• semanticType — What kind of place it is: "TYPE_CAFE", "TYPE_HOME", "TYPE_WORK", "TYPE_SHOPPING", etc. Google's classification, not yours.
• accuracyMetres — How confident Google is about the specific spot within the location.

placeConfidence — Overall confidence that you actually visited this place. Values include "HIGH_CONFIDENCE", "MEDIUM_CONFIDENCE", "LOW_CONFIDENCE".

otherCandidateLocations — Alternative places Google considered. If you were at an intersection with three coffee shops, this array lists the ones Google didn't pick as the top candidate. Same structure as the main location object. Useful if Google guessed wrong — the real place might be in here.

This is important for importing: if the primary location has no coordinates (it happens), Dawarich falls back to the first candidate in otherCandidateLocations. Better than losing the data point entirely.

Format 3: Phone Takeout​

If you exported from the Google Maps app on your phone (Settings → Personal Content → Export Timeline data), you get a completely different JSON structure. The file is usually called location-history.json or Timeline.json.

This format has three main sections: semanticSegments, rawSignals, and userLocationProfile.

semanticSegments​

Similar concept to Semantic Location History's timelineObjects, but with different field names.

Timeline paths:

{
  "startTime": "2024-04-03T08:00:00.000+02:00",
  "endTime": "2024-04-03T10:00:00.000+02:00",
  "timelinePath": [
    {
      "point": "50.0506312°, 14.3439906°",
      "time": "2024-04-03T08:14:00.000+02:00"
    },
    {
      "point": "50.0506312°, 14.3439906°",
      "time": "2024-04-03T08:46:00.000+02:00"
    }
  ]
}

Notice the coordinate format here: "50.0506312°, 14.3439906°" — a string with degree symbols and a comma separator. Not E7 integers or decimal numbers. A formatted string with Unicode degree signs. This is a completely different convention from both Records.json and Semantic Location History.

Some timeline paths also include a durationMinutesOffsetFromStartTime on each point, which lets you calculate the exact timestamp for each waypoint relative to startTime.

Visits:

{
  "startTime": "2024-04-03T08:13:57.000+02:00",
  "endTime": "2024-04-03T20:10:18.000+02:00",
  "startTimeTimezoneUtcOffsetMinutes": 120,
  "endTimeTimezoneUtcOffsetMinutes": 120,
  "visit": {
    "hierarchyLevel": 0,
    "probability": 0.85,
    "topCandidate": {
      "placeId": "ChIJN1t_tDeuEmsRUsoyG83frY4",
      "semanticType": "UNKNOWN",
      "probability": 0.45,
      "placeLocation": {
        "latLng": "50.0506312°, 14.3439906°"
      }
    }
  }
}

startTimeTimezoneUtcOffsetMinutes — The timezone offset at the start of the visit, in minutes. 120 means UTC+2. This is actually useful — it's the first time Google includes timezone info in the export, which means you can reconstruct local time without guessing.

visit.hierarchyLevel — Nesting level for location hierarchy. 0 is the top level. I've never seen this go above 0 in practice.

visit.probability — Confidence that you actually visited this place (0.0 to 1.0).

visit.topCandidate — The most likely place, with its own probability score, placeId, and location in that string-with-degree-signs format.

Activities in semanticSegments follow the same pattern but with activity.start.latLng and activity.end.latLng coordinates, plus activity.topCandidate.type for transportation mode ("IN_PASSENGER_VEHICLE", "WALKING", "CYCLING", etc.).

rawSignals​

This is the stuff most people don't expect to find. Raw sensor data from your device.

Position readings:

{
  "position": {
    "LatLng": "48.833657°, 2.256223°",
    "accuracyMeters": 13,
    "altitudeMeters": 90.7,
    "source": "WIFI",
    "timestamp": "2024-06-06T11:44:37.000+01:00",
    "speedMetersPerSecond": 0.07
  }
}

These are raw GPS/WiFi position readings — similar to Records.json entries but in the phone takeout's string coordinate format. Note the field names here: accuracyMeters instead of accuracy, altitudeMeters instead of altitude, speedMetersPerSecond instead of velocity. Same data, different names. Classic Google.

WiFi scan data:

{
  "wifiScan": {
    "deliveryTime": "2024-06-06T11:44:37.000+01:00",
    "devicesRecords": [
      { "mac": 70474800562644, "rawRssi": -76 },
      { "mac": 193560579751752, "rawRssi": -50 }
    ]
  }
}

Yes, Google was recording every WiFi access point your phone could see, with signal strength (RSSI). The mac values are the MAC addresses of nearby routers, stored as integers. This is how WiFi-based positioning works — by matching the set of visible access points against Google's database of known AP locations.

This is probably the most surprising thing in the export for most people. You expected GPS coordinates, not Google to have a log of every WiFi network your phone has ever detected.

Activity recognition records:

{
  "activityRecord": {
    "probableActivities": [
      { "type": "STILL", "confidence": 0.96 },
      { "type": "IN_VEHICLE", "confidence": 0.01 },
      { "type": "ON_FOOT", "confidence": 0.01 },
      { "type": "WALKING", "confidence": 0.01 }
    ],
    "timestamp": "2024-04-26T20:54:38.000+02:00"
  }
}

Same activity types as Records.json, but confidence values are floats (0.0-1.0) instead of integers (0-100). Because why use the same scale twice.

userLocationProfile​

{
  "userLocationProfile": {
    "frequentPlaces": [
      {
        "placeId": "ChIJN1t...",
        "placeLocation": "50.0506312°, 14.3439906°",
        "label": "WORK"
      },
      {
        "placeId": "ChIJABC...",
        "placeLocation": "48.8336570°, 2.2562230°",
        "label": "HOME"
      }
    ]
  }
}

A list of places Google has identified as your frequent locations, with labels like "HOME" and "WORK". This is Google's model of your daily routine, neatly summarized. Most people have 2-5 entries here.

The coordinates here use the same degree-sign string format as the rest of the phone takeout.

The format detection problem​

So you've unzipped your export and you see some JSON files. Which format are they? Here's how to tell:

• Top-level key is "locations" with entries containing latitudeE7 → Records.json
• Top-level key is "timelineObjects" with activitySegment/placeVisit entries → Semantic Location History
• Top-level key is "semanticSegments" or "rawSignals" → Phone Takeout
• It's an array of objects with visit.topCandidate or activity.start → Phone Takeout (array variant)

Some ZIP exports contain all three. Some contain just one. The Google Takeout web interface tends to give you Records.json and Semantic Location History. The phone export gives you the phone takeout format. Sometimes you get a mix. I've seen exports where some months are in one format and other months in another.

What you can actually do with this data​

Staring at JSON isn't particularly useful. Here are some concrete things:

Visualize it​

All of these formats can be loaded into the Google Timeline Visualizer and rendered on an interactive map. It runs entirely in your browser — no server upload. For a Records.json with 600k+ points, expect 20-30 seconds of processing time.

Convert to standard formats​

Google's formats are proprietary. If you want your data in GPX, GeoJSON, or KML for use with hiking apps, mapping software, or GIS tools, the Google Timeline Converter handles all three formats.

Import into Dawarich​

This is the long-term play. Exporting your data preserves the past, but what about the location data you're generating right now? Google's Timeline was useful because it ran continuously in the background. Without it, that data just stops.

Dawarich imports all three Google formats — Records.json, Semantic Location History, and the phone takeout format. You bring your historical data, then set up continuous tracking going forward using OwnTracks or Overland on your phone. All the activity types, waypoints, accuracy data, and place visits get preserved.

The difference from Google? Your data stays on your server. No one's mining it for ads, no one's going to randomly deprecate the feature, and you get proper statistics, trip detection, and a map that actually works on the web — unlike Google's new mobile-only Timeline.

Either self-host it or use Dawarich Cloud if you don't want to manage a server. 7-day free trial, no credit card required.

Export your data now​

If you haven't done it yet: do it today. Google has already lost data for some users during the Timeline transition, and the longer you wait, the less data you'll have.

1. Google Takeout: Go to takeout.google.com, select "Location History (Timeline)", download the archive
2. Phone export: Google Maps → Settings → Personal Content → Export Timeline data
3. Unzip it, look at what you got
4. Import it somewhere you control, or at least keep the files backed up

Your location history is years of your life, compressed into JSON. It's worth understanding what's in there, and it's worth keeping.

So what are the actual options in 2026? I went through the most popular alternatives, ranked them by how well they replace what Google Timeline used to do, and tried to be honest about the trade-offs — including the ones that apply to my own project.

1. Dawarich​

Yeah, I'm putting my own project first. I built it, I'm biased, deal with it.

Dawarich is a self-hosted, open-source location history tracker. You run it on your own server (or use Dawarich Cloud if you don't want to bother with Docker), and it stores all your location data in your own database. Nobody else sees it.

What makes it a solid Timeline replacement:

• Imports all Google Timeline export formats — Records.json, Semantic Location History, phone exports, all of it
• Interactive map with your full history, filterable by date
• Trips (manual creation from your tracked points) and statistics (distance, countries visited, etc.)
• Supports GPX, GeoJSON, KML, and a bunch of other formats via the import/export system
• Real-time tracking from OwnTracks, Overland, or the Dawarich mobile apps
• Photo integration with Immich and PhotoPrism (it pulls geodata from your photo library, not the other way around)

The downsides: you need to host it yourself or pay for Cloud (starting at €50/yr for Lite, or €120/yr / €18/mo for the full plan, 7-day free trial). The self-hosted setup requires Docker and a bit of patience. It's not a "download from the App Store and forget" kind of thing.

If you're coming from Google and just want to see your exported data on a map without committing to anything, try the free Timeline Visualizer first. It runs entirely in your browser, nothing gets uploaded anywhere.

For a more detailed comparison: Dawarich vs Google Timeline.

2. OwnTracks​

OwnTracks is the OG of self-hosted location tracking. It's been around forever, it's open source, and it does one thing well: recording where you are and sending that data to your own server.

The good:

• Mature, well-tested mobile apps (iOS and Android)
• MQTT or HTTP — your choice
• Very lightweight on the server side
• Large community

The not-so-good:

• No built-in web UI for viewing your history. You get the data, but visualizing it is a separate problem.
• No import from Google Timeline out of the box
• The Recorder component stores data but doesn't do much with it
• If you want maps, statistics, trips — you need to build that yourself or use something else as a frontend

OwnTracks is great as a data source. Dawarich actually supports OwnTracks as a tracking app, so you can use OwnTracks on your phone and Dawarich as the backend with the nice UI. Best of both worlds. For more on how they compare: Dawarich vs OwnTracks.

3. Traccar​

Traccar started as a GPS fleet tracking platform, but a lot of self-hosters use it for personal location tracking too.

Strengths:

• Supports a ridiculous number of GPS devices and protocols
• Has a decent web interface with real-time tracking
• Self-hosted, open source
• Active development

Weaknesses:

• The UI is very much "fleet management" — it works, but it feels like you're monitoring delivery trucks
• No Google Timeline import
• History browsing is functional but bare-bones compared to what Timeline offered
• It's designed for tracking assets, not for "where have I been over the last 5 years"

If you already have Traccar running for other reasons, it can work as a Timeline replacement in a pinch. But it wasn't built for personal location history and it shows.

4. Strava / Komoot / Other Activity Trackers​

These aren't really Timeline alternatives, but I keep seeing them recommended, so let's be clear about what they are.

Strava and Komoot track your activities — runs, bike rides, hikes. They're excellent at that. But they don't do continuous background location tracking. You have to manually start and stop recording. Nobody is going to hit "Start Activity" every time they leave the house.

They're great for what they do. They're just not a replacement for always-on location history. If you only care about tracking workouts and outdoor activities, sure, use them. If you want to know where you had lunch three Tuesdays ago, they won't help.

For a deeper look at the Strava comparison specifically: Dawarich vs Strava.

5. Arc / Life360​

Arc was genuinely good — automatic trip detection, place recognition, nice UI. Then it kind of stalled. The developer is one person, and updates have been sporadic. It's iOS-only and there's no web version. Your data lives on your phone, which is exactly the problem Google created.

Life360 is a family tracking app that's been repeatedly caught selling precise user location data to data brokers. If your definition of "Timeline alternative" includes your family members seeing where you are at all times and third-party advertisers knowing too, go for it. Otherwise, probably not.

6. Google Timeline (what's left of it)​

I'm including this because technically it still exists. On your phone. With limited history. And no web access.

If you're fine with Google's new limitations — data on-device only, no desktop browsing, limited retention — then you don't need an alternative. But if you're reading a blog post titled "Best Google Timeline Alternatives," I'm guessing you're not fine with it.

The Honest Summary​

If you want the closest thing to what Google Timeline used to be — a complete history of everywhere you've been, on a map, accessible from a browser — there honestly aren't that many options. Most of the "alternatives" people recommend are either activity trackers, fleet management tools, or data collectors without a frontend.

Dawarich is the one I built because nothing else did what I needed. If your exported Google data is sitting in a folder somewhere gathering dust, at least run it through the Timeline Visualizer and see what you've got. It takes 30 seconds and everything stays in your browser.

Cheers!

How Hidden GPS Trackers Actually Work​

So, how can a little box keep such close tabs on an entire car? It’s not quite spy-movie magic. It's actually a lot like the package tracking you use for an online order, just shrunk down and designed to be secretive. The device really only has two jobs: figure out its location and then report that location to someone.

Think of it this way: the tracker is constantly listening for signals from the network of satellites orbiting Earth. By timing how long it takes to hear from at least four different satellites, it can triangulate its exact position—latitude, longitude, the works.

The Two Flavors of Trackers​

Once the tracker knows where it is, it has to share that information. This is where you see two distinct types of devices, and knowing the difference is crucial if you think you're being tracked.

• Active Trackers (Real-Time): These are the most common culprits in unauthorized tracking cases. They have a SIM card inside, just like a cell phone, and use cellular networks (like 4G or 5G) to send location data as it happens. This lets someone watch a vehicle's movement live on a map.

• Passive Trackers (Data Loggers): These are more like silent diarists. They record and store location data on the device itself but don't broadcast it in real time. To see the data, the person who planted the device has to physically get it back and download the files. They’re less immediate, but also much harder to find with electronic bug sweepers since they aren't constantly sending out a signal. You can check out our guide on tracking location history to see how this kind of data gets laid out.

Here's a key detail: an active tracker needs a relatively clear view of the sky to get a good satellite lock and a decent cell signal to phone home. This is a big clue—it’s why they’re often hidden on the outside of a vehicle or tucked away near a window.

Keeping the Lights On: Power Sources​

A tracker is just a paperweight without power. How it gets its juice is a major factor in where it can be hidden and how long it can operate.

• Battery-Powered: These are the simplest to deploy, often equipped with strong magnets to slap onto the underside of a car in seconds. The downside is battery life. Depending on the model and how frequently it pings its location, it might last for a few days, weeks, or maybe a couple of months.
• Hard-Wired: For a more permanent solution, these trackers are wired directly into the car's electrical system. This gives them a non-stop power source, allowing them to track a vehicle indefinitely. They are much tougher to find but require a bit more know-how to install.
• OBD-II Port: A popular middle ground. Some trackers plug right into a car's On-Board Diagnostics (OBD-II) port, usually located under the dashboard. It’s a simple plug-and-play install that provides continuous power, making it an incredibly common hiding spot.

The technology for this has become so cheap and accessible that the market is booming. The global GPS tracking device market was valued at USD 2.5 billion in 2023 and is projected to keep growing. You can get more details on this trend over at dataintelo.com.

Why Would Someone Plant a GPS Tracker, Anyway?​

Finding a hidden GPS tracker on your car sounds like a scene ripped straight from a spy thriller. But in reality, the reasons someone might plant one are all over the map—ranging from totally practical to downright illegal. Figuring out these motives is the first step to understanding if you should be concerned.

On one end, you have the completely legitimate, above-board uses. Think safety, efficiency, and keeping track of valuable stuff.

The Good: Legitimate and Legal Uses​

Not every tracker is a tool for spying. Far from it. Many are used for perfectly sensible reasons where everyone is in the loop.

For example, a business owner with a fleet of delivery vans isn't trying to be sneaky. They use GPS tracking to map out the best routes, keep an eye on fuel costs, and make sure drivers are sticking to their schedules. It’s a standard business tool, and drivers know it’s part of the job.

Then there’s the peace-of-mind factor for parents. It’s common for a parent to put a tracker in the car their newly licensed teenager is driving. It’s not about mistrust; it's about being able to help in an emergency or gently coach them on their driving habits. Some insurance companies even offer discounts if you agree to install a device that tracks your driving.

Here are a few common, legit scenarios:

• Fleet Management: Businesses track their vehicles to tighten up logistics and security.
• Asset Protection: Owners of classic cars or expensive construction gear use trackers to recover them if they're stolen.
• Parental Monitoring: Parents keep a virtual eye on young drivers for safety.

In these cases, the person planting the tracker almost always owns the vehicle or has a legal right to monitor it. It’s all about protecting property or people, not creeping on their privacy.

The Bad and The Ugly: Unethical and Illegal Motivations​

This is where the story takes a much darker turn. A hidden GPS tracker can easily be weaponized for harassment, control, and stalking. The same tiny device that helps find a stolen piece of equipment can be used to track an ex-partner’s every move, which is incredibly dangerous.

And unfortunately, it happens more than you'd think. A suspicious partner might secretly plant a tracker on their significant other's car out of distrust. In even more terrifying situations, stalkers and abusers use them to maintain control and intimidate their victims.

Let’s be crystal clear: Placing a tracker on a vehicle you don’t own, without the owner's consent, is illegal in most places. It can result in serious criminal charges like stalking, harassment, and invasion of privacy.

These devices have become cheaper and easier to get, which only adds to the problem. The global market for GPS locators—which includes these hidden trackers—is projected to hit a staggering $2.098 billion by 2025. That growth is driven by both the legitimate uses and, sadly, these more sinister ones. You can dig deeper into these market trends and their drivers if you're curious.

By understanding both sides of the coin, you can get a better read on your own situation. If you share a vehicle with a family member or use a company car, it’s worth a simple conversation. But if your gut tells you something more malicious is going on, trusting that instinct is the first step toward protecting yourself.

Navigating the Legal Maze of GPS Tracking​

Figuring out the laws around hidden GPS trackers can feel like trying to read a map in the dark. The rules are murky, and they change dramatically from one place to the next. While this isn't official legal advice, think of it as a practical field guide to help you understand the core principles and spot when someone's crossing a serious line.

When it comes to GPS tracking laws, most of it boils down to a single, surprisingly simple question: Who owns the car?

If the vehicle is yours, you generally have the right to know where it is. That's the simple part and the basis for most legitimate uses. But the moment you start tracking a car you don't own—or even one you share ownership of—things get messy, fast. That’s when a legal concept called "reasonable expectation of privacy" comes into play, and it changes everything.

When Tracking Is Usually in the Clear​

Let's start with the straightforward scenarios. There are a handful of situations where using a GPS tracker is typically okay, mainly because the person doing the tracking has a clear ownership or guardianship stake in the vehicle.

• Tracking Your Own Car: Slapping a tracker on a vehicle you own outright is almost always legal. People do this all the time for theft recovery or even just to find their car in a massive parking garage.
• Keeping Tabs on Your Teen Driver: If you're a parent or legal guardian, you can generally track a car you own that's being driven by your child, as long as they're under 18.
• Monitoring Company Vehicles: Businesses can legally track company-owned cars used by employees. This is a common practice for managing fleets of vehicles, and employees usually agree to it as part of their job.

In these cases, there's no real violation of that "reasonable expectation of privacy" we talked about. The owner is just keeping an eye on their own property.

Red Flags: When Tracking Is Almost Always Illegal​

Now, let's look at the other side of the coin. Using a hidden GPS tracker turns into a serious legal nightmare when it’s done without consent and tramples all over someone's privacy. Planting a device on a car you don't own is where you step into dangerous territory.

Here’s when it's pretty much always illegal:

• Tracking a Spouse or Ex-Partner: Secretly sticking a tracker on your partner's car, especially if you aren't a co-owner, is a massive violation. This is the kind of thing that leads to stalking and harassment charges.
• Putting a Tracker on a Stranger’s Car: This one’s a no-brainer. It's straight-up illegal surveillance, period.
• Tracking an Employee’s Personal Car: Even if an employee uses their own car for work-related errands, their boss can't legally track it without getting clear, written permission first.

The bottom line is this: If you don't own the vehicle and you don't have the driver's explicit permission, planting a tracker is very likely against the law. The penalties can be severe, ranging from huge fines to actual jail time, depending on your state's laws.

The sheer growth of the GPS industry shows just how common this tech has become—for both good and ill. The market for GPS tracking devices in the United States alone was valued at USD 2.26 billion in 2024 and is on track to more than double by 2033. While legitimate uses in logistics and safety are driving this boom, it also means these tiny devices are easier than ever for people to get their hands on for the wrong reasons. You can dig into more stats about the booming U.S. GPS market to see the full picture.

Knowing these basic legal boundaries is your first and best defense. It helps you recognize the signs of illegal surveillance and gives you the confidence to take action to protect your privacy.

How to Physically Search Your Car for a Tracker​

Alright, it’s time to get your hands a little dirty. If you have that nagging feeling that someone might have planted a GPS tracker on your car, a thorough physical search is your most direct and effective first step. This isn't about just glancing around; we're going to approach this systematically, like a detective sweeping a scene, so you can be confident you've checked all the likely spots.

Before you start, you'll want to grab a couple of simple tools that will make a world of difference: a bright flashlight (your phone works in a pinch, but a real flashlight is way better) and an extendable inspection mirror. These will be your best friends for peering into all the dark, awkward corners where these devices love to hide.

Starting With The Exterior​

Most trackers, especially the magnetic, battery-powered kind, get slapped on the outside of a vehicle. Why? Because it's fast and easy. The person planting it probably only had a few seconds, so they would have gone for the most accessible spots.

Let's begin with the most common exterior hiding places:

• The Undercarriage: This is prime real estate for a magnetic tracker. Get on the ground and use your flashlight to scan the entire frame of your car. Pay extra close attention to any flat metal surfaces where a magnetic box could easily latch on.
• Inside the Wheel Wells: Crouch down and take a good look inside each of the four wheel wells. Run your hand along the plastic lining to feel for any small, unfamiliar boxes. A tracker tucked away here is out of sight but can still get a clear enough signal from GPS satellites.
• Behind the Bumpers: Both your front and rear bumpers have all sorts of nooks and crannies that are perfect for stashing a small device. The plastic often has enough give to let you gently pull it back and peek behind. Be on the lookout for any little black boxes or odd wires that clearly don't belong.

This infographic breaks down who can legally place a tracker on a vehicle and, more importantly, when it crosses a serious legal line.

As you can see, an owner has every right to track their own property, but that right absolutely does not extend to monitoring an ex-partner—an action that almost always falls into illegal territory.

Moving To The Car's Interior​

If you've scoured the outside and come up empty, it's time to move inside. Placing a tracker inside is less common for the quick "slap-and-go" magnetic types, but it's a go-to spot for devices that need to be hardwired to a constant power source.

Here’s where you should focus your attention inside the car:

• Under the Dashboard: This is the #1 spot for an OBD-II port tracker. This port, which is usually found just below your steering wheel, provides continuous power and is incredibly easy to access. Look for any small device plugged into it that isn't a diagnostic tool your mechanic just used.
• Beneath the Seats: Slide your front seats all the way forward, then all the way back. Use your flashlight to inspect every inch of the floor and the seat mechanisms underneath. Feel along the metal tracks and under the seat fabric for any weird lumps or small boxes held in place with tape or velcro.
• The Trunk: Don't forget the trunk! Pop it open and check inside the spare tire well, pull back the carpet lining on the sides, and look in any small storage compartments. It's an easy place to tuck a device where it can go unnoticed for weeks or even months.

A key thing to remember is what you're actually looking for. Most hidden GPS trackers are small, plain black boxes. They are designed to be missed, so they won’t have flashy logos or blinking lights. You’re searching for something that just looks out of place—an object that isn’t a factory part of your car.

To make this easier, here's a quick checklist of the most common hiding spots to keep handy as you do your search.

Checklist of Common Hiding Spots for GPS Trackers​

Going through these spots methodically gives you the best chance of finding anything that shouldn't be there.

Other Less Common Hiding Spots​

If you've checked all the usual suspects and still feel like something's wrong, there are a few other, less common places to look. These spots take more effort to get to, which is why they aren't the first choice for most people.

Consider checking:

• Behind the glove box: Sometimes a tracker can be tucked away behind the glove compartment itself.
• Inside a seat cushion: This is pretty rare, but a very determined person could slip a tiny tracker inside a zippered seat cover.
• Within the center console: Pop out any removable trays or compartments in your car's center console and look underneath.

Taking the time to perform this physical search is the single most effective thing you can do to find a hidden GPS tracker. It costs you nothing but a bit of time and can give you back your peace of mind.

Using Tech to Detect Hidden Tracking Devices​

Sometimes, no matter how thoroughly you search, you just can't shake that feeling. As hidden GPS trackers get smaller and more sophisticated, they can be slipped into spots your eyes and hands will simply never find. When you need that extra layer of certainty, it’s time to bring in technology that can "see" the invisible.

These gadgets work by sniffing out the invisible signals that active, real-time trackers transmit. Think of it like a radio tuning into a specific station—if a tracker is "broadcasting" its whereabouts, these devices are designed to pick up on it loud and clear.

Hunting for Signals With RF Detectors​

Your best bet for a DIY electronic sweep is an RF (Radio Frequency) detector, often called a bug sweeper. This is a handheld device that scans for the radio waves that active trackers use to communicate over cellular networks.

Picture the tracker sending out a tiny text message with its coordinates every minute or so. An RF detector is essentially a specialized antenna that beeps or lights up when it "hears" that signal go out. You just sweep the detector slowly around your car, and as you get closer to a transmitting device, the alert on the detector gets stronger.

To get the most out of it:

• Take your time: You need to move slowly to give the detector a chance to catch signals that might only be sent out intermittently.
• Kill the noise: Your phone, the car's Bluetooth system, and any Wi-Fi hotspots can all trigger false alarms. Shut them all off before you start.
• Get the car moving: Some trackers are designed to only transmit when the vehicle is in motion. If you can do it safely, have a friend drive slowly around an empty parking lot while you scan.

Can Your Smartphone Find a Hidden GPS Tracker?​

You've probably seen apps in the app store that claim to turn your phone into a high-tech spy-finding machine. It's a great concept, but in reality, their effectiveness is extremely limited. Most of these apps are just glorified scanners for nearby Wi-Fi or Bluetooth signals.

That approach has a couple of huge flaws:

• They’ll pick up every single Bluetooth device in the area—your headphones, the car next to you, your smartwatch. It’s a mess of false positives.
• Most real-time GPS trackers use cellular networks (4G/5G) to send their location, not Bluetooth. Your phone's hardware just isn't built to detect those kinds of transmissions like a dedicated RF detector can.
• And, of course, they are completely useless against passive loggers, which don't transmit any signal at all.

So, while an app might get lucky and find a very specific type of Bluetooth-based tag, it's nowhere near a reliable tool for finding the most common hidden GPS trackers.

Don't mistake convenience for effectiveness. A smartphone app is easy to download, but it can give you a dangerous false sense of security by missing the most common types of tracking devices.

When to Call in the Professionals​

Let's say you've done a full physical search and run an electronic sweep, but you're still convinced you're being followed. At this point, it might be time to call in the pros. A Technical Surveillance Counter-Measures (TSCM) expert is a specialist with sophisticated, professional-grade equipment that's light-years beyond what you can buy online.

A professional TSCM sweep is the most surefire option you have. These experts can find everything from hard-wired devices and passive loggers to advanced trackers designed to evade basic detection. It's an investment, for sure, but if your safety is genuinely at risk, it's the only way to be absolutely certain your vehicle is clean.

For those more interested in managing their own location data securely, you can see how a location history visualizer offers a different kind of peace of mind.

What to Do If You Find a Hidden Tracker​

https://www.youtube.com/embed/msOdtBYpCLQ

Finding a hidden tracker on your car is a gut-wrenching moment. It feels like a total violation of your privacy, and your first reaction might be to rip it off and smash it to pieces. It's a totally understandable impulse, but hold on for just a second.

Before you do anything else, take a deep breath. What you do in these next few moments is critical, especially if this ends up involving the police.

Your first job is to play detective. Grab your phone and document everything. Take a bunch of clear photos and videos of the tracker from every possible angle. Make sure you get wide shots that show exactly where it was hidden on your car. This context is gold.

First, Assess Your Safety​

Once you’ve got your evidence, it's time to think about your personal safety. This is priority number one. Ask yourself, who would do this? Is it an ex? A current partner you're worried about? Or a complete stranger?

Your gut feeling here will tell you what to do next.

If you have even the slightest suspicion that you're in danger, do not remove the device. I know it feels wrong to leave it there, but doing so keeps the person who planted it in the dark. They won't know you've found it, which buys you precious time to call the police and figure out a safety plan. This is about being smart and strategic, not just reacting.

But if you’re pretty sure it’s something less sinister—like a misunderstanding with a family member or maybe a leftover device from the car's previous owner—then taking it off yourself might be the way to go.

Crucial Takeaway: Let your safety guide your actions. If stalking, harassment, or domestic violence is a possibility, leave the tracker right where it is and call the police. That device is now evidence in a criminal investigation.

To Remove or to Report?​

So, what's the right call—yank it off yourself or get the authorities involved? It really boils down to your specific situation and what you feel comfortable with.

Here’s a simple way to break it down:

1. Battery-Powered Trackers: If you're confident there’s no immediate threat, you can usually remove these yourself. They’re typically just stuck on with a magnet or some heavy-duty tape. Put on a pair of gloves, gently detach it, and see if you can find a power button to shut it off. Then, stick it somewhere safe.
2. Hard-Wired Trackers: Never try to remove a hard-wired tracker on your own. These are hooked directly into your car’s electrical system. Fiddling with those wires is a great way to cause serious and expensive damage to your vehicle. If you spot one of these, take your car straight to a mechanic you trust or an auto electronics shop to have it removed safely by a pro.
3. When to Call the Cops: If you feel like you're being stalked, harassed, or illegally monitored in any way, your first call should be to law enforcement. Show them the photos and videos you took. They’ll tell you whether to leave the device for them to collect as evidence or if you should go ahead and have it removed.

Discovering a hidden GPS tracker is an unnerving experience, no doubt. But by documenting the evidence and putting your safety first, you can take back control. You turn a moment of fear into one of calm, calculated action.

Frequently Asked Questions About Hidden GPS Trackers​

Alright, so you've swept your car and maybe even found a tracker. It's totally normal to still have a bunch of questions bouncing around. Let's walk through some of the most common ones people ask to help you feel more confident and in control.

Can a Hidden GPS Tracker Record Conversations?​

This is a huge concern for many, and the good news is, almost certainly no. Your typical hidden GPS tracker is a one-trick pony; its only job is to track location coordinates. It simply doesn't have the gear, like a microphone or the right software, to record what you're saying.

That said, you should know that sophisticated (and very pricey) surveillance bugs do exist that can bundle audio recording with GPS tracking. These are pretty rare for everyday situations, but if you have a serious reason to be worried, it’s another good argument for calling in a professional TSCM team.

How Long Does a Tracker's Battery Last?​

Honestly, it's all over the map. For a portable, battery-powered tracker, the lifespan really depends on the specific device and how it's configured. A cheap, basic model might only last a week or two before the battery dies.

On the other hand, some of the more advanced trackers can last for months. They do this by going into a "deep sleep" mode and only waking up to report their location once or twice a day, which saves a ton of power.

Keep in mind, if a tracker is wired directly into your car's power—like one plugged into the OBD-II port—it's got a constant supply of juice. As long as your car battery works, so does the tracker.

Do Police Need a Warrant to Use a Tracker?​

Yes, absolutely. In most places, law enforcement has to get a warrant from a judge before they can legally slap a GPS tracker on someone's vehicle. This comes down to the Fourth Amendment, which protects us from unreasonable searches. Attaching a tracker is legally considered a "search."

To get that warrant, they have to show a judge there's probable cause to believe the car is involved in a crime. If they skip this step, any evidence they collect using that tracker can be thrown out in court.

Have more questions? We’ve got you covered. You can find more answers to common concerns in our detailed Dawarich FAQ section.

If you're looking for a safe way to map your own life's journey without giving up your privacy, check out Dawarich. It's a privacy-first app that automatically builds your personal location journal, putting you in complete control of your data. See how it works at https://dawarich.app.

Some are built for hardcore athletes chasing personal bests, while others are designed for backcountry hikers who need detailed offline topographic maps. A few are social platforms for sharing your routes with a community, and a select group focuses on quietly and privately journaling your life's path without broadcasting your location to the world. It’s easy to get stuck here, downloading three or four apps before landing on one that actually fits your needs.

This guide is here to cut through that noise. We're going to dive into 12 of the best apps available, breaking down what they do best, who they're for, and any potential drawbacks you should know about. Think of this as a practical, straightforward comparison to help you find the app that matches your walking style. We'll look at everything from social fitness giants like Strava to powerful navigation tools like Gaia GPS and privacy-first journaling apps like Dawarich.

Each review will include key feature summaries, pros and cons, pricing notes, and clear screenshots so you know what you're getting into. My goal is to give you all the information you need to make a confident choice, so you can spend less time searching in the app store and more time enjoying your walk. Let's get started.

1. Dawarich​

Dawarich takes a really different approach from most of the apps on this list. It’s an automatic, privacy-first tool for location journaling. Instead of manually starting and stopping a tracker for every walk, Dawarich works silently in the background, building a comprehensive, searchable map of your life's movements. This makes it an exceptional tool not just for planned hikes but for spontaneously capturing every neighborhood stroll, commute, and journey, turning your daily travels into a rich, private timeline.

Its core strength is its "set it and forget it" functionality combined with a powerful suite of visualization tools. Once set up, it automatically logs your routes and places visited. You can then explore this data through interactive maps, detailed trip summaries showing distance and duration, and even a "Scratch Map" that visually fills in as you explore new areas. It makes for an incredible app for mapping walks and discovering just how much ground you cover over time.

Why Dawarich Stands Out​

What truly sets Dawarich apart is its unwavering commitment to user privacy and data ownership. While many apps trade your location data for services, Dawarich is built on a foundation of trust.

• Privacy-First Architecture: All your data is encrypted both in transit (SSL/TLS) and at rest (LUKS). With servers based in Europe, it is fully GDPR compliant, giving you peace of mind that your personal location history remains yours alone.
• Total Data Control: You can easily import existing location data (including from Google Timeline) and export your entire history at any time. This portability ensures you are never locked into the platform.
• Flexible Deployment Options: You can opt for the convenient Dawarich Cloud plan, which includes an official iOS app and managed backups, or choose to self-host the platform for free if you have the technical skills and desire complete control over your server environment.

Pricing and Platform Availability​

• Dawarich Cloud: The managed service costs €7.50/month or €90 when billed annually. It includes a 7-day free trial (no credit card required) and generous limits of up to 10 million data points.
• Self-Hosted: Free for users who prefer to manage their own server and installation.
• Platforms: The managed Cloud plan includes an official iOS app. Android users can still use the platform effectively via third-party apps that feed data to their Dawarich instance.

Best For: Privacy-conscious individuals, travelers, and lifeloggers who want a detailed and automatic visual record of their movements without compromising their data.

Visit Dawarich

2. AllTrails​

AllTrails is a behemoth in the world of outdoor navigation, and for good reason. Think of it as the Yelp or TripAdvisor for hiking and walking trails. Its massive, crowd-sourced database is its biggest strength, offering over 450,000 curated routes globally, though its coverage is particularly dense in the United States. If you’re looking for a reliable app for mapping walks that someone else has already vetted, this is often the best place to start.

The platform shines with its community-driven content. Each trail page includes recent reviews, user-submitted photos, difficulty ratings, and elevation profiles, giving you a real-world preview of what to expect. This is incredibly helpful for finding routes that match your fitness level and for checking current trail conditions before you head out.

Core Features & User Experience​

The free version is great for discovery, but the real power for serious walkers comes with the paid tiers. AllTrails+ unlocks essentials like offline map downloads (a must-have for areas with spotty cell service) and wrong-turn alerts. The user interface is straightforward and beginner-friendly, making it easy to filter trails by length, difficulty, or even dog-friendliness.

Best For: Hikers and walkers who prioritize trail discovery and community-sourced reviews, especially within the U.S.

• Website: https://www.alltrails.com
• Pricing: Free basic plan. AllTrails+ is around $35.99/year and offers offline maps and navigation alerts. The Peak tier adds more advanced planning tools for a higher price. Keep an eye out for frequent promotions and discounts on the annual membership.
• Pros: Enormous database of trails with rich user reviews, very easy for beginners to pick up and use.
• Cons: Key safety features like offline maps are behind a paywall. The shifting of features between membership tiers can sometimes be confusing for long-time users.

3. Strava​

While often associated with competitive cycling and running, Strava has evolved into a powerful and socially-driven platform for anyone mapping a walk. Its biggest draw is the global "heatmap," which visualizes the most popular routes taken by millions of users. This feature is fantastic for discovering safe, well-trodden, and scenic walking paths in your area or a new city, taking the guesswork out of your planning.

Strava functions as both a route planner and a fitness-focused social network. You can track your walks, analyze your performance stats like pace and distance, and share your activities with friends for a bit of friendly encouragement or competition. This social element adds a layer of motivation that many other mapping-only apps lack, making it a great choice if community is important to you. For a deeper look at how its features compare to other journaling apps, you can read this breakdown of Strava.

Core Features & User Experience​

Strava’s route builder is a standout feature, allowing you to draw your own path or get AI-assisted suggestions based on community data. The free version covers basic tracking and sharing, but a subscription unlocks advanced route planning, detailed segment analysis, and Beacon, a live-tracking safety feature. Its seamless integration with devices from Garmin, Apple Watch, and others makes it incredibly easy to sync your walks without manual data entry.

Best For: Walkers who are motivated by data and community, and who want to combine route mapping with a detailed fitness log.

• Website: https://www.strava.com
• Pricing: Free plan with core tracking features. The premium subscription, which unlocks route planning and advanced analytics, is around $79.99/year, though pricing can vary by region.
• Pros: Excellent route discovery through global heatmaps, strong social and community features, and seamless integration with major wearables.
• Cons: Key route planning features are behind a paywall. The interface can feel a bit training-centric if you only want a simple app for mapping walks.

4. MapMyWalk (Under Armour)​

Part of the Under Armour suite of fitness apps, MapMyWalk is laser-focused on the activity of walking, from casual city strolls to more structured training. While other platforms bundle walking into a broader category of outdoor activities, this app for mapping walks dedicates its entire workflow to it. This focus makes it an excellent choice for users who primarily stick to pavement and parks and want features tailored specifically to that experience.

Its biggest draw is the integration with a massive fitness ecosystem. If you’re already using other Under Armour apps like MyFitnessPal or a UA connected shoe, MapMyWalk fits in seamlessly. It also offers a huge library of user-created routes, particularly in urban and suburban areas, making it easy to find a new path right outside your door.

Core Features & User Experience​

The app provides all the core functionality you'd expect: GPS tracking, distance, pace, and calorie burn. Where it stands out is in its motivational tools, such as audio coaching that provides real-time feedback during your walk and community challenges that encourage you to hit new goals. The MVP (premium) subscription unlocks training plans, live tracking so friends can follow your route, and more advanced data analysis. Understanding how to track your location effectively is key to using these features, and you can learn more about location tracking here.

Best For: Urban and suburban walkers who want a fitness-focused experience with strong motivational tools and community challenges.

• Website: https://www.mapmywalk.com
• Pricing: Free with ads. The MVP premium subscription is around $5.99/month or $29.99/year and removes ads while unlocking training plans and live tracking.
• Pros: Walking-specific features and challenges, deep integration with the Under Armour fitness ecosystem, and a large library of urban routes.
• Cons: The website feels a bit sparse until you log in. Some key pricing and feature details are clearer on the app store listings than on the main site.

5. Komoot​

Komoot excels as a powerful route planner and navigation tool, especially popular in Europe. It’s designed for adventurers who want to meticulously plan their journeys, whether it’s a short city walk or a multi-day trek. This app for mapping walks shines with its detailed surface and elevation data, allowing you to know exactly what kind of terrain you’ll be covering before you even step outside.

Unlike subscription-first models, Komoot offers a unique pricing structure. You get one region for free to test its full capabilities, including turn-by-turn voice navigation and offline map downloads. After that, you can purchase individual regions or entire country packs with a one-time payment, which is a fantastic value if you tend to explore a specific area.

Core Features & User Experience​

The platform's route planner is its standout feature, available on both the web and its mobile app. You can create custom routes that snap to known paths and trails, with the app providing detailed information on the waytypes (like pavement, hiking path, or cycleway) you’ll encounter. Its turn-by-turn navigation is clear and reliable, making it feel like a GPS for your feet.

Best For: Planners who love crafting their own routes and walkers who primarily explore one geographic region, seeking excellent value for offline navigation.

• Website: https://www.komoot.com
• Pricing: Free region to start. One-time purchases for single regions (from $3.99), region bundles, or a complete World Pack (around $29.99). A Premium subscription (around $59.99/year) unlocks advanced features like live tracking and multi-day planning.
• Pros: Great value with one-time map purchases, reliable offline navigation with clear voice instructions, powerful and easy-to-use route planners.
• Cons: Some advanced planning features are locked behind the annual Premium subscription, and regional pricing can vary by currency and app store.

6. Gaia GPS​

For walkers who often venture beyond well-trodden paths into national parks and backcountry areas, Gaia GPS is a professional-grade navigation powerhouse. It moves beyond simple trail finding, offering a vast library of specialized map layers that cater to serious outdoor enthusiasts. If your walks frequently take you into areas with unreliable cell service, this app for mapping walks provides the robust, off-grid performance you need.

The platform's biggest strength is its unparalleled collection of over 250 map sources. You can overlay topographic maps, satellite imagery, public land boundaries, and even real-time weather data to plan your route with incredible detail. It's the kind of tool that empowers you to create your own walks, mark important waypoints, and confidently navigate complex terrain far from any marked trail.

Core Features & User Experience​

Gaia GPS offers route recording, waypoint marking, and detailed elevation profiling, all of which sync seamlessly between its web and mobile platforms. The free version provides a taste, but the Premium membership is where the essential features live, most notably the ability to download entire map regions for offline use. The interface is more technical than some competitors, but it’s clean and highly functional once you’re familiar with its layout.

Best For: Serious hikers, backcountry walkers, and anyone who needs detailed, multi-layered maps for off-grid navigation, particularly in the U.S.

• Website: https://www.gaiagps.com
• Pricing: Free basic plan. Gaia GPS Premium is around $39.99/year for offline maps and the full map catalog. It can also be bundled with an Outside+ membership, which provides access to additional content and learning resources.
• Pros: Enormous catalog of specialized U.S. map layers, excellent and reliable offline performance.
• Cons: Some users have noted price increases over the years, and the account system can be confusing as it is sometimes handled through a parent Outside account.

7. CalTopo​

If you think of other apps as guidebooks, CalTopo is the professional cartographer’s toolkit. It’s an incredibly powerful web and mobile platform designed for serious backcountry planning, favored by search-and-rescue teams, wildland firefighters, and meticulous route planners. While it might be overkill for a simple neighborhood stroll, it’s an unparalleled app for mapping walks in complex or remote terrain where safety is paramount.

CalTopo’s strength lies in its layers. You can overlay detailed data like slope angle shading (critical for avalanche safety), public land ownership, weather forecasts, and various satellite imagery sources. Its web-based route-drawing tools are robust, allowing you to precisely plan a trip, analyze its elevation profile, and then seamlessly sync it to your phone for offline use.

Core Features & User Experience​

The interface is dense and technical, reflecting its professional-grade capabilities. There is a steeper learning curve compared to more consumer-focused apps, but the payoff is immense control over your map creation. You can easily draw routes, place waypoints, and print high-quality physical maps for a backup. The free version is surprisingly capable for online planning, but a subscription is necessary to unlock its full potential, including most offline map layers.

Best For: Experienced hikers, backcountry explorers, and anyone who needs detailed terrain analysis and safety-planning tools for their walks.

• Website: https://caltopo.com
• Pricing: Free for basic online use. Paid plans start around $50/year for individuals, unlocking essential features like offline layers and advanced planning tools.
• Pros: Exceptional terrain analysis and safety-planning layers, seamless web-to-mobile workflow for detailed planning, and powerful printing capabilities for physical backups.
• Cons: The user interface can be intimidating for beginners, and key offline features and advanced layers are locked behind a paid subscription.

8. Google Maps​

It might seem obvious, but no list of mapping apps is complete without the default champion, Google Maps. While not a dedicated trail app, it’s arguably the most powerful and accessible tool for urban and suburban walks. Its greatest strength is its unparalleled database of roads, sidewalks, and points of interest (POIs), making it an indispensable app for mapping walks in populated areas. If you need to plan a route from your hotel to a cafe through city streets, this is your go-to.

Google’s platform excels at seamless, everyday navigation. Its step-by-step walking directions are best-in-class, often using landmarks for guidance ("turn right after the Starbucks"), and the Live View AR feature, which overlays directions onto your camera's view, feels like something from the future. It’s also a fantastic discovery tool, letting you find parks, coffee shops, or historical markers to build a walk around, complete with photos and recent reviews.

Core Features & User Experience​

The user experience is familiar to almost everyone, with a clean interface that works flawlessly across web and mobile. Planning a multi-stop walk is simple, and the ability to share your route or live location with friends is a great safety feature. While its offline capabilities for walking can be less detailed than for driving, downloading city maps is a lifesaver when traveling. The platform's integration with other Google services also means your walking plans can sync with your calendar. For those who use tools like Dawarich, the ability to view your private location history on a familiar map interface is a major plus; you can learn more about its map features on their website.

Best For: Urban explorers and anyone needing reliable, free, and feature-rich navigation for walks in cities and towns.

• Website: https://maps.google.com
• Pricing: Completely free for personal use.
• Pros: Unmatched POI data and place search, excellent step-by-step directions with AR, seamlessly syncs across all your devices.
• Cons: Not designed for off-road trails, offline walking data can be inconsistent, and some advanced smartwatch features are Android-exclusive.

9. Apple Maps​

For those already invested in the Apple ecosystem, the built-in Maps app has quietly evolved into a surprisingly capable tool for mapping walks, especially for casual urban exploration and U.S. national park hikes. Instead of needing a third-party download, Apple provides a robust, free, and privacy-focused solution right on your iPhone, iPad, and Apple Watch. Its biggest advantage is the seamless integration across these devices.

The platform has made significant strides, now offering detailed U.S. topographic maps and curated trail guides for national parks, which you can browse directly within the app. For city walkers, features like Look Around and immersive augmented reality (AR) walking directions in select cities offer a futuristic way to navigate. You can also create your own multi-stop walking routes on your Mac or iPad and they will automatically sync to your iPhone and Apple Watch for offline use.

Core Features & User Experience​

The user experience is exactly what you'd expect from Apple: clean, intuitive, and deeply integrated. Planning a walk is straightforward, and the ability to have turn-by-turn directions on your Apple Watch is a fantastic, hands-free benefit. The custom route creation is simple, allowing you to plot points and save the journey for later. As it's a native app, it doesn't drain your battery as aggressively as some other GPS-heavy applications might.

Best For: Apple users looking for a free, private, and seamlessly integrated solution for city walks and exploring trails in U.S. national parks.

• Website: https://www.apple.com/maps
• Pricing: Completely free. All features are included with Apple devices and there are no premium tiers or advertisements.
• Pros: Excellent integration with Apple Watch and iOS, strong U.S. park guides, completely free and privacy-focused.
• Cons: Best features are exclusive to the Apple ecosystem. Advanced AR and topographic map details are not yet globally available.

10. Footpath Route Planner​

Footpath Route Planner stands out for its simplicity and laser focus on one specific task: creating custom walking routes quickly and intuitively. Instead of browsing a massive library of pre-made trails, this app for mapping walks empowers you to draw your own path directly on the map with your finger. Its "snap-to-path" technology intelligently aligns your freehand drawing to actual roads, trails, and footpaths, making route creation a breeze.

This approach is perfect for planning a specific urban walk, a run around your neighborhood, or a custom trail loop in a local park where you already know the area but want a precise distance and navigation. Once your route is set, the app provides turn-by-turn voice navigation and even lets you generate printable cue sheets, a nice touch for those who prefer a physical backup.

Core Features & User Experience​

The user experience is clean and centered entirely around the route-drawing feature. You can analyze your created path for elevation and slope, which is great for planning workout intensity. Routes can be saved into folders for easy organization and exported for use on other devices. The app works seamlessly across iOS, Android, and a web interface, so you can plan on a larger screen and sync to your phone for the actual walk.

Best For: Walkers and runners who want to quickly create and follow their own precise, custom-made routes in urban or familiar areas.

• Website: https://footpathapp.com
• Pricing: Free to plan routes. The Footpath Elite subscription unlocks turn-by-turn navigation, offline maps, and premium map styles. Pricing is shown in-app but is generally affordable, with a 7-day free trial available.
• Pros: Incredibly fast and intuitive finger-drawing route creation, focused and easy-to-use interface, cross-platform support.
• Cons: Not designed for trail discovery; has a much smaller community and fewer shared routes compared to platforms like AllTrails.

11. onX Backcountry​

Originally known for its hunting and off-roading maps, onX has brought its powerful mapping engine to the hiking world with onX Backcountry. This app is a serious contender for those venturing beyond well-trodden paths in the United States. It excels at providing detailed, layered maps that show you not just the trail, but crucial land ownership information, which can be a lifesaver when you're unsure if you're crossing onto private property.

While it might seem like overkill for a simple neighborhood stroll, its robust offline capabilities and clear topographic and satellite layers make it a top-tier app for mapping walks in national forests, state parks, and remote wilderness areas. It even includes specialized data like avalanche forecasts and recent wildfire perimeters, highlighting its focus on safety and situational awareness in the backcountry.

Core Features & User Experience​

The mobile app's user interface is clean and performs well, even when handling complex map layers in remote locations without cell service. You can easily record your tracks, add waypoints with photos, and build routes ahead of time. The guidebook-style trail data provides reliable descriptions and key stats for thousands of hikes, integrated directly into the map.

Best For: Serious hikers, backpackers, and anyone walking in remote U.S. areas where land ownership and access are key considerations.

• Website: https://www.onxmaps.com/backcountry
• Pricing: Premium is around $29.99/year for offline maps and trail data. Elite is about $59.99/year and adds private land data and other advanced layers. Introductory offers are common.
• Pros: Excellent U.S. land ownership and access information, strong mobile performance for backcountry navigation, and straightforward pricing.
• Cons: Content is heavily focused on U.S. outdoor/backcountry use, and the advanced features are likely unnecessary for casual urban walkers.

12. OsmAnd​

OsmAnd is the app for the fiercely independent walker who values privacy and offline capability above all else. Built on the open-source OpenStreetMap (OSM) project, it’s a powerful navigation tool that works entirely offline, making it a fantastic app for mapping walks in remote areas or while traveling internationally without a data plan. Instead of streaming maps, you download detailed maps for entire countries or regions directly to your device.

This app stands out by giving you granular control over your experience without tethering you to a big-tech ecosystem. You can import GPX files for custom routes, customize what details appear on your map, and trust that your location data isn't being harvested. It's less about social discovery and more about pure, reliable, self-sufficient navigation.

Core Features & User Experience​

The initial experience can be daunting; the interface is dense and packed with features, presenting a steeper learning curve than slicker, more mainstream apps. However, for those willing to invest a little time, the payoff is immense. You get turn-by-turn voice navigation for walking, contour lines for terrain, and a high degree of map customization. The free version includes a limited number of map downloads to get you started.

Best For: Privacy-conscious users, international travelers, and tech-savvy walkers who want complete offline functionality and control over their maps.

• Website: https://osmand.net
• Pricing: Free version with limited map downloads. OsmAnd+ Maps & GPS Offline is a one-time purchase (around $29.99 on iOS) or a subscription plan (OsmAnd Pro) is available for access to all features and frequent map updates.
• Pros: Strong privacy posture and extensive offline capability, works globally, and is excellent for custom GPX walks.
• Cons: The user interface has a steep learning curve and can feel cluttered compared to more minimalist apps.

12 Walk-Mapping Apps: Feature Comparison​

Which Walking App is Right for Your Journey?​

Well, that was quite a hike through the world of digital wayfinding! We’ve navigated a dozen different contenders, each promising to be the best app for mapping walks, but as we've seen, the "best" app is less about a universal winner and more about finding the perfect partner for your personal journey. Your ideal tool depends entirely on your "why" for walking.

It's clear the market has an app for every kind of walker. If you thrive on competition, kudos, and community leaderboards, the social ecosystems of Strava and MapMyWalk are designed to keep you motivated and connected. They turn every walk into a shareable event, focusing on performance, fitness goals, and social validation. They’re excellent for training and finding local walking buddies.

For those whose paths lead them off the beaten track, the choice is equally clear but geared toward survival and discovery. Rugged adventurers and serious hikers need the specialized power of Gaia GPS, onX Backcountry, or CalTopo. These apps are less about social sharing and more about detailed topographic layers, offline reliability, and ensuring you make it home safely. They are the digital equivalent of a trusty compass and a well-worn paper map.

Finding Your Fit: A Quick Guide​

So, how do you filter through the noise and pick the right one? Let's boil it down to a few key questions you should ask yourself before downloading anything:

• What is my primary goal? Is it fitness tracking, backcountry navigation, urban exploration, or creating a personal memory log? Your answer is the single most important factor.
• How important is privacy to me? Are you comfortable with your location data being part of a social network, or do you need a private, secure vault for your personal timeline? This is a crucial distinction between apps like Strava and Dawarich.
• Do I need offline access? If you frequently walk in areas with spotty cell service, apps with robust offline mapping capabilities like OsmAnd, Gaia GPS, and Komoot should be at the top of your list.
• What’s my budget? While many apps offer great free tiers, the most powerful features are often locked behind a subscription. Decide if the premium offerings are worth the investment for your specific use case.

The Rise of the Personal Journey Log​

While many apps focus on the walk itself - the pace, the elevation, the calories burned - there's a growing need for an app for mapping walks that focuses on the story behind the walk. This is where the landscape of options shifts dramatically. For lifeloggers, digital nomads, and anyone who wants to preserve their memories, the primary goal isn't performance; it's effortless, automatic documentation.

This is the specific niche where Dawarich shines. It operates on a fundamentally different principle. It’s not about pushing you to walk faster or further. Instead, it works quietly in the background, creating a rich, private, and searchable tapestry of your life's movements. It’s designed for the person who revisits a city and wants to find that tiny cafe they loved, the traveler documenting a multi-month journey, or the memory keeper who values having an accurate timeline of their life.

By prioritizing automatic tracking, GDPR-grade privacy, and powerful journaling features, Dawarich serves a need the fitness and hardcore navigation apps simply don’t address. It’s for those of us who believe the journey itself is the destination, and that every step is part of a larger story worth remembering. So, as you lace up your shoes, consider what you want to get out of your walk. Whether it's a new personal best, a stunning mountain view, or a memory saved for a lifetime, there’s an app ready to map the way.

Ready to start building your own private world map? If you're looking for an app for mapping walks that automatically creates a beautiful, searchable timeline of your life's journeys without compromising your privacy, give Dawarich a try. See your story unfold at Dawarich and begin your life's archive today.

Instead of a spreadsheet of numbers, you get a personal map showing every path you’ve taken and every place you’ve spent your time. I've found it's a fascinating way to truly see your journeys, from the daily grind to that unforgettable road trip.

What Exactly Is a Location History Visualizer?​

Have you ever tried to retrace the exact route of a past vacation or wondered which parts of your city you really hang out in the most? A location history visualizer is the tool that brings those answers to life. Think of it as a personal time machine for your movements, transforming abstract data points from your phone into something you can actually see and interact with.

A good visualizer doesn't just drop pins on a map; it connects the dots. It can draw the precise lines of a cross-country drive or build a colorful heatmap that instantly reveals your favorite neighborhoods, coffee shops, and parks. It’s all about making your own data understandable and, frankly, pretty cool to explore.

It's More Than Just a Fun Distraction​

Seeing your past travels mapped out is one thing, but the practical uses go way deeper. People are using these tools to turn their digital footprints into some genuinely useful insights.

Here’s why you might want to do this:

• Build a Digital Travel Journal: Automatically log every step of a trip, creating an interactive scrapbook of your adventures you can look back on for years.
• See Your Own Habits: Get a clear picture of your daily and weekly routines. Are you hitting the gym as much as you think? How has your commute changed over time?
• Rediscover Forgotten Moments: The best discoveries are often the small detours and forgotten stops—the kind of thing a simple list of addresses would never capture.

A location history visualizer turns a dry list of coordinates into a living document of your experiences. It provides context, reveals patterns, and helps you tell the story of where you've been in a way that data alone never could.

Turning Raw Data Into a Story​

At its core, the real magic of a location history visualizer is its ability to create a narrative. It doesn't just show you where you went; it shows you how you got there. That jump from static points to dynamic paths is what makes the whole thing so compelling.

You can see the winding mountain roads from that summer road trip, the overlapping routes of your daily life, or the concentrated glow of a city you explored entirely on foot. Each visualization is a unique map of your personal history, built from the digital breadcrumbs you leave behind every day. It's your story, told through geography.

How Your Digital Footprints Become a Map​

So how does a bunch of abstract data from your phone magically become a detailed map of your life? It’s a lot like connecting the dots in a massive, invisible drawing that follows you everywhere you go. Once you peek behind the curtain, the process is surprisingly straightforward.

It all starts with data collection. Every time your phone pings a cell tower, hops on a Wi-Fi network, or uses its GPS, it can log your coordinates. Services like Google Maps quietly gather these digital breadcrumbs, building a massive, continuous log of your movements, complete with timestamps.

This raw data is the absolute lifeblood of any location history visualizer. Without it, there’s nothing to map.

Decoding Your Digital Diary​

Your location history is usually packed into specific file formats that are designed to be read by computers. Think of these as the raw ingredients for our visual recipe. To us, they might look like a jumble of code, but they contain a perfectly organized record of your journeys.

The most common formats you’ll bump into are:

• Google's JSON files: When you download your history from Google Takeout, you get a file in JSON (JavaScript Object Notation) format. It’s a text-based format that lays out your data in a clean, hierarchical structure, showing you the places you’ve been and the paths you took to get there.
• GPX (GPS Exchange Format): This is the universal standard loved by fitness apps and hiking gadgets. It's an XML-based file that logs waypoints, routes, and tracks, making it perfect for recreating a specific trip from start to finish.
• KML (Keyhole Markup Language): Originally created for Google Earth, KML files are fantastic for displaying geographic data in an Earth browser. They can hold anything from points and lines to even 3D models.

From Raw Data to a Visual Story​

Once you've got your data file, the visualizer tool steps in to act as the translator. It combs through thousands of data points—each one a specific latitude, longitude, and time—and starts plotting them on a digital map. It's essentially an automated game of "you were here... then here... then here."

The tool then connects these dots chronologically, drawing lines that trace the exact routes you traveled. If the data shows you hung out in one spot for a while, the visualizer can interpret that as a significant stop or a place you visited.

This is where the real magic happens. A good visualizer doesn't just plot dots; it interprets the data to create meaningful pictures like routes, timelines, or heatmaps. It turns a sterile log file into a personal story.

The value here goes way beyond just satisfying your own curiosity. Businesses are catching on to the power of mapping in a big way. A Boston Consulting Group survey found that 95% of executives see geospatial analytics as critical for getting results, and this reliance is only growing. This trend is fueling the global location intelligence market, which is expected to hit nearly USD 35 billion by 2029, as companies use these tools for everything from picking store locations to optimizing delivery routes.

For you, this powerful technology can reveal patterns you’d otherwise miss completely. You might realize your commute has slowly gotten longer over the years or rediscover a hidden gem from a vacation you took long ago — all because a tool was able to connect the dots.

Choosing the Right Visualizer Tool for You​

Not all visualizer tools are built the same, and picking the right one really boils down to what you’re trying to do. Think of it like choosing a camera: sometimes your phone is all you need for a quick snapshot, but other times, you want a professional DSLR with a bag full of lenses. Location history visualizers are a lot like that.

It all starts with figuring out what you actually want. Are you just curious and looking for a simple, automated summary of your year? Or are you a data geek who wants to dig deep, applying custom filters and running your own analysis?

Let's walk through the main options out there.

Built-in Services: The "Set It and Forget It" Option​

For most people, the simplest starting point is a built-in service like Google Timeline. If you have location history turned on for your Google account, it’s already been quietly logging your movements in the background. It automatically pieces together your travels, figures out the places you’ve visited, and gives you a clean, straightforward look at your life on the map.

The biggest draws here are convenience and automation. You don't have to set anything up, download any files, or install a single piece of software. It just works.

• Pros: Completely hands-off, easy to check anytime, and great for a simple day-to-day recap.
• Cons: Very limited customization, you have less control over your own data, and you're locked into the Google ecosystem.

This is the perfect choice if you just want a casual look back at your travels without getting technical. It's the point-and-shoot camera of the visualizer world.

Dedicated Web and Desktop Apps​

If you're ready for a bit more control, dedicated web and desktop applications are the next step up. These tools are specifically built to import your location data—usually from a Google Takeout file—and give you more powerful ways to explore it. You can start filtering by date, switching between different views like heatmaps and routes, and really analyzing your patterns.

These apps hit a sweet spot. They offer far more features than the built-in services but are still pretty easy to get the hang of. You can finally interact with your data in more meaningful ways, like isolating a specific road trip or seeing a density map of your most frequented spots in the city.

A dedicated app unlocks what’s really hiding in your location data. Instead of just seeing where you've been, you can start asking why and how, turning a simple log into a powerful tool for self-reflection.

Self-Hosted Solutions: For Ultimate Privacy and Control​

For anyone who puts data ownership and privacy first, self-hosted solutions are the only way to go. A self-hosted location history visualizer means you run the software on your own server—this could be a spare computer at home or a private cloud server you rent. The bottom line is, you have complete and total control over your personal information.

Tools like Dawarich are designed around this privacy-first idea. You import your data, and it stays entirely within your environment, never uploaded to a third-party service you don't manage. This completely sidesteps the privacy trade-offs you make with other platforms. To see what this feels like, you can check out a timeline visualizer that puts you in the driver's seat.

This path does take a bit more technical know-how to set up (you'll likely run into tools like Docker), but for privacy-minded folks, the payoff is huge. You get powerful features, true ownership of your data, and the peace of mind that comes from knowing your digital footprints are truly your own.

Comparing Location History Visualizer Options​

To help you decide, here’s a breakdown of the common visualizer types. Think about what matters most to you—simplicity, features, or privacy—to find the best fit.

Ultimately, there’s no single "best" tool—it's all about what works for you. Whether you want a quick glance or a deep dive, there’s an option out there that will bring your personal map to life.

How to Visualize Your Own Location History​

Alright, let's get our hands dirty and turn that mountain of raw data into something you can actually see and explore. This is where we move from theory to practice and build your own interactive map. Don't worry, the journey from a data file to a full-blown visualization is much easier than it sounds.

We'll start with the most common first step for most people: getting your data out of Google's hands. After that, we'll walk through setting up a self-hosted location history visualizer called Dawarich. It’s an awesome tool that gives you total control over your private information.

Step 1: Exporting Your Data from Google Takeout​

Before you can map out anything, you need the raw ingredients. If you’re an Android user (or even an iPhone user with Google Maps installed), Google has been logging your every move. Thankfully, they offer a tool called Google Takeout that lets you download a copy of it.

Getting the right file is the key here. It’s pretty straightforward.

1. Head over to Google Takeout: Open up the official Google Takeout site. You’ll see a massive list of every Google service that has a piece of your data.
2. Deselect Everything: By default, it wants to give you everything. Immediately click "Deselect all" at the top. Trust me, you don't need your old YouTube comments for this project.
3. Find and Select Location History: Now, scroll down until you spot "Location History" and just check that one box. This tells Takeout you only want that specific dataset. The format will be JSON, which is exactly what we need.
4. Create the Export: Scroll to the bottom and hit "Next step." On the next screen, you can just stick with the defaults (export once, .zip file) and click "Create export."

Google will start packaging up your history. This might take a few minutes or a bit longer, depending on how much data you have. You’ll get an email with a download link when it's all ready.

Step 2: Setting Up a Self-Hosted Visualizer with Dawarich​

Once that .zip file is on your computer, it's time to bring it to life. For this guide, we're using Dawarich because it’s a powerful, privacy-first option you can run on your own machine. That means your sensitive location data never leaves your computer or gets uploaded to some random third-party service.

The magic of self-hosting is data ownership. When you run the software yourself, you're not just a user—you're the administrator. Your personal history stays completely under your control, from start to finish.

The idea of "self-hosting" might sound a little techy, but tools like Docker make it surprisingly simple. Think of Docker as a way to run applications in their own neat little boxes, so you don't have to fuss with complicated setup and configuration.

This infographic breaks down the choice you have, from easy-but-less-private cloud services to the more controlled, self-hosted route we're taking.

As you can see, you trade a little bit of initial convenience for a massive gain in privacy and control by going the self-hosted route. It's a worthy trade-off.

Step 3: Installation and Data Import​

The Dawarich project keeps everything you need—code, documentation, and instructions—on its GitHub page.

While the exact commands might differ slightly based on your computer, the general process with Docker is a breeze:

• Install Docker: If you don't have it, you'll need to install Docker first. It's a one-time setup.
• Run the Dawarich Container: You'll run a single command from the Dawarich documentation. This will automatically download and start the application.
• Import Your Data: With Dawarich running, open it in your web browser. You’ll see an option to import your Google Takeout file. Just unzip the file you downloaded, find the Location History.json file inside, and upload it.

The platform will chew on the data for a bit and then, like magic, your personal map will start to fill in. For a more detailed walkthrough, you can follow this excellent guide on migrating from Google Location History to Dawarich.

This whole field of location analytics is absolutely exploding. We're talking about a market that was valued at around USD 31.3 billion in 2025 and is expected to rocket to USD 124.3 billion by 2035. This boom is fueled by all the smart devices and IoT tech that generate a constant stream of location data. This data is used for everything from city planning to, well, personal journaling.

By setting up your own visualizer, you’re basically tapping into this powerful technology for your own benefit. You can find more details on the growth of the location analytics market on futuremarketinsights.com.

Practical Ways to Use Your Visualized Data​

https://www.youtube.com/embed/SXAShotdFZo

So, you’ve wrestled with Google Takeout, set up your own visualizer, and now you’re staring at this incredible, intricate map of your life. The big question is: now what? This is more than just a cool digital art project. This is where your data stops being a passive log and starts becoming a tool for reflection, planning, and even storytelling.

Turning those colorful lines and heatmaps into something genuinely useful is the most rewarding part of the whole process. Whether you're a travel junkie, a creature of habit, or just someone curious about your own patterns, there are tons of practical applications waiting to be discovered. It's a chance to see your life from a completely new angle.

For Personal Reflection and Habit Analysis​

One of the most powerful uses for your visualized data is simply getting to know yourself better. A location history visualizer acts like a mirror, reflecting your habits and routines back at you in a way you've never seen before. You might think you have a good handle on your weekly schedule, but the map doesn't lie.

This kind of visual feedback can be incredibly eye-opening if you're looking to make some intentional changes.

• Analyze Your Routines: See exactly how your commute has shifted over the years. Is that new shortcut actually saving you time, or just adding stress? The data will tell you.
• Track Your Goals: Wondering if you're hitting the gym as often as you promised yourself? A heatmap will quickly show you which locations dominate your time—the fitness center or the coffee shop down the street.
• Rediscover Your City: You can easily spot the neighborhoods you gravitate towards and the ones you’ve completely neglected. It’s a great way to inspire yourself to break out of your bubble and explore new places right in your own backyard.

Your location data tells a story about your priorities, whether you realize it or not. Visualizing it lets you read that story and decide if you want to write a different one.

For Travel Journaling and Future Planning​

For anyone who loves to travel, a location history visualizer is the ultimate digital scrapbook. Forget trying to remember the name of that amazing little restaurant you stumbled upon in a new city—your map already has it logged. It creates a definitive, interactive record of your adventures.

You can relive a trip by tracing the exact path you took, seeing every detour and spontaneous stop along the way. But it’s not just about looking back; it’s also an incredible tool for planning what's next. By analyzing your past trips, you can see what kinds of places you're naturally drawn to and plan future adventures that build on old favorites.

For Professional and Creative Projects​

Beyond personal use, visualizing location data has some surprisingly practical professional applications. For people in certain fields, this kind of log is more than just a novelty; it’s a functional dataset that can inform their work and creative projects.

Just think about these examples:

• Photographers: Can automatically log every shoot location, making it a breeze to return to a great spot or find new angles in a familiar area.
• Urban Cyclists: Can analyze their most frequent routes to identify safer or more efficient paths, contributing to a better understanding of city infrastructure.
• Field Researchers: Can document their movements through a study area, providing a verifiable record of where and when data was collected.

Managing Your Location Data with Privacy in Mind​

Let's be real for a second. Diving into your location history is a blast—it’s like re-reading your own personal travel diary. But this data is about as personal as it gets. Handling it with care isn't just a suggestion; it's a must.

This leads you to a crossroads: do you go for convenience or for control? Using a service like Google Timeline is super easy, but it means handing over the keys to your entire movement history to a massive company. On the other hand, a personal location history visualizer puts you in the driver's seat, ensuring your data never leaves your sight.

Taking Control of Your Digital Footprint​

Managing your privacy doesn’t mean you have to go live in a cave. It’s mostly about being mindful and making a few smart tweaks to how you share your info. Good digital habits are your best defense.

Here are a few practical things you can do right now:

• Review App Permissions Regularly: Go through your phone and see which apps are tracking your location. Does that puzzle game really need to know where you are 24/7? Probably not. Shut it down.
• Be Selective with Tracking: You don't need location services running all the time. Try turning it off when you're not actively using it for maps or directions.
• Understand the Trade-Off: For any service that wants your location, ask a simple question: "What am I getting out of this?" Is the convenience truly worth what you're giving away?

The goal isn't to go completely off the grid. It's about making conscious decisions, understanding what you're sharing, and choosing tools that match your personal comfort level for privacy.

For anyone who really wants to take ownership of their data, setting up a privacy-focused visualizer is a fantastic project. If you're curious to learn more, there's a great guide on building a privacy-first Google Timeline visualizer that covers the thinking and the step-by-step process.

Anonymizing Data Before You Share​

So, you’ve made an awesome visualization—maybe a heatmap of your favorite running trails—and you want to show it off. That's great! But before you hit "post," you need to scrub it of anything that points back to you. Raw location data can easily give away your home, your workplace, and other sensitive spots.

Before you share anything publicly, take a few minutes to anonymize your map. This could mean:

1. Generalizing Start and End Points: Don't show the exact dot where your house or office is.
2. Removing Timestamps: Timestamps can reveal your daily routine, like when you leave for work or when your house is empty.
3. Fuzzing the Data: You can slightly reduce the precision of the GPS coordinates, making it impossible to pinpoint an exact address.

Taking these simple steps lets you share your cool data stories with the world without putting your privacy on the line. It's all about finding that sweet spot between enjoying your data and keeping yourself safe.

Got Questions? We've Got Answers​

Diving into location history visualizers for the first time usually sparks a few questions. It's a pretty personal and fascinating topic, so it's totally normal to be curious about how it all works. Here are some quick answers to the things people ask most often.

Is It Safe to Use an Online Visualizer?​

That’s the million-dollar question, isn't it? The honest answer is: it really depends. When you upload your location data to some random website, you're placing a lot of trust in them to keep it safe. Many services are legitimate and secure, but you're still handing over incredibly sensitive information.

The only way to have 100% peace of mind is to use a self-hosted location history visualizer. When the software and your data live on your own computer or server, you slam the door on third-party risks like data breaches or sketchy privacy policies. You're the only one in control.

Can I See My iPhone's Location History?​

Absolutely, though it's not as straightforward as it is with Google. Apple doesn't have a simple, one-click "Takeout" button for your location history. The most reliable way to do it is to use a third-party app that tracks your location and lets you export the data as a GPX file.

Once you have that GPX file, you can pop it into any visualizer that supports the format. While your iPhone does keep track of "Significant Locations," Apple keeps that data pretty locked down and it isn't designed for easy exporting.

What's the Difference Between a Heatmap and a Path Map?​

It really boils down to seeing where you spend your time versus how you got there.

A path map is literal. It connects the dots and draws the exact lines of your travels, showing your journey in chronological order. It's fantastic for reliving a road trip or analyzing your daily commute.

A heatmap, on the other hand, is all about density. It uses colors—usually getting hotter, like red, for more activity—to show the places you frequent most. It gives you a quick, powerful snapshot of the central hubs of your life.

Ready to take back your story and build a map that's truly yours? Dawarich is a privacy-first platform built for just that. Import your history, create stunning visualizations, and own your data from the get-go. Start your free 7-day trial today.

That's why we built the Google Timeline Visualizer — a free, privacy-first tool that turns those cryptic JSON files into an interactive map you can actually explore.

The Problem: Google's Timeline Limitations​

Google recently made some controversial changes to Timeline. They killed the web-based timeline browser, moved all data to mobile devices, lost years of users' data in the process, and started limiting how long your location history is stored. If you want to keep your data or visualize it properly, you're basically on your own.

When you export your Google Timeline data through Takeout or from your phone, you get JSON files — sometimes hundreds of megabytes worth. These files contain years of location data, place visits, and activity segments, but there's no easy way to visualize them without uploading to yet another third-party service.

We needed a solution that was fast, secure, and most importantly: kept your data private.

Privacy-First Architecture​

Location data is incredibly sensitive. It shows where you live, where you work, where you go for medical appointments, who you visit, and your daily routines. Uploading this to a random web service is a huge privacy risk (except for Dawarich Cloud haha).

That's why our visualizer runs entirely in your browser. When you upload your JSON files:

• Nothing is sent to any server — all processing happens locally on your device
• No tracking or analytics on your location data
• Your data stays in your browser's memory and disappears when you close the tab
• Open source and transparent — you can verify exactly what the code does

This approach means your location history never leaves your computer. It's the digital equivalent of opening a paper map in your living room instead of mailing it to a stranger.

How It Works​

The visualizer follows a straightforward process:

1. Upload Your Files — Drop your Google Timeline JSON files into the browser
2. Auto-Detection — The tool automatically identifies the format (Records.json, Semantic Timeline, Location History, etc.)
3. Progressive Processing — Files are parsed in batches to keep your browser responsive
4. Interactive Map — Points and paths appear on the map using Leaflet and OpenStreetMap
5. Year Filtering — Filter by year to explore specific time periods without overwhelming your browser

The entire process happens in JavaScript running in your browser. For a 170 MB file with 630,000 location points, processing takes about 20-30 seconds on a modern computer.

Handling Massive Files​

One of the biggest technical challenges was performance. Google exports can contain hundreds of thousands of GPS points. Loading all of them at once would crash most browsers.

We solved this with several optimizations:

Batch Processing — Points are streamed to the map in batches of 5,000, yielding control to the browser between batches. This keeps the UI responsive even while processing massive datasets.

Year-Based Pagination — The visualizer calculates how many points exist in each year, then defaults to showing only the earliest year. Users can switch between years or view all data at once. This typically reduces the initial render from 600k+ points to 40-60k points.

Incremental Rendering — When switching years, only the new points are added to the map. The library handles clustering and de-duplication automatically.

Lazy Popups — Instead of generating HTML for 600k popups upfront, popup content is created only when you click on a marker.

These optimizations mean you can visualize years of location history without your browser grinding to a halt.

Supported Formats​

Google exports location data in several different formats depending on when and how you export it. The visualizer supports all of them:

Records.json — Raw GPS location records in E7 coordinate format. This is the oldest format and typically the largest file, containing every GPS ping Google recorded.

Semantic Timeline (YYYY_MONTH.json) — Monthly files containing place visits and activity segments. These are more structured and include information about what you were doing (walking, driving, etc.) and which places you visited.

Location History (from phone) — The newer format exported directly from Google Maps on Android or iOS. This uses a different JSON structure with semanticSegments and timeline paths.

Semantic Segments — A processed format with geographic coordinates in "geo:lat,lng" string format, often created by parsing raw exports with tools like jq.

No matter which format Google gives you, the visualizer will detect it automatically and extract:

• GPS coordinates and timestamps
• Place visits with duration
• Activity segments (walking, driving, cycling)
• Activity paths showing your actual route

Features​

Interactive Map — Pan, zoom, and explore your location history on an OpenStreetMap base layer. Markers show individual locations, while colored polylines show your movement paths.

Smart Filtering — The side panel shows only meaningful visits and places, not every GPS ping. For a Records.json file with 600k raw points, the list shows only actual place visits — making it useful instead of overwhelming.

Year Selector — Filter by year to focus on specific time periods. The dropdown shows how many points exist in each year, making it easy to explore your data chronologically.

Auto-Fit Bounds — When you switch years, the map automatically zooms to show all points for that period. Traveled from Europe to the USA in different years? The map adapts to each dataset.

Dark Mode — Full support for light and dark themes with proper contrast.

Limitations​

Bigger files take time to process. A 170 MB file with hundreds of thousands of points needs 20-30 seconds to parse and render. This happens once when you first load the file.

Browser memory limits apply. While we've tested files with 600k+ points across 15 years successfully, extremely large exports (multiple years, multiple large files) might struggle on older computers with limited RAM.

The visualizer shows your data but doesn't edit it. If you want to keep your location history accessible, export it to formats like GPX, or store it long-term, you'll need additional tools.

Getting Your Data​

The visualizer includes detailed instructions for exporting your Google Timeline data:

Google Takeout — Visit takeout.google.com, select "Location History (Timeline)", and export. Note that this method doesn't work for everyone due to Google's policy changes.

Android — Open Google Maps → Settings → Location → Location Services → Timeline → Export Timeline

iOS — Open Google Maps → Settings → Personal Content → Export Timeline data

Once you have your JSON files, just drag and drop them into the visualizer.

When You Need More​

The Timeline Visualizer is great for quick exploration and one-time analysis. But if you want to:

• Store your location history securely long-term
• Import data from multiple sources (GPX, GeoJSON, etc.)
• Track ongoing location data from your devices
• Access your timeline from anywhere
• Share specific trips or areas

...then you need a proper location tracking platform.

That's where Dawarich comes in. It's an open-source location tracker that gives you full control over your location data. It supports all the same Google Timeline formats as the visualizer, plus GPX files from hiking apps, GeoJSON exports, and real-time tracking from mobile apps.

The visualizer shows you what's possible. Dawarich lets you keep it.

Technical Stack​

The visualizer is built with:

• React 18 — UI components and state management
• Leaflet — Interactive maps with OpenStreetMap tiles
• Leaflet.markercluster — Efficient clustering of thousands of markers
• Docusaurus — Static site generation and documentation
• Custom JavaScript parsers — Handle Google's various export formats

All processing happens client-side. No backend, no database, no user tracking.

Future Improvements​

We're exploring additional visualizations like heatmaps, timeline charts, and statistics (most visited places, total distance traveled, etc.). Better performance optimizations are always on the roadmap.

Try It Yourself​

The Google Timeline Visualizer is free to use at dawarich.app/tools/timeline-visualizer.

Export your Google Timeline data, drop it in, and see where you've been. All in your browser, all private, all yours.

Resources & Credits​

Building this visualizer required understanding Google's various export formats and parsing their different JSON structures. Here are the key resources and tools that made it possible:

• https://locationhistoryformat.com/ — Comprehensive documentation of Google Location History formats
• jq — Command-line JSON processor used for parsing and transforming Google Location History (the exports from user's devices)
• Leaflet.js — Open-source JavaScript library for interactive maps

The Google Timeline Visualizer is part of the Dawarich ecosystem. All code is open source and available on GitHub.

What is Dawarich?​

We all use our phones for maps and navigation. The problem is, Big Brothers save this data on their servers, which means they know where you’ve been, how often you travel, and sometimes even guess your habits. If that feels uncomfortable, Dawarich is a refreshing alternative.

Dawarich is a service that lets you keep a personal record of your movements and places you’ve visited. The key difference? You’re in charge. You can run it yourself on your own server or computer (and we now have an iOS app too!), so nobody else has access to your location history.

Main Features​

Track your journeys: Dawarich saves your routes, distances, and the places you’ve been.

See your "life map": Look back at your travels, runs, bike rides, or even your daily routes.

Add memories: If you already use photo storage apps like Immich or Photoprism, you can set up syncing and create short photo notes from your travels!

Privacy first: All information is stored where you choose. We make daily backups and database encryption, an SSL certificate is used for data transfer, and hosted in Europe (Frankfurt and Falkenstein, Germany).

Useful​

• For travelers: keep track of countries, cities, and kilometers you’ve explored.
• For close friends and family: Share vacation and travel locations and create a memory map.
• For fitness enthusiasts: log your distances and routes privately, without sharing with third parties.
• For data-driven persons: enjoy the peace of mind knowing your data is truly yours.

Dawarich is like a private diary for your journeys: digital, secure, and completely under your control. You decide whether to keep it just for yourself, share it with close family, or connect it with other tools.

November was a good month for Dawarich. I've added a lot of new features and fixed a some bugs, and, among other things, I've added a new Patreon tier. It's called "Hosted Dawarich" and basically offers my service of hosting and updating Dawarich for you. Take a look at the Patreon page for more details and feel free to ask me any questions.

Let's dive into the details!

Important features and changes​

The Trips release​

You can now create, edit and delete trips. To create a trip, click on the "New Trip" button on the Trips page. Provide a name, date and time for start and end of the trip. You can add your own notes to the trip as well.

If you have points tracked during provided timeframe, they will be automatically added to the trip and will be shown on the trip map.

Also, if you have Immich integrated, you will see photos from the trip on the trip page, along with a link to look at them on Immich.

The Immich Photos release​

With this release, Dawarich can now show photos from your Immich instance on the map.

To enable this feature, you need to provide your Immich instance URL and API key in the Settings page. Then you need to enable "Photos" layer on the map (top right corner).

An important note to add here is that photos are heavy and hence generate a lot of traffic. The response from Immich for specific dates is being cached in Redis for 1 day, and that may lead to Redis taking a lot more space than previously. But since the cache is being expired after 24 hours, you'll get your space back pretty soon.

The other thing worth mentioning is how Dawarich gets data from Immich. It goes like this:

1. When you click on the "Photos" layer, Dawarich will make a request to GET /api/v1/photos endpoint to get photos for the selected timeframe.
2. This endpoint will make a request to POST /search/metadata endpoint of your Immich instance to get photos for the selected timeframe.
3. The response from Immich is being cached in Redis for 1 day.
4. Dawarich's frontend will make a request to GET /api/v1/photos/:id/thumbnail.jpg endpoint to get photo thumbnail from Immich. The number of requests to this endpoint will depend on how many photos you have in the selected timeframe.
5. For each photo, Dawarich's frontend will make a request to GET /api/v1/photos/:id/thumbnail.jpg endpoint to get photo thumbnail from Immich. This thumbnail request is also cached in Redis for 1 day.

The Websockets release​

This one is more about QoL, making your UI more alive. Notifications, new points on the map, imports now won't require page reloading to see an update, they will just be on your page dynamically.

Scratch map release​

Yeah, you can now enable the "Scratch Map" layer on the map. Have a look:

Changelog​

Added​

• The Trips feature.
• If you have provided your Immich instance URL and API key, the map will now show photos from your Immich instance when Photos layer is enabled.
• GET /api/v1/photos endpoint added to get photos from Immich.
• GET /api/v1/photos/:id/thumbnail.jpg endpoint added to get photo thumbnail from Immich.
• Admins can now see all users in the system on the Users page. The path is /settings/users.
• New notifications are now being indicated with a blue-ish dot in the top right corner of the screen. Hovering over the bell icon will show you last 10 notifications.
• New points on the map will now be shown in real-time. No need to reload the map to see new points.
• User can now enable or disable Live Mode in the map controls. When Live Mode is enabled, the map will automatically move to the new points as they are being added to the map.
• Scratch map. You can enable it in the map controls. The scratch map highlight countries you've visited. The scratch map is working properly only if you have your points reverse geocoded.
• GET /api/v1/countries/borders endpoint to get countries for scratch map feature
• Dawarich now can export metrics to Prometheus. You can find the metrics at your.host:9394/metrics endpoint. The metrics are being exported in the Prometheus format and can be scraped by Prometheus server. To enable exporting, set the PROMETHEUS_EXPORTER_ENABLED env var in your docker-compose.yml to true. Example:

  dawarich_app:
    image: freikin/dawarich:latest
    container_name: dawarich_app
    environment:
      ...
+     PROMETHEUS_EXPORTER_ENABLED: "true"

Fixed​

• Retrieving photos from Immich now using takenAfter and takenBefore instead of createdAfter and createdBefore. With createdAfter and createdBefore Immich was returning no items some years.
• Retrieving photos from Immich now correctly handles cases when Immich returns no items. It also logs the response from Immich for debugging purposes.
• Exported files will now always have an extension when downloaded. Previously, the extension was missing in case of GPX export.
• Deleting and sorting points on the Points page will now preserve filtering and sorting params when points are deleted or sorted. Previously, the page was being reloaded and filtering and sorting params were lost.
• Exported GPX file now being correctly recognized as valid by Garmin Connect, Adobe Lightroom and (probably) other services. Previously, the exported GPX file was not being recognized as valid by these services.
• Speed is now being recorded into points when a GPX file is being imported. Previously, the speed was not being recorded.
• GeoJSON file from GPSLogger now can be imported to Dawarich. Previously, the import was failing due to incorrect parsing of the file.

Changed​

• Maps are now not so rough on the edges.
• Rate limit for the Photon API is now 1 request per second. If you host your own Photon API instance, reverse geocoding requests will not be limited.
• Requests to the Photon API are now have User-Agent header set to "Dawarich APP_VERSION (https://dawarich.app)"
• Default number of Puma workers is now 2 instead of 1. This should improve the performance of the application. If you have a lot of users, you might want to increase the number of workers. You can do this by setting the WEB_CONCURRENCY env var in your docker-compose.yml file. Example:

  dawarich_app:
    image: freikin/dawarich:latest
    container_name: dawarich_app
    environment:
      ...
      WEB_CONCURRENCY: "2"

• PROMETHEUS_EXPORTER_HOST and PROMETHEUS_EXPORTER_PORT env vars were added to the docker-compose.yml file to allow you to set the host and port for the Prometheus exporter. They should be added to both dawarich_app and dawarich_sidekiq services Example:

  dawarich_app:
    image: freikin/dawarich:latest
    container_name: dawarich_app
    environment:
      ...
      PROMETHEUS_EXPORTER_ENABLED: "true"
+     PROMETHEUS_EXPORTER_HOST: 0.0.0.0
+     PROMETHEUS_EXPORTER_PORT: "9394"

  dawarich_sidekiq:
    image: freikin/dawarich:latest
    container_name: dawarich_sidekiq
    environment:
      ...
      PROMETHEUS_EXPORTER_ENABLED: "true"
+     PROMETHEUS_EXPORTER_HOST: dawarich_app
+     PROMETHEUS_EXPORTER_PORT: "9394"

• Dawarich now uses POST /api/search/metadata endpoint to get geodata from Immich.
• Admins can now provide custom password for new users and update passwords for existing users on the Users page.
• The bin/dev file will no longer run bin/rails tailwindcss:watch command. It's useful only for development and doesn't really make sense to run it in production.
• The Vists suggestion job is disabled. It will be re-enabled in the future with a new approach to the visit suggestion process.

Conclusion​

What a month huh? Feel free to reach out to me on X, Mastodon or Discord server if you have any questions or suggestions.

You can also support the project by sponsoring it on Patreon, Ko-Fi or Github Sponsors ✨

Thank you and see you in the next monthly update!

News​

The biggest news of October for me is that I'm looking for a job! If you have a position for a Ruby on Rails developer with 10+ years of experience in Germany, drop me a line on LinkedIn or email me.

As for Dawarich, there is a pretty big list of changes and improvements in this release. Let's dive into them!

Important features and changes​

The Watcher release​

This feature will be useful for those who want to automate the import process. You can now put your GPX and GeoJSON files to the /tmp/imports/watched/USER@EMAIL.COM directory and Dawarich will automatically import them. This is useful if you have a service that can put files to the directory automatically. The directory is being watched every 60 minutes for new files.

For example, if you want to import a file for the user with the email address "email@dawarich.app", you would put it in the tmp/imports/watched/email@dawarich.app directory. The file will be imported into the database and the user will receive a notification in the app.

For now, only GeoJSON and GPX files are supported.

The up-to-date Photon in Docker​

@rtuszik was kind enough to build a new Docker image with the latest version of the Photon API. The source code with the usage instructions can be found on GitHub.

Set up your backup​

This is a kind reminder for you to set up a backup for your Dawarich instance. You can use the backup tutorial to do this. It's important to keep your data safe and secure.

Added​

• linux/arm/v7 is added to the list of supported architectures to support Raspberry Pi 4 and other ARMv7 devices
• Owntracks' .rec files now can be imported to Dawarich. The import process is the same as for other kinds of files, just select the .rec file and choose "owntracks" as a source.
• User can now select between "Raw" and "Simplified" mode in the map controls. "Simplified" mode will show less points, improving the map performance. "Raw" mode will show all points.
• Importing Immich data on the Imports page now will trigger an attempt to write raw json file with the data from Immich to tmp/imports/immich_raw_data_CURRENT_TIME_USER_EMAIL.json file. This is useful to debug the problem with the import if it fails.
• You can now put your GPX and GeoJSON files to tmp/imports/watched/USER@EMAIL.COM directory and Dawarich will automatically import them. This is useful if you have a service that can put files to the directory automatically. The directory is being watched every 60 minutes for new files.
• To expose the watcher functionality to the user, a new directory /tmp/imports/watched/ was created. Add new volume to the docker-compose.yml file to expose this directory to the host machine.

  ...

  dawarich_app:
    image: freikin/dawarich:latest
    container_name: dawarich_app
    volumes:
      - gem_cache:/usr/local/bundle/gems
      - public:/var/app/public
+     - watched:/var/app/tmp/watched

  ...

  dawarich_sidekiq:
      image: freikin/dawarich:latest
      container_name: dawarich_sidekiq
      volumes:
        - gem_cache:/usr/local/bundle/gems
        - public:/var/app/public
+       - watched:/var/app/tmp/watched

    ...

volumes:
  db_data:
  gem_cache:
  shared_data:
  public:
+ watched:

Changed​

• GET /api/v1/points can now accept optional ?order=asc query parameter to return points in ascending order by timestamp. ?order=desc is still available to return points in descending order by timestamp
• GET /api/v1/points now returns id attribute for each point
• Retries disabled for some background jobs
• Use static version of geocoder library that supports http and https for Photon API host. This is a temporary solution until the change is available in a stable release of geocoder.
• The Map page now by default uses timeframe based on last point tracked instead of the today's points. If there are no points, the map will use the today's timeframe.
• The map on the Map page can no longer be infinitely scrolled horizontally.
• Refactored the stats calculation process to make it more efficient.
• Hostname definition for Sidekiq healtcheck to solve #344. See the diff:

  dawarich_sidekiq:
    image: freikin/dawarich:latest
    container_name: dawarich_sidekiq
    healthcheck:
-     test: [ "CMD-SHELL", "bundle exec sidekiqmon processes | grep $(hostname)" ]
+     test: [ "CMD-SHELL", "bundle exec sidekiqmon processes | grep ${HOSTNAME}" ]

• Renamed directories used by app and sidekiq containers for gems cache to fix #339:

  dawarich_app:
    image: freikin/dawarich:latest
    container_name: dawarich_sidekiq
    volumes:
-     - gem_cache:/usr/local/bundle/gems
+     - gem_cache:/usr/local/bundle/gems_app

...

  dawarich_sidekiq:
    image: freikin/dawarich:latest
    container_name: dawarich_sidekiq
    volumes:
-     - gem_cache:/usr/local/bundle/gems
+     - gem_cache:/usr/local/bundle/gems_sidekiq

Fixed​

• Now you can use both http and https protocols for the Photon API host. You now need to explicitly provide PHOTON_API_USE_HTTPS to be true or false depending on what protocol you want to use. Example is in the docker-compose.yml file.
• For stats, total distance per month might have been not equal to the sum of distances per day. Now it's fixed and values are equal.
• Mobile view of the map looks better now.
• Stats update is now being correctly triggered every 6 hours.
• A bug where "RuntimeError: failed to get urandom" was being raised upon importing attempt on Synology.
• Fixed a bug where Google Takeout import was failing due to unsupported date format with milliseconds in the file.
• Stats distance calculation now correctly calculates the daily distances.
• New app version is now being checked every 6 hours instead of 1 day and the check is being performed in the background.

Removed​

• Owntracks' .json files are no longer supported for import as Owntracks itself does not export to this format anymore.

Conclusion​

That's it for the October 2024 monthly update! I hope you enjoyed the news and changes. If you have any questions or suggestions, feel free to reach out to me on Twitter or Mastodon.

You can also support the project by sponsoring it on Patreon, Ko-Fi or Github Sponsors ✨

Thank you and see you in the next monthly update!

As you probably already know, Google discontinuing the web version of its Location History / Timeline service by December 1st, 2024. Here are some dry facts:

• Starting December 1st, 2024, the web version of Timeline will no longer be working
• Timeline data will now be stored on the user's device instead
• Users’ last 90 days of location data will be transferred to the first device they sign in with after December 1, but any data older than this will be deleted unless saved
• Users can manually backup Timeline data to Google’s servers for device restoration, but it will not be the default

The transition offered by Google is far from perfect: some users already have reported they have lost years and years of their location history data.

The least you can do is to export your data from Google. You can do it either using Google's Takeout feature or by navigating to Timeline -> Backup in your Google Maps application. Either way, in the end, you will receive an archive with your location history, hopefully, for the whole time you have been tracking it.

What's next?​

That's where Dawarich comes in very handy. Although Google lacks consistency when it comes to the export file format, Dawarich already supports all three (3) kinds of files that you can get from Google.

Google Takeout​

If you requested your data using Google Takeout, you might end up with two different types of files: Semantic Location History, and Records.

Semantic Location History is a bunch of files, split into yearly directories, and named after a year and a month, for example: Semantic Location History/2022/2022_APRIL.json. There will be a file for each month of location history data. This kind of file is the detailed one, and aside from coordinates and timestamps it usually might also contain addresses, suggested by Google, means of transportation, and so on.

To import Google Semantic Location History files, you just need to navigate to the Imports page of Dawarich, select "Semantic Location History" as a Source, select your files (you can select multiple files at once), and hit "Create import". Dawarich will upload the files, save their contents in the database, and then start creating points in the background. After a few seconds (or minutes, if you have lots of files) the data will be imported and you will receive a notification in Dawarich UI.

Records.json is the second type of file you might receive with your Google Takeout Archive. It usually only contains coordinates of geopoints and timestamps of where you've been there, but it also holds a lot more geodata than Semantic Location History files. Because of this, these kinds of files tend to be a lot heavier and should not be imported via the web interface. Instead, you'll have to complete a series of steps.

1. Upload your Records.json to your server, where you host Dawarich
2. Copy the file to the tmp folder of Dawarich:

docker cp Records.json dawarich_app:/var/app/tmp/imports/Records.json

3. ssh into Dawarich container: `docker exec -it dawarich_app sh
4. Run the importing command:

bundle exec rake import:big_file['tmp/imports/Records.json','user@example.com']

The process will take some time, depending on the size of your file, so let it work. Once the file is processed, all points from it will be queued for background import, which will also take some time. You can monitor the stats of the importing process on the Sidekiq page of your Dawarich instance: https://your.host/sidekiq.

Location history on your device​

If you can't retrieve your location history via Google Takeout, you'll probably be able to do that directly on your mobile device. The instructions on how to do that are available on Google Answers.

When you receive the file with your exported data, you can import it using the Imports page of Dawarich. The process is similar to Semantic Location History kind of files, the only thing you have to do differently is select "Google Phone Takeout" as the source of data before uploading it.

In the end​

There, you have it! If you still haven't exported your location history data, do it ASAP, before it's completely gone, and import it to your instance of Dawarich.

This is the first monthly update of the project. It will be published in the end(-ish) of each month and will contain the most interesting news and updates of the project.

News​

Believe it or not, in the beginning of the month, there was less than 900 stars on the GitHub repository. But now, there are almost 2000 stars! The post on the 0.12.0 release on Reddit was very popular and it helped to attract more attention to the project. Shortly after that post, someone posted a link to Dawarich repo on HackerNews and lots of people visited the project page from there. The project is growing and it's very exciting!

Important features and changes​

Miles​

Dawarich now supports miles! To switch to miles, provide DISTANCE_UNIT environment variable with value mi in the docker-compose.yml file. Default value is km.

It's recommended to update your stats manually after changing the DISTANCE_UNIT environment variable. You can do this by clicking the "Update stats" button on the Stats page.

⚠️IMPORTANT⚠️: All settings are still should be provided in meters. All calculations though will be converted to feets and miles if DISTANCE_UNIT is set to mi.

  dawarich_app:
    image: freikin/dawarich:latest
    container_name: dawarich_app
    environment:
      ...
+     DISTANCE_UNIT: "mi"
  dawarich_sidekiq:
    image: freikin/dawarich:latest
    container_name: dawarich_sidekiq
    environment:
      ...
+     DISTANCE_UNIT: "mi"

Default time range on the map​

The default time range on the map is now 1 day instead of 1 month. It will help you with performance issues if you have a lot of points in the database.

The GPX and GeoJSON export release​

⚠️ BREAKING CHANGES: ⚠️

Default exporting format is now GeoJSON instead of Owntracks-like JSON. This will allow you to use the exported data in other applications that support GeoJSON format. It's also important to highlight, that GeoJSON format does not describe a way to store any time-related data. Dawarich relies on the timestamp field in the GeoJSON format to determine the time of the point. The value of the timestamp field should be a Unix timestamp in seconds. If you import GeoJSON data that does not have a timestamp field, the point will not be imported.

Example of a valid point in GeoJSON format:

{
  "type": "Feature",
  "geometry": {
    "type": "Point",
    "coordinates": [13.350110811262352, 52.51450815]
  },
  "properties": {
    "timestamp": 1725310036
  }
}

Changelog​

Since I already posted about the 0.12.0 release, I will not go into details about it. Instead, I'll tell you about the changes that were made after that release.

Since Dawarich is being actively developed, there are always lots of moving parts. I encourage you to check the releases page regularely to see all the changes that were made. All breaking changes and ways to mitigate them are always described in the release notes.

Added​

• GET /api/v1/health endpoint to check the health of the application with swagger docs
• PATCH /api/v1/settings endpoint to update user settings with swagger docs
• GET /api/v1/settings endpoint to get user settings with swagger docs
• GET /api/v1/points response now will include X-Total-Pages and X-Current-Page headers to make it easier to work with the endpoint
• "Slim" version of GET /api/v1/points: pass optional param ?slim=true to it and it will return only latitude, longitude and timestamp
• 7 new tile layers to choose from. Now you can select the tile layer that suits you the best. You can find the list of available tile layers in the map controls in the top right corner of the map under the layers icon
• The Pages point now shows total number of points found for provided date range
• Links to view import points on the map and on the Points page on the Imports page
• Support for miles. To switch to miles, provide DISTANCE_UNIT environment variable with value mi in the docker-compose.yml file. Default value is km
• GeoJSON format is now available for exporting data
• GPX format is now available for exporting data
• Importing GeoJSON is now available
• Missing page and per_page query parameters to the GET /api/v1/points endpoint swagger docs
• Resource limits to docke-compose.yml file to prevent server overload. Feel free to adjust the limits to your needs

deploy:
  resources:
    limits:
      cpus: '0.50'    # Limit CPU usage to 50% of one core
      memory: '2G'    # Limit memory usage to 2GB

Changed​

• GET /api/v1/points will no longer return raw_data attribute for each point as it's a bit too much
• GPX export now has time and elevation elements for each point
• Default value for RAILS_MAX_THREADS was changed to 10
• Visit suggestions background job was moved to its own low priority queue to prevent it from blocking other jobs.
• Default time range on the map is now 1 day instead of 1 month. It will help you with performance issues if you have a lot of points in the database
• The Points page now have number of points found for provided date range
• Ruby version updated to 3.3.4
• Visits suggestion process now will try to merge consecutive visits to the same place into one visit
• Default exporting format is now GeoJSON instead of Owntracks-like JSON. This will allow you to use the exported data in other applications that support GeoJSON format
• A notification about an existing import with the same name will now show the import name
• Export file now also will contain raw_data field for each point. This field contains the original data that was imported to the application
• Map settings moved to the map itself and are available in the top right corner of the map under the gear icon

Fixed​

• Deleting points from the Points page now preserves start_at and end_at values for the routes
• Visits map now being rendered correctly in the Visits page
• Fixed issue with timezones for negative UTC offsets
• Point page is no longer reloads losing provided timestamps when searching for points on Points page
• Optimize order of the dockerfiles to leverage layer caching by @JoeyEamigh
• Add support for alternate postgres ports and db names in docker by @JoeyEamigh
• Creating exports directory if it doesn't exist by @tetebueno
• Link to Visits page in notification informing about new visit suggestion
• The Imports page now loading faster
• Fixed a bug preventing the application from starting, when there is no users in the database but a data migration tries to update one
• Fixed a bug where the confirmation alert was shown more than once when deleting a point
• Importing geodata from Immich will now not throw an error in the end of the process

Conclusion​

Phew, that was a lot of changes! With every release it always feels like not much was added or changed, but when you look back at the changelog, it's always a surprise how much was done in a month.

I'd also like to thank everyone who contributed to the project in any way, whether it was a bug report, a feature request, a pull request, or just a kind word. You are the ones who make this project better every day. Thank you!

If you're feeling generous, you can support the project by sponsoring it on Patreon, Ko-Fi or Github Sponsors ✨

Thank you and see you in the next monthly update! More exciting stuff is coming soon! 🚀