Dataset Information

Variables in this Dataset

Vdata:

Sequence

dINT32:

Structure

dINT32__0:

32 bit Integer

dUINT32:

Structure

dUINT32__0:

32 bit Unsigned Integer

dINT16:

Structure

dINT16__0:

32 bit Integer

dUINT16:

Structure

dUINT16__0:

32 bit Unsigned Integer

dINT8:

Structure

dINT8__0:

32 bit Integer

dUINT8:

Structure

dUINT8__0:

8 bit Byte

dFLOAT32:

Structure

dFLOAT32__0:

64 bit Real

dFLOAT64:

Structure

dFLOAT64__0:

64 bit Real

dCHAR8:

Structure

dCHAR8__0:

String

dUCHAR8:

Structure

dUCHAR8__0:

String

No Dataset Specific Information Available.

DODS Test Server

This data is being served by the Java-DODS Test Server. This server was created to allow any possible DODS data structure to be tested for viablity in both the client and server software components of DODS.

This server will take any DODS DDS and attempt serve it to clients with all implemented modes of functionality. It will populate it with data (created from thin air!) and hand it back to a requesting client. It can also be intergogated using the other DODS server interfaces such as the ASCII interface (.asc) the DDS (.dds) interface, the DAS interface (.das), and the HTML interface (.html, also know as the interface from hell...)

The key word in the preceding paragraph is attempt. Since the DODS dataset specification allows for a virtually unlimited range of dataset structures, it certainly possible to create datasets that break existing code, either on the client or the server side. We have, to the best of our abilities, made the DODS core software capable of handling all possible syntactically correct DODS datasets as described by a DDS. However, it is possible to construct dataset definitions (DDS's) so weird and twisted that the DODS core software cannot handle them well. Ultimately that's why this server exists:

To explore the boundaries of what DODS can and cannot do.

Hopefully, you will find it useful too.