Is anyone using a Leica DNA level with Trimble Business Center? If so how? I've bee spending an hour or so a day for about a week trying write an export format for our DNA levels. The documentation for both the M5 format(trimble dini) and the Leica format manager are seiously lacking.
Bob
Perhaps it is time to reach out for some tech support, I used the DNA with no problem but all the format set up was done.
I bet someone around here can help, trying to use a trimble soft seems like a really bad idea.
Bobwesternman,
If you are using Leica Geo Office. to import your DNA data there is an easy way to export the data without using a format file. If TBC will accept an ASCII file for level data there is an easy way to do this (but you need to have the data into LGO first).
The level data view in LGO can be customized. While view the level data you can hide or view many different columns. If you right-click on a column header you have a View and a Hide Option. Under the View option you will see allot of different data items you can add as a column. After you have everything you want in the view you can left click and hold on a column and drag it into the order you want it. This is the same as using Excel. The right click somewhere on the data and use the Save As.. command. This will save the view you have into a .CSV which is a comma delimited file with all of you data.
If TBC can accept a ASCII file you should be able to import it quickly.
I wish you the best of luck in your endeavor.
FYI, I use the Leica brand and have a DNA level that goes into LGO very easy, BUT I have no clue how to import the DNA level data into TGO, likely not supported very well between two major competitors. I will say it will probably be via interpreting the XML file output from the level correctly on the import side of TBC. The file I output from the DNA level is via a format file on the level that writes what looks to be an XML file and while the format manager is very powerful from Leica, it is NOT very intuitive as to how it works!
SHG
I guess I should add a little background.
First, the levels are the ONLY Leica hardware we have, so I'm using Leica Survey office, and LevelPak Pro with them, we don't have Geo office. LevelPak pro was written for, I think Windows 98SE, and as far as I've been able to determine, never updated, so I have to run it in XP mode in windows 7 to get it to run at all.
All our other equipment now is Trimble, thus Trimble Business Center.
I never liked Levelpak, or Levelpak Pro. But really none of this really matters much, since we've never gotten a run out of these levels which actually needed to be balanced, and really no one in the office really cares that much about the level files but me.
Shelby, I've been looking at those XML files as something I might be able to transform into the format I'd need, Rec_E aka M5. At first I thought I might be able to create an export format file for the level, but like I said earlier, neither company is very good with their file format documentation.
surveythemark
If you are using Leica Geo Office. to import your DNA data there is an easy way to export the data without using a format file. If TBC will accept an ASCII file for level data there is an easy way to do this (but you need to have the data into LGO first).
I'm not using Geo office, but it's not really necessary to get it into there anyway. I can make an export file format for the level itself, my only problem with that is the format manager doesn't really seem to want to send out all the fields I want from all the observation types. I could probably just send everything to a .csv file, but then I'd still need to manipulate the data again once I got it.
So at this point I'm looking at either building my own export format file for the level, which is kind of tedious since I can only test it by sending it to the level exporting a job and seeing what I need to change, then lather rinse repeat. Or I can export a nice big job in the xml format, and try to reverse engineer that since as far as I can see there are no file specs for that at all, then I need to teach myself some xml programming.
Or I can just keep going as I am and hope we never really need to do anything really drastic like adjusting a really long loop.
Unfortunately TBC does not have the capability to hand input data (i.e. leveled height differences) nor input ascii files with TS data (other than the specified formats).
That is why I do all my adjustments in geolab. I process GPS data in TBC, and maybe topo data, but any traverse, leveling, RTK, etc I process outside of TBC.
> That is why I do all my adjustments in geolab. I process GPS data in TBC, and maybe topo data, but any traverse, leveling, RTK, etc I process outside of TBC.
Star*Net is also excellent for combining and adjusting data from various sources simultaneously.
Hi John,
I've been meaning to get in touch with you.
Kevin told me that if anyone had come up with a method for this, it would be you.
> Unfortunately TBC does not have the capability to hand input data (i.e. leveled height differences) nor input ascii files with TS data (other than the specified formats).
>
> That is why I do all my adjustments in geolab. I process GPS data in TBC, and maybe topo data, but any traverse, leveling, RTK, etc I process outside of TBC.
>
Guess this means nobody has...Yet.
Bob
I don't know if anyone is still watching this thread, but the newest version of TBC 3.61, will now import Leica .gsi files directly.