16 November 2018 - Bugs check¶

Meeting Notes
Topics: Checking bugs for the Stock module of the GRSF

Participants:
FAO (Aureliano Gentile)
FORTH (Yannnis Marketakis)

• Table of contents
• 16 November 2018 - Bugs check
  • Notes
  • Follow-up actions
    • Bug fixing
    • Union of Polygons (bboxes) in case of merge records
  • Resources

Notes¶

The following bugs were discussed in details:

• https://support.d4science.org/issues/12261 (RAM time series not differentiated or duplicated, still not clear which is the issue)
• https://support.d4science.org/issues/12277 (merge action does not work)
• https://support.d4science.org/issues/12420 (Narrative text is messed up when in multiple xml nodes)
• https://support.d4science.org/issues/12419 (Fishing Pressure time series is missing in several records)
• https://support.d4science.org/issues/12424 (Stock status FAO categories not properly handled)

Follow-up actions¶

• FORTH to update tickets and work on that in collaboration with CNR
• FAO to indicate what to do for polygons in case of merged records:

Bug fixing¶

It was agreed that the bulk approve can take place after having solved the bugs in issues #12261, #12419, #12424.
As regards, #12420 FORTH will examine if it can be resolved without re-constructing the GRSF KB (the sequence of narrative text was not defined as important).
The bug on merge action (#12277) is the only one which can be solved also after the bulk approve (within a reasonable lapse of time).

Details about how to proceed with the aforementioned issues will be defined in the corresponding tickets.

Union of Polygons (bboxes) in case of merge records¶

On "what to do for polygons in case of merged records", E.Blondel's reply:

• The generic rule to apply is to keep the bbox distribution of both records, and do a union of bbox geometries.
• This can be provided easily through a "geo-service" that takes 2 geometry inputs (as they are reported in CKAN records, as GeoJSON format), and return the union of it, in GeoJSON format.

Example of geometry union service request:

http://dataminer-prototypes.d4science.org/wps/WebProcessingService?request=Execute&service=WPS&Version=1.0.0&gcube-token=dc3313f2-335e-476f-b4e8-1db1745b93d4-843339462&lang=en-US&Identifier=org.gcube.dataanalysis.wps.statisticalmanager.synchserver.mappedclasses.transducerers.GEOGRSF_BBOXUNION&DataInputs=geom1=%7B%5C%22type%5C%22%3A%5C%22Polygon%5C%22%2C%5C%22coordinates%5C%22%3A%5B%5B%5B-20%2C-50%5D%2C%5B-20%2C-6%5D%2C%5B30%2C-6%5D%2C%5B30%2C-50%5D%2C%5B-20%2C-50%5D%5D%5D%7D;geom2=%7B%5C%22type%5C%22%3A%5C%22Polygon%5C%22%2C%5C%22coordinates%5C%22%3A%5B%5B%5B-10%2C-50%5D%2C%5B-20%2C-6%5D%2C%5B40%2C-6%5D%2C%5B40%2C-50%5D%2C%5B-10%2C-50%5D%5D%5D%7D;

The request handles 2 inputs geom1 and geom2 that should be geometries in GeoJSON format, exactly what is handled in GRSF records, e.g. http://data.d4science.org/ctlg/GRSF_Admin/a20b4472-d8d2-391b-9946-42ee7f76fae2 and http://data.d4science.org/ctlg/GRSF_Admin/4cb84771-3dd8-3061-b379-094346319e6a

To make it work, make sure that input parameters geom1 and geom2:

• are using single quote (in replacement of double quote in GeoJSON strings) OR double quotes but correctly escaped
• are URL encoded

This service approach is fine as long you deal with bboxes (small geometries).

Resources¶

• GRSF requirements
• GRSF Definitions