paleolimbot commented on issue #30: URL: https://github.com/apache/sedona-db/issues/30#issuecomment-3276156038
> I think that we should also be changing 4326 to EPSG:4326 before passing it to proj. Agreed! I'd thought that it was handled here: https://github.com/apache/sedona-db/blob/5633898f591c88b9d1c4db8f292d40cb330bfb0e/rust/sedona-schema/src/crs.rs#L136-L168 ...but it's maybe not making its way all the way through the system (or maybe we're not deserializing a CRS when it's used as input to transform and/or setsrid/crs). The other error I've seen is out-of-bounds coordinates: ```python import sedonadb sd = sedonadb.connect() sd.sql("SELECT ST_Transform(ST_GeomFromText('POINT (1000 1000)'), 'EPSG:4326', 'EPSG:3857')").show() #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> webmerc: Invalid latitude #> SedonaError: Transform error: PROJ coordinate transformation failed with error: Invalid coordinate ``` -- 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]
