Any data can be included in a given data catalog, but not all data can be (or should be) aggregated. Two data files that can (usefully) appear joined together in an Aggregation Server might be records of the same kinds of data on different dates, or different kinds of data at the same location, or data at adjoining locations at the same time. That is, the data to be aggregated must share some common features to be worth the trouble to aggregate them. If you can't imagine a user wanting to make the same query to two different data files, they probably aren't worth aggregating.
Even though two data files are not aggregated, they may still be included as part of the same data catalog. The catalog can help users find data, even though it isn't aggregated.
The OPeNDAP Catalog/Aggregation Server can handle three different forms of aggregation. We call these three JoinNew, JoinExisting, and Union. We'll examine each of these in turn.
NOTE: As of version 0.6 of the Aggregation Server, only Grid and Array data types can be aggregated.
Here, A, B, and C represent sets of measurements in the X and Y dimensions. The three sets are aggregated along the Z axis. This means that none of A, B, or C have a Z variable in those sets, but they all contain (or represent) a single Z value. In our example above, X and Y are spatial dimensions, and Z would be time.
Now that you have the idea of what is meant by aggregation, the next section will show how to specify the method and parameters for aggegration using the necessary XML syntax. The following chapter will explain how to install the server. Chapter 3 describes how to configure the aggregation server so it will show your data in the way you want.