Re: Potential student projects
I think it’s important that the project should start off with some “mechanical” stuff that doesn’t require any design. Coming up to speed on a new code base is challenging. The GIS functions work has that property.
> On Nov 13, 2018, at 11:36 AM, Michael Mior <mmior@xxxxxxxxxx> wrote:
> Good thought. I'll keep that in mind as well. There's probably far more
> projects (and students) than I'll be able to supervise, but hopefully
> Calcite will be able to get some mileage from this.
> Michael Mior
> Le mar. 13 nov. 2018 à 13:04, Julian Hyde <jhyde@xxxxxxxxxx> a écrit :
>> There’s always more work to be done in Geospatial, e.g.
>> https://issues.apache.org/jira/browse/CALCITE-2031 <
>> https://issues.apache.org/jira/browse/CALCITE-2031>. The easy part is to
>> create scalar (row-at-a-time) implementations of spatial functions, but the
>> real fun starts when you transform queries to use materialized views
>> (“indexes”). Until now, everything has been on rectangular grids and
>> space-filling curves (i.e. assuming flat-earth) but indexing using Uber H3
>>  or Google S2 would be challenging and cutting-edge.
>>  https://github.com/uber/h3
>>> On Nov 12, 2018, at 9:02 AM, Michael Mior <mmior@xxxxxxxxxx> wrote:
>>> Hi all,
>>> One of the perks of being a career academic is the availability of
>>> who are looking for interesting projects to work on. I'll be having
>>> students work with me on a regular basis on final projects for their
>>> degree. I'm hoping that some of these can be useful to Calcite.
>>> If anyone can think of a few issues that are technically interesting, not
>>> too large in scope, and don't currently have anyone working on them, I'm
>>> all ears :)
>>> A few issues below I found which could be interesting although some might
>>> be too large in scope for someone who's never seen Calcite before.
>>> Michael Mior