Data · Select a property, draw a box or polygon, or upload a boundary

Download USGS 3DEP lidar elevation data for any Tennessee area

Download the Tennessee lidar DEM for exactly the area you need, from the USGS 3D Elevation Program: a GeoTIFF elevation model, contours as DXF, GeoJSON, Shapefile, KML, SVG or PDF, a 3D mesh as STL or OBJ, the ground surface as a 3D DXF or LandXML TIN for CAD and civil design, or a georeferenced color aerial photo of the site (USGS NAIP, public domain) for your GIS or CAD. Draw or select the area; the file is cut, resampled and written for you.

The National Map has the same public-domain data, but hands you raw tiles to merge, clip and convert in GIS. This skips that step for site-sized areas.

Free to run · pay to download

See the full result on the map free, with no account. Download GeoTIFF, contours (DXF, GeoJSON, Shapefile, KML, SVG, PDF), STL or OBJ meshes, 3D DXF or LandXML surfaces, and a georeferenced aerial photo (JPEG, GeoTIFF, KMZ or PNG) 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

  • GIS analysts and surveyors. Get a DEM cut to a site’s extent without tile wrangling.
  • CAD users. Pull contours, or the ground as a 3D DXF or LandXML surface, straight into AutoCAD or Civil 3D in Tennessee State Plane US survey feet.
  • Makers and educators. Download an STL of any Tennessee landscape to 3D print.

When to use it

  • You want the elevation model itself for GIS, CAD, drainage or structural software.
  • You want to 3D print a property, a mountain or a stretch of coast.
  • You want contours in a specific format without generating them on screen first.
  • You want a georeferenced aerial photo of the site as a CAD or GIS underlay, or over the terrain in Google Earth.

Tools for your job

Download Data is one step in a bigger question. These are the jobs it helps with, and the tools that go with it.

For the job: Plans, CAD, GIS and 3D printing

I need the terrain as a file.

  1. 1.Download Data (this tool) — Contours, a GeoTIFF elevation model, a 3D DXF or LandXML ground surface, a georeferenced aerial photo or a 3D mesh for printing.
  2. 2.Data Here — Which USGS lidar surveys cover a spot, when each was flown, and where to get its files.
  3. 3.Elevation Change — Where USGS lidar was flown twice: whether the ground has slid, been filled or been cut between the surveys, as a GeoTIFF.
  4. 4.Contour Lines — Contours previewed on the map before you export them.
  5. 5.Elevate a File — Adds ground elevation to your own GPX, KML, GeoJSON or CSV points.
  6. 6.Point Elevation — Spot elevations at the points you click or on a grid over a lot, as CSV, GeoJSON or DXF.
  7. 7.Terrain Stats — The highest, lowest and mean ground elevation of an area, and how the land is spread between them.

How to use it

  1. Select a property, draw an area or upload a boundary. For a property, the download covers the rectangle around it, not the clipped outline.
  2. Choose the product (contours, a DEM raster, an aerial photo or a mesh) and the format.
  3. Set the contour interval or the mesh options where they apply, then download.
  4. For several files at once, open Several files in one ZIP and tick the parts. The panel shows each part’s detail and an estimated size, and the ZIP carries a README and manifest naming each file’s coordinate system.
  5. For the GeoTIFF, where the USGS index lists more than the seamless DEM, choose one lidar survey instead: its own 3.3 ft lidar DEM for areas up to 2.54 mi across, on its own NAD83 / UTM grid, with nothing filled in from other surveys. The file name says which survey.

Step by step: Cades Cove

We set up a download of the terrain around Cades Cove.

1.Zoom to the area and choose Download this view, or draw a rectangle or select a property. Then pick contours, a GeoTIFF elevation model or a 3D mesh, and the format.

What it showed

  • The panel shows the resolution before you download: 3.3 ft per pixel for a small lot, coarser for a large area.

How it works

The USGS 3DEP bare-earth model is read for the area at up to 1,024 pixels on the longest side and written in the chosen format. The GeoTIFF is in WGS 84 latitude and longitude (EPSG:4326), above NAVD 88, with a no-data value for gaps; values in the file are in meters, as USGS publishes them. Contour files carry elevations in feet; the DXF is in Tennessee State Plane, US survey feet (EPSG:2274). Meshes are built from the same grid with a base so they print as a solid.

The aerial photo is USGS NAIP orthoimagery (public domain), fetched at up to 4,096 pixels on the longest side and delivered as a JPEG with a world file and projection file, a GeoTIFF, or a lossless PNG with a world file, all in Web Mercator (EPSG:3857), the imagery's own grid, so QGIS, ArcGIS and Civil 3D drop it in place under the DEM and contours. The KMZ is the same photo resampled to WGS 84 longitude and latitude, the grid a Google Earth ground overlay is placed on. Each file says it is a photo with no heights. For a property it covers the parcel plus 100 ft on every side; for a drawn area it covers exactly that area.

The 3D DXF and LandXML files are the ground itself at true scale: the bare-earth model is read on a NAD83 latitude and longitude grid, each cell center is projected to Tennessee State Plane, US survey feet (EPSG:2274, as for the contour DXF, and named in the file; grid coordinates, with no surface adjustment factor) with its height above NAVD 88, and neighboring points are joined into two triangles per cell. X, Y and height are all in US survey feet. Cells with no data are left out rather than filled. The 3D DXF writes each triangle as a 3DFACE on layer TERRAIN, in full Tennessee State Plane coordinates or shifted near 0,0 with the shift written at the top of the file. LandXML lists each point as northing, easting, elevation, the order LandXML uses.

Every file credits its source (the USGS 3D Elevation Program, USGS and USDA for the aerial photo) in its metadata or an accompanying attribution.

Reading the results

The panel shows the output resolution before you download. A small site is delivered at 3.3 ft per pixel; a block 7.5 miles on a side at roughly 39 ft per pixel.

The share of the area that fell outside lidar at 3.3 ft per pixel is reported, and the file is not survey grade where that share is high.

3D DXF and LandXML surfaces keep the full lidar detail up to 0.6 miles per side and are thinned above that. The panel shows the point spacing, the point and triangle counts and the largest the file can be before you download.

Limits and caveats

  • Areas up to 7.5 miles per side.
  • Downloads cover the rectangle around a selected property or drawn shape, not its outline. For contours clipped to a property, export GeoJSON or KML from Contour Lines.
  • Exports are capped at 1,024 pixels on the longest side. Select a smaller area when you need full detail.
  • A full-detail 3D DXF holds millions of triangles and can run to hundreds of megabytes. Keep CAD surfaces small, or use the GeoTIFF where your software can build its own surface.
  • Each 3DFACE repeats its third corner as the fourth, the usual CAD way to write a triangle. GDAL and QGIS may warn "Non closed ring" when they open the 3D DXF; the warning is harmless and the triangles read correctly.
  • The 3D DXF and LandXML surfaces are a model of the ground for planning and early design, not a survey.
  • USGS 3DEP data is in the public domain, so the files are yours to use, including commercially. Crediting “USGS 3D Elevation Program” is good practice.

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

What resolution will the GeoTIFF be?

A site-sized area is delivered at the full 3.3 ft per pixel. Exports are capped at 1,024 pixels on the longest side, so larger areas are resampled: a block 7.5 miles on a side comes out at roughly 39 ft per pixel. The panel shows the resolution before you download.

What units is the GeoTIFF in?

Values in the file are in meters above NAVD 88, as USGS publishes them, on a WGS 84 latitude and longitude grid (EPSG:4326). For feet, export contours: every contour file carries its elevation in feet, and the DXF is in Tennessee State Plane, US survey feet.

Can I download an aerial photo of the site?

Yes. Under Aerial photo, choose JPEG: a georeferenced color aerial photo from USGS NAIP (public domain), about 1 ft per pixel where available, delivered as a JPEG with a world file and projection file in Web Mercator (EPSG:3857), so it drops straight into QGIS, ArcGIS or AutoCAD Civil 3D under the contours. The same photo also comes as a GeoTIFF, a lossless PNG with a world file, or a KMZ for Google Earth. For a property it covers the parcel plus 100 ft on every side. The aerial basemap on the map is Esri World Imagery, for display only.

Can I use the data commercially?

Yes. USGS 3DEP data and USGS NAIP imagery are in the public domain. Crediting “USGS 3D Elevation Program” (and USGS and USDA for the aerial photo) is good practice, and every file carries that credit.

Ready to try it?

Open Download Data on the map →

Free to use, no account. Files are generated on this site’s server from 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.