Route and metrics come from location samples
Marchh processes accepted GPS points to calculate running activity information. Device hardware, satellite visibility and the surrounding environment can affect the line and its metrics.
No GPS app can guarantee a perfectly measured route, pace or distance.
Background recording needs permission
Marchh may continue an intentionally started run while the app is in the background or the phone is locked when the necessary location permission is granted.
Battery and operating-system background settings can interrupt recording. Confirm them before a longer run.
Closed geometry adds a shared result
If accepted route geometry returns around and meets eligibility rules, Marchh can calculate a covered area and virtual territory.
That territory changes a shared map. It does not replace deeper athletic analytics or guarantee a claim.
Use the route record for context
A GPS trace can help a runner remember which streets formed a session and how pace and distance were calculated. It should be interpreted alongside conditions, signal quality and the runner's own knowledge of the route.
When territory is created, the polygon adds a game state. It does not make the underlying metrics more exact.
Questions people ask
What can reduce running GPS accuracy?
Buildings, trees, terrain, tunnels, device hardware, operating-system behavior, signal interference and limited satellite visibility can all affect measurements.
Does every activity create territory?
No. A completed activity does not guarantee a claim. Route geometry, location quality, activity integrity, territory conflicts and other Marchh validation rules can affect eligibility.
