My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD00469
CWCB
>
Board Meetings
>
Backfile
>
1-1000
>
BOARD00469
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 2:50:52 PM
Creation date
10/4/2006 6:39:03 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
5/12/1976
Description
Agenda or Table of Contents, Minutes, Resolution
Board Meetings - Doc Type
Meeting
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
65
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />I <br /> <br />I <br /> <br />MR. VANDEMOER: Mr. Chairman, could I ask a question? You know you <br />were making those studies on what fish were found in Ricardo Creek. <br />I think the last time you were here, you didn't know at that time what <br />type of cutthroat or what that was. You hadn't made the definite <br />distinction on the fish at that time. I believe that's right. <br /> <br />MR. KOCHMAN: That's correct, sir. <br /> <br />MR. VANDEMOER: I think the Board would like to know what you have <br />found out about that. <br /> <br />MR. KOCHMAN: Mr. David Langloiswith the Division of Wildlife is here <br />today. Dave is a very competent individual and the most competent when <br />it comes to the identification of fish species, especially the threatened <br />and endangered. I would like to ask Dave to come up and respond to that. <br /> <br />Before he does though, I would like to say I am sure our director and <br />the rest of the administration within the Division recognizes how <br />controversial this issue is whether it's Ricardo Creek or what. They <br />recognize that the Board has a great deal of responsibility, not only <br />from the minimum stream flow standpoint or other water users, too, and <br />whether it's the thing that Mr. Kroeger mentioned or Mr. Burr. Just in <br />case I don't get to say anything else, I know there is a lot of <br />appreciation for what is being done. I also think if we took a vote at <br />the Division of Wildlife, we would all say this is one of the most <br />controversial things we have ever been involved with. Probably if we <br />added it all up though we could say that it's fairly worth whi:J,e. <br /> <br />MR. STAPLETON: Mr. Kochman, before you leave, do you have any comments <br />on Mr. Ford's questions about the Cimarron River and the other? <br /> <br />MR. KOCHMAN: Yes, I think we can respond to those. Again, I would like <br />another individual to do it who is familiar with the situation, Mr. Bill <br />Wyler. Perhaps after Mr. Langley's response to Ricardo Creek, Bill <br />could come up and talk about each one of these. <br /> <br />MR. BROWNELL: I would like to ask a question. What schedule do you <br />select these streams on? How is the schedule made for selection? <br /> <br />MR. KOCHMAN: We have never made any recommendation for the Rio Grande <br />drainage. We have the available data, the cross section data, and at <br />this time we chose to submit them. They are certainly not all the <br />streams within the Rio Grande, but it's the ones we had supportive data <br />to make recommendations on. . <br /> <br />MR. BROWNELL: There is no method in your madness then? (Laughter) <br />This is what I want to know. I think there should be. <br /> <br />And another question. Why not do each of the streams of the total <br />watershed? There is"one stream here in the Valley that you do two of <br />the tributaries, but there are two others that aren't on there. I <br />think if any is involved on a given stream, the whole watershed ought <br />to be involved when you make this application, not one tributary of it. <br />It looks like somebody has thrown a dart at the map and has come up with <br /> <br />-27- <br />
The URL can be used to link to this page
Your browser does not support the video tag.