Commons:Deletion requests/Third-party photos hosted on weather.gov 2024-10-24

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
  • Add {{delete|reason=Fill in reason for deletion here!|subpage=Third-party photos hosted on weather.gov 2024-10-24|year=2025|month=January|day=14}} to the description page of each file.
  • Notify the uploader(s) with {{subst:idw||Third-party photos hosted on weather.gov 2024-10-24|plural}} ~~~~
  • Add {{Commons:Deletion requests/Third-party photos hosted on weather.gov 2024-10-24}} at the end of today's log.

Third-party photos hosted on weather.gov 2024-10-24

[edit]

These images were all sourced from webpages of the US National Weather Service but are the work of third-party photographers.

For many years, hosting such images on the Commons was done under the rationale that:

  • a process used for a time by the NWS Sioux City regional office that placed photos taken by the public into the public domain as a term of submisison applied to all third party images across all of weather.gov
  • the wording of the general site disclaimer on weather.gov that says "The information on National Weather Service (NWS) Web pages are in the public domain, unless specifically noted otherwise" means "noted with a formal copyright notice" (and ignoring the wording later in the disclaimer that goes on to say "Third-party information and imagery are used under license by the individual third-party provider. [...] Please contact the third-party provider for information on your rights to further use these data/products.")

An extensive review of this rationale in 2024 revealed that:

  • the NWS has had multiple, conflicting processes for public image submissions over the decades, some running concurrently by different regional offices (examples). Some of these processes made release into the public domain a condition of submission, others did not, and some were ambiguous. In practice, we can almost never link a particular image to any particular submission process.
  • in every one of several dozen cases investigated, individual photographers and third-party organizations had not released their work into the public domain when they submitted it for the NWS to use, and still asserted their rights over their images.(examples) This indicates that either the site general disclaimer is not intended to be interpreted the way that uploaders to the Commons have interpreted it over the years, or that this interpretation is correct, but that NWS employees have applied notices to images so very inconsistently over the years as to render the disclaimer completely unreliable.

These findings were confirmed in an RfC conducted from August to October 2024.

Per COM:ONUS it is the responsibility of the person uploading an image to the Commons or anyone arguing for its retention here to obtain permission of the copyright holder. Nevertheless, to expedite this process (and because throughout this review period, the people arguing most strenuously for retention have been remarkably reticent to actually ask photographers about the copyright status of their images), I have approached every one of the creators I have been able to identify.

Number File Basis of identification Contact VRT ticket Comments
1024-1 File:2014ColumbiaMSEF3.jpg Journalist, uncommon name, lives in the same area where this photo was taken Messaged on social media platform September 12; message seen; no response ticket:2024102310011318
ticket:2024121910001057
Photographer confirms taking the photo, but for the Hattiesburg American newspaper.
1024-2 File:PraderScott Rochelle.jpg Confirmed: Social media comment thread with NWS Chicago found Messaged via social media on September 12; no response ticket:2024102310011569 NWS removed this image from their page after inquiry by User:TornadoLGS
1024-3 File:2015MountHopeTornado.jpg Confirmed: Appears on photographer's X feed the day after the event (with copyright notice, FWIW) Emailed on August 14; no response ticket:2024102410013431
1024-4 File:Weather-related traffic collision on the Kansas Turnpike.JPG Confirmed: County EMA confirms this is their photo and that they own the copyright. Contacted via County website September 5. Director initially indicated willingness to release copyright, then stopped responding when shown the declaration of consent ticket:2024091210003412
1024-5 File:Wall cloud near Abingdon, Illinois June 5, 2010.JPG Hobbyist weather photographer with same uncommon name living close to where this photo was taken Messaged via social media on August 30; no response ticket:2024102410013627
1024-6 File:Dunklin co4.jpg Digital content manager for a TV station with same very uncommon name living close to where this photo was taken. Messaged via social media on August 30; no response ticket:2024102410013681
1024-7 File:Tornado in Kansas May 10, 2010.jpg A couple with the same names living close to where this photo was taken. Messaged via social media on September 7; no response ticket:2024102410013734
1024-8 File:EF2CarpenterWyomingTornado2017.jpg Storm chaser and weather photographer with same uncommon name Messaged via social media on September 13; no response ticket:2024102410014028
1024-9 File:El Reno, OK supercell from above 2013-05-31.jpg Confirmed: photographer confirms that the photo is theirs and that they retain the copyright. Stopped responding September 2 when I asked about their willingness to release under a free license ticket:2024091210003556

We do not have any evidence that any of these images are available under a free license and we cannot host them here. --Rlandmann (talk) 23:32, 24 October 2024 (UTC)[reply]

Update

[edit]

The photographer who took File:2014ColumbiaMSEF3.jpg just got back to me. They said they do not own the rights to the image because they took it as part of their work for the Hattiesburg American newspaper.

Therefore, anyone wanting to keep this image should reach out to that publication or its owner, Gannett, to see if they ever freely licensed the image or would be willing to do so. --Rlandmann (talk) 03:16, 19 December 2024 (UTC)[reply]