Commons talk:Structured data/Reconciliation

Say KM if distance is big

Don't say

There is a discrepancy of 203511 meters between the above coordinates and the ones stored at...

Instead say

There is a discrepancy of 204 kilometers between the above coordinates and the ones stored at...

Jidanni (talk) 05:38, 27 October 2020 (UTC)

The picture has been taken on the Koenigstrasse in the city of Schleswig in Germany. I have set in the correct coordinates. --Kommentator1989 (talk) 22:12, 29 November 2020 (UTC)

How to make the warning go away after adding a Location template?

How to fix:
Replace the faulty set of coordinates

Yes the camera wasn't warmed up, so the exif is off by a km.

So we put a {{Location|24.18169|120.86617}} into the page. What more must we do to make the warning go away? Edit the EXIF in the image? I would rather not touch the image anymore. Jidanni (talk) 01:41, 6 February 2021 (UTC)

Oh, I see Structured Data was hidden due to my Preferences. Jidanni (talk) 06:19, 22 February 2023 (UTC)

Coordinates of the position cannot be changed

Tracked in Phabricator
Task T313638

The SDC property P1259 can neither be changed nor deleted for the file Bardowick Mühlenstraße 38 003 2020 01 21.jpg.
F. Riedelio • (talk) • ✉ 12:04, 9 September 2021 (UTC)

The same happened to me with several files. After I hit the red garbage icon or "remove all", there was no way to save the change, although I did try repeatedly. Bizzarely, the solution was to change my language setting, either from English to German or vice versa. Only after this, there was a functioning "publish changes"-button available. --Sitacuisses (talk) 01:22, 23 May 2022 (UTC)

Same here. Could not correct coordinates for File:GOC Dunstable Downs 001 Chilterns Gateway Centre (24629034732).jpg, looked for a solution, found this page, changed language to German, could remove the old coordinates, but could not add the new ones, switched back to English and could add the correct ones. Very inconvenient. --Schlosser67 (talk) 07:25, 23 June 2022 (UTC)

Me too. Thanks for the workaround, Schlosser67! Though in my case under new language settings, I could add new coordinates first, then remove the old ones and finally save. It only works for one image at a time though, resulting in me having to change my language settings with every new file to reconcile. --HyperGaruda (talk) 10:55, 2 July 2022 (UTC)

@F. Riedelio, Sitacuisses, Schlosser67, and HyperGaruda: I added a bug report phab:T313638 to Phabricator. You can enter any additional information or clarifications there. Maybe someone will notice this in the next few years and start solving this bug. --ŠJů (talk) 02:07, 23 July 2022 (UTC)

Hope dies last.

The workaround with the language change also works for me. Therefore, I do not consider this error critical. F. Riedelio • talk 14:43, 23 July 2022 (UTC)

@F. Riedelio: The fact that several individuals have discovered a way around the bug, it does not change the fact that for many users the user interface simply does not work and coordinates cannot be removed or corrected in the normal way. It's not deadly, but it understandably results in databases becoming infested with irrelevant data and many users resigning themselves to maintaining coordinates and structured data. Čekal bych, že po zjištění takové chyby UI se někdo plácne do čela a do deseti minut ji opraví. I would expect, after discovering a UI bug like this, someone to slap themselves on the forehead and fix it within ten minutes. --ŠJů (talk) 11:41, 25 July 2022 (UTC)

I see it the same way . F. Riedelio • talk 12:40, 25 July 2022 (UTC)

This problem still persists; I can't change or delete the wrong location in the 'Structured data' tab. Why should I have to anyway? Even if it did work, it's a confounded waste of time having to change location data twice; it more than doubles the time spent editing files where the location has been entered incorrectly (see e.g. File:California sea lion (Zalophus californianus) Catalina on buoy.jpg where the uploader had put a longitude '+' instead of '-' for a western hemisphere location: a very common error). Sorry to get shouty, but WHY DOES CORRECTING THE LOCATION IN THE FILE TEXT NOT AUTO-CORRECT THE ERROR IN THE STRUCTURED DATA??? There should be a little pop-up box with the text "location changed: automatically correct the location in the structured data: Yes, always perform this action, and do not show this note again/Yes, ask me each time any coordinates are changed/No". But there isn't, and it's been a massive nuisance ever since this 'structured data' bilge ever crept into and took over Commons. - MPF (talk) 11:55, 20 September 2022 (UTC)

@ŠJů: - still no resolution to this. Any chance of getting this sorted? - MPF (talk) 23:27, 16 October 2022 (UTC)

@MPF: Unfortunately, this is the state of the Wikimedia projects. Many ill-conceived steps. Many urgent problems remain unresolved for many years. Wikidata and Structured Data could be useful projects, but they are infested with a lot of ballast - unmaintainable data, copied errors that take on a life of their own, etc.

As it appears from the Phabricator report, the bug mentioned above may be dependent on the browser (only in Firefox, but not in Chrome and Edge), and possibly also by the language setting or selected skin. I have personally resigned myself to correcting the coordinates in SD until the bug is fixed. --ŠJů (talk) 23:46, 16 October 2022 (UTC)

@ŠJů: - many thanks! I'm using firefox, so I guess I'm stuck with it :-( I don't know how to change the language setting or skin (and if I did try to change, I'd fear getting stuck in the wrong language!); any suggestions would be appreciated! - MPF (talk) 23:59, 16 October 2022 (UTC)

@ŠJů: - I've found another work-around with firefox that's succesful: open the file in a private window, and the SD coordinates become deletable there :-) MPF (talk) 00:10, 18 October 2022 (UTC)

How to reconcile?

@Jean-Frédéric:  When I took this image yesterday, my camera got the geocoordinates wrong. Today, I changed them manually to reflect the place where I actually took the image. As a result, I'm getting a message that asks me to "reconcile them." How am I supposed to do that? Edit the EXIF data and re-upload the image? Thanks, --Frank Schulenburg (talk) 02:57, 10 March 2022 (UTC)

I generally click "Structured Data" and delete the erroneous location that came from EXIF. Eventually some bot or something fixes it with the location template that I added, and takes away the error flag. Jim.henderson (talk) 02:54, 11 March 2022 (UTC)

Please put this in the instructions. I didn't notice the Structured Data tab while looking for the "Structured data" page. – Reidgreg (talk) 16:06, 10 April 2022 (UTC)

OK, we can make the warning go away. But how to then also get the photo out of Category: Pages with local camera coordinates and mismatching SDC coordinates? Jidanni (talk) 06:21, 22 February 2023 (UTC)

I figure it might be made instantaneous. When the location is wrong (be that by EXIF or other source) usually I change the template by Location Tool, at least when I am not also changing the heading. See the Tools Menu. It ought to change Structured Data also. Or come to think of it, why must the location be given twice, and changed twice when wrong? Jim.henderson (talk) 18:05, 23 February 2023 (UTC)

Remember the preference controlling if you see the Structured Data link

Mention other reasons why one cannot find the Structured Data link.

Tracked in Phabricator
Task T328278

Jidanni (talk) 02:58, 31 January 2023 (UTC)

Warning too low on the page to be noticed

Often an editor walks away never noticing that he has generated this warning.

Yes it might be ugly if put higher up on the page, so maybe instead add some box that flies up the moment this warning is generated. I.e., keep the warning in the page, but also have a box to catch the attention of the person who just triggered it. Jidanni (talk) 06:39, 12 February 2023 (UTC)

Mention if at wits end, try purging

Mention if nothing seems to work to get the warning off the page, try Purge. More powerful than Liquid Drano. Jidanni (talk) 06:51, 22 February 2023 (UTC)