Ministry of Environment

Fisheries InventoryFisheries Inventory

FAQ - Data Management

Q: In preparation for the digital deliverables, we have run into problems with missing lake data. In some cases, small lakes (too small to be included in the sampling plan), or wetlands, make up individual stream reaches. As they have been excluded from the plan in some cases, their NIDs do not appear in FDIS, but do appear in the GIS databases. As such, when the NIDs in the GIS database are compared with the NIDs in FDIS, there are discrepancies which are unacceptable for the digital deliverables. Should we include all lakes and wetlands within a stream course in the lake table so the NID files in FDIS and GIS match up?

A: There should be no discrepancies between the digital data and maps. All lakes and wetlands should be included in the lake table (if they are broken out as separate reaches). Even if they are deemed too small for consideration for field sampling, they should be identified in the lake table. The other option for stream only type contracts is to not include the anomalous lake information in the GIS data set.

Q: Do we require a photo documentation spreadsheet or is having the photos documented on the Site Cards enough for referencing the negatives and CD's?

A: There is no "separate" spreadsheet required for photodocumentation. This information is entered into the relevant forms in FDIS. An extra FDIS table needs to be completed: the CD file/photo cross-reference table.

Q: Can FDIS be used to enter Fish Cards only?

A: FDIS can be configured to accommodate any combination of cards. This is done when the waterbdy.exp file is built so it is important to provide the project type when submitting a request for watershed codes.

Q: What is the format for the NID/UTM import file?

A: The mapping GIS can generate a file of NID points and UTMs to be imported into FDIS. The GIS file must be in a specific format (see example below), named NIDUTM.CSV and in your FDIS-preferred directory. The columns in NIDUTM.CSV are:

  • TRIM Mapsheet - character field with quotes arround it and a leading zero for 80 and 90 series maps,
  • NID - whole number up to 5 digits,
  • UTM Zone - whole number, 1 or 2 digits,
  • UTM Easting - decimal number, and
  • UTM Northing - decimal number.

The file must be a Comma Separated Values (CSV) file.

Here is an example file (note that it does not have the column headers in it):


Q: Where do Interim Locational Points (ILP’s) go?

A: The ILP for a stream is at the mouth. Stream reaches are numbered consecutively from the mouth. A lake is considered a reach. But, the ILP of a lake or a wetland (if the wetland does not have a visible channel flowing through it) is unique and is at the outlet. Lake and wetland reach data should be entered on the Lake Planning screen of FDIS NOT the Reach Planning screen. If the lake is isolated the ILP is at the centre of the lake. A wetland with obvious channels flowing through it is considered part of the stream and should be entered on the Reach Planning screen.

Q: What are the valid codes for sampling type?

A: Running the Random Sampling program in FDIS generates randomly selected reaches that are identified by Rs in the Sample Column on the Reach Planning Screen. In cases where a reach has been selected for sampling but is inaccessible or cannot be surveyed for some other reason (acceptable to the contract monitor) the R on the Reach Planning screen should be changed to an N, a comment should be entered into the Comment section of the Reach Card and a similar reach should be selected according to the RIC Standards page 2:18. Type a B into the Sample Column to identify the newly selected reach. You can either delete the B or change it to a U if a biased site is not going to be sampled.