News for hackers. Stuff that matters.
Re:Serious Bug in MongoDB Geospatial distance calculation by jandrewrogers on Thursday May 19, 2022 @09:27AM (#31434358)
Geospatial is pervasively Lon/Lat and has been the standard for decades across virtually every software system. GeoJSON is in the correct order, same order as every other common industry format for geospatial. There are similar conventions for polygon winding order, whether a polygon is closed or not, etc which new users frequently ignore.

To someone that works with geospatial data, this is like asserting that RGB is the wrong order for specifying color, ignoring that approximately everyone in industry has been using this ordering convention for a very long time.

Re:Serious Bug in MongoDB Geospatial distance calculation by indymike on Thursday May 19, 2022 @10:14AM (#31434919)
It is usually not the end applications that get it backwards, it's usually a library somewhere in the toolchain that bites you where the author wrote code before learning there are conventions for these things.
Re:Serious Bug in MongoDB Geospatial distance calculation by egl2021 on Thursday May 19, 2022 @09:37AM (#31434472)
OpenCV uses BGR.
Re:Serious Bug in MongoDB Geospatial distance calculation by dekhn on Thursday May 19, 2022 @01:38PM (#31437700)
It also uses y first indexing
Re:Serious Bug in MongoDB Geospatial distance calculation by jandrewrogers on Thursday May 19, 2022 @09:48AM (#31434595)
Heh, I did not know that.