[SERVER-27548] The order of Coordinates [longitude, latitude] Created: 30/Dec/16 Updated: 06/Dec/22 Resolved: 30/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Querying |
| Affects Version/s: | 2.6.0, 3.2.0, 3.4.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | efkan turen | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | geoNear, geoWithin, query | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Backwards Compatibility: | Major Change | ||||||||
| Participants: | |||||||||
| Description |
|
MongoDB has awesome geo functions. This is a huge job! And of course there must be a reasonable reason to order coordinates as longitude first. However it seems that the rest of the world use in this order [latitude, longitude]. Because of this issue, I have to convert order in everywhere on my apps when developing. Neither Google Maps (Java, Javascript etc) nor GeoTools nor Yandex Maps doesn't use the order of MongoDB coordinates. (+ I guess iOS Maps too) http://docs.geotools.org/latest/userguide/library/referencing/order.html https://www.google.com.tr/maps/ |
| Comments |
| Comment by David Storch [ 30/Dec/16 ] |
|
Hi efkan, After review by the Query Team, we have decided to close this request as Won't Fix. The immediate reason for closing is that this is an unacceptable major breaking change, which could require substantial updates to application code in order to upgrade. However, it is also arguable that [longitude, latitude] is a more correct order, despite the fact that [latitude, longitude] order is used broadly. This is because [longitude, latitude] might align more naturally with one's expectation of an (x, y) axis ordering. This article has an interesting summary of the issue. Another reason for MongoDB's use of [longitude, latitude] coordinate ordering is that we conform to the GeoJSON standard, which always specifies positions in this way: see http://geojson.org/geojson-spec.html#positions. Let me know if you have any further questions or concerns. Best, |
| Comment by David Storch [ 30/Dec/16 ] |
|
Hi efkan, I'm sending this to the Query Team for review. Best, |