12 Aug 2025 Hotfix

Update type: HOTFIX

Issue description:

Panning the map horizontally across the antimeridian (180° longitude) or vertically beyond the poles resulted in the front-end sending non-standard, unbounded coordinate values in the SET_BOUNDING_BOX request to the backend.

• Longitude values could exceed the standard -180 to 180 range (e.g., maxLon: 781.67).
• Vertical panning was not properly constrained near the polar regions.

This behavior could lead to unpredictable data requests and potential rendering issues and API crashes

Solution:

The map panning logic has been updated to correctly handle coordinate normalization and boundary constraints:

1. Longitude Wrapping: Longitude values are now mathematically "wrapped" to always stay within the -180 to 180 degree range. This ensures seamless and correct coordinate reporting when panning continuously around the globe.
2. Latitude Constraints: Vertical map movement is now constrained to prevent the user from panning "over" the poles. This guarantees that latitude values remain within the valid -90 to 90 degree range.