List view

• QA Engine

  Implement a high TRL QA engine (i.e. usable) on top of PCAPI filter-chains. As a reminder, an example chain that filters by envelop, date and exports as geojson is: filter=envelope,date,format&bbox=-2.33,33,0.10,34.44&start_date=20151101_12:00:00&end_date=20160105_12:00:00,frmt=geojson Since all filters share parameters we need to avoid name collisions. All new QA parameters should be prefixed by the filter name and underscore e.g. filter=los,los_bearing=-1. The old PCAPI filters keep their existing names.

  No due date

  •3/4 issues closed
  75% complete1 open3 closed

• Implement an extensible OGC OWS endpoint on top of PCAPI

  PCAPI already supports most operations of a WFS/SOS. By providing a WFS and SOS wrapper around existing PCAPI functionality we can implement robust OGC services which can actually work and produce complex schemas dynamically. Other 3d party software have already been tested and none was found to provide a robust service that can generate complex schemas dynamically without post-processing (XSLTs or custom scripting) hacks.

  No due date

  •4/4 issues closed
  100% complete0 open4 closed

• PCAPI downscaling

  Drop the legacy FTGB code which takes up more than half of existing PCAPI's codebase.

  No due date

  •4/5 issues closed
  80% complete1 open4 closed