1 / 9

NGS Leveling Adjustment Course

NGS Leveling Adjustment Course. Module 4: Generating the files needed for loading. Course requirements: VPN (for remote access) UNIX emulator (e.g. PuTTY ) User profile with access to IDB and leveling menus FileZilla to transfer files from UNIX to PC (and back). Outline.

havard
Télécharger la présentation

NGS Leveling Adjustment Course

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NGS Leveling Adjustment Course Module 4: Generating the files needed for loading • Course requirements: • VPN (for remote access) • UNIX emulator (e.g. PuTTY) • User profile with access to IDB and leveling menus • FileZilla to transfer files from UNIX to PC (and back)

  2. Outline • Output from adjustment • Generating HOW_GOOD.BMS • Generating HOW_GOOD.UID • Removing duplicate UIDs • File naming conventions • Files required for loading

  3. Output from adjustment • In your Results folder (in UNIX), you should have: • CONSTRAINTS.report • lines file • L****.r6adj files • L****.rpt files (*.rpt files generated in main project directory, menu_v, #10 – reptgen)

  4. Generating HOW_GOOD.BMS • Create one file that lists all the *.r6adj file names in your adjustment • In your results directory, type: ls *.r6adj > adjfiles (adjfiles is suggested: call this anything you want) • This is similar to your “lines” file in that it contains a list of file names (in this case, the *.r6adj file names) • Check successful listing using command wcadjfiles (the number of lines reported back to you should match the number of l-number files you are adjusting) –otherwise review file in vi Editor (vi adjfiles)

  5. Generating HOW_GOOD.BMS • Create the HOW_GOOD.BMS file • menu6 r6tohgr (#9)  adjfiles • <Enter> • Adjusted r6 FILES  HGR Estimates (YES) • SELECT YOUR ADJUSTMENT DATUM: 1) 88 NAVD • PROCESS ONE FILE (YES) • NAME OF FILE (adjfiles) • PROCESS THE FILE of… CONSTRAINTS (YES) • NAME of FILE (indicate name of CONSTRAINTS file and directions to its directory, e.g. ../CONSTRAINTS) • Q = Quit

  6. Generating HOW_GOOD.BMS • View HOW_GOOD.BMS (e.g. vi Editor) Ortho. Height (m) PIDs Lat/Longs Vert. Datum SE Grav ssn’s Designation SE Height (mm) Gravity “A” = Adjusted

  7. Assigning UIDs • View HOW_GOOD.BMS (e.g. vi Editor) • Once you have the HOW_GOOD.BMS, type the command UIDs (in same directory as HOW_GOOD.BMS) • This creates the HOW_GOOD.UID file • Inspect file in vi Editor, or use more command • You will also need to set the vertical order of the level lines: • set_vorder HOW_GOOD.UID • Note: this assumes all O/C are the same. If not, it is recommended to set up different folders for each O/C and repeat ALL the steps for each. • Finally, combine all HOW_GOOD.UIDs into one file for loading

  8. Combining all HOW_GOOD.UID files • Create one overall HOW_GOOD_XX.UID • (“XX” stands for State code, e.g. TX, AL, MS, etc.) • cat HOW_GOOD_11.UID >> HOW_GOOD_XX.UID • cat HOW_GOOD_12.UID >> HOW_GOOD_XX.UID • Etc. Need to check w/ Vasanthi regarding naming conventions – may require name of job rather than state.

  9. Check for duplicate PIDs • Export HOW_GOOD_XX.UID to Excel • Sort on PIDs, check for duplicate entries. • Eliminate duplicates • Have someone review results of adjustment before submitting to Vasanthi • Submit to Vasanthi (check for exactly which files are needed; she has her own file structure that we need to follow)

More Related