GithubHelp home page GithubHelp logo

Comments (5)

MargaretSiple-NOAA avatar MargaretSiple-NOAA commented on August 19, 2024

from gapindex.

MargaretSiple-NOAA avatar MargaretSiple-NOAA commented on August 19, 2024

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.

BenWilliams-NOAA avatar BenWilliams-NOAA commented on August 19, 2024

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.

zoyafuso-NOAA avatar zoyafuso-NOAA commented on August 19, 2024

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.

zoyafuso-NOAA avatar zoyafuso-NOAA commented on August 19, 2024

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)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.