7.1. The Project Manager’s Web Page¶
Fig. 7.1 The Project Manager’s web page¶
Elements numbered in the figure above are explained in the corresponding subsections below:
7.1.1. Notices¶
Notices about OP and, very rarely, a message specific to a project (no other project will see these specific messages) may appear at the top of the Manager’s, Session and Marks web pages. An email link to the OPUS Projects Team will appear with any notices and messages so that follow-up questions can be asked if needed.
Fig. 7.2 The Notices banner on the OPUS Projects Manager’s Page¶
7.1.2. Results Selection Menu¶
Below the web page’s banner (and any notices) is a pull down menu to select from a list of the solution results available. Broadly, there are three categories: network adjustment, session solutions, and OPUS solutions. As work in a project progresses, displaying all types of results simultaneously becomes confusing. This menu provides a simple “filter” to help emphasize the results of most interest.
Fig. 7.3 Drop-down menu location for displaying results on the Manger’s Page¶
7.1.3. Project Map¶
The Manager’s, Session and Marks web pages are built around a Google Map Services™ interactive map to help orient users within the project and its geographic region. As project members upload observation data to the project through OPUS, icons representing the user marks will appear on the map. CORSs used by OPUS during its processing of the project data will be added to the project at upload or can be added to the project later. Different icons are used to reflect a user mark’s status in the project.
Caution
All marks observed are displayed on the map, as well as all CORSs used in the individual OPUS solutions. This does not mean that all marks were observed in all sessions, nor that all CORSs were available or are automatically selected in all sessions.
Within the map display to the upper-left, there are typical zoom controls (+/-) and controls to zoom specifically to the project’s ‘Marks’ or ‘Marks & CORS.’
Fig. 7.4 Map zooming toggles¶
At the upper-left corner of the map you may set the map background as either Terrain (digital elevation model), Satellite (satellite imagery if available), or Map (towns, streets & highways). You also have the option to click and drag (pan) the map to view nearby areas.
Fig. 7.5 Map background options¶
Holding the cursor over a user mark icon will cause the icon to lighten in color and the mark’s ID to appear.
Fig. 7.6 Mark ID shown by hovering over mark¶
Clicking a mark icon on the map (or under the MARKS list) will cause information about the data files associated with that user mark to appear in an information ‘bubble.’
Fig. 7.7 Mark data information shown when clicking on a user mark icon¶
The mark ID is given at the top of the information bubble. If the mark is a user mark (not a CORS), the ID acts as a convenience link to navigate to the summary web page of that mark. A table listing all of the uploaded data files for a particular user mark is also shown in the bubble. More than one file for a mark means data observed at the mark is in multiple sessions. Note that the antenna type and ARP height associated with each file are also shown for the record. The project team member who uploaded the files is assigned as the ‘OBSERVER.’ Their name is a convenience link to send them an email message.
Similarly, hovering the cursor over a CORS icon will create a bubble containing the four-character CORS ID, its Permanent Identifier (PID), and designation.
Clicking on the CORS icon on the map (or under the CORS list) will cause information about the CORS data to appear in an information ‘bubble.’ Data availability for each of the sessions identified in the project will be displayed under “STATUS.” Additional information such as antenna type, antenna height, data file, etc. are also given in the table.
Fig. 7.8 CORS ID shown when hovering over a CORS¶
Fig. 7.9 CORS data information shown when clicking on the CORS icon¶
7.1.4. Controls Bar¶
Controls for common manager tasks appear on the left side of the map.
Fig. 7.10 The Controls bar¶
Tip
Controls differ somewhat among the different web pages available in OP4.0. They also differ between the Manager’s Page and the session processing page, and may differ according to the steps you have already accomplished.
7.1.4.1. Help, Back and Refresh¶
Fig. 7.11 Top page control options¶
Help, Back, and Refresh buttons appear at the top of the controls. The Help button is under development and may ultimately provide the same resource as this document. The Back “moves back” to the previous web page in the browser’s history. Its action is identical to the browser’s back control. The Refresh button forces the project to be scanned and the current page reloaded. Use this OP refresh button rather than the one for the browser.
7.1.4.2. Preferences¶
Fig. 7.12 Preferences button on the Controls bar¶
The Preferences button enables access to preferences, described in Section 4.
7.1.4.3. Project List¶
Fig. 7.13 Project List button on the Controls bar¶
The Project List button sends an email to the project manager listing all projects created under the manager’s email address. The provided information includes project IDs, keywords, and titles. This can come in very handy for recovering lost or forgotten project information.
7.1.4.4. Solutions¶
Fig. 7.14 Solutions button on the Controls bar¶
The Solutions button opens a new window enabling the manager to rename Session Solutions and Network Adjustments, as well as delete the solutions and adjustments (allowing them to be re-computed). More on Session Solutions in Section 10, and Network Adjustments in Section 11.
Fig. 7.15 Manage Solutions pop-up window¶
7.1.4.5. Add Project Tracking ID¶
Fig. 7.16 Add Tracking ID button on the Controls bar¶
Clicking on the Add Project Tracking ID button will open a separate window in which the user can input the NGS-provided Project Tracking ID (an outcome of submitting a survey project proposal to NGS). Recall that a Project Tracking ID unlocks the advanced features of OP.
Fig. 7.17 Attach NGS Project Tracking ID pop-up window¶
7.1.4.6. Show File¶
Fig. 7.18 Show File button on the Controls bar¶
The Show File button reveals a pop-up window for displaying all available solution reports.
Fig. 7.19 Pop-up window showing a sample solution from a processed session¶
Standard pop-up window controls appear at the top, and the window offers a choice of available reports:
Individual OPUS solutions
Session processing results
Network adjustment results
Below the controls is a header providing the report’s name, its creation and download (current) times. Then the report is displayed. Some browsers offer a print option by right-clicking (right mouse button) anywhere in the report. All browsers should allow the report’s text to be copied and pasted into another file using the method typical of the operating system.
Caution
The output file names available via the “Show Files” menu can be somewhat different from the output file names received by the project manager via email. A table cross-walking the file names is provided in Section 11.
7.1.4.7. Send Email¶
Fig. 7.20 Send Email button on the Controls bar¶
Send Email displays a pop-up window with basic controls permitting the project member viewing this page to send emails to members of the project team, including herself or himself, or the OPUS Projects team.
Fig. 7.21 Send Email Message pop-up window¶
Pop-up window controls appear across the top. Below these controls, the email’s recipients can be selected from the project team (either Processors or All Field Members). “Field Members” are the email addresses associated with individual OPUS uploads to the project so there will always be email addresses under the “All Field Members” selection. A subject line can be added in the next text box. The emails can include available OP reports as attachments. These can be selected by using the controls next to the “Attach” box. Finally, there is an entry field for a short text message.
7.1.4.8. Upload Description¶
Fig. 7.22 Upload Description button on the Controls bar¶
Clicking on the Upload Description button opens a pop-up window providing information on the types of description files needed (5 in all). The user is able to navigate to the corresponding files and upload them to the project from this window. Appendix A provides a tutorial for building description files.
Fig. 7.23 Choose WinDesc Description Files for loading into project (pop-up window)¶
Note that description files are only required for user marks observed in the project. Formal descriptions for CORSs are not needed unless the user intends to supersede published values for a particular CORS. In that case, a new description file for that CORS will need to be created and uploaded.
7.1.4.9. Upload GNSS Observation Field Logs¶
Fig. 7.24 Upload Field Logs button on the Controls bar¶
Click on the Upload Field Logs button to select and upload your PDF, Microsoft Word, or ASCII text files (optionally as a single zip file). Field logs do not modify anything within the actual project, but they are required for all occupations if submitting to NGS.
Fig. 7.25 Choose Field Log to upload pop-up window¶
Please refer to the following links for a sample GNSS observation field log and visibility diagram:
GNSS observation field log: https://www.ngs.noaa.gov/RSD/forms/obslog.pdf
GNSS visibility diagram: https://www.ngs.noaa.gov/surveys/forms/visibility.pdf
Additional field forms and information: https://www.ngs.noaa.gov/surveys/forms/
Caution
Although there is no mechanism for you to see that your log files have been loaded, you will only get a response if there is a problem with the load.
7.1.4.10. Refresh PID Information¶
Fig. 7.26 Refresh PID Information button on the Controls bar¶
Permanent Identifiers, or PIDs uniquely identify marks in the NGS database. Clicking the Refresh PID Information button will retrieve the latest information from NGS on user marks with PIDs whose descriptions have already been entered into OP. If the button is pressed but there are no PIDs associated Although there is no mechanism for you to see that your log files have been loaded, you will only get a response if there is a problem with the load.
with any user marks, an error message will be displayed. If there is any differing information between the NGS database and OP (e.g. updated coordinates), the new information will replace what is in OP. This is recommended prior to session processing, to make sure you have the latest (correct) information for the PIDs in your project.
Fig. 7.27 Confirmation or Cancel PID Refresh¶
Caution
Refresh PID Information will only overwrite any original information loaded directly from the datasheets. It will not overwrite information supplied either by the user or OPUS.
Caution
If PID information has changed in the NGS database after the user has conducted session processing and/or adjustments, and the user then refreshed PID information, prior session processing and/or adjustments will disappear.
7.1.4.11. Set up Adjustment¶
Fig. 7.28 Setup Adjustment button on the Controls bar¶
From the Manager’s Page, the Set up Adjustment button will be active if at least one session in the project has already been processed (more on session processing in Section 10). Clicking on the Set up Adjustment button opens an adjustment processing window. If an NGS Project Tracking ID has been associated with the project, five consecutive adjustment steps are identified (without the Tracking ID, this part of the window is blank):
Preliminary
Horizontal free
Horizontal constrained
Vertical free
Vertical constrained
The procedures for running these adjustments are covered in Sections 11 and 12. Note that the adjustments are meant to be sequential, so not all adjustments are available at any given time.
Fig. 7.29 Setup Adjustment Type, Include Available Solutions pop-up window¶
7.1.4.12. Upload Project Report¶
Fig. 7.30 Upload Project Report button on the Controls bar¶
The Upload Project Report button allows the user to load a completed Project Report into the project. The report will not modify anything in the project, but it is a required input for submission to NGS.
7.1.4.13. Review and Submit to IDB¶
Fig. 7.31 Review and Submit to NGS button on the Controls bar¶
The Review and Submit to IDB button runs a set of programs to ensure that all required files are present and that there are no structural errors with the data files to be submitted to NGS. Specifically, the user will be provided a checklist showing the status of all required adjustment steps and uploaded files, and which of these may be missing. The programs CHKOBS and OBSCHK are run, and the output provided (see Section 11 and the Glossary for more information).
7.1.4.14. Delete Project¶
Fig. 7.32 Delete Project button on the Controls bar¶
Clicking the Delete Project button will initiate a three-step process that, if completed, will delete the project from your own manager list of projects. First a confirmation message appears:
Fig. 7.33 Delete Project confirmation pop-up window¶
Cancel will immediately end this process without the project having been deleted.
OK will send an email to the project manager. If the email is ignored, the process is canceled without the project having been deleted. A reply to the email implies consent and the project is deleted. A confirmation email is sent to the project manager.
7.1.5. Marks and Sessions Table¶
The Marks and Sessions table at the lower left of the Manager’s Page shows the list of user marks associated with GNSS observation files that have been loaded into the Project through OPUS (Section 5). The default display includes which marks were observed in each of the project’s sessions (“Occupations” and “All OPUS Results”), and whether the observations met the minimum quality metrics as defined in the user preferences.
OP assigns session names as follows: “yyyy-ddd-X,” where “yyyy” is the four-digit year, “ddd” is the three-digit GPS day of year, and “X” is the individual session within that day. By default, the first session is named “A.” If there are multiple sessions in the same GPS day, the next session will be named “B,” and so on.
Clicking on the Session ID will open the Session Page for that session.
Fig. 7.34 MARKS and Sessions Table showing summary occupation data for all sessions¶
In addition, the user can select from a number of different displays, including “Solution Statistics,” shown below:
Fig. 7.35 Solution Statistics for All Sessions Table that can be displayed on the Manager’s Page¶
The user can also toggle between displaying the table for all OPUS solutions, all sessions, or adjustment results (once sessions have been processed or an adjustment has been made).
7.1.6. Color Coding Marks, CORS and Baselines¶
The Manager’s Page shows all user marks included in the project (upper right-hand corner) as well as all of the CORSs. The icons relate to how the Quality Thresholds were met for user marks. Icons also identify which CORSs were available for each user mark’s solutions. As more data are loaded into the project, more marks, CORS, and sessions will appear.
Fig. 7.36 Symbology for distinguishing between user marks, CORSs, and baselines¶
The user marks are also listed in the OPUS output table below the map, showing the different sessions OPUS generated based on the Session Definition metrics set in the Preferences.
Note that a user mark may meet the Data & Solution Quality Thresholds immediately based on the particular OPUS solution included in the project. A mark that initially did not meet the thresholds may eventually meet them based on subsequent session or network processing. Similarly, a CORS may not meet the project preferences but still be included and used in the project.
Once a session solution completes, the baselines defined in the processing appear on the map. Each session processed will automatically be assigned a different color (e.g. blue, yellow, orange, red). This provides the Manager with an intuitive view of multiple sessions presented on the map display. Similarly, after a network adjustment, the baselines defined in the constituent session solutions of that adjustment will be shown as solid color lines on the map.
7.1.7. MARK and CORS Lists¶
To the right of the map are lists of user marks and included CORSs.
Fig. 7.37 Add Marks and Add/Delete CORS buttons on the Manger’s Page¶
Like the map icons, holding the cursor over a user mark’s ID in the list will cause the icon to brighten, and clicking (typical left mouse button) a mark ID in the list causes that user mark’s information bubble to appear on the map identifying its location.
Below the user marks list to the right of the map is the Add MARKS button. This button acts as a link to redirect the user to the OPUS Upload web page where more GNSS observations on user marks may be added.
Fig. 7.38 Reminder pop-up window for uploading observation files to the project through the OPUS upload page¶
Tip
Using the “Add CORS” feature while on the Manager’s Page assures that the CORSs selected will be used in every session
Below the CORS list, at the bottom right of the map, is the button. Clicking this button opens a new popup window with controls to add additional CORS to all sessions in the project. The map appearing in the Add/Del CORS window is similar to the map on the Manager’s Page. You may zoom in and out and drag the map to other areas. Notice the icons are color coded to reflect how long they have existed as a CORS. As you zoom in to the map notice that the sites that have been operational for shorter periods of time begin to appear. In stable areas of the country, the longer a CORS has been in operation, the better estimate of its velocity, and the greater the expectation that the CORS data will overlap with your project. Guidelines for selecting CORSs are presented in Section 9.
Fig. 7.39 The Add/Del CORS management pop-up window¶
Move the cursor over the CORS icon to see the CORS ID. Clicking on the icon gives you the option (within the information bubble) to check the CORS site log as well as the data availability. You can also add that particular station to a list on the left side of the window. When you have completed adding CORS to that list, click the Add/Del Cors button at the top of the web page to populate the project with those additional stations.
Caution
If you add CORSs after a given session has been processed (see “Session Processing,” Section 7.2, below), you will have to re-process that session again.
7.1.8. Email the OPUS Projects Team¶
At the bottom of the Manager’s, Session and Marks web pages, an email link to the OPUS Projects Team always appears providing a convenient method to ask questions or make comments. The project manager may receive more than one reply from NGS staff depending on the subject of the email.
Fig. 7.40 Submitting Comments to & Asking Questions of the OPUS team¶