Sounds like you're not using the command to trigger a camera, but perhaps to do something else entirely. Might as well come clean, we promise not to tell anyone :-)
We are triggering a camera array. Doing every 1/2 mile and tossing 1/2 of the photos is not practical at the scale we are acquiring imagery. We're capturing tens of thousands of photos at a time. The wear and tear on the cameras precludes us 'overshooting' and keeping only 1/2 of the image sets.
Replies
Sounds like you're not using the command to trigger a camera, but perhaps to do something else entirely. Might as well come clean, we promise not to tell anyone :-)
We are triggering a camera array. Doing every 1/2 mile and tossing 1/2 of the photos is not practical at the scale we are acquiring imagery. We're capturing tens of thousands of photos at a time. The wear and tear on the cameras precludes us 'overshooting' and keeping only 1/2 of the image sets.
Maybe then set waypoints at every GPS coordinates where a picture should be taken and use do-digicam commands to trigger?
This would require that we hit our WP radius. This will not always be possible. Also it requires some preflight planning that we wish to avoid.
Hi,
Why don't you set the trigger to half a mile (around 800) and use one out of two pictures?
That does seem the simple solution. Unfortunately, that will not work in our specific application.