Activity route: where the recording placed movement
An activity route is the line produced from location samples accepted during a Walk or Run. It helps describe the path and supports metrics such as distance, duration and pace.
The line is an estimate rather than a surveyed path. Buildings, tree cover, tunnels, device conditions and permission interruptions can create offsets, gaps or jumps.
Territory polygon: an evaluated virtual area
When route geometry closes around an area, Marchh can evaluate the covered shape for territory. A polygon is the area representation that results when the activity satisfies current geometry, location, integrity and territory conditions.
A recorded activity and a created territory are therefore not interchangeable. An activity can finish successfully without producing an eligible polygon.
Ownership on a shared map
Territory ownership associates a qualifying virtual area with an account in Marchh. The shared map gives that state context: other participating users may be able to see territory and its ownership rather than each result existing only as a private route record.
Where a visible map object is associated with a user profile, read that association as Marchh account context. It does not identify a landowner or prove who may enter the physical place.
Overlap can change the resulting shape
A new covered area may meet territory already represented on the shared map. Marchh can evaluate those relationships and may reject or modify a result under the current overlap and ownership mechanics.
The service does not publish every priority rule, threshold or validation signal. The live map state is authoritative for the product result, and ownership can change as the system evolves.
Virtual geography versus the real world
Routes, boundaries and ownership in Marchh are virtual. They do not create property, access, privacy, exclusion or enforcement rights over any physical location.
Use real-world signs, lawful access and your own judgment. Marchh is not a hiking, trail, emergency or turn-by-turn navigation service, and an on-screen area never justifies trespass or unsafe movement.
A simple way to inspect an outcome
First identify the activity route, then check whether a separate territory area was created. Review any ownership association in the shared map context, and remember that overlap or validation can make the territory differ from the path's apparent outline.
If the route itself looks inaccurate, troubleshoot permissions and recording conditions. If the route is present but no territory appears, review closure and eligibility guidance rather than assuming the activity was lost.
When the map and your surroundings disagree
Treat the physical environment as authoritative. A route line can be offset, a territory edge can cross a building on screen, and map data may not reflect a current closure or access restriction.
Do not use the Marchh map to decide whether land is public, a crossing is open or a route is safe. Report a technical concern through Support, but never test a questionable boundary by entering a restricted or hazardous place.
Questions people ask
Is a route the same as territory?
No. A route describes recorded movement; territory is a separate virtual area created only when a route qualifies under current rules.
Does Marchh territory represent physical ownership?
No. Marchh territory exists only inside the service and creates no ownership or access right over real land.
