Paweł Tokaj
Paweł Tokaj
I agree with @netanel246 we should be consistent with what Postgis does. And definitely we need communicate that clearly with users.
It's a proposition PR Goals: - dbt support examples (thrift and databricks) - package with geospatial tests which can be included in dbt projects - docker images for local examples...
I need to add docs
and update the description of the MR
@radekaadek, thanks for the research 🙇 Are you able to verify if it applies correctly with your changes? cc: @jiayuasu (iirc, you have been workign on the Flink java)
@jiayuasu I haven't but I can take a look Sat/Sun on this one
@radekaadek, sorry, I've been busy with the Apache Sedona book. I've tried to find an obvious solution, but I haven't found one. Can you explain precisely how you are running...
Sedona needs to register the - custom geometry types like Point (org.locationtech.jts.geom.Point), Polygon (org.locationtech.jts.geom.Polygon) - custom index types like Quadtree (org.locationtech.jts.index.quadtree.Quadtree), STRtree (org.locationtech.jts.index.strtree.STRtree) - custom functions
Is it causing Sedona to no longer work on Databricks in newer versions? Now we register functions by the simple name ```scala val functionName = classTag.runtimeClass.getSimpleName ```` We could add...
I guess the use of Sedona's internal catalog class. They resolve function name conflicts by themselves. I think this is functionality we could add, as it doesn't require a lot...