GPS Timestamp

I’m a LabView and SignalExpress novice so I thought I’d try
this forum before trying the LabView forum.
I’m trying to acquire analog data with a GPS time stamp. My application requires that I acquire approximately
10 hours of data at a rate of 500kS/s.
The system is a PXI1000B containing 2X5922 cards and a 6682 card. Due to the long duration of the collect I’d
like to account for any drift in the sample clock.
I can see two options.
1.                  1.
Use a NI-SCOPE Acquire step with a corresponding
step to get a GPS timestamp for each read length of data (I’ve set it to 512000). This might not work as there is no            step for
GPS functions.
2.
         2. Using a SMB cable route the CLK OUT from the
6682 to the CLK IN on the 5922. Choose
CLK IN on NI-SCOPE acquire – Advanced TAB. This seems too simple.
Again I’m a novice so any advice or help is appreciated.
Thanks

Due to the quick response and my faulty memory, I gave you incorrect information. The 6682 10HMz clock is not synchronized to the GPS, which is why the example you reference requires the use of the Trimble Thunderbolt. The 6682 has a temperature stabilized clock (better than the default PXI backplane clock), but it is not used by default and there is no current method in SignalExpress to activate it.
The 6682 will give you GPS accurate timestamps for triggers. You can use this information by simultaneously triggering the 6682 and the 5922s with the same signal (watch out for line length issues) or triggering one with the other (watch out for delay issues). Check out the 6682 manual for details. Unfortunately, there are no native steps for doing this in SignalExpress. You would need to create one or more user steps to set up the 6682, get the trigger data, and replace the timestamp in the 5922 data. Much as I hate to admit it, it would probably be easier to do the whole thing in LabVIEW, if you have it available. SignalExpress does not currently support the 6682.
Once again, my apologies. If you need further assistance, let us know.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Similar Messages

GPS timestamping continously sampled data

Hi all,
I'm working on an application that samples 32 analog and 5 digital signals at a fixed rate of 4 kHz and I'd like to accurately timestamp each sample using a GPS time reference.
The timestamp accuracy should be better than 120 us. The application is written in C/C++ and uses the DAQmx C API.
The hardware I have available is the following:
* PCI-6224 card (A/D with 32 analog channels, lots of digital I/O and 2 timer/counters)
* PCI-6602 card (8 timer/counters and a 80 MHz clock)
* TrueTime XL-AK (model 600-000) GPS time reference, with serial ASCII output, IRIG-B timecode output and PPS (pulse-per-second) output.
Unfortunately my GPS is not equiped with a 1 MHz or 10 MHz reference output. Also the IRIG-B output is not easily useable because it is AM modulated on top of a 1 kHz carrier (therefore not compatible with a digital input and all 32 analog inputs have already been allocated)
I plan to implement this application by doing all timing generation on the PCI-6602 and doing all sampling (analog/digital) on the PCI-6224. A pair of counters is configured to do GPS timestamping as demonstrated in the document in this thread:
http://forums.ni.com/ni/board/message?board.id=250&message.id=8560
By routing the same sample clock and digital edge start trigger to all blocks that sample data (analog or digital), the data from all measurement tasks would be synchronised to each other. This would result in 3 streams of parallel data: timestamp values (second + sub-second count), analog data (32 channels) and digital data (say 32 bits for each sample).
However I suspect that the counter arrangement from the thread mentioned earlier does not produce *buffered* timestamps. This would make it impossible to use it as I just described above. Is this correct?
Does anyone know another solution?
I've been thinking about the following alternatives:
1) Sample the PPS signal at a higher rate to more accurately find out where the first sample in the current second starts. Then the timestamp for each sample can be calculated as Tsample = Tpps + Tfirst_sample + N/F, where Tpps = time (in seconds) of the last PPS pulse, Tfirst_sample = offset of first sample in the current second, N = sample number within the current second, F = sample frequency.
2) Same as above, but using buffered two-signal edge-separation measurement to get the offset between PPS and sample clock at even better accuracy.

Typically, (and sometimes necessarily), a sample clock signal used for counter measurements would be connected to a counter GATE pin. For the specific case of "encoder" measurement on the 6602, the Z-index signal must be physically wired to the counter's default GATE pin, so the sampling clock signal would need to be physically wired to the GATE pin of a different counter. Having wired the sample clock signal to a single GATE pin, both of the 2 counter measurement tasks can programmatically specify that their sampling clocks come from that single pin.
The M-series board offers more flexibility in programmatic PFI signal routing than the 6602. You can pretty much wire to any PFI pin and then programmatically specify which pin to use as Input (SOURCE) and which as Sample Clock (GATE). I still typically adopt the convention of using default pins whenever possible.
The terminology for counters can be a bit confusing. In my opinion, the old traditional NI-DAQ was a little more cryptic at first glance but much more consistent overall. The new DAQmx terminology tries to hide implementation details more, but in the process generates multiple aliases to the same pin assignment, depending on how you're using it.
A quick rundown. A SOURCE edge causes the count register to increment. Under DAQmx, this may be referenced as an "Input" or a "Timebase" terminal, depending on the measurement mode. When counting edges, it's an Input. When measuring period or frequency, it's a Timebase. Whatever it's called, the natural behavior at the counter hardware is to increment a count register on each active edge.
A GATE edge can cause a count value to be stored in the acquisition buffer. Under DAQmx, it may be referenced as a "Sample Clock" source when counting edges. When measuring period or frequency it may be a "Channel" or an "Input terminal." Again, whatever it's called, the behavior at the board level is to store an instantaneous count value into the data acq buffer on each active edge.
[There are exceptions, of course. The GATE pin is also used for "Pause Triggering", and can also be used to reset the count register for position measurement with Z-indexing enabled. And so on.]
-Kevin P.

Accurate timestamping 6608 counter intervals with gps irig-b

We have a 6608 timer/counter that forms the basis of an astronomical photometer. We have TTL signals coming in on five channels, and have an IRIG-B gps clock. After much help from NI, we now have loops that have precisely timed durations (our "integration times"). The problem is our GPS time stamping. While we have a GPS timestamp for each of these "integration times", the actual times of these events (which, if the integration time was 1s should increment a second at a time) wander around by +/-0.75s. We just cannot figure out how to get this timestamp to reflect reality. The loops bang out the (correct) counts every second, but the clock cannot keep up (though it sometimes does for a few integrations in a row). We need someone to associate the exact start of an integration period with an exact clock time (we understand there are harware limitations at the ms level).
cheers,
tom harrison
Solved!
Go to Solution.

Hi, Tom Harrison.
There is a KnowledgeBase article that presents a solution to this exact issue: PXI-6608 Not Recognizing IRIG-B Signals For GPS Time
Things to check:
(1) Make sure your IRIG-B signal is the "DC Level" type.
(2) Make sure your IRIG-B signal is compatible with the PXI-6608.
(3) Make sure to attach the synchronization signal to the synchronization line of the real-time clock.
For more information on GPS-based synchronization with the 6008, read through this KnowledgeBase.
I hope you're having a great day!
Regards,
Sara Lewandroski
Applications Engineer | National Instruments
http://www.ni.com/support

Can I creat timestamp with the help of 6601 in labview?

I need a timestamp less than 1ms. So far as I know, 6601 can measure the time interval at the accurecy of us. Can this help to creat timestamp?

Jimmyjimmy2000,
The simple answer is probably, yes. I think you can timestamp using the 6601.
I know this is my usual "answer" - to ask more questions, but more information is needed to propose a good solution.
Do you need absolute time or relative time accuracy?
By absolute I mean, do you need a tracable timestamp with clearly definable accuracy to GMT or the NIST clock?
Or is is good enough to measure intervals of time accurately?
For instance,
Absolute:
1st datum logged at January 2, 2003 0847.105 hours EST
2nd datum logged at January 2, 2003 0847.107 hours EST
Relative:
1st datum logged at January 2, 2003 0847.105 hours EST
2nd datum logged after an additional 0.002 seconds
Both structures are possible
and useful for different purposes. In the first case the best evidence is needed to fix the time of the event under examination. In the second case the begining of the acquisiton is fixed as absolutely as possible, but subsequent data are acceptable as timed by the clock of the 6601 card.
I noticed example code at ni.com that allows a clock update using the global positioning system by wireless means. This is for PXI-6608.
There are VI that ship with LabVIEW for GPS timestamping (find examples search for: NI-TIO). The measure buffered pulse VI measures the time between 2 digital edges and builds an array of those intervals as they occur.
Also, what will trigger the timstamping event? A digital pulse? Do you need to trigger at a particular voltage level?
Triggering at a set voltage level could be tricky. It might be important which data acquisition card you are using.
For further info search at ni.com:
http://search.ni.com/?col=alldocs&layout=TechResources&ql=a
A
lso, if you can, call NI at (800)433-3488 in the US. Documentation is limited for counter/timer applications. But, the engineers at NI can help you figure out how to get going on the phone.
Mike

PXI-6682 read IEEE-1588 timestamp from 7953R over RTSI bus

Hi,
I am relatively new to LabVIEW
programming, although I have two years of hard experience using LabVIEW
FPGA tools.
So, I
have a PXI-1033 chassis, and I have plugged in an PXI-6682 IEEE-1588
card into slot 2 and a PXI-7953R card into slot 4. (Random selection
for slot 4) What I am trying to do is read the GPS timestamp from the
6682 card via the RTSI lines directly into the 7953R FPGA card.
Unfortunately, I have no idea where to start and what to read, and all
the examples (keywords: RTSI, IEEE-1588) that I find are for how to
read the IEEE-1588 timestamp inside the Host Operating system and
nothing tells me how to do it directly from the FPGA. My goal is to
build a machine that timestamps network packets that are being read by
the FPGA hosted inside the PXI-7953R card.
Can anybody point me in the right direction? I
basically want to learn more about RTSI, where the PXI-6682 outputs its
IEEE-1588 timestamp, and how data is transferred over the RTSI bus from
inside a PXI chassis.
Thanks,
John

Thanks for the response Alejandro,
I have a 7953R FlexRIO board with the Mimas Prevas Dual Gigabit Adapter Module (http://www.prevas.com/ethernet_simulator.html) plugged in. Ethernet packets enter the Mimas Dual Gigabit Adapter and then go directly to the FPGA as raw Ethernet frames.
From what you are telling me it seems like I cannot have a timestamp go from the PXI-6682 to the 7953R via the RTSI lines and to then be appended to the end of the ethernet frame before being retrasmitted out the other port of the Dual Gigabit Adapter. (With proper recalculation of the 32 bit CRC being done inside the FPGA of course)
I will do some more reading of the manuals and will then call NI Support.
Thanks again!

Timestamp/time elapsed for digital pulses

I am using a PCI-6132 to time digital signals. Ideally, I would like to use the NI-DAQmx C++ API to get a timestamp from the 6132 for each edge (essentially, input capture). I'm pretty sure there is a way to configure a task to do this, but I'm not quite sure how. Most of the tasks seem to measure relative times (ie, the time between two pulses, high time, etc). If someone could point me to the functions/configurations that I should look at, I'd be very grateful.
Thanks,
Ruddick

Hi Ruddick,
I found a few examples which might help you along. Both can be found by navigating to the text-based examples provided in your DAQmx installation.
Start>>All Programs>>National Instruments>>NI DAQ>>Text-Based Code Support>>ANSI C Examples
In the folder, navigate to Events>>Signal>>Change Detection>>Read Dig Chan-Change Detection Event.c This program shows you how to create a DAQmx task which reads change detection events. During the callback phase, you can insert the code to get a timestamp.
The other example, starting with "ANSI C Examples", is located in Counter>>Measure GPS Timestamp>>GPS Timestamp.c
These two examples should give you enough to work with to create a task which outputs a timestep at each rising edge when reading channels on the PCI-6132. Please let me know if you are having trouble finding these examples, I'll be happy to attach to another reply.
Best,
Peter Rifken
Applications Engineer
National Instruments
www.ni.com/support
1-866-ASK-MYNI
Peter Rifken - Field Engineer & Business Manager
Boston / North New England & Maine

V8.2.1: generic file i/o error while loading VI's

Hello,
I had a large LV application open and running fine. I closed it, and upon re-opening the top-level VI it gives "Generic File I/O Error" on several sub-VI's (belonging to me, not LV). Opening those sub VI's individually reveals no problem at all, and in any case the whole code base lives in a Subversion repository and I have tried checking out a fresh copy of the whole source code tree and the problem re-appeared. Before Labview displays the "File I/O error" it will hang for several minutes with no disk or CPU activity.
I just tried checking out a fresh copy of the source tree on a separate computer. Now Labview is hanging while loading "<vilib>:\DAQmx\create\channels.llb\DAQmx Create Channel (CI-GPS Timestamp).vi" after having managed to load 920 VI's. On edit: I spoke too soon. It is now duplicating the "Generic File I/O Error" on one of my sub VI's.
If anyone has any clue to this strange behavior please let me know.
Thank you,
-Brian
Message Edited by brian_g on 04-08-2008 11:43 AM
Message Edited by brian_g on 04-08-2008 11:44 AM

What I found was this...
My code calls a bunch of subVI's in another directory. Those subVI's in turn had some unwise paths saved in some of them that loaded other subVI's from a network shared drive instead of the local disk directory.
The network shared drive had been taken off line since the computer was delivered to a customer last Friday. When LV tried to load the VI's from the shared drive, it would hang for about 5 minutes, then give the "Generic File I/O Error" with an "Ok" button to continue. I eventually sat and did this for about 13 VI's, taking most of an hour while waiting for the network reads to timeout.
Once my now-broken application loaded I was able to successfully re-direct the missing VI's to the local disk, resolving the problem.
The "Generic File I/O Error" message could not be less useful in this case and I'm rather irritated by the genericity of the message. Something like "Network read failed" would have immediately illustrated the problem and kept me from wasting a whole lot of time deciphering it.

Edits overwriting jpeg capture time

Sometimes, but not always, when I edit a jpeg (it may be as simple as changing a keyword or rating), Lightroom will clobber the capture time and overwrite it with the current time. After this happens, the original capture time can't be found anywhere in the EXIF data, except in the GPS timestamp (it's always happened to me with iPhone images, but I don't edit any other jpegs regularly). Strangely, those images still sort in the correct spot when sorted by capture time, so the original timestamp must still be in there somewhere.
Has anyone seen this before?

The only way I can think of troubleshooting that is to save the original .jpg before you import it, and then save a copy of the .jpg after the problem occurs. Then we can compare the metadata of the two files to see what might be going wrong.

Timestamp PXI-5152 waveforms in GPS time

Hello,
I am trying to collect waveforms with a PXI-5152 and correlate them with other data which is collected in GPS time. I have a GPS receiver that can output a PPS pulse. The PPS pulse is the only signal that the two systems can share.
NI support recommended the following.
Split my PPS signal and send one copy into a spare channel on the 5152. Prior to my data acquisition, I would collect one waveform of the PPS pulse. The timestamp of this waveform would be used as my offset from the time counter on the 5152 to the GPS time (assuming I could figure out what second it was which I can)
The other PPS pulse would go to a 6682 time sync card. I was told the card could sync to the PPS and output a 10MHz clock to the 5152.
All measurements on the 5152 would then be converted to GPS time using the offset calculated earlier.
The problem I later found is that the 10MHz clock that is output by the 6682 is not disciplined by the PPS pulse. It is freerunning. Therefore, over time, there would be clock drift between the clock on the 5152 and my other data that is collected in GPS time. This is a problem as I must have 2.5usec accuracy on the time of the data collected on the 5152 card in order to be able to correlate it with the other data set.
Now the question is can this design be salvaged.? Is there a way to use the 6682? It would seem that the 6682 should be able to compute number out 10MHz clock cycles between each PPS pulse. For example if it output 10,000,010 clock cycles between PPS, then there would be a 1 micro second drift for that second. If I were able to read this error once per second then I could (in software) compute and update the error each second. This would allow me to esentially eliminate the clock drift over the long term.
If this is not possible then is there another card that can do something similar...I have been looking at the 6608 which may do something like this.
I appreciate any advice that is out there. Thanks!
Paul

Hi Paul,
You're right, the 6682 out of the box cannot discipline CLK10 to one of the supported Time References.
I think you have 2 high-level options. By leveraging a Trimble Thunderbolt's disciplined CLK10, you can create a system that samples synchronous to GPS. See this link for more information: http://zone.ni.com/devzone/cda/tut/p/id/6818
If you instead want to correlate your free-running 5152 samples to GPS, you're dead on with the approach although this would likely need to be supported with new features from NI-Sync. We currently support timestamping a signal directly which for CLK10 would amount to far too much data. I'd e-mail [email protected] to discuss the possibility of this further.
Thanks for the detailed e-mail
-Adam

Syncronizing 4 counters and Timestamping Values to GPS

Hi,
I'm trying to timestamp the Frequency, Pulse Width, and Edge Count of a TTL signal. The signal is the same throughout. I'm using the 6608 timing card. And each measurement is on a different counter. What I'm having difficulties with is timestamping these values to GPS. Do these measurements have to be synchonized?
My current program entails 4 while loops - one for each measurement and another to acquire GPS time. Each loop was created using Daqmx. Attached is what I'm working on.
Thanks.
--cj
Attachments:
ALL COMBINED.vi ‏349 KB

cmiranda,
Are you measuring the same signal with each of these counters? I opened
your VI, but the configuration sub VIs were missing. If this is the
case, you could get away with using a single counter. A semi-period
measurement would output the high and low times, giving you pusle
width, and with a little calculation, frequency as well. Additionally,
since this measurement is taken on every pulse, the size of your output
array (or in this case half the size, because the data comes out high
time, low time, high time... etc.) would give you the number of pulses.
Finally, I noticed you had a signal connection for your GPS on the fron
panel of your VI, PFI 30, but you don't have the gps counter gate
connected to anything. What signal are you connecting there? Whatever
you connect to the gate will cause a timestamp to be generated. If this
is all the same signal, you could connect it to the gate so the
timestamp corresponds to the exact pulse of the signal. You may want to
look at the DAQmx Connect Terminals VI which would allow you to
internally route signals rather than making separate physical
connections.
Additionally, I noticed that in the loops in your VI you were using
auto-indexing. This will actually create a 2 dimensional array rather
than a single array, which is what I assume you want. Try using a shift
register and a Build Array VI instead. Again, if this is the same
signal we are measuring, I would put everything in one large while loop
to simplify the code.
Hope this helps,
Ryan Verret
Product Marketing Engineer
Signal Generators
National Instruments

GPS Tracker app that INCLUDES Timestamps?

I simply need to import GPS tracks into Google Earth that come in with time data so that I can use the Google Earth time slider and animate the track. I can do this with Android using My Tracks. I have attempted to use apps such as Motion X on the iPhone and while they can import a track they do not include any timestamps. Does anyone know of an iPhone app that can do this? I've been looking for something like this for a while and have been getting no where. Any help would be greatly appreciated.

Have you contacted the support resources provided by the developer of the app and asked them about the problem?

RTSI +DSA4472 +TIO6601 +GPS +sample timestamping

I would like to get accurate periodic time stamps of a continuous data
acquisition with a PCI DSA 4472 using a PCI6601 counter card and GPS
gating. The manual of the 4472 (not very explicit like those of the MIO
or TIO series) speaks about bringing the oversampling clock (also the
DDS clock?) over the RTSI bus to synchronize multiple 4472s dacq. How
does one control this software-wise presumably using the RTSIControl.vi
(I am more familiar with the Route Signal.vi for MIO)? Isn't this
hazardous for the 4472 to use this RSTI (5?) clock as a source to a TIO
PCI 6601counter?
Many thanks for any information about how to proceed in Labview.
Gerard
Regards
Gerard D'Ans ([email protected])
Laborelec Rodestraat,125 B-16
30 Linkebeek
tel 32 2 382 0568
fax 32 2 282 0241
ULB SMA ([email protected])
Blvd F D Roosevelt CP165 B-1050 Brussels
Tel 32 2 650 2515
http://www.ulb.ac.be/polytech/laborulb/index.htm

If it not mandatory to use the PCI6601 counter card and the GPS gating, I think it is possbile for you to use "Get Date/Time in Seconds" function in LabVIEW for the time stamping.

Data acquisition with highly accurate GPS time stamping (hh:mm:ss:sss UT)

A research group has developed a data acquisition system dedicated to daily observations of solar phenomena at radio waves using high time resolution (5-100 ms).
First, the analog signal from the antenna (1000-2500 MHz) is sent to a spectrum analyzer (HP8559-A). After that, the analog signal is digitized during 5 minutes in a NI USB-6009 device connected to the PC, before to be stored in a file. By that time, other acquisition data cycle is restarted and so on up to the end of day.
However, we need timestamp (UTC) the solar data at the beginning and end of each sample of 5 milliseconds, during all acquisition process, in order to have the UTC time information of recorded solar events. So, a time resolution of at least 1 ms is required.
A software permit us to read recorded data and visualize corresponding spectra during last 5 minutes. However, we need UTC time information in the format hh:mm:ss.sss UT. Then, UTC millisecond is important for us, but not available yet.
To solve this problem, we are searching for a high accuracy timing GPS receiver (on the order of microseconds or nanoseconds), with at least three significant digits of precision (UT time in milliseconds) and which give us the UTC signal at least each 5 milliseconds or even better (1 ms). However, most GPS receivers only outputs 1 PPS (Pulse Per Second = 1000 millisecond).
Then, we are open to a better addressing on how to solve this problem !!
We know that GPS time synchronization with PXI-6608 can be used to precisely timestamp data acquisition, but we have to solve this problem with a lower cost. Also, we require a PCI interfacing instead of PXI.
Do we have to use a timer card? How do we use a timer, GPS and USB-6009 to timestamp data acquisition? Does the NI PCI-6602 solve the problem?
Obs:
The data acquisition software was developed in C++ Builder to run on a PC (Pentium III 2 GHz) under Windows XP environment. We used the NI-DAQmxBase driver to sample the signal from the NI USB-6009.
We are sure your expertise can help us on this matter.
Regards,

I better explain my problem in the thread How to timestamp continuous analog data acquisition using USB-6009 and GPS timing board?
We are considering to use the PCI-1588 or a GPS timing board (low-profile slot too), but I´m not sure that the USB-6009 can be used to solve the problem.
How to syncronize the data acquisition and timestamps using USB-6009 and PCI-1588 with external GPS?
In other thread I would appreciate any suggestions for GPS timing board and PCI-1588 too.
Regards,
Lilian

How to get the last received notification timestamp when app in background

Hi All,
We are developing the app in windows phone Silverlight 8.1.
We need to show the last received notification time stamp even when the app is in background.
When the app in foreground, I can get the timestamp.
Since we cant write the background task for the Silverlight phone 8.1 app, I don't know how to get the time stamp of the last
notification(toast/livetile/badge) in the app for display.
Can anyone help on this.
Thanks,
Meena

Yes, continuous background execution is not supported but you can use background tasks.
(Continuous background execution in this context refers to the special run state permitted for GPS Navigation apps.)
For information regarding Background Tasks see: Supporting your app with background tasks -
http://msdn.microsoft.com/library/windows/apps/hh977046.aspx
Additional information is available in these topics:
Guidelines for background tasks
PushNotificationTrigger
How to receive raw notifications
Eric Fleck, Windows Store and Windows Phone Developer Support. If you would like to provide feedback or suggestions for future improvements to the Windows Phone SDK please go to http://wpdev.uservoice.com/ where you can post your suggestions and/or cast
your votes for existing suggestions.

Aperture 3 and GPS logs

According to the manual, Aperture 3 can place photos on a map based on camera GPS data, or else manually by clicking on a map.
I have a camera that doesn't support GPS and was hoping I could find a solution where Aperture can add GPS EXIF data based on importing from a GPS log (from a dedicated GPS device) and comparing timestamps.
Do any such plugins exist for Aperture 3?
(BTW, I've read people's iPhone-related solutions, and that is not going to work for me since I will be roaming in places where the iPhone's accuracy will be called into question...not to mention I'd have to remember to snap an iPhone photo at every waypoint along the way.)

1. GPS Track file: I use "GPS Tracker" (free, app store) on my iPhone to store the GPS track logs on instamapper.com (free). Define the trip and download the track file (in .gpx format).
2. I took about 200 pictures over 3 days on my Nikon D100 onto a CF card.
3. I opened Aperture 3 and imported the images into a new project. I clicked on (Places) button. Used the [GPS] drop down and selected "Import GPS track" (this drew the track nicely!). Selected all images. And dragged the selected images to the track. Aperture asked to assign locations based on time. I selected (Assign Locations). None of the images were assigned the correct locations I removed the images from Aperture.
Marc Vose wrote:
Just wondering which program you're using to actually bring the images off the camera in this scenario.
4. I placed the CF card into the usb CF reader and copied the images to a folder using the finder.
5. I installed exiftool (link: http://www.sno.phy.queensu.ca/~phil/exiftool/) and issued the terminal command:
$ exiftool -geotag=/Users/kent/Downloads/Vacation-2010-02-AZ.gpx .
This tagged all the images in the directory using the track file Vacation-2010-02-AZ.gpx
6. I imported the images into Aperture, clicked on the [Places] button. And all the images have been correctly placed.
7. I burn the raw images to dvd before formatting the CF card (send off-site for backup .
The GPS track support still needs some work in Aperture - but is it nice to be able to work with location information on the images.

GPS Timestamp

Similar Messages

Maybe you are looking for