Hi Jia, 
Thanks for your interest!  I'd be happy to work with you to build out a Drill 
<> Sedona collab.  This sounds really interesting and I think would be a great 
addition to both projects.
With that said, I'm totally unfamiliar with Sedona unfortunately, so I'm not 
sure how much help I can be on that side, but I do know something about 
Drill... :-)
Best,
-- C


> On Feb 2, 2024, at 00:47, Jia Yu <ji...@apache.org> wrote:
> 
> Hi Charles,
> 
> This is Jia Yu from Apache Sedona. I think what you did is fantastic.
> As a project of this Joint codespring, I am proposing to implement a
> comprehensive set of spatial functions to Apache Drill using Apache
> Sedona.
> 
> Apache Sedona has implemented over 130 ST functions and a
> high-performance geometry serializer in pure Java. All these functions
> have been ported to Apache Spark, Apache Flink and Snowflake. They are
> being downloaded over 1.5 million times per month.
> 
> This porting process is fairly simple. Let's take Sedona on Apache
> Flink as an example:
> 
> 1. Call a Sedona java function in a UDF template:
> https://github.com/apache/sedona/blob/master/flink/src/main/java/org/apache/sedona/flink/expressions/Functions.java
> 2. Register this function in a catalog file:
> https://github.com/apache/sedona/blob/master/flink/src/main/java/org/apache/sedona/flink/Catalog.java
> 
> What do you think?
> 
> Thanks,
> Jia
> 
> On Thu, Feb 1, 2024 at 2:44 PM Charles Givre <cgi...@gmail.com> wrote:
>> 
>> Hi Martin,
>> Thanks for sending.  I'd love for Drill to be included in this.  I have a 
>> question for you.  A while ago, I started work on a collection of UDFs for 
>> interacting with H3 Geo Indexes.  I'm not an expert on this but would this 
>> be useful?  Here's the repo: https://github.com/datadistillr/drill-h3-udf   
>> If someone would like to collaborate to complete this and get it integrated, 
>> I'm all for that.
>> Best,
>> -- C
>> 
>> 
>> 
>>> On Jan 31, 2024, at 10:20, Martin Desruisseaux 
>>> <martin.desruisse...@geomatys.com> wrote:
>>> 
>>> Hello all
>>> 
>>> The Open Geospatial Consortium (OGC), The Apache Software Foundation (ASF) 
>>> and The Open Source Geospatial Foundation (OSGeo) hold a join code sprint 
>>> on February 26 to 28 [1]. The main goals are to support the development of 
>>> open standards for geospatial information and to support the development of 
>>> free and open source software which implements those standards, as well as 
>>> creating awareness about the standards and software projects. This is the 
>>> fourth year that this joint code sprint is organized, and this year will be 
>>> physically located in Évora (Portugal). The event can also be attended 
>>> on-line. Registration is free [2].
>>> 
>>> Apache SIS, Sedona, Baremaps, Parquet, Drill and Camel projects 
>>> participated in the past. It would be great if participation was possible 
>>> this year too. Some ideas could be:
>>> 
>>> * Experiment the use of Apache SIS in Sedona for referencing and grid
>>>  coverage services (could be a join effort between Sedona and SIS
>>>  developers).
>>> * Any work related to Geoparquet [3] (an incubating OGC standard based
>>>  on Apache Parquet).
>>> * Any work related to Drill GIS functions [4].
>>> * Any work related to Camel Geocoder [5]. For example, exploring the
>>>  pertinence of using the ISO 19112 standard (could be a join effort
>>>  between Camel and GeoAPI developers).
>>> 
>>> If anyone is interested, the wiki page [1] can be edited directly. If 
>>> particular you can add your project in the "Which Apache projects are going 
>>> to participate?" section. If an introduction to a project can be presented 
>>> as a tutorial, it can also be added in the "Mentor streams" section of [1].
>>> 
>>>    Martin
>>> 
>>> [1]https://github.com/opengeospatial/developer-events/wiki/2024-Joint-OGC-%E2%80%93-OSGeo-%E2%80%93-ASF-Code-Sprint
>>> [2]https://developer.ogc.org/sprints/23/
>>> [3]https://geoparquet.org/
>>> [4]https://drill.apache.org/docs/gis-functions/
>>> [5]https://camel.apache.org/components/4.0.x/geocoder-component.html
>> 

Reply via email to