[
https://issues.apache.org/jira/browse/SEDONA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753975#comment-17753975
]
Martin Desruisseaux commented on SEDONA-356:
--------------------------------------------
One more thing: the title of this issue suggests that an axis order change
would be applied by the coordinate operation between two CRS. If a (lon,lat)
axis order is desired, it should be specified in the CRS definition (with the
caution described in above comment). It is very important that the coordinate
operation obey exactly to the CRS definitions, including axis order, directions
and units, because otherwise it will be a source of chaotic behaviour for
years. So:
* Request for (lon,lat) should be done in the CRS definition.
* Coordinate operations should *always* obey *strictly* to CRS definitions.
Never do any axis flip that are not mandated by CRS definitions.
* Modified CRS should not be confused with EPSG definitions.
* Graphical User Interfaces should use EPSG axis order, directions and units.
> Change CRS transformation from lat/lon to lon/lat order
> -------------------------------------------------------
>
> Key: SEDONA-356
> URL: https://issues.apache.org/jira/browse/SEDONA-356
> Project: Apache Sedona
> Issue Type: Task
> Reporter: Jia Yu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This task to make the behavior of ST_Transform be consistent with other
> libraries. With this solved, ST_Transform/CRStransform will follow lon/lat
> order, instead of lat/lon order.
>
> Users no longer need to use flipCoordinates to workaround.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
