Route planning with Atomic Metrix: describe the ride, get the route

Route planning in Atomic Metrix starts with plain language. You describe the ride you want, and Atomic turns that intent into a cycling route with waypoints, distance, elevation, surface information, GPX export, and follow-up actions.

You do not need to know coordinates, GPX formatting, or map software syntax. The useful input is the same thing you would tell a teammate: where you want to start, where you want to go, whether you want to come back, how long the ride should be, and what kind of roads you prefer.

What you can ask for

Atomic can plan simple point-to-point rides, round trips, and multi-stop routes. You can ask for a destination, a loop distance, a food stop, a terrain preference, or a change to an existing route.

For example, you can say: "Plan a 60 km endurance loop from Illini Union, mostly flat, with a coffee stop." You can also be more specific: "Ride from Illini Union to Homer Lake Forest Preserve, stop at fast food in Homer, then return."

The planner handles both named places and exact businesses. If you ask for a restaurant, cafe, store, or fast-food stop, Atomic searches for a real point of interest nearby instead of sending you to the center of a town. When the place is clear, it uses the business location directly.

A good route prompt describes intent first: start, stops, return, length, and road preference. Atomic handles the map-specific details.

How to describe a good route

Start with the anchor point. That might be your saved home location, a campus building, a park, a shop, or any address. Then add the route shape: point-to-point, out-and-back, round trip, or multi-stop.

Next, add constraints. Distance is the most useful one: "about 40 km", "under 90 minutes", or "a 3 hour endurance ride". Terrain preference also helps: "mostly flat", "hillier if possible", "avoid gravel", or "mixed roads are fine".

You can include purpose too. "Endurance", "recovery", "coffee ride", "race opener", and "long Z2 ride" all give the agent useful context for distance, pacing, and whether the route should be direct or scenic.

Useful route prompt patterns

Destination route: "Plan a cycling route from home to Homer Lake Forest Preserve." This gives you a practical route between two places.

Round trip: "Plan a 50 km loop from Illini Union and return to the start." This is best when you care about the ride stimulus more than a specific destination.

Multi-stop ride: "Go from Illini Union to Homer Lake, stop at fast food in Homer, then return." This is useful for group rides, refuel stops, campus rides, and destination training days.

Modification: "Make this route shorter", "avoid gravel", "add a coffee stop", or "make it hillier". Atomic can take the current route and revise it instead of starting over.

What Atomic shows after planning

Every route preview includes distance, estimated duration, elevation gain, elevation loss, and a waypoint list. The map preview shows the full route shape so you can inspect whether it matches what you asked for.

The surface section breaks the route into categories such as paved, gravel, unpaved, and unknown. When OpenStreetMap data covers the route, you see an OSM match. When only part of the route has surface data, you see a partial OSM match instead of pretending the data is complete.

Surface data is a planning signal, not a guarantee. It helps you spot whether a route is likely road-friendly, mixed-surface, or worth checking before a fast group ride. If a section is unknown, that means the map data did not provide a reliable surface tag for that segment.

What you can do next

Once a route looks right, you can download the GPX for your bike computer or push the route to Intervals.icu on a specific date. You can also ask the agent to modify the route, for example by changing the distance, replacing a stop, or avoiding a surface type.

Route planning also works with training context. A long endurance route can support a Zone 2 day, a short flat loop can fit a recovery ride, and a hilly route can become part of a strength-focused training week.

A few good examples to try

Try prompts like "Plan a 45 km flat loop from my home", "Find a route to a coffee shop and back", "Plan a group ride with a food stop halfway", or "Make the last route shorter and send it to Intervals.icu for Saturday".

The more concrete your goal, the better the route. But you do not need to speak like a mapping API. Say the ride you want. Atomic will turn that into structured route actions.