GPX, KML and GeoJSON
Whatever your GPS unit, your old mapping tool or your county GIS office produced. Elevation comes along when the file carries it, and is filled in from open elevation data when it does not.
Trails and networks
Start from the files you already have
Most organizations arrive with a folder of GPX exports and a map on a wall. Bulk import takes the folder, and what comes out the other side is a trail record your crew works against and your visitors read.
Getting your trails in
Bulk import, not sixty separate uploads
The import reads the three formats a trail organization actually has, and it will take a whole folder at once rather than making somebody sit through one file at a time.
A folder at a time
Drop in every file at once and name them as they land. A season of exports becomes a network in one sitting.
Or record it by walking it
No file at all is a fine starting point — the field app records a line while somebody walks or rides it, and saves it as a trail when they get back.
Length and grade, measured
Distance, ascent, descent, average grade and the steepest pitch are computed from the line itself, over a fixed window, so two trails can honestly be compared.
It exports, too
Trails export as GPX. Your lines stay yours, and nothing here is a one-way door.
Points come with it
Waypoints in an imported file become points of interest on the trail rather than being dropped on the floor.
How it is organized
Trails, networks, areas — in that order
A trail is the line. A network is the set somebody rides in one visit. An area is the ground a network sits on. Conditions, downloads and public pages all work at whichever level makes sense.
01
The trail carries its own character
Difficulty, surface, direction of travel, the season it is open, who it is for, and a color it draws in on every map. Set once, read everywhere.
02
A network groups what belongs together
The trails on one hillside, in one park, under one trailhead. A network is what a visitor picks on your public site and what a crew member downloads before leaving signal.
03
An area rolls networks up
Close an area for mud season and the networks and trails under it inherit the closure, with a note saying why — rather than somebody editing forty rows by hand.
04
Visibility is per trail
Public, or not. A trail still being built, a sensitive reroute or a private landowner agreement stays off the public site and out of the report app's picker while your crew keeps working it normally.
Working with people outside your team
Lend one trail to a builder, not your whole organization
A contractor hired for two trails should get two trails. Trail sharing hands over exactly that — the trail stays yours, the guest gets a read-only view of it, and optionally the maintenance on it.
A loan, and it says so
The screen that accepts a share says in as many words that this is borrowed rather than copied, before anybody accepts. Nobody should build a season of work on ground that can be withdrawn without knowing that is what it is.
They can work the maintenance
Optional per share. A builder files and resolves items on the lent trail and their work is labeled with their company on your issue — so a month later you can still tell who did what.
Withdrawn means withdrawn
Take the share back and the trail stops being viewable and stops being downloadable in the same moment. A copy already on a phone in a valley expires on its own within a fortnight.
In the documentation
How this works, in detail
Step-by-step guides for setting each of these up.
Bring the folder
Import what you have on the free plan and see your network on a map this afternoon.