Summary

When generating End Area Volume (EAV) reports, users may notice additional stations appearing in the output that are not part of the selected Named Boundary Group. These extra rows typically occur at locations where the mass ordinate equals zero, which can make the report appear incorrect or confusing.

This behavior is expected and can be controlled through the report XSL configuration.

 

Description

The XML output generated for End Area Volume calculations intentionally includes additional stations where the mass ordinate is zero. These stations are included for calculation completeness and are labeled differently than the stations coming directly from the Named Boundary Group.

Specifically:

• Stations within the Named Boundary Group are written as:
  StationVolume
• Additional stations (typically where mass ordinate = 0) are written as:
  DerivedStationVolume

By default, the delivered EAV report stylesheets include both station types, which is why these extra rows appear in the final report.

The following delivered XSL stylesheets include both station types by default:

• EndAreaVolume.xsl
• Volume.xsl

Cause

The XSL templates in the delivered reports are configured to process both StationVolume and DerivedStationVolume nodes from the XML output. This results in extra rows appearing in the report table even when those stations are not part of the Named Boundary Group.

 

Resolution / Workaround

If you want the report to include only the stations defined by the Named Boundary Group, you can modify the XSL file to exclude the derived stations.

Steps:

1. Locate the report XSL file you are using (for example:
   EndAreaVolume.xsl or Volume.xsl).
2. Open the XSL file in a text editor.
3. Find the following line in the file:

<xsl:template match="StationVolume | DerivedStationVolume">

4. Replace it with:

<xsl:template match="StationVolume">

5. Save the XSL file.
6. Regenerate the End Area Volume report.

After this change, the report will only include stations that come directly from the Named Boundary Group, and the extra zero–mass-ordinate stations will no longer appear.

 

Additional Notes

• This behavior is by design and not a defect.
• No recalculation of volumes is required, and this is strictly a reporting filter.
• If you prefer to keep the original behavior, you can maintain two versions of the report:
  • One including derived stations
  • One excluding them for cleaner tabular output

Keywords

End Area Volume, EAV report, Mass Ordinate, Named Boundaries, DerivedStationVolume, StationVolume, XSL, OpenRoads reporting