Note the standard watershed
code is a 45 digit number with 11 dashes. The reports will remove insignificant
zeros to preserve
space. The more specific you want to get, the more zeros and dashes you
should provide in the form.
For example, entering the watershed
code
will return the report:
Gazetted Name
Watershed Code
Waterbody Identifier
Type
NTS map
UTM zone
UTM north
UTM east
Alias
COWICHAN LAKE
920-257700
00408COWN
L
092C16
10
5408526
422270
COWICHAN RIVER
920-257700
00000COWN
S
092B13
10
5400219
453212
While entering the watershed
code
will return 277 unique waterbodies, including all the tributaries of the
cowichan river.
Note: be aware that some watersheds
will return a large amount of waterbodies, and may exceed size limitations
of the report.
For example, entering
for the Thompson River watershed (without entering other criteria) would
attempt to return over 14000 waterbodies and would produce a warning of
an incomplete report. On less powerful computers, this may also cause
a 'freezing' effect on the web browser as it attempts to use more memory
than can be alloted. See here for more on problems with
large reports.
The more specific your query
is, the faster it will be returned, and the more useful the report will
be. Try to fill in as many fields as possible on the form. Most queries
should complete within 10 seconds, and during this time the processing message
will appear to indicate the database is working on your report.
If you don't
fill in at least one critical field (marked with an asterisk), you
will receive an error message stating that your query was too big
to submit to the database. Try filling in more information in the
form to avoid this error.
A maximum of 5000 records
will be returned in any one query, and you will be alerted if your query
has gone over this amount. Reports of this size require a large amount
of memory for your web browser, and large reports may cause delays or
error messages on some systems. (more
on large query errors)
Each report
from the database is given as a standalone window from your web
browser, so that you can use the File/Print and File/SaveAs features
on your browser to save and print this page as an HTML document.
To bring the data in
this report into a database, first save the report page as described
above, then use Microsoft Excel File/Open and select 'HTML documents'
from the file types. You can then open this report in Excel, eliminate
any wanted items (such as the header and footer messages) and
use File/SaveAs to save as a format accepted by your database
product. For example, to bring into Microsoft Access:
save
the report page as an HTML document
open the HTML document in
Excel
remove unwanted header/footer
details
save as an Excel (.xls)
document
from Access 97, use File/Get
External Data and select 'Excel .xls documents'
follow the step by step
wizard in Access 97 to import the data into a table
the data warehouse queries
require a browser that is javascript enabled and frames enabled such
as Internet Explorer 4.0 or higher, or Netscape 4.0 or higher
larger queries may experience
delays for slow internet connections such as 28.8 kbps modems
access to the data warehouse
may experience interruptions during weekly maintainence times, typically
Sunday evenings
"My query returned
4999 records and said the report was incomplete."
the maximum size of a report
is 5000 records, and your query was larger than this size. Try to reduce
the size of your query to return a smaller set of records.
"After entering
a query, the processing message kept going and my browser seemed to freeze without
giving a report."
OR
"After entering
a query, there was a long delay and I got a Windows error message saying
I was low on system virtual memory."
it is probable that your
query returned a large amount of records, and your browser was having
problems displaying the report. The data warehouse queries allow a powerful
access to large datasets, but this may cause trouble on some systems.
A compromise allows powerful queries while protecting most computers
from experiencing difficulties. Note, that if you experience these problems
after submitting a large query, there is no risk of harm to your system.
this is particularly likely
if you have under 64MB of RAM, or have several applications open on
your computer
if possible, close some
other applications and/or retry the query. If you are confident in the
use of your OS, you may wish to allocate more virtual memory, or have
your system administrator do this.
restricting the query
by filling in more criteria will return a smaller dataset and is by
far the easiest way to avoid this problem. It would be very rare
to have problems of this nature when returning small datasets (under
1000 rows).