Commons:Featured picture candidates/File:Lotus flower (978659).jpg
Jump to navigation
Jump to search
File:Lotus flower (978659).jpg, featured
[edit]Voting period is over. Please don't add any new votes.Voting period ends on 6 Feb 2016 at 10:49:52 (UTC)
Visit the nomination page to add or modify image notes.
- Category: Commons:Featured pictures/Plants
- Info created by Hong Zhang - uploaded by Josve05a - nominated by Josve05a -- Josve05a (talk) 10:49, 28 January 2016 (UTC)
- Support -- Josve05a (talk) 10:49, 28 January 2016 (UTC)
- Support --Hubertl 11:19, 28 January 2016 (UTC)
- Support - Fantastic and iconic! And now you'll see a remark from me that you've never seen before: This is outstanding bokeh; in my opinion, it's exemplary, and the effect of it is to put the iconic lotus flower (and part of the stem) in a kind of mystical, symbolic landscape. Yes, the one lotus flower is very realistic and detailed, but this composition goes beyond realism to create what looks almost like a brushily painted background, which partly because of the more or less dark greens and partly due to its texture, is not assertive (as when I complain of an "aggressively blurred background" that may contain a grainy surface) but is clearly a supporting actor that fades into the distance while still having a presence that helps set a mood. I hope that makes sense, but in any case, I love this artistic creation. -- Ikan Kekek (talk) 11:45, 28 January 2016 (UTC)
- Comment The image does not have any colourspace tag (or profile), which is required by the Commons:Image guidelines. Assuming sRGB, I may be able to insert these tonight if I get a chance (without this metadata, colours do not display properly on some browser/monitor combinations). The guidelines also require proper categorization and the only categories this image is in are maintenance categories that say "unknown flowering plant". Which is as useful EV-wise as "unknown church". Perhaps someone can identify this. The image is nice, though the saturation/contrast is strong. It isn't hard to take a nice picture of a big flower like this (see the Commons:Featured pictures/Plants) so I think we should insist on identification for our "finest" plant photos. -- Colin (talk) 12:54, 28 January 2016 (UTC)
- Oppose I have added the relevant tag/profile (assuming it was sRGB). Without some identification I oppose however. The actual JPG is heavily compressed and the background quite blocky and posterised suggesting over-processing. -- Colin (talk) 21:55, 28 January 2016 (UTC)
- Support -- EVDiam (talk) 14:07, 28 January 2016 (UTC)
- Support --Johann Jaritz (talk) 14:51, 28 January 2016 (UTC)
. Oppose I don't see how this can be featured when the plant is not identified. Without this, the image has no encyclopaedic value.. Charles (talk) 15:23, 28 January 2016 (UTC)- Oppose
Needs an identification. A bit overprocessed (overcontrasted IMO)--Jebulon (talk) 16:18, 28 January 2016 (UTC) - Neutral I will !vote support if there's an ID. Daniel Case (talk) 21:08, 28 January 2016 (UTC)
neutral As Daniel--LivioAndronico (talk) 12:49, 29 January 2016 (UTC)- Comment @Charlesjsharp, Jebulon, Daniel Case, Livioandronico2013, and Colin: Identified. Josve05a (talk) 13:31, 29 January 2016 (UTC)
- Thanks but my JPG quality concerns remain -- it is simply too compressed as a JPG (only 500KB) leading to blocky and posterised background. -- Colin (talk) 15:10, 29 January 2016 (UTC)
- Comment - We talked about this a little on my user talk page, but since this is a blurred background in which clear realism is not envisioned, anyway, why does it matter if it's posterized, as long as it looks good and helps the flower look good? -- Ikan Kekek (talk) 03:45, 30 January 2016 (UTC)
- I agree.--Jebulon (talk) 16:29, 29 January 2016 (UTC)
- And before we even get into that someone needs to make sure it is licensed as CC-0 at the original website, too. Daniel Case (talk) 19:48, 29 January 2016 (UTC)
- License review has been performed, by Revent. Josve05a (talk) 20:09, 29 January 2016 (UTC)
- Thanks but my JPG quality concerns remain -- it is simply too compressed as a JPG (only 500KB) leading to blocky and posterised background. -- Colin (talk) 15:10, 29 January 2016 (UTC)
- Support Ok for me now --LivioAndronico (talk) 14:34, 29 January 2016 (UTC)
- Support 😄 ArionEstar 😜 (talk) 15:40, 29 January 2016 (UTC)
- Comment For the record (having done the license review). The image is available rather widely across the internet. Google images and Tineye both indicate no usages that are at higher resolution, or are older, than that on Pixabay (the source for this image). I see no indication, at all, that this was not released under CC0 by the original author. Its also beautiful. Revent (talk) 20:29, 29 January 2016 (UTC)
- Revent, would you like to vote on whether to support or oppose the picture? -- Ikan Kekek (talk) 03:42, 30 January 2016 (UTC)
- @Ikan Kekek: I wanted to take some time to 'really look at it' before voting, because from as aesthetic point of view I really like the image. There are a couple of issues tho... first, and briefly, looking at the histogram and colocube confirms my impression that parts of the image are completely burned in. The bigger problem I have is that, to be honest, Colin is correct. The bokeh effect here does not appear to be the result of the actual photography, but the result of extensive post-processing. When viewed at 'native resolution' on a large LCD, the posterization is really, really obvious, even on parts of the flower itself. This is a 8 bit jpeg, so has a 'theoretical' color depth of about 16 million colors... the actual file here has about 230k, less than 2% of that.
- Also, looking at an 'error level analysis' confirms my impression.... the flower appears to have been masked out, and processed separately from the rest of the image. I think Colin is slightly mistaken on one point though... the image is saved at 94%, which is not a particularly high level of compression... it's not a small file or posterized from being overcompressed, it's just small because so much detail was removed while processing that it compresses really well... meh. I think I have to Oppose it as a FP, even though I 'like it', because it's a better example of photoshop use than of photography. Sorry. Revent (talk) 18:52, 30 January 2016 (UTC)
- Thanks for that in-depth analysis. However, I have one small thing to point out. The is a nomination for "Featured picture" not "Featured photograph" ;) Josve05a (talk) 19:00, 30 January 2016 (UTC)
- Question What's the difference? Ikan Kekek (talk) 21:40, 30 January 2016 (UTC)
- Nothing really, just that if you think it is a beautiful picture then it is beautiful and should be promoted as such. Then if it may not be the best photography you can take, that's a difference story. Post-processing might have made it look good and it's not in it's natural form, but that doesn't make it a less beautiful picture. Josve05a (talk) 21:42, 30 January 2016 (UTC)
- Good point. I agree with this, and what's more, so does pretty much everyone who votes here, at least in the sense that people ask for things that were actually there to be removed from the photo for aesthetic reasons. Ikan Kekek (talk) 03:00, 31 January 2016 (UTC)
- @Ikan Kekek: Maybe I could have phrased myself better. I think it's a beautiful photograph, when viewed as a thumbnail, and that if the creator had managed the exact same effect 'without' reducing the image quality so much, I would not oppose it. I just think that, when viewed at full size (or, probably, when printed) the flaws created in the processing are distractingly obvious, to the point that it's not really usable unless scaled down significantly. Revent (talk) 06:12, 3 February 2016 (UTC)
- I appreciate the explanation, but I'm not sure I understand. Does this have to do with the bokeh? Because bokeh typically is a big blur, and I find this blur pleasant, which is not usually the case. Ikan Kekek (talk) 06:29, 3 February 2016 (UTC)
- @Ikan Kekek: Only in that the bokeh was not created in the 'photographic process' (i.e., not through the use of settings on the camera), but through postprocessing. That would itself be fine, if well done. However... I temporarily cropped out a small section of the background, specifically so that it would appear at full resolution (and then reverted myself)... it's in the history on the file page. If you look at it closely, it's not just 'blurred', but significantly posterized as a result of the amount of digital processing done in order to create the bokeh effect. To my eye, at least, it's really obvious when looking at the full image instead of a scaled down thumbnail. Revent (talk) 06:57, 3 February 2016 (UTC)
- I appreciate your response, but I would further respond that I don't care if it's posterized, because it's a deliberately blurred background, anyway. If you find the result aesthetically displeasing, then I can completely understand why you'd object to it, regardless of the process used to achieve the result. However, I'm not fully clear on whether that's the issue or whether you are objecting based on the idea that posterization is a technical fault in how the bokeh effect is achieved, rather than based on aesthetic criteria. If that's the case, it wouldn't make any sense to me because a blur is a blur, not (generally speaking) an attempt at a realistic depiction of how our eyes would actually see a scene, and the only basis that makes sense to me to use in judging bokeh is a resort to aesthetic, not technical, criteria. Ikan Kekek (talk) 11:45, 3 February 2016 (UTC)
- @Ikan Kekek: I, indeed, think the image is technically flawed, and to a high enough degree that the flaws are obvious at full resolution. I think it's aesthetically pleasing (it's pretty) but we have far better images with similar content. I don't think it's 'one of the best images on Commons', at all. I think someone took a good photo and broke it so that it only works as a thumbnail. Revent (talk) 15:21, 3 February 2016 (UTC)
- If there are many better images with similar content, that's certainly a valid reason to oppose featuring this. Ikan Kekek (talk) 21:23, 3 February 2016 (UTC)
- @Ikan Kekek: I, indeed, think the image is technically flawed, and to a high enough degree that the flaws are obvious at full resolution. I think it's aesthetically pleasing (it's pretty) but we have far better images with similar content. I don't think it's 'one of the best images on Commons', at all. I think someone took a good photo and broke it so that it only works as a thumbnail. Revent (talk) 15:21, 3 February 2016 (UTC)
- I appreciate your response, but I would further respond that I don't care if it's posterized, because it's a deliberately blurred background, anyway. If you find the result aesthetically displeasing, then I can completely understand why you'd object to it, regardless of the process used to achieve the result. However, I'm not fully clear on whether that's the issue or whether you are objecting based on the idea that posterization is a technical fault in how the bokeh effect is achieved, rather than based on aesthetic criteria. If that's the case, it wouldn't make any sense to me because a blur is a blur, not (generally speaking) an attempt at a realistic depiction of how our eyes would actually see a scene, and the only basis that makes sense to me to use in judging bokeh is a resort to aesthetic, not technical, criteria. Ikan Kekek (talk) 11:45, 3 February 2016 (UTC)
- @Ikan Kekek: Only in that the bokeh was not created in the 'photographic process' (i.e., not through the use of settings on the camera), but through postprocessing. That would itself be fine, if well done. However... I temporarily cropped out a small section of the background, specifically so that it would appear at full resolution (and then reverted myself)... it's in the history on the file page. If you look at it closely, it's not just 'blurred', but significantly posterized as a result of the amount of digital processing done in order to create the bokeh effect. To my eye, at least, it's really obvious when looking at the full image instead of a scaled down thumbnail. Revent (talk) 06:57, 3 February 2016 (UTC)
- I appreciate the explanation, but I'm not sure I understand. Does this have to do with the bokeh? Because bokeh typically is a big blur, and I find this blur pleasant, which is not usually the case. Ikan Kekek (talk) 06:29, 3 February 2016 (UTC)
- @Ikan Kekek: Maybe I could have phrased myself better. I think it's a beautiful photograph, when viewed as a thumbnail, and that if the creator had managed the exact same effect 'without' reducing the image quality so much, I would not oppose it. I just think that, when viewed at full size (or, probably, when printed) the flaws created in the processing are distractingly obvious, to the point that it's not really usable unless scaled down significantly. Revent (talk) 06:12, 3 February 2016 (UTC)
- Good point. I agree with this, and what's more, so does pretty much everyone who votes here, at least in the sense that people ask for things that were actually there to be removed from the photo for aesthetic reasons. Ikan Kekek (talk) 03:00, 31 January 2016 (UTC)
- Nothing really, just that if you think it is a beautiful picture then it is beautiful and should be promoted as such. Then if it may not be the best photography you can take, that's a difference story. Post-processing might have made it look good and it's not in it's natural form, but that doesn't make it a less beautiful picture. Josve05a (talk) 21:42, 30 January 2016 (UTC)
- Question What's the difference? Ikan Kekek (talk) 21:40, 30 January 2016 (UTC)
- Thanks for that in-depth analysis. However, I have one small thing to point out. The is a nomination for "Featured picture" not "Featured photograph" ;) Josve05a (talk) 19:00, 30 January 2016 (UTC)
- Support Kruusamägi (talk) 15:24, 31 January 2016 (UTC)
- Support --Medium69 You wanted talk to me? 13:12, 3 February 2016 (UTC)
Confirmed results:
This image will be added to the FP gallery: Plants