Kontinuation opened a new pull request, #1828:
URL: https://github.com/apache/sedona/pull/1828

   ## Did you read the Contributor Guide?
   
   - Yes, I have read the [Contributor 
Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and 
[Contributor Development 
Guide](https://sedona.apache.org/latest-snapshot/community/develop/)
   
   ## Is this PR related to a JIRA ticket?
   
   - Yes, the URL of the associated JIRA ticket is 
https://issues.apache.org/jira/browse/SEDONA-711. The PR name follows the 
format `[SEDONA-711] my subject`.
   
   ## What changes were proposed in this PR?
   
   This work is largely based on https://github.com/apache/sedona/pull/1811.
   
   This PR adds a `GeographyUDT` to match the `GeometryUDT`. This matches how 
the types are defined in Iceberg and Parquet, and maps to the concepts of 
`"edges": "spherical"` in GeoParquet and GeoArrow.
   
   The newly added `Geography` type that backs `GeographyUDT` is a simple 
wrapper around JTS Geometry type. This is for illustrating the idea of how we 
support Geography types, and does not reflect how we'll actually implement 
Geography type and spherical computations.
   
   We've also enhanced `InferredExpression` to support function overloading 
with same arity. For instance, we can have the following 2 overloads to support 
both Geometry and Geography:
   
   * `ST_AsEWKB(geometry) -> geometry`
   * `ST_AsEWKB(geography) -> geography`
   
   The rule for resolving overloaded function is pretty simple for now: it 
selects the function requiring minimal amount of type coercions. Please refer 
to `FunctionResolver.resolveFunction` for details.
   
   ## How was this patch tested?
   
   Added new tests.
   
   ## Did this PR include necessary documentation updates?
   
   The support for Geography type is not complete yet, so we don't bother 
updating the documentation for now.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to