5 July 2021 - GRSF area standards: switching to polygons¶
- Table of contents
- 5 July 2021 - GRSF area standards: switching to polygons
Meeting Notes¶
Participants:
FAO (Emmanuel Blondel, Aureliano Gentile)
FORTH (Yannis Marketakis)
key points¶
Aureliano
As immediate needs the following is envisaged:
- a better representation of assessment areas/fishing areas over the map
- the possibility to detect intersections and percentage of overlapping among them. For example between a GRSF stock and a GRSF fishery, regardless the source. Or between two stocks or two fisheries. In case of two stocks, indeed any intersection is valuable, but we may start assuming that two records from the same source are already distinct and might not need to be computed (if this can help a bit your work).
- Detecting stocks per area can be through a map (i.e. drawing a BBOx) or by selecting an area code (e.g. selecting an area tag in the ckan) or by submitting coordinates in the GRSF Swagger.
Yannis
we need to test the polygons are properly visualized in the catalogue
area ontology: the use case "given an area code (e.g. 37) retrieve all those records with areas included/overlapped with that code": this information needs to be added in the knowledge base. Will provide a template to fill it.
GRSF API Swagger: a tool to facilitate users working with GRSF APIs which is accessing sparql endpoint. The extension we use on sparqlendpoint is experimental for polygons and we need to verify if the extension is working properly or not.
Emmanuel
from BBox to rich geometries, the computation is more complex, for example for intersections for which a refactoring is in progress.
the CKan map viewer has little flexibility for polygons across the date line. CKan does not have this feature the issue may persist in the maps of the record pages but it will be solved in the GRSF map viewer being made with a different technology.
Due to the switch into polygons, the coordinates are much longer and should be hidden in the catalogue pages but giving options to download in text format.
Intersections: percentage of overlap, distance etc. are available. However, as of today the percentage of intersections is the only information retained (in a table) but still not used.
Spatial searches are always via BBox for easier computation.
Actions¶
- FORTH to provide template for area codes equivalence/inclusions.
- New standards to be added in FIRMS and in the GRSF with reference to the documentation available at https://support.d4science.org/projects/stocksandfisherieskb/wiki/GRSF_database_overview#Area-standards-in-GRSF
