Incorrect OpenMap lat/long conversion?

I just tried setting my lat/long using OpenMap and it gave me some odd values. It set my latitude to 53:60:05 and longitude to 03:02:60. I expected minutes and seconds to be in the range of 0-59 so I wouldn’t have thought that 60 was a valid value? See attached image for the raw data.


Having just checked another way the converted numbers are further wrong than I thought…

My Lat - 53:49:14
My Long - 03:01:40

oh
humm, WD is just pulling out the data supplied by open weather map

I’ve just checked my lat & long using OpenMap and taking the digital lat & long from the GPS on my lightning detector and they both came out the same in conversion.

GPS:
Lat 56.71523
Long 5.22397

Actual:
56° 42’ 54" N
005° 13’ 26" W

Conversion gave the GPS location above as:
056.60.52 (57° 0’ 45"N)
0005.22.39 (5° 22’ 44"W)

As OpenMap & the GPS both agree, somewhere the conversion is putting the location 34.4km too far North, in my case. :wink:

The data provided by OpenMap is correct. It looks like the conversion from decimal degrees to degrees/minutes/seconds isn’t working properly. I’m not sure but it looks like it’s taking the decimal degrees value and using the first two decimal digits as the minutes. If the number of minutes is > 60 then set it to 60. This seems to work for my and Budgie’s latitudes, i.e.

Mine - 53.8205 turns into 53:60
Budgie - 56.7152 turns into 56:60

Incidentally, I wasn’t able to cut and paste the values from the OpenMap site so maybe that’s a change from how it used to work.

I will see what I can do

It’s part of the initial config so it might avoid some confusion for new users if you’re able to find a problem.

My cut & paste from OpenMap worked fine. :wink:

Maybe it’s a browser thing? I was using Firefox.

OK, i have changed the minutes to be a max of 59
and I should do the same for seconds?

Seconds and minutes should both be in the range of 0 (for decimal .00) to 59 (for decimal .99) and ranging between…so 30 minutes/seconds would be 0.50 (decimal). I hope that makes sense!

the problem is its coming from decimal to minutes/seconds
and I have not allowed for the spill over to be carried over
but the user can make those adjustments manually

interestingly openweathermap is blocked for me…no map is loaded

Windows 10’s Edge and IE 11 do not show the map just a pink background, google chrome does show the map so as Brian has just found out the browser does not always work

New Edge does. . .

New Edge - as in Microsoft Chrome?

I’d be inclined to remove the feature. A lot of people just accept what the system tells them and they won’t adjust the info because they don’t know it’s wrong. Given that openmap seems to have some accessibility problems the option might not help too many people anyway!

what are other peoples experiences?

I tried it yesterday and found it ridiculously difficult to navigate anywhere from the default position in US and then zoom in. I did not try the conversion, but I could copy and paste in new Edge (Microsoft Chrome).

my edge does not appear to have been updated yet via windows update