These utils can not be mapping library specific. So feature grid can work with multiple mapping libraries.
For this reason mapstore provides utilities for WKT parsing.
Please use that utilities.

This makes the restriction not be applied for anonymous users. Only for logged, not-admin.
It is a little unconsistent as a restriction.

I think we should at least apply the same restrictedArea to the anonymous users?

Maybe a configuration inside the restrictedAreas that defines who has the restriction can be more generic.

Indeed, we have think avout authenticated users (to works with geOrchestra restricted org area) first and forget anonymous users.

To apply this restriction, we needs to confirm if restricted area is apply in edit mode only or not as explain in global review comment.

Here the tooltipId but the tooltip is not present in translation file.
Moreover the property do not exist for normal bootstrap button. In order to use it you should use TButton (created for feature grid) or Button with tooltip enhancer.
I noticed that bsStyle property anyway is overridden by the TButton.
So in order to have a tooltip here you should:

• Apply the following changes.

• insert a localized string for each translation file (at least mandatory ones, as usual)
• Fix TButton like this (putting bsStyle after the forced one).

+++ b/web/client/components/data/featuregrid/toolbars/TButton.jsx
@@ -18,7 +18,7 @@ const hideStyle = {
 const normalStyle = {};
 const getStyle = (visible) => visible ? normalStyle : hideStyle;
 export const SimpleTButton = forwardRef(({ disabled, id, visible, onClick, glyph, active, className = "square-button-md", ...props }, ref) => {
-    return (<Button ref={ref} {...props} bsStyle={active ? "success" : "primary"} disabled={disabled} id={`fg-${id}`}
+    return (<Button ref={ref} bsStyle={active ? "success" : "primary"} {...props} disabled={disabled} id={`fg-${id}`}
         style={getStyle(visible)}
         className={className}
         onClick={() => !disabled && onClick()}>

Note: I removed "disabled" flag for a better aspect.

Using this approach makes the sync with map not working. While it still makes sense with viewport filter (because the map already shows the features in map), here this makes things a little unconsistent, and it could be practical for the user to see only the allowed rows on the map. What do you think?

A more functional approach is to add / remove the filter to the query object, as well as the other filters, like quick filter, do.

The filters section recently added to the filter may help you to manage it in a easier way.

Basically you can add to the filter a section filters: that can contain and use cql filter to apply some additional logic.
You can identify these filters by id, adding your own property, to manage them (e.g. adding/removing).