Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-02 Thread Charles Givre
Hi Bertil, Let me explain a bit about Drill and Calcite. Drill uses Calcite for query planning. Until fairly recently, Drill had a fork of Calcite that had some special features which Drill required. However, about 1-2 versions ago, we were able to get Drill off of the fork an onto "mainstr

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-02 Thread Charles Givre
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 b

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-02 Thread Martin Desruisseaux
Hello Charles Le 2024-02-01 à 23 h 43, Charles Givre a écrit : I'd love for Drill to be included in this. That would be great. You are welcome to add Drill in the wiki page at [1]. A while ago, I started work on a collection of UDFs for interacting with H3 Geo Indexes. I'm not an expert on

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-02 Thread Bertil Chapuis
No offence taken on my side ;-) Do you think sedona-common could broaden its scope to non cluster technologies? In Baremaps, we assumed that a few TBs of vector data can now easily be processed efficiently on a single node with a lot of RAM and NVMe SSDs. Our current implementation uses Postgis

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-02 Thread Jia Yu
Hi all (removing non-geospatial projects from the loop), Just to clarify about the mission of the Apache Sedona project and make sure nobody gets offended by my words before :-) First of all, sedona-common is not a replacement of JTS at all. I also contribute to JTS. Instead, sedona-common is mor

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-01 Thread Bertil Chapuis
Hi Jia, > This is awesome. However, although Flink depends on Calcite, the > SpatialType does not seem to be supported by Flink (based on my test > last year). Not sure if this works for Drill. Please correct me if I'm > wrong. This may be related to the version of calcite used by Flink (1.32) [1

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-01 Thread Jia Yu
Hi Bertil, This is awesome. However, although Flink depends on Calcite, the SpatialType does not seem to be supported by Flink (based on my test last year). Not sure if this works for Drill. Please correct me if I'm wrong. On a side note, why don't we implement all geometric computation logics in

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-01 Thread Bertil Chapuis
Hello Jia and Charles, I'm really interested in this topic as well. Apache Calcite transitionned from ESRI Geometry to JTS, and many ST functions have been implemented there as well [1, 2, 3]. Sharing experiences and code could benefit all projects. I haven’t looked into the details of each pro

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-01 Thread Jia Yu
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-perform

Re: Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-02-01 Thread Charles Givre
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

Joint OGC / ASF / OSGeo codesprint in 3 weeks

2024-01-31 Thread Martin Desruisseaux
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 th