Export Generic

return

Standard Columns ^₁₎
Seq	Sequence or Prefix number from the online Session Setup	Same value appears multiple times when the database was split during recording
Raw Database	Filename of the recorded raw database	The file is always located in the project's Database subfolder
Size	File size on disk of the recorded raw database
Linename	Name of the mainline (point, line or route) during recording or replay	Will be displayed in red color when: The mainline is a route, and the original line data file (qgf) is not found in the projects LineData subfolder. This may affect exporting Line Offsets items (group RESULT DATA), because the individual route section co-ordinates need to be retrieved for accurate line offset calculation. The mainline from the last replay session is different than the selected mainline during recording time. In both situations a tool-tip will be displayed in the column with a notification.
Start (UTC)	UTC date/time of the start of the recording	Without the extra run-in period. The date value is only preceded at every new date change
Duration	Duration (hh:mm:ss) of the recording session.	Possible pause recording actions are not taken into account
Line change	The time period (hh:mm:ss) between the stop recording event of this database and the start recording event of the next selected database.	The period will be 00:00:00 when the selected databases are part of the same sequence and have been split. Will be displayed in red color when the period is 'negative', most likely because a database and a copy (filt.db) is selected simultaneously.
Fix Range	The first and the last fix number
Results	Indicates if the corresponding result file (res) can be found in the project's Results subfolder. A results file is needed for exporting items from group RESULT DATA (e.g. Computations, Nodes, Line Offsets)	Yes A full result file is found, containing results for the entire duration of the recording. Partial A result file is found, but does not contain results for the entire duration of the recording, most likely because the database was replayed partially. Empty A result file is found but no fix numbers were detected. Fix numbers are currently used to determine whether the database was replayed partially or in full. So you may most likely ignore this and continue... No No results are found. Only raw data can be exported. Replay the database first when you want to export group RESULT DATA items. A tool-tip will be displayed at the mouse cursor with additional information about the result file.
QPD	Indicates if the corresponding DTM Qinsy Processing Points file (qpd) can be found in the project's DtmData subfolder. A Qinsy Processing Points file is needed for exporting QPD items (group DTM).	Yes A full qpd file is found, containing DTM data for the entire duration of the recording Yes A full qpd file is found, containing DTM data for the entire duration of the recording. This file is not accepted yet in the Survey Manager, hence the red color. Partial A qpd file is found, but does not contain DTM data for the entire duration of the recording, most likely because the database was replayed partially. No No DTM data is found. Replay the database and create a Qinsy Processing Points file in case you want to export QPD items from the DTM group. A tool-tip will be displayed at the mouse cursor with additional information about the qpd file.

All Columns ¹⁾
Seq	Sequence or Prefix number from the online Session Setup	Same value appears multiple times when the database was split during recording
Raw Database	Filename of the recorded raw database	The file is always located in the project's Database subfolder
Vn	The Qinsy Product Release version at time of recording	As reference, the current installed version can be checked using the Console under the Support pull-down menu
Size	File size on disk of the recorded raw database
Linename	Name of the mainline (point, line or route) during recording or replay	Will be displayed in red color when: The mainline is a route, and the original line data file (qgf) is not found in the projects LineData subfolder. This may affect exporting Line Offsets items (group RESULT DATA), because the individual route section co-ordinates need to be retrieved for accurate line offset calculation. The mainline from the last replay session is different than the selected mainline during recording time. In both situations a tool-tip will be displayed in the column with a notification.
Run-in	Each recorded raw database contains about 30 seconds of raw data before the actual time of recording. This value will be less when start recording happened immediately after coming online. The run-in time is only used during replay in order to settle computation filters and avoiding extrapolating data at the start.	By default, all exported data will be excluded from this run-in time. In case you do need to export data from this extra period, enable the option in the Settings dialog (click on the icon in the upper left corner). Notice that multibeam data is not part of the run-in period, only positioning, heading and motion related data.
Start Date	UTC date/time of the start of the recording	Without the extra run-in period.
Start Time	UTC date/time of the start of the recording	Without the extra run-in period. The resolution of the seconds can be increased in the Settings dialog (click on the icon in the upper left corner).
End Date	UTC date/time of the end of the recording
End Time	UTC date/time of the end of the recording
Duration	Duration (hh:mm:ss) of the recording session.	Possible pause recording actions are not taken into account
Line change	The time period (hh:mm:ss) between the stop recording event of this database and the start recording event of the next selected database.	The period will be 00:00:00 when the selected databases are part of the same sequence and have been split. Will be displayed in red color when the period is 'negative', most likely because a database and a copy (filt.db) is selected simultaneously.
First Fix	First fix number
Last Fix	Last fix number
Results	Indicates if the corresponding result file (res) can be found in the project's Results subfolder. A results file is needed for exporting items from group RESULT DATA (e.g. Computations, Nodes, Line Offsets)	Yes A full result file is found, containing results for the entire duration of the recording. Partial A result file is found, but does not contain results for the entire duration of the recording, most likely because the database was replayed partially. Empty A result file is found but no fix numbers were detected. Fix numbers are currently used to determine whether the database was replayed partially or in full. So you may most likely ignore this and continue... No No results are found. Only raw data can be exported. Replay the database first when you want to export group RESULT DATA items. A tool-tip will be displayed at the mouse cursor with additional information about the result file.
QPD	Indicates if the corresponding DTM Qinsy Processing Points file (qpd) can be found in the project's DtmData subfolder. A Qinsy Processing Points file is needed for exporting QPD items (group DTM).	Yes A full qpd file is found, containing DTM data for the entire duration of the recording Yes A full qpd file is found, containing DTM data for the entire duration of the recording. This file is not accepted yet in the Survey Manager, hence the red color. Partial A qpd file is found, but does not contain DTM data for the entire duration of the recording, most likely because the database was replayed partially. No No DTM data is found. Replay the database and create a Qinsy Processing Points file in case you want to export QPD items from the DTM group. A tool-tip will be displayed at the mouse cursor with additional information about the qpd file
Use Template	The online used template at time of recording	Will be displayed in gray and appended by an asterix when the online used template is not found in the project's Database subfolder.

Note 1)
Use right mouse popup menu to toggle between showing the standard or all columns