BES - Modules - CSV Handler - Revision history

Jimg: /* Simple attribute definitions */

2015-05-01T22:43:55Z

Simple attribute definitions

← Older revision		Revision as of 22:43, 1 May 2015
Line 46:		Line 46:
	Attributes {		Attributes {
	Station {		Station {
	String bouy_type 17;		String bouy_type "flashing";
	Byte Age 53;		Byte Age 53;
	}		}
	Global {		Global {
	String DateCompiled "11/17/98";		String DateCompiled "11/17/98";
			String Conventions "CF-1.0", "CF-1.6";
	}		}
	}		}
	</source>		</source>
	The format of this file is very simple: Each variable in the dataset may have a collection of attributes, each of which		The format of this file is very simple: Each variable in the dataset may have a collection of attributes, each of which consists of a type, a name and one or more values. In the above example, the variable ''Station'' will have the additional attributes ''bouy_type'' and ''Age'' with the respective types and values. Note that datasets may also define global attributes - information about the dataset as a whole - by adding a section with a name that doesn't match the name of any variable in the dataset. In this example, I used ''Global'' for this (because it's obvious) but I could have used ''foo''. Also note the attribute ''Conventions'' has two values, ''CF-1.0'' and 'CF-1.6''.

Jimg at 22:38, 1 May 2015

2015-05-01T22:38:01Z

← Older revision		Revision as of 22:38, 1 May 2015
Line 45:		Line 45:
	<source lang="c">		<source lang="c">
	Attributes {		Attributes {
	~~Bill~~ {		Station {
	String ~~LastName "Evans"~~;		String bouy_type 17;
	Byte Age 53;		Byte Age 53;
	~~String DaughterName "Matilda";~~
	~~Matilda {~~
	~~String LastName "Fink";~~
	~~Byte Age 26;~~
	}
	}		}
	Global {		Global {
	~~String Name "FamilyData";~~		String DateCompiled "11/17/98";
	String DateCompiled "11/17/98";
	}		}
	}		}
	</source>		</source>
	The format of this file is very simple: Each variable in the dataset may have a collection of attributes, each of which		The format of this file is very simple: Each variable in the dataset may have a collection of attributes, each of which

Jimg: /* Configuring Datasets */

2015-05-01T22:36:17Z

Configuring Datasets

← Older revision		Revision as of 22:36, 1 May 2015
Line 40:		Line 40:
	=== Configuring Datasets ===		=== Configuring Datasets ===
	There are two ways to add custom attributes to a dataset. First, you can use an ''ancillary attribute'' file in the same directory as the dataset. Alternatively, you can use NcML to add new attributes, variables, etc. See [[BES_-_Modules_-_NcML_Module \| the NcML Handler documentation]] for more information on that option. Here we will describe how to set up an ancillary attribute file.		There are two ways to add custom attributes to a dataset. First, you can use an ''ancillary attribute'' file in the same directory as the dataset. Alternatively, you can use NcML to add new attributes, variables, etc. See [[BES_-_Modules_-_NcML_Module \| the NcML Handler documentation]] for more information on that option. Here we will describe how to set up an ancillary attribute file.

			===== Simple attribute definitions =====
			For any OpenDAP dataset, it is possible to write an ancillary attributes file like the following. If that file has the name ''dataset''.<tt>das</tt> then whenever Hyrax reads ''dataset'', it will also read those attributes, and return them when asked.
			<source lang="c">
			Attributes {
			Bill {
			String LastName "Evans";
			Byte Age 53;
			String DaughterName "Matilda";
			Matilda {
			String LastName "Fink";
			Byte Age 26;
			}
			}
			Global {
			String Name "FamilyData";
			String DateCompiled "11/17/98";
			}
			}
			</source>
			The format of this file is very simple: Each variable in the dataset may have a collection of attributes, each of which

Jimg: /* = */

2015-05-01T22:31:30Z

← Older revision		Revision as of 22:31, 1 May 2015
Line 40:		Line 40:
	=== Configuring Datasets ===		=== Configuring Datasets ===
	There are two ways to add custom attributes to a dataset. First, you can use an ''ancillary attribute'' file in the same directory as the dataset. Alternatively, you can use NcML to add new attributes, variables, etc. See [[BES_-_Modules_-_NcML_Module \| the NcML Handler documentation]] for more information on that option. Here we will describe how to set up an ancillary attribute file.		There are two ways to add custom attributes to a dataset. First, you can use an ''ancillary attribute'' file in the same directory as the dataset. Alternatively, you can use NcML to add new attributes, variables, etc. See [[BES_-_Modules_-_NcML_Module \| the NcML Handler documentation]] for more information on that option. Here we will describe how to set up an ancillary attribute file.

	~~=====~~

Jimg: /* Configuring Datasets */

2015-05-01T22:27:03Z

Configuring Datasets

← Older revision		Revision as of 22:27, 1 May 2015
Line 39:		Line 39:

	=== Configuring Datasets ===		=== Configuring Datasets ===
	There are two ways to add custom attributes to a dataset. First, you can use an ''ancillary attribute'' file in the same directory as the dataset. Alternatively, you can use NcML to add new attributes, variables, etc. See [\|the NcML Handler documentation] for more information on that option.		There are two ways to add custom attributes to a dataset. First, you can use an ''ancillary attribute'' file in the same directory as the dataset. Alternatively, you can use NcML to add new attributes, variables, etc. See [[BES_-_Modules_-_NcML_Module \| the NcML Handler documentation]] for more information on that option. Here we will describe how to set up an ancillary attribute file.

			=====

Jimg: /* Configuring Datasets */

2015-05-01T22:21:34Z

Configuring Datasets

← Older revision		Revision as of 22:21, 1 May 2015
Line 39:		Line 39:

	=== Configuring Datasets ===		=== Configuring Datasets ===
			There are two ways to add custom attributes to a dataset. First, you can use an ''ancillary attribute'' file in the same directory as the dataset. Alternatively, you can use NcML to add new attributes, variables, etc. See [\|the NcML Handler documentation] for more information on that option.

Jimg: /* Dataset representation */

2015-05-01T22:18:52Z

Dataset representation

← Older revision		Revision as of 22:18, 1 May 2015
Line 27:		Line 27:
	</source>		</source>
	This is in contrast to the FreeForm handler that would represent these data as a Sequence with five columns.		This is in contrast to the FreeForm handler that would represent these data as a Sequence with five columns.

			For each column, the corresponding Array in the OpenDAP dataset has one attribute named ''type'' with a string value of ''Int16'', ..., ''String''. However, see below for information on how to add custom attributes to a dataset.

	=== Known problems ===		=== Known problems ===

Jimg: /* Configuring the handler */

2015-05-01T22:16:53Z

Configuring the handler

← Older revision		Revision as of 22:16, 1 May 2015
Line 34:		Line 34:

	=== Configuring the handler ===		=== Configuring the handler ===
			This handler has no specific configuration parameters.

	=== Configuring Datasets ===		=== Configuring Datasets ===

Jimg: /* Supported OpenDAP datatypes */

2015-05-01T22:16:23Z

Supported OpenDAP datatypes

← Older revision		Revision as of 22:16, 1 May 2015
Line 13:		Line 13:

	===== Supported OpenDAP datatypes =====		===== Supported OpenDAP datatypes =====
	The CSV handler supports ~~all of~~ the DAP2 simple types: ~~Byte,~~ Int16~~, UInt16~~, Int32~~, UInt32~~, Float32, Float64, String~~, and Url~~.		The CSV handler supports the following DAP2 simple types: Int16, Int32, Float32, Float64, String.

	===== Dataset representation =====		===== Dataset representation =====

Jimg: /* Configuration parameters */

2015-05-01T22:14:32Z

Configuration parameters

@@ Line 32: / Line 32: @@
 == Configuration parameters ==
 === Configuring the handler ===
 === Configuring Datasets ===