#12146: ArcGIS support for FeatureService

[dsuren1]

Description

This PR adds ArcGIS FeatureService support to MapStore

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Feature

Issue

What is the current behavior?

• ArcGIS support for FeatureService #12146

What is the new behavior?

• ArcGIS Feature Service support has been added for OpenLayers and CesiumJS maps, including Catalog service, Identify tool, Style Editor, and data persistence

{
    "type": "arcgis-feature",
    "url": "https://services2.arcgis.com/pROHh69WvVijk4nR/ArcGIS/rest/services/GSE_DISTRIBUTORI_STANDARD/FeatureServer",
    "title": "Title",
    "visibility": true
}

Example

Cesium

OL

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

FeatureServer URL below can be used for testing:
https://services2.arcgis.com/pROHh69WvVijk4nR/ArcGIS/rest/services/GSE_DISTRIBUTORI_STANDARD/FeatureServer

[anup39]

Hi @dsuren1, I had a question regarding the two functions extentToBoundingBox and extentToBoundingBox4326.

Do we need both of them?

From what I can see, extentToBoundingBox4326 handles reprojection more robustly (including WKT and fallback cases). It might make sense to consolidate to a single implementation to avoid duplication. We could also consider renaming it to extentToBoundingBox if we standardize on this new version considering(replacing) the existing use of extentToBoundingBox.

Let me know your thoughts on this.

Apart from this, everything else looks good to me. Thanks

[dsuren1]

This is intentional. While extentToBoundingBox4326 provides more robust reprojection, the two functions differ in output contract, reprojection logic, and error handling. Keeping them separate helps maintain clarity, whereas combining them may introduce a flag and make the behavior less explicit at the call site

[anup39]

@ElenaGallo Kindly test this new feature on DEV. Thanks