jiayuasu opened a new issue, #3203: URL: https://github.com/apache/sedona/issues/3203
### Problem The default object rendering of `WKBGeography` uses the S2 WKT writer with a fixed precision model. Ordinary stored coordinates are therefore truncated: ```text Stored/ST_AsText: POINT (-122.4194 37.7749) toString/df.show: POINT (-122.4 37.8) ``` This also makes object display disagree with structural accessors backed by the authoritative WKB. ### Root cause `WKBGeography.toString()` and `toEWKT()` delegate to the lazily derived S2 Geography. The base S2 rendering path defaults to `PrecisionModel.FIXED`, and converting WKB coordinates through S2 is unnecessary for text serialization. ### Expected behavior - Render the default `WKBGeography.toString()` directly from its stored WKB/JTS representation. - Render default object EWKT from the same structural representation and preserve the SRID. - Preserve ordinary input coordinates without fixed-precision truncation or an S2 coordinate round trip. - Keep explicitly precision-controlled overloads available for callers that request S2/precision-model formatting. - Add coverage for ordinary points and repeated LineString coordinates. This is pre-existing behavior discovered while reviewing #3195. That pull request improves the SQL `ST_AsText` and `ST_AsEWKT` paths but does not need to own the object-rendering change. -- 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]
