RS_ raster predicates: reconsider assuming WGS84 for a missing CRS
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 784
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 58
Description
`RS_Intersects`/`RS_Contains`/`RS_Within` default a missing CRS on either operand to WGS84. Now that the GeoParquet reader attaches CRSes, CRS-less-but-actually-WGS84 values are much rarer, so this default may do more harm than good — a one-sided-CRS error would surface the mismatch instead of silently assuming a frame.
This tracks the Sedona (Spark) side. The SedonaDB side: https://github.com/apache/sedona-db/issues/1075.
Contributor guide
Research direction
Start by tracing the RS_Intersects, RS_Contains, and RS_Within entry points and their missing-CRS handling on the Sedona (Spark) side. Review the linked SedonaDB issue for related context; done means the intended one-sided-CRS behavior is agreed and covered by regression tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- data, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100