Checkpoints
Meaningful points attached to Tracks, Routes, or your library
A Checkpoint is a meaningful point captured at your current GPS fix. Its coordinate is taken when the creation sheet opens, not when you press save, so you mark the place you are standing and describe it afterwards.
Ownership follows how it was made. Created during a Track it belongs to that Track; created on its own it is a standalone personal Checkpoint. Saving a Track as a Route copies its Checkpoints, which is why a point can exist twice and why editing the Route copy never changes the original.
Checkpoints are yours rather than Crew objects, so they are not published to a Crew the way a Marker is. Creating and editing them are server writes that need connectivity, and a usable GPS fix is required — without one there is nothing to capture.
Photos and an arrival radius can be attached. Arrival detection follows the same partial background pipeline as Marker arrivals and depends on Always location, notifications, and accuracy.
How to Add a Checkpoint
During a Track, tap ADD CHECKPOINT. Without a running Track, use the available Checkpoint creation surface when presented. STALKR captures the current GPS position when the sheet opens.
How Track and Route Checkpoints Differ
A Track Checkpoint belongs to that recorded Track. Saving the Track as a Route copies its Checkpoints; deleting or renaming the Route copy does not change the original.
Checkpoint Photos and Arrival Alerts
Open a Checkpoint to add photos or enable an arrival radius. Photos require connectivity; background arrival behavior requires Always location, notifications, accuracy, and OS execution.