Basecamp won't geotag .nef files

If you could send a sample image to [email][email protected][/email] with a mention of this discussion, we will take a look and see why BaseCamp isn't able to geotag it.

Has this been resolved yet? I've just tried geotagging a jpeg created on camera from Nikon nef file and it isn't recognising the files as per the first post.

I just checked our bug database and I did not find anything, so this is most likely still an issue.

Would you mind attaching a gpx file with the track and one sample file from your camera?

BaseCamp currently only supports the JPG and JPEG formats for geo-tagging.

If the pictures from your camera are not in JPG format, you might have to convert them to JPG first.

I have successfully geotagged .jpg files created from Canon CR2 raw files. The jpgs were created via Adobe Camera Raw. Would be convenient if basecamp would recognize the more popular raw formats as well as the .xmp file that Adobe Camera Raw creates and uses.

By the way the bmp files created by the 62s screencapture feature are not recognizable by BaseCamp for geotagging. Had to convert to jpg then edit the metadata to fix the creation date/time in order to tag them. Even better if the GPS would tag the screencapture image automatically.

Any update on this ?

This is a pretty old thread and it doesn't look like anything has changed. The suggestion to convert NEF files to JPG and then geotag the JPGs is just not workable for a serious photographer. I have many NEF files which I edit in Lightroom. I create different output files for different purposes at different times - eg small low res SRGB JPG for the web, high res ProPhotRGB jpgs to show clients, TIFS for printing etc etc. These are all done when I need them. I want to geotag the NEF files which will only need to be done once. The geotag info from the NEFs gets propogated to the generated JPGs, TIFs etc. The EXIF info in the various file formats is pretty much the same so it should not be hard for basecamp to support multiple file formats like just about every over geotagging program around does.

The initial release of Windows Vista - was it January 2007? - incorporated jpg image file management that licensed and supported the appended/prepended Adobe XMP metadata scheme. At that time "raw" image data files, as well as certain other types, required the inclusion of a companion "sidecar" jpg file merely to support the attached Adobe XMP metadata.

Writing to or searching digital camera maker's exif data fields for anything but time hacks may not yet have been directly supported by any major computer operating systems in 2007. Nearly every Photo Editor app had a different key word metadata scheme. Times are a' changing though, and if users want to now trust their original raw image files to automated exif data field editing by BaseCamp, good luck with that.

Edit: In any event, Nuvi track logs are somewhat problematic for coordinate georeferencing, due to being thinned rather heavily by distance, not time, and snapped to the nearest road centerline by default.

You are correct about converting RAW to JPG and tagging those being less than optimum. But, seeing we can't geotag RAW files, its the only way. I too would prefer to tag the RAWs early in the editing process. For now, I just geotag the resulting JPGs before uploading to Flickr.
John

I use, with great success, a wonderful free tool: GeoSetter.

I use, with great success, a wonderful free tool: GeoSetter.

Gonna check it out...thanks!
John

Yes I will too thanks