Embed Size (px)
Citation preview
1
EZSurv® Post-Processing BAP Precision GMS Data
2
EZSurv and BAP GMS
• GeoMobileSolution (GMS from BAP precision, V.0.0.1.8 and higher) generates different data files including GNSS observations files (on the Flinth or Forge data collector) along with SQL Lite files along with a project file (*.emp). The Post-Processor requires all these files to calculate post-processed positions for each layers (point, line and polygon).
• GNSS Observations files (*.bp3), as recorded by GMS includes all required GNSS data for post-processing (observations and orbits).
• EZSurv updates the SQL Tables (*.ema) with post-processed positions.
You need EZSurv version 2.94.2324.00 or higher
EZSurv and GMS Data Flow
GMS
SQL files with
updated *.ema files
GMS
SQL Files
Real-time scenario
Post-process scenario
Post-Processing is a simple step
inserted into the data flow.
Post-Processing simply writes Corrected positions in the *.ema file.
Post-Processing
3
SQL Files
GMS Office
GMS data collection the field
4
GMS Trajectories
• Trajectories are created when a rover file (GNSS observations) is combined with base station data (covering the rover file time span). A trajectory is similar to a typical RTK run (can be seen as an offline RTK run).
• EZSurv can automatically creates and post-process trajectories with the submitted GNSS data files. The match between rover files and Base Station data is automatically done.
Trajectory (or RTK Survey)
A typical GMS survey includes many feature points, lines and polygons
5
If you are using a commercial Provider, check it properly in the Tools/Base Station/Provider Manager
Configuring Base Station Providers To be done only once, if required
If you want to access Base Station data from a provider, make sure it is checked in the Edit/process parameters (download section)
6
• EZSurv generates automatically all trajectories using field metadata («start and end time» of each observation file, as well as their status, static or kinematic)
• Make sure that Maximum distance option is checked and input a proper distance tolerance (maximum distance between your rover and the Base). The distance between Base and rover will affect the final accuracy (shorter is the
distance, better will be the post-processed positions accuracy)
Configuring Trajectory Parameters To be done only once
7
• Usually, this has to be done once if the user always uses the same reference system.
• Select the General tab from the Tools > Options. In the Units section, select your unit of measure (International Feet, Metric or US Survey Feet).
Configuring Unit of Measure To be done only once
8
• Select Tools>Mapping Systems>Selectors
• Then select your reference
Set your Geo Reference To be done only once
Select WGS84 if you are not sure
9
Importing your GMS Data in EZSurv
• For the GMS data: Select Observations > Import… or simply drag and drop your *.emp file into the observations folder of the Post-Processor.
• For the Base: Select Observations > Import… or simply drag and drop your receiver binary file *.bp1 (into the observations folder of the Post-Processor
View/Project Manager
This «use case» is typically used when users are working only in PP
Typical use case: You run your field survey with GMS software and you collect GNSS data at a Know Base
Station (our own base) with GeoAssist.
10
Setting your Base Station
• To set your private Base Station, go to the Site Editor using Edit > Site:
o select your base station site in the «site name» dropdown box, o Set it as «Use as reference coordinate» o enter its coordinate (in proper mapping system/datum).
• Using the Occupation tab of the Site Editor, enter the its antenna model and height (for GIS application you can use «none» without to much impact on accuracy).
11
When your *.emp file is imported into the Observations folder, you have access to a list of all your field positions in Analysis > Survey Sites > Field Coordinates.
Processing GMS Data – Field positions
Positions from line features
Positions from point features
Positions from polygon features
12
Processing GMS Data– Start Processing
Select Process Auto... from the Tools menu to start the GNSS post-processing (or press F9 on the keyboard). The following steps are performed automatically:
> scan for base stations. > merge base data (if required). > define trajectories/baselines. > post-process the data.
If you are using a Base Station provider, before processing, make sure your base station data is available. Some providers are generating hourly files whereas others are using daily files! See with your provider for the exact time of availability of their base station files on their FTP site.
13
• The Process Summary is displayed once the GNSS post-processing is completed.
• Close the Process Summary windows, select Save as from the File menu, EZSurv will propose you a project file name and a folder, then click Save.
Processing GMS Data – Updating RAW
When you save your Post-Processor project, EZSurv automatically updates your *.ema files with post-processed positions.
14
After post-processing, you have access to a list of all your positions in Analysis > Survey Sites > Post-Processed Coordinates.
Processing GMS Data – PP positions
15
Processing GMS Data – Back to the data flow
At this point in time, you are back, with your corrected/updated *.ema file, to your usual data flow.
GMS SQL Files
Usual user
data flow
Post-Processor
«Corrected» GMS
SQL Files
GMS Office software
16
GMS Coordinates – EZSurv CSV Export
Tools > export > Sites…
• Click on to access the Profile Editor
• Then select your parameters, order them using the «Move up» and «Move down»
• Save it under a specific name
If there is a need for, EZSurv can export GMS coordinates into a CSV file. CSV export can be configured according to your needs. All parameters related to a post-processed point can be exported. You can configure a CSV output and save it using a profile.
