 | SpBotarchives all sections tagged with{{Section resolved|1=~~~~}} after 7 days. |
I wanted to addbased on media(P12346) to link fromFile:Anker A8370 card reader HS04 (cropped).jpg to the uncropped version, but when I try to search for P12346 in the web interface for SDC, it doesn't come up as an option. Anyone know why? –IagoQnsi (talk)21:33, 24 August 2025 (UTC)
Inthis file, a bot addedparticipant in(P1344) "Wiki Loves Monuments 2025", and I addedpoint in time(P585) "2 Jun 2019". (Normally, P585 is added by bot, but I am using{{DTZ}} which the bot does not understand, and this is why I added the date manually to SDC.) Now, I got the warning in the P1344 sector, which says that for 2025 WLM participants eligible range of P585 is September 2025. However, I took the picture in 2019, and this is perfectly fine to use P585 to indicate this. This photo is eligible for WLM2025 since I uploaded it a few days ago. I have a similar issue in at least one more file. Maybe some constraints need to be cleaned up, or possibly I am using a wrong property for the day I took the photograph.Ymblanter (talk)15:45, 22 September 2025 (UTC)
What about new a SDC / Wikidata property to describe a geographical bounding box? I think it would be useful for maps as well as for Digital Orthophotos (DOP) – maybe even allowing a query for media displaying a certain geographical area? Currently, as far as I see, only the{{Map}} template allows to describe the bounding box of the file exactly, using the coordinates of the four rectangle corners as values for thelatitude /longitude parameters. For a DOP with Bounding Box data, see, for example,DOP40 - Stadt Erlangen 32645 5496 (Bayerische Vermessungsverwaltung).tif. There, I've used both{{Information}} and{{Map}} as file description, while using only thelatitude /longitude andwarp_status parameters of{{Map}}. At least, it seems to be possible to set and show the coords of the four corners exactly. But sadly, it seems that the Wikimap Warper can't handle TIFF files – thus, settingwarp_status toskip is required, and there's currently no way to show the DOP as map "layer", or to make use of the bounding box otherwise.Fl.schmitt (talk)19:41, 23 September 2025 (UTC)
defin[ing] the limits of a map, theconstraints allow usage on MediaInfo entities, and there are a handful of existing files using the properties this way, such asFile:Geographic map of Balkan Peninsula.svg.Lucas Werkmeister (talk)20:39, 23 September 2025 (UTC)
.jpg){kind=link}
latitude andlongitude parameters). Thus, choosing a "single" southernmost point is arbitrary. This might be ok for humans, but it's a problem for structured data and applications using those data. The Balkan Peninsula Map is a nice example: It uses only three "points" - thecoordinates of southernmost point(P1333) is missing, thecoordinates of easternmost point(P1334) seems to denote thecoordinates of southernmost point(P1333) as well. A human being is able to cope with this, but i think it's hard to handle such data in a SPARQL query. Additionally, in the case of the Balkan Peninsula Map, it seems thatcoordinates of westernmost point(P1335) andcoordinates of northernmost point(P1332) are both set to the same location. If there's no rule to choose the corners as reference for those properties, using a single point is meaningless - no semantics. For rectangular Maps or DOP, even two corners would be sufficient to describe the bounding box. But doing so will trigger the "item-requires-statement constraint" for the two other corners. So, the concept of combiningcoordinates of northernmost point(P1332) /coordinates of southernmost point(P1333) /coordinates of easternmost point(P1334) /coordinates of westernmost point(P1335) won't work well to describe a geographical bounding box.Fl.schmitt (talk)20:29, 24 September 2025 (UTC)Can someone tell me why we are not allowed to use this as a qualifier to location of creation (P1071)--Trade (talk)12:09, 28 November 2025 (UTC)