The actual conversion code in Pywikibot is at https://git.wikimedia.org/blob/pywikibot%2Fcore.git/HEAD/pywikibot%2F__init__.py#L292

Reminded me to file a task to also implement the other way around (https://phabricator.wikimedia.org/T89670)

Converting that to meters is not possible without taking the latitude into account (which is what pywikibot correctly does). Which means, the same precision value (stored in degrees and displayed in meters) will be displayed different on different locations. The precision will even "magically change" when you edit the latitude, but not the precision.

Our GeoCoordinateValue is defined with a precision in degrees, not meters. We may discuss this decision, if necessary. But as long as it's degrees, I think it's better to display degrees and not do possibly confusing conversions.

I suggest to close this as wontfix.

In T89218#1042264, @thiemowmde wrote:

Converting that to meters is not possible without taking the latitude into account (which is what pywikibot correctly does). Which means, the same precision value (stored in degrees and displayed in meters) will be displayed different on different locations. The precision will even "magically change" when you edit the latitude, but not the precision.

Our GeoCoordinateValue is defined with a precision in degrees, not meters. We may discuss this decision, if necessary. But as long as it's degrees, I think it's better to display degrees and not do possibly confusing conversions.

And a precision of ±0.014000802722428° is not confusing? If the interface would say ±0.014000802722428° (about 10 meters), that would be a lot clearer

I suggest to close this as wontfix.

I don't agree with that.

+/-0.014000802722428° is something between 0 and 1555.644746936 meters. How is that helpful?

In T89218#1053382, @thiemowmde wrote:

+/-0.014000802722428° is something between 0 and 1555.644746936 meters. How is that helpful?

I agree not doing the calculation is not useful at all. You should do the calculation based on 50°4'51"N, 18°12'3"E so you know how many meters it is.

The dimension of an object is different than the precision. The horizontal dimensions of the [[en:Middlebury to Her Soldiers (sculpture)]] monument appears to be about 3 m. But if I were the one who had to measure the location, my recreation-grade GPS unit would only be accurate to about a 30 m radius. So precision should be separate from horizontal size, and we should not conflate them. When precision is understood as the uncertainty in measuring latitude and longitude, it makes perfect sense that the uncertainty in the location of the monument is ±0.0001° (about 11 m in the north-south direction or 8 m in the east-west direction). Of course, since there is only one value available for precision, the editor who enters it will have to determine the greatest angular uncertainty, depending on the method for finding the position, and enter it.

Congratulations on the development team for displaying the unit of measure, degrees, for the precision in the user interface.

I have added this to "Lack of geographic shape data type causing trouble" on the data model talk page, since there seems to be disagreement about the conceptual meaning of the precision of a latitude or longitude.