Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Drop the support of Circle geometry in SQL interface #245
Circle object is not a standard type in common geospatial data format. In GeoSpark, it is mainly used to help distance join. The radius of the circles serve as the buffer.
This actually leads to lots of confusion when GeoSpark users want to convert it back to the normal geometry. Will use ST_Buffer or ST_DWithin to solve this issue in the next release.
GeoSpark version = All till 1.1.3
Apache Spark version = all
JRE version = all
API type = SQL in Scala and Java
ST_Circle shouldn't be used in 1.1.3. This may lead to wrong results. CircleRDD in RDD API should be only used for distance join. In order to do a distance join in SQL API, use this instead http://datasystemslab.github.io/GeoSpark/api/sql/GeoSparkSQL-Optimizer/#distance-join…
------------------------------------ Jia Yu, Ph.D. Student in Computer Science Arizona State University <http://www.asu.edu/> Reach me via Jia Yu's Homepage <http://www.public.asu.edu/~jiayu2/> | GitHub Repositories <https://github.com/jiayuasu>
On Sun, Jan 27, 2019 at 5:17 AM Pedro Henrique Mano Fernandes < ***@***.***> wrote: @jiayuasu <https://github.com/jiayuasu>, is it safe, tough, to use Circle, CirceRDD and ST_Circle in 1.1.3? For instance, I'm noticing that, in a join query circle/point, points that fall in the boundary of a circle aren't considered to be intersecting/contained. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#245 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKcRAMdKdi7KTxNhhPtE629seBvbCHs9ks5vHZjvgaJpZM4Uuuia> .
@jiayuasu, looks like distance join isn't considering points that fall in boundary of the circle. However, PostGIS does consider them. Example:
Well, it can be related to the projection PostGIS is doing. I'm using projection EPSG:3035 for Spain.