Comments (5)
from gapindex.
Never mind! Zack has already looked! He asked me to paste this since he can't log into his GitHub at sea:
Hi Ben,
Thanks for looking at the tables. For the Bering Sea shelf and slope surveys, the definitions and/or shapes of the strata are periodically updated. The “DESIGN_YEAR” field in the GAP_PRODUCTS.AREA table is used to version those changes over the years. That means that there will be duplicate AREA_ID values for a given survey. The GAP_PRODUCTS.SURVEY_DESIGN table tells you which DESIGN_YEAR to use for a given survey and survey year. So, if you wanted all of the spatial records for the Bering Sea slope survey, you want to be filtering for AREA_ID values where DESIGN_YEAR = 2002.
Thanks,
Zack
from gapindex.
Thanks you two. One note though for my clarification.
While reviewing these fields I filtered out anything 2023+ so am skipping the duplicate field during that.
For the EBS slope there are two design years 2000 and 2002 which do have duplicate area_id fields.
Is there a guide where survey_definition_id
, design_year
and area_id
are identified , for example here is what I gather the GOA codes are:
survey definition 47 = GOA area_id
type = "stratum" 10:550
type = "region" 99903
type = "INPFC By Depth" c(911:914,921:924,931:934,941:944,951:954)
type = "inpfc" seq(919,959,10)
type = "depth" - all 991:994
type = "area" - regulatory 803:805
but when I get to the EBS slope there are two survey_definition_id
's (78, 98) with the following design years:
design_year survey_definition_id
<dbl> <dbl>
2022 78
2000 78
2002 78
2022 98
2019 98
2010 98
2002 98
1993 98
1992 98
All of the survey_definition_id == 98
appear to be for the shelf except for the design_year == 2002
which has slope subarea in the description (and has the duplicate area_id with survey_definition_id == 78, design_year==2000
). Is this correct? and if so I could really use a guide.
from gapindex.
Sorry again for the late response. Just got back from survey and post-survey leave.
Ohh, okay I see what you mean. I think the records in GAP_PRODUCTS.AREA where we have survey_definition_id == 98
and design_year == 2002
are erroneously duplicated from records associated with survey_definition_id == 78, design_year==2002
. We'll remove those records to avoid confusion. So if you are only interested in Bering Sea Slope records in the GAP_PRODUCTS.AREA, filter records with survey_definition_id == 78, design_year==2002
.
A guide for which design year to use for a given survey/year can be found in GAP_PRODUCTS.SURVEY_DESIGN.
from gapindex.
The gap_products.area table has been cleaned up to remove duplicates and non-standard areas. Closing the issue here unless anything comes up again.
from gapindex.
Related Issues (20)
- Update documentation: get_data() output dfs
- Added functionality for multiple regions HOT 1
- Error checkpoints for calc_size_stratum_BS/AIGOA(): unavailable data
- Data pulls for model-based estimates HOT 3
- AI-GOA Age Data Upload Schedule HOT 5
- Data input for Agecomp scripts (PERFORMANCE codes) HOT 4
- Regional differences in size composition calculation HOT 3
- gapindex::get_data error in function : Error in fix.by(by.x, x) : 'by' must specify uniquely valid columns HOT 16
- calc_biomass_subarea bug HOT 1
- Issue with get_data() when there's no size/age data HOT 1
- AREA_ID = 99902 not returned from calc_biomass_subarea() HOT 5
- [tasks] Specify AFSC database in get_connected() HOT 2
- are all species in the spp_start_year table? HOT 2
- data access HOT 6
- SPECIES_CODE changes in GAP_PRODUCTS break functionality
- Name of functions for calculating comps by subareas/areas/regions HOT 2
- SPECIES_CODE changes in GAP_PRODUCTS break functionality HOT 11
- connecting to database via VM HOT 2
- gap_products not matching gapindex for agecomp HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gapindex.