Hadn't realized this before but very much realizing this as I write k-means clustering code over geographic data: the convention of saying "latitude and longitude" is backwards from the convention of "x and y". Having to call my library's coordinates `d1` and `d2`…aargh.
Follow
@shriramk it gets really fun when one of the major geospatial library frameworks (GDAL) decides to break compatibility by switching the order in a major release (2 -> 3) without changing the API in any way that would prevent accidental misuse when porting over old code, and also offers an opt-in feature to get the old behavior back.
