21-12-02-GRSF area standards with FAO, FORTH, FishSource¶
- Table of contents
- 21-12-02-GRSF area standards with FAO, FORTH, FishSource
Participants:
FishSource (Merul Patel, Patricia Amorim, Susana Segurado)
FORTH (Yannis Marketakis)
FAO (Bracken van Niekerk, Aureliano Gentile, Arturo Muñoz Albero)
Meeting Notes¶
Key points¶
FAO
Suggestion to include a code field in the FishSource API in order to clearly distinguish the description of the area from the code to be used in the semantic identifier.
Sharing of GRSF_area_standards to be done in the GRSF Wiki, that include guidelines for the definition of areas and codes for records.
Highlighted that those records whose code is set as "other:" should be actualized to "unk:", as stated in the GRSF_area_standards. The new competency queries developed by FORTH on codes and names easily allow to detect wrong entries (e.g other or unknown). See at https://i-marine.d4science.org/group/grsf_admin/grsf-competency-queries (scroll down to the bottom under "GRSF Resources Queries").
Noted that the UUID is the unique element identifying the stock or fishery, the semantic ID contributes additional information that helps to quickly identify the record and doesn't necessarily have to be unique, for example fisheries onshore/offshore which can have the same semantic identifier.
FishSource
Suggestion to link all areas to FAO areas (i.e. gfcm areas linked to FAO 37 areas) to facilitate data queries and future analysis. This can also be done for subareas within an eez country area, etc.
Highlighted the need of creating a repository with all areas for cross-checking that FIRMS, RAM and FishSource are aligned in the procedure for defining areas and to avoid the same area to be defined differently by each of the partners.
Noted the potentially continuous issue on granularity, especially in the Pacific e.g. Indonesia, with unique semantic identifiers. Will have to keep adding additional information in the semantic identifier.
FORTH
It would be possible to extract from the knowledge base "csv" files with area codes used for FIRMS, RAM and FishSource, but it would not be the whole classification. What currently is included in the knowledge base is not all that is contained in the database. Adding those new classifications will be an important improvement for the database.
Actualization of the area codes of all approved records could be performed manually by FORTH as there is difficulty with extracting the fisheries due to the mismatch of the original IDs in the dissection process, which could potentially cause issues with the GRSF KB refresh.
Proposed the next refresh of the GRSF KB in January 2022.
Actions¶
A new field "CODE" under "fishing_areas" will be included in the FishSource API to expose the area code (see i.e. https://www.fishsource.org/api/bluebridge/v5/stock/1588), well distinct from the area name (currently in the field "name").
Where possible, area codes will be aligned with the GRSF_area_standards. The GRSF_area_standards Wiki page will be actualized with new code systems that will be developed (i.e. NZL area codes, AUS area codes, USA area codes, etc.).
Regarding the need to relate most granulated areas relate to higher level areas (i.e. NZL QMAs related with NZL EEZ, NZL EEZ related with FAO areas), in the GRSF this should be done at GRSF KB level as well as at the geospatial intersection engine.
Coordinate work of SFP and FAO (Ms Patricia, Mr Arturo) on national and sub-regional area standards.
The Wiki page GRSF_area_standards should be enriched with links to the GitHub repository where available. When a GitHub repository is not available for a specific standard, FORTH expressed its availability to create and maintain such repositories. Once done, FishSource will use these "sources of truth" for validating its area codes.
FishSource to expose the updated API for FORTH to harvest.
