British Columbia Government Crest
Advanced Search
Main Index Help
Contact Us
MOE > ESD > Ecosystems Branch > Fisheries Inventory > FDIS > Getting Started > Importing the Code Files
current
 
  FISHERIES INVENTORY
Fisheries Inventory Home
Fisheries Information Summary System (FISS)
Methods
Survey Data
Watershed Atlas Maps
Contacts
 
  POPULAR TOPICS
EcoCat Reports
Data Queries
FDIS Tool
HabitatWizard
RISC Standards
WSCA maps
 
 
 
Exit this e-service
Ministry of Environment
Fisheries Inventory

Importing the Code Files

  • Before you can start entering data into FDIS you must import 4 code files: codes.exp, species.csv, gisfeat.csv and waterbdy.csv

  • When you receive the code files, put them into a separated directory from the program files (e.g. c:\fdis\work)

  • go into FDIS. From the Main Menu click on Administrative Menu. Then click on User's Preferences. At the the top of the User's Preferences window there is a place to type in the path to the directory where FDIS can find your 4 code files (or any other files you want to import like rplans or lplans)

  • Go back to the Main Menu and click on Data Imports/Exports. Then click on Import Code Tables.

  • Check the Reach and/or Lake Planning Screens to ensure that the codes imported successfully and you have all the watershed codes you need for your project:

    • From Main Menu click on Reach Data Collection, then Reach Data - the Reach Planning Screen will appear

    • Click on the down arrow in the first record of the first column (Project WS Code) - a pick list of Project watershed codes will be displayed - make sure yours are all there

    • Click on the down arrow in the second column (Watershed Code) - a pick list of all the reach watershed codes will be displayed - make sure yours are all there

    • In the Main Menu click on Lake Data Collection, then Lake Data – the Lake Planning Screen will appear - make sure your Project WS Codes and Waterbody Identifiers are all there

 
FDIS Tools

top

Web Page Last Updated:  February 11, 2008

 

Copyright Disclaimer Privacy Accessibility