DOCUMENT ID: RELNOTES-2026-09-30 · Rel 2.7a
Group communication and ride sharing · 30 September 2026
GroupTrack is complete as installed, and 2.7a adds your community. It is two products in one: a complete personal navigation product that lets you share rides and maps with other GroupTrack users, and a true situational awareness product for your group on the trail.
Trails and maps on your device, working with no signal; a planner that builds routes for you to compare; waypoints, map downloads and your own track recordings. Manual: The Ride Planning Map
One ride holds the route, the trailhead, the date and time, the maps to download and the mesh radio configuration. Send it in one click; your friends open it in one click — and ride anywhere off grid in total confidence. Manual: ★ Create a Ride
Your rider profile — callsign and email — is who you are in GroupTrack. It is private: it stays on your tablet, nothing is sent to GroupTrack, and it goes only to the riders you ride with. Manual: Your rider profile
Add a Meshtastic radio — any Meshtastic radio, not only the T1000-E — and you see your group on the map with no cell service. GroupTrack sets the radio up for you. Manual: Group Awareness
For the organizer it is one step: build the ride and send it.
NEW Three one-time steps. (1) Your rider profile — GroupTrack asks for it the first time it opens. (2) Update your radio, if you ride with one: 2.7a moves GroupTrack to TAK messaging, so each radio needs the GroupTrack default once. GroupTrack asks at first start — Do you have a mesh radio to use with GroupTrack? — and YES takes you to GRP Awareness to connect it and apply the default. Said NO? Do it before your first ride: GRP Awareness → connect → Select a ride and apply settings to the radio → GroupTrack default. (3) Ride files — the first time you tap one, choose GroupTrack, then Always. New to GroupTrack? The Quick Start walks you through it. Manual: First start
Riding together starts with a ride. GroupTrack's community begins with the ride package — a route, starting at its defined trailhead, on a set date and time, with the maps it needs and its radio configuration. Send it to friends and riders who want to ride with you.
One click, and everyone has the same preparation: the trailhead marked on their map, the route outlined to follow, the required maps downloaded along it. At the trailhead, check-in applies the ride's radio configuration for them. The fastest way to create one is a map touch: tap a route or a track on the Ride Planning Map, then CREATE RIDE — Manual: Map touches, the fastest way to Create a Ride.
No more night before the ride spent downloading an area and hoping the trail goes where you think it does. No one asks where to meet, and no one waits at the trailhead while someone else catches up. Everyone's time goes to riding.
From a route: tap it on the map — CREATE RIDE on the description of a route the planner built, or ADD A RIDE on the detail panel of a route you drew. From a track: CREATE RIDE turns the track into a route (every turn kept) and opens the ride form.
Manual: ★ Create a Ride · Manual: Creating a ride from a route · Manual: Creating a ride from a track
Your callsign and email, asked for once when you first open 2.7a. Change them any time: Settings → Your Profile.
Created the first time you open the ride form, named after you, and used by every ride you organize. A one-off event can have its own.
Every radio GroupTrack sets up reports your position with your callsign in the TAK format — on its own, even with your tablet off.
A ride carries its route, trailhead, waypoints, map imagery and radio settings. Send it from Work with Rides → Rides → Share.
Receive a Ride invite and tap it (the first time, choose GroupTrack, then Always). GroupTrack creates the route, its trailhead and the ride's description, stores the radio settings, and imports the map imagery along the route.
A route is saved with its trailhead — its first point. A Trailhead already there is used; otherwise GroupTrack asks you to name one.
The ride's name, Private ride (off = public), the radio network, the date and rollout time, and the Leader's Notes — the route and its picture last.
One menu for rides: Rides — share, edit, delete · Import a ride · Apply ride to radio / Nucleus · Compare / Apply Archive Configs. Edit a ride before you send it; after sending, change its date and send it again.
A ride leaves the lists 30 days after its date, but it is kept on your tablet, with its record and its survey.
The red ✔ CHK IN › REC button: pick your ride, your callsign and your role; if your radio is not on the ride's network yet, CHECK IN sets it up first. No radio connected? The button reads ⏺ REC and records a solo ride. The check-in is for group awareness only — riding solo, you never see it.
Manual: CHK IN › REC · Manual: Checking in and recording your track
One of each per ride, claimed at check-in and broadcast to every member. A role someone holds is refused (a red window says who). Change your own at a stop: CHECKIN / SELECT CART → CHANGE MY ROLE.
END names the track after the ride. On a public ride, rate it, say how hard it was and whether you would recommend it, and choose whether to share your track.
Replaces Mesh on both maps: green when your radio is connected, red when not, pulsing as the group is heard. Tap it to connect, pair or forget a radio, see the ride last applied, and apply a ride to a radio.
The carts on the ride's network, Leader, Middle and Tail gunner first. REMOVE takes a cart off your map and out of your group; ACTIVATE brings it back; END brings every cart back.
Shows your radio's interval while moving (for example 4 s) and how busy the channel is: green, yellow or red. Tap to set 3–10 seconds; the radio is set once and reconnects by itself.
The HUD text follows the map — white over satellite, dark over topo — with a crisp outline instead of a blurred glow; the right-hand menu words are plain colour.
2.7a moves GroupTrack to TAK messaging, so every radio used with it needs the GroupTrack default. GroupTrack cannot tell whether you own a radio, so it asks once, before loading your trails: YES opens GRP Awareness to connect, select the GroupTrack default and apply; NO leaves it for later. Pairing code: 123456 by default, or the code a radio with a screen shows. Your callsign becomes the radio's name — set up more radios the same way, each with its own callsign.
GroupTrack connects to, sets up and tracks any radio running Meshtastic — handheld trackers, radios with a screen, base stations, and the Nucleus IP-mesh box — not only the SenseCAP T1000-E. Connect it in GRP Awareness; checking in to a ride, or Work with Rides → Apply ride to radio / Nucleus, sets it up.
Every setting GroupTrack manages is written in steps, read back and ticked. To set up another rider's radio, type their callsign. Radios report every 15 s standing and as often as every 4 s moving.
Radios use MEDIUM_FAST with a 4-second smart interval: the share of airtime each radio uses fell from about 22% to 4–5%.
Tap a waypoint on either map: its detail panel opens, with CHANGE TYPE and delete. A waypoint that is a route's trailhead stays a Trailhead — remove the route first.
Long press on the map: New Waypoint opens with Trailhead chosen; choosing Other asks once.
DOCUMENT ID: RELNOTES-2026-08-29-B
This release is about one thing: the route planner is finished. Tell it where you are starting, how far you want to go and how fast you ride, and it brings back up to six routes for you to compare.
The planner asks one thing at a time. An overview explains what you will get. A second screen sets your distance and pace, and shows the ride duration as you move the sliders — set the mileage until the hours match the day you have.
After that each step puts a short prompt at the bottom of the screen and leaves the map clear to work on. Pick where you will park. Drop pins on places the ride should reach, if you have any in mind. Say whether you are looping back or finishing somewhere else. Then read back what is about to be built, and press Continue to Compare.
The routes are drawn on the map, each in its own colour, next to a table showing what each one covers. Tap a route's name to hide or unhide its line, so you can see one at a time. Tick the ones you want and press Save Selected / Delete Unselected — the ones you do not tick are removed.
Every route the planner builds records the settings that produced it. Open a saved route and press Build Routes From Recipe: it reads those settings back, shows you a summary, and rebuilds. This is how you get back the alternatives you did not keep the first time.
The button only appears on routes the planner built — a route drawn by hand or imported from another app has no settings to rebuild from.
A shared route now carries its description with it. Export one and the summary the planner wrote travels in the file, along with the settings that built it — so whoever you send it to can build their own six routes from your parameters. Routes imported from Gaia or onX bring their descriptions in the same way.
Better trail data. The trails on your device today are selected by shape alone, which means some paved neighbourhood roads come in as trails and some dirt roads you ride do not come in at all. The next release fixes that, and adds trail types you can filter — so you can turn hiking trails off, or see at a glance which parts of a route are on ground built for vehicles.
⚠ One thing to expect when it arrives: your saved routes are safe and will still draw and navigate. But rebuilding one from its recipe may return different alternatives than it does today, because the ground the planner can see will have changed. That is the improvement working, not a fault.
— carried forward —
DOCUMENT ID: RELNOTES-2026-08-29
If you imported the trails for a state other than Utah and GroupTrack closed near the end, this was the reason. The last step checks which trails cross private land, using a land-ownership map — and that map only covers Utah. GroupTrack was downloading it and working through all of it for every state, including ones it could never apply to. On most tablets that ran out of memory right at the end.
It now only does that work for Utah, where the data applies, and it reads Utah's map far more efficiently. If an import of your state stopped before, run it again.
⚠ If the import screen won't start after an import was interrupted — you pick your state and nothing happens — close GroupTrack completely (swipe it away from your recent apps, or use Force stop in Android's app settings) and open it again. A fix for that is coming.
The option to download the maps along with the trails is now switched on when the import screen opens, and easier to read. Untick it if you only want the trails.
If your device has no GPS chip, GroupTrack could not find you at all. Your cart showed its name but no position, and the map opened on a view of the whole country instead of where you were. The app now also asks your network connection for a location, which is how a device without GPS knows where it is.
And it now tells you when that is what is happening. A network location works at home and in the car park. It does not work on the trail, because there is no network out there. If GroupTrack is locating you that way you will see a message saying so once, with the option not to be told again.
⚠ A device with no GPS of its own needs a mesh radio to work off-grid. The radio carries its own GPS, so it answers both problems at once — it knows where you are and it shares that with your group. We recommend the Seeed SenseCAP Card Tracker T1000-E.
If the app cannot find you by any means at all, it now says that too, rather than quietly showing you an empty map.
On topo maps the view jumped in and out every couple of seconds. My Cart was asking to zoom closer than the map has detail for, the map pushed back, and round it went. My Cart now asks for the closest zoom the map you are on actually has — so it settles and stays.
You can still pinch in past that. The picture is enlarged rather than sharper, which is the point: your tracks and waypoints stay crisp so you can place one precisely.
Search an area from the ride map and it used to snap back to your own cart a second or two later. Following your cart is now switched off when a search moves the map, exactly as it is when you drag the map with your finger. Look around as long as you like; tap MY CART when you want to come back, and following starts again.
Searching for a track, route, trail or waypoint by name is unchanged — that opens its details without moving the map, so you stay followed.
Topo maps were downloading two zoom levels the app never draws. Those levels are roughly four times the size of the one below, each, so a topo download was several times larger than it needed to be with nothing to show for it. They are no longer fetched. Satellite is unchanged — it has real detail at every level it offers.
⚠ The estimate shown before a download still counts those levels, so it will read higher than what actually arrives.
In some situations the app could lose track of which map sources it had and fall back to a built-in list that did not include the one you had chosen — which showed up as a blank map on every source. It now reads your actual map settings instead of guessing.
Two paths below. Open the one that applies to you.
GroupTrack needs your location all the time — it is how the app keeps your position on the map and how the convoy sees where you are while you ride. Follow the prompts.
Let it download the trails. It takes around 25 minutes and it only happens once. After that the trails work with no signal, which is most of where you ride.
Do this before you start building routes. Every track you bring in adds its trails to the trail database — so the more of your riding history you import, the more complete your map becomes.
Put your GPX files in Downloads on your Android: save them from an email attachment, or download them straight from your navigation app.
Then tap Import Trails on the Map Features screen from the planning map. You will be asked to pick the files.
To select several files at once, press and hold the first file, then tap the others.
When the app has your location, you are ready to go.
GroupTrack used to keep your trails, tracks, routes and maps in your phone's Documents folder. It now keeps them in its own storage instead.
The first time you open this version it asks you to choose a folder. Choose Documents and allow access. Everything moves across on its own.
Your data takes a couple of minutes. Your maps are handled separately and take longer — a large map store can run up to 15 minutes. Leave the screen open while it works.
Maps need space to move. If there is not enough, GroupTrack tells you, and those maps are deleted — you will need to download them again when you have room. Everything else still moves across.
GroupTrack no longer searches your Downloads folder by itself. Tap Import Trails on the Map Features screen and you will be asked to pick the files you want.
To select several files at once, press and hold the first file, then tap the others.
And this is worth doing with your whole track history. Every track you import adds its trails to the trail database, so bringing in years of old tracks fills out your map in a way nothing else does. Put the GPX files in Downloads first — from an email attachment or straight from your navigation app.
Google restricts which apps may keep files in shared folders like Documents. Rather than ask for an exception, GroupTrack now stores its own data in its own place — which is what the rules are for.
One thing worth knowing: data kept this way is removed if you uninstall the app. Use the share options to keep a copy of any route or track you would not want to lose.
GroupTrack used to keep your trails, tracks, routes and downloaded maps in your phone's Documents folder. It now keeps them in its own storage instead.
The first time you open this version it will ask you to select your Documents folder. Tap it, and everything moves across on its own — trails, tracks, routes, waypoints, your saved colours, and your downloaded maps if there is room for them. If you are new to GroupTrack there is nothing to move and it simply carries on.
Your maps are the slow part. Everything else takes under a minute; a large map store can take several. Leave the screen open while it works.
Google restricts which apps may keep files in shared folders like Documents. Rather than ask for an exception, GroupTrack now stores its own data in its own place — which is what the rules are for.
One thing worth knowing: data kept this way is removed if you uninstall the app. Use the share options to keep a copy of any route or track you would not want to lose.
Set a trail type to the colour, line pattern or thickness you want, and the map draws it that way from the moment it opens — on the ride map and the planning map both. Previously your choices only reached the map after you opened the key panel and changed something, so a setting could appear to revert every time you restarted the app. It was never lost; the map simply was not being told.
Saved routes were drawn with a long dashed line that was almost indistinguishable from a solid one, even zoomed right in. They are solid now, like every other line you can ride, and the key panel matches. Your recorded tracks are still dashed — that pattern is visible and it tells the two apart.
Tapping a trail, track or route on the ride map now opens its detail panel. Tracks in particular were hard to hit — the line is thin and dashed, and zoomed in there was very little to aim at. There is now a wider invisible target along every track, so a tap near the line works. Nothing looks different.
The map key panel has a new CATEGORIES EXPLAINED button at the foot, beside My tracks and My routes. It says in plain words what each trail type is.
Two are worth knowing before you plan on them. Rider trails are ground you have actually ridden, so a machine has been there — a stronger claim than any survey. Forestry / access roads are open unless posted otherwise, so look for a sign at the gate.
If the app was opened while it was busy — during a state import, or the first launch after an update — it could come up showing three map sources instead of the full list, and ignore the ones you had chosen. Restarting was the only cure. It now recovers on its own.
Send a route to another rider and they get the whole thing — the summary, what they will see along the way, the cautions, and the settings it was built from.
Opened in Gaia or onX the route still reads normally; those apps see the name, description and points and ignore the rest.
Tap one of your own rider trails and there is now a DELETE button. Surveyed trails do not have one.
Mostly useful when a recorder was left running on the drive to the trailhead — highways are not in the trail data, so the whole drive comes in as new ground.
It opened a small bubble, or nothing at all. It now opens the full detail panel, the same as the planning map.
Trails, tracks and routes also draw in proper order now — trails widest and underneath, then tracks, then routes — so where all three share ground you can see each of them and tap the one you meant.
If you skip this, the route planner will send you the long way around ground you have already ridden. It cannot use a trail it does not have, and published maps are missing a great deal of what riders actually use.
The order that gets you the best routes:
Already built routes before importing? Rebuild them. They will come back different, and that is the point — the planner can finally see the ground you know.
Published trail data leaves a lot out. Roads and tracks that get ridden every weekend are simply not in it, and until now that ground did not exist as far as the app was concerned.
Tested on one rider's collection: 88 tracks produced 1,872 new trails covering about 2,400 miles of ground that no published source had.
Export every track you have from onX, Gaia or wherever else you have kept them, and import the lot. ⚠ Tracks, not routes. A route is a plan somebody drew; a track is where a rider actually went. Only a track is evidence that the ground goes through.
Load your states first. A ride crossing into a state you have not imported has no trails underneath it, so the whole stretch is treated as new ground even where trails already exist. After that the order does not matter — each track is checked as it arrives.
There is a new ADD TRAILS FROM TRACKS button under RESYNC TRACKS on the import panel. It reads every track you already have and adds whatever ground is missing. Safe to press more than once — a second run finds nothing, because the first one already covered it.
The long stretch in the middle of a state import used to sit on Processing for ten minutes without moving. It now shows what is being worked on and how far through it is.
The import also has a new step of its own — Trails from tracks — which runs after your trail data has loaded and reports how many it added.
Routes you built before will come back different. With more network to work with, the planner finds rides it could not find before. That is the improvement working.
A trail from your ride is honest, not authoritative. It says you rode that ground — not that it is maintained, public, or open to anyone else. Check ownership and access the way you would anywhere else.
The list down the left side of the app belongs to Meshtastic, the radio software GroupTrack is built on. If you ride with a tablet alone, none of it is for you.
Hide Mesh at the bottom of that column folds the whole thing away. A Mesh button then appears with Map Features and Help on the right of either map — tap it to bring the column back. GroupTrack remembers which you chose.
The GroupTrack tab is now GroupTrack Mesh Radio Setup, and the menu behind it is titled the same. Everything in it is radio work and nothing else, so it is clear at a glance whether it concerns you.
Its five entries now name what they do — creating a ride's radio configuration, sending it, importing one, applying it to your radio, and restoring a saved one. The Map Settings section has gone; everything live in it is reachable elsewhere.
Saving several routes from one search used to give them all the same name. They now carry a number — Broken Ridge Route 1, 2, and so on.
The mileage and point count have come out of the name, since tapping a route shows the distance and riding time anyway.
Routes you saved before this keep the names they have.
Tap any route you have saved and it opens with the description of the ride — how far, how long, what you will see, and the stops in the order you reach them. Previously that was three screens away.
The long lists start folded so the distance, the riding time and the warnings are what you see first. Tap a heading to open one.
Two things you can do from there without leaving: Download maps for the route's area, and Route details for the full record.
Routes built before the app started writing descriptions open the details panel as they always did.
Classifying the trails — working out which are motorized and which sit on private ground — is now listed as its own step when a state loads, with its own count. Before, it ran silently at the end and a failure could look like a finished import.
And the summary at the end of an import now waits for you. If you put the phone down while a state loads and come back later, it is still there.
The first launch after installing clears the trail data and asks you to import your state again — about twenty minutes for a large state. A red SYSTEM HOUSEKEEPING message appears while it prepares, and Continue turns on by itself when it is safe.
Your maps, tracks, routes and waypoints are not affected.
Yesterday's Map Keys panel did two jobs. It now does one. Which trails appear is chosen from Map Features › Trails › SELECT — the same place you have always chosen what shows for tracks, waypoints and routes. Everything is in one place instead of trails being the exception.
That panel has the two groups, Motorized and Non-motorized, with a tick beside each type, and a single Include private land option. Untick a type and it goes; tap a heading and the whole group goes. And OFF on the Trails row still hides every trail in one tap when you want the map clear.
It shows what each line means. Tap the name of any type and you can change its colour, its pattern and how thick it draws. The panel shows the line as it is now beside the line as it would be, so you can compare before you commit. Apply, and the map changes.
What you choose is yours and it stays. The colours the app ships with are simply a starting point.
Solid lines are motorized. Dotted lines are not. That is the first thing to read on the map, and it does not depend on telling colours apart in bright sun.
The app now also ships knowing, for every trail, whether it sits on public or private ground and whether it is a motorized route — worked out during the import from the state's land-ownership records and from what each source published. That is what the filter acts on.
Trails used to show a small bubble with a name. They now open the same detail card that tracks and routes do, showing everything the sources published and nothing they did not — the surface, who manages it, any posted restrictions, and where the record came from.
Where a trail carries a roughness rating it is written plainly: "Severe — ATV or tractor" rather than a code. It is only recorded on a minority of trails, but where it exists it is the one thing that tells you whether a machine will get through.
The first launch after installing clears the trail data and asks you to import your state again. It takes about twenty minutes for a large state. This is necessary — the new information about land ownership and trail type is worked out during the import, and it cannot be added to data that is already loaded.
Your maps, tracks, routes and waypoints are not affected. Only trail data reloads.
The app starts by showing motorized trails on public land. Hiking, biking and equestrian trails are hidden, and so is private ground. That is deliberate for an off-road app — but if you are looking for a trail you know exists and cannot see it, that is why. Map Features › Trails › SELECT turns them back on.
The key that explains the colours has become something you can use. It is on the convoy map now as well as the planning map — the convoy map never had one before. On the convoy map it opens from the new Map Keys button, between Map Features and Help.
Inside it, the trail types are grouped into Motorized and Non-motorized, side by side. Every type starts switched on. Unchecking a row hides that type; tapping a column heading hides the whole group.
The panel has one filter at the top: Both, Public, or Private. Choosing Public hides everything that sits on private land — which, near a town, is most of the street grid. If you have been zooming past a mess of residential streets to find the trail you actually want, this is the switch for that.
Choosing Private does the opposite, which is useful when a private road is how you get from one piece of public ground to the next.
Whatever you choose is remembered and applied the next time you open the map.
Anything you can ride is now a shade of blue, and the shade tells you how confident the app is:
Green, yellow, purple and brown are walking, biking and horse trails. Deep pink is a residential road on private land. A red dashed line means the trail is recorded as unofficial or uncertain — worth knowing before you commit to it.
The app now keeps a great deal more of what each source publishes — surface, trail class, which system it belongs to, which agency manages it, and any posted restrictions. None of it is on screen yet; it is being kept so it can be shown, and used for route building, in a coming release.
Some trails that are in the app's records are not drawing on the map. We have confirmed the trail data itself is correct and are tracing where they are being lost on the way to the screen. If you know a trail exists and cannot see it, that is this problem and not your data.
Trail data now carries what the source published about each piece of ground — its type, who manages it, and whether it sits on public or private land. It is what makes the trail filter and the land setting work.
Much of this is groundwork you will not see directly. What you will notice is that tapping a trail tells you more than it used to.
Clearing trail data could lock the app up on startup. It no longer does.
The rest of this release was work on how trail data is brought in and sorted — nothing visible, but it is what the classification and filtering are built on.
Open any route the planner built for you and you will find Build Routes From Recipe under its overview. One press and it rebuilds from the same settings — the same starting point, the same distance, the same points you asked it to cover — and shows you what it is about to do before it runs.
The button only appears on routes the planner built. A route you drew by hand, or imported from somewhere else, has no settings to rebuild from.
If you searched an area, then searched it again without closing the app, the second set of rides could be worse than the first. Points you asked the ride to cover were more likely to be left out. This is fixed — the second search now starts from the same clean slate as the first.
— carried forward from 2026-08-28 —
DOCUMENT ID: RELNOTES-2026-08-28
Planning a route is now a set of screens that ask one thing at a time. Instead of a checklist you read all at once, each step tells you what it needs, you do it on the map, and the next step appears.
Planning stays in portrait throughout, and the map layers are cleared before the comparison so the routes are readable.
— carried forward from 2026-08-27 —
DOCUMENT ID: RELNOTES-2026-08-27
When the planner finds you rides, you can now see them side by side. Ask for routes and the app draws every one it found, each in its own colour, with a table underneath that lines them up against each other.
Trails, tracks and waypoints are hidden so the routes are readable, and put back exactly as you had them when you leave. The map does not switch to route-drawing mode, so tapping a route to look at it will not add points to it.
Leaving without saving keeps everything — the routes are still there next time you tap Route+. Only Save Selected finishes the job. If you tick nothing, the app asks first: all the routes go, and you would have to start the search over.
— carried forward from 2026-08-26 —
V2.6h · in development · RELNOTES-2026-08-26
These notes ship inside the app, so they always describe the build you
are running.
Document revision RELNOTES-2.6h-r2 · 26 August 2026
QuickStart is for a new rider on a first install — getting the app on the phone, permissions, radio pairing, and getting trails onto the map. It is a summary of how things work right now, not a history. It opens by itself the first time you install.
These release notes are for riders who already have GroupTrack. They cover what is new in this release and how to use it, and they open after an update. Earlier releases are kept below under Release history.
The user manual is the walkthrough. Where something new needs more than a paragraph, these notes point at the manual page for it.
What this means to you. Nothing in this build, and that is deliberate. The part of GroupTrack that suggests rides was taken apart and rebuilt this week. It now works properly on the bench — it will offer you several genuinely different rides from where you park, rather than one — but the screens you would use it through are still being finished.
How to use it. You cannot yet. It is listed here so you know it is coming and that the quiet in this area is work, not neglect. Manual: Planning a route — link pending anchors
What this means to you. When someone emails you a GPX file and you tap it, everything in it comes across — the tracks, the waypoints and the routes. Before, only the tracks arrived and the rest were dropped without saying so, which is why a file could look like it imported nothing. If you learned to save files to Downloads first as a workaround, you no longer need to.
How to use it. Tap the attachment in your email and choose GroupTrack. Importing from Map Features → IMPORT TRACKS, WAYPOINTS & ROUTES still works and gives the same result. Manual: Importing files — link pending anchors
What this means to you. If you loaded your state and found the trails gone again a day or two later, that is fixed. It was a one-time cleanup that kept running every time the app opened instead of once. You should not have to load a state twice.
How to use it. Nothing to do. If your trails are missing right now, import your state one more time and it will stay. Manual: Loading trails for your state — link pending anchors
What this means to you. Nothing yet. Work is going on behind the scenes to let GroupTrack suggest rides from your trail data, and to let you mark places a ride has to reach. It is not finished and is not something to rely on in this build. It is listed here so you know it is coming, not so you can try it.
KNOWN A state import can stop partway. Some sources finish and the rest never start. Your trail count still looks reasonable, so nothing appears wrong — but the largest source, Open Source Maps, is usually the one that did not run, and it carries most of the trail network.
What it looks like: route building offers one route where you would
expect several, or comes back well short of the distance you asked for. The map still shows
plenty of trails, which is what makes it confusing.
What to do: run the state import again. Trails already on your device are skipped, so
only what is missing is fetched and nothing is duplicated.
KNOWN Route planning near a town suggests roads. The trail data GroupTrack imports contains roads as well as trails, and it cannot yet tell them apart. Planning from a staging point inside a town will offer you rides that follow streets.
What to do: plan from where the trails actually start — a trailhead or a parking area out of town. Work to separate roads from trails in the imported data is underway.
KNOWN An import record can be opened by the wrong import routine. The record left behind by a run is picked up by an older code path than the one that wrote it, so a run can be misread afterwards — and a stopped import may be reported inaccurately. Being fixed by pointing the existing routine at the current one rather than leaving two.
KNOWN Some trail sources report errors on every record in some areas. Affected in some areas and not others; under investigation. The per-source counts on the completion screen are what make it visible.
KNOWN A state may be listed for your area without having trails in it. States are matched using a rectangle around each state and those rectangles overlap. It costs download time; it does not affect your data.
KNOWN Re-importing the same state on the same day replaces that day's earlier import record.
Earlier releases, newest first. Each one shows what changed at the time.
Release date: In development · Branch: feature/convoy-event-ride
FIX GPX files containing routes or waypoints now import. Previously only the tracks in a file were read — routes and waypoints were skipped without any message, so a file that contained them appeared to import nothing.
This affects files shared between riders, and exports from other apps.
HOW TO IMPORT
Save the file to your Downloads folder first, then open Map Features on the Ride Planning Map and choose IMPORT TRACKS, WAYPOINTS & ROUTES.
Tapping a GPX attachment directly in your email will not import routes yet — it still reads tracks only. Save it to Downloads and import it from Map Features instead. This is being worked on.
Note: the file is removed from Downloads once it has been imported.
FIX US Geological Survey National Trails now imports. Every record from this source was failing, in every state, and the source appeared simply to have no data for your area. It was reading the wrong field names from the service. In New Hampshire it now brings in 390 trails where it previously brought none.
NEW Import Trails now asks how you want to choose your ground. One button on the Map Features panel, two ways in:
Either way there is no source checklist. Every source that covers your ground runs, because that is what lets one source fill in what another is missing.
NEW Every import now records what happened to each record, not just how many were added. Per source: how many were read, how many fell inside your state or area, how many you already had, how many were added, and how many could not be processed.
The summary still shows one number — records added. The detail sits behind the source name if you want it, and it is written into the import record on your device either way, so it can be looked up later.
CHANGE Each import run now carries an identifier, so a run can be identified exactly when something needs looking into.
NEW One-tap trail data setup on first launch. When GroupTrack detects no trail data, it offers to load your home state's trails automatically:
NEW Shipped geofabrik_states.json — 54 entries with download URLs for every US state and territory. Supports the automatic Geofabrik GPKG download (302 redirect handling included). Refreshable via update_geofabrik_states.py.
NEW release-assets/ folder in the repo. Holds dated docs (manual, release notes, quickstart) and two Python scripts. One command (python release-assets/prepare_release_assets.py) refreshes Geofabrik URLs, copies newest dated docs to app assets, and verifies markers.
CHANGE Plain-language source names throughout — no unexplained acronyms:
FIX Geofabrik -latest- URL 302 redirect now followed automatically.
FIX GPS state detection at border areas (NH/MA) now uses Android Geocoder instead of bbox matching.
FIX OSM import ledger creation before pending bbox set (prevented silent import failure).