Where the data comes from
ThWay combines trail geometry, accommodation data, and route generation to plan multi-day hiking routes. If a Routeplanner is going to shape your itinerary, you should be able to see where its information comes from and how it is used.
Below is an overview of our core data layers, the methodology behind the routing algorithm, and the way we keep everything current and useful in the field.
Hiking route geometry is sourced from OpenStreetMap, and our route coverage is currently focused on Denmark. We use route data from Waymarked Trails to build the route, which the Routeplanner can then follow.
Some routes are divided into linked segments, which makes custom multi-day planning possible. The trail network is split at natural junctions, crossings, and branch points so the Routeplanner can build itineraries around the exact sections you want to walk.
We try to keep the trail data true to what is on the ground, but route markings and trail conditions change over time. If you notice an issue between the map and the actual trail, please let us know through the contact page so we can review it.
Stay data comes from multiple sources. In Denmark, commercial accommodation (hotels, B&Bs, hostels) is sourced from the overlap between the Danish Central Business Register (CVR) and OpenStreetMap, while shelters, huts, camping sites, tent pitches, and wild-camping areas come from GeoFA (Geografiske Fagdata), the shared public database where Danish municipalities and agencies record outdoor facilities.
Finding a place to sleep is often the hardest part of planning a multi-day hike. Our accommodation database is designed to cover the full spectrum: from commercial hotels and rural guesthouses to primitive shelters and designated wild-camping areas. Each listing includes its type, approximate location, and how far it sits from the trail.
We are especially attentive to shelters and free-to-use facilities that do not appear in commercial booking platforms. Many long-distance hikers rely on these, and we believe a Routeplanner that ignores them is missing part of the picture. We still recommend verifying availability and conditions directly before setting out, as these can change with the season.
We do not include every commercial stay in the database, so you can add your own stay while planning. If you run a hotel, B&B, hostel or campsite and would like it included, please get in touch with us through the contact page.
Routing between trail and accommodation uses a road network derived from OpenStreetMap. We apply weighted distance calculations that prefer footpaths and hiking trails over roads.
When you finish a day’s walk and head to your accommodation, the route between the trail and your stay matters. We do not measure only a straight line. We calculate actual walking routes using the surrounding road and path network. Footpaths and unpaved trails receive lower weights than asphalt roads, so the algorithm naturally prefers the routes hikers would choose.
This network also underpins our daily distance calculations. The distance shown for each candidate stay is the real walking distance along paths, not a rough approximation. For hikers planning around physical limits or daylight hours, that precision makes a real difference.
methodology
Our routing algorithm finds the most suitable route between your start point and candidate stays. Each day, it searches for accommodation within a configured distance of your target walking day and ranks options by how closely they match your ideal.
Generating a route is interactive, and the same choices always give the same result. When you start a route, the Routeplanner calculates the first day’s candidate stays based on your starting point and preferred daily distance. You choose the stay that suits you, and the next day is generated from that choice. This repeats until the route is complete.
Because each day depends on the one before it, the process is sequential by design. It reflects the way multi-day hiking is usually planned: one stage at a time, with each decision shaping the next. If you change an earlier stay, the remaining days is recalculated.
GPX download & navigation apps
Once you have planned a route, you can download it as a GPX file and import it into navigation and outdoor mapping apps. This is useful if you want to follow the route on your phone while on the trail, or keep a copy of the itinerary in another app for offline use.
We recommend Organic Maps and OSMAndMaps as the primary options. They work well for offline hiking use and make GPX imports straightforward. The same GPX file can also be used in Komoot and AllTrails, where it can be opened as a planned route or imported for reference while you walk.
To use it, download the GPX file from your route, open the app of your choice, and import or open the file from the app’s route or GPX menu. Always check the route against current trail conditions, local signage, and the terrain in front of you before setting out.
underfoot data
ThWay also shows, for each day, the elevation profile and what kind of landscape you have beneath your feet. For now, this information is only available for Denmark, but the structure makes it possible to add more countries later without changing the underlying approach.
The landscape along the route is divided into three categories: forest, protected nature, and cultural heritage. Click on a category below to learn more about the data sources and what they cover.
<b>We remind you that route markings, conditions on the ground, and your own judgment take priority when you are out walking.</b>
This layer is descriptive rather than a substitute for local guidance and It helps estimate the overall character of the day’s walking.
data updates
Trail networks and accommodation do not stand still. Paths are rerouted, shelters close for renovation, and new guesthouses open along popular corridors. We strive to keep our data up to date, so the Route Planner reflects reality. If you spot a mismatch, please let us know through the contact page.
We review and refresh our data before each hiking season. For OpenStreetMap-derived trail and road data, we re-import updated exports. For government sources such as CVR and GeoFA, we refresh the data when new versions become available. Manual corrections, often prompted by hiker reports, are applied as they arrive.
There may still be a lag between a real-world change and its appearance in the Routeplanner. If something looks outdated, please let us know so we can review it.
data accuracy & limitations
We work hard to keep our data current and accurate, but trail conditions, accommodation availability, and opening hours can change without notice. <b>Always verify critical details before your hike, and follow official trail markers and local guidance<b>.
Some specific limitations are worth noting: distance calculations are based on the road and path network in our database, which may not account for very recent reroutes or temporary closures. Accommodation listings reflect the best information we have, but we cannot guarantee availability or pricing. Primitive shelters in particular may have no formal booking system, and conditions can vary with the season.
Data quality is never finished. Every hiker who reports an issue makes the Routeplanner better for the next person on that trail.