User talk:Multichill/Archives/2014/May

Importing blank location maps

Import blank location map as item image ([1]) really does not make any sense. Also adding "imported from xxwiki" as reference makes only a little sense (in this case just consider, if it is really needed). --Jklamo (talk) 07:31, 30 April 2014 (UTC)

Jklamo, I use illustrate wikidata.py. It uses the image from Extension:PageImages. I think this extension doesn't consider the logo at nl:Detroit/Hamtramck Assembly and falls back to the second image in the page. This should prevent any future edits. It was decided a while back that bot should add the source from where the information is imported should be added (sorry no link). My bots comply to that. Multichill (talk) 18:57, 30 April 2014 (UTC)

I am not sure if that script is suitable for bot use without human control. I am importing images using "Wikidata Usefuls" script and cases, when images from articles are not suitable to use for P18 (but may be suitable for another "image property"), are not rare. At least some expection list will be usefull. --Jklamo (talk) 09:50, 2 May 2014 (UTC)

I wouldn't run it on all articles. I only run it on articles which have an infobox with an image set. That's a much smaller subset with a much higher success rate. The only thing I see every once in a while is that the image is too small so the extension skips it to the next image (the blank map in this case). Multichill (talk) 17:47, 2 May 2014 (UTC)

odd error

One of your bot edits is now an error on Wikimedia Foundation (Q180) saying "The value does not comply with the property's definition. The value's data value type "ununserializable" does not match the property's data type's data value type "globecoordinate"." Software bug? John Vandenberg (talk) 09:51, 2 May 2014 (UTC)

Yup, see bugzilla:62105. Multichill (talk) 17:44, 2 May 2014 (UTC)

Why not avoid adding data which the software does not support (yet)? Another one today. John Vandenberg (talk) 03:46, 13 May 2014 (UTC)

I have checked the last 100 edits by the bot, and they all have this error. Please fix this stop the bot, talk with the devs, and come to agreement on whether they are going to support any precision or you have to pick one of their preset precision amounts. John Vandenberg (talk) 23:17, 15 May 2014 (UTC)

I have raised this issue at Wikidata:Project chat#Invalid coordinates. John Vandenberg (talk) 04:16, 16 May 2014 (UTC)

Issue with bot

Hi, I had to block your bot as it was inserting buggy coordinates [2] "The value does not comply with the property's definition. The value's data value type "ununserializable" does not match the property's data type's data value type "globecoordinate".". I thought issues with the coordinates datatype were solved but apparently it's not. As manually added coordinates work, it appears that it's not (or not entirely) an issue with Wikidata's software.

By the way, I reverted your edits in Bliss (Q2368) because it should rather be coordinates of the point of view (P1259) than coordinate location (P625) (the difference may seem like hair-splitting in this case, but having two different properties is necesssary for non-numeric photos). --Zolo (talk) 17:17, 11 May 2014 (UTC)

Oh I see that you had spotted the issue with precision, but it shows up in many items. Can you make sure the values you enter are correct before resuming the bot ? Thanks. --Zolo (talk) 17:21, 11 May 2014 (UTC)

The precision is correct, it's just the Wikibase software that contains a bug, see bugzilla:62105. Don't block if you don't understand what you're doing. Resumed the bot. Multichill (talk) 17:56, 11 May 2014 (UTC)

If display is buggish, maybe it's best to wait until it works. But does a precision of "0.0147" really makes sense ? What does it correspond to ? --Zolo (talk) 21:38, 12 May 2014 (UTC)

Wikipedia uses "dim" for the dimension in meters (more info). Precision is in degrees. The dim in meters gets converted to degrees (code). Multichill (talk) 18:03, 16 May 2014 (UTC)

Coordinate error

https://www.wikidata.org/w/index.php?title=Q15186849&diff=0&oldid=86900378 HTH. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:21, 12 May 2014 (UTC)

Also for companies, it is meaningless to add coordinates directly, as they belong to headquarters, thus needs to be as qualifier for hq.

And also not to add coordinates, when they are at hq already [3]. --Jklamo (talk) 00:20, 13 May 2014 (UTC)

Five days later, still the same problem with the bot: Tandberg Storage (Q7682417). John Vandenberg (talk) 23:21, 15 May 2014 (UTC)

Six days after, still same problem. I am afraid that block request is only option. --Jklamo (talk) 17:37, 16 May 2014 (UTC)

As you can read at Wikidata:Project chat#Invalid coordinates this is a bug in the software that is currently being worked on. The coordinates are not incorrect. Multichill (talk) 17:51, 16 May 2014 (UTC)

I am not reffering to the overprecise coordinates, but to the situation, when your bot is adding coordinates to company item, while these coordinates are already in item as qualifier of Property:P159. --Jklamo (talk) 10:06, 19 May 2014 (UTC)

@Jklamo: Andy's very clear style of communication confused me. bugzilla:65430 was opened by me to prevent this in the future. I added you to the bug. Multichill (talk) 10:28, 30 May 2014 (UTC)

Coordinates of movable objects

Hi, could you do not add P625 property directly to humans or spacecrafts (something else maybe)? In both cases relation between item`s object an coordinates is very unclear for direct P625 usage. Humans can be detected by P31=Q5, spacecrafts by COSPAR ID (P247). — Ivan A. Krestinin (talk) 20:31, 14 May 2014 (UTC)

Adding coordinates to persons seems to be an English Wikipedia fetish. I'll leave the weird edge cases for the humans. This is a one time run. I'll have a look at these cases when it's done. Multichill (talk) 17:57, 16 May 2014 (UTC)

Looks like the number of these edge cases are limited.

Human: http://tools.wmflabs.org/wikidata-todo/autolist.html?q=CLAIM[31:5]%20AND%20CLAIM[625] some make sense, some need to be moved to something like place of burial.

COSPAR ID (P247): http://tools.wmflabs.org/wikidata-todo/autolist.html?q=CLAIM[247]%20AND%20CLAIM[625] might be some geostationary satellites

I worked my way down en:Category:Coordinates not on Wikidata. I'm now creating the missing items. Once that is done, I'll do another pass. I created bugzilla:65430 to prevent the bot from re-adding coordinate location (P625) after it's moved. Multichill (talk) 10:42, 17 May 2014 (UTC)

Articles about spacecrafts contain many different types of coordinates: orbital position (this is not geographical coordinates), landing place of capsule, launch place, crash place and etc. Situation is similar for humans: burial place, death place, home location, major works for architect or sculptor and etc. Direct adding P625 decrease whole data quality only. Some time ago one user ask me to improve Wikidata:Database reports/Constraint violations/P21 report. I am trying to clean up the report from excess violations, but your bot makes this task hard. — Ivan A. Krestinin (talk) 12:19, 17 May 2014 (UTC)

KrBot has been removing coordinates from persons, causing edit wars between KrBot and BotMultichill. 117Avenue (talk) 23:35, 18 May 2014 (UTC)

Oh, I see now that bot is operated by Ivan A. Krestinin. 117Avenue (talk) 23:40, 18 May 2014 (UTC)

That's good! That saves me the manual work :-)

I'm done with en:Category:Coordinates not on Wikidata for now. I'll probably do another pass in the future, but only after bugzilla:65430 has been implemented. That way the bot will just skip these items. Multichill (talk) 15:03, 19 May 2014 (UTC)

@Ivan A. Krestinin: All clear now? I'm getting the hang of killing constraint violations so please ping me if you need a hand. Multichill (talk) 10:25, 30 May 2014 (UTC)

It would be great if you help with clearing Wikidata:Database reports/Constraint violations/P21#"Conflicts with" violations, Wikidata:Database reports/Constraint violations/P21#"Conflicts with" violations, Wikidata:Database reports/Constraint violations/P625#"Conflicts with" violations. — Ivan A. Krestinin (talk) 19:43, 30 May 2014 (UTC)

Hmm, I spy bot job. Correct me if I'm wrong @Ivan A. Krestinin::

• If an item is a company and contains headquarters location (P159) than the coordinate location (P625) should be moved to be a qualifier of headquarters location (P159) (262 items CLAIM[31:783794] AND CLAIM[625] AND CLAIM[159])
• Same goes for human place of burial, but I can't find any of those. Probably all fixed already.

Multichill (talk) 20:50, 30 May 2014 (UTC)

Your are right, coordinate location (P625) for humans and companies must be used as qualifier. The problem is that coordinates in WP article can highlight different points. For example for humans these are death place, burial place, monument place, home place and etc. So full automation is impossible. But some cases can be automated. For example if coordinates are located in "resting_place_coordinates" parameter of en:Template:Infobox person, then its can be added as qualifier to place of burial (P119). — Ivan A. Krestinin (talk) 21:15, 30 May 2014 (UTC)