OK, so those who use a digital level (why wouldn't you?)...
do you use it like a standard level, and write down the observations in the fieldbook (and therefore defeat one of the main advantages of using a digital level)...
or...
Do you download the data file and process it, adjust, etc?
I have, in the last 2 days, come across two totally different entities (one state, one private) that simply write stuff in the book, and then use those raw elevations. No adjustment, no processing. The private sector company said they didn't know how to download it.
I find it hard to believe that this is still going on, more than 20+ years after the first digital level came out. The company I worked for bought a digital level in the early 90's...first thing I did was write a program to process the data. Nowadays I now there are automated ways to deal with the data.
I posted this request a few minutes ago, but it didn't show up for whatever reason...can someone send me a description of the file format in the Sokkia digital level? I already have setup my program for Topcon, Zeiss/Trimble, and Leica. This latest fiasco is with a Sokkia file (that is if they can get it downloaded).
We keep simple notes, descriptions and such, in a book. I download the data and incorporate it in TBC, though, as part of my LSA.
Digital levels are absolutely the bomb-diggity.
we write down the elevation at each point we want to process (i.e. BM, TBM, traverse station, etc). This helps in case a number was entered wrong or not at all. TP's do not get recorded.
The Sokkia and newer Topcon Digital Levels can export an SDR33 file.
It is a little tricky. You need Topcon/Sokkia software loaded.
Then you go to
My Computer >Topcon Digital Level >Add New Level
Point it to your COM port and proper settings
Then double click on your setting
You will see file1.sdr - this is a dummy file, nothing it it yet.
Double click in the file1.sdr and you will see this
The SDR format looks like...
And the report looks like....
We write it in a field book. We have a Leica level, maybe 15 years old, and I never liked the software that was onboard. As far as adjustments, never really did anything complicated in regards to that. Say I start on a benchmark, run 1 mile to a new one, come back and close on the starting benchmark and misclose by 0.02' I just adjust the new benchmark by 0.01'. Most of the time the digital level does so well I often don't adjust anything.
> Do you download the data file and process it, adjust, etc?
I carry a field book just in case, but normally don't write anything in it when running levels. I store the observation data in the gun (Leica DNA03), then download the GSI file and use bit of custom software to turn it into a human-readable format similar to field notes. From that file I hand-calc the differences and distances between stations and enter those into a Star*Net input file.
I use a Topcon DL 102 and write the foresight's, backsights and elevations in the FB. The reason why is we do State work and they want to see level notes in the field book. I also download the info and adjust. Usually there's not much to adjust.
I usually write it in the fieldbook and store it in SurvCE. SurvCE will do Sokkia and Lieca levels, maybe others, not sure. I think you can stake to a centerline or station/offset with it, but I haven't fooled around with it yet, haven't really needed to.
I have a cheaper Lieca Sprinter 100m construction grade level, and it gets amazing closures. One of the biggest benefits to me is, it won't read the rod wrong, like an old dyslexic surveyor such as me is prone to do.
We have two Zeiss/Trimble geodetic levels at LSU. One is for indoor optical tooling and that data is recorded manually. The other is for outdoor geodetic leveling and we use the data logging storage and Chuck Whalen's software package for getting it into BlueBook format.
I still have to make a sketch, so why not book as well. My loops are usually fairly short, for the type work that I do, there's no LS, just hit same elevations a couple of times with a couple of runs.
I have been using a Leica DNA since 2002 and I don't think I have booked anything in the last 12 years, that defeats one of the best features, no booking errors! LGO will do simple run reductions and produce a nice field book output.
SHG
I had a 1990s era Topcon DL level. Never could get it downloaded so I booked it.
Now I have a Trimble whatever-they-call-it and it couldn't be simpler. Just run a line level and copy the TXT file onto a thumb drive, it's even readable.
I carry a field book and make the typical table; + HI - SS ELEV DESC // REMARKS:
I make check marks in the fields where plus, minus and rod shots would traditionally have values, the HI field will be forever blank but I put it in the table out of habit. I put the letter T next to the check mark on inverted shots.
I book the closing elevation and delta, if I am applying an adjustment I run the program and record the correction per turn applied.
In a case where there is a real long run of turns I might be tempted to use an ellipses instead of booking every turn but in general I like the pause and brief mental check in that I get out of making the note and closing the book. I usually only run like 2000 ft at a time.
I have worked at two companies previously where it was required to book the numbers, one because they could not get the old gif card reader to work and at the other they were just generally suspicious of electronic data storage.
> Now I have a Trimble whatever-they-call-it and it couldn't be simpler. Just run a line level and copy the TXT file onto a thumb drive, it's even readable.
The Leica GSI format isn't very user-friendly, and I didn't want to spring for the Leica leveling software, so I went the roll-your-own route. Here's what a typical run looks like after putting it through my converter:
[pre]
=================================================
Begin conventional observations.
=================================================
Begin new level line:
+ HI - Elev Dist Balance Cumulative Distance
BM01 0.06410
1.57211 1.63621 19.02
0001 1.79203 -0.15582 19.52 -0.50 38.53 Meters
0.56625 0.41043 19.59
0002 1.81213 -1.40170 19.35 0.24 77.47 Meters
0.67616 -0.72554 18.25
0003 1.87118 -2.59672 18.06 0.19 113.78 Meters
0.77420 -1.82252 12.07
0004 1.70383 -3.52635 11.98 0.10 137.83 Meters
0.74691 -2.77944 10.97
0005 1.77537 -4.55481 10.93 0.04 159.74 Meters
0.52049 -4.03432 12.47
0006 1.63331 -5.66763 12.41 0.07 184.62 Meters
1.20693 -4.46070 63.98
0007 1.42528 -5.88598 64.26 -0.29 312.86 Meters
1.28313 -4.60285 60.01
0008 1.35774 -5.96059 60.05 -0.05 432.92 Meters
1.34244 -4.61815 40.95
0009 1.42737 -6.04552 40.85 0.10 514.73 Meters
0.91464 -5.13088 41.60
VP01 1.55021 -6.68109 41.48 0.11 597.80 Meters
1.72591 -4.95518 41.41
0009 0.95441 -5.90959 41.67 -0.26 680.88 Meters
1.25948 -4.65011 62.66
0010 1.21711 -5.86722 62.35 0.31 805.88 Meters
1.35500 -4.51222 62.02
0011 1.21887 -5.73109 61.73 0.29 929.64 Meters
1.67758 -4.05351 15.96
0012 0.59620 -4.64971 16.31 -0.35 961.91 Meters
1.84133 -2.80838 10.85
0013 0.58087 -3.38925 11.12 -0.27 983.88 Meters
1.85754 -1.53171 11.36
0014 0.67822 -2.20993 11.55 -0.19 1006.78 Meters
1.88960 -0.32033 11.41
0015 0.66040 -0.98073 11.21 0.20 1029.41 Meters
1.87135 0.89062 9.83
0016 0.59860 0.29202 9.65 0.18 1048.89 Meters
1.69272 1.98474 14.71
0017 1.13436 0.85038 14.40 0.31 1078.00 Meters
1.08590 1.93628 14.49
BM01 1.87287 0.06341 14.01 0.48 1106.50 Meters
=================================================
Total distance: 1106.50 Net balance: 0.71
[/pre]
Sokkia levels (or the ones I am using SDL 50) has NO on board option to enter the station name:-S
It only records the BS/FS entries so you have to note what the readings are for the BMs.After you download the data using Sokkia Link and convert the txt file into Excel, you then locate the FS reading that match what you wrote on your fieldbook. Heaven forbids if the fieldbook gets wet or lost!:'(
Wow, that is amazing that you don't have the capability to enter pojt info with the Sokkia.
I will be the first to say that the Zeiss M5 format could definitely be improved, but it does work and it does have all the info needed. You can put in point numbers and point codes, as well as notes, time stamps, etc.
M5 was developed when memory was at a premium, I am not sure why Trimble does not change it. Oops, I shouldn't say that...next thing you know they will make it proprietary!
Here is what my program produces, this is a short run to tie between two NSRS BM's:
FILE C:projects14051levelsrun2.dat PROCESSED ON 10-21-2014 AT 15:23:54
Units of measure - METERS
********************************************************************************
******BS****** INST ******FS****** GROUND CUMULATIVE
ROD DIST ELEV ROD DIST ELEV DIST UNB STA NAME
0.000 M11
3.5003 14.7 3.5003
0.2312 22.5 3.2691 37 -8
1.4385 49.9 4.7076
2.1655 46.5 2.5422 133 -4 HL120
2.1491 46.5 4.6913
1.4225 49.8 3.2688 229 -8
0.1679 20.7 3.4366
3.4368 17.2 -0.0002 267 -4 M11
It also makes an input file for geolab at the same time:
OHDF M11 HL120 2.5422 0.0004
OHDF HL120 M11 -2.5424 0.0004
[pre]For M5|Adr 1|TO eel-1106.dat | | | |
For M5|Adr 2|TO Start-Line BF 1| | | |
For M5|Adr 3|KD1 1 1| | |Z 100.0000 m |
For M5|Adr 4|KD1 1 3 1|Rb 1.5069 m |HD 11.42 m | |
For M5|Adr 5|KD1 2 3 1|Rf 1.5679 m |HD 11.21 m | |
For M5|Adr 6|KD1 2 1| | |Z 99.9390 m |
For M5|Adr 7|KD1 2 3 1|Rb 1.5086 m |HD 11.38 m | |
For M5|Adr 8|KD1 3 3 1|Rf 1.5509 m |HD 11.24 m | |
For M5|Adr 9|KD1 3 1| | |Z 99.8967 m |
For M5|Adr 10|KD1 3 3 1|Rb 1.4905 m |HD 15.27 m | |
For M5|Adr 11|KD1 4 3 1|Rf 1.5654 m |HD 14.85 m | |
For M5|Adr 12|KD1 4 1| | |Z 99.8218 m |
For M5|Adr 13|KD1 4 3 1|Rb 1.5152 m |HD 15.18 m | |
For M5|Adr 14|KD1 5 3 1|Rf 1.5590 m |HD 15.25 m | |
For M5|Adr 15|KD1 5 1| | |Z 99.7780 m |
For M5|Adr 16|KD1 5 3 1|Rb 1.5054 m |HD 11.39 m | |
For M5|Adr 17|KD1 6 3 1|Rf 1.5675 m |HD 11.44 m | |
For M5|Adr 18|KD1 6 1| | |Z 99.7159 m |
For M5|Adr 19|KD1 6 3 1|Rb 1.5088 m |HD 11.37 m | |
For M5|Adr 20|KD1 7 3 1|Rf 1.6306 m |HD 11.69 m | |
For M5|Adr 21|KD1 7 1| | |Z 99.5941 m |
For M5|Adr 22|KD1 7 3 1|Rb 1.6303 m |HD 3.88 m | |
For M5|Adr 23|KD1 8 3 1|Rf 1.6140 m |HD 3.66 m | |
For M5|Adr 24|KD1 8 1| | |Z 99.6104 m |
For M5|Adr 25|KD1 8 3 1|Rb 1.6250 m |HD 11.77 m | |
For M5|Adr 26|KD1 9 3 1|Rf 1.5198 m |HD 11.29 m | |
For M5|Adr 27|KD1 9 1| | |Z 99.7156 m |
For M5|Adr 28|KD1 9 3 1|Rb 1.5943 m |HD 11.45 m | |
For M5|Adr 29|KD1 10 3 1|Rf 1.5320 m |HD 11.40 m | |
For M5|Adr 30|KD1 10 1| | |Z 99.7779 m |
For M5|Adr 31|KD1 10 3 1|Rb 1.5706 m |HD 15.36 m | |
For M5|Adr 32|KD1 11 3 1|Rf 1.5226 m |HD 15.06 m | |
For M5|Adr 33|KD1 11 1| | |Z 99.8259 m |
For M5|Adr 34|KD1 11 3 1|Rb 1.5842 m |HD 15.01 m | |
For M5|Adr 35|KD1 12 3 1|Rf 1.5007 m |HD 15.03 m | |
For M5|Adr 36|KD1 12 1| | |Z 99.9094 m |
For M5|Adr 37|KD1 12 3 1|Rb 1.5335 m |HD 11.26 m | |
For M5|Adr 38|KD1 13 3 1|Rf 1.5027 m |HD 11.40 m | |
For M5|Adr 39|KD1 13 1| | |Z 99.9402 m |
For M5|Adr 40|KD1 13 3 1|Rb 1.5617 m |HD 11.33 m | |
For M5|Adr 41|KD1 14 3 1|Rf 1.5041 m |HD 11.29 m | |
For M5|Adr 42|KD1 14 1| | |Z 99.9978 m |
For M5|Adr 43|KD1 14 3 1|Rb 1.6299 m |HD 3.68 m | |
For M5|Adr 44|KD1 1 3 1|Rf 1.6255 m |HD 3.85 m | |
For M5|Adr 45|KD1 1 1| | |Z 100.0022 m |
For M5|Adr 46|KD1 1 1|Sh 0.0022 m |dz -0.0022 m |Z 100.0000 m |
For M5|Adr 47|KD2 1 14 1|Db 159.75 m |Df 158.66 m |Z 100.0022 m |
For M5|Adr 48|TO End-Line 1| | | |[/pre]
I learned something...
put pre in [] brackets before the text then /pre in [] brackets after the text and it keeps the spaces and lines up the text correctly :-).
Post formatting
I've seen pre mentioned before. Don't know what it stands for. It works even though it isn't in the pushbutton list at the right of the entry screen.
What's the difference between code and pre?
Post formatting
> I've seen pre mentioned before. Don't know what it stands for.
Preformatted text.
