-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change "MPA" to "no take reserve" #158
Comments
I've changed question 506 to be worded "Is/are there no-take reserves or marine protected areas (MPAs) in the fishery? If so, are these well enforced and can they represent unfished size and density?" and have added "reserves" together with MPAs in the description. Anywhere else? |
There are no other questions where this appears to be an issue. Following is where MPA is used in options:
|
So I'm thinking that maybe we need to add the word "reserve" to where "MPA" or "marine protected area" appear in these options. I think option 4 (per above numbering) is fine as is - and possibly option 5. |
Looking back at the papers that options 1,2 and 3 are based on, all four (Babcock and MacCall 2011, McGilliard et al. 2011, Wilson et al. 2010, Kay et al. 2012) explicitly refer to the MPA or reserve being no-take. @NatalieDowling, in general I agree with your comment. I am putting the explicit changes I am suggesting below and passing back for a review. I can input into FishPath once we finalize the rewording. For 1 and 2: I suggest changing anywhere it says marine protected areas/MPAs to no-take reserve. For 3: I think also just switching to no-take reserve would be the most clear, unless we want to leave open the possibility that one could do this on an area with less protection than year-round no-take (even if its not be written up in the literature we provide). For 4: I agree that this can stay as is. For 5: We could update "no-take zone" to "no-take reserve" to keep it consistent. Otherwise agree that it can stay as is. |
Thanks Brian. Personally I think we need to keep these descriptions inclusive, partly because MPAs, reserves, and no-take zones can all mean quite different things from a management perspective and in terms of why each has been established. My suggestions (based on yours!): For 1 and 2: I suggest changing anywhere it says marine protected areas/MPAs to "marine protected areas (MPAs), or established no-take zones/reserves". For 3: As for 1 and 2. For 4: I agree that this can stay as is. For 5: I suggest changing all instances of "zones" to "zones or reserves" |
I like all of those suggestions, Natalie.
…On Tue, Apr 14, 2020 at 2:22 PM NatalieDowling ***@***.***> wrote:
Thanks Brian. Personally I think we need to keep these descriptions
inclusive, partly because MPAs, reserves, and no-take zones can all mean
quite different things from a management perspective and in terms of why
each has been established. My suggestions (based on yours!):
For 1 and 2: I suggest changing anywhere it says marine protected
areas/MPAs to "marine protected areas (MPAs), or established no-take
zones/reserves".
For 3: As for 1 and 2.
For 4: I agree that this can stay as is.
For 5: I suggest changing all instances of "zones" to "zones or reserves"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#158 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6IZLVEQE3XK7JOQ7YOAP3RMTHYLANCNFSM4FUNUWCA>
.
--
*Jason M. Cope, Ph.D.Research Fishery Biologist*
*Fishery Resource Analysis and Monitoring Division*
*Northwest Fisheries Science Center*
*2725 Montlake Blvd. East*
*Seattle, WA 98112-2013*
*NOAA Fisheries*
*jason.cope@noaa.gov <email@noaa.gov>206.302.2417www.nmfs.noaa.gov
<http://www.nmfs.noaa.gov/>*
|
Updates made (in bold):
This is a method for estimating localized abundance and determining target fishing rates in unprotected areas based on the ratio of fish density inside a no-take protected area to fish density in the unprotected area. Using this method, Babcock and MacCall (2011) and McGilliard et al. (2011) evaluated the use of the density ratio (DR) of fish inside and outside marine protected areas (or established no-take zones/reserves) in a management action to determine the direction and magnitude of change in fishing effort in the next year. They established that this comparative method can be used in any location that contains established MPA or no-take marine zones/ reserves with similar environmental and habitat characteristics to fished areas. According to Babcock and MacCall, this method is advantageous because historical data is not required, it can be used at localized spatial scales, and it is robust to environmental changes. The following link may serve as a useful resource for this assessment option: http://www.datalimitedtoolkit.org/
This is an assessment option developed by Wilson et al. (2010). It is a tiered decision tree based on four levels of length/size-specific catch-rate indicators for fish sampled inside and outside of MPAs, or no-take zones/reserves, and per-recruit. These four levels of length/size-specific catch-rate indicators are:
A permanent no-take zone or reserve is an area where fishing is prohibited for some or all species for a long period of time (usually more than 10 years). No-take zones or reserves are established to protect habitat, rebuild fish stocks, and protect against overfishing. No-take zones or reserves are not generally adjusted in response to performance indicators. |
For 3) Adjust based on data collected from closed areas or marine protected areas This one has the added wrinkle of closed areas listed as well. Seems like it could get kind of long and repetitive to change to "Adjust based on data collected from closed areas or marine protected areas, or no-take zones/reserves." Also, I noticed that there is an input category titled "MPA". Should this be updated as well? "MPA or No-Take Zones/Reserves"? |
Thanks for all this, Brian. Against 2) I think we need to throw is "established no take zones/reserves" a little more in the description - to distinguish from newly-established, or temporary, zones or reserves. For 3), good pickup. Thank you. Yes, I agree with your suggestion. And I think yes, we should update the input category. Thanks for the careful eye to detail; you are a legend. |
Inputted into FishPath.
For category name: Turns out there is no way to edit (or delete) an input category. I added a new input category with the new name, "MPA or No-Take Zone/Reserve", and replaced the old input cat in the options to fix the current issue. I will write a new GitHub issue to address the broader problem of not being able to edit/delete input categories. |
Fantastic – thank you, Brian. Great stuff.
From: Brian Snouffer <notifications@github.com>
Sent: Friday, 17 April 2020 6:07 AM
To: shcaba/FishPath-updates <FishPath-updates@noreply.github.com>
Cc: Dowling, Natalie (O&A, Hobart) <Natalie.Dowling@csiro.au>; Assign <assign@noreply.github.com>
Subject: Re: [shcaba/FishPath-updates] Change "MPA" to "no take reserve" (#158)
Inputted into FishPath.
1. added "established" before "no-take zones/reserves" in the description.
2. Additions in bold (done for both catch and effort limits):
Title: Adjust based on data collected from marine protected areas or established no-take zones/reserves
This option uses estimates of density or abundance from within marine protected areas (MPAs), or established no-take zones/reserves, to infer overall stock status. These estimates are determined either in isolation or in relation to estimates undertaken outside the MPA or no-take zone/reserve. The stock status is compared with a reference point(s), and the level of catch in areas open to fishing is adjusted accordingly.
For category name: Turns out there is no way to edit (or delete) an input category. I added a new input category with the new name, "MPA or No-Take Zone/Reserve", and replaced the old input cat in the options to fix the current issue. I will write a new GitHub issue to address the broader problem of not being able to edit/delete input categories.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub<#158 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJRE225SC7F3KEX6VADLJPTRM5QNBANCNFSM4FUNUWCA>.
|
No description provided.
The text was updated successfully, but these errors were encountered: