Okay, for that application you are concerned with two aspects of accuracy.
If you use the GPS readings to trigger the camera you need a reasonable degree of accuracy of the distance measurement.
If you are going to geocode the images so they can be matched to specific locations on a map, you also need a reasonable degree of accuracy for the absolute position, at least relative to the accuracy of the calibration of the map(s) you plan to use them with.
Here are some options that spring immediately to mind. (Caveat: this is just thinking out loud with no actual analysis of practicality in your particular case.)
----------------------
Option 1.
Use a video camera so it's running continuously. Make sure that it's a camera that timestamps either the frames or at least the first frame.
Use a GPS to record the track as you drive it.
At the start of a shooting session, sync the time in the camera with the time in the GPS.
Use post-processing to match individual frames with the relevant times in the GPS track log, pull them out as single images and geocode them.
----------------------
Option 2.
Don't do the shooting based on position; do it based on speed. Write a simple application for the laptop to notify your trigger software based on your speed. At any speed it's trivial to compute how much time it takes to travel 5 metres.
Connect the GPS and camera to the laptop. Use the GPS to provide the realtime speed to the camera control program and to capture a track log.
Use post-processing to match images based on their timestamps with the relevant locations in the track log and geocode them.
----------------------
Option 3.
Don't do the shooting based on position; do it based on speed. Write a simple application for the laptop to notify your trigger software based on your speed. At any speed it's trivial to compute how much time it takes to travel 5 metres.
Use a camera that can have an external GPS connected to it so the images will be geocoded on the fly.
Use an ODBII cable and software for the laptop to get your speed from the car's computer to feed the camera control program.
----------------------
The "camera control" program I mention in options 2 and 3 would simply sample the speed, calculate how much time it takes to travel 5 metres and send notification to the stuff you already have. In the case of GPS input to it, you just need to know the applicable sentence for speed:
Quote:
VTG - Velocity made good.
GPVTG,054.7,T,034.4,M,005.5,N,010.2,K*48
where:
- VTG Track made good and ground speed
- 054.7,T True track made good (degrees)
- 034.4,M Magnetic track made good
- 005.5,N Ground speed, knots
- 010.2,K Ground speed, Kilometers per hour
- *48 Checksum
I have no clue how you would do the equivalent with ODBII but it shouldn't be any more difficult.
Those are just off the top of my head. I'm sure there are more possibilities that someone more creative than I can think up.
The limiting factor underlying all of these or any others is how accurate do the actual locations have to be? What maps are you planning to use the images with and how accurately are they calibrated with respect to reality? (Tip: Google's maps are not terribly accurate nor all that consistent from place to place.)
...ken...