Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sensorweb integration
urnvessel:heincke:gaps
contenttypeMetadata
ManufactureriXblue
ModelOIGAPS-Carbone
Serial No.n/a
Typeultra short baseline positioning systems



Sensorweb integration
urnvessel:heincke:gaps
contenttypeImages



...

Sensorweb integration
urnvessel:heincke:gaps
contenttypeContacts
NameInstitutionRole
Ralf KrockerAlfred-Wegener-Institute for Polar and Marine ResearchEngineer In Charge

Components

The system consists of the GAPS antenna itself, mounting for installation at the ships bottom, the Easy Connect Box (ECB) and monitoring software "GAPS MMI - Man Machine Interface". The transponders can be mounted to winch wire or to a submarine vehicle or other submarine object.

...

Sensorweb integration
urnvessel:heincke:gaps
contenttypeLocalFrame
Origin Description:Electronics of the GAPS system are located in the server rack in the Mess- and Registrierraum and software is installed on the CTD-PC. The GAPS is deployed via the Hydrographenschacht.

Data logging, storage and archiving

...

Sensorweb integration
urnvessel:heincke:gaps
contenttypeParameters
ParameterSensor Output TypeUnit
headingattitudedegree
latitudelatitudedegree
longitudelongitudedegree
altitudeattitudem
rollattitudedegree
pitchattitudedegree
transponder numberindexunknown
x-coordinatedistancem
y-coordinatedistancem
z-coordinatedistancem
depthdepthm
monthdate and timeunknown
time in hoursdate and timeunknown
yeardate and timeunknown
daydate and timeunknown

Central geographical ship's position and time standard


Metadata (Metadata Plugin)
0timestandard
Time synchronising of the PC with MMI-Software via Windows-Domain-Affiliation. Centering of GPS-antenna position to GAPS and to transponders.

Rawdata storage on board

Metadata (Metadata Plugin)
0Rawdata
Data storage in DShip system.

DShip

Metadata (Metadata Plugin)
0DShip
Uncorrected measurement data.
Metadata list
|| Device name

...

 | GAPS || 
|| Parameters| Transponder2; Transponder3; Transponder1; Ship0; Altitude std dev; GAPS.HEHDT.Sentence; GAPS.PIXSE.ATI.datafield01;  GAPS.PIXSE.ATI.datafield04; GAPS.PIXSE.STDH.datafield01; GAPS.PIXSE.STDP.datafield01; Heading \[deg\]; Heading std dev; Latitude std dev; Longitude std dev; Pitch \[deg\]; Pitch std dev; Roll \[deg\]; Roll std

...

 dev ||
|| Transponder Parameter| Day; Depth \[m\]; EW; Month; NS; Time; Transponder No SAG; Transponder No SAX; X coordinate \[m\]; Y coordinate \[m\]; Year; Z coordinate \[m\] ||
|| Ship0 Parameter| Day; Depth \[m\]; EW; GAPS.PTSAG.0.Latitude; GAPS.PTSAG.0.Longitude; Month; NS; Time; Transponder_No_SAG;Transponder_No_SAX; X_coordinate \[m\]; Y_coordinate \[m\]; Year; Z_coordinate \[m\] ||

Data archiving on land

Metadata (Metadata Plugin)
0DataOnLand
After the cruise the DShip data set can be extracted from https://dms.awi.de.

Documentation

Sensorweb integration
urnvessel:heincke:gaps
contenttypeResources