Justin --
As you surmise, ArcSWAT uses the initial land-use category in the land-use grid or shapefile in creating HRUs. It's not using the grid value -- it's using the reclassified SWAT land-use name that you assign to that number. All the different grid values that you assign to PAST will get called the same thing by ArcSWAT -- at that point it has no idea that management practices will differ in later years.
The initial land-use designation in SWAT is really not that important for those places where you're going to institute a crop rotation. Once you start a rotation, SWAT will forget what the initial land-use designation was. Lately I've taken to lumping all my agricultural land into a single SWAT category (AGRR, agricultural row crops), and then afterward I'll assign different crop rotations to this land (I have more detailed information on crop rotations from county agents that I think are better than using the sequential CDL data layer methods).
Your options:
(1) Easiest would be to assign different initial land uses (crop types) from the many existing SWAT land uses to your different pasture scenarios. E.g., call one pasture, call another fescue, call another brome, another bluegrass, etc. It really doesn't matter what you call it (as long as it's unique and not conflicting with a real land use elsewhere) -- you're going to change it anyway when you enter the rotation information later.
(2) Probably better would be to add your own crop types to the crop data base -- I think you're allowed to do this. If you've got 4 different pasture rotations, I'd simply copy the PAST data line 4 times in the data base, and rename each type something sensible you can remember, like PAS1, PAS2, etc. (I don't know the rules for adding crop type and naming conventions.) Later you'll have to add the rotation information, but at least this way you'll retain the spatial locations of these different rotations.
(3) Otherwise -- what I commonly do is to accept the lumping of similar land uses by ArcSWAT, and assign rotations to HRUs later. If I know I've got 500 ha of Corn-Soybean rotation in the watershed, I'll export the HRU table with areas, sort to find the AGRR HRUs (see note above). Then I'll use a formula with a random number generator in it to select an array of AGRR HRUs and keep making trial random selections until I get a total area very close to my target. Then I'll take those Corn-Soybean HRUs and assign half to a Corn-Soybean rotation, and half to a Soybean-Corn rotation.
This involves a lot of copying, pasting, sorting, and so forth in Excel, and I've lost some minor control on where these rotations end up on the landscape -- except it does of course crops do end up on cropland.
Distributing your management scenarios (rotations) among your HRUs is one of the most tedious parts of constructing a SWAT model, I think. But I'm not sure how to improve the methods.
Cheers,
-- Jim
From: "Justin" <
gold...@gmail.com>
To: "SWAT-user" <
swat...@googlegroups.com>
Sent: Wednesday, December 1, 2010 8:32:09 PM
Subject: [SWAT-user:2496] Question re: Land Use Classes