Data

2007-08 V3 CEAMARC-CASO Event List

data.gov.au
Australian Antarctic Division (Owned by)
Viewed: [[ro.stat.viewed]] Cited: [[ro.stat.cited]] Accessed: [[ro.stat.accessed]]
ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&rfr_id=info%3Asid%2FANDS&rft_id=http://data.gov.au/dataset/dba8ea5e-1c8a-4895-bb5c-ccae880343f0&rft.title=2007-08 V3 CEAMARC-CASO Event List&rft.identifier=2007-08-v3-ceamarc-caso-event-list&rft.publisher=data.gov.au&rft.description=GET DATA - Download the excel spreadsheets detailing the event logsTwo components. The first component is an even log for all station and instrument deployements. The second component is a log where start and end bottom times need to be recorded for instruments for example the benthic trawl. There is one file for each of the logs. Both logs need to be ideally merged into one to have one data source of event information. The start and end bottom times need to ideally go into the event logging system on the ship.\n \n 1) Event log for stations and all instrument deployments\n \n Stations and instrument deployments were recorded (including failures) over the progress of the voyage to provide a summary of all work carried out over voyage and and assigned an Event ID number for referencing data associated with these events.\n \n Data_Format \n \n Data was initially recorded in the ship board PostgreSQL database. Data was exported as a comma delimited file 'events.csv' at the end of the voyage.\n \n Column 1 - Setcode (voyage identifier of the form 200708030 meaning year 2007-08, voyage 3)\n \n Column 2 - Voyage Code (text voyage identifier)\n \n Column 3 - Transect ID (transect identifier, no transects were identified this voyage)\n \n Column 4 - Station ID (Station identifier, blank for events not associated with a station, CEAMARC project stations are pre-pended with 'CEAMARC', CASo stations are pre-pended with 'CASO', sampling near icebergs for trace metals pre-pended with 'ICEBERG', woCE SR3 transect sampling pre-pended wuith 'SR3').\n \n Column 5 - Event ID (unique ID across voyage for individual events)\n \n Column 6 - Event Type (usually the instrument deployed, self explanatory. One event type 'Plankton Water Sample' refers to mass water sampling undertaken for genomics work).\n \n Column 7 - User Reference (id used by individual scientitsts to reference their data for this event. If left blank they are using the auto assigned event id from this table).\n \n Column 8 - Start Timestamp (start timestamp of the event in UTC).\n \n Column 9 - Start Latitude (start latitude of the event from the ship gps)\n \n Column 10 - Start Longitude (start longitude of the event from the ship gps)\n \n Column 11 - Start Bottom Depth (bottom depth at the start time of the event in metres from EK60 sounder bathymetry export)\n \n Column 12 - End Timestamp (end timestamp of the event in UTC)\n \n Column 13 - End Latitude (end latitude of the event from the ship gps)\n \n Column 14 - End Longitude (end longitude of the event from the ship gps)\n \n Column 15 - Duration (duration of the event in hours)\n \n Column 16 - End Bottom Depth (bottom depth at the end time of the event in metres from EK60 sounder bathymetry export)\n \n Column 17 - Min bottom Depth (minimum bottom depth encountered over event period from EK60 sounder bathymetry export)\n \n Column 17 - Avg Bottom Depth (average bottom depth encountered over event period from EK60 sounder bathymetry export)\n \n Column 18 - Max Bottom Depth (maximum bottom depth encountered over event period from EK60 sounder bathymetry export)\n \n Column 19 - Author (person who entered event details into logging system)\n \n Column 20 - Notes (notes peculiar to the event, may be blank)\n \n 2) Log of instrument bottom times.\n \n Excel spreadsheet 'Trawl_log_18_Jan_08_final.xls'\n \n Column A - Station number, these are all CEAMARC station numbers, matching stations in the event log pre-pended by 'CEAMARC'.\n \n Column B - Event ID (matching event log, sometimes blank as this log an contain entries on intended events that did not get carried out for some reason or another)\n \n Column C - Trawl Name (labelled trawl name, actually event type as the log started off with ust trawl start/end bottom times, but was expanded to encompass other event types like grabs etc.)\n \n Column D - Date of the event.\n \n Column E - Ship Speed (in knots from displays of gps speed).\n \n Column F - Time instrument hit the water in utc\n \n Column G - Time instrument reached the bottom in utc.\n \n Column H - Time instrument left the bottom (i.e. hauling started) in utc.\n \n Column I - Time instrument on the deck (ie out of the water)\n \n Column J - Depth in meters read of EK60 sounder display (could be any time during event).\n \n Column K - Comments pertaining to the event.&rft.creator=Australian Antarctic Division&rft.date=2023&rft.coverage=139.01488,-67.07104 150.06479,-67.07104 150.06479,-42.88246 139.01488,-42.88246 139.01488,-67.07104&rft.coverage=139.01488,-67.07104 150.06479,-67.07104 150.06479,-42.88246 139.01488,-42.88246 139.01488,-67.07104&rft.coverage=true&rft_rights=Other&rft_subject=AMD&rft_subject=Beam Trawl&rft_subject=CEOS&rft_subject=CURRENT METERS&rft_subject=Cameras&rft_subject=SHIPS&rft_subject=SIDE-SCAN SONAR&rft_subject=Sled trawl&rft_subject=Smith McIntyre Grab&rft_subject=bottom trawl&rft.type=dataset&rft.language=English Access the data

Licence & Rights:

Other view details
Other

Other

Brief description

Two components. The first component is an even log for all station and instrument deployements. The second component is a log where start and end bottom times need to be recorded for instruments for example the benthic trawl. There is one file for each of the logs. Both logs need to be ideally merged into one to have one data source of event information. The start and end bottom times need to ideally go into the event logging system on the ship.\n \n 1) Event log for stations and all instrument deployments\n \n Stations and instrument deployments were recorded (including failures) over the progress of the voyage to provide a summary of all work carried out over voyage and and assigned an Event ID number for referencing data associated with these events.\n \n Data_Format \n \n Data was initially recorded in the ship board PostgreSQL database. Data was exported as a comma delimited file 'events.csv' at the end of the voyage.\n \n Column 1 - Setcode (voyage identifier of the form 200708030 meaning year 2007-08, voyage 3)\n \n Column 2 - Voyage Code (text voyage identifier)\n \n Column 3 - Transect ID (transect identifier, no transects were identified this voyage)\n \n Column 4 - Station ID (Station identifier, blank for events not associated with a station, CEAMARC project stations are pre-pended with 'CEAMARC', CASo stations are pre-pended with 'CASO', sampling near icebergs for trace metals pre-pended with 'ICEBERG', woCE SR3 transect sampling pre-pended wuith 'SR3').\n \n Column 5 - Event ID (unique ID across voyage for individual events)\n \n Column 6 - Event Type (usually the instrument deployed, self explanatory. One event type 'Plankton Water Sample' refers to mass water sampling undertaken for genomics work).\n \n Column 7 - User Reference (id used by individual scientitsts to reference their data for this event. If left blank they are using the auto assigned event id from this table).\n \n Column 8 - Start Timestamp (start timestamp of the event in UTC).\n \n Column 9 - Start Latitude (start latitude of the event from the ship gps)\n \n Column 10 - Start Longitude (start longitude of the event from the ship gps)\n \n Column 11 - Start Bottom Depth (bottom depth at the start time of the event in metres from EK60 sounder bathymetry export)\n \n Column 12 - End Timestamp (end timestamp of the event in UTC)\n \n Column 13 - End Latitude (end latitude of the event from the ship gps)\n \n Column 14 - End Longitude (end longitude of the event from the ship gps)\n \n Column 15 - Duration (duration of the event in hours)\n \n Column 16 - End Bottom Depth (bottom depth at the end time of the event in metres from EK60 sounder bathymetry export)\n \n Column 17 - Min bottom Depth (minimum bottom depth encountered over event period from EK60 sounder bathymetry export)\n \n Column 17 - Avg Bottom Depth (average bottom depth encountered over event period from EK60 sounder bathymetry export)\n \n Column 18 - Max Bottom Depth (maximum bottom depth encountered over event period from EK60 sounder bathymetry export)\n \n Column 19 - Author (person who entered event details into logging system)\n \n Column 20 - Notes (notes peculiar to the event, may be blank)\n \n 2) Log of instrument bottom times.\n \n Excel spreadsheet 'Trawl_log_18_Jan_08_final.xls'\n \n Column A - Station number, these are all CEAMARC station numbers, matching stations in the event log pre-pended by 'CEAMARC'.\n \n Column B - Event ID (matching event log, sometimes blank as this log an contain entries on intended events that did not get carried out for some reason or another)\n \n Column C - Trawl Name (labelled trawl name, actually event type as the log started off with ust trawl start/end bottom times, but was expanded to encompass other event types like grabs etc.)\n \n Column D - Date of the event.\n \n Column E - Ship Speed (in knots from displays of gps speed).\n \n Column F - Time instrument hit the water in utc\n \n Column G - Time instrument reached the bottom in utc.\n \n Column H - Time instrument left the bottom (i.e. hauling started) in utc.\n \n Column I - Time instrument on the deck (ie out of the water)\n \n Column J - Depth in meters read of EK60 sounder display (could be any time during event).\n \n Column K - Comments pertaining to the event.

Full description

GET DATA - Download the excel spreadsheets detailing the event logs

This dataset is part of a larger collection

Click to explore relationships graph

139.01488,-67.07104 150.06479,-67.07104 150.06479,-42.88246 139.01488,-42.88246 139.01488,-67.07104

144.539835,-54.97675

139.01488,-67.07104 150.06479,-67.07104 150.06479,-42.88246 139.01488,-42.88246 139.01488,-67.07104

144.539835,-54.97675

text: true

Subjects

User Contributed Tags    

Login to tag this record with meaningful keywords to make it easier to discover

Identifiers