GPS PATHFINDER OFFICE BACKGROUND FILE IMPORT SOFTWARE
If you collected 10 positions for the point feature, the software spatially averages those positions to come up with a single location. Here is how Pathfinder Office calculates that value: In other words, if you were using a Geo7X, H-Star receiver, you would want very small numbers to be revealed. The standard deviation is a precision value calculated by Pathfinder Office that reflects how closely the individual GNSS positions were able to repeat to themselves.
![gps pathfinder office background file import gps pathfinder office background file import](https://land-infotech.com/kedai/Trimblegeo7x-2.jpg)
Now, let’s look at the standard deviation of each point feature. Does it look like it’s supposed to, based on how and where you collected the data? Okay check. You open the corrected file in the Pathfinder Office Map window and check your file visually. This is ideal when selecting a base station when using a multi-constellation GNSS receiver. Let’s also assume that the base station file contained both GPS and GLONASS data with an integrity index of 80 or higher. You post process the data file with a base station close enough to your project site to achieve the rated accuracy of your field device. The first step is to perform differential correction, assuming that you did not have a real time correction source in the field. Here are some recommended steps you can go through to insure that you are exporting your best data when it comes time to send it to GIS. When you bring your data back into the office and look at it in Pathfinder Office, you notice that some of your features don’t look right. This is certainly a common environment in the Pacific Northwest and in many other areas. Let’s also say you are using a handheld GNSS mapping system with no external antenna. Let’s say you are collecting data in a moderately open area where hills and some trees are present.
![gps pathfinder office background file import gps pathfinder office background file import](https://www.miqrogroove.com/wp-content/uploads/2012/07/goodnotes-import-screen-680x906@2x.png)
Short of this, there are going to be errors in your dataset, most of which you can remove before sending it to GIS or CAD. This is one in which there are no obstructions higher than the GNSS antenna and the data capture is performed perfectly by an experienced user. The only users who can almost avoid this are those who perform their field work in a completely open environment. Try as we might to setup our data collection software correctly and use a repeatable field data collection protocol to collect high accuracy data, there’s not much we can do to prevent GNSS errors from creeping into our features.