DM versus SS in Starnet

Check your JXL file records for <AngleUnits> and <LatitudeLongitudeUnits> match what you expect

DM is a direction measurement, SS is an angle.

Check the options on the importer. 

SS should contain all your data for a shot,  HZ angle, VZ angle, SD, IH, RH and Desc.

Hi Mark @norman-oklahoma:

Yep - wondering why the difference between the Trimble and Topcon outputs from the Starnet converters and how to change it from DM to SS (like our old Topcon data - they should be obtaining the same angular data), since this is just a product (or so it appears) of the data converters in Starnet.  What am I not understanding?  

Thanks!

Here is what the "new" Trimble output looks like:

DB 4
DM 3 0-00-00.00 902.2727 90-12-20.80 5.349/5.290 'CP SETIR
DM 3 180-00-00.93 902.2735 269-47-38.80 5.349/5.290 'CP SETIR
DM 105 205-52-39.45 962.6901 89-31-56.74 5.349/6.562 'SETHUB
DM 1000 205-59-11.30 956.6973 89-32-53.92 5.349/6.562 'EP1 B
DM 1003 206-15-47.15 930.1750 89-36-52.04 5.349/6.562 'EP1
DM 1004 206-28-30.74 897.7333 89-42-35.28 5.349/6.562 'EP1

DE

Here is what the "old" Topcon output looks like:

DV 4-5 319.3566 90-14-34.00 5.240/5.050 'CP SETMAG
SS 4-5-1000 160-37-27.00 373.6470 89-47-56.00 5.240/6.500 'EP1 B
SS 4-5-1001 158-58-37.00 372.8520 89-44-42.00 5.240/6.500 'PSCL1 B
SS 4-5-1002 157-27-49.00 373.5170 89-44-03.00 5.240/6.500 'EP2 B
SS 4-5-1003 157-14-59.00 341.6620 89-44-31.00 5.240/6.500 'EP2
SS 4-5-1004 158-54-24.00 341.3320 89-43-37.00 5.240/6.500 'PSCL1

It appears to be the same angular data, just in a different format.  Again, not sure why or if there is a way to change it so the Data Converters display the "new" Trimble data the same as the "old" Topcon data.  

Thanks for looking!

Paul

Having written a few converters over the years, including for STAR*NET input data, I would GUESS that it could be something specific to your workflows, or a shortcoming in the converter itself. At first glance it looks to me like the orientation (backsight) observation is not recognized as a backsight or something along those lines, and as a result it's spitting everything out as direction measurements. If you haven't already, send the support team at MicroSurvey a copy of you input file and they should be able to tell you why it's happening. I have not wirtten any JXL converters so I'm not familiar with what to expect there. Resection setups may require additional logic, which a converter shoudl be handle as well if all the info is in the JXL.

In the Trimble Dc can you export to Rw5 or a .dc file? I have not used the jxl file type.

@gary_g We looked, but couldn't find any .raw or .rw5 or similar data exports from our Trimble software.  We also looked at other formats, but nothing seemed to be what we were wanting either.  Thanks for the interest!

Paul

I was a Trimble user for many years, buts it's been over 4 years now since I last touched one, and 8 since I was a regular user.  Back then, there was a little utility called the "Ascii File Generator" that Trimble put out that will convert your jxl's to rw5's.  

Also, you can download Trimble DC v10.0 and v10.7 formats.  Try that and the "TSC converter" of StarNet. 

I've just found that the different converters read their associated file formats and produce different outputs. So I go with that. It all works.

@paul 

Not part of the standard install, there is an Access to RW5 export stylesheet available on the Trimble website

https://help.fieldsystems.trimble.com/trimble-access/latest/en/downloads-stylesheets.htm

Haven't used it myself, but the price is right (free)

@norman-oklahoma Yeah - that seems like the weird part to me, that they don't all have the same output settings, so they affect the solution differently.  

Update: we did finally find something that our data collector could convert to (SDR33) that we could use the Starnet Converter program (SDR) to import something like we wanted to see, which pulled the number count for the sideshots out of the adjustment and changed the solution.  Still unsure why these sideshots would be counted when they weren't tied to anything.  

But we figured it out.  

Thanks for everyone's help!

Paul

I think besides the rw5 export you can find a style sheet specifically for StarNet as well. I think I remember seeing one as I try to checkout any style sheets as they come around for using as a base to what might be close to what we might want in certain situations for a client. 

If you have Trimble I would recommend looking at TBC as it makes a great way to adjust networks with any type of sensor you use while running access. RTK terrestrial levels scanner drones etc. It is an easy learning curve if coming from StarNet and I have seen comparisons of the same raw data run in both and so I am confident in my results. 

Try this link

https://helpdesk.microsurvey.com/en-us/article/1550-export-star-net-data-directly-from-trimble-controller-using-a-stylesheet

Hi,

If you can export a tdef format file from TBC there are two options that will write the input you require:

Current STAR*NET has a TDEF converter that always writes input as M lines.

The online tool linked to below reads a TDEF file and allows creating input as either M lines or Direction sets.

https://support.microsurvey.com/convert/tdef2sn.html

@jimcox be aware on the Rw5 exporter. Nothing wrong with it at all. However say you are set up using state plane in the data collector for terrestrial data.  When you export via the rw5. It exports original raw angles so you are basically back to ground. I also did some checks not enough to confirm yet because I use TBC for least squares adjustments. But I was checking to see if what came out in rw5 had actually accounted for C/R and Temp and Pressure as this is being done in access .  Also ZA correction. I was not able to fully inspect this as it was not a priority but I would do some checks so you don’t double correct or not correct thinking access did it.  My gut sais based on some of what I dove into was it was as measured no corrections but have not confirm this.