I’m shocked this kind of post is written, and there are so many comments, yet no one has mentioned spatial references. Not a single time. When you understand th

I’m shocked this kind of post is written, and there are so many comments, yet no one has mentioned spatial references. Not a single time. When you understand the underlying complexity of spatial references/datums/coordinate systems the deviation in library choices isn’t surprising. Aside: If you are using a modern language (like C#) you can just use parameter labels and avoid this whole mess by being explicit each time. Underscores as separators in numeric literals are also pretty neat if you ever need to hard-code a scale or lat/lon for some reason. Some of the libraries under complaint only support WGS84 (basically what anyone using GPS thinks of when they say lat/lon). If you have never seen a coordinate from anything other than GPS or Google Maps, then it would seem strange that someone would expect coordinates in x,y. Other libraries support a wide variety, including projected (rather than geographic) coordinate systems where x,y is more appropriate (WebMercator, for example). Libraries like Google Maps never expose the underlying xy coordinates, but others will. State plane coordinates, for example of widely-used xy system: https://en.m.wikipedia.org/wiki/State_Plane_Coordinate_System https://en.m.wikipedia.org/wiki/State_Plane_Coordinate_Syste... More info on projected/Cartesian coordinates vs geographic/spherical coordinates: https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/coordinate-systems-difference/ https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping...