You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Great Basin version 3 model, I have zones that split some of the hydrographic areas into mountains and valleys. The zones were already 3 digits so that they could (in most cases) match the official HA number. To split them I added a fourth digit. Zonebudget seems to be able to handle this, and the .csv and .2.csv files are readable, although there is no space between the word zone and the number. The .zblst file, however, prints those zone numbers out as ***. This causes a problem when trying to use GWChart to look at things. Is there any way to fix that? And if you are changing things anyway, is there any way to make Zonebudget work with alphanumeric zones instead of only numeric zones. That way I wouldn't have to name HA 240B, for example, as 340 because HA 240A is already named 240. And flow regions could be named by an abbreviation instead of a number that means nothing.
I'm underfunded this year. If you could send me funding and money to get a compiler, I could look at this.
Lynette
Lynette E. Brooks, P.E.
Hydrologist
U.S. Geological Survey
Utah Water Science Center
2329 Orton Circle
Salt Lake City, Utah 84119-2047
(801) 908-5014
The text was updated successfully, but these errors were encountered:
Chris,
In the Great Basin version 3 model, I have zones that split some of the hydrographic areas into mountains and valleys. The zones were already 3 digits so that they could (in most cases) match the official HA number. To split them I added a fourth digit. Zonebudget seems to be able to handle this, and the .csv and .2.csv files are readable, although there is no space between the word zone and the number. The .zblst file, however, prints those zone numbers out as ***. This causes a problem when trying to use GWChart to look at things. Is there any way to fix that? And if you are changing things anyway, is there any way to make Zonebudget work with alphanumeric zones instead of only numeric zones. That way I wouldn't have to name HA 240B, for example, as 340 because HA 240A is already named 240. And flow regions could be named by an abbreviation instead of a number that means nothing.
I'm underfunded this year. If you could send me funding and money to get a compiler, I could look at this.
Lynette
Lynette E. Brooks, P.E.
Hydrologist
U.S. Geological Survey
Utah Water Science Center
2329 Orton Circle
Salt Lake City, Utah 84119-2047
(801) 908-5014
The text was updated successfully, but these errors were encountered: