MicroSurvey-StarNet-7-PRO-Manual.pdf

MicroSurvey

STAR*NETLeast Squares Survey Adjustment Package

Reference Manual

Professional Edition Supplement

v 6.0.42.1 (7/6/2011)

Copyright © 2011 MicroSurvey Software Inc.All Rights Reserved

MicroSurvey End-User License Agreement

- i -

MICROSURVEY END-USER LICENSE AGREEMENTThisMicroSurveyEnd-User License Agreement ("Agreement") is a legal and binding agreement between you ("Licensee") andMicroSurveySoftwareInc., a BC corporation ("MICROSURVEY") concerning the use of theMicroSurveyproducts (the "Product"), the software provided in connection with theuse and operation of the Product, including firmware and storedmeasurement data (collectively the "Software") and all related documentation providedin connection with the acquisition of the Product ("Documentation"). The Software includes software owned by, and licensed from, third party licensors.

By clicking the "I ACCEPT" checkboxand completing the processof installing the Software, LICENSEE consents to and agrees to be bound byall of thetermsand conditionsof thisAgreement. BYCLICKINGTHE "I DO NOT ACCEPT"CHECKBOXor IF LICENSEEdisagreeswith anyof the termsor con-ditionsof thisAgreement, LICENSEE IS not permitted to install and/or use the Software, PRODUCT AND DOCUMENTATION. IF LICENSEEHASANYquestionsOR COMMENTSCONCERNINGTHISAGREEMENT LICENSEEMAYCONTACT MICROSURVEYATWestbank, BC Canada.

1. Title to Product and Rights to Use Software and Documentation. Title to the Product and the rights to use the Software and Doc-umentation are conditioned upon the payment of the required purchase price and anyapplicable license andmaintenance feesand Licensee'sacceptance of the termsand conditionsof thisAgreement.

2. License.

1. License Grant. MICROSURVEYherebygrants Licensee a nonexclusive, non-transferable, non-sublicensable right to (i) install anduse one copyof the Software and Documentation on the Product and one copy for use on nomore than one personal computer simul-taneously, and , (ii) to access the storedmeasurement data generated by the Software, for Licensee's own internal businesspurposesand in accordance with the termsand conditionsof thisAgreement. MICROSURVEYalso herebygrants Licensee a nonexclusive, non-sublicensable right to reproduce the Documentation, solely asnecessary for Licensee's internal use of the Product and Software.

2. Conditions and Restrictions. The following conditionsand restrictionsapply to the use of the Product, Software and Documentation:

i. Licensee shall not, and shall not attempt to, reverse engineer, decompile, disassemble or otherwise attempt to identify thesource code of anyobject code portionsof, distribute, modify, encrypt, or create derivative worksof the Software, Doc-umentation, and/or any storedmeasurement data in whole or in part, including, but not limited to, storedmeasurement data.

ii. Licensee shall not use the Software or Documentation for anypurpose not expressly permitted by thisAgreement.

iii. Licensee shall not copyanypart of the Software, except that Licenseemaymake one copyof the Software for backup purposesonly.

iv. Licensee agreesnot to remove or destroyany copyright, logo, trademark, trade name, proprietarymarkings, or confidentialitylegendsplaced upon or contained within the Software or Documentation. Licensee shall not, and agree not to assist others to,circumvent or disable the license provisioning technology for the Software.

v. Licensee's license to the Software under thisAgreement continuesuntil it is terminated byLicensee or MICROSURVEY.Licenseemay terminate the license bydiscontinuing use of all or anyof the Software and bydestroying all Licensee copiesof theSoftware and Documentation.

vi. ThisAgreement will terminate automatically if (x) Licensee violate anyof the termsor conditionsof thisAgreement, (y) MICRO-SURVEYpublicly posts a written notice of termination on itswebsite www.microsurvey.com (that, or any successor site, the"Site"); or (z) MICROSURVEY revokes thisAgreement or issuesa new agreement in writing or electronic form and conditionsLicensee continued use of the Software upon acceptance of the new agreement.

3. Ownership.All rights, title and interest in and to the Software and Documentation including, without limitation, all copyright, patent, trade secretand other intellectual property rights shall at all times remain the property of MICROSURVEY, it licensors, or its suppliers, as applicable. The Soft-ware and Documentation are licensed, not sold, and are protected by copyright and other intellectual property lawsand treaties. Licensee shalltake appropriate steps reasonably calculated to notify others of MICROSURVEYand its licensor's/suppliers' ownership of the Software and Doc-umentation.

4. Warranty.MICROSURVEYwarrants that the Product will, for 90 daysafter the Effective Date (the "WarrantyPeriod"), substantially conform tothe Documentation; provided, that Licenseemust notifyMICROSURVEY in writing of anybreach of the foregoing warrantywithin theWarrantyPeriod. For anybreach of the foregoing warranty reported during theWarrantyPeriod, MICROSURVEYwill use reasonable efforts to promptlycorrect such defect without further charge. If MICROSURVEY is unable to correct such defect, thenMICROSURVEYwill refund the license feespaid for the Product. This representsMICROSURVEY'S exclusive liability and Licensee's sole and exclusive remedy in the event of a breach ofthe foregoing warranty.

5. Warranty Disclaimer.EXCEPT ASDESCRIBED IN SECTION 4 (WARRANTY), MICROSURVEYHEREBYDISCLAIMSALLWARRANTIESRELATINGTOTHEPRODUCT, SOFTWARE, AND DOCUMENTATION, INCLUDINGWITHOUT LIMITATION THE IMPLIEDWAR-RANTIESOF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESSFOR APARTICULAR PURPOSE.MICROSURVEYDOESNOT

MicroSurvey STAR*NET-PROReferenceManual

- ii -

REPRESENT THAT THEOPERATIONOF THEPRODUCT AND/OR SOFTWAREWILL BEUNINTERRUPTEDOR ERROR-FREE.WITH-OUT LIMITINGTHEGENERALITYOF THEFOREGOING,MICROSURVEYMAKESNOWARRANTYTHAT: (A) OPERATIONOF THEPRODUCT AND/OR SOFTWAREWILL BEUNINTERRUPTEDOR ERROR-FREE, (B) THEPRODUCT AND/OR SOFTWAREWILLMEETLICENSEESPECIFIC NEEDS, (C) SPECIFIC RESULTSWILL BEACHIEVEDWITH THEPRODUCT AND/OR SOFTWARE, OR (D) ALLERRORSOR FAILURESWILL BECORRECTED. IN NOEVENT SHALLMICROSURVEY'S, ITS LICENSORS', OR ITSSUPPLIERS' LIA-BILITYTOLICENSEEFOR THEPRODUCT AND/OR SOFTWARE,WHETHER BASEDONCONTRACT, TORT,WARRANTY, OR ANYOTHER LEGAL THEORY, EXCEED THEAMOUNT OF PURCHASEPRICEPAID FOR THEPRODUCT AND ANYRELATED LICENSEORMAINTENANCEFEESPAID BYLICENSEE.

6. Exclusion of Damages. TOTHEMAXIMUMEXTENT PERMITTED BYAPPLICABLELAW, IN NOEVENT SHALLMICROSURVEY, ITSLICENSORS, OR ITSSUPPLIERSBELIABLEFOR ANYSPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIALDAM-AGESWHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGESFOR LOSSOF PROFITSOROTHER DATAOR INFORMATION,OR FOR BUSINESS INTERRUPTION) ARISINGOUT OF OR IN ANYWAYRELATED TOTHEUSEOF OR INABILITYTOUSETHEPROD-UCT AND/OR SOFTWARE, EVEN IN THEEVENT OF THEFAULT, TORT (INCLUDINGNEGLIGENCE), STRICT LIABILITY, BREACHOFCONTRACT OR BREACHOFWARRANTYOF MICROSURVEY, ITS LICENSORSOR ANYSUPPLIERS, AND EVEN IF MICROSURVEYOR ANYof ITS LICENSORSOR SUPPLIERSHAVEBEEN ADVISEDOF THEPOSSIBILITYOF SUCHDAMAGES. BECAUSESOMEJURIS-DICTIONSDONOT ALLOWTHEEXCLUSIONOR LIMITATIONOF LIABILITYFOR CONSEQUENTIALOR INCIDENTALDAMAGES, THEABOVELIMITATIONMAYNOT APPLYTOLICENSEE.

7. Limitation of Liability.NOTWITHSTANDINGANYDAMAGESTHAT LICENSEEMIGHT INCUR FOR ANYREASONWHATSOEVER(INCLUDING,WITHOUT LIMITATION, ALL DAMAGESREFERENCED ABOVEAND ALLDIRECT ORGENERALDAMAGES), THEENTIRELIABILITYOF MICROSURVEYAND ANYOF ITS LICENSORSOR SUPPLIERSUNDER ANYPROVISIONOF THISAGREEMENTAND LICENSEEEXCLUSIVEREMEDYFOR ALLOF THEFOREGOINGSHALL BELIMITED TOTHEAMOUNT ACTUALLYPAID BYLICENSEEFOR THEPRODUCT AND ANYRELATED LICENSEORMAINTENANCEFEESPAID BYLICENSEE. THEFOREGOINGLIM-ITATIONS, EXCLUSIONSAND DISCLAIMERS (INCLUDINGSECTIONS5 AND 6ABOVE) SHALL APPLYTOTHEMAXIMUMEXTENTPERMITTED BYAPPLICABLELAW, EVEN IF ANYREMEDYFAILS ITSESSENTIAL PURPOSE. LICENSEEACKNOWLEDGESTHAT (A)THEPROVISIONOF THEPRODUCT AND SOFTWARE ISCONDITIONALUPONMICROSURVEYEXCLUDINGAND/OR LIMITING ITSAND ITS LICENSORS' AND SUPPLIERS' LIABILITYTOLICENSEE IN ACCORDANCEWITH THISAGREEMENT, AND (B) THEEXCLU-SIONSAND LIMITATION CONTAINED IN THISAGREEMENT AREFAIR AND REASONABLE IN ALL THECIRCUMSTANCESKNOWNATTHEDATEOF THISAGREEMENT.

8. Indemnification. Licensee agrees to defend, indemnify and holdMICROSURVEY, its affiliates, distributors, licensors, and suppliers harmlessfrom and against anyand all losses, damages, costs or expenses (including reasonable attorney's fees) (a) suffered byLicensee related in anyway to the Product, Software, or thisAgreement and/or (b) related to any claim or demandmade byany third party in connection with or arisingout of (i) anybreach byLicensee of anyof the termsand conditionsof thisAgreement, (ii) Licensee use or misuse of the Product or Software, (iii)Licensee violation of applicable laws, and/or (iv) Licensee violation of the rights of anyother person or entity. MICROSURVEY reserves the right,at its own expense, to assume the exclusive defense and control of (but not liability for) anymatter otherwise subject to indemnification byLicensee. Licensee will be liable toMICROSURVEY for reasonable attorney's fees in any such case.

9. Support.

a. General.Except as set forth in Section 9(b) (Website Support) and 9(c) (Contract Support), MICROSURVEYshall have no obligationunder thisAgreement to maintain or support the Software. Licenseemaycontact MICROSURVEY to inquire about MICROSURVEY'Scommercially available support andmaintenance servicesprovided pursuant to separate agreements. ThisAgreement shall not obli-gate either party to enter into any such separate agreement. Anyupdatesor error corrections to the Software that maybe provided toLicensee from time-to-time, if any, shall be deemed Software hereunder and shall be licensed to Licensee under the termsand con-ditionsof thisAgreement. If any such updatesor error correctionsaremade available to Licensee, then Licensee shall promptly (a) imple-ment such updatesor error corrections, (b) cease using the earlier versionswithout such updatesor error corrections, and (c) makesuch updatesor error correctionsavailable to the users of the earlier versions. Licensee shall be solely responsible for procuring all hard-ware and third-party software necessary to operate the Software.

b. Website Support.MICROSURVEYwill use reasonable commercial efforts to host andmaintain a web site (the "Support Site") for theSoftware during its commercial life (as reasonably determined byMICROSURVEY) that will include some or all of the following features:

l A "FrequentlyAskedQuestions" section with answers to common questionsabout the Software.

l A searchable "Helpdesk" section with general user instructionsand information about the Software.

l A link to allow end users of the Software to download anybug fixes, error correctionsor other updates to the Software thatMICROSURVEYmaymake available through the Site.

MicroSurvey End-User License Agreement

- iii -

l "Contact MICROSURVEY" electronic response capability. MICROSURVEYwill use reasonable commercial efforts to respondwithin two (2) businessdays to a customer inquiry received via this system. Answers to such inquireswill be added to the FAQ's,as appropriate.

c. Contract Support.Uponmutual agreement in writing between Licensee andMICROSURVEY, or between Licensee and one ofMICROSURVEY'S authorized reseller's, MICROSURVEYwill provide contracted support services to Licensee asmaybe agreed uponand related to the Software.

10. Term and Termination.

a. ThisAgreement is effective until terminated. Licenseemay terminate thisAgreement at any time, with or without cause, upon notice toMICROSURVEY.MICROSURVEYmay terminate thisAgreement for Licensee's breach of thisAgreement.

b. Upon termination of thisAgreement, Licensee shall immediately cease all use of the Software and Documentation and return toMICRO-SURVEYall copiesof thereof within five (5) daysafter such termination. UponMICROSURVEY'S request, Licensee will certify in writingtoMICROSURVEY that all such copieshave been returned toMICROSURVEY. The following provisionsof thisAgreement shall survivetermination or expiration of thisAgreement: Sections2(b) (Restrictions), 3 (Ownership), 5 (WarrantyDisclaimer), 6 (Exclusion of Dam-ages), 7 (Limitation of Liability), 10 (Term and Termination), and 11 (General).

11. General.

a. Assignment.MICROSURVEYmayassign thisAgreement without notice to Licensee. Licensee shall not assign thisAgreement ortransfer anyof the rights, duties, or obligationsarising under thisAgreement without the prior written consent of MICROSURVEY. ThisAgreement shall be binding upon, and inure to the benefit of, the permitted successors and assignsof the parties thereto.

b. Amendments;Modifications. Noticesof changes to thisAgreement or other mattersmaybemade to Licensee bydisplaying noticesorlinks to notices to Licensee generally on the Site.

c. Governing Law; Forum; Attorney'sFees, Injunctive Relief. The termsof thisAgreement shall be construed and governed exclusivelyby the lawsof the province of British Columbia, excluding the application of its conflict of law provisionsand rules. Anydispute, con-troversyor claim between the parties arising out of or relating to thisAgreement or a breach of thisAgreement shall be settled pursuantto the termsof thisSection 11(c) byarbitration before three neutral arbitrators (selected from a panel of personshaving experience withand knowledge of the computer business), provided at least one of which arbitrators shall be an attorney, and administered by the Arbi-tratorsAssociation of British Columbia in accordance with itsCommercial Arbitration Rules in Kelowna, British Columbia. Anyprovisionalor equitable remedywhich would be available from a court of law shall be available from the arbitrators to the parties. Judgment uponthe award of the arbitratorsmaybe enforced in any court having jurisdiction thereof. The parties hereby consent to the non-exclusivejurisdiction of the courts of the Province of British Columbia for anyaction (i) to compel arbitration, (ii) to enforce the award of the arbi-trators or (iii) prior to the appointment and confirmation of the arbitrators, for temporary, interim or provisional equitable remedies, andto service of process in any such action by registeredmail, return receipt requested, or byanyother meansprovided by law. The appli-cation of the United NationsConvention of Contracts for the InternationalSale of Goods is expressly excluded.

d. Severability. The illegality, invalidity or unenforceability of one or more provisionsof thisAgreement shall not affect the legality, validityor enforceability of anyother provision, and thisAgreement shall be construed in all respects as if such illegal, invalid or unenforceableprovision were deemed amended to achieve asnear aspossible the same economiceffect as the original in a legal, valid and enforce-ablemanner if possible.

e. Further Relationships.Neither party is obligated by thisAgreement to enter into any further business relationship after the ter-mination or expiration of thisAgreement.

f. Notices.All noticesunder thisAgreement shall be in writing, and shall be deemed given when personally delivered, when received if bynationally recognized courier, or three daysafter being sent bypostage prepaid, certified or registered CanadianMail, as applicable, toMICROSURVEYatMICROSURVEY's addressas set forth herein or to Licensee at the address that Licensee provided upon enteringinto thisAgreement, or such other addressasa party last provided to the other bywritten notice.

g. Independent Contractor.MICROSURVEYand Licensee are independent contractors. No partnership, joint venture, or other jointrelationship is created by thisAgreement.

h. Entire Agreement. ThisAgreement represents the entire agreement between the parties relating to its subject matter and supersedesall prior representations, discussions, negotiationsand agreements. All changes, modifications, additionsor deletions shall be effectiveimmediately upon notice thereof, whichmaybe given bymeans including, but not limited to, posting on the Site, or byelectronic or con-ventionalmail, or byanyother meansbywhich Licenseemayobtain notice thereof. Use of the Product and/or Software after such noticeconstitutesacceptance of such changes, modificationsor additions. ThisAgreement maybe amended at any time bymutual agreementof the parties.


- iv -

MICROSURVEY TECHNICAL SUPPORTMicroSurvey Software Technical Support is available to help you get themost out of your MicroSurvey product. The followinginformation explains how to prepare for your call so that your inquiry can be answered promptly and accurately.

Please prepare yourself before you call for Technical Support

Take a few minutes before you place your call to check the printed documentation and the online help files to see if the answeris already at your disposal. OurWeb site on the Internet can also save time. Please check it for assistance if you can. Pleasehave the following information available if requested: version of the program, operating system version and architecture, andyour Technical Support Number.

Pleasemake sure that you have all the steps you completed prior to your problem and can explain them to the technical sup-port representative. Wemay ask that you forward a copy of your data to us if we cannot find the problem immediately.

MicroSurvey offers a 90-day complimentary support period to all of our registered users, starting the date of purchase. Intro-ductory support is available weekdays between 8:00 am and 5:00 pm (Pacific Time) excluding holidays.

Yearly Support

For clients who have had their original 90-day complimentary support period expire and feel that they will need on going supportover the next year, we have a Yearly Support Contact option available. This gives you the ability to contact us for technical sup-port, as much as you require, and you pay a flat fee once a year. This option is not to be used in place of training but is to assistyou on the occasions when you really need it. The charge for the Yearly Support Contract is to be billed and paid for prior to thesupport commencing. This rate is subject to change, call for current rates.

Electronic Support

MicroSurvey maintains and provides at no charge, our Internet Web site at www.microsurvey.com

This web site has sections on frequently asked questions, Technical Notes, Technical Specifications, and as required, freeupdates and program fixes, along with a lot of other helpful information.

Training

MicroSurvey Software Inc. can provide training to you, in your office or in a classroom situation (where facilities and numbersallow. MicroSurvey has training staff that will travel to almost anywhere and provide you with the professional skills you requireto operate your MicroSurvey program. Please feel free to call and ask for a quotation or inquire about potential classroom sit-uations. Your local dealer may also be able to setup or arrange a training session for you. Contact our head office for more infor-mation about training.

http://www.microsurvey.com/helpdesk

MicroSurvey Contact Information

- v -

MICROSURVEY CONTACT INFORMATIONInternet

CorporateWebsite: www.microsurvey.comTechnical Support Helpdesk: www.microsurvey.com/helpdeskGeneral Information E-Mail: [email protected]

Telephone

Phone (Toll Free): 1-800-668-3312Phone (International): 1-250-707-0000Fax: 1-250-707-0150

8:00 am to 5:00 pm (Pacific Time)(Monday to Friday, except holidays)

Mailing Address

MicroSurvey Software Inc.205 - 3500 Carrington RoadWest Kelowna, BC V4T 3C1Canada

http://www.microsurvey.com/

http://www.microsurvey.com/helpdesk

mailto:[email protected]


- vi -

TABLE OF CONTENTSMicroSurvey End-User License Agreement i

MicroSurvey Technical Support iv

MicroSurvey Contact Information v

Table of Contents vi

Chapter 1: OVERVIEW 1

Chapter 2: USING STAR*NET-PRO 3

2.1 Overview 3

2.2 Setting GPS-Related Project Options 3

2.3 Import GPS Vectors 3

2.4 Description of Imported GPS Vector Data 4

2.5 Factoring the Supplied GPS Vector Standard Errors 5

2.6 Elevations and Ellipsoid Heights 5

2.7 Solving for Transformations 6

Minimally-Constrained Networks 6

Fully-Constrained Networks 7

General Notes About Constraining Your Network 7

2.8 Notes About Running Preanalysis 8

Chapter 3: GPS OPTIONS 9

3.1 Overview 9

3.2 GPS Options 10

3.3 Inline Options Relating to GPS Vector Data 15

Inline Option .GPS DEFAULT [ stderr ppm [ VERTICAL stderr ppm ] | FREE | IGNORE ] 15

Inline Option .GPS FACTOR [ factor [ VERTICAL factor ] | FREE | IGNORE ] 16

Inline Option .GPS USE [ stderr ppm [ VERTICAL stderr ppm ] | FREE | OFF ] 17

Inline Option .GPS CENTERING [ value [ VERTICAL value ] ] 19

Inline Option .GPS { IGNORE | FREE } vectors 20

Inline Option .GPS ADDHIHT [ HI HT ] 20

Inline Option .GPS { NETWORK | SS } 21

Inline Option .BASE PointName [ AntennaHeight ] 22

Chapter 4: IMPORTING GPS VECTORS 25

Table of Contents

- vii -

4.1 Overview 25

4.2 Using the GPS Importer 26

4.3 General Notes on Importing Vectors 29

4.4 Importing from Selected Baseline File Formats 29

4.5 Special Leica Descriptor Extraction Options 33

4.6 OPUS Stations 33

Inline Option: .OPUS { FACTOR | CENTERING } [ number [ VERTICAL number ] ] 35

Chapter 5: GEOID HEIGHTS AND VERTICAL DEFLECTIONS 39

5.1 Overview 39

5.2 The “GH” and “GT” Data Type Lines 39

5.3Modeling Options 40

GeoidModeling 40

Vertical DeflectionModeling 41

5.4 Using the StarGeoid Utility Program 43

Using StarGeoid to Create “GHT” Geoid Height Files 44

Using StarGeoid to Create “VDF” Vertical Deflection Files 44

5.5 GeoidModel Data 45

United States NGS Geoid and DeflectionModel Data 45

Canadian GeoidModel Data 46

World GeoidModel Data 46

Chapter 6: GPS OUTPUT LISTING SECTIONS 49

6.1 Overview 49

6.2 Summary of Unadjusted Input Observations 49

6.3 Statistical Summary 50

6.4 Adjusted Observations and Residuals 51

6.5 Vector Residual Summary 52

6.6 Results of GeoidModeling 53

Appendix A: TOUR OF THE STAR*NET-PRO PACKAGE 55

Overview 55

0.1 Example 8: Simple GPS Network 56

0.2 Example 9: Combining Conventional Observations andGPS 64

Index 69


- viii -

Chapter 1: OVERVIEW

- 1 -

CHAPTER 1: OVERVIEWSTAR*NET-PRO, the professional edition of STAR*NET, includes:

l All the features of the STAR*NET-PLUS edition.

l The ability to import GPS vectors frommost popular baseline file formats.

l Handling of GPS vectors in adjustments, either alone or combined with conventional terrestrial observations and dif-ferential leveling observations.

l The ability to manually enter Geoid Height and Vertical Deflection values for individual stations.

l The ability to perform Geoid Height modeling and Vertical Deflectionmodeling during an adjustment.

Themain STAR*NETmanual describes the installation of the software, and the basic information required for its operation.This supplement describes the GPS aspects of the program such as data types, options and its operation. It also describesuse of the geoidmodeling facility. It is essential that you become completely familiar with both themain STAR*NETmanualand this supplement manual before attempting adjustments of projects which includeGPS vectors.

Just as with the adjustment of conventional observations, STAR*NET-PRO adjusts GPS vector observations right “on-the-plane.” During each adjustment iteration, conversions aremade between the earth-centered Cartesian coordinate system andyour grid system so that residuals can be calculated for the vectors and proper corrections can be applied to the stations. Thisallows conventional observations andGPS vectors to be combined in a very natural way. But this alsomeans that all stationsin your project must be somewhat localized so they relate to a single grid system. For example, in the United States and Can-ada, projects are run using a single NAD83, NAD27 or UTM zone. Jobs are not handled that span several zones.

A GPS vector importer built into the program extracts baseline vectors and their weighting from several popular formats. Vec-tors are imported into standard text files whichmay be easily edited and included with the adjustment.

Options relating to GPS vectors and processing are set in the GPS section of the Project Options dialog. In addition, certainoption settings which youmight want to change anywhere in the vector data (such as factoring vector standard errors and appli-cation of centering errors for special situations) may be entered as “inline” options to give you complete control.

If your network is fully constrained, STAR*NET-PRO can solve for transformations consisting of a scale and three rotations.When working on a datum other than theWGS84 (or NAD83) native to GPS, this transformation facility allows you solve yournetwork directly on that grid system.

When you install the STAR*NET program as described in Chapter 2 of themainmanual, the software installed contains all thefeatures of both the standard edition and the professional edition. The security key issued to you enables the features of thestandard edition or the high-end professional edition depending on which program you purchased. The program will also runwithout the security key attached, but it will run in as a “Professional Edition” demowhich handles 10 adjustable stations, manyconventional observations and 15GPS vectors. Users running the standard edition can experiment with using the professionaledition.

During installation, data files for several example projects including twoGPS related tutorials are copied to your computer. Thefirst tutorial is in Appendix-A of themain STAR*NETmanual, and the second in Appendix-A of this professional edition sup-plement manual. These examples are located on a subdirectory of your My Documents directory named “Micro-Survey\StarNet\Examples.”

We strongly encourage you to complete the following two steps before reviewing the remainder of this manual in detail:


- 2 -

1. Run the Tutorial in themain STAR*NETManual, Appendix-A.

If you are a new user to the STAR*NET program we suggest that you run the complete tutorial. This will introduce you tothe operation of the program and walk you through the use of all menus. The tutorial illustrates the adjustment of severalnetworks using conventional observations.

2. Run theGPS Tutorial in this STAR*NET-PROSupplement, Appendix-A.

This will give you a chance to review the use of the GPS-related options dialogs, import a few GPS baseline vectors andgain some experience with the program by running an actual adjustment containing vectors. The second sample projectin this tutorial combines a few conventional observations with GPS vectors.

The next chapter, “Using STAR*NET-PRO” is an overview of the steps you will go through when preparing data and adjusting aproject containing GPS vectors.

The remaining chapters discuss in detail project options relating to GPS vectors, importing of vectors from baseline files, geoidmodeling, and additional output listing sections which relate to GPS vectors.

Chapter 2: USINGSTAR*NET-PRO

- 3 -

CHAPTER 2: USING STAR*NET-PRO2.1 OVERVIEWThe list below shows the sequence of tasks you will generally follow when creating a project and performing adjustments withthe STAR*NET-PRO program:

l Open a new project.

l Set options describing your project and conventional observations.

l Set GPS-related options.

l Create one or more input data files containing control points and observations.

l Import GPS vectors which adds one or more data files to the project.

l Run the adjustment.

l If errors or warnings were found, check the error listing for specific details.

l Edit your input data files to correct any errors found.

l Rerun the adjustment until there are no errors or warnings.

l Display the network graphically on your screen.

l Review the output listing.

l Repeat the edit-run-review cycle as needed to get satisfactory results.

l Print output listing, coordinate information and plot diagrams.

This sequence is identical to that shown in the Chapter 3, “Using STAR*NET,” of themainmanual, except for the two addi-tional steps shown below.

2.2 SETTING GPS-RELATED PROJECT OPTIONSChooseOptions>Project Options, or press the Project Options tool button. Besides dialogs discussed in themainmanual,GPS andModeling options, are available in the professional edition to set GPS-related options.

See Chapter 3, “GPS Options” in this supplement for complete details.

2.3 IMPORT GPS VECTORSChoose Input>Import GPS Vectors to import GPS vectors from a variety of baseline formats. These vectors are written to astandard text file just like data for conventional observations described in themainmanual. This file is shown in the Data FilesList dialog and it can be viewed or edited just like any other data file shown in the list.

See Chapter 4, “Importing GPS Vectors” in this supplement for complete details.

The remainder of this chapter discusses general GPS-related information including a description vector format plus someissues relating to GPS adjustments.


- 4 -

2.4 DESCRIPTION OF IMPORTED GPS VECTOR DATAData for a GPS project is very simple and consists mainly of vectors and weighting information imported by the GPS Vectorimporter. See Chapter 4 in this supplement for a complete set of instructions for importing vectors.

An imported GPS vector consists of four lines, each beginning with a “G” character. TheG0 (G-Zero) line contains vector iden-tification, the G1 line contains the station names and the earth-centered DX, DY and DZ vector components, and the G2 andG3 lines contain the weighting. The weighting information will be either standard errors and correlations, or covariances depend-ing on the origin of the baseline vectors. If weighting is not supplied, the G2 andG3 lines will not be present.

If the weighting is in the form of covariances, Trimble and Leica vectors for example, the lines will contain this information:

G1 From-To DX DY DZ (vector components)G2 CvXX CvYY CvZZ (vector covariances)G3 CvXY CvXZ CvYZ (vector covariances)

Or if the weighting information is in the form of standard errors and correlations, Ashtech vectors for example, the G1, G2 andG3 lines will contain this information:

G1 From-To DX DY DZ (vector components)G2 SDX SDY SDZ (vector standard errors)G3 CrXY CrXZ CrYZ (vector correlations)

The following shows data for twoGPS vectors imported from Trimble SSF files. The inline “.GPSWEIGHT” option precedingthe vectors indicates that the following weighting information is supplied as covariances. The option line would include the keyword “STDERRCORR” if the weighting were supplied as standard errors and correlations. This data line is automatically addedby the GPS Vector Importer so you never have to be concerned about hand-entering it.

.GPS WEIGHT COVARIANCEG0 'V532 Day134(3) 01:15 12346643.SSFG1 0036-0040 4861.328134 -348.097034 2463.249801G2 4.35804625082312E-008 2.00368296412947E-007 1.23348139662277E-007G3 1.29776877121456E-008 -4.73073036591065E-009 -7.87018453390485E-008

G0 'V533 Day134(3) 01:15 12346333.SSFG1 0035-0040 2064.545306 837.615578 2476.161963G2 6.79408614714407E-008 3.19044736655059E-007 2.03723479067936E-007G3 2.52277334566666E-008 -6.54246971775426E-010 -1.41369343650741E-007

The “G0” line contains vector identifier text beginning with a single quote (') character. This identifier text contains a vectorserial number plus any other information whichmight help identify the vector such as day of year, session, time of observationand source file name. For example, the descriptor for the first vector above indicates serial number 532, day of year 134, ses-sion 3, time of observation 01:15 and the file name.

A vector file created from another manufacturer’s baselines might contain somewhat different information. For example, theidentifier text may include just the serial number and source file name.


- 5 -

The “G0” identifier lines are not actually required for an adjustment to run. However when present, the identifiers are includedwith all listings of the vectors in the output helping you tomatch output (residuals, etc.) to particular input vectors.

Imported vector information supplied onG1, G2 andG3 data lines will always be inMeters whether or not the project is setup torun inMeters. When the project is setup to run in other linear units, for example FeetUS, vector information is automatically con-verted to project units for calculations and output in the listing file.

When vector component weights are supplied as covariances (as shown in the example), they are internally converted bySTAR*NET-PRO to standard errors and correlations. In addition, the vectors and their standard errors are rotated to local-hori-zon north, east and up components which offers muchmore understandable output. This rotation also allows you to inde-pendently apply factoring and centering errors to the horizontal and vertical standard error components. See Chapter 3, “GPSOptions,” in this supplement for details on factoring and centering options as well as an option to that allows you to specifydefault vector standard errors whenG2 andG3weighting lines are not supplied.

2.5 FACTORING THE SUPPLIED GPS VECTOR STANDARD ERRORSAs described in the previous section, when you import GPS vectors, you usually also get weighting information. STAR*NET-PRO shows this weighting as standard errors. Standard errors reported by most manufacturer’s baseline processors, however,are often overly-optimistic, and to change these standard errors to real-world values, you will need to factor them by somevalue. To do this, you can set a default factor in the GPS options dialog. In addition, a special “.GPS FACTOR” inline optionmay be inserted in your vector data to control factoring of different parts of your vector data when required. See Chapter 3,“GPS Options,” in this supplement for details on setting these factors.

How do you determine a proper factor? There is no definitive answer to this question except to say that youmust determine fac-tors based on your own experience. The factor will depend on the equipment you are using (single or dual frequency), the kindof GPS survey being performed (static, RTK, etc.) and the care taken by your field crew. If your equipment is properly cal-ibrated and you have removed all blunders, the factor you apply should cause the “Total Error Factor” for an adjustment to comeout to approximately 1. This means that your residuals are coming out approximately equal to your standard errors - your expec-tation.

We hear of factors being used anywhere between 1 and 30. Therefore, if after experience with several projects, you determinethat a typical “static” survey requires a factor of about 5 for example, you should then normally start out with a default factor of 5for that type of survey. Then if the “Total Error Factor” for an adjustment of another “static” job comes out about 1, you knowyou are doing typical work. If it is significantly higher than the value 1, you should find out why!

2.6 ELEVATIONS AND ELLIPSOID HEIGHTSSometimes when adjusting GPS projects, youmay want to specify that entered height values are ellipsoid heights rather thanorthometric elevations.

As discussed in Chapter 5, “Preparing Data” in themain STAR*NETmanual, height information for controlling coordinates maybe entered in two ways:

Heights entered on C, P or E lines (Coordinate, Position or Elevation data type lines) are assumed to be orthometric elevations.Heights entered on CH, PH or EH lines are assumed to be ellipsoid heights. Examples:


- 6 -

# Fixed Coordinate, Position and Elevation data lines# Example lines entered with Orthometric ElevationsC 151 2186987.234 6417594.321 320.26 ! ! !P 165 38-01-23.0007 120-59-45.2243 319.55 ! ! !E 168 321.56 !

# Example lines entered with Ellipsoid HeightsCH 251 2186922.443 6417665.234 221.42 ! ! !PH 265 38-01-43.3245 120-59-49.4311 209.98 ! ! !EH 268 212.23 !

The program uses supplied geoid height values to internally calculate ellipsoid heights from entered orthometric elevations, andorthometric elevations from entered ellipsoid heights. These geoid heights are determined by one of the following:

l The average project geoid height entered in the Project Options/Adjustment dialog

l Geoid heights calculated by geoidmodeling

l Individual heights entered using the GH data type

Note that if your GPS network contains conventional vertical observations based on the geoid such as zenith angles orelevation differences, it is very important that accurate geoid height information is given or modeled. Geoid heights are the onlyconnection between ellipsoid heights (referenced by GPS vectors) and orthometric elevations (referenced by conventionalobservations).

Youmust exercise great caution whenmixing fixed orthometric elevations and ellipsoid heights in the same adjustment. Besure your geoid heights are accurate, otherwise this scheme can cause warping in your network!

Note that only ellipsoid heights entered as fixed (or partially fixed using a standard deviation) will be listed as ellipsoid heights inthe review of data in the listing file. Any ellipsoid heights entered with approximate (free) values will be immediately convertedto orthometric and processed in the adjustment as a normal orthometric elevation.

2.7 SOLVING FOR TRANSFORMATIONSIn a fully-constrained network containing GPS vectors, STAR*NET-PRO can solve for transformations, a scale and three rota-tions to better fit your control. Indicate whether or not you want these transformations solved by setting options in the GPSoptions dialog as described in Chapter 3, “GPS Options” of this referencemanual supplement.

Why solve for transformations? Sometimes systematic errors or biases may exist in your GPS vector data. Solving for a scaleand rotations will “best-fit” the vectors to your constrained network stations. Depending on the type of network being adjusted,experienced users may solve for scale only, or solve only for rotations about two axes. Whether any or all requested trans-formations can even be solved depends on the constraints present in your network.

Minimally-Constrained NetworksA minimally-constrained network contains a single fixed station only. Always run aminimally-constrained network adjustmentfirst to make sure your observations fit together before attempting a fully-constrained adjustment. In aminimally-constrainedadjustment transformations cannot be solved. STAR*NET-PROwill adjust the network based only on the observations and thenetwork geometry. The adjustment will indicate how well the observations fit together, but not how they fit coordinate con-straints.


- 7 -

It is very important to note that adjustments of minimally-constrainedGPS networks will not produce valid grid coordinateswhen running on a non-GPS based datum such as the Clarke 1866 ellipsoid for NAD27! To get valid grid coordinates usingthese datums, youmust run a fully-constrained adjustment solving for all transformations!

Fully-Constrained NetworksA fully-constrained network contains at least two fixed horizontal coordinates and at least three fixed elevations. (These con-straints may be full fixities, or partial fixities defined as standard errors.) In a fully-constrained network, STAR*NET-PRO canusually solve for scale and three rotations of the GPS vectors during the adjustment.

When you run a fully-constrained adjustment using the GPS-basedWGS84 ellipsoid (or the essentially-identical GRS80 ellip-soid used for NAD83), solved scale and rotations should be very small, nearly zero. These solved values might represent smallsystematic errors or biases in the GPS vectors. If the solved values seem unreasonably large, you should determine the rea-son why and possibly make changes to your data.

When running a constrained adjustment using a non-GPS datum (such as the Clarke 1866 ellipsoid), you should expect thesolved scale and rotations to have small values. These solved values represent the transformations between the two ellipsoids(between Clarke 1866 and theGPS-basedWGS84 ellipsoids for example).

General Notes About Constraining Your Network1. Always run aminimally-constrained adjustment to make sure your observations fit together properly before addingmore

constraints!

2. When constraining a network to several fixed stations, add fixed stations one or two at a time to assure that the networkisn’t being warped by some bad station. If you are solving for scale and rotations, pay attention to their solutions. Anunexpected large change in one or more of these solved values may indicate the presence of an erroneous coordinatevalue.

3. When performing a fully-constrained adjustment using the GPS-basedWGS84 ellipsoid (or essentially-identical GRS80ellipsoid for NAD83), it is recommended that you first adjust the network with the transformations solving option turnedoff! If the adjustment runs OK, with small residuals, then if you wish, you can turn the transformations solving option onto refine your adjustment.

If you solve for transformations on your initial run, some larger-than-expected residuals may be partially absorbed by thetransformation (especially if your network is lightly constrained), and youmay miss an important clue pointing to a prob-lem with your observations or possibly bad coordinate constraints.

4. If you have a partially-constrained network consisting of two sets of fixed horizontal coordinates and only a single fixedelevation, STAR*NET-PROwill be able to solve for scale only.

5. Caution! If you have a partially-constrained network containing two or more fixed elevations but only a single station hav-ing fixed horizontal coordinates, any scale transformation solution will be based entirely on the elevation constraints!This may lead to unexpectedly large solutions for scale causing large changes in horizontal coordinates. To preventthis, either add horizontal constraints (whichmainly control scale solutions), or turn off the scale transformations solv-ing.

6. You can “set” scale and rotation transformations to predetermined values. For example, youmay have “solved” for trans-formation values during the adjustment of a fully-constrained network. Then at a later time you do another GPS surveyat the same site. But this time you simply want to run aminimally-constrained adjustment of the new survey and applythe originally solved scale and rotation transformations. Enter the solved scale and three rotations as “set” values in the


- 8 -

GPS options, and these transformations will be applied to the new adjustment. See Chapter 3 “GPS Options” in this sup-plement for details on doing this.

2.8 NOTES ABOUT RUNNING PREANALYSISYou can includeGPS vector observations in a preanalysis run just like you would conventional observations. You will, ofcourse, have to provide approximate coordinates for all stations. See Chapter 5, “Running Adjustments” in themainSTAR*NETmanual for details on required data for running preanalysis.

WhenG1, G2 andG3 lines already exist in your data, STAR*NET will use the FROM and TO station information from theG1lines, and the weighting information from theG2 andG3 lines.

However, if your GPS vectors have not yet been observed, you obviously will not have vector data or weighting information yetavailable. In this case you can prepare true “pre-planning” data by hand-entering proposedGPS vectors. Lay out a preliminarysketch of your proposed survey including station names. Then when preparing your preanalysis data, enter only G1 lines withthe planned FROM and TO stations names.

To provide the proposed weighting, use the “Apply Default StdErrs to Vectors with no SuppliedWeighting” option in the GPSOptions dialog to give these proposed vectors the same default weighting. Or to give different weighting to various areas of theproposed project, use the “.GPS DEFAULT” inline option as illustrated below. See Chapter 3, “GPS Options” in this manualsupplement for details these options.

For example, hand-entered vector data for a preanalysis jobmight look like this:

.GPS DEFAULT 0.007 2 #Setting StdErrs of 0.007 meters and 2 PPM

G1 DIABLO-CONCORD #Proposed vector connectionsG1 DIABLO-X365G1 90112-HAYWARDG1 90112-CONCORDG1 90112-90555

.GPS DEFAULT 0.004 5 #Changing the default weightingG1 90555-92201etc...

These proposed vectors can be included with proposed conventional and differerential levelingmeasurements in a single prea-nalysis run for survey planning of a true combined observation-type network.

Chapter 3: GPS OPTIONS

- 9 -

CHAPTER 3: GPS OPTIONS3.1 OVERVIEW

As discussed in Chapter 4 of themain STAR*NETmanual, the programmaintains a list of option settings for each project. Toset or change options for the current project, chooseOptions>Project, or press the Project Options tool button. An optionsdialog appears with eight tabbed dialog pages:

The first six tabbed options dialogs, Adjustment, General, Instrument, Listing File, Other Files and Special are fully describedin Chapter 4 “Options” of themainmanual.


- 10 -

Although the adjustment options were fully discussed in Chapter 4 of themainmanual, it should be noted that for any projectcontaining GPS vectors, the adjustment options must be set to either "2D" or “3D” and the Coordinate Systemmust be set tosome “Grid” zone as illustrated in the example settings above.

TheGPS andModeling tabbed options dialogs, active in the “Professional” edition, are described in this chapter. Options set inthese two dialogs assume the settings relate to an entire project. However, there are some settings that may not remain thesame throughout an entire data file. These changes to option settings within a data file are controlled by “Inline Options” whichare also described in this chapter.

3.2 GPS OPTIONS

These fields allow you to set default values or options relating to GPS vectors present in your network data. Some optionsrelate to weighting of your vectors, or solving for transformations to better fit your vectors to the datum. Other options simplyallow you the set preferences for the appearance of GPS information in your output listing.

Vector Default Weighting, Factoring and Centering Errors Settings


- 11 -

l Apply Default StdErrs to Vectors with no SuppliedWeighting – This option affects only vectors that aremissing their G2& G3 data lines. Often times, for example, RTK vectors imported from some systems are not supplied with weighting.This option allows you to set a default weighting scheme that will be applied to these vectors during an adjustment.

By default, both horizontal and vertical vector standard errors and PPM are set to the same values. If you want to applydifferent vertical standard error and PPM values, check the “Alt Vert StdErr” box and enter alternate values. In the exam-ple dialog above, the default horizontal values are set to 0.008meters and 4 PPM, and the vertical values to 0.010meters and 6 PPM.

When this option is selected, the default values for missing weights are used for the entire project. However, thesedefaults may be changed anywhere in a vector data file by inserting the “.GPS Default” inline option. See details later inthis chapter.

Note! If you feel that none of your imported vectors should bemissing the weighting data (the G2 & G3 lines), we rec-ommend that you do not select this option. Then if the program finds a vector without weighting during an adjustment, itwill issue an error and you can review your data and take any action required.

l Factor Supplied Vector StdErrors by – This option affects only vectors that have supplied weighting onG2 & G3 lines.As discussed earlier, standard errors supplied for vectors are often over-optimistic, and to change them to real-worldvalues, you can factor them. To factor (multiply) all these supplied vector standard errors by a single value, check thebox and enter the value.

By default, both horizontal and vertical components of the vector standard errors aremultiplied by the same factor. Ifyou want to a apply different factor to the vertical standard error component, check the “Alternate Vert” box and enter analternate value. In the example dialog settings shown, the horizontal components of imported vector standard errors willbemultiplied by 3.0, and the vertical, by 5.0.

When this option is selected, these values become the default factoring values for the entire project. However, thesedefault factors may be changed anywhere in a vector data file by inserting the “.GPS Factor” inline option. See detailslater in this chapter.

l Apply Centering to StdErrs - This option allows you to inflate vector standard errors of by applying horizontal and verticalcentering errors at both receiver ends. The size of the centering error is assumed to be the same at each receiver. Whenthis option is on, all vectors are affected regardless of how the original standard errors were set.

By default, both horizontal and vertical components of the centering error are the same. To apply different vertical cen-tering, check the “Alternate Vert” box and enter an alternate value. In the example dialog settings shown, 0.002meterscentering will be applied to the horizontal component of each vector at both receivers, and 0.004meters centering to thevertical component, at both receivers. Note that vector centering errors are always entered inmeters! When the pro-gram adds the effects of centering to vector standard errors, the centering error is always applied after any factoring hasbeen applied. In other words, the centering is not factored too.

These values become the “default” centering values for all vectors in your project. However if required, these default fac-tors may be changed anywhere in a vector data file by inserting the “.GPS Centering” inline option. See details later inthis chapter.

Option Group: Transformations

l Transformations – Check this box if you want the program to solve for (or possibly set values for) transformations duringthe adjustment. When you select transformations, you can specify which of the four transformations that should besolved for (or set) during the adjustment process. These transformations include a scale and three rotations about theNorth, East and Up axes. You can choose from three common solve-for selections:


- 12 -

1. Solve for Scale and Rotations

2. Solve for Scale Only

3. Solve for Rotations Only

In addition to the three preset selections, you can choose “Custom” to define any combination for solving or setting ofthe scale and three rotations as shown next.

Press the “Custom Settings” button as shown below to open up the Custom GPS Transformations dialog as shown inthe next paragraph. Note that any current custom settings in the dialog are reviewed to the right of the button for con-venience.

This settings dialog allows you to independently control Scale, North-Rotation, East-Rotation and Up-Rotation trans-formations. Check the box of each component you want to control, and select “Solve” or “Set” for each. When the “Set”choice is selected, enter a preset transformation value in its field.

For example, to solve for Scale, set Rotation about the North axis to 1.25 seconds, set Rotation about the East axis to0.333 seconds, and no solving or setting of Rotation about the Up axis, the dialog settings would be entered like this.

Note that STAR*NET-PRO can solve for transformations only when your network is adequately constrained! If yourequest that certain transformation be solved, but the network doesn’t have enough constraints for them to be solved,the program will go ahead and perform the adjustment anyway. The listing, however, will indicate that certain requestedtransformations could not be solved.

See “Solving for Transformations” in Chapter 2 of this supplement for more information onminimally-constrained andfully-constrained adjustments and the solving of transformations.

Option Group: Listing Appearance

l List VectorWeighting as –Most surveyors wish to see standard errors rather than covariances since they aremoreunderstandable and can be easily related to standard errors of conventional observations such as angles and distances.However if you prefer to see weighting expressed as covariances, select that option choice.

l Sort Unadjusted Vectors by – In the review of unadjusted vectors in the listing file, you can select the order you preferthem shown. By default, the vectors will be listed in the same order they were first read in by the program, but you can


- 13 -

also choose that they be sorted by their station names or by their lengths. Sorting by length usually causes redundantlyobserved vectors to be listed together, often useful when debugging an adjustment.

l Sort Adjusted Vectors by – Likewise, in the adjusted observations and residuals section of the listing file, you can selectfrom the same orders as offered for the unadjusted vectors. In addition, you can choose that the vectors be listed by thesize of their residuals, largest residuals first.

l Show Residual Summary/Sort by – Check this option to create an output section in the listing consisting of a one-line-per-vector table which is very helpful for finding the “worst” GPS vectors in a network. Each line in the table contains avector’s two station names, N, E, and Up residuals, 2D and 3D residual lengths, total length and the vector serialnumber. It can be sorted in various ways. For example, if you are particularly interested in the size of horizontal resid-uals (those computed from North and East vector residuals) choose to sort by “2D” residuals.

Choosing to sort by “Adj Vect Order” creates the listing in the same order as selected by the “Sort Adjusted Vectors by”field previously described above.

l Show ECEF Information - By default, final adjusted XYZ earth-centered-earth-fixed Cartesian coordinate values andCartesian DX, DY and DX residuals are not shown in the listing. Most surveyors prefer to see the final adjusted coor-dinates expressed as grid coordinates or geodetic positions, and vector residuals expressed in themore familiar Delta-North, Delta-East and Delta-Up form.

But to see ECEF Cartesian values, select this option, and then choose whether to show the information for Coor-dinates, Residuals or Both. If the “Both” choice were selected, the following example listing sections illustrate the extrainformation printed. The first is a section listing the X, Y and Z Cartesian coordinates.

Adjusted ECEF Coordinates (Meters)

Station X Y Z0001 -2092498.154661 -4924379.150235 3460379.9581740002 -2091276.069216 -4924320.650192 3461198.0605140003 -2091439.881629 -4925183.184356 3459816.765030etc.....

And in the “Adjusted GPS Vector Observations” section, DX, DY and DZ vector components and residuals are added tothe original listing format. .


- 14 -

Adjusted GPS Vector Observations Sorted by Names (Meters)

From Component Adj Value Residual StdErr StdResTo(V117 Day124(1) 15:34 00010002.SSF)0001 Delta-N 975.7438 -0.0003 0.0037 0.10002 Delta-E 1101.8681 0.0013 0.0033 0.4

Delta-U 0.7383 -0.0004 0.0055 0.1Delta-X 1222.0804 0.0013 0.0038 0.3Delta-Y 58.5045 -0.0003 0.0049 0.1Delta-Z 818.0993 -0.0005 0.0041 0.1Length 1471.7981

(V109 Day124(3) 19:24 00010003.SSF)0001 Delta-N -649.9083 0.0072 0.0078 0.90003 Delta-E 1288.4278 0.0023 0.0059 0.4

Delta-U -34.0012 0.0029 0.0128 0.2etc.....

Option Group: OPUS Station

TheOPUS Station options only affect vectors imported via the OPUS importer, it provides ameans of adjusting the StdErrvalues as specified in the OPUS report with more appropriate values.

l Factor Supplied StdErrors by – This option affects only vectors that have supplied weighting onG2 & G3 lines. As dis-cussed earlier, standard errors supplied for vectors are often over-optimistic, and to change them to real-world values,you can factor them. To factor (multiply) all these supplied vector standard errors by a single value, check the box andenter the value.

By default, both horizontal and vertical components of the vector standard errors aremultiplied by the same factor. Ifyou want to a apply different factor to the vertical standard error component, check the “Alternate Vert” box and enter analternate value. In the example dialog settings shown, the horizontal components of imported vector standard errors willbemultiplied by 3.0, and the vertical, by 5.0.

When this option is selected, these values become the default factoring values for the entire project. However, thesedefault factors may be changed anywhere in a vector data file by inserting the “.GPS Factor” inline option. See detailslater in this chapter.

l Apply Centering to StdErrs - This option allows you to inflate vector standard errors of by applying horizontal and verticalcentering errors at both receiver ends. The size of the centering error is assumed to be the same at each receiver. Whenthis option is on, all vectors are affected regardless of how the original standard errors were set.

By default, both horizontal and vertical components of the centering error are the same. To apply different vertical cen-tering, check the “Alternate Vert” box and enter an alternate value. In the example dialog settings shown, 0.002meterscentering will be applied to the horizontal component of each vector at both receivers, and 0.004meters centering to thevertical component, at both receivers. Note that vector centering errors are always entered inmeters! When the pro-gram adds the effects of centering to vector standard errors, the centering error is always applied after any factoring hasbeen applied. In other words, the centering is not factored too.

These values become the “default” centering values for all vectors in your project. However if required, these default fac-tors may be changed anywhere in a vector data file by inserting the “.GPS Centering” inline option. See details later inthis chapter.


- 15 -

3.3 INLINE OPTIONS RELATING TO GPS VECTOR DATAAs described in themain operatingmanual, there is a category of options called “inline” options that you insert directly into aninput data file, and that in general, affect only data lines that follow them in that file. Some of these inline options simply changedefault settings originally defined in dialogs already discussed. Others perform special functions unrelated to other option set-tings.

It is important to note that, in general, the effect of any inline option is only on data within a single file. Every file listed in theInput Data Files dialog is initialized with the standard Project Options as it is read in during an adjustment. Therefore, if youwant an inline option to affect several files, youmust enter it in each file.

Inline options begin with a period “.” andmay be followed by option names, keywords and numeric values. Option names andkeywords may be upper or lower case and abbreviated as long as the remaining characters are unique. For example both of theoptions shown below are exactly the same, except the second is abbreviated.

.GPS FACTOR 7.5 VERTICAL 12 # Using full keywords

.GP FA 7.5 V 12 # Fully abbreviated

TheGPS inline options listed below are described in detail in the following sections. These inline options all begin with a spe-cial “GPS” header to differentiate them from other options more general in character.

Option Function

.GPSWEIGHT This option is automatically inserted into the data file by the vector importer to define the type ofimported weighting.

.GPS DEFAULT Change the current Default Standard Error values for imported vectors not having supplied weighting.

.GPS FACTOR Change the current Standard Error multiplier for imported vectors having supplied weighting.

.GPS USE Override the current weighting schemewith your own scheme based on your entered StdError andPPM values.

.GPS CENTERING Change the current vector Centering Error value.

.GPS IGNORE Ignore a list of vectors identified by serial numbers.

.GPS FREE Free a list of vectors identified by serial numbers.

.GPS ADDHIHT Adjust the Base and Rover Heights by a fixed amount, to correct for antenna height errors.

.GPS NETWORK Process vectors following this as part of the network of adjusted observations.

.GPS SS Process vectors following this as sideshots, after themain network is adjusted.

Inline Option .GPS DEFAULT [ stderr ppm [ VERTICAL stderr ppm ] | FREE |IGNORE ]This inline option affects only vectors that aremissing G2 & G3 data lines. It sets the same items as the “Apply Default StdErrsto Vectors with no SuppliedWeighting” section in the GPS Options dialog. The inline sets new “default” standard errors, andthis weighting remains in effect until the inline option is again used, until the option is turned off, or until the end of the file. Whenthe inline option is turned off or the end of the file is reached, any “Apply Default” settings from theGPS Options dialog againbecome the current defaults. The ability to change the “default” standard errors anywhere is a data file allows you to control theweighting of different groups of vectors that may exist in your data – for example, vectors from different equipment.

The example below causes a standard error of 0.005meters and 3 PPM to be assigned to subsequently read vectors that havenoG2 & G3weighting lines. Just as with all vector data, standard error values are always entered inmeters.

../../../../../Content/StarNet-PRO-Manual/Inline Option GPS WEIGHT.htm



- 16 -

.GPS DEFAULT 0.005 3

G0 'V532 Day134(3) 01:15G1 0036-0040 4861.328134 -348.097034 2463.249801

G0 'V533 Day134(3) 01:22G1 0036-0041 4874.221344 -534.211324 2644.237764

And just as allowed in the options dialog, you can apply separate weighting values to the horizontal and vertical components ofthe vector. Add the “Vertical” keyword and standard error and PPM values. The following specifies 0.005meters and 3 PPM forthe horizontal (N & E) components and 0.007 and 4 PPM for the vertical (Up) component.

.GPS DEFAULT 0.005 3 VERT .007 4

Also, the DEFAULT inline optionmay be used to define any following vectors that aremissing their G2 & G3 lines as free orignored. Just add the “Free” or “Ignore” keyword. Free vectors remain in the network but have no influence in the adjustment;ignored vectors are completely excluded from the network.

.GPS DEFAULT FREE #Use the FREE keyword to include vectors

.GPS DEFAULT IGNORE #Use the IGNORE keyword to exclude vectors

To change back to the original values specified in the GPS Options dialog, enter the default option line with no values.

.GPS DEFAULT

Note that if the original “Default” section in the options dialog had not been selected, there will be no “default” values available.So unless this or some other option is used to provide some sort of weighting status, an adjustment run will properly terminateif vectors are found without G2 & G3 lines.

Inline Option .GPS FACTOR [ factor [ VERTICAL factor ] | FREE | IGNORE ]This option affects only vectors that have supplied weighting onG2 & G3 lines. It sets the same items as the “Factor SuppliedVector StdErrors by” section in the GPS Options dialog. The inline sets new “factoring” values to be applied to weighting sup-plied on imported G2 & G3 lines, and this new factoring remains in effect until the inline option is again used, until the option isturned off, or until the end of the file. When the inline option is turned off or the end of the file is reached, any “Factor Supplied…” settings from theGPS Options dialog again become the current factoring values.

This ability to change the factoring of vector standard errors anywhere in your data allows you to control the weighting of dif-ferent groups of vectors in a network. For example one groupmight be from static observations, another from kinematic, andanother might be vectors from another manufacturer’s equipment.

The example below multiplies all following imported vector standard errors by 7.5.


- 17 -

.GPS FACTOR 7.5

G0 'V532 Day134(3) 01:15 12346643.SSFG1 0036-0040 4861.328134 -348.097034 2463.249801G2 4.35804625082312E-008 2.00368296412947E-007 1.23348139662277E-007G3 1.29776877121456E-008 -4.73073036591065E-009 -7.87018453390485E-008

And just as allowed in the options dialog, you can apply separatemultipliers to the horizontal and vertical standard error com-ponents of the vector. Add the “Vertical” keyword and amultiplier. The following example specifies amultiplier of 7.5 to the hor-izontal (N & E) components and 12 to the vertical (Up) component.

.GPS FACTOR 7.5 VERT 12

Also, the FACTOR inlinemay be used to define any following vectors as free or ignored even though weighting onG2 & G3lines is supplied. Just add the “Free” or “Ignore” keyword. Free vectors remain in the network but have no influence in the adjust-ment; ignored vectors are completely excluded from the network.

.GPS FACTOR FREE #Use the FREE keyword to include vectors

.GPS FACTOR IGNORE #Use the IGNORE keyword to exclude vectors

To change back to the original values specified in the GPS Options dialog, enter the factor option line with no values. Or if theoriginal “Factor” option in the GPS Options dialog had not been selected, then no factoring is applied to subsequent vectors.

.GPS FACTOR

Inline Option .GPS USE [ stderr ppm [ VERTICAL stderr ppm ] | FREE | OFF ]In certain cases, youmay want to apply your ownweighting scheme to the vectors regardless of whether imported weighting issupplied or not. When the USE option line is entered, your ownweighting scheme is applied to GPS vectors found on theG1lines. Any G2 & G3 lines are completely ignored, and in fact, they do not have to be present. Note that when you apply yourownweighting schemewith the USE inline option, correlations (interdependence between vector components) are set to zero.

The USE inline causes the DEFAULT and FACTOR inlines and the corresponding GPS Dialog options to be temporarily inac-tive. When the USE inline is turned off (or the end of the file is reached) the other weighting schemes again are reset to their pre-vious status.

On the option line, enter a standard error value in meters and a PPM value. The PPM is based on the total point to point vectorlength. The example USE line below sets a standard error 0.008meters and 3 PPM, and causes any G2 & G3 lines to beignored. Just as with all vector data, standard error values are always entered inmeters.


- 18 -

.GPS USE 0.008 3

G0 'V532 Day134(3) 01:15 12346643.SSFG1 0036-0040 4861.328134 -348.097034 2463.249801G2 4.35804625082312E-008 2.00368296412947E-007 1.23348139662277E-007G3 1.29776877121456E-008 -4.73073036591065E-009 -7.87018453390485E-008

Toweight the horizontal and vertical components of each vector separately, add the “Vertical” keyword plus a standard errorvalue and PPM. The example USE line below sets a standard error value of 0.008meters and 3 PPM for the horizontal (northand east) components and 0.012meters and 5 PPM for the vertical (up) component.

.GPS USE 0.008 3 VERT 0.012 5

Also, the USE inlinemay be used to define any following vectors as free or ignored. Just add the “Free” or “Ignore” keyword.Free vectors remain in the network but have no influence in the adjustment; ignored vectors are completely excluded from thenetwork.

.GPS USE FREE #Or the IGNORE keyword to exclude vectors

When the USE line is entered to define custom weighting, this weighting applies to all vectors that follow until weighting is rede-fined by another USE option line, or until the USE weighting is turned off. Turn the USE weighting off by adding the “Off” key-word to the inline. Weighting then reverts back to using the original weighting imported on theG2 & G3 lines or weightingmodified by the DEFAULT or FACTOR options.

.GPS USE OFF

Modifying Weighting Status of a Single Vector Using the “G0” Line

This feature allows you to change the weighting status of a single vector by entering extra data on the “G0” line of the vector.The functionality and data parameters are identical to the FACTOR inline option previously described.

This option takes temporary precedence over any DEFAULT, FACTOR or USE inline options or corresponding GPS Dialogoptions that may be currently in effect. No other option that is currently in effect is changed by the use of this feature.

To factor existing weighting supplied for a single vector, enter the “Factor” keyword and themultiplier following the “G0” code.In the example below, the 7.5multiplier on the “G0” line affects only the standard error components of the single vector. To usethis factor option, the G2 & G3weighting lines must be present.

G0 FACTOR 7.5 'V532 Day134(3) 01:15 12346643.SSFG1 0036-0040 4861.328134 -348.097034 2463.249801G2 4.35804625082312E-008 2.00368296412947E-007 1.23348139662277E-007G3 1.29776877121456E-008 -4.73073036591065E-009 -7.87018453390485E-008

Or you can factor the horizontal & vertical weight components differently.


- 19 -

G0 FACTOR 7.5 VERT 12 'V532 Day134(3) 01:15 12346643.SSF

Also, in a similar fashion, the “G0” linemay be used to free or ignore the single vector. Just insert the “Free” or “Ignore” keyworddirectly after the “G0” code as shown in the example. A free vector remains in the network but has no influence in the adjust-ment; an ignored vector is completely excluded from the network.

G0 FREE 'V532 Day134(3) 01:15 12346643.SSFG1 0036-0040 4861.328134 -348.097034 2463.249801G2 4.35804625082312E-008 2.00368296412947E-007 1.23348139662277E-007G3 1.29776877121456E-008 -4.73073036591065E-009 -7.87018453390485E-008

Inline Option .GPS CENTERING [ value [ VERTICAL value ] ]This inline sets the same values as the “Apply Centering to StdErrs” option section in the GPS Options dialog. The inline optionsets new default centering values which remain in effect until the inline option is again used or until the end of the file. When theinline option is turned off or the end of the file is reached, any “Apply Centering” settings from theGPS Options dialog againbecome the current defaults.

The example below specifies that an instrument error of 0.003meters is to be applied to the north, east and up components ofthe vector at both receiver ends. Just as with all vector data, centering errors are always entered inmeters.

.GPS CENTER 0.003G0 'V532 Day134(3) 01:15 12346643.SSFG1 0036-0040 4861.328134 -348.097034 2463.249801G2 4.35804625082312E-008 2.00368296412947E-007 1.23348139662277E-007G3 1.29776877121456E-008 -4.73073036591065E-009 -7.87018453390485E-008

And just as allowed in the options dialog, you can apply separate horizontal and vertical centering errors to the ends of the vec-tors. Add the “Vertical” keyword and a centering error value. The following example specifies 0.003meters centering error to beapplied to each end of the horizontal (north and east) components, and a 0.006meters centering error to each end of the vertical(up) component.

.GPS CENTER 0.003 VERT 0.006

To change back to the original centering default specified in the GPS options dialog, enter the centering option with no values.

.GPS CENTER

When centering values are set, centering affects the standard errors of all vectors whether their weighting is imported from sup-plied G2 & G3 lines or their weighting is given using the “DEFAULT” option for vectors not supplied G2 & G3 lines.


- 20 -

Note that the FACTOR option allows standard errors supplied with G2 & G3 lines to bemultiplied by a factor. When the cen-tering errors are applied to standard errors that are factored, the centering error is applied last (i.e. the centering is not factoredtoo).

Inline Option .GPS { IGNORE | FREE } vectorsWhen debugging aGPS network, it is very useful to be able to quickly disable selected vectors so you can rerun an adjustmentand see how the results are affected.

These options allow you to specify a list of vectors to ignore or free up. The vectors are identified by the serial numbersassigned to them by the vector importer routine. These serial numbers are on the “G0” lines of the vector data and they alsoappear on all sections of the output that list vectors.

In the example below, the first two option lines cause any following vectors read by the program having the specified serialnumbers to be ignored in the adjustment. The third line causes vectors to be set free. As indicated by the example, you can putone or more serial numbers on each line, and include as many lines as you wish.

.GPS IGNORE 33 37 38 76 321 334 352 432 166 167 168 521

.GPS IGNORE 214

.GPS FREE 255 256 257 199 198

These option lines may be placed anywhere in you data before the vector data, but we suggest putting them somewhere veryconspicuous. For example, if you place them at the very top of your main data file or your vector file, you can quickly find them,edit them and rerun the adjustment.

The IGNORE option causes the vector to be ignored completely when you run the adjustment. It will show up nowhere in thelistings. The FREE option, however, leaves the vector in the adjustment but gives it no weight. It will not influence the adjust-ment in any way, but the vector and its residual will be listed in the output. Freeing vectors is often a useful debugging toolwhen analyzing a network adjustment.

Whenever the IGNORE inline is used, a list of ignored vectors are written to an output section near the beginning of the listingto help you keep track of what you have done. No such listing is created when the FREE inline is used, but these vectors ofcourse will show up as “free” in the data review and residual listings.

Error messages will be generated if you try to “ignore” or “free” using a vector serial number which does not exist, or using aserial number that exists more than once.

We see this facility as a convenient debugging tool only, and highly recommend that once you determine which vectors to elim-inate, you actually edit your vector file and remove or comment them out permanently.

Inline Option .GPS ADDHIHT [ HI HT ]The purpose of the AddHiHt command is to correct recording errors of either base station or rover heights. If a large number ofvectors are collected with the same "systematic" error in height this inline provides a single line correction without large editingof either the field collection file or the resulting STAR*NET data file.

STAR*NET version 6 required GPS vectors to bemark-to-mark; it has no concept of base or rover heights.

STAR*NET version 7 now supports height values on theG1 record in the usual syntax. If the heights aremissing, the heightsare assumed to be as if "0.0/0.0" were entered. Thus, every vector has base and rover heights.


- 21 -

GPS AddHiHt requires two numbers separated by whitespace, or no parameters. The first number is the correction for the baseheight, the second for the rover height. The numeric values may positive, negative, or zero. If no numbers are present, both cor-rection values are set to zero.

The height correction values are added to all subsequent vector heights.

If this command is not present, the default HI and HT corrections are zero.

# Project Settings# Adjustment# Type 3D# Units Meters# Grid NAD83# Zone CA Zone 3# Geoid -32# GPS# Enable default weight for G1 only vectors## ControlC 1 646210.759201 1844193.216901 100.000000 ! ! !B 1-2 N20-00-00E## Correct field error recording rover pole height.# Height is really 2 meters..GPS AddHiHt 0.0 1.0## Field data collected with invalid but correctable heightsG1 1-2 53.2277 23.8799 81.4181 0.5/1.0G1 1-3 147.3038 -0.8556 135.5121 0.5/1.0G1 1-4 64.2874 -35.5183 32.4483 0.5/1.0G1 2-3 93.5277 -25.6040 54.8908 0.7/1.0G1 2-4 10.5113 -60.2667 -48.1730 0.7/1.0G1 3-4 -83.5226 -35.4644 -102.3282 0.8/1.0#.GPS AddHiHt# continue with more data ...

Inline Option .GPS { NETWORK | SS }GPS vectors following the "GPS NETWORK" command are included in in the network of adjusted observations. Stations ref-erenced in the G1 command are part of the network, are adjusted, and receive error propagation. "GPS NETWORK" is thedefault condition.

GPS vectors following the "GPS SS" command are applied after the least squares solution is found for the network. The side-shot vector's target station position is computed from the origin station's adjusted position. Error propagation is not performedfor sideshot stations.

Sideshot vector target station names may be duplicated or be the same as stations in the adjusted network. This is the sameas for conventional sideshots. Checking for these conditions is controlled in the project options in the "Special" tab. Duplicatenaming can be allowed, allowed with warnings, or disallowed with error message.

Sideshot vectors have no residuals.

Sideshot vector target station coordinates are reported separately in the listing file under the heading: "GPS Sideshot Coor-dinates Computed After Adjustment".


- 22 -

Sideshot vector target station geodetic positions are reported only in the positions output file enabled under the "Other Files"project options.

# Project Settings# Adjustment# Type 3D# Units Meters# Grid NAD83# Zone CA Zone 3# Geoid -32# GPS# Enable default weight for G1 only vectors#P 1 37-48-15.00000000 122-16-10.00000000 100.000000 ! ! !B 1-2 N20-00-00E.GPS NETWORKG1 1-2 53.8602 24.8819 80.4983 "GPS NETWORKG1 1-3 147.9357 0.1464 134.5920G1 1-4 64.9198 -34.5161 31.5287G1 2-3 94.0756 -24.7354 54.0937G1 2-4 11.0596 -59.3980 -48.9696.GPS SSG1 2-GPS_SS1 -62.4405 60.5783 23.0533 "GPS SIDESHOTG1 2-GPS_SS2 -49.7530 81.5096 54.5969G1 2-GPS_SS3 -20.3143 93.5383 87.9655.GPS NETWORKG1 3-4 -83.0159 -34.6626 -103.0632# Conventional SideshotsSS 2-1-SS1 30-00-00 30.000 90-00-00SS 2-1-SS2 50-00-00 50.000 90-00-00SS 2-1-SS3 70-00-00 70.000 90-00-00

Inline Option .BASE PointName [ AntennaHeight ]The Base command is used in conjunction with theMicroSurvey FieldGenius GPS Vector Importer, for cases when the raw filebeing imported does not contain the necessary base point information. For example, this can occur when connecting a roverreceiver to a permanent reference station or to an NTRIP or GPRS server.

When using a typical two-receiver base/rover configuration and the reference receiver has been configured by FieldGenius, theraw file will contain all of the pertinent base information such as its point id, antenna height, and its geodetic and cartesian coor-dinates. However, this information will not be present if the reference receiver has not been configured by FieldGenius, forexample when connecting a rover receiver to a permanent reference station via a long-range radio link, or to an NTRIP orGPRS server via an internet connection.

The .Base command can be used for defining a physical reference receiver - youmust give it a Point ID and reduced AntennaHeight to its phase center. If the AntennaHeight value is not present, it will be assumed to be zero.

The .Base command can also be used for defining a virtual reference receiver - youmust give it a Point ID, but not an antennaheight.

Following is a snippet from the start of a FieldGenius raw file containing GPS vector data, with some added comments andinlines.


- 23 -

--FieldGenius v4.4.0.6 (2011-02-09)JB,NMBASEROVERAUTO,DT02-21-2011,TM14:09:31MO,AD0,UN1,SF1.000000,EC0,EO0.0,AU0CS,CO3,ZGUTM Zones NAD83,ZNUTM83-11,DNVA,PV3,N 0.0000,E 0.0000,LZ0.0000,SO0.00000,SA0.00000,GNEllipsoidal

.Data off# Note, if using RTK radio corrections from a base receiver which has been configured by FieldGenius, you do# not need to use the .Base inline option because the raw file already contains the relevant information.--Instrument Selected: Type=GNSS,Profile=JAVADBASE,Model=Triumph--Antenna: Desc=User Defined,True=0.000m,Meas=0.000m,ARP_V=0.0mm,ARP_H=0.0mm,NGS_ID="USER_DEFINED ",NGS_L1=0.0mmAH,DC1,MA0.000,ME2,RA0.000BP,PN1,LA49.83849763141,LN-119.61016040066,HT396.0871,SG0GS,PN1,N 5523942.4350,E 312322.4015,EL396.0871,--.Data on

.Data off# However, if using RTK radio corrections from a base receiver which has not been configured by FieldGenius,# the above information will not be present in the raw file so you will need to insert a .Base command# to define the base station's Point ID and reduced antenna height to the phase center..Base 1 0.000.Data on

.Data off# Similarly, when connecting to an internet NTRIP or GPRS server to receiver RTK corrections,# the virtual reference station information will also not be present in the raw file so you will need to insert# a .Base command to define the virtual base station's Point ID..Base 1.Data on

--Instrument Selected: Type=GNSS,Profile=ALTUSRADIOROVER,Model=APS-3 Rev 2--GPS Tolerance: Sol=2,Elev=10,PDOP=4.0,SVs=5,RefID=0,HRMS=5.000,VRMS=5.000,Obs=5,Time=5--Antenna: Desc=User Defined,True=0.000m,Meas=0.000m,ARP_V=0.0mm,ARP_H=0.0mm,NGS_ID="USER_DEFINED ",NGS_L1=0.0mmAH,DC2,MA0.000,ME2,RA0.000EP,TM22:12:08.0000,LA49.83859270308,LN-119.61001119903,HT388.2826,RN0.2571,RE0.1293,RV0.6401,DH1.6,DV2.1,GM3,CL1BL,DCROVER,PN2,DX15.8089,DY6.0947,DZ0.8661,--,GM3,CL1,HP0.257,VP0.640CV,DCROVER,SV7,SC1,XX1.09950208664,XY1.36327779293,XZ-0.95057028532,YY2.07779598236,YZ-1.58409154415,ZZ1.73618268967GS,PN2,N 5523952.6297,E 312333.4964,EL388.2826,--

And here is the resulting STAR*NET vector data after import. Notice the G1 1-2 record, indicating the point ids of the base sta-tion (1) and rover measurement (2).

.GPS WEIGHT COVARIANCEG0 'V1 02-21-2011 22:12:08.0000 baseroverauto.rawG1 1-2 15.808900 6.094700 0.866100G2 1.099502086640E+000 2.077795982360E+000 1.736182689670E+000G3 1.363277792930E+000 -9.505702853200E-001 -1.584091544150E+000


- 24 -

Chapter 4: IMPORTINGGPS VECTORS

- 25 -

CHAPTER 4: IMPORTING GPS VECTORS4.1 OVERVIEWGPS vectors can be extracted from a variety of baseline file formats using the vector importer facility. Choose Input>ImportGPS Vectors:

TheGPS Vector Importer dialog consists of four tabbed pages. To import vectors into your project, first select a baseline for-mat on the Import dialog page. Next, set any desired importing options on theOptions page. And finally return to the Importpage to actually select the baseline files and perform the import. Review your imported vector file from the Vector File page, orif there were problems encountered during the import processing, review any errors or warnings from the Error Log page.

Details on all steps required to import vectors are described in the following pages.


- 26 -

4.2 USING THE GPS IMPORTERFirst, on the Import dialog page illustrated on the previous page, select the format for your particular system’s baseline vectorsfrom the “GPS Baseline Format” dropdown selection list.

Note that, in our example, we will be working with “Trimble GPSurvey” baselines.

Next, change to theOptions page to set any options you would like the importer to use when importing the selected type ofvectors.

The options page below shows options for importing our “Trimble GPSurvey” vectors. Options for most vector types will lookthe same or similar to this example.

l Strip Leading Zeros – This setting causes all leading zeros to be stripped from any vector station names that are purelynumeric. For example, a station having the name “0057” will be imported as “57” when this option is on. However a sta-tion containing any non-numeric characters such as “00A5” will remain unchanged.

l Change Case of Alpha Station Names – Simply changes the case of alphabetic characters in station names to all upperor all lower case, if desired.

l Change Dash in Station Names – In STAR*NET programs, dashes are used as separators in station name strings (forexample 0001-0002). If you know that you have embedded dashes in your individual station names, you can substituteanother character for these dashes. For example, if a station name is “A-773”, and you select to substitute a “Period” forthe dash, the name “A.773” will be used.

l Change Station Name Separator – As indicated above, dashes are used as separators in station name strings. Ratherthan replacing the dash with another character, youmay prefer to preserve the dashes in your names. This option allowsyou to change the separator character to something else. For example, if you choose to change the dash separator to acomma, the station string “0001-0002” becomes “0001,0002” and in addition, a “.SEP” inline option is automaticallyinserted in the vector file to alert STAR*NET that the separator character has been redefined. See Chapter 5 in themainmanual for details on the “.SEP” inline.

l Import Descriptors when Present – This setting allows you to extract descriptors from certain baseline files whenever


- 27 -

they are present. Some baseline files contain descriptor information for stations, some do not. Trimble and Leica for-mats, for example, often contain descriptor information. Leica files sometimes contain fairly complex descriptor andattribute information which you can selectively import. Seemore details for Leica descriptors in the “Importing SpecificFormats” section.

Descriptors are inserted into vector data as “C” lines and define the “TO” stations. The “C” line is usually used for enter-ing coordinates, but can also be used to initialize a descriptor for a station. Below is an imported vectors having anextracted descriptor.

C 0040 'Iron pipe G0 'V532 Day134(3) 01:15 12346643.SSFG1 0036-0040 4861.328134 -348.097034 2463.249801G2 4.35804625082312E-008 2.00368296412947E-007 1.23348139662277E-007G3 1.29776877121456E-008 -4.73073036591065E-009 -7.87018453390485E-008

Depending on the particular type of baseline files being imported, the “C” lines containing the vector informationmay beshownwith the vector as shown above, or they may be bunched together above the vector information.

l Default Folder to Look in - At the bottom of options dialog, you can specify a folder you would like the importer to look infirst when you are selecting vector files on the Import page. For example, if you are running Trimble’s “GPSurvey,” youwould probably want to set this folder to “C:\GPSurvey\Projects” since this directory will contain subdirectories con-taining your various projects. Setting this folder is optional, but it can save you some time each time you select baselinefiles to import as described in the next final importing step described next.

Before going on, it is important to note that options set for a particular type of baseline format are uniquely saved for that type ofvector format. Options for Leica, Ashtech, and Trimble GPSurvey, for example, can be separately set. These options arestored in the STAR*NET settings in your computer’s registry. Therefore, whenever selecting a baseline format for importingvectors to a project, the last options set for that baseline format will be recalled as defaults. In addition, the last “Baseline For-mat” type is also remembered, and the next time you import vectors, that baseline format will automatically be recalled as thedefault.

To complete the importing process, change back to the Import page as shown below.


- 28 -

l Make sure the “Import Vectors To” file shown is the file you want to have the vectors written to. When you first importvectors for a new project, the default file name shown is the name of your project plus a “GPS” extension. To useanother file, press the “Change” button and choose another new or existing file name.

l Check that the “Beginning Vector ID” is set the way you wish. The Vector ID is an incrementing number assigned to vec-tors as they are imported into a project. When the vector import is finished, the next available number is saved in thejob’s project file. If additional vectors are imported later, the beginning ID number is set to this next available number.

l To select the vectors to import, press the “Select Baseline Files” button, and if necessary, browse to the directory con-taining your baseline files. Highlight one or more baseline files to import as shown below, and press the “Select” button.

Note that in this example, “Trimble GPSurvey” had been selected as the default baseline format type, therefore the“Files of type” field in this example file selection dialog above show “SSF” and “SSK” files. If another baseline format hadbeen chosen, the “native” extension for that format would have been shown.

l These selected files now appear in themain Import page dialog.


- 29 -

l Press the “Import” button to actually import the vectors into your data file. In this example, they are imported to the “Vec-torJob.gps” file shown above. This file will be automatically added to the Data Files List for the project. When you importto a particular file, and that file already exists, the importer routine will ask you if you want to “Append” vectors to thefile, or “Overwrite” the file.

l After successfully importing, and the vector file is created, the “Vector File” tab becomes active. You can review the vec-tors by opening that tabbed page. And of course, you can edit your vector data file from themain Data Files dialog.

l If the import process created errors or warnings, the “Error Log” tab becomes active and you can open that tabbed pageto review what problems were found. When errors are found, an output vector file is not created, (or overwritten). Whenonly warnings are issued, the vectors will be imported, however, themessages may indicate that problems were foundthat you will have to deal with yourself. For example, if imported station names exceed 15 characters, vectors will beimported anyway, but you will have to correct the station names by editing the vector file.

l Finally, to exit the GPS Vector importer, press the “Exit” button.

4.3 GENERAL NOTES ON IMPORTING VECTORS1. You are free to import the GPS vectors into any file you wish. As indicated in the previous section. The importer, by

default, chooses the name of your project and adds a “GPS” extension. If your project name is named SouthPark forexample, a file named SouthPark.gps is automatically offered as an import file, and it will be located in your project direc-tory. Whatever file name is chosen, that file namewill be stored in the job’s project file, and the next time you import vec-tors to that job, the same “Import Vectors To” file will be offered as the default.

For very small GPS jobs, youmay want to append imported vectors to your standard data file, the one having the “DAT”extension. In this case when running the importer, you can simply press the “Change” button, and browse to that file.Note that when that data file (or any file you are importing to) already exists, the importer will ask you if you want to“Append” or “Overwrite” the file. Be sure to select the “Append” choice to add the vectors to your file.

For very large GPS jobs, youmay want to create a new “Import Vectors To” file to hold vectors for each part of a project,or maybe for each day’s collection of vectors. To do this, you would press the “Change” button for each import and entera new data file name. Every time you import vectors to a new file, that file will be automatically added to the project’sData File List, and you can easily view or edit these files from the Input Data Files dialog.

2. You are free to change the “Beginning Vector ID” number in the Importer page to any numeric value you wish. Someusers take advantage of this by assigning special beginning serial numbers to different vector groups to further identifythem, for example “1000” to one group, “2000” to another, etc. These serial numbers are only an aid designed to help youmatch specific input vectors to the vectors listed in the output listings.

The vector ID serial number scheme, however, was also designed to be used with the “.GPS IGNORE” and “.GPSFREE” inline options described in Chapter 3 of this supplement. These inline options cause selected vectors to beignored or set free in the adjustment, so for that purpose, it is important that they remain unique.

3. When you press the “Select Baseline Files” button, the files selected are shown in the large window on the Import dialogpage. To remove one or more files from the list, highlight them and press the “Clear Highlighted” button. To clear all filesfrom the list, press the “Clear All” button.

4.4 IMPORTING FROM SELECTED BASELINE FILE FORMATSTheGPS Vector Importer can import baseline data from several vendor file formats. Each vendor’s files contain somewhat dif-ferent information, and each has different naming conventions. Besides that, some baseline files contain single vectors whileothers contain many.


- 30 -

The STAR*NET program handles alpha/numeric station names up to 15 characters in length. If the GPS Vector Importer rou-tine finds names longer than that, they are imported anyway, and warningmessages are posted by the importer in the ErrorLog. It is the responsibility of the user to edit the vector data files and correct any problems.

Also during the importing process, if embedded blanks are found in any station names, they are replaced with the underscore “_” character.

The following baseline vector formats, listed in alphabetical order, are currently supported by the vector importer routine. Theseformats may change from time to time, and new formats may be added. Also, as indicated at the end of this section, some ven-dors create baseline files that are already formatted in STAR*NET format. Therefore if you have questions about a baseline for-mat not mentioned here, or some change of an existing format, contact technical support at Starplus Software for themostcurrent information.

Ashtech

Ashtech vector files are binary files, and they begin with the alphabetic “O” character. Each file may contain a single vector, orit may contain multiple vectors.

Blue Book Gfile

This format is a standard established by NGS, the National Geodetic Survey. This is text file which is set up in a structured for-mat, and it normally contains many vectors.

Many GPS vendors have software available to convert their vector data to this format. Therefore for vendor file formats not cur-rently supported by the vector importer routine, we suggest they be converted to the Gfile format. Old formats, such as Trimble640 and Ashtech ASCII formats, will never be directly supported, and therefore these files can be converted to the Gfile formatto be imported for use in STAR*NET-PRO.

These files may have any name, but the importer routine expects an “NGS” extension. Since these files may be created frommany sources, you can, of course, specify any extension when selecting the vectors in the importer routine.

Geo Genius (and Geotracer)

TheGeoGenius baseline processor, a Spectra Precision product, stores its vectors in an integrated database that the importercannot directly use. It has several export formats, but it has a simple text export to a Geolab format which creates a file named“Geolab.txt.” GeoLab is a trademark of BitWise Ideas Inc. It is recommended you export to this format. See theGeoGeniusmanuals for details on exporting vectors.

TheGeotracer baseline processor is a Geodimeter/Spectra Precision product which stores its vectors in an integrated data-base that the importer cannot directly use. Just like with GeoGenius described above, you can export the vectors to a GeoLabformat which creates a file named “Geolab.txt.” Then in the importer, use the GeoGenius selection to import. See theGeo-tracer manuals for details on exporting vectors.

Leica (Ski-Pro and Lecia Geomatics Office)

The Leica baseline processors store vectors in an integrated database that the vector importer routine cannot directly use. Touse these baseline vectors, you can export them from the database to a standard text file. In Leica software, use the “ExportASCII Data” feature, and in the “Save as type” field, choose the “SKI ASCII file (*.asc)” selection and press the Export button.The Leica software allows you to export to any file name, but it defaults to an “ASC” extension unless you indicate otherwise.Likewise, the importer routine in STAR*NET also defaults to the “.ASC” extension.

When exporting, a tabbed dialog lets you set Export Settings. On theGeneral tab dialog, select “Baselines” for File Type,select “Cartesian” for Coordinate Type, and in the “Include items” area at the bottom of the dialog, the “Keywords” and “Header”boxes should be checked. Then finally, on the Baseline tab, make sure the “Covariance” item is checked so that vector weight-


- 31 -

ing is exported. Different versions of Leica software have slightly different options. See Leica SKI, SKI-PRO and LGO user’smanuals for details on exporting vectors.

Leica has an elaborate scheme for collecting station descriptors and attributes. See the next section in this chapter for specialoptions available to extract selected descriptor and attribute text from the Leica database into STAR*NET data.

MicroSurvey FieldGenius

MicroSurvey FieldGenius data collection software can collect RTK vector information as well as total station observation data.The built-in importer can extract GPS vector information from these field files on your computer. A “RAW” extension isassumed.

Vectors can be collected from several GPS equipment manufacturers, and can result from a conventional two-receiverbase/rover configuration, or from a single rover receiver connected via an NTRIP or GPRS server.

When using an NTRIP/GPRS virtual reference station, or when connecting to a permanent base receiver, users may need tomanually insert a .BASE inline option to establish any necessary base station data not explicitly defined in the raw file.

NovAtel

The NovAtel GPS baseline processor stores vectors in an integrated database that the importer cannot directly use. To getaccess to these vectors, youmust export the vector information to a text (ASCII) format. The export format is to the GeoLabformat. (GeoLab is a trademark of BitWise Ideas Inc.) This file may be given any name, and the extension will be “IOB” bydefault. See the NovAtel user’s manual for details on exporting baseline vectors.

Sokkia

The Sokkia GPS baseline processor stores vectors in binary files, one vector per file. These files may have any namewith an“SGL” extension.

TDS Survey Pro GPS

The TDS Survey Pro GPS is a data collector used to record RTK vector information as well as conventional observation data.The built-in importer can extract GPS vector information from these field files on your computer. A “RAW” extension isassumed.

This collector system can collect vectors from several brands of equipment (Trimble, Topcon, etc.). Note that these importedvectors may or may not include weighting information depending on what TDS options were set when the vectors wererecorded.

It is important to note that the vector information present in a the raw file is based on Cartesian Delta X, Y and Z vectors meas-ured from antenna to antenna, not ground to ground. The importer uses antenna height information in the field file plus approx-imate geographical positions calculated for all points in the file to convert the vectors into ground point to point Delta X, Y and Zmeasurements.

Topcon Tools – TVF Files

The Topcon Tools baseline processor saves vector information in an internal database. However the Topcon Tools has a built-in export to a simple comma-delimitated text file that can be imported into STAR*NET. This exported vector file has a “TVF”extension.

The exported file contains a list of vectors (with from & to point names, DX, DY & DZ vector components and x, y & z standarderrors and correlations). Following the vectors is a list of points (name, latitude, longitude, ellipsoid height and optional descrip-tor). The first line of the file contains an indicator of the “units” of the data (USFeet, Meters, etc.). As is the case with all importsto STAR*NET format, imported vectors will always be converted toMeters units.

Topcon – Turf Files (Old)


- 32 -

The Topcon baseline processor stores vectors in what is called “TURF” files. These file names have extensions beginning with“TS” and are appended with single character numbers (for example, TS0, TS1, TS2, etc.) Each file contains a single vector.

This file was created with very-early software from Topcon andmore than likely few if any files are still being created with thissoftware.

Trimble Data Exchange

The Trimble Geomatics Office (TGO) or Trimble Business Center (TBC) baseline processors store vectors in an integrateddatabase that the importer cannot directly use. You can export vectors directly from the TGO/TBC suite into a text file that, bydefault, has an “ASC” extension.

Briefly, this is the procedure: From the TGO/TBC processing screen, select all the vectors you wish to export. You can clickeach vector, select a group by dragging your mouse, or press Control-A to select all. Then choose “File>Export” to bring up anexport dialog, and select the “Trimble Data Exchange Format (*.ASC)” item. Press OK, giving a file name in the file selectiondialog. (Note that the export dialog was named “Observation Data Export Format” in early TGO versions.)

Trimble GPSurvey

The Trimble GPSurvey baseline processors store vectors in binary files. These files have “SSF” and “SSK” extensions and aresupported by the vector importer routine. Depending on the particular baseline processor used, the “SSF” files may contain oneor more vectors. The “SSK” files usually contain multiple vectors and are the result of kinematic processing.

Trimble TSC1/TSCe/TSC2

The Trimble TSC1, TSCe and TSC2 are data collectors used to record RTK vectors as well as conventional observation data.The importer will extract GPS vector information from these field files on your computer. A “DC” extension is assumed.

Note that these imported vectors may or may not contain weighting information depending on what collector options were setwhen the vectors were recorded.

It is important to note that the vector information present in the raw file is based on Cartesian Delta X, Y and Z vectors meas-ured from antenna to antenna, not ground to ground. The importer uses antenna height information in the field file plus approx-imate geographical positions calculated for all points in the file to convert the vectors into ground point to point Delta X, Y and Zmeasurements.

Waypoint

TheWaypoint software is an independent suite which processes baselines using raw files frommany manufacturer’s receiv-ers. The processed baseline vector files are then stored in files having “EXP” extensions (meaning exported). These are stand-ard text files and each file may contain many vectors. See theWaypoint user’s manual for details on exporting baselinevectors.

Other Formats

All the formats just described are either formats for themanufacturer’s “native” vector files, or formats for the “exported” vectorfiles.

Somemanufacturer’s have developed their own exports directly to STAR*NET format. Magellan and Javad have both createdexports to text files that can be read directly by STAR*NET-PROwithout modification.

To use one of these data files, simply “Add” it to the data file list using the Data Files dialog described in Chapter 5, “PreparingData” in themain STAR*NETmanual.

See thesemanufacturer’s operatingmanuals for details on exporting baseline vectors.


- 33 -

4.5 SPECIAL LEICA DESCRIPTOR EXTRACTION OPTIONSAs mentioned earlier, Leica has an elaborate scheme for collecting station descriptors and attributes. Special options havebeen added to the GPS importer to extract selected items of text from Leica’s vector file and construct descriptors for points.

As Leica users know, all lines in the text file exported from the Leica database begin with the “@”character. TheGPS vectorimporter routine can extract descriptor text from lines beginning with the following character codes: @1, @2, @3, @4 and@A.

There will be only single occurrences of @1, @2 and@3 lines for any station.

But theremay be up to four@4 lines per station. And theremay bemany @A lines, but the importer only works with the firstnine appearing for each station.

When “Leica” is selected as the baseline format in the vector importer, you will see a “Descriptor Specification” field on theimporter “Options” dialog page. In this field, you can specify what descriptor text items to import.

An item specification begins with a “/” forward slash character, followed directly by the item identifier. If you wish, separateeach specification item by one or more separator characters. (You can use any character except a “/” character.) The examplespecification string below indicates that you want to extract text from: the@1 line, the@2 line, the first and third@4 lines, andthe sixth and seventh@A lines:

In the example above, each item was separated from the next by a comma and a space.

In the Leica vector file, the “@A” line always contains two parts, a “prompt string” (the part to the left of the equal sign), and thedescriptor text (the part to the right of the equal sign). The specifications shown above extracts just the descriptor text part.You can extract the “prompt string” for any of the nine “@A” lines by entering a specification such as “/A3P” which, in this case,extracts the prompt for the third line.

In the example above, six text strings would be extracted from selected fields in the Leica file and concatenated into a singlepoint descriptor. The separators shown in the specification (a comma plus space in this example) would appear in the descrip-tor separating the parts.

4.6 OPUS STATIONSOPUS stations are points that have a full covariancematrix. The NGS OPUS service was the instigator for this feature, but theconcept is general purpose. Any source for points with full covariance information is acceptable, even Starnet (the "dump" filecontains full station covariance as a result of adjustment).

OPUS station are entered in three line sets. The first line is a normal C, CH, P, or PH data record specifying the station's loca-tion. The second and third lines contain the covariance data. The form of these two lines is similar to the covariance data forGPS vectors: values are given as standard errors and correlations, or as variances and covariances. No other data types mayinterleave with the station set.

Whereas GPS distinguishes the type of covariance data by the inline option .GPSWEIGHT { COVARIANCE | STDERRCOR-RELATION } with either type onG2 andG3 lines, the station covariance data is distinguished by different command codespairs:











- 34 -

WS1 - standard errorsWS2 - correlations

WV1 - variancesWV2 - covariances

The order of value entry is dependent on the current coordinate order specified by the project options and the inline option.ORDER.

Given north is Y and east is X, the possible sets are...

By Standard Error / Correlation:

C PNYXZWS1StdErr_YStdErr_XStdErr_ZWS2Correl_YXCorrel_YZCorrel_XZ

C PNXYZWS1StdErr_XStdErr_YStdErr_ZWS2Correl_XYCorrel_XZCorrel_YZ

C PNYXWS1StdErr_YStdErr_XWS2Correl_YX

C PNXYWS1StdErr_XStdErr_YWS2Correl_XY

By Variance / Covariance:

C PNYXZWV1Var_YYVar_XXVar_ZZWV2Covarl_YXCovarl_YZCovarl_XZ

C PNXYZWV1Var_XXVar_YYVar_ZZWV2Covarl_XYCovarl_XZCovarl_YZ

C PNYXWV1Var_YYVar_XXWV2Covarl_YX

C PNXYWV1Var_XXVar_YYWS2Covarl_XY

The first line of the set (C, CH, P, PH)may have an optional descriptor, but it cannot have weight data as a normal coordinatedata line.

StdErr/Correl and Var/Covar are equivalent. The relation between variance and correlation is: CoVar_xy = Correl_xy * StdErr_x* StdErr_y

There is amissing feature in current OPUS support. The NGS OPUS service, being based onGPS observations, produces ahighly optimistic covariancematrix for the rover station. Like Starnet GPS data, the OPUS station requires amultiplier factor togive reasonable weights.


- 35 -

Inline Option: .OPUS { FACTOR | CENTERING } [ number [ VERTICAL number ]]TheOPUS importer provides ameans to set weight factors similar to the .GPS FACTOR inline option . The dialog lets the usersupply the factors and a .OPUS inline option is automatically inserted into the output Starnet data file.

The syntax for the inline option is a follows:

.OPUS { FACTOR | CENTERING } [ number [ VERTICAL number ] ]

OPUS, FACTOR, CENTERING, and VERTICAL can be abbreviated down to their least unique values.

Examples:

.OPUS FACTOR -- revert to that specified on the GPS options dialog

.OPUS FACTOR 100 -- Multiply X,Y,and Z standard errors by 100

.OPUS FACTOR 100 V 200 -- Multiply X,and Y standard errors by 100 and Z by 200

.OPUS CENTER -- revert to that specified on the GPS options dialog

.OPUS CENTER 0.001 -- Increase X, Y, and Z standard errors by propagating .001

.OPUS CENTER 0.001 V 0.002 -- Increase X and Y standard errors by propagating .001 and Z by 0.002

The opus factor is applied by multiplying the station standard errors by the factor. If both factoring and centering is applied, fac-toring is applied first.

Centering error is propageted by square root of the sum of squares:

Standard Error of X = SE (given)Horizontal Centering value = C (given)Adjusted Standard Error of X = Sqrt( SE * SE + C * C )

If the opus station is stated in covariance terms, the covariancematrix is first converted to standard error / correlation form.Factors and centering is applied to the standard errors; correlation remains constant.

Sample Data


- 36 -

# Project options:# 3D# Meters# Grid, NAD83, CA Zone 3 (0403)########################################### #### OPUS Data #### ###########################################.data onC 1 646210.001 1844190.001 100.001#CH 1 646210.001 1844190.001 68.001#P 1 37-48-14.9734386 122-16-10.1308614 100.00100#PH 1 37-48-14.9734386 122-16-10.1308614 68.00100# the following two weight sets are equivalent# only one can be on.data onWS1 0.001 0.002 0.003 # Standard ErrorsWS2 0.100 0.200 0.300 # Correlations.data offWV1 0.0000010 0.0000040 0.0000090 # VariancesWV2 0.0000002 0.0000006 0.0000018 # Covariances.data off.data on# additional observations to point 1# their weights are the same# if all weights are the same for three observations# the average should be 646210.002 1844190.002 100.002C 1 646210.002 1844190.002 100.002WS1 0.001 0.002 0.003WS2 0.100 0.200 0.300C 1 646210.003 1844190.003 100.003WS1 0.001 0.002 0.003WS2 0.100 0.200 0.300.data off.data off# Another additional observation to point 1.# If the above additions are off and this on# the average would be 646210.002 1844190.002 100.002# if the weights were equal.# But the weights here are greater, so the average# is closer to this observation.C 1 646210.003 1844190.003 100.003WS1 0.0005 0.0015 0.0025WS2 0.100 0.200 0.300.data off.data onC 2 646300.0 1844230.0 110.0WS1 0.001 0.002 0.003WS2 0.100 0.200 0.300.data off.data onC 3 646360.0 1844320.0 120.0WS1 0.001 0.002 0.003WS2 0.100 0.200 0.300.data off#########################################


- 37 -

## #### Conventional Observations #### ###########################################.data on.3dDV 1-2 99.0001 84-12-15.17M 1-2-3 16-57-08.73 199.5127 84-14-53.19M 1-3-4 31-03-41.97 81.8660 79-26-36.47DV 2-3 108.6368 84-43-07.94M 2-3-4 94-23-35.81 74.8191 86-10-04.45M 2-4-1 53-15-31.27 99.0001 95-47-47.58DV 3-4 136.1509 92-06-17.33M 3-4-1 17-46-11.89 199.5127 95-45-12.33M 3-1-2 15-23-44.19 108.6368 95-16-55.06DV 4-1 81.8660 100-33-25.76M 4-1-2 78-43-38.03 74.8191 93-49-57.63M 4-2-3 52-26-28.12 136.1509 87-53-46.47.data off########################################### #### GPS Observations #### ###########################################.data onG1 1-2 57.8585 19.9092 77.8270G1 1-3 148.9647 -2.2344 132.7021G1 1-4 66.5955 -36.9673 30.0084G1 2-3 91.1062 -22.1436 54.8750G1 2-4 8.7370 -56.8765 -47.8187G1 3-4 -82.3692 -34.7329 -102.6937.data off########################################### #### Sideshots #### ###########################################.data on.3dSS 2-1-SS1 30-00-00 30.000 90-00-00SS 2-1-SS2 50-00-00 50.000 90-00-00SS 2-1-SS3 70-00-00 70.000 90-00-00.gps ssG1 2-GPS_SS1 -62.4405 60.5783 23.0533G1 2-GPS_SS2 -49.7530 81.5096 54.5969G1 2-GPS_SS3 -20.3143 93.5383 87.9655.data off


- 38 -

Chapter 5: GEOID HEIGHTS AND VERTICALDEFLECTIONS

- 39 -

CHAPTER 5: GEOID HEIGHTS AND VERTICALDEFLECTIONS5.1 OVERVIEWBy default, the averageGeoid Height value that you specify in the Project Options Adjustment dialog is assigned to every sta-tion. In the standard STAR*NET edition, this constant value is used for the entire project.

However in the STAR*NET-PRO edition, you can assign a different geoid height value to each individual station. In addition,you can perform modeling for both geoid heights and vertical deflections during an adjustment.

5.2 THE “GH” AND “GT” DATA TYPE LINESGH At Geoid Height [Vert Def-North] [Vert Def-East]GT At Vert Def-North Vert Def-East

The “GH” data line allows you to assign a geoid height value to a specific station, and if you also know the vertical deflectionsat that station, you can enter them on the same line. The “GT” line (Geoid Tilt) is used to enter just vertical deflections for a sta-tion.

Since geoid heights are usually published inmeters, a geoid height assigned using this data linemust also be entered inmeters, not necessarily the units of the project. If your project is run in units other thanmeters however, any review of thesegeoid heights in your listing are converted to the project units for consistency.

Vertical deflections define known north and east deflections from a vertical line normal to the ellipsoid. They are always enteredin DMS seconds. A positive deflection in the north direction, for example, means that the top of a plumb line leans north of itsbottom when compared to a vertical line normal to the ellipsoid passing through the point.

The following “GH” and “GT” lines illustrate the assignment of specific geoid heights and/or vertical deflections to three individ-ual stations. These lines may be entered anywhere in any of the data files that will be processed in the adjustment.

GH CONCORD -32.76 # assign –32.76 geoid height to CONCORDGH MRK009 -32.58 2.5 -3.8 # assign both geoid height and deflectionsGT BRIDGE 3.6 -4.6 # assign just vertical deflections

Geoid height values explicitly defined for any of these stations take precedence over the default value from the AdjustmentOptions dialog. In addition, geoid height and vertical deflections set by these data lines take precedence over any geoid heightor deflection values calculated by modeling.


- 40 -

5.3 MODELING OPTIONS

Geoid ModelingBefore geoidmodeling can be actually preformed, youmust first create one or more geoid files in a “neutral” STAR*NET formatusing the “StarGeoid” utility program included with this installation. This utility creates “neutral” geoid files by extracting geoiddata from files supplied by government agencies such as the NGS in the United States and theGeodetic Survey Division ofNatural Resources Canada. See detailed instructions on using the “StarGeoid” utility program later in this chapter.

Once you have created one or more “neutral” geoid files as mentioned above, you can simply check the “Perform GeoidMod-eling” box in the Project Options/Modeling dialog to direct STAR*NET to perform geoidmodeling during subsequent adjust-ments.

With the Perform GeoidModeling box checked as shown above, choose how the “neutral” geoid files should be selected in themodeling process during the adjustment:

l Automatic Selection from “GHT” Files – This choice directs the program to look in the “Models” subdirectory of yourinstallation directory and automatically choose a geoid file with a “GHT” extension that covers the extent of your project.


- 41 -

l Select Specific Geoid File – This choice allows you to select a “specific” geoid file to use with your project adjustment.Simply browse for any STAR*NET formatted geoid file. It can be located anywhere and have any name.

Also in the GeoidModeling options above, you can choose whether or not to havemodeled geoid heights shown in the outputadjustment listing file.

General Notes About GeoidModeling:

1. When you choose the “automatic” geoid file selectionmethod, STAR*NET will look through all geoid files having a“GHT” extension in the “Models” directory and choose the first one it finds that includes the geographical extent of yourproject. If a file cannot be found that includes the extent of your project, the adjustment terminates with an appropriateerror message. It is recommended that you name your geoid files with descriptive names such as “Calif-Nevada.ght” or“Florida.ght.”

2. Whenever government agencies issue newer geoid data, you will likely want to create all new “GHT” files based on newundulation data (for example, updating from NGS Geoid96 to the newer Geoid99 data). When you do this, be sure to firstdelete all your old GHT files from the “Models” directory so there is no chance that wrong undulation data will be chosenby the STAR*NET program.

3. When you update your geoid files using newer undulation data, youmay want to continue using older geoid data forsome projects that are still in progress. In this case, instead of deleting an old “GHT” file used for the project, simplyrename it to some descriptive namewithout the “GHT” extension (or with a different extension) such as “Flor-idaGeoid.1993.” And then in theModeling options, choose the “Select Specific Geoid File” option and specify that newname.

Note that neutral geoid files with and without the “GHT” extension can be safely mixed together in the “Models” directorysince the “Automatic” selectionmethod looks only for files with “GHT” extensions. For simplicity we recommend keep-ing all geoid files in the “Models” directory, however you can place a geoid file that is only referenced by the “Select Spe-cific Geoid File” option anywhere.

4. Except for stations having their geoid heights pre-defined by the GH data type, geoidmodeling is performed on all net-work stations every iteration. This assures that, as each stationmoves around during the adjustment, even though asmall amount, the correct geoid height will have been computed when the adjustment is finished.

5. Geoidmodeling is not performed on sideshot stations (those defined using the “SS” data type). As a good approx-imation, the geoid height computed at the instrument station is used as the geoid height for the sideshot station.

6. Even though you invoke geoidmodeling, you should still enter a reasonably correct geoid height in the Adjustmentoptions dialog. That geoid height will be used for computing approximate elevation values from the unadjusted vectordata.

7. If you are running an adjustment using NAD27 in the United States, geoidmodeling is disabled. By definition, the geoidand ellipsoid for that system are the same.

Vertical Deflection ModelingJust as with geoidmodeling, before vertical deflectionmodeling can be preformed, youmust first create one or more verticaldeflection files in a “neutral” STAR*NET format using the “StarGeoid” utility program. This utility creates “neutral” vertical deflec-tion files by extracting data frommodels supplied by government agencies such as the NGS in the United States and theGeo-detic Survey Division of Natural Resources Canada. See detailed instructions on using the “StarGeoid” utility program later inthis chapter.


- 42 -

Once you have created one or more “neutral” vertical deflection files, you can simply check the “Perform Vertical DeflectionModeling” box in theModeling dialog to direct STAR*NET to perform vertical deflectionmodeling during subsequent adjust-ments.

With the Perform Vertical DeflectionModeling box checked as shown above, choose how the “neutral” vertical deflection filesshould be selected during the adjustment:

l Automatic Selection from “VDF” Files – This choice directs the program to look in the “Models” subdirectory of yourinstallation directory and automatically choose a vertical deflection file with a “VDF” extension that covers the extent ofyour project.

l Select Specific Deflection File – This choice allows you to select a “specific” vertical deflection file to use. Simplybrowse for any STAR*NET formatted vertical deflection file. It can be located anywhere and have any name.

Also in the Vertical DeflectionModeling options above, you can choose whether or not to havemodeled vertical deflectionsshown in the output adjustment listing file.

l Apply Constant Deflections Only – Alternately, if you know that the geoid plane in your project area has a fairly constanttilt or slope (i.e. it doesn’t undulate), you can choose to apply constant deflections only.

If you perform geoidmodeling and your network includes conventional data, it is highly recommended that you also perform ver-tical deflectionmodeling (or at least specify constant deflections if the geoid plane is at a somewhat constant tilt). Verticaldeflections affect zenith angle, turned angle, direction and azimuth observation computations in grid jobs. These computationsrely on knowing the relationship between gravity (plumb line) at a point and the normal to the ellipsoid at the same point.

Vertical deflectionmodeling is particularly important when combining conventional observations (gravity based) andGPS vec-tors (ellipsoid based) in the same adjustment.

General Notes on Vertical DeflectionModeling:

1. When you choose the “automatic” deflection file selectionmethod, STAR*NET will look through all deflection files hav-ing a “VDF” extension in the “Models” directory and choose the first one it finds that includes the geographical extent ofyour project. If a file cannot be found that includes the extent of your project, the adjustment terminates with an appro-priate error message. It is recommended that you name your deflection files with descriptive names such as “Calif-Nevada.vdf” or “Florida.vdf.”

2. As mentioned before, whenever government agencies issue newer geoid and/or deflectionmodels data, you will likelywant to create all new modeling files based on new undulation data. When you create new vertical deflection files, besure to first delete all your old VDF files from the “Models” directory so there is no chance that wrong deflection data willbe chosen by the STAR*NET program.

3. When you update your deflection files using newer undulation data, youmay want to continue using older deflectiondata for some projects that are still in progress. In this case, instead of deleting an old “VDF” file used for the project,simply rename it to some descriptive namewithout the “VDF” extension (or with a different extension) such as “Flor-idaDef.1993.” And then in theModeling options, choose the “Select Specific Geoid File” option and specify the newname.

Note that deflection files with and without the “VDF” extension can be safely mixed together in the “Models” directorysince the “Automatic” selectionmethod looks only for files with “VDF” extensions. Although for simplicity we rec-ommend keeping all deflection files in the “Models” directory, you can place a deflection file that is only referenced bythe “Select Specific Deflection File” option anywhere.

4. Except for stations having their vertical deflections pre-defined onGH or GT data type lines, deflectionmodeling is per-formed on all network stations every iteration. This assures that, as each stationmoves around during the adjustment,


- 43 -

even though a small amount, the correct vertical deflection values will have been computed when the adjustment is fin-ished.

5. If you are running an adjustment using NAD27 in the United States, geoidmodeling is disabled because by definition thegeoid and ellipsoid for that system are the same. And therefore, government supplied geoid and deflectionmodel datadoes not exist. However in an NAD27 job, if you can determine average north and east deflections one way or another,you are still allowed to enter average deflection values in the Project Options/Adjustment dialog and those deflectionswill be applied.

5.4 USING THE STARGEOID UTILITY PROGRAMThe StarGeoid program is a stand-alone utility used to extract geoid undulation data and vertical deflection data from threekinds of file formats:

1. United States National Geodetic Survey files (Geoid96, Geoid99, Geoid03, etc.)

2. Canadian Geodetic Survey Division files (GSD95, HT97, etc.)

3. World files (based on NGS binary “BIN” file format)

Using the extracted data, the utility builds geoid or vertical deflection files in “neutral” formats and places them in your “Models”subdirectory. As described in the last two sections, whenmodeling is performed, these “neutral” files are used during the adjust-ment to determine the geoid height and/or deflection values.

To run the StarGeoid utility, press theStartmenu, select Programs>MicroSurvey>StarNet V6, and then click theStarGeoidprogram selection. Follow the general procedure shown below:

1. Select to extract either geoid heights or vertical deflections.

2. Select the type of model source to extract data from –USA, Canadian orWorld.

3. Enter the desired boundaries as geodetic positions in D-M-S or DD.MMSS format paying attention to the rules for signsdisplayed below the latitude/longitude fields.

4. Browse for an “Input Folder” containing themodel files from which the geoid height or vertical deflection information willbe extracted (i.e. NGS files, etc.).


- 44 -

5. Browse to a folder and then enter a file name to receive the extracted geoid height or vertical deflection information.

6. Finally press the “Build” button to actually perform the extraction process!

Using StarGeoid to Create “GHT” Geoid Height FilesThe following illustrates the appearance of the utility dialog with all values entered. Pressing the “Build” button performs thegeoid height data extraction process.

Example settings shown in the dialog indicate that geoid height information is to be extracted from USA model files (Geoid96,Geoid99, etc.). The bounding geodetic positions will cause information to be extracted from a region including all of Californiaand Nevada. Geodetic positions can entered to whole degrees for convenience. However minutes and seconds may beincluded, for example 31-22-55.7 or 31.22557.

The input model source files are located in a “C:\GeoidData\Geoid99” folder, and the extracted geoid data will be written to“C:\Program Files\MicroSurvey\StarNet\Models\CalNevada.ght” in this example dialog.

Notes on Extracting Geoid Height Data:

1. When specifying the Output File, the initial default directory offered will be the “Models” subdirectory of the install directory.This is where you normally want these files placed so that they can be “automatically” selected during the adjustment.

2. By default, output files are created with a “GHT” extension. To create a file with a different extension (or no extension),select the “*.*” file type in the “Files of Type” field in the file selection dialog.

3. See additional notes on the following pages relating to particular details on the USA, Canada andWorld model data.

Using StarGeoid to Create “VDF” Vertical Deflection FilesThe following illustrates the appearance of the utility dialog with all values entered. Pressing the “Build” button performs the ver-tical deflection data extraction process.


- 45 -

Example settings shown in the dialog indicate that vertical deflection information is to be extracted from USA files (Deflec96,Deflec99, etc.). The bounding geodetic positions will cause information to be extracted from a region including all of Californiaand Nevada. Geodetic positions can entered to whole degrees for convenience. However minutes and seconds may beincluded, for example 31-22-55.7 or 31.22557.

The input model files are located in a “C:\GeoidData\Deflec99” folder, and the extracted deflection data will be written to “C:\P-rogramData\MicroSurvey\StarNet\V6\Models\CalNevada.vdf” in this example dialog.

Notes on Extracting Vertical Deflection Data:

1. When specifying the Output File, the initial default directory offered will be the “Models” subdirectory of the install directory.This is where you normally want these files placed so that they can be “automatically” selected during the adjustment.

2. By default, output files are created with a “VDF” extension. To create a file with a different extension (or no extension),select the “*.*” file type in the “Files of Type” field in the file selection dialog.

3. See additional notes on the following pages relating to particular details on the USA, Canada andWorld model data.

5.5 GEOID MODEL DATA

United States NGS Geoid and Deflection Model Data The StarGeoid utility handles data from all currently available NGS models. Depending on whether geoid height or verticaldeflection information is to be extracted, the program examines the names and/or extensions of the source files to determine ifthe proper files are present, and if so, what method to use to extract the data.

Files for the Geoid99 release (and newer releases) begin with a “G” and have a “BIN” extension. Older files (Geoid96 and ear-lier) simply have a “GEO” extension.

Files for the Deflec99 release (and newer releases) come in pairs. Each file in the pair begins with “E” and “X” respectively, andall files have a “BIN” extension. Older deflection files (Deflec96 and earlier) also come in pairs, and each file in the pair simplyhas an “ETA” and “XII” extension respectively.

It is important to keep NGS geoid and deflectionmodel files from different years in separate folders! When you select the “InputFolder” in the StarGeoid utility, you are actually choosing to extract information frommodel files for a specific year.


- 46 -

Note that if your specified bounding region spans two or more NGS files, the program extracts data from parts of each file tocreate a single “GHT” or “VDF” file.

National Geodetic Survey geoidmodel files can be downloaded from the NGS web site.

Phone: 301-713-3242 or the web site is: www.ngs.noaa.gov.

At the web site, click “Download Software” and then on the next page, scroll down until you see the “GEOID03” title (or what-ever geoid file system you want) and click the title. This takes you to the download page. Then scroll down until you see thelocation you want such as “Conterminous United States” (or “Alaska,” etc.). Directly below you will see a list of “Binary Grids”available. Click a particular grid file (Grid #1, Grid #2, etc.) to download it. Repeat to download grid files for additional areas.

Canadian Geoid Model DataAfter mid-year 2001, a geoidmodel namedCGG2000 was issued in Canada. This model has a “BIN” format compatible withthe USA “BIN” format. The original combination “SLV/BIN” format used in Canada is still available and can be used as detailedin the next paragraph. But when extracting data from the new CGG2000.bin model, select the “USA” Type in the StarGeoid util-ity and follow the instructions for the USA extraction. Currently, there is no vertical deflectionmodeling provision in STAR*NETusing this model. Note that as of the beginning of 2007, the CGG2000.bin model is not actually on the Natural Resources Can-ada web site but will be copied to their FTP site if you simply contact them (see contact information on next page). TheCGG2000.bin model and additional models using a new Canadian-defined “BYN” format are in the process of being created andwill be added to their website later in 2007 and/or 2008.

Prior to mid-year 2001, Canadian geoid files names for regions below 72 degrees latitude begin with one of more of the fol-lowing names: GSD91, GSD95, HT97 or HT1_01. Geoid files for regions above 72 degrees latitude begin with POL91 or Arc-tic96. Eachmodel includes a pair of files having “SLV” and “BIN” extensions. So for example, if you only have the “HT97” geoidmodel data on your computer, you will have two data files named “HT97.slv” and “HT97.bin.”When you use the StarGeoid util-ity to extract data from Canadian geoidmodels, it first looks in the “Input Folder” for a single pair of “SLV” and “BIN” files thatcontains the geographical area selected by your latitude and longitude boundaries. If found, the program then extracts the geoidinformation.

Note that when extracting vertical deflections to create a “VDF” file, the StarGeoid program uses the geoidmodels to calculatevertical deflections based on formulas provided by Natural Resources Canada. No separate vertical deflectionmodels exist.

Keep these geoidmodels for different years in separate folders! When you select the “Input Folder” in the StarGeoid utility, youare actually choosing to extract information from geoidmodels for a specific year.

For Canadian geoidmodels and information, contact the Canadian Geodetic Service.

Phone: 613-995-4410 or the website is: www.geod.nrcan.gc.ca.

World Geoid Model DataThe NIMA/NASA EGM96 Earth Gravity Model is available via certain internet sources. This is a geoidmodel with geoid heightinformation at every 15minute increment covering the globe. Themodel was created in a somewhat bulky text-based form.

MicroSurvey has a version of this model available in amore compressed “BIN” format, the same format employed by the new-est NGS Geoid99 andGeoid03model files. This model file is available by contactingMicroSurvey Software Inc .

MicroSurvey also has a version of the EGM2008models (1minute or 2.5minute grids) available for download in the EGM96binary .bin format which can be extracted using this option. Contact MicroSurvey Software Inc for details.

To extract from the supplied world model, select “World” as the type in the StarGeoid utility. Extracting geoid height data fromthis model is handled the same as from USA geoidmodel files having “bin” extensions. The only difference is that youmust

http://www.ngs.noaa.gov/

http://www.geod.nrcan.gc.ca/


- 47 -

use international sign conventions (negative latitudes south of equator and negative longitudes west of Greenwich) for theentered bounding geodetic positions to assure that the location of the extraction region in the world is uniquely defined.

The extraction process creates a “GHT” file as usual. For example, if you extract an area including Singapore, youmight namethe file “Singapore.ght.” With this file placed in your “Models” subdirectory, you can simply turn onGeoidModeling in theProject Options/Modeling dialog, and geoidmodeling will be performed during an adjustment.

There is no provision for performing Vertical Deflectionmodeling using theWorld type.


- 48 -

Chapter 6: GPS OUTPUT LISTINGSECTIONS

- 49 -

CHAPTER 6: GPS OUTPUT LISTING SECTIONS6.1 OVERVIEWThis chapter illustrates the additional listing sections created when you run adjustments containing GPS vector observations.Some of these listing sections are optional andmay be turned on or off by settings in the Project Options/Listing dialog. Othersections are always there and contain additional information due to the existence of the vectors.

You should thoroughly review Chapter 8 “Analysis of Adjustment Output” in themain STAR*NETmanual for a complete dis-cussion of output listings for adjustments which include conventional observations. That chapter also discusses the StatisticalSummary listing and Chi Square test in detail.

6.2 SUMMARY OF UNADJUSTED INPUT OBSERVATIONSThis section includes a review of controlling input stations and all unadjusted input observations. The first part of this sectionconsists of any fixed or partially fixed coordinates that control the network constraints.

When network constraints are entered as coordinate values, the review of the entered stations shows the information as coor-dinates. When geodetic positions are entered as constraints, as they often are in networks that contain GPS vectors, thereview of entered stations will show the latitudes and longitudes as illustrated below.

Summary of Unadjusted Input Observations========================================

Number of Entered Stations (Meters) = 5Fixed Stations Latitude Longitude Elev Description0038 33-06-59.983100 112-59-00.927810 657.0410 Rock0040 33-05-55.750960 112-38-57.752370 250.8570 ADOT 80.1360043 32-54-32.648860 112-58-19.794590 221.4100 MIDPartially Fixed Latitude Longitude Elev Description

N-StdErr E-StdErr StdErr0041 32-55-33.146010 112-40-40.571420 250.2870 Giant

FREE FREE FIXED0042 32-55-04.583950 112-54-20.124750 219.2800 Crossing

FREE FREE FIXEDetc..

Only the controlling coordinates or positions “entered” by the user are reviewed in this listing, not “approximate” coordinatesautomatically computed by the program.

The unadjusted GPS vector observations are reviewed next. The vector components (Delta X, Y & Z values) and weightingsare listed as earth-centered Cartesian values, just as originally imported. By default, however, the reviewed component weight-ings are expressed as standard errors and correlations even though weightings may have been imported as covariances. Ingeneral, most surveyors wish to see standard errors rather than covariances since they are easier to understand andmoreeasily related to standard errors of conventional observations. If you prefer to see weightings in the listing expressed as covar-iances, a setting in the GPS options dialog allows this to be done.

The text shown in parentheses above each vector is the vector identifier. It includes a vector number and any other descriptiveinformation that may have been available when it was imported. This text helps you relate vector listings to input vector data.


- 50 -

Number of GPS Vector Observations (Meters) = 120

From DeltaX StdErrX CorrelXYTo DeltaY StdErrY CorrelXZ

DeltaZ StdErrZ CorrelYZ(V117 Day124(1) 15:34 00010002.SSF)0001 1222.0791 0.0044 0.09040002 58.5048 0.0047 -0.0380

818.0998 0.0045 -0.0780(V109 Day124(3) 19:24 00010003.SSF)0001 1058.2695 0.0051 0.15270003 -804.0274 0.0068 0.0131

-563.1984 0.0070 -0.3813(V116 Day124(1) 15:34 00010004.SSF)0001 1762.3854 0.0046 0.12910004 -667.0269 0.0051 -0.0615

39.7325 0.0048 -0.1300(V108 Day124(3) 18:33 00010005.SSF)0001 1020.0136 0.0049 0.10820005 -6324.0743 0.0060 0.0047

-8367.1653 0.0066 -0.3507(V107 Day124(3) 18:38 00010037.SSF)0001 2129.2314 0.0046 0.07200037 -3512.9613 0.0052 0.0071

-3642.2568 0.0055 -0.2312(V115 Day124(2) 17:22 00020003.SSF)0002 -163.8113 0.0048 0.18220003 -862.5286 0.0053 -0.0947

-1381.2898 0.0046 -0.1410etc...

The vector component standard errors shown in this listing include the affects of any “Factoring” and “Centering” set in the GPSoptions dialog or by inline options. The vector and standard error values are displayed in the units of the project.

A setting in the GPS options dialog controls the order in which these vectors are listed. The vector review shown in the exam-ple listing above is sorted by station name.

6.3 STATISTICAL SUMMARYThe statistical summary contains some very important information, especially when you aremixing conventional observationsandGPS vectors in the same adjustment. The listing includes a summary line for each type of observation existing in your net-work (i.e. angles, distances, zeniths, GPS vector components) indicating how well that type of data fit into the adjustment. Theexample Statistical Summary shown below is for a project having 120GPS vectors but no other types of observations.


- 51 -

Adjustment Statistical Summary==============================

Convergence Iterations = 4

Number of Stations = 45

Number of Observations = 360Number of Unknowns = 128Number of Redundant Obs = 232

Observation Count Sum Squares Errorof StdRes Factor

GPS Deltas 360 158.33 0.83

Total 360 158.33 0.83

Adjustment Passed the Chi Square Test at 5% Level

The first line indicates how many iterations were performed to get convergence.

The next item indicates how many stations are in the network. Any station included in your data, but not connected to other sta-tion by an observation, is not counted.

The next three lines indicate the numbers of observations, unknowns and redundant observations in the network. A single GPSvector includes three observations, the X, Y and Z components. Therefore, the 120GPS vectors in this network create a totalof 360 observations. Any vector in the adjustment that has been set free is not counted.

The “Error Factor” shown for GPS vectors is very important. In general, when residuals in your adjustment are approximatelyequal to your weighting expectations (the standard errors), the value of the Error Factor will be approximately 1.00. If your vec-tor residuals seem reasonable but the error factor for the vectors is much higher than 1.00 (for example 15), youmay need to“factor” your imported vector standard errors to make themmore realistic. This is particularly important whenmixing con-ventional observations (angles, distances etc.) with GPS vectors. For details on factoring GPS standard errors, see Chapter 3,“GPS Options” in this supplement.

For a complete description of the Statistical Summary, including a discussion on Error Factors, Total Error Factor and the ChiSquare test, read the “Adjustment Statistical Summary” section in Chapter 8 of themain STAR*NETmanual.

6.4 ADJUSTED OBSERVATIONS AND RESIDUALSOutput relating to adjusted observations and residuals consists of two sections.

The first section lists any scale and rotation transformations that you have asked to be solved or set in the GPS options dialog.A note on each line shows a status for each transformation: None, Solved, Set by User, or Unsolvable. An “Unsolvable” statusmeans that a requested transformation could not be solved because of inadequate constraints. When no transformations arerequested, this section will not be present.

The second section lists adjusted GPS vectors and their residuals. All vector, residual and standard error components havebeen rotated from XYZ earth-centered Cartesian components to local-horizon North, East and Up components. This orientationis easy to understand and very easily related to conventional observations.


- 52 -

Adjusted Observations and Residuals===================================

Adjusted GPS Vector Observations Sorted by Names (Meters)

Datum Transformations StdDevScale Factor 0.999995829182 : 4.170818 PPM 0.1393 (Solved)Rotation Around North Axis : 0.667364 Sec 0.0482 (Solved)Rotation Around East Axis : 0.058706 Sec 0.0438 (Solved)Rotation Around Vert Axis : 0.371553 Sec 0.0288 (Solved)

From Component Adj Value Residual StdErr StdResTo(V117 Day124(1) 15:34 00010002.SSF)0001 Delta-N 975.7430 -0.0010 0.0044 0.20002 Delta-E 1101.8684 0.0016 0.0043 0.4

Delta-U 0.7376 -0.0012 0.0049 0.2Length 1471.7979

(V109 Day124(3) 19:24 00010003.SSF)0001 Delta-N -649.9085 0.0088 0.0028 3.1*0003 Delta-E 1288.4280 0.0024 0.0051 0.5

Delta-U -34.0018 0.0024 0.0079 0.3Length 1443.4624

etc...

The vector standard error components shown in this listing section include the affects of any “Factoring” and “Centering” set inthe GPS options dialog or by inline options. Adjusted vectors, residuals and standard errors are listed in the units of the project.

A setting in the GPS options controls the order in which adjusted vectors are listed. The adjusted vector listing shown in theexample above is sorted by station name.

As discussed in Chapter 8 “Analysis of Adjustment Output” of themainmanual, you should carefully examine the residuals tosee if they appear reasonable. The listing shows a Standardized Residual (StdRes) which is simply the residual divided by thestandard error. Standardized Residuals larger values than 3 are flagged with an asterisk character (*) to help you find vectorshaving potential problems.

6.5 VECTOR RESIDUAL SUMMARYOutput for this section is a compressed one-line-per-vector table which lists residuals in various ways. By choosing a listingsetting in the GPS options dialog, this summary may be sorted by 3D residuals, 2D residuals, Up residuals, or it may be simplylisted in the same order as other vector shown in the output listing. This entire sectionmay also be eliminated from the listingfile if you choose.

This summary is useful for finding the “worst” vectors in a network. For example, if you are particularly interested in the size ofhorizontal residuals (made up of North and East residuals), you could set this table to be sorted by 2D residuals. The examplebelow is sorted by 3D residuals, largest residuals listed first.


- 53 -

GPS Vector Residual Summary (Meters)(Sorted by 3D Residual Length)

(Vectors Marked with (*) are Free)

From To N E Up 2D 3D Length VectID0009 0013 0.000 0.010 0.021 0.010 0.023 4875 *530011 0013 0.002 0.001 0.021 0.002 0.021 1672 510011 0012 -0.005 -0.003 -0.019 0.006 0.020 10468 *920009 0015 -0.002 0.011 0.012 0.011 0.016 9825 520012 0013 -0.002 -0.002 -0.015 0.003 0.015 10262 900031 0033 -0.008 -0.002 0.011 0.009 0.014 2023 90008 0012 -0.006 -0.004 -0.012 0.007 0.014 5740 950018 0036 -0.002 0.006 -0.011 0.007 0.013 9709 640007 0009 0.003 0.011 0.006 0.011 0.013 3201 550029 0031 0.007 0.002 -0.010 0.007 0.012 1608 120006 0007 0.004 0.008 -0.007 0.009 0.011 11163 1030013 0015 -0.002 0.002 -0.011 0.003 0.011 4999 490005 0009 0.001 0.008 0.006 0.008 0.010 4020 560007 0008 -0.007 -0.004 -0.006 0.008 0.010 11374 1000017 0042 -0.000 -0.002 0.010 0.002 0.010 12463 440015 0019 -0.003 0.004 0.008 0.005 0.010 8530 470009 0011 -0.003 0.009 -0.001 0.010 0.010 3228 540043 0007 -0.008 -0.005 -0.001 0.009 0.009 6232 590038 0002 0.005 0.008 -0.001 0.009 0.009 5089 1190003 0005 0.006 0.006 0.003 0.009 0.009 9559 1060029 0035 0.001 -0.002 0.009 0.002 0.009 4931 100010 0011 0.001 0.000 0.009 0.001 0.009 10484 940013 0014 0.001 0.001 0.009 0.001 0.009 8296 870011 0015 0.000 0.003 0.008 0.003 0.009 6668 500010 0012 -0.003 -0.001 -0.008 0.003 0.008 3222 930043 0009 -0.004 0.003 0.006 0.006 0.008 8789 58

etc...

The vector serial number ID is included in this listing so that it is easy for you to relate any line in this output to the actual inputvector. When “debugging” a network, vector serial numbers can be used with the “.IGNORE” and “.FREE” inline options toquickly ignore or free certain vectors so you can rerun an adjustment and see how the results are affected. As illustrated above,vectors whose serial numbers are prefixed with an asterisk character (*) had been set free.

6.6 RESULTS OF GEOID MODELINGWhen geoidmodeling is performed, or when individual geoid heights are entered for stations using the “GH” data type, thesemodeled or entered heights may be shown in the output listing file. There is an option in theModeling options dialog whichallows you select whether or not to show modeled heights for every point.

When geodetic positions are selected in the Listing options to be shown in the listing, the Geoid Heights will be shown as illus-trated below.


- 54 -

Adjusted Positions and Ellipsoid Heights (Meters)

Station Latitude Longitude Ellip Ht Geoid Ht0001 33-04-04.729598 113-01-18.892909 184.5589 -31.28940002 33-04-36.399347 113-00-36.410946 185.4698 -31.26330003 33-03-43.631136 113-00-29.226324 150.7246 -31.28360004 33-04-07.138671 113-00-06.305634 143.3870 -31.27000005 32-58-41.087753 112-59-07.491499 171.2339 -31.32830006 33-03-52.060232 112-59-17.411999 173.8724 -31.26570007 32-57-54.635274 112-58-06.878665 171.2370 -31.33430008 33-04-03.809294 112-58-12.051914 175.5950 -31.25050009 32-59-03.939538 112-56-35.046118 172.5443 -31.31900010 33-04-27.272136 112-56-38.621043 177.1151 -31.22690011 32-59-04.475307 112-54-30.727495 173.0659 -31.31350012 33-04-44.244330 112-54-36.045690 193.0912 -31.2082etc...

However, when geodetic positions are not selected in the Listing options to be shown in the listing, the Geoid Heights will beshown in their own section. If vertical deflections aremanually entered using the “GH” or “GT” data type, or calculated using ver-tical deflectionmodeling, this output section will be always be shown rather than showing the geoid heights with the geodeticpositions.

Geoid Heights (Meters) and Vertical Deflections (Seconds)

Station Geoid Ht North Def East Def0001 -31.2894 0.0000 0.00000002 -31.2633 0.0000 0.00000003 -31.2836 0.0000 0.00000004 -31.2700 0.0000 0.00000005 -31.3283 0.0000 0.00000006 -31.2657 0.0000 0.00000007 -31.3343 0.0000 0.00000008 -31.2505 0.0000 0.00000009 -31.3190 0.0000 0.00000010 -31.2269 0.0000 0.00000011 -31.3135 0.0000 0.00000012 -31.2082 0.0000 0.0000etc...

Appendix A: TOUR OF THE STAR*NET-PROPACKAGE

- 55 -

APPENDIX A: TOUR OF THE STAR*NET-PRO PACK-AGEOverviewThis tutorial is designed to be used with the STAR*NET-PRO edition and the supplied sample data files to acquaint you withsome of the capabilities of the package.

However, if you are new to the STAR*NET program, we strongly suggest before you run this tutorial, you first review the stand-ard STAR*NETmanual and run its tutorial located in Appendix-A. That will introduce you to the general operation of the soft-ware and illustrate the adjustment of networks having conventional observations.

The STAR*NET-PRO tutorial contains the following examples:

Example 8:

A simple network containing only GPS vectors. The example walks you through the basic steps of settingrequired options, setting up themain data file, importing vectors, and running an adjustment. The example alsotakes you through the output adjustment listing to review the particular sections which relate to GPS projects.

This example demonstrates the adjustment of a fully-constrained network. Note that you should always run aminimally-constrained adjustment first to check the integrity of the observations before adding coordinateconstraints! However to keep this tutorial short, we have bypassed this initial step.

Example 9:

This example demonstrates combining conventional observations with GPS vectors. The network consists ofGPS vectors from the first example, and conventional observations consisting of a single traverse plus fourobservation ties to other GPS stations.

It is assumed that you have already run the tutorial in themain STAR*NETmanual and know how tomakemenu selections,set options andmaneuver through text files.

However, if you have not run themain STAR*NET tutorial, we suggest before continuing, you at least review that tour’s Over-view to see how to select projects and run two of the example projects. Review Example 1 which will acquaint you with usingall options dialogs, using the Data Files dialog, running an adjustment, and viewing listed and plotted output. Finally reviewExample 4 to get a good overview on a running project in a grid coordinate system.


- 56 -

0.1 EXAMPLE 8: SIMPLE GPS NETWORKThis example demonstrates themajor steps you would go through to setup and adjust a simple network made up of only GPSvectors. You will set a few required project options, review themain data file which defines the coordinate constraints, import afew vectors from Trimble GPSurvey baseline files, and adjust the network.

# Simple GPS Network# Fully-constrained, two fixed stations plus a fixed elevation# Grid Coordinates are used for constraints in this example

C 0012 230946.1786 120618.7749 224.299 ! ! ! 'North RockC 0017 218691.2153 131994.0354 209.384 ! ! ! '80-1339E 0013 205.450 ! 'BM-9331

1. Open the "Tutorial08-VectorJob.prj" example project.

2. ChooseOptions>Project, or press the Project Options tool button.


- 57 -

Options in the Adjustment tab are settings that describe the project. Note that the Adjustment Type is set is "3D" andthe Coordinate System is set to "Grid." When a project contains GPS vectors, these two options must always be setthis way. This example project is set to use NAD83 Arizona Central zone 0202.

The AverageGeoid Height is set to -31.20meters. For GPS vector adjustments however, it is very important to performgeoidmodeling as the connection between vectors (which are ellipsoid-based) and elevations (which are geoid-based)are accurate geoid separations. For simplicity though, we will not be performing geoidmodeling in this tutorial example,therefore this value will be assigned as the geoid height to all stations in the project.

If you wish, review the next four option tabs: General, Instrument, Listing File, andOther Files. They contain typical set-tings you have seen before while reviewing the tutorial in themainmanual. The "Instrument" settings only relate to con-ventional observations, so in the case of this project having only GPS vectors, they have no relevance in theadjustment.

3. Review the "GPS" options by clicking the "GPS" tab. These fields allow you to set default values or options relating toGPS vectors present in your network data.


- 58 -

We know that all vectors imported for this example have supplied weighting so we didn’t set any default standard errorsoffered by the "Apply Default StdErrs" field.

A value of 8.00 has been set for the "Factor Vector StdErrors" field whichmeans that all the imported vector standarderrors will bemultiplied by this factor. Standard errors reported by many baseline processors are over-optimistic and thisoption allows you tomake themmore realistic. A "Vector Centering StdError" value of 0.002meters has been enteredwhich further inflates the standard errors.

The "Transformations" box is checked and a choice has beenmade to solve for scale and three rotations, around North,East and Up axes, during the adjustment. Solving for these transformations often helps "best-fit" vectors to your stationconstraints by removing systematic errors or biases that may exist in vector data.

Finally, in the "Listing Appearance" options, certain output preferences are set for various listing items including howyou like to see vector weighting expressed and how both unadjusted and adjusted vectors data should be sorted. Notethat in this sections, it has been chosen to show a "Residual Summary" section in the listing. We’ll review this very use-ful report later.

4. Review the "Modeling" tab. It is here that you select to perform both geoidmodeling and deflectionmodeling during anadjustment. For simplicity in this demo tutorial, we are not going to perform any modeling. The average geoid heightspecified on the Adjustment options page will be applied to all stations in the network.

5. This concludes the overview of the Project Options for this example. After you are finished reviewing the options, press"OK" to close the dialog.

6. Next, review the input data. ChooseView>Data Files if necessary. Note there are two files in the list. The first file isthemain data file shown at the beginning of this example. It simply contains two stations with fixed north, east andelevation values, and one station with a fixed elevation.


- 59 -

The second file contains the imported vectors for this project. For simplicity, we have already imported the vectors intoa file for this example, and it appears in the data file list with the same name as the project, and with a "GPS" extension.In the next step, we’ll actually go through the exercise of running the GPS importer to show you how this file wascreated.

But while we are still in the Data Files dialog, let’s review the vector file. Double-click the "Tutorial08-VectorJob.gps" filein the list.

The file contains eight imported vectors. Each vector consists or four lines which includes a vector ID number, theDelta-X, Y & Z vector lengths, and covariance information for weighting. After reviewing the vector data, close the win-dow.

7. Now that the imported vectors have been reviewed, let’s see how they were actually imported in the first place. ChooseInput>Import GPS Vectors.


- 60 -

The first step in importing vectors is to choose aGPS Baseline Format from the drop down selection list. In this exam-ple we are extracting vectors from baseline files created using the Trimble GPSurvey package. Next, take a quick lookat the "Options" tab. Here you can set a few options that will affect vector importing.

Back in the "Import" tab, press the "Select Baseline Files" button to bring up a file selection dialog. (The baselines are inthe "Examples" sub-folder of your "My Documents\MicroSurvey\StarNet\" directory, so if the dialog does not openthere, go ahead and browse there.) The selection dialog will show eight Trimble "SSF" baseline files. Highlight thesefiles as shown, and press the "Select" button.

These selected files now appear in themain Import page dialog as shown below and the "Import" button is now active.


- 61 -

If we press "Import," the importer will extract vectors from these files and write them to the file named "VectorJob.GPS"specified in the "Import Vectors to" field above. But to simplify this tutorial example, we had previously imported them.

However, if you want to import the vectors anyway just to see how it works, press the "Import!" button. When importerwarns you that the file already exists, it asks if you want to Overwrite or Append the file - select to Overwrite the file.

Complete details on importing vectors, setting import options, and information on the current baseline formats availableto import from are fully discussed in the STAR*NET-PRO documentation. Press "Close" to exit the vector importer.

8. Project Options have been set and all input data files created, so now we can adjust the network. ChooseRun>AdjustNetwork, or press the Run Adjustment button.

The Processing Summary window opens, and the network adjustment iterations finish quickly. Note that the total "ErrorFactor" was low, less than 1.00, and the adjustment passed the "Chi Square" test.

9. Review the network plot if you wish. Note that the geometry for point 0015 seems rather weak, and the error ellipse forthat point is larger than those for the other points. In the next example, we will run a traverse from 0013 to 0018 andmake ties from the traverse to points 0015 and 0016.

10. View the output Listing file and browse through the various sections, especially the output sections relating to GPS vec-tors. Go to the "Summary of Unadjusted Input Observations" section where you will first see the list of controlling coor-dinates.

Directly following will be the unadjusted vectors showing the lengths and standard errors of the Delta X, Y and Z com-ponents of each vector expressed in the earth-centered Cartesian system. Standard errors shown for these com-ponents include the affects of any "Factoring" and "Centering Errors" set in the options.

Next go to the "Adjusted Observations and Residuals" section. The first part of this section shows solutions of the trans-formations requested in the GPS options reviewed earlier. Here you see solutions for a scale and three rotations. Thescale change is very small as are the three rotations. This should be expected when performing an adjustment on aGPS-based ellipsoid such as WGS-84 or GRS-80. If any of these solved transformation values are unreasonably large,you need to review your observations and constraints and find the reason why.


- 62 -

As shown above, the next output in the same section are the adjusted GPS vectors and their residuals. Always reviewthis important section since it shows you how much STAR*NET had to change each vector to produce a best-fit solu-tion.

Note that all the vector, residual and standard error components have been rotated from earth-centered Cartesian tolocal-horizon North, East and Up components. This orientation is simple to understand and very easily related to con-ventional observations.

The next section is the "GPS Vector Residual Summary" mentioned earlier in this example. Users find this one of themost helpful GPS related sections in the listing. It can be sorted in various ways to help you find the "Worst" vectors inyour network. In our example, the summary is sorted by "3D" residuals, made up of local-horizon North, East and Upresidual components.

Review the remaining sections in the listing file if you wish. These section are not unique to GPS vectors, and you haveseen them before when running the examples earlier in this tutorial.

11. This completes the "VectorJob" example project. This was a realistic example of a small GPS job containing only


- 63 -

vectors.

To keep the tutorial short however, this example skipped a very important step! When running your own adjustments,always run aminimally-constrained adjustment first, holding only a single station fixed. This will test the integrity of theobservations without the influence of external constraints. When you are confident that all observations are fittingtogether well, then add any remaining fixed stations to the network.

The next example will add the vectors from this project to some conventional observations and you will run a combinednetwork adjustment. If you want to continue on to the next example, turn the page for instructions.


- 64 -

0.2 EXAMPLE 9: COMBINING CONVENTIONAL OBSERVATIONS AND GPSThis example demonstrates combining conventional observations andGPS vectors in a single adjustment. We'll be using thesame imported vectors and constraints as in the last example, only now a traverse and some ties have been added to the net-work.

# Combining Conventional Observations and GPS Vectors# Latitudes and Longitudes are used as constraints in this example# The "VectorJob.GPS" file is added in the Data Files DialogP 0012 33-04-44.24402 112-54-36.04569 224.299 ! ! ! 'North RockP 0017 32-58-09.73117 112-47-13.55717 209.384 ! ! ! 'AZDOT 80-1339E 0013 205.450 ! 'BM-9331

TB 0012T 0013 67-58-23.5 4013.95 90-04-44 5.35/5.40T 0051 160-18-01.7 2208.27 90-14-33 5.40/5.40T 0052 213-47-22.1 2202.07 89-43-20 5.36/5.40 'SW BridgeT 0053 198-52-17.3 2714.30 89-58-19 5.35/5.38TE 0018

# Ties to GPS pointsM 0051-0013-0015 240-35-47.03 1601.22 90-27-52 5.40/5.40M 0052-0051-0015 320-50-46.25 2499.61 90-05-49 5.36/5.41M 0052-0051-0016 142-02-01.50 2639.68 90-07-37 5.36/5.40M 0053-0052-0016 61-14-43.77 2859.65 90-20-19 5.35/5.42


- 65 -

1. Open the "Tutorial09-VectorCombined.snproj" example project.

2. Review the Project Options if you wish. Since this project contains conventional observations, the "Instrument" optionssettings will be relevant in the adjustment. Note that the standard error values entered for the turned angle, distance andzenith angle observations are quite small indicating that high quality instruments and field procedures are being used.The "GPS" option settings are the same as in the first example project.

When combining conventional observations with GPS vectors, it is particularly important to carefully set weightingparameters in the Instrument options as well as in the GPS options since standard errors determine the relativeinfluence of each type of data in the adjustment.

3. Open the Input Data Files dialog. There are two files in the list. The first file named "Tutorial09-VectorCombined.dat"contains the station constraints and conventional observations, and the second file named "Tutorial08-VectorJob.gps"contains GPS vectors imported to that file in the last example project. This file was simply added to the data file list bypressing the "Add" button and selecting the file. View either of these files if you wish.

Note that in the "Tutorial09-VectorCombined.dat" file, shown on the first page of this example, the same stations havebeen constrained as were in the last project, except they are entered as equivalent geodetic positions rather than gridcoordinates simply to illustrate use of that data type. Results will be identical either way.

Conventional observations in the network include a traverse and four ties from traverse stations to two of the GPS sta-tions. The traverse lines and the tie observations (the "M" lines) include turned angles, slope distances and zenithangles. Instrument and target heights are also included.

4. Run the network adjustment! The Processing Summary window opens, and the adjustment converges in a few iter-ations. The total "Error Factor" was slightly greater than 1, but the adjustment passed the "Chi Square" test.


- 66 -

5. View the network plot. Note that although the standard errors for the conventional observations were set quite small(indicating use of high quality instruments and field procedures), the error ellipses for points observed only by theseobservations are noticeably larger than those observed by GPS vectors.

If you wish, open the plot properties dialog, and turn on both relative ellipses and point descriptors.

Experiment by double clicking points and connection lines to see the adjusted information including ellipse and relativeellipse sizes.

6. View the listing file. Note that listing sections reviewing unadjusted and adjusted observations now include both


- 67 -

conventional andGPS vector observations.

Find the "Statistical Summary" listing section and review how each type of observation (angle, distance, zenith angleand vector) fit in to the adjusted network.

7. This completes the "VectorCombined.Prj" project, the last example in this tour.

As you can see, combining conventional observations andGPS vector observations is very easy. When combining con-ventional andGPS observations, themost important consideration is establishing realistic weighting relationships betweenyour GPS vector observations and your conventional observations. As mentioned in the first example, the standard errorsreported by most manufacturer’s baseline processors are usually over-optimistic, so you normally need to set a "factor" in theGPS options tomake them realistic, andmore compatible with conventional observations.

Note that geoidmodeling has beenmentionedmore than once in the two example projects containing GPS vectors. But for sim-plicity, geoidmodeling was not performed. However, installed along with this demo program is a separate utility program whichextracts geoid information from a variety of government-supplied files and creates neutral geoid files that are used with theSTAR*NET-PRO edition. This utility, named StarGeoid, is an-easy-to-use single dialog program:

The use of this utility is not discussed in the tutorial, but in short, it allows you to extract geoid (and vertical deflection) infor-mation from government sources and save the data in a neutral format for use by STAR*NET-PRO. Then when you want to per-form modeling, all you do is to check the "Perform GeoidModeling" box in theModeling options, andmodeling will beautomatically performed during the adjustment – very easy!


- 68 -

Index

- 69 -

INDEX

A

Adjustment Output Listing

Adjustment Observations and Residuals 51

Results of GeoidModeling 53

Statistical Summary 50

Summary of Unadjusted Input Observations 49

Vector Residual Summary 52

Ashtech 30

B

Blue Book Gfile 30

C

Constraining your Network

Fully 7

General Notes 7

Minimally 6

Contact Information v

D

Data Types

Coordinates 5

Elevations 5

Ellipse Heights 5

Geoid Height 39

Positions 5

Vertical Deflection 39

Disclaimer and LimitedWarranty i

E

ECEF Output information

Adjusted Coordinates 13

Adjusted Vectors 13

End-User License Agreement i

Example

Combining Conventional Observations andGPS 64

Simple GPS Network 56

F

FieldGenius 31

G

GeoGenius 30

Geotracer 30

GPS Options 10

I

Importing Vectors

Baseline Formats 29

General Notes 29

Overview 25

Setting Importing Options 26

Special Leica Descriptor Extraction 33

Using the Importer 26

Inline Options

.BASE 22

.GPS ADDHIHT 20

.GPS CENTERING 19

.GPS DEFAULT 15

.GPS FACTOR 16

.GPS FREE 20


- 70 -

.GPS IGNORE 20

.GPS NETWORK 21

.GPS SS 21

.GPS USE 17

.GPSWEIGHT 4

.OPUS 35

Inline Options Overview 15

J

Javad 32

L

Leica Geomatics Office (LGO) 30

Leica Ski-Pro 30

M

Magellan 32

MicroSurvey FieldGenius 31

MicroSurvey Software Inc. v

Modeling Options 40

Modeling Source Data

Canadian GeoidModels 46

United States NGS Geoid and DeflectionModels 45

World GeoidModels 46

N

NGS OPUS Service 33

NovAtel 31

O

OPUS Stations 33

P

Preanalysis

Notes about Running 8

Weighting with the .GPS USE inline 8

S

Sokkia 31

StarGeoid Utility Program

Extracting from Geoid Height Models 44

Extracting from Vertical DeflectionModels 44

Overview 43

T

TDS Survey Pro GPS 31

Technical Support iv

Topcon 31

Topcon Tools – TVF Files 31

Transformations, Vector Scale and Rotations

Setting 11

Solving 6, 11

Trimble Business Center (TBC) 32

Trimble Data Exchange 32

Trimble Geomatics Office (TGO) 32

Trimble GPSurvey 32

Trimble TSC1/TSCe/TSC2 32

V

Vectors

Factoring a Single Vector 18

Freeing or Ignoring a Single Vector 18

Importing 25

Weighting a Single Vector 18

Index

- 71 -

Vertical DeflectionModeling 41

W

Waypoint 32


- 72 -