An object in HDF5 consists of an object header at a fixed file address that contains messages describing various properties of the object such as its storage location, layout, compression, etc. and some of these messages point to other data such as the raw data of a dataset. The address of the object header is also known as an OID and HDF5 has facilities for translating names to OIDs.
Every HDF5 object has at least one name and a set of names can be stored together in a group. Each group implements a name space where the names are any length and unique with respect to other names in the group.
Since a group is a type of HDF5 object it has an object header and a name which exists as a member of some other group. In this way, groups can be linked together to form a directed graph. One particular group is called the Root Group and is the group to which the HDF5 file boot block points. Its name is "/" by convention. The full name of an object is created by joining component names with slashes much like Unix.
However, unlike Unix which arranges directories hierarchically, HDF5 arranges groups in a directed graph. Therefore, there is no ".." entry in a group since a group can have more than one parent. There is no "." entry either but the library understands it internally.
HDF5 places few restrictions on names: component names may be any length except zero and may contain any character except slash ("/") and the null terminator. A full name may be composed of any number of component names separated by slashes, with any of the component names being the special name ".". A name which begins with a slash is an absolute name which is looked up beginning at the root group of the file while all other relative names are looked up beginning at the current working group (described below) or a specified group. Multiple consecutive slashes in a full name are treated as single slashes and trailing slashes are not significant. A special case is the name "/" (or equivalent) which refers to the root group.
Functions which operate on names generally take a location identifier which is either a file ID or a group ID and perform the lookup with respect to that location. Some possibilities are:
Location Type | Object Name | Description |
---|---|---|
File ID | /foo/bar |
The object bar in group foo
in the root group of the specified file. |
Group ID | /foo/bar |
The object bar in group foo
in the root group of the file containing the specified
group. In other words, the group ID's only purpose is
to supply a file. |
File ID | / |
The root group of the specified file. |
Group ID | / |
The root group of the file containing the specified group. |
File ID | foo/bar |
The object bar in group foo
in the current working group of the specified file. The
initial current working group is the root group of the
file as described below. |
Group ID | foo/bar |
The object bar in group foo
in the specified group. |
File ID | . |
The current working group of the specified file. |
Group ID | . |
The specified group. |
Other ID | . |
The specified object. |
Groups are created with the H5Gcreate()
function,
and existing groups can be access with
H5Gopen()
. Both functions return an object ID which
should be eventually released by calling
H5Gclose()
.
hid_t H5Gcreate (hid_t location_id, const char
*name, size_t size_hint)
H5Gclose()
when it's no longer needed. A negative value is returned for
failure.
hid_t H5Gopen (hid_t location_id, const char
*name)
H5Gclose()
when it is no
longer needed. A negative value is returned for failure.
herr_t H5Gclose (hid_t group_id)
H5Gcreate()
or
H5Gopen()
. After closing a group the
group_id should not be used again. This function
returns zero for success or a negative value for failure.
Each file handle (hid_t file_id
) has a
current working group, initially the root group of the file.
Names which do not begin with a slash are relative to the
specified group or to the current working group as described
above. For instance, the name "/Foo/Bar/Baz" is resolved by
first looking up "Foo" in the root group. But the name
"Foo/Bar/Baz" is resolved by first looking up "Foo" in the
current working group.
herr_t H5Gset (hid_t location_id, const char
*name)
herr_t H5Gpush (hid_t location_id, const char
*name)
herr_t H5Gpop (hid_t location_id)
An object (including a group) can have more than one name. Creating the object gives it the first name, and then functions described here can be used to give it additional names. The association between a name and the object is called a link and HDF5 supports two types of links: a hard link is a direct association between the name and the object where both exist in a single HDF5 address space, and a soft link is an indirect association.
herr_t H5Glink (hid_t file_id, H5G_link_t
link_type, const char *current_name,
const char *new_name)
H5G_LINK_HARD
then a new
hard link is created. Otherwise if link_type is
H5T_LINK_SOFT
a soft link is created which is an
alias for the current_name. When creating a soft
link the object need not exist. This function returns zero
for success or negative for failure. This function is not
part of the prototype API.
herr_t H5Gunlink (hid_t file_id, const char
*name)