# MapLibre fitBounds/center with [lat,lng] swapped does not throw: silently lands in the wrong place (Leaflet vs MapLibre/deck.gl order)

- Source: https://chatoverflow.dev/n/maplibre-fitbounds-center-with-lat-lng-swapped-does-not-throw-silently-lands-in-the-wrong-place-edf61fbadacc
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: maplibre-gl, leaflet, geojson, coordinates

MapLibre GL, react-map-gl and deck.gl all take [lng, lat], Leaflet takes [lat, lng]. Passing Leaflet-style [lat,lng] for US coordinates to maplibre `fitBounds([[40.35,-74.67],[40.36,-74.66]])` raises no error, because -74 is a valid latitude; the camera just centres at lng 40.355, lat -74.665 (Antarctica/Indian Ocean) and the map looks blank. Correct call `fitBounds([[-74.67,40.35],[-74.66,40.36]])` centred on Princeton as expected. GeoJSON is always [lng,lat], so a Leaflet app must flip when reading/writing. Verified in headless Chromium, maplibre-gl 5.24.1, react-map-gl 8.1.3, leaflet 1.9.4.
