Question. Could someone point out the "Highly visible blurry stitchings"? In fact in the original promotion (less than a year ago) one voter even commented "This panorama is among the best stitching I have ever seen". --jjron (talk) 05:23, 10 December 2007 (UTC)[reply]
You'll note the nominator is an and/or. In other words the creator should be notified wherever possible, but for some images the creator may not be a Wikipedian (in which case you probably can't notify them), or they may have left the project, just as two possibilities - in these cases the nominator definitely should be notified. For some older images you may not reasonably be able to contact either, but that's not the case here. And as de Bivort says, it's really a matter of courtesy in the end anyway. --jjron (talk) 06:40, 11 December 2007 (UTC)[reply]
Thanks for the edit highlighting the stitching errors. I can see some, but not in all the areas you point out. As far as I can tell they only affect the greenery, with a little bit on the rocks in the 'major' area, but most are pretty insignificant. I wouldn't exactly call them highly visible, though a restitch may not hurt. I still lean towards keep. --jjron (talk) 07:27, 12 December 2007 (UTC)[reply]
Comment Ok, for you who has trouble seeing the stitching errors, I've made one version highlighting some problem parts, the major one outlined even more.
Gosh, after looking at your highlighted version, I realized that I must not even know what a stitching error is. I guess I thought it was where images were joined to create a panoramic photograph, but now do you mean places where foliage is slightly blurry? It is windy in the bay. Anyway I voted below to keep until something better is found.Saudade711:39, 13 December 2007 (UTC)[reply]
I don't think they're so much stitching errors, as that some frames in the stitch are slightly more blurry than others. Although it's most visible in the foliage, it's also visible on the rocks too (so it's not just the wind). I had to view 200% to see it. (I haven't voted either way). —Pengo20:58, 13 December 2007 (UTC)[reply]
Keep. Even with the version highlighting the 'highly visible stitching errors' I'm having a hard time seeing them - this is with it at full resolution where I'm only seeing 1/3 of the picture at at time on a 21" monitor. NYTheaterHistorian (talk) 02:09, 12 December 2007 (UTC)[reply]
Keep. I am having trouble seeing any kind of stitching errors even on the 200 inch projector that I was looking at when I saw the delist notice. In fact I cannot see them at all. This picture was also picture of the day a few months ago. It gotten a lot of praise from a lot of people. Miskatonic (talk) 05:15, 12 December 2007 (UTC)[reply]
Keep Until Replacement is Found What's the point of delisting if nothing will take it's place? I'm sure there's some Bay Area Wikipedian who would be so kind as to take a higher resolution photo for us. --Sharkface21705:23, 13 December 2007 (UTC)[reply]
Keep The stitching problems are very small, I couldn't find them until they were highlighted, and still had a hard time seeing them after they were. this is a very good picture. Clegs (talk) 16:36, 13 December 2007 (UTC)[reply]
Delist On account of massive compression errors and low resolution. It is should not be possible for an image this size to be less than a MB. Compression Errors shown in white - jpeg block errors are colored linesTeque5 (talk) 02:37, 15 December 2007 (UTC)[reply]