Location Data Formats Explained

Location Export Formats Explained: JSON vs KML vs Others – What TimeTrack Pro Uses in 2026

When Android exports your location history, it offers two primary formats: JSON (the modern, structured default) and KML (the older, map-focused format originally built for Google Earth). TimeTrack Pro supports both, but they are not interchangeable. JSON contains far more metadata and unlocks almost every core and planned feature of the app, while KML is more limited and best suited for basic route visualization in other tools. This exhaustive guide explains every detail of both formats as they exist in 2026 (Android 14–16, direct exports, Google Takeout, manufacturer variations), compares them field-by-field with real export examples, shows exactly what data is present or missing, covers file structure, size, parsing speed, import performance in TimeTrack Pro, compatibility with future features (distance calculation, speed analysis, transport mode detection, altitude graphing, heatmap view, most-visited-places list, year-in-review summary), provides decision trees for every use case (commute logging, tax mileage proof, travel journals, fitness tracking, legal/alibi documentation, family safety review, productivity analysis, routine auditing), includes conversion methods when you only have one format, discusses privacy/security implications, lists format-specific import problems with fixes, and ends with best-practice recommendations to always maximize data quality and app functionality. All information is accurate as of January 2026.

1. Quick Executive Summary – JSON Is the Clear Choice for TimeTrack Pro

Direct device exports (Settings → Location → Timeline → Export) on nearly all Android 13+ phones now default to JSON. JSON is richer in metadata, faster to parse, more future-proof, and enables the full power of TimeTrack Pro. KML is still available via Google Takeout or older exports, but it omits critical fields that make the app truly useful. Unless you specifically need KML for Google Earth compatibility or have no access to JSON, always choose JSON.

Aspect JSON (2026 direct export default) KML (Takeout or legacy) Winner for TimeTrack Pro
Metadata depth Extensive: timestamp (millisecond), lat/long (full precision), accuracy radius (meters), altitude (meters), velocity (m/s), heading (degrees), activity type (still, walking, in vehicle, on bicycle, tilting, unknown), sometimes inferred place name/confidence Limited: timestamp (second precision), lat/long, basic altitude, path lines JSON – unlocks copy-time, search, future stats
File size (1 year typical) 50–400 MB (text-based, compressible) 20–150 MB KML smaller, but JSON worth the size
Import speed in TimeTrack Pro Fast (structured JSON parsing) Slower (XML parsing overhead) JSON
Copy-time feature Full millisecond precision timestamps Basic second-level timestamps JSON
Future features support (distance calc, speed analysis, mode detection, altitude graph, heatmap) Yes — velocity, activity, accuracy, altitude all present No — missing velocity/activity/accuracy JSON
Search & filtering Fast and accurate (structured fields) Limited (basic timestamp/location) JSON
Best for Detailed analysis, mileage proof, routine tracking, productivity hacks, legal/alibi notes, family safety, fitness logging Simple route visualization in Google Earth or basic maps JSON for 95%+ of users
Availability in 2026 Default in direct device export on almost all devices Takeout option or older direct exports JSON easy to get

Strong 2026 recommendation: Use JSON from direct device export whenever possible. It unlocks one-tap copy-time, precise search, future stats and visualizations, and maximum analytical power. Reserve KML for occasional Google Earth route views or if JSON is unavailable on your device.

2. Field-by-Field Comparison – What You Actually Get (or Lose)

Here is a detailed breakdown of every field commonly present in real 2025–2026 exports:

Field JSON (direct export example) KML (Takeout example) Why it matters in TimeTrack Pro
Timestamp 2026-01-25T14:32:45.123Z (millisecond precision) 2026-01-25T14:32:45Z (second precision) JSON enables exact copy-time (HH:MM:SS.mmm) for logs, proof, journals
Latitude / Longitude 51.507445, -0.127765 (full double precision) 51.507445, -0.127765 Equal quality
Accuracy radius (meters) 48 (integer) Not present JSON shows reliability — critical for legal, tax, alibi use
Altitude (meters) 32.5 (when available) Sometimes (basic value) JSON supports future altitude graphs and elevation analysis
Velocity (m/s) 12.4 (when moving) Not present JSON enables future speed analysis, mode detection
Heading (degrees) 187 (direction of travel) Not present JSON helps future route direction visualization
Activity type / confidence "in vehicle" (95% confidence), "walking" (80%), etc. Not present JSON unlocks transport mode filtering and stats (future)
Inferred place name / semantic label Sometimes ("Home", "Office", "Tesco") Not present JSON makes search, most-visited-places, and labeling easier
Path / route lines Not present (point-based only) Yes (continuous ) KML better for Google Earth route playback

JSON provides 5–10× more usable data fields than KML. This gap is why TimeTrack Pro strongly favors JSON — it enables precise timestamp copying, reliable search, future analytical features, and richer filtering/visualization.

3. Export Availability & Default Format in 2026 – By Device & Skin

Direct device export (Settings → Location → Timeline → Export)

  • Stock Android 15/16 (Pixel 9/9 Pro, Nothing Phone 3, Fairphone 5): JSON default
  • Samsung One UI 7/8: JSON default
  • Xiaomi / Poco / Redmi HyperOS 2: JSON default
  • OnePlus OxygenOS 15/16: JSON default
  • Realme UI 6 (ColorOS base): JSON default
  • Huawei HarmonyOS 4/5 (no Google): Proprietary format (not JSON/KML – conversion may be needed)
  • GrapheneOS / CalyxOS / LineageOS: No Google Timeline – manual log export via ADB/logcat or microG if installed

Google Takeout (takeout.google.com)

  • Offers both JSON and KML
  • JSON richer for recent data
  • KML useful for legacy route visualization

4. File Size, Import Speed, and Performance Comparison in TimeTrack Pro

JSON

  • Size: 50–400 MB per year (text-based, compressible)
  • Import time: 10–90 seconds for 1 year on mid-range 2025–2026 phones
  • Parsing: Structured key-value → very fast search/copy-time
  • Large-file tip: Export 3–6 months → import sequentially to avoid freezes

KML

  • Size: 20–150 MB per year (XML-based)
  • Import time: 30–180 seconds (XML parsing slower)
  • Parsing: Hierarchical → less efficient for metadata extraction
  • Large-file tip: Better for very long histories if you only need basic route view

5. Use Case Decision Tree – Which Format Should You Choose?

Use JSON if any of these apply:

  • You want one-tap copy-time timestamps for logs, proof, journals
  • You need search by place/time/activity (future features)
  • You plan to use future stats (distance traveled, speed profiles, mode detection, altitude graphs)
  • You are logging mileage for tax/freelance deductions
  • You need reliable legal/alibi evidence (accuracy + velocity)
  • You want productivity/routine analysis (time at locations)
  • You care about family safety/elderly monitoring patterns
  • You want fitness tracking (running/cycling/hiking routes)

Use KML if:

  • You only need basic route visualization in Google Earth or similar tools
  • You have very old data only available in KML
  • File size is a major concern (KML smaller)
  • You do not plan to use advanced TimeTrack Pro features

Hybrid strategy (best of both):

  • Export JSON monthly/quarterly for detailed analysis in TimeTrack Pro
  • Export KML yearly via Takeout for route overview in Google Earth

6. Conversion Workarounds – If You Only Have One Format

KML to JSON conversion

  • Use free online tools in incognito mode (e.g. mygeodata.cloud/converter/kml-to-geojson)
  • Python script (xml.etree.ElementTree to parse placemarks → output JSON)
  • Limitations: velocity/activity/accuracy lost forever

JSON to KML conversion

  • Tools like geojson.io or GDAL/ogr2ogr
  • Lossy — drops all non-coordinate fields

Best practice: avoid conversion. Export JSON directly from device whenever possible — no data loss.

7. Privacy & Security Comparison Between Formats

JSON

  • More sensitive fields (velocity, activity, accuracy) — higher risk if file leaked
  • Enable TimeTrack Pro encryption immediately after import
  • Delete original export after successful import

KML

  • Less sensitive (basic coordinates + timestamp) — lower risk
  • Still encrypt in app if concerned

Both formats: stay on your device. TimeTrack Pro never uploads anything. Use airplane mode during import/review for maximum isolation.

8. Format-Specific Import Problems & Fixes in TimeTrack Pro

JSON-specific problems

  • Large file freeze/crash → export smaller date ranges
  • Missing fields (velocity/activity) → older export — use recent data
  • Parsing error → corrupted download — re-export

KML-specific problems

  • No accuracy/activity → limited features (expected)
  • XML parsing error → invalid KML — re-download from Takeout
  • Slow import on large files → normal for XML — use smaller ranges

9. Best Practices Checklist – Get the Most from Your Exports

  1. Default to direct device export → always choose JSON
  2. Use Takeout only for full archives → prefer JSON download
  3. Export small ranges (1–3 months) → faster import, less risk
  4. Verify data exists first in Google Maps Timeline
  5. Enable TimeTrack Pro encryption for sensitive periods
  6. Backup original exports offline (encrypted drive/SD card)
  7. Test import with small file first on large histories
  8. Keep phone updated — export format improvements happen regularly
  9. Document export dates — helps track coverage
  10. Delete old exports after import — free space & reduce risk

10. Summary & Final 2026 Recommendation

JSON is superior in every way that matters for TimeTrack Pro: richer metadata, better feature support, faster import, future-proof for stats/visualizations/mode detection. KML is legacy and limited — use it only for Google Earth routes or if JSON is unavailable. Prioritize direct device JSON exports, fall back to Takeout JSON when needed, keep ranges small, and encrypt sensitive data. Your location history stays completely private, offline, and maximally useful.

Having issues with a specific export format or device? Email [email protected] with model, Android version, format used, and problem details — direct, personal support available.