[
https://issues.apache.org/jira/browse/SEDONA-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694308#comment-17694308
]
Kristin Cowalcijk commented on SEDONA-244:
------------------------------------------
I'm not familiar with the R binding of Apache Sedona. As far as I can tell,
having a {{GeometryUDT}} column could be fine since it is the user-defined type
to represent geometry in Spark SQL, and it indicates that GeoParquet reader is
dealing with the GeoParquet metadata correctly. So just as Jia said, as long as
it works with other ST functions it could be OK.
> Align R read/write functions with the Sparklyr framework
> --------------------------------------------------------
>
> Key: SEDONA-244
> URL: https://issues.apache.org/jira/browse/SEDONA-244
> Project: Apache Sedona
> Issue Type: Improvement
> Reporter: Gregoire Leleu
> Priority: Major
>
> Apache Sedona in R works as an extension of Sparklyr. Read/write functions
> for Sedona should follow the same overall format than the rest of the
> framework. E.g. :
> * Type of return value (I believe a tbl)
> * Standard arguments: name, path, memory, repartition...
> * Standard behavior: overwrite, default names etc.
> Currently some functions in R sedona return RDDs that need to be registered
> as sdf.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
