summaryrefslogtreecommitdiffstats
path: root/doc/html/Attributes.html
blob: d09b1b51df999723bd326a26692af22a8053a480 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268

<html>
  <head>
    <title>Attribute Interface (H5A)</title>
    
<!-- #BeginLibraryItem "/ed_libs/styles_UG.lbi" --><link href="ed_styles/UGelect.css" rel="stylesheet" type="text/css">
<!-- #EndLibraryItem --></head>

  <body bgcolor="#FFFFFF">
  
  
<!-- #BeginLibraryItem "/ed_libs/NavBar_UG.lbi" --><hr>
<center>
<table border=0 width=98%>
<tr><td valign=top align=left>
    <a href="index.html">HDF5 documents and links</a>&nbsp;<br>
    <a href="H5.intro.html">Introduction to HDF5</a>&nbsp;<br>
    <a href="RM_H5Front.html">HDF5 Reference Manual</a>&nbsp;<br>   
    <!--
    <a href="Glossary.html">Glossary</a><br>
    -->
</td>
<td valign=top align=right>
    And in this document, the 
    <a href="H5.user.html"><strong>HDF5 User's Guide:</strong></a>&nbsp;&nbsp;&nbsp;&nbsp;
        <br>
        <a href="Files.html">Files</a>&nbsp;&nbsp;
        <a href="Datasets.html">Datasets</a>&nbsp;&nbsp;
        <a href="Datatypes.html">Datatypes</a>&nbsp;&nbsp;
        <a href="Dataspaces.html">Dataspaces</a>&nbsp;&nbsp;
        <a href="Groups.html">Groups</a>&nbsp;&nbsp;
        <br>
        <a href="References.html">References</a>&nbsp;&nbsp;
        <a href="Attributes.html">Attributes</a>&nbsp;&nbsp;
        <a href="Properties.html">Property Lists</a>&nbsp;&nbsp;
        <a href="Errors.html">Error Handling</a>&nbsp;&nbsp;
        <br>
        <a href="Filters.html">Filters</a>&nbsp;&nbsp;
        <a href="Caching.html">Caching</a>&nbsp;&nbsp;
        <a href="Chunking.html">Chunking</a>&nbsp;&nbsp;
        <a href="MountingFiles.html">Mounting Files</a>&nbsp;&nbsp;
        <br>
        <a href="Performance.html">Performance</a>&nbsp;&nbsp;
        <a href="Debugging.html">Debugging</a>&nbsp;&nbsp;
        <a href="Environment.html">Environment</a>&nbsp;&nbsp;
        <a href="ddl.html">DDL</a>&nbsp;&nbsp;
</td></tr>
</table>
</center>
<hr>
<!-- #EndLibraryItem --><h1>The Attribute Interface (H5A)</h1>

    <h2>1. Introduction</h2>

    <p>The attribute API (H5A) is primarily designed to easily allow small
        datasets to be attached to primary datasets as metadata information.
        Additional goals for the H5A interface include keeping storage
        requirements for each attribute to a minimum and easily sharing
        attributes among datasets.
    <p>Because attributes are intended to be small objects, large datasets
        intended as additional information for a primary dataset should be
        stored as supplemental datasets in a group with the primary dataset.
        Attributes can then be attached to the group containing everything to
        indicate a particular type of dataset with supplemental datasets is
        located in the group.  How small is "small" is not defined by the
        library and is up to the user's interpretation.
    <p>Attributes are not separate objects in the file, they are always
        contained in the object header of the object they are attached to.  The
        I/O functions defined below are required to read or write attribute
        information, not the H5D I/O routines.

    <h2>2. Creating, Opening, Closing and Deleting Attributes</h2>

    <p>Attributes are created with the <code>H5Acreate()</code> function,
      and existing attributes can be accessed with either the
      <code>H5Aopen_name()</code> or <code>H5Aopen_idx()</code> functions. All
      three functions return an object ID which should be eventually released
      by calling <code>H5Aclose()</code>.

    <dl>
      <dt><code>hid_t H5Acreate (hid_t <em>loc_id</em>, const char
	  *<em>name</em>, hid_t <em>type_id</em>, hid_t <em>space_id</em>,
	  hid_t <em>create_plist_id</em>)</code>
        <dd>This function creates an attribute which is attached to the object
    specified with <em>loc_id</em>.  The name specified with <em>name</em>
    for each attribute for an object must be unique for that object.  The <em>type_id</em>
    and <em>space_id</em> are created with the H5T and H5S interfaces
    respectively.  Currently only simple dataspaces are allowed for attribute
    dataspaces.  The <em>create_plist_id</em> property list is currently
    unused, but will be used in the future for optional properties of
    attributes.  The attribute ID returned from this function must be released
    with H5Aclose or resource leaks will develop.  Attempting to create an
    attribute with the same name as an already existing attribute will fail,
    leaving the pre-existing attribute in place.
    This function returns an attribute ID for success or negative for failure.

	<br><br>
      <dt><code>hid_t H5Aopen_name (hid_t <em>loc_id</em>, const char
	  *<em>name</em>)</code>
      <dd> This function opens an attribute which is attached to the object
    specified with <em>loc_id</em>.  The name specified with <em>name</em>
    indicates the attribute to access.  The attribute ID returned from this
    function must be released with H5Aclose or resource leaks will develop.
    This function returns an attribute ID for success or negative for failure.

	<br><br>
      <dt><code>hid_t H5Aopen_idx (hid_t <em>loc_id</em>, unsigned
	  <em>idx</em>)</code>
      <dd>This function opens an attribute which is attached to the object
    specified with <em>loc_id</em>.  The attribute specified with <em>idx</em>
    indicates the <em>idx</em>th attribute to access, starting with '0'. The
    attribute ID returned from this function must be released with H5Aclose or
    resource leaks will develop.
    This function returns an attribute ID for success or negative for failure.

	<br><br>
      <dt><code>herr_t H5Aclose (hid_t <em>attr_id</em>)</code>
      <dd>This function releases an attribute from use.  Further use of the
    attribute ID will result in undefined behavior.
    This function returns non-negative on success, negative on failure.

	<br><br>
      <dt><code>herr_t H5Adelete (hid_t <em>loc_id</em>, 
        const char *<em>name</em>)</code>
      <dd>This function removes the named attribute from a dataset or group.
    This function should not be used when attribute IDs are open on <em>loc_id</em>
    as it may cause the internal indexes of the attributes to change and future 
    writes to the open attributes to produce incorrect results.
    Returns non-negative on success, negative on failure.
    </dl>

    <h2>3. Attribute I/O Functions</h2>

    <p>Attributes may only be written as an entire object, no partial I/O
        is currently supported.

    <dl>
      <dt><code>herr_t H5Awrite (hid_t <em>attr_id</em>,
      hid_t <em>mem_type_id</em>, void *<em>buf</em>)</code>
      <dd>This function writes an attribute, specified with <em>attr_id</em>,
    with <em>mem_type_id</em> specifying the datatype in memory.  The entire
    attribute is written from <em>buf</em> to the file.
    This function returns non-negative on success, negative on failure.

	<br><br>
      <dt><code>herr_t H5Aread (hid_t <em>attr_id</em>,
      hid_t <em>mem_type_id</em>, void *<em>buf</em>)</code>
      <dd>This function read an attribute, specified with <em>attr_id</em>, with
    <em>mem_type_id</em> specifying the datatype in memory.  The entire
    attribute is read into <em>buf</em> from the file.
    This function returns non-negative on success, negative on failure.

    </dl>

    <h2>4. Attribute Inquiry Functions</h2>

    <dl>
      <dt><code>herr_t H5Aiterate (hid_t <em>loc_id</em>, 
      unsigned *<em>attr_number</em>, 
      H5A_operator <em>operator</em>, 
	  void *<em>operator_data</em>)</code>
      <dd> This function iterates over the attributes of the dataset or group
    specified with <em>loc_id</em>.  For each attribute of the object, the
    <em>operator_data</em> and some additional information (specified below)
    are passed to the <em>operator</em> function.  The iteration begins with
    the <em>*attr_number</em> object in the group and the next attribute to be
    processed by the operator is returned in <em>*attr_number</em>.
        <P>The iterator returns a negative value if something is wrong, the return
    value of the last operator if it was non-zero, or zero if all attributes
    were processed.
        <P>The prototype for H5A_operator_t is: <br>
            <code>typedef herr_t (*H5A_operator_t)(hid_t <em>loc_id</em>,
                const char *<em>attr_name</em>, void *<em>operator_data</em>);</code>
    <P>The operation receives the ID for the group or dataset being iterated over
    (<em>loc_id</em>), the name of the current attribute about the object (<em>attr_name</em>)
    and the pointer to the operator data passed in to H5Aiterate
    (<em>operator_data</em>).  The return values from an operator are:
        <ul>
        <li>Zero causes the iterator to continue, returning zero when all 
            attributes have been processed.
        <li>Positive causes the iterator to immediately return that positive
            value, indicating short-circuit success.  The iterator can be
            restarted at the next attribute.
        <li>Negative causes the iterator to immediately return that value,
            indicating failure.  The iterator can be restarted at the next
            attribute.
        </ul>
	<br><br>
      <dt><code>hid_t H5Aget_space (hid_t <em>attr_id</em>)</code>
      <dd>This function retrieves a copy of the dataspace for an attribute.
    The dataspace ID returned from this function must be released with H5Sclose
    or resource leaks will develop.
    This function returns a dataspace ID for success or negative for failure.
	<br><br>
      <dt><code>hid_t H5Aget_type (hid_t <em>attr_id</em>)</code>
      <dd>This function retrieves a copy of the datatype for an attribute.
    The datatype ID returned from this function must be released with H5Tclose
    or resource leaks will develop.
    This function returns a datatype ID for success or negative for failure.
	<br><br>
      <dt><code>ssize_t H5Aget_name (hid_t <em>attr_id</em>,
          size_t <em>buf_size</em>, char *<em>buf</em>)</code>
      <dd>This function retrieves the name of an attribute for an attribute ID.
    Up to <em>buf_size</em> characters are stored in <em>buf</em> followed by a
    '\0' string terminator.  If the name of the attribute is longer than
    <em>buf_size</em>-1, the string terminator is stored in the last position
    of the buffer to properly terminate the string.
    This function returns the length of the attribute's name (which may be
    longer than <em>buf_size</em>) on success or negative for failure.
	<br><br>
      <dt><code>int H5Aget_num_attrs (hid_t <em>loc_id</em>)</code>
      <dd>This function returns the number of attributes attached to a dataset or
    group, <em>loc_id</em>.
    This function returns non-negative for success or negative for failure.
    </dl>


<!-- #BeginLibraryItem "/ed_libs/NavBar_UG.lbi" --><hr>
<center>
<table border=0 width=98%>
<tr><td valign=top align=left>
    <a href="index.html">HDF5 documents and links</a>&nbsp;<br>
    <a href="H5.intro.html">Introduction to HDF5</a>&nbsp;<br>
    <a href="RM_H5Front.html">HDF5 Reference Manual</a>&nbsp;<br>   
    <!--
    <a href="Glossary.html">Glossary</a><br>
    -->
</td>
<td valign=top align=right>
    And in this document, the 
    <a href="H5.user.html"><strong>HDF5 User's Guide:</strong></a>&nbsp;&nbsp;&nbsp;&nbsp;
        <br>
        <a href="Files.html">Files</a>&nbsp;&nbsp;
        <a href="Datasets.html">Datasets</a>&nbsp;&nbsp;
        <a href="Datatypes.html">Datatypes</a>&nbsp;&nbsp;
        <a href="Dataspaces.html">Dataspaces</a>&nbsp;&nbsp;
        <a href="Groups.html">Groups</a>&nbsp;&nbsp;
        <br>
        <a href="References.html">References</a>&nbsp;&nbsp;
        <a href="Attributes.html">Attributes</a>&nbsp;&nbsp;
        <a href="Properties.html">Property Lists</a>&nbsp;&nbsp;
        <a href="Errors.html">Error Handling</a>&nbsp;&nbsp;
        <br>
        <a href="Filters.html">Filters</a>&nbsp;&nbsp;
        <a href="Caching.html">Caching</a>&nbsp;&nbsp;
        <a href="Chunking.html">Chunking</a>&nbsp;&nbsp;
        <a href="MountingFiles.html">Mounting Files</a>&nbsp;&nbsp;
        <br>
        <a href="Performance.html">Performance</a>&nbsp;&nbsp;
        <a href="Debugging.html">Debugging</a>&nbsp;&nbsp;
        <a href="Environment.html">Environment</a>&nbsp;&nbsp;
        <a href="ddl.html">DDL</a>&nbsp;&nbsp;
</td></tr>
</table>
</center>
<hr>
<!-- #EndLibraryItem --><!-- #BeginLibraryItem "/ed_libs/Footer.lbi" --><address>
<a href="mailto:hdfhelp@ncsa.uiuc.edu">HDF Help Desk</a> 
<br>
Describes HDF5 Release 1.5, Unreleased Development Branch
</address><!-- #EndLibraryItem -->

 
Last modified: 6 July 2000 


</body>
</html>