[SEDONA-508] Add ST_CrossesDateLine

[prantogg]

Did you read the Contributor Guide?

• Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

• Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-508. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

Introduces a predicate function, ST_CrossesDateLine to determines if a given geometry crosses the International Date Line.

• Checks if the difference in longitude between any pair of consecutive points in the geometry exceeds 180 degrees. If so, returns true, else false.
• For multi-geometries (e.g., MultiPolygon, MultiLineString), this function will return true if any one of the geometries within the multi-geometry crosses the International Date Line.

How was this patch tested?

• Passes new and existing tests

Did this PR include necessary documentation updates?

• Yes, I am adding a new API. I am using the current SNAPSHOT version number in since vX.Y.Z format.

[jiayuasu]

Please put this one in Functions. Predicates are for functions that take two geometries as input and return true/false.

[jiayuasu]

@prantogg Can you address this?

[prantogg]

Done

[jiayuasu]

Is there a reason why use AtomicBoolean? I believe the filter functions will be called in a sequential order?

[prantogg]

The CoordinateSequenceFilter being an anonymous inner class could not modify a local variable outside its filter scope unless its final. AtomicBoolean was a work around because final variable's cannot be modified. I have removed separate handling of GeometryCollection so I can define a private local variable crossesDateLine within the filter.

[jiayuasu]

Why explicitly do this for GeometryCollection? Note that: GeometryCollection can have nested GeometryCollection inside. We should avoid implementing our own logic to iterate GeometryCollection. If we really want to do it, this should be done via a recursive function.

[prantogg]

I initially wanted to make sure Every geometry within the GeometryCollection is handled separately because crossesDateLine should return true if any geometry is crossing the dateline.
You're right, explicit handling for GeometryCollection was not required, CoordinateSequenceFilter is able to handle this well. Have pushed the changes.

[jiayuasu]

Please remove the comments.