I tried to switch to buffer, but I don't see any improvement. The 2nd feature remains highlighted.

If it is not a strict requirement, I think that when switching the tool from buffer to intersection and viceversa, we could simply reset the full status, including the selection.
In fact the presence of a field with a feature to select depends on the tool, and it is only a case that the 2 tools shares a feature to select as first element.
What do you thing @tdipisa ? I'm not fully aware if it is a requirement or not.

@MV88

I think something similar to this would be nicer and coherent for this tool

or this

Here my review. Some issues found

Tested using http://localhost:8081/#/context/geoprocessing_rev/45727

• As you can see the layers are still unconsistent. Running twice the process, we have 2 groups. The two group seem to have the same ID, because when you try to select one, the second is selected too. This doesn't happen with Buffered layer. I'd suggest to use only one group named "Geoprocessing Outputs" to use as target group for all the layers. What do you think?
  double_layer.webm

• When you close the panel afte the selction, the interaction with the tool is still active.

• Trying the tool I had a crash

This is the log:

Error in epic "zoomToExtentEpic". Original error: TypeError: coordinates must be finite numbers
    at checkCoord (checkSanity.js:14:11)
    at __WEBPACK_DEFAULT_EXPORT__ (checkSanity.js:6:3)
    at Function.transform (transform.js:27:56)
    at Object.reproject (CoordinatesUtils.js:248:158)
    at reprojectBbox (CoordinatesUtils.js:481:42)
    at eval (Map.jsx:276:92)
    at SwitchMapSubscriber.eval [as project] (map.js:206:7)
    at SwitchMapSubscriber._next (switchMap.js:88:27)
    at Subscriber.next (Subscriber.js:89:18)
    at FilterSubscriber._next (filter.js:88:30)
    at Subscriber.next (Subscriber.js:89:18)
    at MapSubscriber._next (map.js:83:26)
    at Subscriber.next (Subscriber.js:89:18)
    at FilterSubscriber._next (filter.js:88:30)
    at Subscriber.next (Subscriber.js:89:18)
    at WithLatestFromSubscriber._next (withLatestFrom.js:113:34)
overrideMethod @ console.js:213
eval @ EpicsUtils.js:28
CatchSubscriber.error @ catch.js:104
Subscriber._error @ Subscriber.js:128
[...]

EpicsUtils.js:31 Uncaught TypeError: coordinates must be finite numbers
    at checkCoord (checkSanity.js:14:11)
    at __WEBPACK_DEFAULT_EXPORT__ (checkSanity.js:6:3)
    at Function.transform (transform.js:27:56)
    at Object.reproject (CoordinatesUtils.js:248:158)
    at reprojectBbox (CoordinatesUtils.js:481:42)
    at eval (Map.jsx:276:92)
    at SwitchMapSubscriber.eval [as project] (map.js:206:7)
    at SwitchMapSubscriber._next (switchMap.js:88:27)
    at Subscriber.next (Subscriber.js:89:18)
    at FilterSubscriber._next (filter.js:88:30)
    at Subscriber.next (Subscriber.js:89:18)
    at MapSubscriber._next (map.js:83:26)
    at Subscriber.next (Subscriber.js:89:18)
    at FilterSubscriber._next (filter.js:88:30)
    at Subscriber.next (Subscriber.js:89:18)
    at WithLatestFromSubscriber._next (withLatestFrom.js:113:34)
checkCoord @ checkSanity.js:14
__WEBPACK_DEFAULT_EXPORT__ @ checkSanity.js:6
transform @ transform.js:27
reproject @ CoordinatesUtils.js:248
reprojectBbox @ CoordinatesUtils.js:481
eval @ Map.jsx:276
[...]

• I see advanced options are not understandable.
  
  This is because you used the descriptions of the process options without using the name. This is conusing. "Indicates" what indicates ?
  
  I suggest to use the name as label. If we want a better description, add a tooltip with the description of the field.

Summarizing the points in the #9367 , here I list them providing the current status. Please correct me if I'm wrong somewhere

1. It seems all times I try to use the Intersection process, the tool returns the same error. This need to be investigated PENDING
   • I understood it is probably due to the process and still to investigate. So this will not be part of the PR. Should we open an issue for that?
2. There is no need to have the validation icon clickable as a button. FIXED.
3. Let's use simply GeoProcessing and Select the process to use FIXED
4. One of the main goal of a tool should be to display the result clearly without letting the user to find it. It is not the case here [...]
   • Both Buffer and intersection layers are appended in TOC and for this reason they are not visible - FIXED now they are on top FIXED
   • Changing the style of the generated layer to yellow-orange. FIXED
   • At the end of the process the map should zoom to the interested area covered by the geometry produced by the process. At the same time the layer should have a good default style to properly highlight it and make it more evident. FIXED the zoom is done, the style changed.
5. Tow consecutive runs of the same process generate an inconsistent behavior in TOC. STILL TO BE PROPERLY FIXED
6. When selecting the layer result of a process, the "zoom to" doesn't appear in TOC toolbar but it should be. FIXED
7. A more coherent tool icon must be created FIXED -- @tdipisa the layer with "i" has been used. Did you sync on this?
8. If you click on the tool icon with the catalog tool opened the tool's panel is not visible. Visibility rules and thees kind of interactions must be better managed WONT DO - This requires a window manager for mapstore
9. Typo to be fixed for the following notification message FIXED
10. As I indicated [...] IN PROGRESS something is done in this PR, something have to be done in a separate issue.

So point 1 and 8 are remaining, but they need to be done separately.
Please also cinfirm me the point about the icon.

When posting an incomplete review fix, it could be a good practice ( sometimes happens also to me to forget) to summarize what is missing, and why, and what has been ackieved to be changed.

Here the issues I noticed.

• If you run a process, click on home, get back in instory and re-open the panel ,the panel contains the old setting. I suppose this is not a desired behavior. I noticed this while trying to replicate the crash.

• I noticed that on panel close I have an error in console

EpicsUtils.js:28 Error in epic "toggleHighlightLayersOnOpenCloseGPTEpic". Original error: TypeError: You provided an invalid object where a stream was expected. You can provide an Observable, Promise, Array, or Iterable.
    at Object.subscribeToResult (subscribeToResult.js:73:27)
    at MergeAllSubscriber._next (mergeAll.js:85:42)
    at Subscriber.next (Subscriber.js:89:18)
    at ArrayObservable._subscribe (ArrayObservable.js:114:28)
    at Observable._trySubscribe (Observable.js:57:25)
    at Observable.subscribe (Observable.js:45:27)
    at MergeAllOperator.call (mergeAll.js:63:23)
    at Observable.subscribe (Observable.js:42:22)
    at Observable._subscribe (Observable.js:113:28)
    at Observable._trySubscribe (Observable.js:57:25)
    at Observable.subscribe (Observable.js:45:27)
    at Object.subscribeToResult (subscribeToResult.js:22:27)
    at SwitchMapSubscriber._innerSub (switchMap.js:101:63)
    at SwitchMapSubscriber._next (switchMap.js:94:14)
    at Subscriber.next (Subscriber.js:89:18)
    at FilterSubscriber._next (filter.js:88:30)

• I still can repliacate he crash, here another video. ( using locally, pointing on dev , this context map : http://localhost:8081/#/context/geoprocessing_rev/45727 )

I noticed that this is caused by the layer bbox.bounds is for some reason:

maxx: -Infinity
maxy: -Infinity
minx: Infinity
miny: Infinity