Problem in detecting location coordinates
-
Location detection no longer works properly. The attached screenshots shows that the ',' separator in the longitude is not interpreted correctly by the application (the coordinate is truncated). If the ',' is replaced with the '.' symbol, it returns full coordinate and therefore the correct location (and consequently the toponym of the nearest town). This separator problem only affects the longitude part of coordinates.
-
Hi there :)
Coordinates must be provided in WGS84 decimal degrees notation using a '.' as the decimal separator. Using a ',' in the longitude causes truncation and incorrect location detection. The interface expects a comma-separated list of latitude, longitude, optional elevation, and optional location name, but decimal points within coordinates must always be '.'.
Tabs and white spaces are accepted as separators and detected automatically, but the decimal notation must be correct to ensure proper location detection. The issue you described aligns with this expected behavior when the decimal separator is incorrect.
We hope we were able to answer your questions and wish you pleasant weather with meteoblue.
-
Sorry, maybe I didn't explain myself well. The coordinates are automatically populated by the app when you press the location button (the one shaped like an arrow).
Also I should mention the app version: Cirrus Uncinus 3.0.0 - 27015
-
Ok, thanks for the clarification. We will get back to you shortly.
-
Update: our dev team says thanks for spotting this issue :) It will be fixed asap, in the public beta today and in the main app within a few days.
-
Dear Matteo, please check your email regarding a reward for this tip :)
