Changeset 7015 in ntrip
- Timestamp:
- Jul 6, 2015, 3:53:34 PM (9 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (19 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7009 r7015 298 298 299 299 <p> 300 The main window of BNC shows a 'Top menu bar' section, a 'Settings' sections with tabs to set processing options, a 'Streams' section, a section for 'Log' tabs, and a 'Bottom menu bar' section, see figure below.300 The main window of BNC shows a 'Top menu bar' section, a 'Settings' sections with panels to set processing options, a 'Streams' section, a section for 'Log' tabs, and a 'Bottom menu bar' section, see figure below. 301 301 </p> 302 302 <p><img src="IMG/screenshot09.png"/></p> … … 312 312 313 313 <p> 314 The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration tabs to select a combination of input, processing and output options before you start the program ('Start'). Most configuration tabs are dedicated to a certain functionality of BNC. If the first option field on such a configuration tabis empty, the affected functionality is - apart from a few exceptions - deactivated.</p>315 316 Records of BNC's activities are shown in the 'Log' tab. The bandwidth consumption per stream, the latency of incoming observations and a PPP time series for coordinates are shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs of the main window.314 The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration panels to select a combination of input, processing and output options before you start the program ('Start'). Most configuration panels are dedicated to a certain functionality of BNC. If the first option field on such a configuration panel is empty, the affected functionality is - apart from a few exceptions - deactivated.</p> 315 316 Records of BNC's activities are shown in the 'Log' tab. The bandwidth consumption per stream, the latency of incoming observations and a PPP time series for coordinates are shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs. 317 317 </p> 318 318 … … 437 437 3.12.4. <a href=#miscport>Port</a><br> 438 438 3.13. <a href=#pppclient>PPP Client</a><br> 439 3.13.1 <a href=#pppmode>Mode & Mountpoints</a><br> 440 3.13.1.1 <a href=#pppmodus>Mode</a><br> 441 3.13.1.2 <a href=#pppobsmount>Obs Mountpoint</a><br> 442 3.13.1.3 <a href=#pppcorrmount>Corr Mountpoint</a><br> 443 3.13.2 <a href=#pppxyz>Marker Coordinates</a><br> 444 3.13.3 <a href=#pppneu>Antenna Eccentricity</a><br> 445 3.13.4 <a href=#pppoutput>NMEA & Plot Output</a><br> 446 3.13.4.1 <a href=#pppnmeafile>NMEA File</a><br> 447 3.13.4.2 <a href=#pppnmeaport>NMEA Port</a><br> 448 3.13.5 <a href=#ppppost>Post Processing</a><br> 449 3.13.6 <a href=#ppprecant>Antennas</a><br> 450 3.13.6.1 <a href=#pppantex>ANTEX File</a><br> 451 3.13.6.2 <a href=#ppprecantenna>Antenna Name</a><br> 452 3.13.7 <a href=#pppbasics>Basics</a><br> 453 3.13.7.1 <a href=#pppphase>Use Phase Obs</a><br> 454 3.13.7.2 <a href=#ppptropo>Estimate Tropo</a><br> 455 3.13.7.3 <a href=#pppglo>Use GLONASS</a><br> 456 3.13.7.4 <a href=#pppgal>Use Galileo</a><br> 457 3.13.7.5 <a href=#pppsync>Sync Corr</a><br> 458 3.13.7.6 <a href=#pppaverage>Averaging</a><br> 459 3.13.7.7 <a href=#pppquick>Quick-Start</a><br> 460 3.13.7.8 <a href=#pppgap>Maximal Solution Gap</a><br> 461 3.13.7.9 <a href=#pppaudio>Audio Response</a><br> 462 3.13.8 <a href=#pppsigmas>Sigmas</a><br> 463 3.13.8.1 <a href=#pppsigc>Code</a><br> 464 3.13.8.2 <a href=#pppsigp>Phase</a><br> 465 3.13.8.3 <a href=#pppsigxyzi>XYZ Init</a><br> 466 3.13.8.4 <a href=#pppsigxyzn>XYZ White Noise</a><br> 467 3.13.8.5 <a href=#pppsigtrpi>Tropo Init</a><br> 468 3.13.8.6 <a href=#pppsigtrpn>Tropo White Noise</a><br> 469 3.13.9 <a href=#pppplots>PPP Plot</a><br> 470 3.13.10 <a href=#ppptracepos>Track Plot</a><br> 471 3.13.10.1 <a href=#pppmap>Open Map</a><br> 472 3.13.10.2 <a href=#pppmaptype>Google/OSM</a><br> 473 3.13.10.3 <a href=#pppdot>Dot Size</a><br> 474 3.13.10.4 <a href=#pppcolor>Dot Color</a><br> 475 3.13.10.5 <a href=#pppspeed>Speed</a><br> 476 439 3.13.1 <a href=#pppInp>PPP (1): Input and Output</a><br> 440 3.13.1.1 <a href=#pppdatasource>Data Source</a><br> 441 3.13.1.2 <a href=#ppprnxobs>RINEX Observation File</a><br> 442 3.13.1.3 <a href=#ppprnxnav>RINEX Navigation File</a><br> 443 3.13.1.4 <a href=#pppcorrfile>Correction File</a><br> 444 3.13.1.5 <a href=#pppcorrstream>Corrections Stream</a><br> 445 3.13.1.6 <a href=#pppmarkcoor>Coordinates</a><br> 446 3.13.1.7 <a href=#ppplogfile>Logfile</a><br> 447 3.13.1.8 <a href=#pppantexfile>ANTEX File</a><br> 448 3.13.1.9 <a href=#pppnmeafile>NMEA File</a><br> 449 3.13.1.10 <a href=#pppsnxtrofile>SNX TRO File</a><br> 450 3.13.2 <a href=#pppStation>PPP (2): Processed Stations</a><br> 451 3.13.2.1 <a href=#pppnehsigma>Sigma North/East/Height</a><br> 452 3.13.2.2 <a href=#pppnehnoise>Noise North/East/Height</a><br> 453 3.13.2.3 <a href=#ppptropsigma>Tropo Sigma</a><br> 454 3.13.2.4 <a href=#ppptropnoise>Tropo Noise</a><br> 455 3.13.2.5 <a href=#pppnmeaport>NMEA Port</a><br> 456 3.13.3 <a href=#pppOptions>PPP (3): Processing Options</a><br> 457 3.13.3.1 <a href=#ppplinecombi>Linear Combinations</a><br> 458 3.13.3.2 <a href=#pppcodeobs>Code Observations</a><br> 459 3.13.3.3 <a href=#pppphaseobs>Phase Observations</a><br> 460 3.13.3.4 <a href=#pppeleweight>Elevation Depending Weighting</a><br> 461 3.13.3.5 <a href=#pppminobs>Minimum Number of Observations</a><br> 462 3.13.3.6 <a href=#pppmineleva>Minimum Elevation</a><br> 463 3.13.3.7 <a href=#pppwaitclockcorr>Wait for Clock Corrections</a><br> 464 3.13.3.8 <a href=#pppseeding>Seeding</a><br> 465 3.13.4 <a href=#pppPlots>PPP (4): Plots</a><br> 466 3.13.4.1 <a href=#ppptimeseries>PPP Plot</a><br> 467 3.13.4.2 <a href=#pppaudioresp>Audio Response</a><br> 468 3.13.4.3 <a href=#ppptrackmap>Track Map</a><br> 469 3.13.4.3.1 <a href=#pppmaptype>Google/OSM</a><br> 470 3.13.4.4 <a href=#pppdotprop>Dot-properties</a><br> 471 3.13.4.4.1 <a href=#pppdotsize>Size</a><br> 472 3.13.4.4.2 <a href=#pppdotcolor>Color</a><br> 473 3.13.4.5 <a href=#pppspeed>Post Processing Speed</a><br> 477 474 3.14. <a href=#combi>Combine Corrections</a><br> 478 475 3.14.1 <a href=#combimounttab>Combine Corrections Table</a><br> … … 2077 2074 BNC can derive coordinates for a rover position following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data from one or more GNSS systems in ionosphere free linear combinations P3 or L3. Besides pulling a stream of observations from a dual frequency GNSS receiver, this also 2078 2075 <ul> 2079 <li>requires pulling in addition a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of RTCM Version 3 'State Space Representation' (SSR) messages. Note that for BNC these Broadcast Corrections need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. Stream 'CLK11' on NTRIP Broadcaster 'products.igs-ip.net:2101' is an example.</li> 2080 <li>may require pulling a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019, 1020, 1043, 1044, 1045, 1046 and 63 (tentative). This is a must only when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only at very low repetition rate. Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. Stream 'RTCM3EPH' on caster 'products.igs-ip.net:2101' is an example.</li> 2081 </ul> 2082 </p> 2083 <p> 2084 The following figure provides the screenshot of an example PPP session with BNC. 2085 </p> 2086 2087 <p><img src="IMG/screenshot03.png"/></p> 2088 <p><u>Figure 20:</u> Real-time Precise Point Positioning with BNC, PPP Panel 1.</p> 2089 2090 <p><img src="IMG/screenshot17.png"/></p> 2091 <p><u>Figure 21:</u> Precise Point Positioning with BNC, PPP Panel 2.</p> 2092 2093 <p><img src="IMG/screenshot18.png"/></p> 2094 <p><u>Figure 22:</u> Precise Point Positioning with BNC, PPP Panel 3.</p> 2095 2076 <li>Requires pulling in addition a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of RTCM Version 3 'State Space Representation' (SSR) messages. Note that for BNC these Broadcast Corrections need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. Stream 'CLK11' on NTRIP Broadcaster 'products.igs-ip.net:2101' is an example.</li> 2077 <li>May require pulling a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019, 1020, 1043, 1044, 1045, 1046 and 63 (tentative). This becomes a must only when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only at very low repetition rate. Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. Stream 'RTCM3EPH' on caster 'products.igs-ip.net:2101' is an example.</li> 2078 </ul> 2079 </p> 2080 2081 <p>When using the PPP option, it is important to understand which effects are corrected by BNC. 2082 </p> 2083 <ul> 2084 <li>BNC does correct for Solid Earth Tides and Phase Windup.</li> 2085 <li>Satellite antenna phase center offsets are corrected.</li> 2086 <li>Satellite antenna phase center variations are neglected because this is a small effect usually less than 2 centimeters.</li> 2087 <li>Observations can be corrected for a Receiver Antenna Offset. Depending on whether or not this correction is applied, the estimated position is either that of the receiver's antenna phase center or that of the receiver's Antenna Reference Point.</li> 2088 <li>Receiver antenna phase center variations are not included in the model. The bias caused by this neglect depends on the receiver antenna type. For most antennas it is smaller than a few centimeters.</li> 2089 <li>Ocean and atmospheric loading is neglected. Atmospheric loading is pretty small. Ocean loading is usually also a small effect but may reach up to about 10 centimeters for coastal stations.</li> 2090 <li>Rotational deformation due to polar motion (Polar Tides) is not corrected because this is a small effect usually less than 2 centimeters.</li> 2091 </ul> 2092 </p> 2093 <p> 2094 The provider of an orbit/clock corrections stream may switch with his service at any time from a duty to a backup server installation. This shall be noted in the SSR stream through a change of the Issue Of Data (IOD SSR) parameter. The PPP option in BNC will immediately reset all ambiguities in such a situation. 2095 </p> 2096 <p> 2097 PPP options are specified in BNC through the following four panels. 2098 <ul> 2099 <li>PPP (1): Input and output, sprecifying real-time or post processing mode and associated data sources</li> 2100 <li>PPP (2): Processed stations, specifying sigmas and noise of a-priori coordinates and NMEA stream output</li> 2101 <li>PPP (3): Processing options, specifying general PPP processing options</li> 2102 <li>PPP (4): Plots, specifying visualization through time series and track maps</li> 2103 </ul> 2104 </p> 2105 2106 <p><a name="pppInp"><h4>3.13.1 PPP (1): Input and Output</h4></p> 2107 <p> 2108 This panel provides options for specifying the input and output streams and files required by BNC for real-time or post processing PPP. 2109 </p> 2110 2111 <p><a name="pppdatasource"><h4>3.13.1.1 Data Source - optional</h4></p> 2112 <p> 2113 Choose between input from 'Real-time Streams' or 'RINEX Files' for PPP with BNC in real-time or post processing mode. 2114 </p> 2115 2116 <p> 2117 <u>Real-time Streams</u><br> 2118 When choosing 'Real-time Streams' BNC will do a PPP solutions in real-time. This requires pulling an GNSS observations stream, Broadcast Ephemeris messages and a stream containing corrections to Broadcast Ephemeris. Streams must come in RTCM Version 2 or RTCM Version 3 format. 2119 </p> 2120 <p> 2121 If you don't pull Broadcast Corrections BNC will switch with its solution to 'Single Point Positioning' (SPP) mode. 2122 </p> 2123 2124 <p> 2125 <u>RINEX Files</u><br> 2126 This input mode allows you to specify RINEX Observation, RINEX Navigation and Broadcast Correction files. BNC accepts RINEX Version 2 as well as RINEX Version 3 Observation or Navigation file formats. Files carrying Broadcast Corrections must have the format produced by BNC through the 'Broadcast Corrections' panel. 2127 </p> 2128 <p> 2129 Specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Corrections file leads BNC to a 'Single Point Positioning' (SPP) solution. 2130 <p> 2131 <u>Debugging</u><br> 2132 Note that for debugging purposes BNC's real-time PPP functionality can also be used offline. Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations, orbit and clock correctors, and Broadcast Ephemeris. Example:<br><br> 2133 bnc.exe --conf c:\temp\PPP.bnc --file c:\temp\RAW<br><br> 2134 Such a file (here: 'RAW') must be saved beforehand using BNC's 'Raw output file' option. 2135 </li> 2136 </ul> 2137 </p> 2138 2139 <p><a name="ppprnxobs"><h4>3.13.1.2 RINEX Observation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p> 2140 <p> 2141 Specify one or more RINEX Observation files. The file format can be RINEX Version 2 or RINEX Version 3. 2142 </p> 2143 2144 <p><a name="ppprnxnav"><h4>3.13.1.3 RINEX Navigation File - mandatory if 'Data source' is set to 'RINEX Files'</h4></p> 2145 <p> 2146 Specify one or more RINEX Navigation files. The file format can be RINEX Version 2 or RINEX Version 3. 2147 </p> 2148 2149 <p><a name="pppcorrfile"><h4>3.13.1.4 Correction File - optional if 'Data source' is set to 'RINEX Files'</h4></p> 2150 <p> 2151 Specify one or more Broadcast 'Correction files' as saved beforehand using BNC. The file contents is basically the ASCII representation of a RTCM Version 3 Broadcast Correction (SSR) stream. 2152 </p> 2153 <p> 2154 If you don't specify a 'Correction file' BNC will fall back from a PPP solution to a Single Point Positioning (SPP) solution. 2155 </p> 2156 2157 <p><a name="pppcorrstream"><h4>3.13.1.5 Corrections Stream - optional if 'Data source' is set to 'Real-Time Streams'</h4></p> 2158 <p> 2159 Specify a Broadcast Ephemeris 'Corrections stream' from the list of selected 'Streams' you are pulling if you want BNC to correct your satellite ephemeris accordingly. Note that the stream's orbit and clock corrections must refer to the satellite Antenna Phase Center (APC). Streams providing such corrections are made availabel e.g. through the International GNSS Service (IGS) and listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. The stream format must be RTCM Version 3 containing so-called SSR messages. Streams 'IGS03' and 'CLK11' supporting GPS plus GLONASS are examples. 2160 </p> 2161 <p> 2162 If you don't specify a 'Corrections stream' BNC will fall back from a PPP solution to a Single Point Positioning (SPP) solution. 2163 </p> 2164 2165 <p><a name="pppmarkcoor"><h4>3.13.1.6 Coordinates - mandatory</h4></p> 2166 <p> 2167 Enter the full path to an ASCII file which specifies all streams or files from stationary or mobile receivers you potentially may want to process. The 'Coordinates' file must contain one record per file or stream with the following parameters separated by blank characters: 2168 </p> 2169 <p> 2170 <ul> 2171 <li>Input data source, to be specifiedy either through 2172 <ul> 2173 <li>the 'Mountpoint' of an RTCM stream (when in real-time PPP mode), or 2174 </li> 2175 <li>the first four characters of the RINEX observations file (when in post processing PPP mode).</li> 2176 </ul> 2177 Having this parameter first in each record is mandatory. BNC will carry out PPP solutions only for streams or files specified here.</li><br> 2178 <li>Only for static observations from a stationary receiver:<br>Approximate a-priori X,Y,Z coordinate [m] of the station's marker; specify '0.0 0.0 0.0' if unknown or when observations come from a mobile receiver.</li><br> 2179 <li>Nort, East and Up component [m] of antenna excentricity which is the difference between Antenna Reference Point (ARP) and a nearby marker position; when specifying the antenna excentricity BNC will produce coordinates referring to the marker position and not referring to ARP; specify '0.0 0.0 0.0' if excentricity is unknown or the ARP itself is understood as the marker.</li><br> 2180 <li>Receiver's antenna name as defined in your ANTEX file (see below); Observations will be corrected for the Antenna Phase Center's (APC) offset and variation which may result in a reduction of a few centimeters at max; the specified name must consist of 20 characters; add trailing blanks if the antenna name has less than 20 characters, examples:<br><pre> 2181 'JPSREGANT_SD_E ' (no radome) 2182 'LEIAT504 NONE' (no radome) 2183 'LEIAR25.R3 LEIT' (radome)</pre> 2184 Leave blank if you don't want to correct observations for antenna phase center offsets.</li> 2185 </ul> 2186 </p> 2187 <p> 2188 Records in the 'Coordinates' file with exclamation mark '!' in the first column or blank records will be understood as comment lines and ignored. 2189 </p> 2190 <p> 2191 The following is an example contents for a 'Coordinates' file. Here each record describes the mountpoint of a stream available from the 2192 global stationary IGS real-time network. A-prioriy coordinates are followed by North/East/Up excentricity components of the ARP 2193 followed by the antenna type and radom in use. 2194 </p> 2195 <pre> 2196 ! 2197 ! Station X[m] Y[m] Z[m] North[m] EAST[m] UP[m] Antenna Radom 2198 ! ----------------------------------------------------------------------------------------------------------- 2199 ADIS0 4913652.6612 3945922.7678 995383.4359 0.0000 0.0000 0.0010 TRM29659.00 NONE 2200 ALIC0 -4052052.5593 4212836.0078 -2545104.8289 0.0000 0.0000 0.0015 LEIAR25.R3 NONE 2201 BELF0 3685257.8823 -382908.8992 5174311.1067 0.0000 0.0000 0.0000 LEIAT504GG LEIS 2202 BNDY0 -5125977.4106 2688801.2966 -2669890.4345 0.0000 0.0000 0.0000 ASH701945E_M NONE 2203 BRAZ0 4115014.0678 -4550641.6105 -1741443.8244 0.0000 0.0000 0.0080 LEIAR10 NONE 2204 CAGZ0 4893379.8326 772650.6854 4004180.1625 0.0000 0.0000 0.0945 JPSREGANT_DD_E NONE 2205 CALG0 -1635378.1748 -3665371.5746 4941664.3370 0.0000 0.0000 0.0000 SOK702 NONE 2206 CONZ0 1492004.6119 -4887911.2671 -3803640.2397 0.0000 0.0000 0.0574 LEIAR25.R3 LEIT 2207 CTWN0 5023564.4285 1677795.7211 -3542025.8392 0.0000 0.0000 0.0000 ASH701941.B NONE 2208 CUT07 -2364337.4408 4870285.6055 -3360809.6280 0.0000 0.0000 0.0000 TRM59800.00 SCIS 2209 DHLG3 -2319099.4261 -4799846.4583 3490090.4018 0.0000 0.0000 0.1224 ASH701945B_M SCIS 2210 FAA10 -5247393.4678 -3076866.6580 -1911521.1749 0.0000 0.0000 0.1262 LEIAR25.R4 NONE 2211 GANP0 3929181.3480 1455236.9105 4793653.9880 0.0000 0.0000 0.3830 TRM55971.00 NONE 2212 HLFX0 2018905.6037 -4069070.5095 4462415.4771 0.0000 0.0000 0.1000 TPSCR.G3 NONE 2213 KIRU0 2251420.6255 862817.3340 5885476.8395 0.0000 0.0000 0.0620 ASH701945C_M SNOW 2214 LHAZ0 -106941.9272 5549269.8041 3139215.1564 0.0000 0.0000 0.1330 ASH701941.B NONE 2215 LMMF7 2993387.3587 -5399363.8649 1596748.0983 0.0000 0.0000 0.0000 TRM57971.00 NONE 2216 MAO07 -5466067.0979 -2404333.0198 2242123.1929 0.0000 0.0000 0.0000 LEIAR25.R3 LEIT 2217 NICO0 4359415.5252 2874117.1872 3650777.9614 0.0000 0.0000 0.0650 LEIAR25.R4 LEIT 2218 NKLG7 6287385.7320 1071574.7606 39133.1088 -0.0015 -0.0025 3.0430 TRM59800.00 SCIS 2219 NURK7 5516756.5103 3196624.9684 -215027.1315 0.0000 0.0000 0.1300 TPSCR3_GGD NONE 2220 OHIX7 1525809.2353 -2432478.7568 -5676166.2639 0.0000 0.0000 0.0660 LEIAR25.R4 LEIT 2221 ONSA0 3370658.3928 711877.2903 5349787.0603 0.0000 0.0000 0.9950 AOAD/M_B OSOD 2222 PDEL0 4551595.9072 -2186892.9495 3883410.9685 0.0000 0.0000 0.0000 LEIAT504GG NONE 2223 RCMN0 5101056.6270 3829074.4206 -135016.1589 0.0000 0.0000 0.0000 LEIAT504GG LEIS 2224 REUN0 3364098.9668 4907944.6121 -2293466.7379 0.0000 0.0000 0.0610 TRM55971.00 NONE 2225 REYK7 2587384.0890 -1043033.5433 5716564.1301 0.0000 0.0000 0.0570 LEIAR25.R4 LEIT 2226 RIO27 1429907.8578 -3495354.8953 -5122698.5595 0.0000 0.0000 0.0350 ASH700936C_M SNOW 2227 SMR50 927077.1096 -2195043.5597 -5896521.1344 0.0000 0.0000 0.0000 TRM41249.00 TZGD 2228 SUWN0 -3062023.1604 4055447.8946 3841818.1684 0.0000 0.0000 1.5700 TRM29659.00 DOME 2229 TASH7 1695944.9208 4487138.6220 4190140.7391 0.0000 0.0000 0.1206 JAV_RINGANT_G3T NONE 2230 UFPR0 3763751.6731 -4365113.9039 -2724404.5331 0.0000 0.0000 0.1000 TRM55971.00 NONE 2231 UNB30 1761287.9724 -4078238.5659 4561417.8448 0.0000 0.0000 0.3145 TRM57971.00 NONE 2232 VILL0 4849833.5863 -335048.8133 4116015.0652 0.0000 0.0000 0.0437 AOAD/M_T NONE 2233 WIND7 5633708.8016 1732017.9297 -2433985.5795 0.0000 0.0000 0.0460 ASH700936C_M SNOW 2234 WTZR0 4075580.3797 931853.9767 4801568.2360 0.0000 0.0000 0.0710 LEIAR25.R3 LEIT 2235 WUH27 -2267749.9761 5009154.5504 3221294.4429 0.0000 0.0000 0.1206 JAV_RINGANT_G3T NONE 2236 YELL7 -1224452.8796 -2689216.1863 5633638.2832 0.0000 0.0000 0.1000 AOAD/M_T NONE 2237 </pre> 2238 <p> 2239 Note that the only mandatory parameter in this is the 'Station' parameter standing for an observation's mountpoint or RINEX file name. 2240 The following shows further valid examples for records of a 'Coordinates' file. 2241 </p> 2242 2243 <pre> 2244 ! 2245 ! Station X[m] Y[m] Z[m] N[m] E[m] U[m] Antenna Radom 2246 ! --------------------------------------------------------------------------------------- 2247 FFMJ1 4053455.7384 617729.8393 4869395.8214 0.000 0.000 0.045 2248 TITZ1 3993780.4501 450206.8969 4936136.9886 2249 WARN 2250 SASS1 0.0 0.0 0.0 0.000 0.000 0.031 TPSCR3_GGD CONE 2251 </pre> 2252 2253 <p> 2254 In this file 2255 </p> 2256 <ul> 2257 <li> Record 'FFMJ1' describes a stream from a stationary receiver with known a-priory marker coordinate and antenna excentricity but unknown antenna type and radom.</li> 2258 <li> Record 'TITZ1' describes a stream coming from a stationary receiver where an a-priory marker coordinate is known but antenna excentricity, type and radom are unknown.</li> 2259 <li>The 4-character station ID 'WARN' indicates that a RINEX observations file for post processing PPP is available for station 'WARN' but an a-priory marker coordinate as well as antenna excentricity, type and radom are unknown.</li> 2260 <li>Record 'SASS1' stands for a mountpoint where the stream comes from a mobile rover receiver. Hence an a-priory coordinate is unknown although antenna excentricity, type and radom are known.</li> 2261 </ul> 2262 </p> 2263 2264 <p><a name="ppplogfile"><h4>3.13.1.7 Logfile - optional</h4></p> 2096 2265 <p> 2097 2266 PPP results are shown in the 'Log' tab on the bottom of BNC's main window. Depending on the processing options, the following values are shown about once per second (example): 2098 2267 <pre> 2099 10-09-08 09:14:06 FFMJ1 PPP 09:14:04.0 12 4053457.429 +- 2.323 617730.551 +- 1.630 4869395.266 +- 2.951 2268 15-06-30 11:40:24 2015-06-30_11:40:22.000 CUT07 X = -2364337.6864 Y = 4870283.8106 Z = -3360808.3099 NEU: +0.1543 +0.2121 -1.0190 TRP: +2.4022 +0.0009 2269 15-06-30 11:40:25 2015-06-30_11:40:23.000 CUT07 X = -2364337.6861 Y = 4870283.8111 Z = -3360808.3105 NEU: -0.9782 +0.0916 -2.3544 TRP: +2.4017 +0.0013 2270 15-06-30 11:40:26 2015-06-30_11:40:24.000 CUT07 X = -2364337.6884 Y = 4870283.8123 Z = -3360808.3103 NEU: -0.5606 -0.0938 -1.9498 TRP: +2.4018 +0.0016 2100 2271 </pre> 2101 2272 </p> … … 2158 2329 </p> 2159 2330 2160 <p> 2161 Note that for debugging or Post Processing purposes BNC's 'PPP' functionality option can also be used offline. 2162 <ul> 2163 <li> 2164 <u>Debugging:</u> Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations, orbit and clock correctors, and Broadcast Ephemeris. Such a file must be generated before using BNC's 'Raw output file' option. Example:<br> 2165 bnc.exe --conf c:\temp\PPP.bnc --file c:\temp\FFMJ1 2166 </li> 2167 <li> 2168 <u>Post Processing:</u> Apply the 'Post Processing' option as described below. 2169 </li> 2170 </ul> 2171 </p> 2172 2173 <p>When using the PPP option, it is important to understand which effects are corrected by BNC. 2174 </p> 2175 <ul> 2176 <li>BNC does correct for Solid Earth Tides and Phase Windup.</li> 2177 <li>Satellite antenna phase center offsets are corrected.</li> 2178 <li>Satellite antenna phase center variations are neglected because this is a small effect usually less than 2 centimeters.</li> 2179 <li>Observations can be corrected for a Receiver Antenna Offset. Depending on whether or not this correction is applied, the estimated position is either that of the receiver's antenna phase center or that of the receiver's Antenna Reference Point.</li> 2180 <li>Receiver antenna phase center variations are not included in the model. The bias caused by this neglect depends on the receiver antenna type. For most antennas it is smaller than a few centimeters.</li> 2181 <li>Ocean and atmospheric loading is neglected. Atmospheric loading is pretty small. Ocean loading is usually also a small effect but may reach up to about 10 centimeters for coastal stations.</li> 2182 <li>Rotational deformation due to polar motion (Polar Tides) is not corrected because this is a small effect usually less than 2 centimeters.</li> 2183 </ul> 2184 </p> 2185 <p> 2186 The provider of an orbit/clock corrections stream may switch with his service at any time from a duty to a backup server installation. This shall be noted in the SSR stream through a change of the Issue Of Data (IOD SSR) parameter. The PPP option in BNC will immediately reset all ambiguities in such a situation. 2187 </p> 2188 2189 <p><a name="pppmode"><h4>3.13.1 Mode & Mountpoints - optional</h4></p> 2190 <p> 2191 Specify the Point Positioning mode you want to apply and the mountpoints for observations and Broadcast Corrections. 2192 </p> 2193 2194 <p><a name="pppmodus"><h4>3.13.1.1 Mode - optional</h4></p> 2195 <p> 2196 Choose between plain Single Point Positioning (SPP) and Precise Point Positioning (PPP) in 'Realtime' or 'Post-Processing' mode. Options are 'Realtime-PPP', 'Realtime-SPP', and 'Post-Processing'. 2197 </p> 2198 2199 <p><a name="pppobsmount"><h4>3.13.1.2 Obs Mountpoint - optional</h4></p> 2200 <p> 2201 Specify an 'Observations Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to derive coordinates for the affected rover position through a Point Positioning solution. 2202 </p> 2203 2204 <p><a name="pppcorrmount"><h4>3.13.1.3 Corr Mountpoint - optional</h4></p> 2205 <p> 2206 Specify a Broadcast Ephemeris 'Corrections Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to correct your positioning solution accordingly. Not that the stream's corrections must refer to the satellite Antenna Phase Center (APC). 2207 </p> 2208 2209 <p><a name="pppxyz"><h4>3.13.2 Marker Coordinates - optional</h4></p> 2210 <p> 2211 Enter the reference coordinate XYZ of the receiver's position in meters if known. This option makes only sense for static observations. Defaults are empty option fields, meaning that the antenna's XYZ position is unknown. 2212 </p> 2213 <p> 2214 Once a XYZ coordinate is defined, the 'PPP' line in BNC's logfile is extended by North, East and Up displacements to (example): 2215 </p> 2216 <pre> 2217 10-08-09 06:01:56 FFMJ1 PPP 06:02:09.0 11 4053457.628 +- 2.639 617729.438 +- 1.180 4869396.447 +- 1.921 NEU -0.908 -0.571 1.629 2218 </pre> 2219 <p> 2220 The parameters following the 'NEU' string provide North, East and Up components of the current coordinate displacement in meters. 2221 </p> 2222 2223 <p><a name="pppneu"><h4>3.13.3 Antenna Eccentricity - optional</h4></p> 2224 <p> 2225 You may like to specify North, East and Up components of an antenna eccentricity which is the difference between a nearby marker position and the antenna phase center. If you do so BNC will produce coordinates referring to the marker position and not referring to the antenna phase center. 2226 </p> 2227 2228 <p><a name="pppoutput"><h4>3.13.4 NMEA Output - optional</h4></p> 2229 <p> 2230 BNC allows to output results from Precise Point Positioning in NMEA format. 2231 </p> 2232 <p> 2233 Note that Tomoji Takasu has written a program called RTKPLOT for visualizing NMEA strings. It is available from <u>http://www.rtklib.com</u> and compatible with the NMEA file and port output of BNC's 'PPP' client option. 2234 </p> 2235 2236 <p><a name="pppnmeafile"><h4>3.13.4.1 NMEA File - optional</h4></p> 2331 <p><a name="pppantexfile"><h4>3.13.1.8 ANTEX File - optional</h4></p> 2332 <p> 2333 IGS provides a file containing absolute phase center corrections for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required for correcting observations for antenna phase center offsets and variations. It allows you to specify the name of your receiver's antenna (as contained in the ANTEX file) to apply such corrections. 2334 </p> 2335 <p> 2336 Default is an empty option field, meaning that you don't want to correct observations for antenna phase center offsets and variations. 2337 </p> 2338 2339 <p><a name="pppnmeafile"><h4>3.13.1.9 NMEA File - optional</h4></p> 2237 2340 <p> 2238 2341 The NMEA sentences generated about once per second are pairs of … … 2270 2373 </pre> 2271 2374 2272 <p><a name="pppnmeaport"><h4>3.13.4.2 NMEA Port - optional</h4></p> 2273 <p> 2274 Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA messages vi IP port. Note that the NMEA file output and the NMEA IP port output are the same. 2275 </p> 2276 <p> 2277 NASA's 'World Wind' software (see <u>http://worldwindcentral.com/wiki/NASA_World_Wind_Download</u>) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from <u>http://worldwindcentral.com/wiki/GPS_Tracker</u> for that. The 'Word Wind' map resolution is not meant for showing centimeter level details. 2278 </p> 2279 2280 <p><a name="ppppost"><h4>3.13.5 Post Processing - optional</h4></p> 2281 <p>When in 'Post-Processing' mode 2282 <ul> 2283 <li>Specifying a RINEX Observation, a RINEX Navigation and a Broadcast Corrections file leads to a PPP solution.</li> 2284 <li>Specifying only a RINEX Observation and a RINEX Navigation file and no Broadcast Corrections file leads to a SPP solution.</li> 2285 </ul> 2286 </p> 2287 <p>BNC accepts RINEX Version 2 as well as RINEX Version 3 Observation or Navigation file formats. Files carrying Broadcast Corrections must have the format produced by BNC through the 'Broadcast Corrections' tab. 2288 <p> 2289 Post Processing PPP results can be saved in a specific output file. 2290 </p> 2291 2292 <p><a name="ppprecant"><h4>3.13.6 Antennas - optional</h4></p> 2293 <p> 2294 BNC allows correcting observations for antenna phase center offsets and variations. 2295 </p> 2296 2297 <p><a name="pppantex"><h4>3.13.6.1 ANTEX File - optional</h4></p> 2298 <p> 2299 IGS provides a file containing absolute phase center corrections for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required for correcting observations for antenna phase center offsets and variations. It allows you to specify the name of your receiver's antenna (as contained in the ANTEX file) to apply such corrections. 2300 </p> 2301 <p> 2302 Default is an empty option field, meaning that you don't want to correct observations for antenna phase center offsets and variations. 2303 </p> 2304 2305 <p><a name="ppprecantenna"><h4>3.13.6.2 Receiver Antenna Name - optional if 'ANTEX File' is set</h4></p> 2306 <p> 2307 Specify the receiver's antenna name as defined in your ANTEX file. Observations will be corrected for the antenna phase center's offset which may result in a reduction of a few centimeters at max. Corrections for phase center variations are not yet applied by BNC. The specified name must consist of 20 characters. Add trailing blanks if the antenna name has less than 20 characters. Examples: 2308 <pre> 2309 'JPSREGANT_SD_E ' (no radome) 2310 'LEIAT504 NONE' (no radome) 2311 'LEIAR25.R3 LEIT' (radome) 2312 </pre> 2313 </p> 2314 <p> 2315 Default is an empty option field, meaning that you don't want to correct observations for antenna phase center offsets. 2316 </p> 2317 2318 <p><a name="pppbasics"><h4>3.13.7 Basics</h4></p> 2319 <p>BNC allows using different Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows introducing specific sigmas for code and phase observations as well as for reference coordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold. 2320 </p> 2321 2322 <p><a name="pppphase"><h4>3.13.7.1 Use Phase Obs - optional</h4></p> 2323 <p> 2324 By default BNC applies a Point Positioning solution using an ionosphere free P3 linear combination of code observations. Tick 'Use phase obs' for an ionosphere free L3 linear combination of phase observations. 2325 </p> 2326 2327 <p><a name="ppptropo"><h4>3.13.7.2 Estimate Tropo - optional</h4></p> 2375 <p><a name="pppsnxtrofile"><h4>3.13.1.10 SNX TRO File - optional</h4></p> 2328 2376 <p> 2329 2377 BNC estimates the tropospheric delay according to equation … … 2398 2446 </pre> 2399 2447 2400 <p><a name="pppglo"><h4>3.13.7.3 Use GLONASS - optional</h4></p> 2448 <p><a name="pppStation"><h4>3.13.2 PPP (2): Processed Stations</h4></p> 2449 2450 <p><a name="pppnehsigma"><h4>3.13.2.1 Sigma North/East/Height - mandatory</h4></p> 2451 <p> 2452 Enter a sigma in meters for the initial XYZ coordinate. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known XZY position in Quick-Start mode. 2453 </p> 2454 2455 <p><a name="pppnehnoise"><h4>3.13.2.2 Noise North/East/Height - mandatory</h4></p> 2456 <p> 2457 Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 (default) may be appropriate when considering possible sudden movements of a rover. 2458 </p> 2459 2460 <p><a name="ppptropsigma"><h4>3.13.2.3 Tropo Sigma - mandatory if 'Estimate tropo' is set</h4></p> 2461 <p> 2462 Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice. 2463 </p> 2464 2465 <p><a name="ppptropnoise"><h4>3.13.2.4 Tropo Noise - mandatory if 'Estimate tropo' is set</h4></p> 2466 <p> 2467 Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 3e-6 (default) would mean that the tropospheric effect may vary for 3600 * 3e-6 = 0.01 meters per hour. 2468 </p> 2469 2470 <p><a name="pppnmeaport"><h4>3.13.2.5 NMEA Port - optional</h4></p> 2471 Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA messages vi IP port. Note that the NMEA file output and the NMEA IP port output are the same. 2472 </p> 2473 <p> 2474 NASA's 'World Wind' software (see <u>http://worldwindcentral.com/wiki/NASA_World_Wind_Download</u>) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from <u>http://worldwindcentral.com/wiki/GPS_Tracker</u> for that. The 'Word Wind' map resolution is not meant for showing centimeter level details. 2475 </p> 2476 <p> 2477 Note that Tomoji Takasu has written a program called RTKPLOT for visualizing NMEA strings. It is available from <u>http://www.rtklib.com</u> and compatible with the NMEA file and port output of BNC's 'PPP' client option. 2478 </p> 2479 2480 <p><a name="pppOptions"><h4>3.13.3 PPP (3): Processing Options</h4></p> 2481 <p>BNC allows using different Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows introducing specific sigmas for code and phase observations as well as for reference coordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold. 2482 </p> 2483 2484 <p><a name="ppplinecombi"><h4>3.13.3.1 Linear Combinations - mandatory</h4></p> 2485 <p> 2486 By default BNC applies a Point Positioning solution using an ionosphere free P3 linear combination of code observations. Tick 'Use phase obs' for an ionosphere free L3 linear combination of phase observations. 2487 </p> 2488 2401 2489 <p> 2402 2490 By default BNC does not process GLONASS but only GPS observations when in Point Positioning mode. Tick 'Use GLONASS' to use GLONASS observations in addition to GPS (and Galileo if specified) for estimating coordinates in Point Positioning mode. 2403 2491 </p> 2404 2405 <p><a name="pppgal"><h4>3.12.7.4 Use Galileo - optional</h4></p>2406 2492 <p> 2407 2493 By default BNC does not process Galileo but only GPS observations when in Point Positioning mode. Tick 'Use Galileo' to use Galileo observations in addition to GPS (and GLONASS if specified) for estimating coordinates in Point Positioning mode. 2408 2494 </p> 2409 2495 2410 <p><a name="pppsync"><h4>3.13.7.5 Sync Corr - optional</h4></p> 2496 <p><a name="pppcodeobs"><h4>3.13.3.2 Code Observations - mandatory</h4></p> 2497 <p> 2498 You may like to introduce specific sigmas for code and phase observations and for the estimation of troposphere parameters. 2499 </p> 2500 2501 <p><a name="pppphaseobs"><h4>3.13.3.3 Phase Observations - mandatory if 'Use Phase Obs' is set</h4></p> 2502 <p> 2503 When 'Use phase obs' is set in BNC, the PPP solution will be carried out using both, code and phase observations. A sigma of 10.0 m for code observations and a sigma of 0.02 m for phase observations (defaults) are used to combine both types of observations. As the convergence characteristic of a PPP solution can be influenced by the ratio of the sigmas for code and phase, you may like to introduce you own sigmas for code and phase observations which differ from the default values. 2504 <ul> 2505 <li>Introducing a smaller sigma (higher accuracy) for code observations or a larger sigma for phase observations leads to better results shortly after program start. However, it may take more time till you finally get the best possible solution.</li> 2506 <li>Introducing a larger sigma (lower accuracy) for code observations or a smaller sigma for phase observations may lead to less accurate results shortly after program start and thus a prolonged period of convergence but could provide better positions in the long run.</li> 2507 </ul> 2508 </p> 2509 <p> 2510 Specify a sigma for code observations. Default is 10.0 m. 2511 </p> 2512 2513 <p> 2514 Specify a sigma for phase observations. Default is 0.02 m. 2515 </p> 2516 2517 <p><a name="pppeleweight"><h4>3.13.3.4 Elevation Depending Weighting - optional</h4></p> 2518 2519 <p><a name="pppminobs"><h4>3.13.3.5 Minimum Number of Observations - optional</h4></p> 2520 2521 <p><a name="pppmineleva"><h4>3.13.3.6 Minimum Elevation - optional</h4></p> 2522 2523 <p><a name="pppwaitclockcorr"><h4>3.13.3.7 Wait for Clock Corrections - optional</h4></p> 2411 2524 <p> 2412 2525 Zero value (or empty field) means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value 'Sync Corr' means that the epochs of data are buffered and the processing of each epoch is postponed till the satellite clock corrections not older than 'Sync Corr' are available. Specifying a value of half the update rate of the clock corrections as 'Sync Corr' (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of half of the update rate. … … 2419 2532 </p> 2420 2533 2421 <p><a name="pppaverage"><h4>3.13.7.6 Averaging - optional if XYZ is set</h4></p> 2422 <p> 2423 Enter the length of a sliding time window in minutes. BNC will continuously output moving average values and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenith path delays are bias reduced while RMS values for North/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string "AVE-XYZ" in BNC's logfile and 'Log' section while averaged values for NEU displacements and their RMS are marked with string "AVE-NEU" and averaged values for the tropospheric delays and their RMS are marked with string "AVE-TRP". Example: 2424 </p> 2425 <pre> 2426 10-09-08 09:13:05 FFMJ1 AVE-XYZ 09:13:04.0 4053455.948 +- 0.284 617730.422 +- 0.504 4869397.692 +- 0.089 2427 10-09-08 09:13:05 FFMJ1 AVE-NEU 09:13:04.0 1.043 +- 0.179 0.640 +- 0.456 1.624 +- 0.331 2428 10-09-08 09:13:05 FFMJ1 AVE-TRP 09:13:04.0 2.336 +- 0.002 2429 </pre> 2430 <p> 2431 Entering any positive value up to 1440 (24h mean value) is allowed. An empty option field (default) means that you don't want BNC to output moving average positions into the logfile and the 'Log' section. Note that averaging positions makes only sense for a stationary receiver. 2432 </p> 2433 2434 <p><a name="pppquick"><h4>3.13.7.7 Quick-Start - optional if XYZ is set</h4></p> 2534 <p><a name="pppseeding"><h4>3.13.3.8 Seeding - optional if XYZ is set</h4></p> 2435 2535 <p> 2436 2536 Enter the length of a startup period in seconds for which you want to fix the PPP solution to a known XYZ coordinate. Constraining coordinates is done in BNC through setting the 'XYZ White Noise' temporarily to zero. … … 2441 2541 You may need to create your own reference coordinate through running BNC for an hour in normal mode before applying the 'Quick-Start' option. Don't forget to introduce a realistic sigma 'XYZ Ini' according to the coordinate's precision. 2442 2542 </p> 2543 2544 <p> 2545 The following figure provides the screenshot of an example PPP session with BNC. 2546 </p> 2547 2548 <p><img src="IMG/screenshot03.png"/></p> 2549 <p><u>Figure 20:</u> Real-time Precise Point Positioning with BNC, PPP Panel 1.</p> 2550 2551 <p><img src="IMG/screenshot17.png"/></p> 2552 <p><u>Figure 21:</u> Precise Point Positioning with BNC, PPP Panel 2.</p> 2553 2554 <p><img src="IMG/screenshot18.png"/></p> 2555 <p><u>Figure 22:</u> Precise Point Positioning with BNC, PPP Panel 3.</p> 2443 2556 2444 2557 <p><img src="IMG/screenshot22.png"/></p> 2445 2558 <p><u>Figure 23:</u> BNC in 'Quick-Start' mode (PPP, Panel 2)</p> 2446 2559 2447 <p><a name="pppgap"><h4>3.13.7.8 Maximal Solution Gap - optional if Quick-Start is set</h4></p> 2448 <p> 2449 Specify a 'Maximum Solution Gap' in seconds. Should the time span between two consecutive solutions exceed this limit, the algorithm returns into the 'Quick-Start' mode and fixes the introduced reference coordinate for the specified 'Quick-Start' period. A value of '60' seconds could be an appropriate choice. 2450 </p> 2451 <p> 2452 This option makes only sense for a stationary operated receiver where solution convergence can be enforced because a good approximation for the rover position is known. Default is an empty option field, meaning that you don't want BNC to return into the 'Quick-Start' mode after failures caused i.e. by longer lasting outages. 2453 </p> 2454 2455 <p><a name="pppaudio"><h4>3.13.7.9 Audio Response - optional if Quick-Start is set</h4></p> 2560 <p><a name="pppaverage"><h4>3.13.3.NN Averaging - optional if XYZ is set</h4></p> 2561 <p><a name="pppgap"><h4>3.13.3.NN Maximal Solution Gap - optional if Quick-Start is set</h4></p> 2562 2563 <p><a name="pppPlots"><h4>3.13.4 PPP (4): Plots</h4></p> 2564 2565 <p><a name="ppptimeseries"><h4>3.13.4.1 PPP Plot - optional</h4></p> 2566 <p> 2567 You make like to track your rover position using Google Maps or Open StreetMap as a background map. Track maps can be produced with BNC in 'Real-time Streams' mode or in 'RINEX Files' post processing mode with data coming from files. 2568 </p> 2569 <p> 2570 When in 'Post Processing' mode you should not forget to specify a proxy under the 'Network' panel if that is operated in front of BNC. 2571 </p> 2572 <p> 2573 PPP time series of North (red), East (green) and Up (blue) displacements will be plotted in the 'PPP Plot' panel when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes. 2574 </p> 2575 <p> 2576 Note that a PPP time series makes only sense for a stationary operated receiver. 2577 </p> 2578 2579 <p><a name="pppaudioresp"><h4>3.13.4.2 Audio Response - optional if Quick-Start is set</h4></p> 2456 2580 <p> 2457 2581 For natural hazard prediction and monitoring it may be appropriate to generate audio alerts. For that you can specify an 'Audio response' threshold in meters. A beep is produced by BNC whenever a horizontal PPP coordinate component differs by more than the threshold value from the specified marker coordinate. … … 2459 2583 <p> 2460 2584 Default is an empty option field, meaning that you don't want BNC to produce acoustic warning signals. 2461 </p>2462 2463 <p><a name="pppsigmas"><h4>3.13.8 Sigmas</h4></p>2464 <p>2465 You may like to introduce specific sigmas for code and phase observations and for the estimation of troposphere parameters.2466 </p>2467 2468 <p><a name="pppsigc"><h4>3.13.8.1 Code - mandatory if 'Use Phase Obs' is set</h4></p>2469 <p>2470 When 'Use phase obs' is set in BNC, the PPP solution will be carried out using both, code and phase observations. A sigma of 10.0 m for code observations and a sigma of 0.02 m for phase observations (defaults) are used to combine both types of observations. As the convergence characteristic of a PPP solution can be influenced by the ratio of the sigmas for code and phase, you may like to introduce you own sigmas for code and phase observations which differ from the default values.2471 <ul>2472 <li>Introducing a smaller sigma (higher accuracy) for code observations or a larger sigma for phase observations leads to better results shortly after program start. However, it may take more time till you finally get the best possible solution.</li>2473 <li>Introducing a larger sigma (lower accuracy) for code observations or a smaller sigma for phase observations may lead to less accurate results shortly after program start and thus a prolonged period of convergence but could provide better positions in the long run.</li>2474 </ul>2475 </p>2476 <p>2477 Specify a sigma for code observations. Default is 10.0 m.2478 </p>2479 2480 <p><a name="pppsigp"><h4>3.13.8.2 Phase - mandatory if 'Use Phase Obs' is set</h4></p>2481 <p>2482 Specify a sigma for phase observations. Default is 0.02 m.2483 </p>2484 2485 <p><a name="pppsigxyzi"><h4>3.13.8.3 XYZ Init - mandatory</h4></p>2486 <p>2487 Enter a sigma in meters for the initial XYZ coordinate. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known XZY position in Quick-Start mode.2488 </p>2489 2490 <p><a name="pppsigxyzn"><h4>3.13.8.4 XYZ White Noise - mandatory</h4></p>2491 <p>2492 Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 (default) may be appropriate when considering possible sudden movements of a rover.2493 </p>2494 2495 <p><a name="pppsigtrpi"><h4>3.13.8.5 Tropo Init - mandatory if 'Estimate tropo' is set</h4></p>2496 <p>2497 Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice.2498 </p>2499 2500 <p><a name="pppsigtrpn"><h4>3.13.8.6 Tropo White Noise - mandatory if 'Estimate tropo' is set</h4></p>2501 <p>2502 Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 3e-6 (default) would mean that the tropospheric effect may vary for 3600 * 3e-6 = 0.01 meters per hour.2503 </p>2504 2505 <p><a name="pppplots"><h4>3.13.9 PPP Plot - optional</h4></p>2506 <p>2507 PPP time series of North (red), East (green) and Up (blue) displacements will be plotted in the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes.2508 </p>2509 <p>2510 Note that a PPP time series makes only sense for a stationary operated receiver.2511 </p>2512 2513 <p><a name="ppptracepos"><h4>3.13.10 Track Plot</h4></p>2514 <p>2515 You make like to track your rover position using Google Maps or Open StreetMap as a background map. Track maps can be produced with BNC in 'Realtime-PPP', 'Realtime-SPP' and 'Post-Processing' PPP mode.2516 </p>2517 <p>2518 When in 'Post-Processing' mode you should not forget to specify a proxy under the 'Network' tab if that is operated in front of BNC.2519 2585 </p> 2520 2586 … … 2523 2589 <p><u>Figure 24:</u> Track of positions from BNC with Google Maps in the background.</p> 2524 2590 2525 <p><a name="ppp map"><h4>3.13.10.1 OpenMap - optional</h4></p>2591 <p><a name="ppptrackmap"><h4>3.13.4.3 Track Map - optional</h4></p> 2526 2592 <p> 2527 2593 The 'Open Map' button opens a windows showing a map according to options specified below. 2528 2594 </p> 2529 2595 2530 <p><a name="pppmaptype"><h4>3.13. 10.2Google/OSM - mandatory before pushing 'Open Map'</h4></p>2596 <p><a name="pppmaptype"><h4>3.13.4.3.1 Google/OSM - mandatory before pushing 'Open Map'</h4></p> 2531 2597 <p> 2532 2598 Specify either 'Google' or 'OSM' as the background for your rover positions. 2533 2599 </p> 2534 2600 2535 <p><a name="pppdot"><h4>3.13.10.3 Dot Size - mandatory before pushing 'Open Map'</h4></p> 2601 <p><a name="pppdotprop"><h4>3.13.4.4 Dot-properties - mandatory before pushing 'Open Map'</h4></p> 2602 2603 <p><a name="pppdotsize"><h4>3.13.4.4.1 Size - mandatory before pushing 'Open Map'</h4></p> 2536 2604 <p> 2537 2605 Specify the size of dots showing the rover position. A dot size of '3' may be appropriate. The maximum possible dot size is '10'. An empty option field or a size of '0' would mean that you don't want BNC to show the rover's track on the map. 2538 2606 </p> 2539 2607 2540 <p><a name="ppp color"><h4>3.13.10.4 DotColor - mandatory before pushing 'Open Map'</h4></p>2608 <p><a name="pppdotcolor"><h4>3.13.4.4.2 Color - mandatory before pushing 'Open Map'</h4></p> 2541 2609 <p> 2542 2610 Specify the color of dots showing the rover track. 2543 2611 </p> 2544 2612 2545 <p><a name="pppspeed"><h4>3.13. 10.5Speed - mandatory before pushing 'Open Map'</h4></p>2546 <p> 2547 With BNC in PPP post -processing mode you can specify the speed of computations as appropriate for visualization. Note that you can adjust 'Speed' on-the-fly while BNC is processing your observatins.2613 <p><a name="pppspeed"><h4>3.13.4.5 Post Processing Speed - mandatory before pushing 'Open Map'</h4></p> 2614 <p> 2615 With BNC in PPP post processing mode you can specify the speed of computations as appropriate for visualization. Note that you can adjust 'Speed' on-the-fly while BNC is processing your observatins. 2548 2616 </p> 2549 2617 … … 2615 2683 The sequence of entries in the 'Combine Corrections' table is not of importance. Note that the orbit information in the final combination stream is just copied from one of the incoming streams. The stream used for providing the orbits may vary over time: if the orbit providing stream has an outage then BNC switches to the next remaining stream for getting hold of the orbit information.</p> 2616 2684 <p> 2617 It is possible to specify only one Broadcast Ephemeris corrections stream in the 'Combine Corrections' table. Instead of combining corrections from several sources, BNC will then merge the single corrections stream with Broadcast Ephemeris to save results in SP3 and/or Clock RINEX format when specified accordingly under the 'Upload Corrections' tab. Note that in such a BNC application you must not pull more than one Broadcast Ephemeris corrections stream even if a second stream would provide the same corrections from a backup caster.2685 It is possible to specify only one Broadcast Ephemeris corrections stream in the 'Combine Corrections' table. Instead of combining corrections from several sources, BNC will then merge the single corrections stream with Broadcast Ephemeris to save results in SP3 and/or Clock RINEX format when specified accordingly under the 'Upload Corrections' panel. Note that in such a BNC application you must not pull more than one Broadcast Ephemeris corrections stream even if a second stream would provide the same corrections from a backup caster. 2618 2686 </p> 2619 2687 <p> … … 2627 2695 2628 2696 <p> 2629 The following screenshots describe an example setup of BNC when combining Broadcast Correction streams and uploading them to an NTRIP Broadcaster. Note that this application requires specifying options under tabs 'Combine Corrections' and 'Upload Corrections'. The example uses the combination product to simultaneously carry out an 'INTERNAL' PPP solution which allows monitoring the quality of the combination product in the space domain.2697 The following screenshots describe an example setup of BNC when combining Broadcast Correction streams and uploading them to an NTRIP Broadcaster. Note that this application requires specifying options under panels 'Combine Corrections' and 'Upload Corrections'. The example uses the combination product to simultaneously carry out an 'INTERNAL' PPP solution which allows monitoring the quality of the combination product in the space domain. 2630 2698 </p> 2631 2699 … … 3135 3203 <p><a name="logs"><h4>3.18. Logging</h4></p> 3136 3204 <p> 3137 A tabssection on the bottom of the main window provides online control of BNC's activities. Tabs are available to show the records saved in a logfile, for a plot to control the bandwidth consumption, for a plot showing stream latencies, and for time series plots of PPP results.3205 The section on the bottom of the main window provides online control of BNC's activities. Tabs are available to show the records saved in a logfile, for a plot to control the bandwidth consumption, for a plot showing stream latencies, and for time series plots of PPP results. 3138 3206 </p> 3139 3207 <p><a name="logfile"><h4>3.18.1 Log</h4></p> … … 3514 3582 <tr> 3515 3583 <td>Nov 2009 </td><td>Version 1.7 </td> 3516 <td>[Bug] RINEX Navigation file format<br> [Add] Upgrade to Qt Version 4.5.2<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port<br> [Add] Show broadcaster table from www.rtcm-ntrip.org<br> [Add] Enable/disable tabwidgets<br> [Add] User defined configuration file name<br> [Mod] Switch to configuration files in ini-Format<br> [Add] Daily logfile rotation<br> [Add] Read from TCP/IP port, by-pass NTRIP transport protocol<br> [Add] Save NMEA messages coming from rover<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Read from serial port, by-pass NTRIP transport protocol<br> [Mod] Update of SSR messages following RTCM 091-2009-SC104-542<br> [Add] Read from UPD port, by-pass NTRIP transport protocol<br> [Mod] Output format of Broadcast Corrections<br> [Add] Throughput plot<br> [Add] Latency plot</td>3584 <td>[Bug] RINEX Navigation file format<br> [Add] Upgrade to Qt Version 4.5.2<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port<br> [Add] Show broadcaster table from www.rtcm-ntrip.org<br> [Add] Enable/disable panel widgets<br> [Add] User defined configuration file name<br> [Mod] Switch to configuration files in ini-Format<br> [Add] Daily logfile rotation<br> [Add] Read from TCP/IP port, by-pass NTRIP transport protocol<br> [Add] Save NMEA messages coming from rover<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Read from serial port, by-pass NTRIP transport protocol<br> [Mod] Update of SSR messages following RTCM 091-2009-SC104-542<br> [Add] Read from UPD port, by-pass NTRIP transport protocol<br> [Mod] Output format of Broadcast Corrections<br> [Add] Throughput plot<br> [Add] Latency plot</td> 3517 3585 </tr> 3518 3586 … … 3544 3612 <tr> 3545 3613 <td>Dec 2010 </td><td>Version 2.4 </td> 3546 <td>[Add] Output of averaged positions when in PPP mode<br> [Mod] Use always the latest received set of Broadcast Ephemeris<br> [Add] QuickStart PPP option<br> [Mod] Improvement of data sharing efficiency among different threads<br> [Mod] Design of PPP tabsection<br> [Add] Sigmas for observations and parameters<br> [Add] Stream distribution map<br> [Bug] GPS Ephemeris in RINEX v3 format</td>3614 <td>[Add] Output of averaged positions when in PPP mode<br> [Mod] Use always the latest received set of Broadcast Ephemeris<br> [Add] QuickStart PPP option<br> [Mod] Improvement of data sharing efficiency among different threads<br> [Mod] Design of PPP panel section<br> [Add] Sigmas for observations and parameters<br> [Add] Stream distribution map<br> [Bug] GPS Ephemeris in RINEX v3 format</td> 3547 3615 </tr> 3548 3616 3549 3617 <tr> 3550 3618 <td>Feb 2011 </td><td>Version 2.5 </td> 3551 <td>[Add] PPP option for sync of clock observations and corrections<br> [Add] Drafted RTCMv3 Galileo ephemeris messages 1045<br> [Add] Drafted RTCMv3 Multiple Signal Messages<br> [Add] Optional specification of sigmas for coordinates and troposphere in PPP<br> [Add] Include Galileo in SPP<br> [Add] Include Galileo observations in output via IP port<br> [Add] Include Galileo observations in output via RINEXv3 files<br> [Mod] Interface format for feeding a real-time engine with observations<br> [Add] Correct observations for antenna phase center offsets<br> [Add] Combine orbit/clock correction streams<br> [Add] Specify corrections mountpoint in PPP tab</td>3619 <td>[Add] PPP option for sync of clock observations and corrections<br> [Add] Drafted RTCMv3 Galileo ephemeris messages 1045<br> [Add] Drafted RTCMv3 Multiple Signal Messages<br> [Add] Optional specification of sigmas for coordinates and troposphere in PPP<br> [Add] Include Galileo in SPP<br> [Add] Include Galileo observations in output via IP port<br> [Add] Include Galileo observations in output via RINEXv3 files<br> [Mod] Interface format for feeding a real-time engine with observations<br> [Add] Correct observations for antenna phase center offsets<br> [Add] Combine orbit/clock correction streams<br> [Add] Specify corrections mountpoint in PPP panel</td> 3552 3620 </tr> 3553 3621 … … 3908 3976 3909 3977 <p> 3910 The example configurations assume that no proxy protects your BNC host. Should a proxy be operated in front of BNC then you need to introduce its IP and port in the 'Network' tab.3978 The example configurations assume that no proxy protects your BNC host. Should a proxy be operated in front of BNC then you need to introduce its IP and port in the 'Network' panel. 3911 3979 </p> 3912 3980 … … 3957 4025 3958 4026 <li>File 'PPPGoogleMaps.bnc'<br> 3959 The purpose of this configuration is to track BNC's point positioning solution using Google Maps or Open StreetMap as background. BNC reads a RINEX Observation file and a RINEX Navigation file to carry out a 'Standard Point Positioning' solution in post -processing mode. Although this is not a real-time application it requires the BNC host to be connected to the Internet. Specify a computation speed, then hit button 'Open Map' to open the track map, then hit 'Start' to visualize receiver positions on top of GM/OSM maps.4027 The purpose of this configuration is to track BNC's point positioning solution using Google Maps or Open StreetMap as background. BNC reads a RINEX Observation file and a RINEX Navigation file to carry out a 'Standard Point Positioning' solution in post processing mode. Although this is not a real-time application it requires the BNC host to be connected to the Internet. Specify a computation speed, then hit button 'Open Map' to open the track map, then hit 'Start' to visualize receiver positions on top of GM/OSM maps. 3960 4028 </li><br> 3961 4029 … … 4006 4074 <tr><td><b>Option</b></td><td><b>Affiliation</b></td></tr> 4007 4075 <tr><td>[General]</td><td>Settings: Group</td></tr> 4008 <tr><td>startTab=</td><td>Internal: Top tabindex</td></tr>4009 <tr><td>statusTab=</td><td>Internal: Bottom tabindex</td></tr>4076 <tr><td>startTab=</td><td>Internal: Top panel index</td></tr> 4077 <tr><td>statusTab=</td><td>Internal: Bottom panel index</td></tr> 4010 4078 <tr><td>font=</td><td>Internal: Used font</td></tr> 4011 4079 <tr><td>casterUrlList=</td><td>Internal: Visited URLs</td></tr>
Note:
See TracChangeset
for help on using the changeset viewer.
