james-willis commented on issue #986: URL: https://github.com/apache/sedona-db/issues/986#issuecomment-5431938658
The CRS half of this landed in #1126 (merged 2026-08-06). `docs/concepts/crs.md` now covers: - the three forms a CRS definition can take (authority code, PROJJSON, WKT) and that SedonaDB preserves whichever form you supply verbatim - column-level vs row-level (item) CRS - the authority-code-first equality rule and what it means in practice - why `RS_Intersects` behaves differently from `ST_Intersects` in this respect - SRID vs CRS, plus an internals/design section It also cross-links the CRS-related SQL reference pages and adds a "Concepts" section to the docs nav. What's still outstanding, and what I'd suggest this issue now tracks: - **The Geography / Edges model** — the planar vs spherical edges interpretation, how it interacts with the geographic params of a CRS, and the errors you get when trying to set a geographic CRS on a non-geographic system. - **A data-type-level reference page** — the "our data types are more like the ArgMatcher variants" point from the description. Probably its own page rather than something folded into the CRS concept page. Happy to retitle this / edit the description to match the narrowed scope if that's preferred. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
