Variables in this Dataset

  • Description: "Common Name of the Fish Species"
  • Description: "Scientific Name of the Fish Species"
  • Description: "Lifestage is one of the following: Eggs, Larvae, Juveniles or Adults"
GENDER: String
  • Description: "Gender which is either: Both, Unknown, Male or Female."
  • Description: "Habitat Association is either: Strong, Medium, Weak or Unknown."
SEASON: String
  • Description: "Season is one of: Spring, Summer, Autumn, Winter, All Year or Unknown."
  • Description: "Habitat based on 4 tier scheme. Level 1 Habitat examples include: Abyssal Plain, Coastal Intertidal, Estuarine, Inland Sea, Nearshore, etc."
  • Description: "Habitat based on 4 tier scheme. Level 2 Habitat is one of: Basin, Benthos, Intertidal Benthos, Seamount, Submarine Canyon, Unknown or Water Column."
  • Description: "Habitat based on 4 tier scheme. Level 3 Habitat examples include: Artificial Structure, Biogenic, Epipelagic Zone, Hardbottom, etc."
  • Description: "Habitat based on 4 tier scheme. Level 4 Habitat examples include: Algal Beds/Macro, Artificial Reef, Bedrock, Boulder, Clay, Cobble, etc."
  • Description: "Activity is one of: All, Breeding, Feeding, Growth to Maturity, Spawning or Unknown."
  • Description: "Activity Association is either: Strong, Medium, Weak or Unknown"

No Dataset Specific Information Available.

DODS Relational Database Server

This data is being served by a DODS Relational Database Server (DRDS), which is a somewhat unusual instance of a DODS server. All of the data served by the DRDS is stored in a relational database management system (DBMS). Queries from DODS clients are translated into SQL queries and sent to the underlying DBMS. The reuturned data is read by the DRDS and returned to the requesting client.

Because the DRDS is essentially a front end to a DBMS, the DDS's have a somewhat different meaning than in other DODS servers. Each DDS served by the a DRDS represents a table in the underlying DBMS. Since queries to the DBMS will return an unknown amount of data, each DDS basically must contain a representation of the tables contents defined as a DODS sequence. Because of this it rarely makes sense for a client to request the entire "dataset", as this request will return the entire contents of the table. When requesting data from a DRDS, it is best to get the dataset information (using the .info extension on the DODS URL) and then build a constrained request that just returns data that is actually desired. This doesn't mean that the entire table cannot be requested and sent, it is simply a caution that each dataset/DDS/table may in fact be very large.

Server Functions:

unique(): This function gets used in the selection part of the DODS constraint expression. It requires no parameters. Calling this funcion will cause the return to contain only unique rows. This is useful for sifting through numerous identical fields, for example station data that contains instrument names. This is NOT very useful if you are trying to retrieve a ship track...


Regular Expressions: The typical DODS server supports the full range regular expression syntax. THIS DODS server does not. Limited string matching is available. The wild card characters '.' and '.*' may used. The '[...]' notation for matching a range of characters may be used, but only to match a single character to a range of possiblities.



String fields in the DBMS may contain white space (spaces). In order for a constraint to match you must include the spaces. For example, if you wish to retrieve all data where a field called location has a value of "Southern Ocean", in your DODS URL you will have to represent the space between "Southern" and "Ocean" with the symbol "%20". Like this:
However, if the DODS URL is formed with a space like this:
    location="Southern Ocean"
It will not be handled correctly by the DRDS.

Have fun!