Switch to Longitude-Latitude for coordinates?

In quite a few places I’m looking at APIs that are built for GeoJSON input and output and having to flip coords and reconstruct bounding boxes for Leaflet to read. Changing Leaflet’s APIs to all do things the GeoJSON way would be (wonderful but) a big, breaking change. Having them all autodetect would be error-prone, and having an is_geojson argument to lots of functions would be lame.

Maybe GeoJSON everywhere is something to think about in 1.0.0, and a global flag, L.GEOJSON_API might be a better near-term goal for the [lat, lon] shortcut to be [lon, lat], for toJSON methods to return GeoJSON, and for bounds to be represented and usable as GeoJSON bounds.

[ghybs]

Just for reference, since this issue seems to become the main justification: https://macwright.org/lonlat/

Which is right? Neither. This is an opinion with no right answer. Geographical tradition favors lat, lon. Math and software prefer lon, lat.

[perliedman]

@lukedohner use the builtin GeoJSON layer, it works out of the box with coordinates that follow the GeoJSON spec (lon/lat).

If you really need to flip the axis, there are several ways to go about it, one is to use reproject’s reverse function.