Demo Implementation Details

The creation of the pixel lists for the cBathy and stack data requires the PIXel Toolbox to be downloaded and on your Matlab path.

The toolbox is called UAVProcessing and includes a Contents.m file that describes all of the routines (‘help UAVProcessingCodes’). The toolbox includes a demo data set and all routines are already set up to allow automatic processing of this 400 frame demo case (in local folder demoMovies) by typing ‘sampleAerielleVideoDemo’ while in the toolbox. Due to the size of the demo images (> 1GB) they are not managed using SVN but are available from http://cil-www.coas.oregonstate.edu/UAVdemoMovies.zip. This zip file should be unpacked in the toolbox directory, creating a demoMovies directory.

Some routines are listed in the help as being ‘CIL routines’ that are called and are located in a folder called neededCILRoutines. If you don’t have CIL routines set up, you should either add this folder to your path or just copy the routines to the UAVProcessingCodes folder.

When you run the demo, you will have to click on the gcps shown in Figure 1, going from seaward to shoreward on the pier, then on the south (right), then north (left), checkerboard targets on the dune crest. All targets are checkerboards, but the seaward one is REALLY hard to see (it is just a tiny white dot). In choosing the reference points, chose a dune target as the first point with a box size similar to that shown in Figure 1. Of the four reference points, you can choose three points on the dune but at least one must not be in line with the others (on the pier is the obvious choice). Click a small surrounding box so there is no chance of getting background breakers in the target search. Figure 2 in your display will show the video frame by frame along with the found reference points (red) and geometry solution (black circles). This will allow you to determine if the tracking gets confused. If you want to see the reference point windows, set inputs.showFoundRefPoints to 1 and they will be displayed in figure window 11, 12 ….

You can change the instruments as much as you want.

If you run the analysis, results will be stored in a default output directory, determined by the contents of makeUAVPn.m (set by default to demoMovies/demoOutput). The default is ONLY for demonstration and should not be used for real analysis (set up a good output strategy like the one discussed above and in commented text in this routine). Note that once you have run the demo once, the default output folder will contain the results including the meta data file. Thus if a second person tries the demo, the program will find the meta data file and assume that you don’t want to redo geometries. Delete files in the output directory to give a second person a fresh analysis. Look in the output directory for all of your output.

argusFilename.m (in neededCILRoutines) usually looks to the argus database for information. The version here has those references removed so times will be whatever you want but will say GMT. You will receive a warning occasionally that the station name was not found in the toolbox so the GMT time zone will be assumed. Ignore this.

‘every’ is a perl script to break out frames. It is included but likely won’t work. You are responsible for breaking out your own frames.

Exiftool is a free tool that is available on the web or is commonly part of standard computer software. It provides, among other things, the GPS and vertical location of the camera for images (not for all cameras) that can be used for geometry solutions. The same info may be available from iminfo in matlab or in image library packages like Portfolio. Values must be accurate to fractions of a second in latitude and longitude to be useful.