|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| While WMS is capable of reading HSPF User’s Control Input (*.uci) files created manually or in other programs, some limitations exist. Some of these limitations are permanent in WMS, other are currently under development and will be resolved.
| | #Redirect [[WMS:HSPF#HSPF_Reading_Existing_Files]] |
| | |
| * WMS will only allow input from one WDM file and output to one OUT file. If more WDM or OUT files are included in the FILES block of the *.uci file, they will be ignored.
| |
| * WMS currently reads the SCHEMATIC and MASS LINK blocks to determine the structure and connectivity of the watershed. The NETWORK block is not yet supported.
| |
| * If a particular land segment contributes to more than one reach/reservoir segment, that land segment will be copied to a new segment for each reach/reservoir. This can result in many new segments if the *.uci file contains several of these cases. Each new segment created will have the exact same attributes as the original, and will represent the area of the original segment which contributes to each reach/reservoir.
| |
| * WMS currently does not read the COPY or GENER block from the *.uci file.
| |
| | |
| Many of these limitations will be eliminated as development of the HSPF interface continues.
| |
| | |
| | |
| ==Related Topics==
| |
| * [[WMS:HSPF|Overview of HSPF]]
| |
| * [[WMS:HSPF Saving and Reading HSPF UCI Files|Reading and Writing HSPF Files]]
| |
| | |
| | |
| {{WMSMain}}
| |
