User Details
- User Since
- Oct 15 2014, 8:56 PM (524 w, 18 h)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Herzi Pinki [ Global Accounts ]
Wed, Oct 9
Sep 30 2024
Sep 24 2024
Sep 8 2024
Sep 2 2024
Sep 1 2024
Aug 30 2024
Aug 1 2024
the rules for the competition read (https://meta.wikimedia.org/wiki/Wikipedia_Pages_Wanting_Photos_2024): Include the hashtag #WPWP in the edit summary of all articles improved with images.
Jul 20 2024
acc. to @JoKalliauer there seems to be a render problem with
transform="scale( in combination with <text and text-anchor="middle").
Jul 15 2024
related to T358438?
There is a contest going on. For this contest it is crucial infrastructure. Be kind, be responsive.
Jul 5 2024
as far as I can judge, everything is back to normal. Thanks
Jul 4 2024
Jul 2 2024
We are running our annual photo competition WikiDaheim (starting with July, 1st), which is highly based on a working UW.
Jun 18 2024
May 14 2024
Apr 24 2024
Now I logged in to test.wikipedia.org, it does not change the behavior.
I also tried to log out and log in from paws, did not change anything.
thanks for caring - still help needed
pwb.py version:
Feb 14 2024
I will also remove the WMDE related tags here since we're currently not working on this feature, especially when it's about adding new functionality.
Feb 7 2024
Jan 16 2024
I set the max width now to 1024 and it works also when zoom > 100%.
Thanks.
New observations (hint to reproduce the problem):
Jan 15 2024
Jan 3 2024
Nov 13 2023
@dcausse thanks for your investigations. Your query is 8 times faster than mine (optimizing is obviously not always the way to go) and it gives 165 matches instead of my query that still gives 171.
Nov 11 2023
as things are stochastic:
Now the difference between landforms and mountains is in Hanauer Spitze https://www.wikidata.org/wiki/Q21878328 and Brunnkarspitze https://www.wikidata.org/wiki/Q21878293
Nov 5 2023
Nov 2 2023
Mar 24 2023
The Wikidata User Interface, https://www.wikidata.org/wiki/Q117151102:
Mar 20 2023
Jan 5 2023
Dec 5 2022
Nov 3 2022
Oct 29 2022
Sep 21 2022
the solution for this (allow the deletion of false coordinates) is only half way. In principle the bot copied it, the bot shall keep it in sync without user intervention.
Mar 23 2022
Let's consider this to be an epic fail of problem management in Wikidata. This is now open for more than 7 years, and it is about trimming whitespaces. facepalm.
Everybody paralysed? The current proposal is to improve documentation and error messages, needless to say this is NOT the solution but an annoyance.
The UI is apparently not a first class interface to Wikidata.
Sep 20 2021
I have the problem NOW. I was advised in T290438 to ask for reloading the erronous item. You can create your own testcases.
Sep 14 2021
Sep 6 2021
Jul 4 2021
this seems to happen when the jupiter notebook contains output and becomes too large. Then it does not load anymore. Mine had around 66 MByre. You can strip the output before loading using
Jun 22 2021
So then this needs a policy update on commons when to DR redirects. And we need a global cleanup of such wrong redirects to clean the results of media Seacrh
May 26 2021
Dec 8 2020
Dec 2 2020
There are ~130600 redirects with location data in geo_tags (for commons file namespace):
Oct 15 2020
Oct 14 2020
May 13 2020
I suspect that when storing coordinates the precision is applied to the value and values are changed acc. to the given precision. Changing the precision will again do some conversion on the coordinates and store new values. Original values get lost. I take the coordinates from GIS services, that offer decimal notation and degree/minutes/seconds notation as well. I have no idea, which of those values is the primary value and which is a simple conversion (not lossless!). So taking the wrong one is the first step where precision might get lost. The second is storing to WP where values might be converted to and fro. When coordinates are imported to wikidata, again a loss of precision occurs.
May 6 2020
Apr 30 2020
Hi, I just observered a behavior. Possible reactions are:
not reproducable, wontfix (with reason), fixed (the best of all possibilities) (scnr)
clarify, if unclear.
Apr 28 2020
Apr 24 2020
https://www.wikidata.org/w/index.php?title=Q7861551&oldid=1095688967
first coord links to 47° 15′ 28.8″ N, 11° 24′ 38.16″ E in geohack, but is rendered as 47°15'7"N, 11°24'34"E in Wikidata (a difference of 20'' / 4'')
same for the first coord in https://www.wikidata.org/w/index.php?title=Q12343559&diff=1082146732&oldid=896933408&diffmode=source
with precision +/- 0.013101
is rendered as 46°42'19"N, 12°36'59"E in WD
but for geohack this is 46° 42′ 38.52″ N, 12° 37′ 0.12″ E
Apr 21 2020
same for the second coordinate in https://www.wikidata.org/w/index.php?title=Q801607&oldid=1162774540
WD shows ''48°8'2"N, 16°17'13"E'' while
geohack shows 48° 8′ 4.92″ N, 16° 17′ 2.04″ E
Apr 19 2020
Apr 17 2020
Jun 25 2019
the problem occurs on Commons: https://commons.wikimedia.org/wiki/Help:Gadget-ImageAnnotator
The issue is also reported here: https://commons.wikimedia.org/wiki/MediaWiki_talk:Gadget-ImageAnnotator.js#Problem
Jan 15 2019
Jan 12 2019
this is a duplicate of T213341
Jan 8 2019
Jan 3 2019
@Legoktm, can you please help again to push that issue?
Dec 17 2018
Dec 3 2018
Nov 29 2018
Tried with another bundle of files, could not reproduce the faulty behaviour. Thanks for your attention. Sorry.
The file does not exist as I nominated it for speedy deletion. You can see the log entry.
Nov 26 2018
Nov 23 2018
workaround as suggested in https://www.mediawiki.org/wiki/Topic:Up2kw5v8m8q3v477
Currently we have about 1500 articles in the German WP affected by this problem (https://de.wikipedia.org/w/index.php?search=insource%3A%22ICON2%22&title=Spezial%3ASuche&go=Artikel) with usually multiple occurrences of the problem. Any change in such a page will invalidate the cache and later affect all readers. If I do a change (e.g. a typo), I do not re-check all the coordinate links.
Nov 21 2018
Nov 19 2018
Nov 18 2018
@Aklapper, seems to be an easy to fix problem, something like the typical off by 1 (you can hang me of course, if I'm completely wrong)
can you please schedule it to the correct project?