BES Aggregation

From OPeNDAP Documentation
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

By default there are no aggregation engines installed with the BES. But there is a mechanism to register your own aggregation engine. This page will discuss how to go about doing that.

How does aggregation work in the BES?

A request comes into the BES that references some containers, create a definition using those containers adding constraints and specifying an aggregation engine to use and an aggregation command, and then a get command to grab the containers, constrain them, and then aggregate. The command would look something like this:

<?xml version="1.0" encoding="UTF-8"?>
<request reqID="some_unique_value" >
    <setContainer name="c1" space="catalog">/data/nc/</setContainer>
    <setContainer name="c2" space="catalog">/data/nc/</setContainer>
    <setContainer name="c3" space="catalog">/data/nc/</setContainer>
    <setContainer name="c4" space="catalog">/data/nc/</setContainer>
    <define name="d">
	<container name="c1">
	<container name="c2">
	<container name="c3">
	<container name="c4">
        <aggregate handler="someHandler" cmd="someCommand" />
    <get type="dods" definition="d" />