location_log

Build and maintain a single master location file in browser cache, then visualize and export it.

File and Import

Step 1. Create or Load Master File

Start by creating an empty location_log.geojson or uploading an existing one.

Step 2. Add New Data

Upload Strava, Google Timeline, Arc exports (including .json.gz samples), and other supported formats. New points are appended; duplicates are ignored.

Step 3. Review and Manage Master File

Last updated: Not set yet

Cache size estimate: 84 B

City Completion

OSM streets, ranked places, incomplete streets, and route planning.

Feature Coverage

Current status against the walk-every-street requirements.

4 present | 5 partial | 2 planned

Generic project scope

partial

City queries and custom imported traces are generic; persisted multi-project records still need a database model.

GPS import

present

Imports GPX, TCX, FIT, GeoJSON, CSV, Strava ZIPs, Arc JSON/GZIP, and Google/Timeline JSON without dropping non-walking activity types.

Walking filter

present

Activity metadata is preserved and views can switch between all movement, walking only, non-walking, and unknown activity.

Master export and backup

present

Browser cache, IndexedDB fallback, restore snapshots, GeoJSON, CSV, GPX route export, and PNG export are available.

Completion map

partial

OSM streets can be fetched for a queried place and compared against filtered traces; segment-level audited evidence is not database-backed yet.

Area progress

partial

OSM neighborhoods/local areas are ranked when available; configurable administrative hierarchies still need persistent GeographicArea records.

Route planning

partial

Manual waypoint planning, walking-route snapping, saved routes, GPX export, and cleanup-cluster route starts are available.

Review queue and audit log

partial

City completion results now generate a local review queue with persisted accept/reject/cleanup/inaccessible decisions and an audit trail.

Network versioning

planned

The current OSM fetch is ad hoc; baseline network versions and approved migrations need PostGIS-backed storage.

Cleanup clustering

present

Remaining streets are grouped into geographic cleanup clusters with distance, route estimate, efficiency, focus, and route-start actions.

Offline/live walking mode

planned

Current-location controls exist, but offline queueing, mobile live completion, notes, and photos are not implemented yet.

Import diagnostics

  • Enable high-confidence mode for cleaner route geometry.