Lines · Tap a start, any stops and a finish
Farm road and driveway route planner by grade
This farm road grade planner finds a route from a start to a finish, through any stops you add, that favors gentle grades and stays under the maximum grade you set, then offers a smoothed version of it and charts both. It switchbacks up a face the way a road designer would, using the USGS 3DEP lidar model.
Use it to test whether a grade limit can be met at all, and to sketch where a road or driveway could go before walking it with a contractor.
Free to run · pay to download
See the full result on the map free, with no account. Download the route, smoothed or original, as 3D GeoJSON, KML or DXF and its profile as CSV with a pass: US$29 for 24 hours, US$99 for 30 days or US$399 for 12 months, a one-off payment in US dollars that never renews. Every download on the site is included while the pass lasts.
Who uses this
- Farmers, ranchers and foresters. Sketch a road line that equipment can use.
- Rural landowners. Test whether a driveway to the house site can make the grade.
When to use it
- Sketching where a farm road, a driveway or a trail could go on a hillside.
- Checking whether a grade limit can be met at all between two points.
- Guiding the route past places it has to reach, such as a gate, a house site or a stream crossing, by adding them as stops.
Tools for your job
Route Explorer is one step in a bigger question. These are the jobs it helps with, and the tools that go with it.
For the job: Excavation, driveways and farm roads
How much digging, and can a driveway or farm road make the grade?
- 1.Cut & Fill — Cut and fill in cubic yards to level a pad, at an elevation you set or the one that balances.
- 2.Elevation Profile — Grade along a proposed driveway, section by section.
- 3.Route Explorer (this tool) — Finds a line between two points that stays under a maximum grade.
- 4.Contour Lines — Site contours at 1 or 2 ft to hand to a designer.
How to use it
- Open Route Explorer and tap the start. Tap any stops the route must pass, in order, then the finish: up to 10 points in all. Undo point removes the last one.
- Set the maximum route grade in percent.
- Choose Finish route and run. Two versions are drawn: the smoothed route in blue and the original grid path in gray. The panel compares their length, climb and steepest grade, and the chart shows both.
- Choose Smoothed or Original grid path. The one you choose is drawn in blue, is the solid line on the chart, and is the one the downloads contain. Hover or drag along the chart, or along the route on the map, to read each point.
- With a pass, download the chosen route as 3D GeoJSON or KML (WGS 84) or a 3D DXF polyline (Tennessee State Plane, US survey feet), and its profile as CSV with coordinates. Each file name and its notes say which version it is. Saving a picture of the chart is free.
Step by step: Cades Cove
We ask for a route from the cove floor up the mountainside that never gets steeper than 20%.
1.Open Route Explorer, tap the start and the end (and any stops in between), then choose Finish route. Set the maximum grade.
2.Run the analysis. Instead of the straight line, the route switchbacks up the slope; the panel gives the length, total climb and the steepest section.
What it showed
- Lower the grade limit and the route gets longer. If no route fits, the panel says so: raise the limit or move the points.
- Choose Smoothed or Original grid path. The one you choose is drawn in blue, charted solid and downloaded; the file name says which.
- Drag along the chart and a marker follows the route on the map, with the gradient at each point.
How it works
Terrain is loaded for all the route points plus a 0.31 mi margin. Every cell is a node connected to its eight neighbors, with a cost that grows with distance and with grade. A step between cells steeper than your limit is not allowed. The lowest-cost path is found from the start to the first stop, then from each stop to the next, and the legs are joined into one route. That is why the route switchbacks up a face rather than going straight. This is the original grid path: a staircase of steps between cell centers.
The smoothed route pulls that staircase straight. From each corner, a straight line is run as far along the grid path as it can go while staying within about 33 ft of it (or 1.5 cells, if that is more, on the coarser grid of a long route), so the cell-to-cell zig-zag goes but the switchbacks stay. A straight line can end at a stop but never cut past one, so the smoothed route passes through every stop too. Heights are read from the terrain every half cell along the line, and it is kept only if it crosses no missing data and neither any stretch of about 33 ft nor any one cell length is steeper than your limit, the same step rule the grid path follows. Where no straight line passes, the grid steps stay. So the smoothed route is shorter or the same length and never steeper than your limit, though a straight stretch can be steeper than the grid path was at that spot.
Reading the results
Both versions are measured the same way. The steepest grade is the steepest over any stretch of about 33 ft of horizontal distance along the route, so a single noisy cell does not count as a pinch. Neither version goes over your limit, over that stretch or over one cell length; if no route fits within the margin, the panel says so instead, and with stops it says which leg failed.
The gradient shown as you move along the chart, and the gradient column in the CSV, is the rise over one cell length centered on that point, so it reads the same rule the route was built to.
Length and total climb are along the route, not the straight line. Ascent and descent ignore ups and downs of less than 6.6 ft, the same as Elevation Profile; whatever is still climbing or falling at the end is counted, so ascent minus descent equals the change from start to finish.
The panel says how many stretches of the smoothed route stayed on the grid path because a straight line there would have been steeper.
Limits and caveats
- A terrain exploration aid, not a road design. Cut and fill, drainage, culverts, sight distances and legal access are not considered.
- The search is limited to 0.31 mi either side of the route points, so a route that needs a wide detour will not be found. Adding a stop on the detour widens the search there.
- Stops are visited in the order you tap them. The route does not reorder them for you.
- Outside the finest lidar work units, 3DEP can use older lidar at about 9.8 ft per pixel or a coarser model at about 33 ft per pixel. Fine output spacing cannot recover missing source detail. Lidar coverage and source dates vary across Tennessee. Check your site against the USGS 3DEP work-unit index; an unavailable lookup means coverage is unknown.
Data and attribution
Results come from the USGS 3D Elevation Program (3DEP) bare-earth elevation model: lidar at 3.3 ft per pixel where it has been flown, with older lidar at about 9.8 ft per pixel and coarser sources at about 33 ft per pixel elsewhere, with elevations above NAVD 88. Every tool is bare earth: trees and buildings are not in the elevation model for Tennessee, so Sunlight, Viewshed and Sightline work from the terrain alone.
USGS 3DEP elevation data and USGS maps are U.S. Government works in the public domain: you may use the results, including commercially. A credit to the USGS 3D Elevation Program is appreciated, and every file you download carries it. Tennessee parcel boundaries come from the county assessors of property, through the Comptroller’s Division of Property Assessments and county GIS offices, and are not legal surveys; the parcel disclaimer accompanies the selection. The Esri aerial basemap follows Esri’s terms and is display-only; downloadable aerial photos use USGS NAIP.
Questions
Is this a road design?
No. It is a terrain exploration aid. Cut and fill, drainage, culverts, sight distances and legal access are not considered.
Ready to try it?
Open Route Explorer on the map →Free to use, no account. The analysis runs in your browser on public-domain USGS 3DEP data. Downloading the results needs a pass: see pricing.
Missing something you need? Suggest a feature or ask about custom work.