Skip to main content

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

C1 V8.2 and V8.3 geotagging import errors

Comments

3 comments

  • dredlew
    Now that you mention it, I see the same issue. Not that this would be very concerning to me since there is no collective map view in C1 like there is in Aperture. That Google Map link isn't very useful in that sense but it seems like it's a UI display issue of the longitude (latitude is fine) that's completely messed up. The link then uses that same incorrect info to display the wrong location on the map.

    Personally, this is a bug that doesn't really bother me since there's no collective map. Once that's in there, yes, this would be annoying. The location I shot was in NYC, whereas the location shown on the map was Madrid, Spain. lol
    0
  • Paul Steunebrink
    I suggest you both report it in a support case. Upload an image and your findings. Support can have R&D to take a look at it.
    0
  • NNN635158767546269381
    [quote="dredlew" wrote:


    Personally, this is a bug that doesn't really bother me since there's no collective map. Once that's in there, yes, this would be annoying. The location I shot was in NYC, whereas the location shown on the map was Madrid, Spain. lol


    So far it works for me as usual.

    I tagged the photo using PhotoLinker and synced the metaata.

    Anyway, Madrid ad the surrouding are good places!
    0

Post is closed for comments.