Upgrade to esri-geometry-api version 2.2.0

[tdcmeehan]

Updating the esri-geometry-api to leverage better support for geometry collections.

[tdcmeehan]

Note the addition of point (25, 25) on the output.

[martint]

What’s the motivation for updating? Are there specific bug fixes or performance improvements that would benefit presto?

[tdcmeehan]

@martint I would like to add support for the ST_Union aggregation function (there is already a scalar version of this, see #10921). In order for this to be completely useful as an aggregation function, the Esri library must have robust support for geometry collections (for example, to gracefully handle situations where we union disjoint geometries). Unfortunately, as I understand it, prior to version 2.2.0, there were several outstanding issues relating to collections (see Esri/geometry-api-java#177 and Esri/geometry-api-java#176). By upgrading the library to version 2.2.0, it will unblock the work required to add support for the ST_Union aggregation function, and potentially other operations on geometry collections.

As a quick example of why this may be required, in version 2.1.0 of the library, if I union these two geometries:
LINESTRING (5 5, 7 7) and POLYGON ((2 2, 3 1, 1 1, 2 2))
I receive: POLYGON ((2 2, 1 1, 3 1, 2 2)) (i.e. the LINESTRING is silently dropped). In version 2.2.0, it is GEOMETRYCOLLECTION (LINESTRING (5 5, 7 7), POLYGON ((1 1, 3 1, 2 2, 1 1))).

CC: @mbasmanova

[mbasmanova]

@martint 2.2.0 version adds support for geometry collections to multiple operations: Esri/geometry-api-java#176 . It will allow us to fix #10628

[martint]

Can we add that to the commit message?

[tdcmeehan]

My testing has discovered a corner case: Esri/geometry-api-java#192 It's probably best to wait until that is fixed before we update this dependency.

[mbasmanova]

@tdcmeehan Tim, thanks for reporting this issue. It would be nice to fix it, but in the meantime we can workaround by adding an geometry.isEmpty() check before calling estimateMemorySize(). The latest version of the library didn't include any changes to this API, so it is an existing issue and shouldn't block the upgrade which adds support for geometry collections.