Whats a .Jxl file

The JXL contains the job and point information, as well as observation statistics, corresponding to the raw data gathered by the receiver(s). The raw data files contain satellite timing and ranging information as well as some marker flags for the stop-and-go or kinematic portions, but needs the JXL to essentially translate it into observations after baseline processing.

For RTK data the .jxl contains the vectors (base to rover measurements) as resolved at the data collector (for total station measurements it contains the measure angle and distance data).?ÿ If what you are hoping to do is re-resolve the observation data to vectors you will need the appropriate TBC module. Even with that, and only the observation data (the .T02 files), you aren't going to see vectors until you have resolved them.?ÿ?ÿ

My experience with TBC specifically is limited and now 5 yrs in the past (I have more experience with TBC's predecessor TGO and with LGO and it's predecessor, Leica SKI - plus a little touching base with Topcon Tools). So I can't advise you in detail. But that is the general work flow of all these programs.?ÿ ?ÿ

I guess that when You first import. The jxl, all associated files will be imported automaticaly (if of course present on the same location)

chr.

@christ-lambrecht

That is correct - the JXL references the raw data files, and if imported using the Import function in TBC, the raw files will come in at the same time.

It is possible to process stop-and-go (PPK) raw data files without the JXL, but it will be missing job information, i.e. point numbers, descriptors, FXL, etc. It will also make it slightly more difficult to analyze and clean up the data.

PPK is under-utilitized in my opinion; when conditions are right it is a great tool to have in the arsenal. Although it is becoming more common as more UAS platforms make use of it...

Oh my god youre right, such a beautiful comment. And here i was everytime importing first the statics then the jxl, when all i needed to do, was just import the jxl. You can never get enough helpful information in this forum!

@rover83

PPK seems to be the GPS technique that gets short shift, I don't know why, many users that I've dealt with are scared of it. PPK and Xfill are powerful uses that have saved so much time over the years I've surveyed with GPS, not sure why they aren't used more. Also PPK is great if only to use as checks, and it offers far more opportunities for adjustments.

@mightymoe

We have good RTK-VRS in Belgium, so I did not dive into PPK (yet)

What is your typical PPK-occupation time for points shots with open skies. 

Christof.

Bumping an old thread again but being a new-ish Trimble user I had hopefully a pretty basic question.?ÿ Does this .jxl file contain the calibration information??ÿ So if I create a project/job in a new controller and import the .jxl for that project I can roll out there and get working??ÿ Or do I need other stuff too?

@bstrand

Yes, JXL files do contain coordinate system information, including calibration parameters.

YMMV, but for us the smoothest workflow has been to export a JXL from TBC with all the control points, and name it with the project number and "template" tag. Crews can start a new job from that JXL and have the coordinate system + control embedded already, then link to any additional DXF/CSV/RXL files that they need to see.

@rover83

Is there a good reason to import .jxl rather than the .job file?

?ÿ

I always use the .job file.

@bobwesterman?ÿ

Primary difference is format - JOB files are binary, JXL files are XML. JXL files can be read by text editors or reporting.

JOB files are more compact, and so were the standard back when data collectors had minimal processing power and storage space. The downside is that they cannot be read with a text editor, and are more version-dependent than JXLs. TBC actually converts JOBs to JXLs during import.

Functionally speaking, though, there's no difference in the actual data stored. Trimble always has the job file conversion utility if you need to change things. JXLs just tend to be more friendly to different versions of Access and are more easily viewed in text format.

@bobwesterman?ÿ

as Rover said, usually not, but may depend on your workflow.

For our F2F we heavily rely on the use of Notes. Ctrl-N and always a fresh blank line available, even wirth Ctrl-c & -v support. However notes are not attached to points in TBC and can not be exported along with the points.

We export jxl from dc, read that file and convert notes to descriptions, after importing in TBC they are attached to the points and can be viewed/edited and exported as we need. Would not be possible without jxl.

the jxl is a very good source to check and follow step by step what happened in the field (see the fieldbook section) and in the reductions section you find your best co??rdinates for the points, also for points with multiple shots. Stake-out points and lines have also their deltas stored, just as you can review on the dc.

Chr.

Posted by: @christ-lambrecht

↑

@bobwesterman?ÿ

as Rover said, usually not, but may depend on your workflow.

For our F2F we heavily rely on the use of Notes. Ctrl-N and always a fresh blank line available, even wirth Ctrl-c & -v support. However notes are not attached to points in TBC and can not be exported along with the points.

We export jxl from dc, read that file and convert notes to descriptions, after importing in TBC they are attached to the points and can be viewed/edited and exported as we need. Would not be possible without jxl.

the jxl is a very good source to check and follow step by step what happened in the field (see the fieldbook section) and in the reductions section you find your best co??rdinates for the points, also for points with multiple shots. Stake-out points and lines have also their deltas stored, just as you can review on the dc.

Chr.

I saw this reply the first time around, but somehow got sidetracked and forgot about it. How exactly do you convert the notes to descriptions? That could be very useful.  Right now rhe only way I can put the notes with the points is in a csv file from the Job Report Generator.

I wrote a piece of software to read and modify jxl files.
Read a note and insert it as a description with the preceeding point.

So while coding we insert the note AFTER the point and all our notes starts with a dot .

There are a lot of Trimble notes in the jxl.

You can then import your modified jxl in TBC where the entered notes come in as Descriptions

Not sure if that could work for, depending on your gear that jxl may have different sections.
Worked for us for our S6 and RTK GNNS R4 an R6.