You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sedona.apache.org by "MrPowers (via GitHub)" <gi...@apache.org> on 2025/10/02 15:15:31 UTC

[I] epic: st function coverage [sedona-db]

MrPowers opened a new issue, #174:
URL: https://github.com/apache/sedona-db/issues/174

   This document outlines the ST functions implemented in the latest version of SedonaDB.  Feel free to create PRs to add support for more ST functions!
   
   ## Constructor Functions
   
   - [ ] ST_GeomCollFromText
   - [ ] ST_GeomFromEWKB
   - [ ] ST_GeomFromEWKT
   - [ ] ST_GeomFromGML
   - [ ] ST_GeomFromGeoHash
   - [ ] ST_GeomFromGeoJSON
   - [ ] ST_GeomFromKML
   - [ ] ST_GeomFromText (alias for ST_GeomFromWKT)
   - [x] ST_GeomFromWKB
   - [x] ST_GeomFromWKT
   - [ ] ST_GeometryFromText
   - [ ] ST_LineFromText
   - [ ] ST_LineFromWKB
   - [ ] ST_LineStringFromText
   - [ ] ST_LinestringFromWKB
   - [ ] ST_MakeEnvelope
   - [ ] ST_MLineFromText
   - [ ] ST_MPointFromText
   - [ ] ST_MPolyFromText
   - [ ] ST_MakePoint
   - [ ] ST_MakePointM
   - [x] ST_Point
   - [ ] ST_PointFromGeoHash
   - [ ] ST_PointFromText
   - [x] ST_PointZ
   - [x] ST_PointM
   - [x] ST_PointZM
   - [ ] ST_PointFromWKB
   - [ ] ST_PolygonFromEnvelope
   - [ ] ST_PolygonFromText
   
   ## Geometry Functions
   
   - [ ] GeometryType
   - [ ] ST_3DDistance
   - [ ] ST_AddMeasure
   - [ ] ST_AddPoint
   - [ ] ST_Affine
   - [ ] ST_Angle
   - [x] ST_Area
   - [ ] ST_AreaSpheroid
   - [x] ST_AsBinary
   - [ ] ST_AsEWKB
   - [ ] ST_AsEWKT
   - [ ] ST_AsGeoJSON
   - [ ] ST_AsGML
   - [ ] ST_AsHEXEWKB
   - [ ] ST_AsKML
   - [x] ST_AsText
   - [ ] ST_Azimuth
   - [ ] ST_BestSRID
   - [ ] ST_BinaryDistanceBandColumn
   - [ ] ST_Boundary
   - [ ] ST_BoundingDiagonal
   - [x] ST_Buffer
   - [ ] ST_BuildArea
   - [x] ST_Centroid
   - [ ] ST_ClosestPoint
   - [x] ST_Collect
   - [ ] ST_CollectionExtract
   - [ ] ST_ConcaveHull
   - [ ] ST_ConvexHull
   - [ ] ST_CoordDim
   - [ ] ST_CrossesDateLine
   - [ ] ST_DBSCAN
   - [ ] ST_Degrees
   - [ ] ST_DelaunayTriangles
   - [x] ST_Difference
   - [x] ST_Dimension
   - [x] ST_Distance
   - [x] ST_DistanceSphere
   - [x] ST_DistanceSpheroid
   - [ ] ST_Dump
   - [ ] ST_DumpPoints
   - [ ] ST_EndPoint
   - [x] ST_Envelope
   - [ ] ST_Expand
   - [ ] ST_ExteriorRing
   - [x] ST_FlipCoordinates
   - [ ] ST_Force_2D
   - [ ] ST_Force2D
   - [ ] ST_Force3D
   - [ ] ST_Force3DM
   - [ ] ST_Force3DZ
   - [ ] ST_Force4D
   - [ ] ST_ForceCollection
   - [ ] ST_ForcePolygonCCW
   - [ ] ST_ForcePolygonCW
   - [ ] ST_ForceRHR
   - [x] ST_FrechetDistance
   - [ ] ST_GeneratePoints
   - [ ] ST_GeoHash
   - [ ] ST_GeometricMedian
   - [ ] ST_GeometryN
   - [x] ST_GeometryType
   - [ ] ST_GLocal
   - [ ] ST_H3CellDistance
   - [ ] ST_H3CellIDs
   - [ ] ST_H3KRing
   - [ ] ST_H3ToGeom
   - [x] ST_HasM
   - [x] ST_HasZ
   - [x] ST_HausdorffDistance
   - [ ] ST_InteriorRingN
   - [ ] ST_InterpolatePoint
   - [x] ST_Intersection
   - [ ] ST_IsClosed
   - [ ] ST_IsCollection
   - [x] ST_IsEmpty
   - [ ] ST_IsPolygonCCW
   - [ ] ST_IsPolygonCW
   - [ ] ST_IsRing
   - [ ] ST_IsSimple
   - [ ] ST_IsValid
   - [ ] ST_IsValidDetail
   - [ ] ST_IsValidReason
   - [ ] ST_IsValidTrajectory
   - [ ] ST_LabelPoint
   - [x] ST_Length
   - [ ] ST_Length2D
   - [ ] ST_LengthSpheroid
   - [ ] ST_LineFromMultiPoint
   - [ ] ST_LineInterpolatePoint
   - [ ] ST_LineLocatePoint
   - [ ] ST_LineMerge
   - [ ] ST_LineSegments
   - [ ] ST_LineSubstring
   - [ ] ST_LocalOutlierFactor
   - [ ] ST_LocateAlong
   - [ ] ST_LongestLine
   - [x] ST_M
   - [x] ST_MMax
   - [x] ST_MMin
   - [x] ST_MakeLine
   - [ ] ST_MakePolygon
   - [ ] ST_MakeValid
   - [ ] ST_MaximumInscribedCircle
   - [x] ST_MaxDistance
   - [ ] ST_MinimumClearance
   - [ ] ST_MinimumClearanceLine
   - [ ] ST_MinimumBoundingCircle
   - [ ] ST_MinimumBoundingRadius
   - [ ] ST_Multi
   - [ ] ST_NDims
   - [ ] ST_Normalize
   - [ ] ST_NPoints
   - [ ] ST_NRings
   - [ ] ST_NumGeometries
   - [ ] ST_NumInteriorRing
   - [ ] ST_NumInteriorRings
   - [ ] ST_NumPoints
   - [x] ST_Perimeter
   - [ ] ST_Perimeter2D
   - [ ] ST_PointN
   - [ ] ST_PointOnSurface
   - [ ] ST_Points
   - [ ] ST_Polygon
   - [ ] ST_Polygonize
   - [ ] ST_Project
   - [ ] ST_ReducePrecision
   - [ ] ST_RemovePoint
   - [ ] ST_RemoveRepeatedPoints
   - [ ] ST_Reverse
   - [ ] ST_Rotate
   - [ ] ST_RotateX
   - [ ] ST_RotateY
   - [ ] ST_S2CellIDs
   - [ ] ST_S2ToGeom
   - [ ] ST_Scale
   - [ ] ST_ScaleGeom
   - [ ] ST_SetPoint
   - [x] ST_SetSRID
   - [ ] ST_ShiftLongitude
   - [ ] ST_Simplify
   - [ ] ST_SimplifyPolygonHull
   - [ ] ST_SimplifyPreserveTopology
   - [ ] ST_SimplifyVW
   - [ ] ST_Snap
   - [ ] ST_Split
   - [x] ST_SRID
   - [ ] ST_StartPoint
   - [ ] ST_SubDivide
   - [ ] ST_SubDivideExplode
   - [x] ST_SymDifference
   - [x] ST_Transform
   - [ ] ST_Translate
   - [ ] ST_TriangulatePolygon
   - [ ] ST_UnaryUnion
   - [x] ST_Union
   - [ ] ST_VoronoiPolygons
   - [ ] ST_WeightedDistanceBandColumn
   - [x] ST_X
   - [x] ST_XMax
   - [x] ST_XMin
   - [x] ST_Y
   - [x] ST_YMax
   - [x] ST_YMin
   - [x] ST_Z
   - [x] ST_ZMax
   - [x] ST_ZMin
   - [ ] ST_Zmflag
   
   ## Predicate Functions
   
   - [x] ST_Contains
   - [ ] ST_Crosses
   - [x] ST_Disjoint
   - [x] ST_DWithin
   - [x] ST_Equals
   - [x] ST_Intersects
   - [ ] ST_OrderingEquals
   - [ ] ST_Overlaps
   - [ ] ST_Relate
   - [ ] ST_RelateMatch
   - [x] ST_Touches
   - [x] ST_Within
   - [x] ST_Covers
   - [x] ST_CoveredBy
   
   ## Aggregate Functions
   
   - [x] ST_Envelope_Aggr
   - [x] ST_Intersection_Aggr
   - [x] ST_Union_Aggr
   
   ## Advanced Functions
   
   - [x] ST_KNN


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "paleolimbot (via GitHub)" <gi...@apache.org>.
paleolimbot commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3785943476

   Great!
   
   I believe ST_Relate can be implemented with GEOS, which would be the easiest way to do so. See https://github.com/apache/sedona-db/pull/503 for a recent PR as a template to follow (that PR added `ST_LineMerge`, also based on GEOS).
   
   If after that PR you'd like to look into optimizing the function using a different library (e.g., tg or geo), I'm happy to walk you through that process!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "Mehak3010 (via GitHub)" <gi...@apache.org>.
Mehak3010 commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-4288926804

   While going through the ST functions listed here, I’ve been reviewing their behavior across SQL and Python to better understand consistency and edge cases (e.g., NULL handling, boundary conditions).
   
   This is mainly to build a clearer picture for the boolean predicate alignment work I’m exploring. Happy to take a closer look at any areas that might need improvement.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "yutannihilation (via GitHub)" <gi...@apache.org>.
yutannihilation commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3610702756

   > “ST_DistanceSphere”、“ST_DistanceSpheroid”
   
   It seems these functions were just removed in https://github.com/apache/sedona-db/pull/368/files#diff-2803e56a1d053803b52c082ffe2f04513486746037de6d1bb9396118e2eaaf2dL320, so I guess the docs will be eventually updated so.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "paleolimbot (via GitHub)" <gi...@apache.org>.
paleolimbot commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3420496883

   Peter noticed that in the latest PRs...when we get the SQL documentation generated we can have a CI job that checks this. Right now the story regarding SQL documentation is a little fuzzy and I'm fine not requiring it until I fix that so as not to subject new contributors to any fuziness that we haven't worked out yet (e.g., I'm not sure exactly how the generation script is supposed to work or whose job it will be to run it yet).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "Mehak3010 (via GitHub)" <gi...@apache.org>.
Mehak3010 commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3785290178

   Hi, I’m interested in contributing by implementing `ST_Relate` and wanted to clarify the expected scope before starting.
   
   Specifically, I’d like to understand few things:
   
   **1. Which geometry combinations should be supported in the initial version (e.g., Point–Polygon, Polygon–Polygon)?**
   
   **2. Should the function return a full DE-9IM relation matrix string, or do you prefer a simplified/partial implementation for v1?**
   
   **3. Are there existing geometry kernels or utilities in SedonaDB that you recommend reusing for this logic?**
   
   **4. Any preferences around performance optimizations or test coverage for this function?**
   
   I’m planning to start with a minimal, well-tested v1 and iterate based on feedback.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "petern48 (via GitHub)" <gi...@apache.org>.
petern48 commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3404597792

   Hmm, some functions have been marked as completed in this list, and their documentations exist in [sql.md](https://github.com/apache/sedona-db/blob/df8f7205a0a99bd75195933084ae4216781f067c/docs/reference/sql.md), even though we haven't actually implemented them. It's because we have stubs for the functions, and the docs got generated for them (e.g `ST_HausdorffDistance`)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "jiayuasu (via GitHub)" <gi...@apache.org>.
jiayuasu commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3420454307

   One thing I noticed is that the recent ST function PR do not have doc update. I think we should require doc update per function. We do that for Apache Sedona. @petern48 @paleolimbot 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "wangwuhua11 (via GitHub)" <gi...@apache.org>.
wangwuhua11 commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3610383607

   Excuse me, I'm a beginner and I really like SedonaDb. Can I know why the “ST_DistanceSphere”、“ST_DistanceSpheroid” doesn't work?The documentation mentions this function
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "MrPowers (via GitHub)" <gi...@apache.org>.
MrPowers commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3581156852

   I am working on manual updates to the SQL docs for the v0.2 release right now, but I will figure out a better way to automate them after the release.
   
   It would be cool if the docs were executable, so we can easily check that all the functions are running as expected.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "petern48 (via GitHub)" <gi...@apache.org>.
petern48 commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3610459481

   Sorry about that! That's because neither of those functions has actually been implemented yet 😬. As I mentioned above in this comment (https://github.com/apache/sedona-db/issues/174#issuecomment-3404597792), we have a few functions that we implemented as "stub functions" (like placeholders) earlier on. Most of these have actual implementations, but some still do not. When we wrote the initial docs, it seemed to include the stub functions that haven't yet been implemented. Thank you for re-surfacing this problem. I just filed an issue: https://github.com/apache/sedona-db/issues/408
   
   I think it's best that we also delete the unused stub functions. It's very easy to search the codebase for a function (like [this](https://github.com/search?q=repo%3Aapache%2Fsedona-db%20ST_DistanceSphere&type=code), see the stub, and then improperly assume the function has been implemented.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "petern48 (via GitHub)" <gi...@apache.org>.
petern48 commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3785988228

   Looks Dewey, barely beat me to it. I created an issue for ST_Relate here: https://github.com/apache/sedona-db/issues/539. Let's move the conversation there in case this conversation drags out, and also since ST_Relate has multiple versions that might involve multiple PRs. Answered your individual questions there @Mehak3010.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "Mehak3010 (via GitHub)" <gi...@apache.org>.
Mehak3010 commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3817799346

   Thanks for creating the dedicated issue! @petern48 
   
   That makes sense — I’ll continue the discussion and follow the guidance in #539. I’ll start with a minimal GEOS-based v1 implementation and iterate from there as discussed.
   
   Appreciate the clarification!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "paleolimbot (via GitHub)" <gi...@apache.org>.
paleolimbot commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-3581762500

   Thank you!
   
   https://github.com/apache/sedona-db/issues/180 is the issue I created for that but we could take it in a few different directions (I'll add a note there while I'm thinking about it)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] epic: st function coverage [sedona-db]

Posted by "paleolimbot (via GitHub)" <gi...@apache.org>.
paleolimbot commented on issue #174:
URL: https://github.com/apache/sedona-db/issues/174#issuecomment-5167709478

   I went through and updated our progress here and added the pin back (since I think we got a number of contributors through the pin!). We can also split this up more but the one issue is nice to avoid one issue per missing function (which is a lot!)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org