StocksAndFisheriesKB

They are 2 different functional requirements expressed here:

• Visualization: visualization the actual geographic extent of the record, which was the initial purpose of handling the polygons
• Geospatial search: not really a requirement in context of GRSF given the coarse geospatial resolution of records (generally speaking). In other words, I don't see geospatial search as fundamental GRSF requirement, but colleagues may advise differently. In any case, if this geospatial search may be need, it should be limited to bbox, and not detailed polygons. They are solutions to do geospatial search of detailed data, but CKAN is not a candidate

Coming back to visualization, the geospatial widget available as extension of CKAN, is a basic widget developed to fill the gap of CKAN technology (which is more a dummy tech in the field of GIS) that was not capable to handle the geographic extent of records like GeoNetwork.

If the approach is to keep CKAN as catalogue, the most complete solution would be to revert back to bbox as geographic extent (displayed through the CKAN widget), and to explore a way to dispatch (through the knowledge base) a map overview (as URL poiting to GeoServer WMS) for each record.

For the bbox, we should revert to the previous approach (cc @marketak@ics.forth.gr ) and for the map overviews, I will have to do some technical assessment and fulfill other activities required upstream (ie proper GRSF areas database exposed through OGC services)