The Debrief Blog

REP file parsing is complete. Legacy Debrief files now transform into validated GeoJSON with line-level error reporting.

Enhancing our spec workflow to detect UI features and capture interaction design details upfront.

Local STAC catalog operations are complete. Debrief v4.x can now create catalogs, store plots, and preserve provenance — all offline.

Building local STAC catalog operations for offline-first analysis storage in Debrief v4.x.

Establishing the schema foundation for Debrief v4.x with LinkML as the single source of truth.

Learn more about handling periods of missing data in Debrief

On occasion it’s useful to determine the version of Java that a Debrief installation is using.

After a couple of months of development, we're preparing the release of the new Debrief scripting ability This new capability is intended to enable Debrief Power Users to take on more advanced data manipulation tasks, including: Apply bulk changes to Debrief objects Import unexpected data-types from file Conduct ad-hoc calculations on Debrief data

We're coming to the end of another new feature. Most of the time Debrief data comes in digital form, captured on another system. But, occasionally it arrives in text form and has to be transcribed. Some users do this within Debrief, others perform the task in a text editor such as Notepad, then save the...

Symbols are used to add value to analysis plots, through giving a visual indication of the vehicle type. In the past, the symbols have been hard-coded in Debrief, but now Debrief supports the provision of vectored symbols in the industry standard SVG format. The first set of symbols is shown below. Please feel free to...