Build 200 – New Effort and Sightings Detail Reports

Mysticetus build number hits 200!

The last build I posted about was 170, so that’s 30 builds of new features – sometimes multiple features per build. I haven’t been posting recently because I’ve been so insanely busy. But I certainly haven’t quit adding features to Mysticetus. So the next few weeks I’ll post at least once a week catching up with the features I’ve been adding over the past few months.

To kick it off, some new report types.


Effort Detail Report

The existing Effort Summary report is nice. It totals up time and trackline distance spent on and off effort. But it isn’t very detailed, nor does it handle situations (e.g. mitigation efforts) where there are more than one “On” and “Off” effort state.

The new Effort Detail Report now buckets time and trackline data across all effort states and all regions (as defined by polygons). For example, here’s a cumulative effort detail report of a week of aerial marine mammal surveys, broken down by effort type (Systematic, Transit, Overland, etc.) and by the polygon region where the effort took place.

To run this report, choose the Reports menu item, and then configure the items correctly, in particular specifying your effort or environmental sheet and the field that controls the effort type:

As I show here, you can apply restrictions to the report, such as “Only report effort where the Bft state was equal to 3”. You can also set up some “Ignore States” – for week-long summary reports being able to ignore times the airplane is at the airport or boat at the dock is critical.

Optionally, you can define some polygon regions. Here are some we use in the Puget Sound:

If you don’t use any regions, Mysticetus will simply calculate an Overall Total for you.

Sighting Detail Report

The Sighting Detail Report creates a row for each sighting across all entry sheets in the system. And you control what goes in each column. First, configure the Sighting Detail report how you want

Note that you can also pick a Distance To any vehicle in the system. This comes in handy with, for example, seismic surveys where you want to know exactly how far a sighting was from a source vessel…even if the sighting came from some other station (aerial, theodolite, etc.) – Mysticetus will match up the source vessel’s trackline at the time of the sighting, and calculate exact distance.

Then generate the report. Here is an example of a detail report. As you can see, Mysticetus reports exactly what you tell it to report (I chose Init Spec, Region and Psd (perpendicular sighting distance)) – you can of course choose any and all fields from your sighting sheet.


Next post, I’ll go through a ton of new editing features in Mysticetus that facilitate QA, GIS and Cloud Storage and Reporting.

Take Care


Leave a Reply

Your email address will not be published. Required fields are marked *

fourteen − seven =