KINEROS results issues

[Cathy Rosenthal]

Good morning,

I am at a loss for why this model won't work for me.  I've tried it several times yesterday and this morning and keep getting the same messages and problems.  I delineated a watershed using the KINEROS model in ArcGIS 10.5.  All the inputs seemed to have worked as I've been able to run the Discretization, Parameterization and Precipitation without issues.  When I run the KINEROS simulation I get the image attached as Capture 1.  The one thing I wonder about is the multiplier file which I don't know what that is and don't seem to have a file to map too?  Once I write the simulation and run it, Capture 2 is what I get.  Then when I try and view the results, it let's me import my simulation but I get the message on Capture 3.  Please help.  I'm tired of running in circles with this.  The sooner the better too please!

Thank you!

Cathy Rosenthal

[Shea]

Hi Cathy,

Sorry you're having trouble. The multiplier file is optional and is created when you use the optional multipliers tab in the form from Capture1, so that's not the issue here. Notice in Capture2, there's a message that says Total watershed area = 0.0 ha. That's an indication that the parameter file for the model wasn't written completely, which means there was an unhandled error earlier in the process, most likely in the parameterization step. Add the parLUT attribute tables from the geodatabase containing your delineation and discretization to the map and check for null values. That should help us troubleshoot the issue.

What land cover and soils datasets are you using?

Shea

[Cathy Rosenthal]

Hello Shea,

It won't let me enter the parLUT that I created as part of the geodatabase.  It only let's me enter the the LUT look-up tables from the AGWA datafiles folder.  Hope that makes sense?

--
You received this message because you are subscribed to the Google Groups "AGWA Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agwa-support...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/agwa-support/7d2b8a65-6289-4af3-9cfb-fbf9b0c22398n%40googlegroups.com.

--

Cathy Rosenthal

Watershed Coordinator

Wyoming Association of Conservation Districts

Phone:  307-751-9389

Address: 2390 Cooper Rd.  Riverton, WY 82501

Email:  cathy.r...@conservewy.com

[Shea]

Hi Cathy,

The parLUT tables store the model parameters characterized during the parameterization step, which is different than the land cover look-up table selected during the parameterization step. The land cover look-up table associates the pixel values in the input land cover to canopy cover, hydraulic roughness, and interception values for a land cover type. To look for null values in the parLUT tables, right-click on them in the Table of Contents and select Open Attribute Table.

Shea

[Cathy Rosenthal]

I only have one "0" value in the symbology and no null values in the Land Use raster.  I used an NLCD 2001 raster.  Should I change the "0" to something else?

For soils I used statsgo which doesn't appear to have any null values.

To view this discussion on the web visit https://groups.google.com/d/msgid/agwa-support/5932303c-2cf3-48d4-b6a1-952ba2ff8f4dn%40googlegroups.com.

[Shea]

Hi Cathy,

There doesn't seem to be a problem with your land cover or its attribute table. Open the AlamoCreek_NEW_Discret_p_parLUT attribute table instead and check that for null values. It's the table created during the parameterization process, and if there was an error that occurred in those steps there will either be missing fields, null values, or zero values that should be non-zero in that table. If you'd like to attach the geodatabase as a zip file, I can also take a look to see what could be going wrong. Also, i forgot to mention, there should be an errors.txt file located where the map document is saved. If you attach that also, I'll be able to help you troubleshoot a little more effectively. 

Shea

[Cathy Rosenthal]

Hello Shea,

Ok, maybe we're getting somewhere:).  The "planes"AlamoCreek_New_Discret" file has Null values in the "Side" Column.  Could that be what's happening?  If so what value should I enter?  Those that don't have "null" have -1 or 0.  I'll work at attaching the geodatabase.

Thank you so much for your help!

Cathy

To view this discussion on the web visit https://groups.google.com/d/msgid/agwa-support/ad8b6e4f-e824-4bd1-888a-52c39e2b64b9n%40googlegroups.com.

[Shea]

Hi Cathy,

Actually, the nulls in the Side field are OK, they represent the headwater plane model elements. Values of 0 and -1 represent elements on the left and right, respectively, of a channel when facing downstream. In that screenshot, you have the correct table in the Table of Contents highlighted, but the attribute table that is open is for the planes feature class. Open the AlamoCreek_NEW_Discret_p_parLUT, it should look somewhat similar to the attached.

Shea

[Cathy Rosenthal]

Oh geesh.  Thank you for being patient with me.  As you can see I'm struggling a bit with this whole thing - first time trying everything.  Here is the AlamoCreek_NEW_Discret_p_parLUT and YES it has several Null values (X, Y, width and length).  So something obviously didn't run right..

To view this discussion on the web visit https://groups.google.com/d/msgid/agwa-support/73466cd3-133d-486c-ac5d-60ffb3b33c69n%40googlegroups.com.

[Shea]

No worries, there's always a bit of a learning curve when trying something new, but you're doing fine, and in fact you probably didn't do anything wrong. However, something did go wrong during the parameterization step- the X, Y, Width, and Length fields should definitely not be null. The Int, Cover, and Mann_N fields should also be non-zero, but this could be a second, unrelated error to the null values as they're calculated in separate parts of the parameterization process. The first thing to do is simply to save your project, close ArcMap, and restart it. Then, try the parameterization step again.The fact that there was an error and those fields didn't get populated is sometimes just bad luck, as frustrating as that can be. I wish I could say exactly what goes wrong when this happens, but it still happens to me occasionally and I don't know why, other than it's likely a read/write conflict with the data and restarting ArcMap usually helps. It *generally* is resolved on the second attempt, but not always, so check the attribute table again after the second parameterization. Note that you'll have to provide a different name for the second parameterization (and any others that follow), and when you check the attribute table afterwards make sure you're looking for the null values in the records associated with the second parameterization.

As to the zeroes in the Int_, Cover, and Mann_N fields, that may be due to using the wrong land cover look-up table for your selected land cover. I noticed you had both the nalc_lut and the mrlc2001_lut in the project in the screenshot attached to your second message above, so just make sure you use the mrlc2001_lut, which corresponds to the NLCD 2001 and newer land cover databases, in the Land Cover and Soils form of the parameterization. The NALC (North American Landscape Characterization project) data and associated nalc_lut aren't commonly used, I'm not even sure where to get it anymore, but we include it because it was a cross-border dataset and we use it in our San Pedro tutorial, which spans the US-Mexico border in southern Arizona and Sonora, Mexico. 

Shea

[Cathy Rosenthal]

It's still missing the values in a few of the columns.  I used the land use file that is shown in the previous email.  The latest error is what I'm getting.

To view this discussion on the web visit https://groups.google.com/d/msgid/agwa-support/8624d578-4145-4d13-8e15-4dc255cf7e6an%40googlegroups.com.

[Shea]

Hi Cathy,

Looking at the screenshot of the errors.txt file, it looks like you're using some older STATSGO data that used an MUID field to identify map units. The current generation uses an MUKEY field. Because you're still encountering errors, can you try using the current STATSGO or SSURGO data and see if that makes a difference? The latest version of STATSGO for Wyoming can be downloaded from https://nrcs.app.box.com/v/soils/folder/18247487156?page=3. Once downloaded, you'll need to double-click on the soildb_US_2003.mdb file to open it in Access, and from there run the Import macro to import the tabular data into the soils database.

Shea

[Cathy Rosenthal]

Hi Shea,

It's me again:).  Ok.  I uploaded a new soils shapefile / geodatabase and the parameterize worked!  But I still got this message and this error?  In the table I do have a few null values and 0's.  What should I do about those?  Are those what are giving me the errors?

Thanks,

Cathy

To view this discussion on the web visit https://groups.google.com/d/msgid/agwa-support/764a4e81-1ab8-41e8-85f6-4ce61fd44e4an%40googlegroups.com.

[Shea]

Cathy,

It looks like there may still be a problematic plane element, perhaps one still isn't being split by the channel. Can you ZIP the geodatabase and attach it to a post?

Shea

[Cathy Rosenthal]

Hello!  I think I finally figured out how to zip the geodatabase.  Hopefully it is all there for you. 

https://wacd.box.com/s/odoko7o41o09063ft8kgpvb5vo5s2j90

Thanks,

Cathy

To view this discussion on the web visit https://groups.google.com/d/msgid/agwa-support/a87ba07b-a7ff-4c1c-be4f-58328a41b0cbn%40googlegroups.com.

[Shea]

Your delineated watershed is tricky. While this isn't the source of your error (more on that below), your watershed, the Alama Creek-Bighorn River (100800071207) HUC12, has a series of other HUC12s draining into it which are not captured with your delineation . While it's possible to create a working model in this situation, be aware that you're not modeling/representing the whole watershed. See the attached screenshot for reference. Depending on what you're trying to do, it might be better represented by modeling several smaller tributaries that are draining into the Bighorn River since there's a significant portion of the Bighorn to the south that is not being represented (and also the Nowood River to the east).

Back to the error, the highlighted stream below in the Alamo2_Distric_trial discretization did not successfully split the plane element it passes through, which cause a problem during the parameterization step resulting in that null value. I'm not sure why the plane element didn't split, it does appear capable of it being done. To resolve this, you could try increasing or decreasing the CSA by 0.5%. Alternatively, because it does appear capable of being split, you could start an editing session and use the Cut Polygon tool in the Editor toolbar with the Trace construction method to trace the stream element to manually split it. If you choose to manually split it, after saving the edits run the parameterization again and see if the null values are corrected.

[Cathy Rosenthal]

Shea,

Thank you for the suggestions.  I tried both increasing and decreasing the CSA and it didn't work as well as splitting the plane.  I think I've gone as far as I can with this model and might move on to something else.  Thank you so much for your guidance and help!  If I come back to this and try it again I'm sure I'll be contacting you again.

Thanks,

Cathy

You received this message because you are subscribed to a topic in the Google Groups "AGWA Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/agwa-support/urxIjdslXaY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to agwa-support...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/agwa-support/c002303a-afd7-428c-89f0-7f68f7ea0f7cn%40googlegroups.com.

[Shea]

Happy to help Cathy, good luck!