Pathfinder Office Software
►
‘Project’ is the main way in which data is organized in PFO. A directory
where Pathfinder Office looks for data. There are three subdirectories in
a project for organizing other kinds of files: base, export and backup.
►
The backup subdirectory contains backup copies of field collected files.
When data is downloaded from the datalogger, an extra copy of each
file is placed in this subdirectory.
►
The base subdirectory is where you should store base station files for
differential correction.
►
The export subdirectory is the default target location when GPS files
are exported for use in another program.
►
NOTE: Do not rename or delete any of the default folders in the project folder or
Pathfinder Office will not open the project.
Pathfinder Office Software
Interface
►
►
►
►
►
►
►
►
►
Mouse and menu driven, like any Windows program.
File: open/close/save data files, select projects, control background
map display.
Edit: edit data files.
View: chose map or timeline view of data files, zoom, pan, set graphics
display.
Data: view the details of each feature/position in data files.
Utilities: data transfer, differential correction, export, create data
dictionary, and more.
Options: set units, coordinate system and time zone.
Window
Help
Pathfinder Office Software
Directory Structure
►
C:\Users\username\Documents\GNSS Projects\project_name\roverfiles
(corrected and uncorrected)
\base (basefiles)
\export (shapefiles)
\backup
►
C:\Program Files (x86)\Common Files\Trimble\Planning
Almanacs (ephemeris data), by default, are saved in this location and
are named almanac.alm. Whenever you download a new almanac it
will overwrite the old almanac, and that is fine. You do not need to
save old almanacs.
Pathfinder Office Software
File Names
Rover Files (Field data): N 0326 17 a
User
selected
prefix
Base Files:
Month
&
Date
Hour
(GMT)
R 20326 17
Prefix
selected
by base
station
Year,
Month &
Date
Hour
(GMT)
Extensions:
.ssf: uncorrected (raw) rover file OR a base file
.cor: differentially corrected rover file
.ddf: data dictionary
File
Indicator
(a-z)
Pathfinder Office Software
File Management
►
Implement a project file management system, including directory
structure and file naming convention, before you go out in the field for
the many files that may be generated.
►
Keep all data on one machine that is regularly backed-up.
►
Create one folder for each project or particular field season.
►
Keep GPS data separate from GIS data.
►
Keep separate folds for raw GPS data, interim GPS data, and final GPS
data.
►
Keep separate folders for interim GIS data and final GIS data.
Pathfinder Office Software
File Management (example)
PFO Data Dictionary Editor
Feature Name….Bear
Attribute Name….Texture
Attribute Value….Soft
Data Dictionary - The power of a
GIS Data Capture Tool
►
Controls how location information is stored (e.g., how
many positions are averaged for a point, logging
interval)
►
Allows us to collect information efficiently (as opposed
to writing in a notebook or using field-sheets)
►
Organizes information for GIS / geodatabase
(essentially pre-constructs your attribute table)
►
Enforces consistency (e.g., providing drop-down
menus, radio buttons, etc.)
Data Dictionary - Design Considerations





Consider how to address the stated research questions
List the target features
– points, lines or polygons
List the attributes for each feature class and identify their type
– menu (fewer errors, easily queried)
– free text (flexible, handles the unexpected)
– numeric (enumerated, range, derived)
– automatic value (e.g. increment, date)
Consider including common data fields
– e.g. a linking ID number
Design to accommodate the unexpected or uncertain
Setting Up Your Features

Feature Level
 Properties
 Default Settings
 Symbol
Labeling – Cause and Effect
in TerraSync
in Map Section
ID#, Feature Name
Label 1 (Attribute Value)
Label 2 (Attribute Value)
Northing
Easting
Elevation
…View Labels (Attribute Values)
in TerraSync
in Update
ID#
Feature Name
Label 1 (Attribute Value)
Label 2 (Attribute Value)
At the Feature Level
►
8 Character limit for Shapefile Export
►
If you must use more, ensure first 8 char are diff.
►
Generally use 1 sec. log interval (exception is walking)
►
Use same color for like features
►
Symbols are not transferred to GIS
Standards for Attributes

Attribute Types
Standards for Attributes

Menu Type
 Name/Alias
 User Codes vs Value
 Display differences
 Repeat or Not
 Field Entry
 Conditions
Invisible Field Entry
Not Seen by Field
User
Populates into
GIS
Use for Attributes
that wont
change for a
summer
Eg. Park Name
Separators Attributes
Not passed into GIS
Use succinct alias to
tell user what is here
“DON’T EDIT!”
Breaks up Attributes in
logical stages
When collapsed, hides
complexity
File Name Attributes
Passed into GIS as Text 230
characters
Useful for hyperlinking of
photos
Can launch any windows file
(eg. Excel)
Conditional Attributes
Controls how TS can autopopulate a dependent
attribute
Set conditions to an attribute
above
Can auto assign an attribute
overriding an attribute
default value
Extremely powerful
Attributes: Number of Characters Limitations
Attribute Names - 10
Alias – 40
Menu Attribute Values - 40
Text Attributes - 230
At the Attribute Level
10 Character limit for Shapefile Export
► If you must use more, ensure first 10 char are diff.
► Use Default values sparingly. If user enables repeat, and
alters default value, next feature will use last value
► Use Field Entry – Required for critical settings
► Place menus higher up in attribute list for maximum
conditional use.
► Group attributes and place most important at top
► Conditional Attributes do not carry over when copying and
pasting among DDF’s
►
Guidelines
Test, test, test
Ensure co-workers
understand data
dictionary
Use same data
dictionary for all data
collection within a
project
Print,
Import,
Export
Pathfinder Office Example
ArcGIS
Feature Name
Veg
Shapefile Name
Feature Classification
Point
Geometry Type
Attribute Name
VegClass
Field Name
Attribute Type
Menu
Attribute Value
Shrub
Tree
Other
Value
Pathfinder Office Example
ESRI
Feature Name
Veg
Feature Class Name
Feature Classification
Point
Geometry
Attribute Name
VegClass
Field Name
Attribute Type
Menu
Data Type (Text)
Attribute Value
Shrub
Tree
Other
Coded Values