|
Hey naden@harana.com thanks for the ticket! I noticed the original blog post and "golang/geo" Github issue were both updated to indicate the issue was related to using incorrect point coordinate order (e.g. (latitude, longitude) vs (longitude, latitude)) and no longer suggests a bug in the Go Driver. That confusion is understandable because the coordinate order is different in various standards and tools (MongoDB uses GeoJSON, which expects order (longitude, latitude)). Considering that, I filed DOCS-15351 that suggests making the expected coordinate order in MongoDB more prominent in the geospatial operations documentation. Please feel free to leave any comments about the proposed documentation improvement on that ticket.
Were you able to resolve your original issue by switching the latitude and longitude values in your code?
Edit: naden@harana.com I just saw your comment about closing this ticket! Thanks for the update, will close.
|