1. Saving results to a file
When exporting results using the ‘Save to File’, users should select a regular folder where they have write permissions: the folder suggested by default, “Program Files”, is typically not user-writable.
2. Saving results files.
The user will not be able to save results files if the boundary polygon name contains punctuation such as ‘:’. After completing a flow estimate the user should edit the site name in the top left hand box with a simple descriptive name. This name will be used as the export file name.
3. Saving results to a file from the Flow-Duration tab in Scotland.
If the ‘Save to File’ option is selected from the Flow-Duration tab in the results form, LowFlows 2 will export the natural flows without lake adjustment, even if the lake adjustment check box is selected. In addition, the file will indicate that there are ‘no significant lakes’ within the catchment. To avoid this, users should select ‘Save to File’ from the Results Summary tab instead.
4. Importing catchments from the FEH Web Service.
There is a known issue in LowFlows 2 when importing some catchments from the FEH Web Service. The catchment polygon generated by the FEH Web Service does not start at a fixed location, whereas LowFlows 2 expects it to start at the outlet. A run-time error “91 (Object variable or With block variable not set)” can occur when a polygon starts at the opposite side of the catchment boundary. This can be resolved by tracing the boundary in a new shapefile, being sure to start the boundary at the catchment outlet. Tracing functionality is available in most GIS software.
5. Error “91 (Object variable or With block variable not set)”
This error may arise in a number of places; Question 4, above, is one example. If you see this error elsewhere please contact our support team and describe the steps leading up to the error.