WEBVTT

00:00:00.440 --> 00:00:02.520
Welcome to OPUS Projects Training.

00:00:03.080 --> 00:00:06.050
In this module, we will discuss the importance of field

00:00:06.100 --> 00:00:07.560
logs and their correctness.

00:00:08.119 --> 00:00:11.000
If you intend to submit your project to NGS for

00:00:11.060 --> 00:00:14.560
publication, It is important to note that your field logs

00:00:14.620 --> 00:00:17.560
must be included as part of your project report.

00:00:19.360 --> 00:00:22.210
Please note the current version of OPUS Projects may look

00:00:22.260 --> 00:00:25.120
slightly different than the screens in this presentation.

00:00:25.640 --> 00:00:28.680
The functionality generally remains the same.

00:00:31.640 --> 00:00:35.390
A field log standardizes the metadata and reminds or even

00:00:35.460 --> 00:00:38.880
forces field observers to enter certain information.

00:00:39.560 --> 00:00:43.780
Many data collectors can be pre configured with standardized responses

00:00:43.840 --> 00:00:46.200
such as check boxes or pull down lists.

00:00:47.240 --> 00:00:51.170
Even some default values can be prefilled such as

00:00:51.250 --> 00:00:54.360
agency name, observer name and others.

00:00:55.360 --> 00:00:58.280
A field log can be electronic or paper.

00:00:58.920 --> 00:01:01.840
Paper field logs can be scanned to PDF form for

00:01:01.910 --> 00:01:05.140
submittal, or they can be hand entered in the office

00:01:05.200 --> 00:01:07.880
into an electronic form and then submitted.

00:01:09.240 --> 00:01:12.080
Field logs should be archived for future reference.

00:01:12.920 --> 00:01:15.840
Please note again that if you intend to submit your

00:01:15.900 --> 00:01:19.050
project to NGS for publication, your field logs must be

00:01:19.110 --> 00:01:21.400
included as part of your project report.

00:01:23.760 --> 00:01:26.690
Here's a listing of many of the common metadata items

00:01:26.750 --> 00:01:28.240
that some agencies require.

00:01:28.720 --> 00:01:33.179
In this case, it reflects the items on the NGS GNSS

00:01:33.280 --> 00:01:35.240
observation log sheet.

00:01:36.040 --> 00:01:41.300
The NGS GNSS observation log sheet places the metadata items in

00:01:41.390 --> 00:01:46.319
logically related groups, and these are some of the groups.

00:01:48.840 --> 00:01:52.460
Here are the remaining groups of metadata, about 50 fields

00:01:52.520 --> 00:01:52.960
in all.

00:01:55.840 --> 00:02:00.760
The NGS GNSS Observation log sheet can be obtained from

00:02:00.850 --> 00:02:02.280
the NGS website.

00:02:02.840 --> 00:02:09.600
It is the obslog.pdf choice and is preferred for OPUS Projects submissions.

00:02:11.400 --> 00:02:15.700
The NGS Field Survey Forms page offers a second, simpler

00:02:15.770 --> 00:02:19.840
alternative log sheet for RTN or OPUS share purposes.

00:02:20.639 --> 00:02:26.389
It is the obslog-OPUS.pdf choice and is preferred for OPUS

00:02:26.490 --> 00:02:28.280
share submissions.

00:02:30.080 --> 00:02:33.600
Certain agencies require their own field log forms.

00:02:33.720 --> 00:02:36.200
Here's the FAA airport's field log.

00:02:36.880 --> 00:02:40.919
It's a 2 sided form with about 70 fields, and

00:02:41.010 --> 00:02:46.210
this is an example of the Vermont Agency of Transportation

00:02:46.300 --> 00:02:49.080
Field log with about 20 fields.

00:02:49.760 --> 00:02:52.780
Be sure you know which field log forms are required

00:02:52.840 --> 00:02:55.630
by your agency or contract, and be sure you are

00:02:55.690 --> 00:02:58.600
familiar with the expected entries in each field.

00:02:58.680 --> 00:03:00.720
Don't guess, ask for training.

00:03:04.400 --> 00:03:08.110
Mistakes in file naming and session naming are not uncommon,

00:03:08.169 --> 00:03:11.880
yet they can cause significant confusion and mistakes later.

00:03:13.000 --> 00:03:15.880
RINEX file names follow conventional rules.

00:03:16.360 --> 00:03:20.340
Note that proprietary RAW to RINEX converters might not name

00:03:20.410 --> 00:03:23.940
files as expected by OPUS Projects rules, so care must

00:03:24.000 --> 00:03:27.400
be taken to verify that the RINEX file names follow

00:03:27.470 --> 00:03:28.120
the rules.

00:03:28.720 --> 00:03:33.389
Session naming sessions are observed sequentially in the field in,

00:03:33.460 --> 00:03:38.130
usually lettered A through Z, but observers sometimes have several

00:03:38.200 --> 00:03:39.760
sessions during a day.

00:03:40.280 --> 00:03:44.640
Observer 1 might be observing his or her third session

00:03:44.720 --> 00:03:48.510
equal session C of the day, while Observer 2 is

00:03:48.590 --> 00:03:52.870
observing his or her first session equal to session A

00:03:52.950 --> 00:03:53.840
of the day.

00:03:54.800 --> 00:03:58.160
So OPUS Projects needs a consistent set of names.

00:03:58.640 --> 00:04:04.050
OPUS Projects renames the incoming RINEX file automatically according to

00:04:04.130 --> 00:04:05.760
the file's start time.

00:04:09.360 --> 00:04:12.720
RINEX files should be named according to conventional rules.

00:04:12.800 --> 00:04:13.840
Let's work through them.

00:04:16.080 --> 00:04:20.990
SSSS is the unique 4 character mark ID assigned to

00:04:21.089 --> 00:04:24.040
each user mark in the project.

00:04:24.520 --> 00:04:27.480
This should be the first four characters of the file

00:04:27.540 --> 00:04:28.960
that is uploaded to OPUS.

00:04:30.080 --> 00:04:34.600
To easily associate observation files to specific user marks, make

00:04:34.670 --> 00:04:38.310
sure to start the observation file name with the four

00:04:38.380 --> 00:04:40.160
character ID for the mark.

00:04:41.200 --> 00:04:45.050
DDD is the day of the year of the start

00:04:45.150 --> 00:04:46.240
of the day.

00:04:46.760 --> 00:04:49.480
This is sometimes called the Julian day number.

00:04:51.000 --> 00:04:55.589
H is a letter representing the starting hour of the

00:04:55.680 --> 00:04:56.760
data in UTC.

00:04:58.040 --> 00:05:01.810
OPUS will convert your field file name to this format

00:05:01.880 --> 00:05:02.880
when uploaded.

00:05:04.440 --> 00:05:07.560
X is the session identifier.

00:05:08.080 --> 00:05:10.360
The first session is named A.

00:05:11.240 --> 00:05:14.800
If there are multiple sessions in the same GPS day,

00:05:14.870 --> 00:05:17.880
the next session will be named B and so on.

00:05:18.440 --> 00:05:22.320
This is the recommended format for naming your field files.

00:05:24.080 --> 00:05:28.470
YY is the 2 digit year, T is the file

00:05:28.589 --> 00:05:36.180
type, O for observation, N for navigation, M for meteorological,

00:05:36.290 --> 00:05:37.480
and so on.

00:05:38.360 --> 00:05:41.970
Let me draw special attention to the H and X in the

00:05:42.050 --> 00:05:43.280
next few slides.

00:05:45.839 --> 00:05:48.960
Here's a diagram of the RINEX naming convention.

00:05:49.000 --> 00:05:52.420
In this example, the letter A is the user assigned

00:05:52.490 --> 00:05:56.400
session letter for the first observation file of the day.

00:05:58.920 --> 00:06:03.060
The OPUS Projects user guide states that the OPUS Projects

00:06:03.130 --> 00:06:07.630
will rename your your uploaded file using this convention based

00:06:07.700 --> 00:06:11.480
on the starting time of the observations in the file.

00:06:14.960 --> 00:06:18.820
Here's a diagram of the renaming sequence followed by OPUS

00:06:18.880 --> 00:06:19.480
projects.

00:06:20.120 --> 00:06:23.839
In this example, the letter A will be replaced by

00:06:23.910 --> 00:06:28.380
OPUS Projects with the letter T since the first observation

00:06:28.460 --> 00:06:31.570
time in the file was in the 19th UTC hour

00:06:31.640 --> 00:06:32.480
of the day.

00:06:36.600 --> 00:06:39.370
When you upload a file to OPUS Projects, a pop

00:06:39.430 --> 00:06:43.100
up window informs you of certain information which you should

00:06:43.160 --> 00:06:43.640
confirm.

00:06:44.400 --> 00:06:47.160
Note the automatic conversion of the file name.

00:06:51.120 --> 00:06:56.440
The individual session names on a field log sheet should

00:06:56.540 --> 00:07:02.040
follow the pattern year, day of year, sequence letter, for

00:07:02.140 --> 00:07:04.040
example, 2013-121-A.

00:07:05.360 --> 00:07:09.210
Later, when the field log is converted or scanned into

00:07:09.279 --> 00:07:13.770
electronic form for submission, the file name should follow the

00:07:13.840 --> 00:07:17.970
pattern for character ID, day of year, session letter, and

00:07:18.040 --> 00:07:18.400
year.

00:07:20.200 --> 00:07:26.580
NGS will accept several file types, including PDF, TXT and so on,

00:07:26.690 --> 00:07:28.730
so the file name will include the three character

00:07:29.040 --> 00:07:39.680
file name extension as well, for example BM02-121-a-2013.pdf.

00:07:42.720 --> 00:07:47.500
If each field log is a unique electronic file, they

00:07:47.590 --> 00:07:52.469
can be zipped into a single file for submission, for

00:07:52.560 --> 00:07:55.840
example project_9734.zip. Paper

00:07:55.840 --> 00:08:00.739
field logs should first be grouped by 4 character ID,

00:08:00.830 --> 00:08:06.460
then chronologically by session and year, then scanned into a

00:08:06.560 --> 00:08:12.560
single multi page format file for submission. For example

00:08:12.660 --> 00:08:14.320
project_9734.pdf.

00:08:15.480 --> 00:08:17.040
This is the end of the module.

00:08:17.040 --> 00:08:19.240
I hope you have found it helpful and thank you

00:08:19.290 --> 00:08:19.960
for listening.