Equipment
Photo Taking
Actually taking photos of a trail only requires some common equipment:
GoPro
- GoPro with GPS (newer models do not have GPS anymore…)
- Micro SD Card (for reference, a 1KM trail takes about 12GB of storage), I use a 512GB.
- Enough batteries (usually 1 battery per 800m).
A GoPro is used because:
- It is relatively common.
- It includes lots of extra useful data (such as gyoroscope and GPS).
- It has a removable SD card with decent write speeds (there is a lot of data to transfer).
- It has swappable batteries.
- It is quite rugged and weather proof.
- It is a simple, single lens.
Currently, only the Hero 10 Black has been verified to work. It is important that you know that using any other type of GoPro will likely require some adjustments, due to differences in lenses.
Scale Bar
A scale bar is a reference object used in scans, in order to give the camera something of known size.
It is extremely important, that the scale bar is as rigid as possible. Even millimeteres of bow/flex is enough to throw off the accuracy of the reconstruction.
Given this, my current scale bar is as follows:
- 1m square steel tube
- 3x flat builders shim (just a flat piece of plastic)
- 3x APRILtags, attached to the shims with double sided tape
3 tagStandard41h12 tags are printed (see https://novanix.github.io/apriltag-pdf-gen/) and placed onto 3 of the flat builders shims. These shims are then bolted onto the square steel tube (1 at start, 1 center, 1 at end).
Then, the distances between these 3 tags are measured extremely carefully, and entered into the reconstruction settings.
Fluro token
This is just a piece of plastic that is fluroescent and easily visible. Because the scanning requires 2 passes of the trail (forwards and backwards), the token is dropped onto the ground to mark where the turnaround point was, so you don’t need to remember it.
Processing scans
Unfortunately, processing these models does require a decently equipped PC due to the sheer amount of computation required.
I have had success on my mid-range PC:
- 16GB RAM
- RTX3070 8GB Graphics Card
- AMD Ryzen 5 5600X 6-Core Processor
- Linux
- Enough storage (a 1KM trail takes about 50GB of total storage for all the intermediary data)
The only difference really will be the processing time. Currently with the above setup, the end to end processing time is about 20 hours per KM of trail (I aim to get this as low as possible though!).
The only hard constraint really is a modern-ish graphics card - due to Nvidia CUDA driver support being dropped for older graphics cards.