Commons:Featured picture candidates/File:Ponte Barca Abril 2019-1a.jpg

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Voting period is over. Please don't add any new votes.Voting period ends on 18 May 2019 at 13:19:07 (UTC)
Visit the nomination page to add or modify image notes.

View of River Lima and bridge.
  • One easy way of getting the exif right when you do a panorama, is to simply take one of the photos in the panorama, make it as large as the panorama in an ordinary post-processing program, add the panorama as a layer and merge. That way you get all the right exif from at least one of the photos. It is usually more right than the strange things the pano-making give you. I usually do so with my panos, example. You could do that and upload the file on top of this. Change a pixel somewhere so the auto-blocking doesn't complain about uploading the "same" file. --Cart (talk) 20:13, 9 May 2019 (UTC)[reply]
  •  Support --BoothSift 22:50, 9 May 2019 (UTC)[reply]
  •  Comment To examine the EXIF data (included any embedded colour profile) of an image on Commons, it is handy to follow the steps at Commons talk:Featured picture candidates/Archive 19#Jeffrey's Image Metadata Viewer where Christian Ferrer has written a little script to add a link to an online tool. If you examine this image then it does actually have an embedded sRGB colour profile. I'm not sure why Cart doesn't see one, and there's only one version of the file. Perhaps you could check again? Alvesgaspar, I wonder what profile you used when exporting your images as files for Hugin to assemble. Did you save them all with sRGB colour profile, or accidentally use another profile such as ProPhoto RGB or Adobe RGB? It is also worth checking that all your source images are set to the same colour temperature and tint -- usually they will not be if your camera is set to auto white balance. If they aren't, pick the average or best and ensure they are all set the same before exporting. For fixing up EXIF, exiftool is the one for the job, though it takes a bit to learn what the right options are. Alvesgaspar, if you view one of your source images (exported as JPG) in a browser and also this image in a browser, do they appear the same? If they do then we can't blame Hugin. Perhaps this is the colour Alvesgaspar saw or desires for the morning photo. It may still be worth experimenting with the RAW files for the tint (for green) or temperature (for blue coldness) to see if you prefer another. -- Colin (talk) 07:28, 10 May 2019 (UTC)[reply]
  • I only looked at the exif where it says 'Uncalibrated'. I didn't think of using the tools mentioned above, but I thought you could sort it out one way or the other. :-) --Cart (talk) 08:24, 10 May 2019 (UTC)[reply]
  • Footnote: I have learned that the EXIF information ‘Uncalibrated’ is rather unreliable. If I save a photo in AdobeRGB colourspace (with Photoshop), the EXIF data also say ‘Uncalibrated’, only further examination reveals that it is indeed AdobeRGB. --Aristeas (talk)
  • Cart, ah I didn't spot the "Color Space" tag. I only noticed that it has an embedded profile. And that is in fact what browsers do -- the "Color Space" EXIF tag is ignored by web browsers. Aristeas, this EXIF tag only has two values: sRGB or uncalibrated. A photo exported in any colour space other than sRGB should set this tag to uncalibrated (and embed the profile). So this makes me a little suspicious that Alvesgaspar's individual photos might have been exported with a colour space other than sRGB, even though the final image claims it is sRGB in the embedded profile. But it also could just be that Hugin lost the tag. I do seem to recall, when I used Hugin in the past, that it could get confused with colour spaces. -- Colin (talk) 09:05, 10 May 2019 (UTC)[reply]
Confirmed results:
Result: 9 support, 5 oppose, 1 neutral → not featured. /Lucas 13:05, 13 May 2019 (UTC)[reply]