Assigning data types
Assigning Datatypes – Guide & Tips
In order to assign a datatype, you first need to understand the layout of the data.
The default datatype is Point, but it could also be a Profile, Profile Biology, Timeseries, or various other options. Start by finding out the parameter that is associated with the platform's position. It might be station, haul, tow, etc.
For example, ‘mooring’ usually has the position information. Go to the parameters page, select ‘mooring’ and assign the following datatypes: ‘profile’, ‘graphable’, and ‘do not display as options’ (so it won’t appear in the drop-down box on the mapper page).
Then select the parameter that contains the depth data, usually ‘depth’ or ‘press’ and assign datatypes: ‘depth variable’ and ‘graphable’
The parameters that will be plotted should be assigned ‘graphable’. Examples are u,v,w (adcp data).
If latitude and longitude have unusual names (eg. lat_start, lon_start), assign them to ‘object latitude exception’ and ‘object longtude exception’.
Other parameters must be assigned datatypes also, if they are to be mapped. Some confusing ones include:
‘select scale it’ will cause the mapper to display the ‘narrow search by’ option. Assign this to the parameter that will be the name of the list. For example, taxon, species, common_name, contaminant, temp_ss.
‘scale it count columns’ will cause the mapper to display the ‘group by’ option. Assign this to parameters such as abundance, biomass, net.
‘scale it subselect columns’ will allow a subselection, for example, if you have chosen taxon and then want to subselect a stage within that taxon, or if you have a tow and want to subselect the net number. Example parameters for this type: stage, mesh, size, net (for tow photos), config.
‘fetch multiple rows’ is needed when some of the parameters are on different levels from others. An example might be length and mesh size (NEC gillnet data).
Time series:
depth = depth
yrday_gmt = both TS Time and Time Series – Rank 2, plus graphable
assign the x and y variables (x is depth, y is time, z is current, for eg.) ***??? This needs to be verified.
Example with zoo_MOC_GoM:
“I added the lat and lon to zoo_MOC_GoM so it now is mappable. Can the temp_avg and sal_avg be mapped, too? should they be? For laughs, I made sal_avg "scale it count columns' and it showed up under 'group by' along with abund and biomass but it doesn't give an xy-plot. I think a plot of abund or biomass vs. salinity or temperature would be useful, but perhaps not necessary. “ (NC)
“You have to mark it as profile (biology) first. Then you have to mark something as the 'location'. Is there a station or tow column? If you leave temp and sal alone and don't mark them anything but graphable, you will get plots of temp vs depth. We're still working on what happens when you mark something select scale it. Not to be done lightly...” (DA)
“The plots look reasonable, like abund vs. depth_mid or biomass vs. temp_avg.” (NC)
Here are the parameter datatype assignments: Overall datatype is ‘point’.
| Parameter | Datatype | Datatype |
| abund | graphable | scale it count columns |
| biomass | graphable | scale it count columns |
| cast | graphable | profile Biology |
| comments | ||
| cruiseid | ||
| date_local | ||
| depth_interval | ||
| depth_mid | depth variable | |
| lat | ||
| lon | ||
| month_local | ||
| net | ||
| day_night | ||
| sal_avg | graphable | |
| site | ||
| taxon_code | select scale it | |
| time_local | ||
| temp_avg | graphable | |
| year | ||
| yrday_local | graphable |