Star*Net question

You are correct that .survey is the Spectra Precision Survey Pro (fka TDS) native format.

If you download "Style Sheet Converter" from the Spectra website you can use that to convert your .survey file to .jxl format. Then use Star*JobXML (Trimble) to convert that to StarNet format.

The other way is to find somebody with a Spectra Survey Pro Data Collector to load up your .survey file and export the .raw. Then StarTDS will convert the .raw to .dat format. I'd do that, but the collectors available to me are in the field just now.

The .survey is Spectra's dynamic controller file that replaced the old TDS .job/.raw version. I'm running Spectra SP on one of my controllers and will convert the .survey to the old .job/.raw format. If you just need it converted let me know.

Trimble's Ascii File Generator has a stylesheet available to convert .jxl to .rw5, which StarTDS could handle.

I found a work around. I imported the files into TBC, and then exported out to Trimble Data Exchange Format, and Star*Net was able to convert that.

I have hardly used Star*Net since I bought it in March. I was surprised to find that EACH converter costs $200. I have done a few conventional adjustments, but this will be the first adjustment of RTK (VRS) vectors. Usually I do all my adjustments in Geolab after loading the data into my database, but since I can't read a .survey file I cannot do that workflow.

I didn't like what I saw in TBC. Onservations were made on 20 days (2 files), and SP created a virtual base at the same location, but called it three different names, and then created another virtual base at a different location with a previously used name. Not sure how it kept creating the same virtual base day after day, that is different than what Survey controller or access does.

If you have StarNET PRO ( which I assume, since you are doing GPS) all converters for GPS data are included. It's conventional data converters which need to be purchased separately.

Ok, thanks. Like I said, I am a newbie to star*net. I do have the pro version.

Figured out a way to get what I want (data into my database so that I can analyze it).

You can create a custom export in TBC, and pick the fields, separator, etc. The only thing missing is the variance/covariance data for each vector. There is no option to export that, but it is in the trimble data exchange format (TDXF).

The vectors are numbered in the custom export, but not in the TDXF (why not?), so it is a bit difficult to relate the data from each type, but not impossible. I imagine I could use the DX, DY, DZ from each to find the matching record, as all three components are unlikely to be the same in different sessions. But that seems like a basic data feature that should be included.

If you convert a .jxl file using the Star*JobXML converter (which you have) you will get covariance data and numbered vectors in your StarNet format file.

Thanks. That sounds like a good converter to have.

edit: actually, the only thing in the .jxl file are coordinates, not vectors. I tried expoting from TBC as a jxl and also first exporting to a .job file and then converting that to a .jxl. In both cases all of the points are showed as "keyed in".

John Hamilton, post: 346847, member: 640 wrote: Thanks. That sounds like a good converter to have.

edit: actually, the only thing in the .jxl file are coordinates, not vectors. I tried expoting from TBC as a jxl and also first exporting to a .job file and then converting that to a .jxl. In both cases all of the points are showed as "keyed in".

There is a setting in the survey style to store positions or vectors. That may make a difference. Will only affect new data though.

Norman Oklahoma, post: 346846, member: 9981 wrote: If you convert a .jxl file using the Star*JobXML converter (which you have) you will get covariance data and numbered vectors in your StarNet format file.

You get numbered vectors by importing the TDEF file, too, but they're sequential starting with a user-specified integer rather than corresponding to the TBC vector IDs. Are you sure that the .jxl export uses the Trimble vector numbers?

Yes that is annoying. I had Access delete a bunch of conventional observations since I rotated and translated them (I learned don't do that) but was able to turn them back on in TBC. I found no way to export them. The JXL thing and the TDEF thing only exported coordinates which is not very useful considering you can do that with a CSV file.

I finally just opened the observation spreadsheet and cut and pasted them into Excel then manually made a DAT file.

My comments were predicated on John having a Spectra Precision .survey file as a starting point, and Spectra offing a utility to convert to .jxl. I didn't mean to imply that there was no other way to go.

The Star*JobXML converter assigns vector numbers beginning at whatever number the user assigns, defaulting to 1. I don't think that there are vector numbers in the .jxl.

It is quite possible to have a .survey file that contains nothing more than imported coordinates. Naturally if that were so there would be nothing more than imported coordinates in the .jxl file and StarNet data file created from it. Trimble Survey Controller and Access contains settings that regulate the amount of RTK data that is recorded - coordinates only - coordinates plus vectors - coordinates plus vectors plus covariance. Spectra Precision Survey Pro (fka TDS) has no such setting. You get it all. I can't comment on the many other dc programs one might be using.