Undefined SSURGO soils in database

23 views
Skip to first unread message

Emily Blue

unread,
Oct 13, 2025, 12:06:57 PMOct 13
to SWAT+

Hi everyone,
I’m getting the following error during HRU creation in SWAT+:

“SSURGO soil 1724686 (and perhaps others) not defined in ssurgo table in database. soils_sol table incomplete, see QSWAT+ log messages for full list of undefined soils.”

I’ve tried using multiple SSURGO rasters, but the issue persists, which makes me think something might be wrong with the SSURGO-related tables in the database.

Here’s a screenshot from my model setup for reference.
Has anyone else encountered this issue or found a fix?

Thanks in advance!SSURGO_soils.png

Matthew Lombardo

unread,
Oct 15, 2025, 9:37:38 AMOct 15
to SWAT+
Hi Emily,

I ran into this problem a month ago with my model also. All of the SSURGO soils are stored in the swat_soils.sqlite and if you open up the sqlite in QGIS you can go through the two SSURGO soil tables to see if your soils are in there. None of my soils were in the database, so I had to create my own soil lookup and usersoil tables.

To make your own:
1.) If you type the MUKEY ID in at the end of this URL, you can see the soil name.
2.) Then, go to this link. If you define your area of interest, all of you soils will be here. To find specific soils, look up the full name of them. This link has all of the parameters that you need besides the moist albedo and the % organic carbon. You can calculate the organic carbon from the organic matter content. 

Also, these are links to an example for the soil lookup and usersoils. For the usersoil, SWAT won't let you use more than 10 layers per soil.

Hope this helps!
Reply all
Reply to author
Forward
0 new messages