Re: [DISCUSS] Graduate Sedona to Top Level Project

2021-12-10 Thread Felix Cheung
Hi!

Highly recommend the community look at and complete the Maturity mode

https://community.apache.org/apache-way/apache-project-maturity-model.html

Also it is a good idea to compute some community stats: number of contributions 
(commits), number of contributors (and growth since incubation), email 
discussions, releases,  number of release managers, affiliations of committers 
/ PPMC members, new committers or PPMC members since incubation etc


From: Paweł Kociński 
Sent: Friday, December 10, 2021 2:12:57 AM
To: Jia Yu 
Cc: Jinxuan Wu ; Mohamed Sarwat ; 
Netanel Malka ; Zongsi Zhang ; 
dev@sedona.apache.org 
Subject: Re: [DISCUSS] Graduate Sedona to Top Level Project

That sounds awesome. Can I help you somehow with the process ?


W dniu pt., 10.12.2021 o 01:56 Jia Yu  napisał(a):

> Dear all,
>
> It has been 16 months since Apache Sedona joined the Apache Incubator in
> July 2020. We have made 4 Apache releases so far. I think it is a good time
> to start the discussion of  graduating Apache Sedona from the incubator to
> become a Top Level Project.
>
> For graduation, to the best of my knowledge, we need to follow the
> graduation guideline [1] and podling status report [2]. After a brief
> evaluation, I think most of the remaining steps are to clear up the
> copyright issues.
>
> Please feel free to chime in if you think there are any blockers.
> Meanwhile, I will start to fix the issues on our way to graduation.
>
> [1] https://incubator.apache.org/guides/graduation.html
> [2] https://incubator.apache.org/projects/sedona.html
>
> Thanks,
> Jia
>


Re: [DISCUSS] Graduate Sedona to Top Level Project

2021-12-10 Thread Paweł Kociński
That sounds awesome. Can I help you somehow with the process ?


W dniu pt., 10.12.2021 o 01:56 Jia Yu  napisał(a):

> Dear all,
>
> It has been 16 months since Apache Sedona joined the Apache Incubator in
> July 2020. We have made 4 Apache releases so far. I think it is a good time
> to start the discussion of  graduating Apache Sedona from the incubator to
> become a Top Level Project.
>
> For graduation, to the best of my knowledge, we need to follow the
> graduation guideline [1] and podling status report [2]. After a brief
> evaluation, I think most of the remaining steps are to clear up the
> copyright issues.
>
> Please feel free to chime in if you think there are any blockers.
> Meanwhile, I will start to fix the issues on our way to graduation.
>
> [1] https://incubator.apache.org/guides/graduation.html
> [2] https://incubator.apache.org/projects/sedona.html
>
> Thanks,
> Jia
>


[jira] [Commented] (SEDONA-52) Create Osm pbf loader for Apache Sedona.

2021-12-10 Thread Netanel Malka (Jira)


[ 
https://issues.apache.org/jira/browse/SEDONA-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456964#comment-17456964
 ] 

Netanel Malka commented on SEDONA-52:
-

[~imbruced] 

Are you working on that?

I found those packages which can help us to implement that:

Python: [https://github.com/HTenkanen/pyrosm/blob/master/pyrosm/pyrosm.py]

Sacla: [https://github.com/simplexspatial/osm4scala]

 

> Create Osm pbf loader for Apache Sedona.
> 
>
> Key: SEDONA-52
> URL: https://issues.apache.org/jira/browse/SEDONA-52
> Project: Apache Sedona
>  Issue Type: New Feature
>Reporter: Paweł Kociński
>Assignee: Paweł Kociński
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Commented] (SEDONA-28) Add WKB serializer in RDD and SQL API and let the user choose the SerDe

2021-12-10 Thread Netanel Malka (Jira)


[ 
https://issues.apache.org/jira/browse/SEDONA-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456960#comment-17456960
 ] 

Netanel Malka commented on SEDONA-28:
-

[~jiayu]  I saw that:

 
{code:java}
Reverts #516
PR 516 for SEDONA-28 requires a more thorough test under the cluster mode. Will 
not include it in Sedona 1.1.0.
{code}
 

This issue is still relevant?

Can we check the bug on a local cluster?

There are any actions we can take to prevent from that happening? (tests on a 
local cluster or something like that)

> Add WKB serializer in RDD and SQL API  and let the user choose the SerDe
> 
>
> Key: SEDONA-28
> URL: https://issues.apache.org/jira/browse/SEDONA-28
> Project: Apache Sedona
>  Issue Type: Task
>Reporter: Netanel Malka
>Assignee: Netanel Malka
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Add WKB serializer as an optional serializer and use the old Serde as the 
> default SerDe for both Core and SQL. The user should only use it if they use 
> geometries that are currently not supported by the old Serde.
> The user should be able to choose the serializer as follows
> .config("spark.serializer", classOf[KryoSerializer].getName) // 
> org.apache.spark.serializer.KryoSerializer
> .config("spark.kryo.registrator", classOf[SedonaKryoRegistrator].getName)
> .config("spark.serializer", classOf[KryoSerializer].getName) // 
> org.apache.spark.serializer.KryoSerializer
> .config("spark.kryo.registrator", classOf[SedonaWKBKryoRegistrator].getName)
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)