Description

Integration for FlatGeoBuf format only for read remote layers.

Acceptance criteria

implementation order

• 1. Catalog/MetadataExplorer
• 2. TOC and new component layer (plugins: OL, Cesium (/components/map/openlayers | cesium)
• 3. map identify
• 4. styles support (in this case needed support to dynamic update of features)
• 5. update docs and tests coverage

Subtasks by Mapstore parts:

1. Catalog/MetadataExplorer add new module in API api/catalog/FGB with minimums methods exposed documented in api/catalog/index
   (ex. COG layer )

   API new module /api/FGB.js
   implements internal parser with basic methods, using OL when possible wrapping it and reuse common methods, base methods integration example of IFCModel )
   getFGB load data from URL use OL deserialize() in fgb-ol OR VectorTileSource()

   in Catalog Epic addLayerAndDescribeEpic and support for FGB format:
   example edits
   MetadataExplorer mapping new format FGB in serviceTypes

   CSW mapping new FGB format ‎web/client/api/catalog/CSW.js

2. TOC support FGB layer

   new Component Layer
   define new layer in (plugins: OL, Cesium (/components/map/openlayers|cesium)
   (mandatory for rending inside map)

   in DefaultLayer apply this same workaround, also for FGB format.
   example edits

   Check support “legend render”, visibility, opacity in layerNode for FGB in TOC

3. Mapstore Identify
   update utils/mapinfo the same of Model format here:
   example edits

4. update docs and tests coverage
   example edits
   High Priority tests for api/model/FGB and api/catalog/FGB

Other useful information

• flatgeobuf version used v3.38
• Official Specs: https://flatgeobuf.org/#specification
• good FlatGeobuf GuideLines:
  https://guide.cloudnativegeo.org/flatgeobuf/intro.html
• OpenLayers Samples: https://flatgeobuf.org/examples/openlayers/
• API Docs https://unpkg.com/[email protected]/dist/doc/index.html