Saltar al contenido principal

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

GPS

Permanently deleted user
I use a program gps4cam to add GPS info to my images prior to importing them into Capture One Pro. If I open an image with Preview, I can see the GPS data. However, after import, the GPS data does not show up in C1. Any suggestions would be appreciated.
0

Comentarios

4 comentarios

Fecha Votos
  • Permanently deleted user
    Have you tried "Reload Metadata"?
    0
  • Permanently deleted user
    I found a solution to my issue although I don't understand exactly what is happening. I changed Preferences\Image\Auto Sync Sidecar XMP from None to Full Sync. Then I reimported the images. All now have GPS locations. But I would appreciate someone explaining what Sidecar XMP is, what Full Sync does, how it differs from Load and why I would choose "Prefer Embedded XMP over Embedded IPTC" over or in addition to "Prefer Sidecar XMP over Embedded Metadata." Capture One 10 defaults to Auto Sync = none and "Prefer Sidecar XMP."
    0
  • OddS.
    [quote="FredK" wrote:
    ...I would appreciate someone explaining what Sidecar XMP is


    It is all about exchanging information between applications. Welcome to the confusing world of image metadata 😉

    I am traveling and do not have access to C1 nor to my processing notes. Take this post with a pinch of salt, the info may not be accurate.

    There is a lot of information available on image metadata in general. I believe the specifics of C1 may become more clear if you read a little about Exif, IPTC, XMP etc. before diving into the C1 side of it. You may find some useful insight here: https://www.carlseibert.com/xmp-iptciim ... preferred/

    Among the things I believe confuse some metadata explorers are;

    Three different storage locations:
    - Embedded in the image file itself in addition to the graphics (the "image")
    - In a companion "sidecar" file that can be written to without modifying the original source image file.
    - In an application's local storage (a local file or database of some sort)

    - At least three sets of metadata (Exif, IPTC, XMP)
    - Information sometimes duplicated or triplicated... to be present in multiple sets. But not always!
    - Different applications may display data from different "Caption" fields depending on the metadata set preferred by the programmer

    - C1 appears to read (load) embedded metadata at first image file encounter
    - C1 appears to not read (load) embedded metadata more than once, later reads from sidecar
    - C1 does not write embedded metadata as that means modifying the source image file.
    - C1 appears to always write metadata to local storage (database for the catalog or for the session)
    - C1 appears to copy (synchronize, auto or manual) its local database metadata to the image sidecar file

    The exchange of a specific piece of metadata, read about Caption in the link provided above, requires the applications involved to use the same set of metadata stored at the same location. Bluntly: information written as "Title" in a notebook may not transfer well to someone who looks for "Topic" on a wallboard.

    Once you get the hang of the different metadata sets and realize that sets may have overlapping information, even contradicting information, things may become less confusing. You will also be able to see the benefit of setting C1 to prefer data from one set of image data over a different set.
    0
  • Permanently deleted user
    [quote="OddS" wrote:

    It is all about exchanging information between applications. Welcome to the confusing world of image metadata 😉

    Thanks for your detailed reply. I will have to take some time to make sense of it all.
    0

La publicación no admite más comentarios.