Jia Yu
To be merged after this PR: https://github.com/apache/incubator-sedona/pull/647
@Kimahriman This sounds like a good idea to me! But there are way more functions need to move to this Sedona-common, such as spatial partitioning, serializer, format reader... I believe...
@netanel246 @Imbruced @yitao-li Any opinions?
> > > > > > > > > Doing it piece by piece is probably a good idea but it would be nice to have a clear end goal....
> > > > > > > > > Doing it piece by piece is probably a good idea but it would be nice to have a clear end goal....
@Kimahriman Do you think we should release sedona-common as a separate module or it is automatically packaged in other modules?
@Kimahriman Users were supposed to call Sedona modules individually. They can mix and match different modules. Each module does not have any compile scope dependencies. This is great for Scala/Java...
@Kimahriman Yes, I think it will be good to make Sedona-common as a compile scope dependency to whatever package needs it. So the user no need to include it manually....
@netanel246 @Imbruced @yitao-li Since Sedona 1.0.0, ST_Transform uses lat/lon order, instead of lon/lat order in GeoSpark. So now Sedona behavior is different from what PostGIS does. Currently, who uses lon/lat...
@netanel246 @Imbruced Got it. I will then continue working on this PR.