12 October 2022 - GRSF area standards¶

• Table of contents
• 12 October 2022 - GRSF area standards
  • Meeting Notes
    • Area standards
    • SDG 14.4.1 Questionnaire
    • Traceabilty Units
  • Actions
  • Resources

Participants:
FishSource (Patricia Amorim, Merul Patel, Susana Segurado)
FAO (Emmanuel Blondel, Aureliano Gentile)
FORTH (Yannis Marketakis)
UW/RAMLDB (Michael Melnychuk, Arturo Muñoz Albero)

Meeting Notes¶

Scope of the meeting was to report on the activity between FAO and the University of Washington on “Improving area standards of the RAM Legacy Stock Assessment Database (RAMLDB) and further review and validation of RAMLDB records loaded in the Global Record of Stocks and Fisheries (GRSF)".
National and regional areas have been collected, properly meta-informed, and stored in the GRSF github repository, now ready to be ingested in the GRSF source databases (RAMLDB, FishSource, FIRMS), as well as to be computed and rendered within the GRSF records and maps.
The call was also the opportunity to update the group on the latest developments on Traceability Units and FAO SDG 14.4.1 questionnaire.

Area standards¶

• Mr Arturo Munoz presented the work done on harmonization and standardization of the GRSF area codes. The work was carried out during the 2022 and covered regional, national and sub national level areas.

• The areas are standardized by always collecting the following data:

  • Country. 3alha code of the country that the area pertains to.
  • System owner. Code and name of the agency that defines the code-system of the related area.
  • Code system. Code and name of the code-system in which the area is included.
  • Differentiating code system. For those areas in which the code-system leads to confusion with other code-system from the same system owner and country, a differentiating code-system is defined (if not available) for ensuring the areas are clearly differentiated. Code and name of the differentiating code-system are recorded.
  • Area code: code of the area, as defined in the code system.
  • Area name: name of the area, as defined by the system owner.
  • Area type: type of area, as defined by the system owner.
  • Typology: typology of the area by analyzing the area type and the use by related agencies. The 4 groups defined are: management area, statistical area, assessment area, biological area. Further description and analysis on areas' typologies will follow.
  • Species specific. Yes/No field for clarifying if the area is species specific (i.e. only applying to one species or group of species) or not.
  • Parent area. FAO Major Area(s) in which the area described is within.
  • Layer name. Name of the layer that represents the area as per the system owner. The main difference with "area name" is that "layer name" tends to be in an standardized format (i.e. Functional Unit 1), while "area name" can be the common name of the area (i.e. Chatham rise, name of the bay, strait, sea, etc.)
  • Source. Website in which the area is defined.
  • georef. Geo-referencing process name and code for connecting the areas files with the shapefiles.
  • Shapefile. GIS file in which the area polygon can be found.
  • Coordinates. If necessary, coordinates of the area as defined in the official source.
  • Other data. Open field for including further information that could be of use.

• Mr Arturo Munoz also presented the proposal for connecting the RAMLDB and GRSF databases with the area files and GIS polygons. The full description of the connection process can be found in the attached PPT "GRSF Records areas - Standards and Connection process.pptx".

Among other operational decisions, it was conveyed that GRSF records - upon codes from the git vocabulary - will inherit the labels stored in the vocabulary and replace those from source databases.

SDG 14.4.1 Questionnaire¶

• Mr Yannis presented the Excel based workflow for the submission of SDG14.4.1 records. FORTH has developed an interface to upload SDG records via an Excel template including the possbility to merge or updated already exisiting records. The environment is ready for completing the tests in GRSF Pre VRE and eventually moved into production (GRSF Admin, GRSF public VREs).

Traceabilty Units¶

• Mr Yannis presented the work carried out so far for the traceability units at KB level including competency queries and API - web services. The GRSF CKan catalogue now needs to be configured to host such new information domain.

Actions¶

• Arturo to liaise with Emmanuel Blondel and Yannis Marketakis for completion of area codes in GRSF and related ingestion in the geospatial database for being rendered within the GRSF records.
• Arturo to liaise with SFP for completing national area files, e.g. Russia.
• Arturo to liaise with UW colleagues for addition of the new area codes in the RAM database.
• Aureliano to run tests on FAO SDG records with Anne Elise.
• Aureliano and Bracken to validate the last batch of RAM records provided by Arturo
• Yannis to update the gear and species vocabulary in git

Resources¶

• GRSF Github https://github.com/GRSF