Tyler,
In general here’s my current boundary workflow...I’m always happy with the results...and I really stick to this.
I’m definitely a promoter of network adjustment programs...not just cause I like the results but I’m just a nut for file management... I find that programs like StarNet are a good place to gather all my data.
I was using Trimble Business Center for a LONG while...till I made the jump to Javad. Now this is my workflow and it works with all kinds of data...so adjust as you need to
My Equipment:
Javad LS/T2 setup for GNSS
Trimble S7 with Trimble Survey Controller TSC
StarNet v9.1
Carlson Survey 2019
First Round - initial survey & unadjusted Fieldwork:
For initial GNSS work I always start a fresh project file with my coordinate system set to my state plane grid system. If I already have coordinated search points then I use the LS and our State VRN to measure the point I plan to start the base on. Then the T2 base gets started on that known position. If I’m going to start from scratch with just paper in hand I’ll start the T2 base on an autonomous position. Network adjustment needs redundancy...so at each corner or control point I observe a minimum of 2 or three positions. Naming the repeated locations in the LS with a suffix (easy for StarNet...explained below) ex: 1, 1A, 1B, 201, 201A, 201B...or...1, 1.1, 1.2...201, 201.1, 201.2
When I get control and GNSS work done I export a quick csv file of the project to a usb drive...and transfer this to my total station controller.
In Trimble Survey Controller I also start anew job with a state plane grid coordinate system and link or import the file. Then do my total station work/traverse. Trimble files are clean in that they “stack” data in the “store another” option. So tie shots and cross checks are stored as the same point number as the first Javad point number...some data collectors wont let you do that...so toy around with it’s ability to work with a suffix.
As with any workflow...if you pay attention to good fieldwork / point numbers / field codes you can get to the point where there is zero editing of your data collector file.
Back in the Office:
First I let the LS run it’s DPOS routine and browse the post processed data.
When i’m ready to get something into CAD. I pass everything through StarNet. (Personally I wouldn’t combine any GNSS / Total Station data any other way...or it can get real sloppy real quick.)
~ Files:
The exported Trimble total station file is a .DC file and it gets imported through StarNet’s TSC converter to StarNet’s .dat format file.
Sounds complicated...but it’s real simple...each major manufacture can export to StarNet....
The Javad LS current version of JField will now export a StarNet .gps format vector file which is real nice.
These resulting files (.dat/.gps) get linked to the StarNet project.
For control I either hold the DPOS processed base location or if I’ve made a geodetic tie I will hold the published coordinate. Generally for a new boundary survey there is one horizontal and one vertical point held fixed.
These can be entered as a C record line. (See image)
StarNet 7 and newer allows an input line called “.alias” at the top of the GNSS vector file. Rather than edit the point numbers below...you simply match them by alias. If you measure multiple point numbers on an iron. You can enter the alias like this:
.alias name 201 202 203 504 652
(Usually requires a field sketch for me...)
If you utilize a suffix style point number system you can enter the alias like this:
.alias suffix 201 a b c d
Or:
.alias suffix .1 .2 .3 .4
(This style is much easier to remember and keep straight)
Additional files can be added same way...
Ground Scale:
In StarNet there is an “other files” option where you can output a ground scaled file by selecting a specific point. [Options - Project... - Other files - Settings...] (See image)
I usually choose a boundary corner that will make a good tie line to my geodetic control point. After choosing this and processing the network adjustment successfully StarNet outputs a comma separated .gnd file.
The header of this file is 15 lines long contains all the local site info.... you can manually transfer this back to your Javad LS coordinate system. It can also be imported directly into Carlson if you specify that you want to skip the first 15 lines.
Now you’ve got adjusted and scaled to ground files in CAD.
Sounds like a process when you spell it out but if you notice there is no data editing...no cut and paste...no messing with file extensions...it’s as clean as your fieldwork is tight...and it’s untouched. The only entering of data is the control coordinate line and the .alias lines.
Going Back in the field:
For total station work it’s real easy...scale 1 from this point. Output and Link an adjusted file...more search points...etc...and go for it. As you perform subsequent days of fieldwork just export your raw files and compile them into the StarNet project.
For the LS you can either start a fresh project with the ground scale coordinate system parameters or you can “adjust to ground and rename” the existing coordinate system using the same iron/parameters listed on the .gnd file header from StarNet. After completing more field locations you can export further vector files by date or by range of numbers. This keeps repeating vectors from creeping into the network adjustment.
Ultimately the goal with this workflow is to get the project into a ground system and keep the StarNet project the master data set for the end product survey. The first dataset that you get on ground is the full circle I describe here...subsequent days just file right in order.
As you start the base day after day, just use the suffix to the point number and the .alias command in StarNet will keep them merged in your adjustment.
Here’s a video on the .alias command:
Hope that helps you!