Skip to main content

Result sets

A result set is a saved snapshot of analysis results at a point in time. Result sets are not modified or overwritten when new analyses run — they are the authoritative artifact drawings and forms reference, even after the underlying project keeps evolving. They are also where you fine-tune symbology for a specific deliverable, and the unit a course-of-action (COA) workflow uses to compare scenarios.

Learning objectives

By the end of this lesson you should be able to:

  • Capture a result set from a completed analysis
  • Read the four tabs of a result set (Details, Calculations, Spatial Analysis, Symbols)
  • Adjust per-result symbology, dimension lines, and arc precision without affecting the live project or other result sets
  • Use multiple result sets to compare COAs

Why result sets exist​

A live analysis result changes every time a feature edit triggers a re-run. A drawing or form that references live results will silently shift as the project evolves — sometimes invisibly, sometimes catastrophically (a deliverable approved on Monday no longer matches the project on Friday).

A result set decouples the deliverable from the working state. The drawing you ship today will look the same a month from now, even if the project has been heavily edited in the interim. The project keeps moving; the result set stays put.

Beyond that compliance role, result sets earn their keep in two more places:

  • Symbology fine-tuning — each result set carries its own copy of the four-category styling (arcs, spatial-analysis encumbrances, violation lines, dimension lines). Customize colors, line weights, union toggles, and dimension labels for a specific deliverable without polluting the project default.
  • Course-of-action (COA) analysis — when you want to compare scenarios (e.g., "what if we relocated Magazine 3?" vs "what if we reduce its NEW?"), capture a result set per COA. The frozen snapshots let you see the differences side-by-side.

The four tabs​

Opening a result set surfaces four tabs:

TabWhat it carries
DetailsThe result set's name (editable) and metadata
CalculationsThe same calc-results table as the project results panel — frozen at the snapshot's creation. All filter views, columns, and per-row detail (Criteria Path, Analysis Path, Adjust Arc Precision, Dimension Line + Dimension Text) operate on the snapshot copy
Spatial AnalysisThe encumbrances frozen alongside the calculations
SymbolsThe four-category styling (arcs, spatial analysis, violation lines, dimension lines), per-result-set

Edit any of these and the result set goes "dirty" — a discard control appears alongside save.

The toolbar​

A result set's toolbar carries five controls:

  • Save Current Result Set State — commits pending changes to the snapshot
  • Arc Tools menu — removes checked rows from the snapshot, covered in Trimming a result set
  • Discard changes — reverts to the last save (only visible when dirty)
  • Delete this Result Set — permanently removes the result set, after a confirmation dialog that names it
  • Export Results menu — covered in Generating drawings from a result set

Trimming a result set​

A snapshot often carries more than a deliverable needs — every calculation for every pair, when the drawing only shows one operating line. The Arc Tools menu removes checked rows from the snapshot itself. Because a saved result set starts with every row checked (checked rows are the ones drawn on the map), the safe sequence is: clear the header checkbox on the Calculations or Spatial Analysis tab, tick only the rows to drop, then choose Remove N Checked Calculations or Remove N Checked Spatial Results — the label counts the checked rows, so read it before confirming. The rows and their map graphics go immediately; the result set goes dirty, so Save Current Result Set State keeps the trim and Discard changes restores it.

Two details matter when trimming a filtered table:

  • The header checkbox and uncheck all act only on the rows currently listed — rows hidden by a view, filter, or search keep their checked state and their map graphics
  • Removing rows clears any column-filter selection that no longer matches a remaining row, so the table never shows an empty filter you cannot see

Trimming is per result set. The live project results and every other result set are untouched, which is what makes it safe to cut a deliverable-specific snapshot down to exactly what the drawing shows. For the click-by-click steps see Result Sets → How to remove results from a Result Set.

Generating drawings from a result set​

The Export Results menu offers four drawing presets plus a result-set export:

OptionOutput
Generate Drawing (1":400')Standard DCMA scale, no legend
Generate Drawing (1":400') with LegendStandard DCMA scale, includes a legend
Generate Drawing (Current)Extent based on the current map zoom — useful for briefing-style outputs where exact scale isn't required
Generate Drawing (Current) with LegendCurrent-extent + legend
ExportExports the result set itself for handoff or backup

Drawings produced from a result set inherit the snapshot's symbology — including any per-result-set style edits you made on the Symbols tab.

Adjusting arc precision​

Each calculation row's per-row detail exposes Adjust Arc Precision — a per-result-set knob that controls how many vertices the arc polygon uses. Higher precision means a smoother arc and slightly longer render time; lower precision means a faceted arc that renders faster. Adjust per result set, per arc, when a deliverable's medium (printed drawing vs on-screen briefing) calls for different fidelity.

Dimension lines and labels​

Dimension lines are added per calculation row from the per-row detail in the Calculations tab. The default label format is auto-generated from the result; the Dimension Text field lets you override it for the deliverable's authority — K18 ILD, 1,250 ft fixed, or a fully custom label.

Override the text when:

  • The convention at your organization differs from the auto-generated default
  • The deliverable needs additional context (e.g., naming the analysis code explicitly)
  • A label collides with another and needs to be shortened or relocated

Naming and lifecycle​

Result sets accumulate over a project's life. Pick names that will still make sense in six months: Initial baseline 2026-05, After magazine relocation, DCMA Q3 submittal final, COA-A: NEW reduction, COA-B: relocate M3. Avoid bare dates with no context, and avoid context with no date.

Result sets stay editable after creation — the Save button on the toolbar commits new state. Delete this Result Set asks you to confirm, naming the result set in the dialog, then removes it permanently; any drawings already generated from a deleted result set keep their captured contents but lose the ability to regenerate against that snapshot.

Try it​

Snapshot baseline:

  1. In an analyzed project, capture a result set named Baseline
  2. Make a deliberate edit (e.g., increase NEW on a PES) and re-run
  3. Confirm live results show the post-edit state while Baseline still reflects the pre-edit state
  4. Generate a drawing against Baseline and confirm it shows the original arcs

COA comparison:

  1. From the same project, capture a second result set named COA-A: NEW reduced
  2. Edit the project to apply COA-A's changes (reduce NEW on the PES) and re-run
  3. Save the COA-A result set with the new state
  4. Open both Baseline and COA-A: NEW reduced side-by-side. The two snapshots are independent — comparing them shows the COA's effect without the underlying project getting in the way.