giseldo/neodataset huggingface dataset:
FE: If FF display solution to enable container queries

If running FF display info on how to enable container queries

![image](/uploads/6dfbf9fcbed222e7fc8d4ad4104aa987/image.png)


You can check for not supporting container queries like:
```
if (!('container' in document.documentElement.style)) {
 // I do not understand container queries
}
```
https://github.com/GoogleChromeLabs/container-query-polyfill/blob/main/src/index.ts

Story points: 3.0
FE: inform users to update to newest browser version

With the use of a modal, (1) inform users about the browser issue, and (2) redirect users to a possible solution.

![image](/uploads/56b913a1d80adff23deb655c32fe4e5b/image.png)

* users should be able to click away the warning
* check if the browser support container queries, if not show dialog (that way, in the future, when the browser does support it, we don't have to change anything in the code)

Story points: 3.0
FE: inform user of minimal browser version in index.html

Issue:
- the browser won't run javascript and the application cannot be shown (blocking)

Desired solution:
- Add an info text in the base html of the application (`index.html`) telling your that GeoWeb is loading:
"Loading GeoWeb......" -> see if it is annoying for the "normal" users.

To replicate issue:
- Run application from build
- Modify the dist folder so it contains invalid js
- Try and run it in your modern browser

Story points: 2.0
FE: TAF: publish draft AMD/COR without changes gives wrong message

Publishing a previously saved (and changed) AMD or COR TAF results in a message that there are no changes in the TAF

### Steps to reproduce

* Make a new TAF, save it and publish it.
* Make a correction, change the TAF and save it
* Publish the saved TAF. A message displays that there are no changes in the TAF

- Taf is available in the list - you should be able to find via previousId
- Compare current draft to that original TAF excluding the following fields:
     - baseforecast: valid start
     - validDateStart
     - messageType
     - issueTime
     - previousId
     - previousValidDateStart
     - previousValidDateEnd
     - uuid

Story points: 3.0
FE: Incorrect title for COR and AMD

When going to a published TAF-> hit editor-mode-> then press Correct: The title header still shows 'Published'. If you now save the draft it will be called 'Draft Corrected'

For New amendments and corrections we need to base the title on the action taken by button:
* New Correction
* New Amendment

Also, for status amended and corrected, rename title to:
* Published Correction
* Published Amended

Please ensure that the tooltips on the icons in the location tabs and the TAC overview are not affected as they are also based on the same function I believe.

Story points: 3.0
FE: TAF COR. When editing and leave for 5 minutes all input is gone

When Correcting a published TAF and I put content into the draft without saving, and then leave the screen untouched for approx. 5 minutes, all new content is gone. This could very well happen in a situation a meteorologist gets one or multiple calls and is not working on the TAF for a bit.

- Could be related to shouldUnregister: true, we need to investigate what the issue is here
- Related to the poller that runs every 5 minutes refreshing the list and potentially clearing out the form?

Story points: 3.0
FE: fix flaky tests

Taf
- https://gitlab.com/opengeoweb/opengeoweb/-/jobs/3643752770
- https://gitlab.com/opengeoweb/opengeoweb/-/jobs/3666971763
- https://gitlab.com/opengeoweb/opengeoweb/-/jobs/3689341618

Shared
- https://gitlab.com/opengeoweb/opengeoweb/-/jobs/3593519010

Spaceweather
- https://gitlab.com/opengeoweb/opengeoweb/-/jobs/3681899733

Story points: 2.0
FE: sigmet/airmet add tests to prevent sigmet2tac to break

When working on sigmet2tac, I could not get the unit tests to work. To ensure extra safety, we need some extra checks to make sure unrendered inputs are not send to the sigmet2tac (or perhaps later when posting a form)

possible scenario sigmet
- choose a new sigmet, make sure you have volcanic fields in and type as far to make a sigmet2tac
- choose other phenomenon, and do another sigmet2tac call, should have not the volcanic fields included

Story points: 2.0
FE: Airmet Broken Cloud above and surface checkboxes not displayed correctly on React 18

- create a new Airmet
- choose phenomenon `Broken Cloud` or `Overcast cloud`
- fill in levels like this, with Above and SFC checked:
- ![image](/uploads/a7690c1047f5659018c11cd537285665/image.png)
- save as Draft
- open it from the list
- the levels should be displayed correctly
- instead, the Above and SFC checkboxes are shown unchecked (they did get saved correctly):
- ![image](/uploads/78592f1f6a1671bca2d147192b31e657/image.png)
- if you click Save or Publish, the fields get populated and saved correctly. But they show up very late.

Story points: 3.0
FE: Volcanic Ash Cloud fields missing on published and cancelled Sigmet in React 18



On React 18 the Volcanic Ash Cloud fields are not shown, see images below which fields. To reproduce:

- create a Volcanic Ash cloud sigmet with Volcano name and coordinates filled and publish it
- open it from the list
- expected: the Volcano name and coordinates are visible
- actual: Volcano name and coordinates are missing
- Cancel it and choose a FIR that it's moving to
- open the Cancels sigmet
- expected: text `Volcanic Cloud is moving in the direction of:` is visible
- actual: the text is missing
- open the Cancelled sigmet
- expected: the Volcano name and coordinates are visible
- actual: Volcano name and coordinates are missing

They are saved correctly but not getting displayed.

![image](/uploads/3583262058402eca8ac7e3e172fb6198/image.png)
![image](/uploads/43bbece583125f6661810fbf86d6eccb/image.png)

Story points: 3.0
FE: TAF extra drafts created when switching between a corrected and draft corrected/amended TAF in React 18

To reproduce:

- use React 18 branch
- nx serve
- open TAF module
- publish a TAF correction
- set the correction to editor mode
- click Correct
- click Save
- now you should have one correction and one draft correction for the same location, the draft correction is currently open
- select the correction
- select the draft correction again
- this will trigger autosave and another draft correction is saved, you will now have 2 draft corrections and one correction for the same location
- same happens for amendment

On master the autosave is not triggered here.

Story points: 3.0
BE: cleanup satcomp wms from presets

* In this file: https://gitlab.com/opengeoweb/backend-services/presets-backend/-/blob/main/staticpresets/view-presets.json links to satcomp should be replaced with the satellite wms
* Line 57: update link to adaguc server wms & satellite as msgrt has been added to geoweb adaguc server
* Double check where static preset data is written into database

Story points: 2.0
Harmonize layer types in older to solve #2859 - part 2

This is part 2 to correctly solve https://gitlab.com/opengeoweb/opengeoweb/-/issues/2859 (FE: Layer info not visible for all layers)

Layer interfaces are re-used where possible.

To test: Make sure everything layer related still works.

See MR https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2175

Story points: 1.0
BE: new TAF BE - migrate current state of TAF

Import data from DynamoDB to ensure compatibility

If it is very difficult, skip this. When going to PRD, it has been accepted that older TAFs cannot be accessed for a single timeslot.

For development: functionality to grab data with a /taflist call and copy into database

Should not be more than 1.5 days of work, or if it feels not feasible after a couple of hours, it can be dropped

Story points: 3.0
FE: Published clock symbol shows 'Upcoming' in TAF overview

When a TAF gets published a green clock symbol shows up in the TAF overview and in the editor menu on the left. When you go to a published TAF in the menu on the left and it opens it shows 'Published' in the title header. When you hover the green clock symbol in the TAF-overview a popup appears with 'Upcoming' This leads to confusion. 

When hovering the green clock-symbol, the text should say 'Published' to prevent confusion. Fix could be to show status from BE on hover

Story points: 2.0
BE: Clean up of TAF table

### Test criteria

* All databases (especially TST/ACC/PRD) should be cleaned up
* TAFs in databases should be accessible for 10 days
* It is proposed to integrate the cleanup of the database into the "tafplaceholder" lambda which runs every hour.
* Use startDate (start time of validity) to determine if the TAF is older than 10 days.
* While developing, try to use a different retention time so not everything is removed at once (testing)

Story points: 3.0
BE: Implement new cleanup in GeoWeb-Adaguc

If you use the latest nested stack version of adaguc, then we can configure the clean up as part of the layer configurations

Latest version is 1.3.4

Then we could remove all the eventrules in the cloudformation

For the layers that should be cleaned up, three properties should be added to the configuration: RetentionPeriod, RetentionType & EnableCleanup (see [documentation](https://github.com/KNMI/adaguc-server/blob/master/doc/configuration/FilePath.md))

On ACC this cannot be tested for all datasources (will only work for event based datastreams), this should nog be a problem

Story points: 3.0
Release to ACC Tue 17/1/23

Confluence: https://confluence.knmi.nl/display/GW/GeoWeb+2.7.1

Release to ACC failed with following message: `Resource handler returned message: "API Key already exists (Service: ApiGateway, Status Code: 409, Request ID: 14f972e9-f0bf-4071-89d4-1cd9b392d89d)" (RequestToken: e39651e4-d83b-fb05-07cf-b89803483f46, HandlerErrorCode: AlreadyExists)`

Story points: 3.0
In Layer interfaces: Change the text property to title, in order to harmonize layer types

This is part1 to correctly solve https://gitlab.com/opengeoweb/opengeoweb/-/issues/2859 (FE: Layer info not visible for all layers)

`text` property is named `title` where possible.

The `text` property on some layer interfaces was needed to accommodate previous ExtJS components. The text property does represent the title property of the layer. We currently need many unnecessary conversions from text to title and vice versa. This MR harmonized that.

To test: Make sure everything layer related still works.

MR: https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2173

Story points: 1.0
BE: Update openapi specs for TAF

An issue reported by Marcel brought forward the following problem: in the openapi specification a validation case is missing where the change group contains _only_ a "probability" field and **not** a "change" field. 


#### What should be done?
Currently, the "change" field is set as required. An additional validation case should be created where the "probability" field is required and should have a value of "PROB30" or "PROB40" and the "change" field may be left empty.


#### Requirements
The changegroup below should be accepted by the openapi specification. In a change group:
1. The field "change" is not empty, the field "probability" may be empty
2. The field "probability" is not empty, the field "change" may be empty
3. Both may be not empty
4. At least one of the two should have a value


#### Example
Changegroup causing error:
```
 {
        "probability": "PROB30",
        "valid": {
          "start": "2022-11-23T05:00:00Z",
          "end": "2022-11-23T08:00:00Z"
        },
        "visibility": {
          "range": 4000,
          "unit": "M"
        },
        "weather": {
          "weather1": "BR"
        },
        "cloud": {
          "cloud1": {
            "coverage": "BKN",
            "height": 4
          }
        }
      }
```

Story points: 2.0
FE: wmjsmap doesn't currently work with React 18 in Strict mode

We be fixed in:

1. https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2081
1. https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2105
1. https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2124

Story points: 5.0
Investigate alerts coming from presets

>  [Alerting] Nginx ERROR ALERTS (tst) alert
> 
> A Nginx error occurred in the Presets Backend service. Affected environment: tst

NGINX looking up token to talk to cognito. Latest fix to cater for cognito changing IP did not fix the problems.

- Possibly exceeding amount of connections? Try this and see if it fixes it.
- Could possibly be that the FE is working fine and the message is simply a warning or if it is really failing?

Story points: 3.0
Investigate: Getting 403 errors when loading TAF interface

Investigate the issue and see if we can reproduce.

This occurred during the TAF-testing period in the weather office on ACC when multiple people were working at other positions at the same time.

The only thing I did a couple of times after each other was:

* Reload GeoWeb
* Login
* Click on the hamburger menu select TAF
* This is the moment the 403's were encountered.
* After another click in the menu the error went away

Story points: 3.0
ADAGUC: Add GOES images to Satcomp GeoWeb system WMS

Goals of this issue is to add the newly processed GOES satellite images for the BES to the existing Satcomp system WMS services of GeoWeb.

Link to WMS with both existing Satcomp and newly processed GOES BES : https://adaguc-server-wkdinnov.wlm.acc.knmi.cloud/adaguc-server?dataset=satcomp&service=WMS&request=GetCapabilities

Note that, because of cost reduction, images for BES are currently updated every 1 hour.

MR already created: https://gitlab.com/KNMI/geoweb/geoweb-adaguc-server/-/merge_requests/48

Story points: 2.0
ADAGUC: Add faultlines database

The standard fault line database in the GeoWeb dashboard should be **replaced** by the [GEM Global Active Faults Database](https://github.com/GEMScienceTools/gem-global-active-faults).

Implement the GeoJSON file: [harmonised file](https://github.com/GEMScienceTools/gem-global-active-faults/blob/master/geojson/gem_active_faults_harmonized.geojson)

Ensure keep the same name so it works with the existing preset

Story points: 3.0
FE: Clicking on map triggers getFeatureInfo

Add a button that allows you to click on features on the map to trigger a getFeatureInfo. The information retrieved will be shown in a pop-up.
- Add tests
- No snapshots as there is no design yet!

(meta)data window (see attached screenshot as an example)

* when the user clicks on a event marker, the selected marker needs to be clearly identifiable
* when the context window is not open yet, the window will appear when the user clicks on a event-marker
* the window will display the (selected) content of the active event-marker
* the window can be resized
* the window can be closed
* the window can be moved around within the map view (to discuss how to deal with multi-tiled map views)
* the last position of the window before closing will be saved for future use
* each map can have one pop-up over open

Story points: 3.0
FE: layermanager fix opacity select

Some issues to fix with the opacity slider:
- styling is not correct
- zIndex is not correct
- doesn't show correct position for medium layermanager (for example if you open row 3) 

![Screenshot_2022-11-14_at_08.48.57](/uploads/6865a946def4d63c3bc96107765e7283/Screenshot_2022-11-14_at_08.48.57.png)

Story points: 3.0
FE: add firefox container queries polyfill to fix layermanager size issues

The firefox polyfill works locally, but breaks in the build and showing a blank screen. It looks like the css is broken, because buttons still seem to click. Maybe we can use the cdn link and include it somehow? Or some (babel) config for build which we can tweek? 

The polyfill has been moved in the MR to the polyfill file in the app. 

To test:
- firefox should work (in the build)
- firefox should be able to show correct container queries

Check the MR: https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/1985. To test this out with the build, deploy to poc.opengeoweb.com after the build is ready in Firefox. (maybe this can be tested locally as well?)

Without this polyfill, the layermanager in firefox is not working correct, like not showing the correct size buttons or handling resize correctly.

Story points: 3.0
BE: PresetsBE: Update Aurora RDS postgres version

Update https://gitlab.com/KNMI/geoweb/backend-services/deploy-presets-backend/-/blob/master/cloudformation.cfn.yaml#L541 to new version. (11.13 would suffice, but maybe 14 is better).

The database will automatically update, but make sure that this is really the case.

This was done as well for the adaguc nested stack: https://gitlab.com/KNMI/shs/adaguc-server-cfn/-/blob/master/rdbms-postgres-serverless.component.cfn.yaml#L116

Story points: 1.0
FE: ServicePopupConnect rerender issue

Move the ServicePopupConnect up the child tree, so it won't rerender when LayerSelect is rerendering. Probably some redux state needs to be added to the `layerSelect` store, so we can hide/show it on every place as long as it's a connected component.

To test: `console.log` the component, and see if it does not rerender when searching for example for new service. Hold in account that the docked layermanager can cause issues with this, we should be careful when to render the component.

Story points: 3.0
FE: Fix initial load of service chips

Show all services as disabled initially, and when ready enable them one by one.

Ticket is re-opened because of issues with selecting knmi services, code has been reverted. Should wait for https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2073

- fix issue with knmi services
- reducer should be rewritten so it's more readable

Story points: 3.0
FE: Layer info not visible for all layers

See US

- Part1: https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2173
- Part2: https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2175
- Part3: https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/2199

Story points: 2.0
FE: layermanager dock/undock

- add layermanager ~~to screenmanager view~~ to mapStore
- add layermanager as prop to the ~~screenmanager store~~ map store with properties:
    - isOpen
    - ... width/size (later ticket)
    - ... position (later ticket)
- add layermanager actions show/hide per map
- possibly sagas need to help to connect the different store modules (ui/map)
- only focus on this ticket on the show/hide button of the layermanager; not the main control button of layermanager on the map

see: https://www.sketch.com/s/4a6c597a-34a0-4382-ba18-e8de658f132d/prototype/a/E85F4838-1508-48A2-9D2C-47AFE660F1EB

Story points: 5.0
BE: Fix comments on FMI-avimessageconverter lib

Can affect other libraries, include updates. Main focus on FMI-avimessageconverter

Refine comments, plan of action
If comment means lot of work, create separate ticket. Link as "to do" in code and pick up (or in next sprint)

Link to MR and review comments: https://github.com/fmidev/fmi-avi-messageconverter/pull/100

Comments:
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974932710
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974933055
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974935517
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974941462
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974941847
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r975136677
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r975184529
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r975289369
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r975302052
 - [ ] __: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r975310439
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r977188468
 - [x] BH: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r989696087
 - [x] EV: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r975013125
 - [x] EV: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974933055
 - [ ] EV: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974973461
 - [ ] __: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974979761 TBD!!
 - [ ] EV: https://github.com/fmidev/fmi-avi-messageconverter/pull/100#discussion_r974986298
 - [ ] 
Put your initials if you're working on a comment. And tick the checkbox when done. Commit your work to branch `merge-fmi`: https://gitlab.com/opengeoweb/avi-msgconverter/fmi-avi-messageconverter/-/commits/merge-fmi

Story points: 5.0
FE: layermanager size buttons

When clicking the buttons, add the size the layermanager. Use width/heights, the container queries should do the rest (don't use types for this). Always hide your current size button.

- the layermanager should always be in view. If it's too big, it should jump back to be visible inside screen (if too big split in separate ticket).
- also fix the header height, on small screen should be small

Story points: 3.0
FE: TAF sorting in TAF overview current and expired

Check if sorting based on issue date goes as required: the order should be for every station the current TAF on top and the expired TAF below. Do not use status but issue date, as the expired TAF should have an earlier issue date.

NOTE: A placeholder TAF does not have an issuedate, but it should still sort correctly. In that case expired should still show below current.

NOTE2: The examples in the user story that went wrong are all with corrected and amended tafs. A draft correction or amendment also doesn't have an issuedate, make sure to handle these as well.

Story points: 2.0
BE: Number of TAFs in TAF overview current and expired

In the TAF overview current and expired there always should be visible the current TAF and the expired TAF for every station. The order should be for every station the current TAF on top and the expired TAF below.


Required:
* Should return correct number of TAFs
* Expired TAF should be returned after the current TAF per station
* FE takes care of sorting of stations

Story points: 3.0
BE: TAC starting new lines goes wrong with PROB and TEMPO

In the TAC overview, the starting of new lines goes wrong sometimes. A new line should always start in the same way a line in the editor field starts, with the starting of a new change group. Even when the last item of the previous linev needs a new line, the next change group must be on a new line in the overview.. A new line must start in the TAC overview with the start of a new group in the TAF, with

* FM
* BECMG
* TEMPO
* PROB30
* PROB40
* PROB30 TEMPO
* PROB40 TEMPO


Possibly a FE fix is required after BE update as well. If necessary, create a follow up ticket

Story points: 3.0
BE: Research & solve presetsBE not working

From the logging we found that the nginx container was not able to communicate with the userinfo endpoint of cognito. This is because the ip adress behind the domain name of cognito changes once in a while. The domain name is not re-resolved by nginx.

Possible fix in https://gitlab.com/opengeoweb/backend-services/presets-backend/-/merge_requests/54

This resolves the new IP to the domain name on regular basis.

This is deployed in tst for testing.

Story points: 3.0