Jump to content
TUFLOW Forum
O-Dogs

Error 2807 trying to apply more than 1 level boundary

Recommended Posts

Running the new 2020 release and have just come across the following error:  2807 trying to apply more than 1 level boundary.

Can not find any literature on this error. 😞

Any guidance on rectifying this issue would be greatly appreciated. 🙏

Cheers 👽

Share this post


Link to post
Share on other sites
38 minutes ago, O-Dogs said:

2807 trying to apply more than 1 level boundary.

This indicates that there is a Quadtree cell for which more than 1 water level boundary (HT, HQ, HX or QT) is being applied.  There should be a spatial messages in the _messages GIS file which locates the cell.

Share this post


Link to post
Share on other sites

...so the rectification is to check your digitisation of your H boundaries at this location (as indicated by your spatial message(s)) and re-digitise at least one of them so they aren't selecting the same cell. 😉
If you think there's a reason why there should be more than one HT being applied at the same place, do come back and there can be some discussion on that! As a rule though, it's not allowed, as you're instructing the model to apply two (presumably conflicting) water levels at the same place, and the model can only every have one water level in a cell. If they are always applying the same level and you've snapped them together to ensure continuity, consider making them into a single feature.

Share this post


Link to post
Share on other sites

Historically TUFLOW has allowed multiple HT boundaries to be applied to the same cell. The water level used by TUFLOW is the sum of all HT boundaries. See the notes in table 7-4 (page 7-11) of the 2018-03 TUFLOW Manual.

Share this post


Link to post
Share on other sites
On 5/20/2020 at 6:34 AM, stormwater01 said:

Historically TUFLOW has allowed multiple HT boundaries to be applied to the same cell. The water level used by TUFLOW is the sum of all HT boundaries. See the notes in table 7-4 (page 7-11) of the 2018-03 TUFLOW Manual.

You're quite right; so tidal profiles could be built up of astronomical profile and surge profile, for example. The place it isn't allowed is when dealing with HX boundaries (and by extension QT boundaries) and HQ boundaries where adding up the water levels makes no sence.

From the reading of those release notes Phil, such tidal examples would no longer function though? They'd only apply the first HT they read in (a solution which I wholeheartedly approve of for HX and HQ though, and will make downstream ends of 1D/2D river models that bit easier). Could TUFLOW perhaps permit multiple HTs (or at least have the option to do so for legacy models), and only if any of the other flavours of H boundary are applied do the "first one wins" approach? Easy enough for the user to just change the input data though, I suppose. Also, as a thought, in just about every other walk of TUFLOW life, when conflicting inputs are applied in the same place it's the last that wins; is there a rational for diverging from that approach here?

Many thanks,

Peter.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...