Notifications
Clear all

Leica files in Trimble Business Centre

12 Posts
7 Users
6 Likes
750 Views
Geomágico
(@geomagico)
Posts: 22
Member Member
Topic starter
 

Hello all, our firm uses Trimble equipment so all the data is processed in TBC. We started working with a sub-contractor that uses Leica and we would like to process his data in TBC. I was able to find online a specific stylesheet where I am able to export a JXL file that is readable in TBC. However, the GNSS RTN vectors do not show up, only the coordinates of the points that were measured with GNSS. 

1) Is the JXL file supposed to show the 3D vectors?

2) If the JXL file does not read the vectors, how can I import this data in TBC?

Appreciate any input on this.

 
Posted : February 3, 2022 7:01 am
Alan Chyko
(@alan-chyko)
Posts: 153
Member Member
 

Have you confirmed with them that they are storing the vectors?  I know Access has the option to store either the vectors or just the points, so I would assume that Leica's software may have the same option.  

 
Posted : February 3, 2022 7:15 am
Geomágico
(@geomagico)
Posts: 22
Member Member
Topic starter
 

@alan-chyko He ran the DBX file in Leica Infinity and said he can read the vectors in this program.

 
Posted : February 3, 2022 7:20 am

Get the 2023 SurveyorConnect Wall Calendar

Squirltech
(@squirl)
Posts: 1068
Member Member
 
Posted by: @alan-chyko

Have you confirmed with them that they are storing the vectors?  I know Access has the option to store either the vectors or just the points, so I would assume that Leica's software may have the same option.  

Exactly what I was thinking too. There's a check box in Access, within the survey style, that allows for vectors to be stored. I'm not 100% sure but I think Leica has this same kind of option.

Also, I think they can select this option, then re-export the file and the vectors will show. If I'm not mistaken, the vectors are there, they're just not being exported/visible. I could be way off here but this sounds familiar. I haven't personally had this issue for a really long time so I may not be remembering it quite right.

 
Posted : February 3, 2022 7:23 am
Alan Chyko
(@alan-chyko)
Posts: 153
Member Member
 

Have you opened the file in Notepad or something similar to see if the vector data is in there?  I assume it is since it imports vectors into Infinity.  I have never tried importing a JXL with vector data, so there could also be an import setting that needs to be fixed.

This will add another step, but you could also try using ASCII File Generator to convert that JXL into Trimble Data Exchange Format.  I have used that to export vector data from one TBC project and import it into another.

 
Posted : February 3, 2022 7:51 am
Geomágico
(@geomagico)
Posts: 22
Member Member
Topic starter
 

@alan-chyko the following shows up:

<?xml version="1.0" encoding="utf-8"?>
<JOBFile jobName="21709-INT-JAN-18" version="5.66" product="" productVersion="3.71" productDBVersion="3.71" TimeStamp="2022-02-01T08:00:37" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Environment>

<DisplaySettings>
<DistanceUnits>Metres</DistanceUnits>
<HeightUnits>Metres</HeightUnits>
<AngleUnits>DMSDegrees</AngleUnits>
<AzimuthFormat>Azimuth</AzimuthFormat>
<LatitudeLongitudeUnits>DMSDegrees</LatitudeLongitudeUnits>
<CoordinateOrder>East-North-Elevation</CoordinateOrder>
<TemperatureUnits>Celsius</TemperatureUnits>
<PressureUnits>MilliBar</PressureUnits>
<GradeUnits />
<AreaUnits>SquareMetres</AreaUnits>
<VolumeUnits>CubicMetres</VolumeUnits>
<StationingFormat />
<StationIndexIncrement />
</DisplaySettings>

<CoordinateSystem>
<SystemName>UTM 17N N83HT2</SystemName>
<ZoneName>17 north</ZoneName>
<DatumName>UTM17N</DatumName>
<Ellipsoid>
<EarthRadius>6378137.000000</EarthRadius>
<Flattening>0.003353</Flattening>
</Ellipsoid>
<Projection>
<Type>UniversalTransverseMercator</Type>
<ShiftGridFileName />
<CentralLatitude>0</CentralLatitude>
<CentralLongitude>81</CentralLongitude>
<FalseNorthing>0</FalseNorthing>
<FalseEasting>500000</FalseEasting>
<Scale>0.9996</Scale>
<SouthAzimuth>false</SouthAzimuth>
<GridOrientation>IncreasingNorthEast</GridOrientation>
<ApplySeaLevelCorrection>true</ApplySeaLevelCorrection>
</Projection>
<Datum>
<Type>NoDatum</Type>
</Datum>
<HorizontalAdjustment>
<Type>NoAdjustment</Type>
</HorizontalAdjustment>
<VerticalAdjustment>
<Type>NoAdjustment</Type>
</VerticalAdjustment>
</CoordinateSystem>

<TimeZone>
<ZoneName />
<HoursToUTC>4</HoursToUTC>
</TimeZone>
</Environment>

<FieldBook>

<UnitsRecord ID="00000000000000002" TimeStamp="2022-01-18T13:21:47">
<DistanceUnits>Metres</DistanceUnits>
<HeightUnits>Metres</HeightUnits>
<AngleUnits>DMSDegrees</AngleUnits>
<AzimuthFormat>Azimuth</AzimuthFormat>
<LatitudeLongitudeUnits>DMSDegrees</LatitudeLongitudeUnits>
<CoordinateOrder>East-North-Elevation</CoordinateOrder>
<TemperatureUnits>Celsius</TemperatureUnits>
<PressureUnits>MilliBar</PressureUnits>
<GradeUnits />
<AreaUnits>SquareMetres</AreaUnits>
<VolumeUnits>CubicMetres</VolumeUnits>
<StationingFormat />
<StationIndexIncrement />
</UnitsRecord>

<JobPropertiesRecord ID="00000000000000003" TimeStamp="2022-01-18T13:21:47">
<Reference />
<Description>638 N. LAKE RD.</Description>
<Operator>GB</Operator>
<JobNote />
</JobPropertiesRecord>

<FeatureCodingRecord ID="00000000000000004" TimeStamp="2022-01-18T13:21:47">
<LibraryName>ES CODE LIST</LibraryName>
<SourceFilename>ES CODE LIST.fxl</SourceFilename>
<AttributeCheckSum>0</AttributeCheckSum>
<AttributesStored>true</AttributesStored>
</FeatureCodingRecord>
</FieldBook>

<Reductions>

<Point>
<ID>RTCM-Ref 3744</ID>
<Name>RTCM-Ref 3744</Name>
<Code></Code>
<SurveyMethod>NetworkRTK</SurveyMethod>
<Classification>Normal</Classification>

<WGS84>
<Latitude>44.039118111165490</Latitude>
<Longitude>-79.455027760950430</Longitude>
<Height>223.552800</Height>
</WGS84>

<Grid>
<North>4877377.920431</North>
<East>623785.891283</East>
<Elevation>259.736890</Elevation>
</Grid>
</Point>

<Point>
<ID>1001</ID>
<Name>1001</Name>
<Code>FDCM</Code>
<SurveyMethod>NetworkRTK</SurveyMethod>
<Classification>Normal</Classification>

<WGS84>
<Latitude>43.953488197278400</Latitude>
<Longitude>-79.434041296278200</Longitude>
<Height>260.501337</Height>
</WGS84>

<Grid>
<North>4867898.811229</North>
<East>625647.982570</East>
<Elevation>296.715815</Elevation>
</Grid>
</Point>

<Point>
<ID>1003</ID>
<Name>1003</Name>
<Code>FDCM</Code>
<SurveyMethod>NetworkRTK</SurveyMethod>
<Classification>Normal</Classification>

<WGS84>
<Latitude>43.953536500857126</Latitude>
<Longitude>-79.434233992476790</Longitude>
<Height>260.418135</Height>
</WGS84>

<Grid>
<North>4867903.882876</North>
<East>625632.419253</East>
<Elevation>296.632621</Elevation>
</Grid>
</Point>

<Point>
<ID>1203</ID>
<Name>1203</Name>
<Code>SETCM</Code>
<SurveyMethod>NetworkRTK</SurveyMethod>
<Classification>Normal</Classification>

<WGS84>
<Latitude>43.953579236746290</Latitude>
<Longitude>-79.433623338728310</Longitude>
<Height>260.885040</Height>
</WGS84>

<Grid>
<North>4867909.559261</North>
<East>625681.326675</East>
<Elevation>297.099361</Elevation>
</Grid>
</Point>

<Point>
<ID>1201</ID>
<Name>1201</Name>
<Code>SETCM</Code>
<SurveyMethod>NetworkRTK</SurveyMethod>
<Classification>Normal</Classification>

<WGS84>
<Latitude>43.953845835423190</Latitude>
<Longitude>-79.432389532740770</Longitude>
<Height>262.653287</Height>
</WGS84>

<Grid>
<North>4867941.049658</North>
<East>625779.762031</East>
<Elevation>298.867159</Elevation>
</Grid>
</Point>
</Reductions>
</JOBFile>

 

 

The ASCII file option would work, however I am looking to have the observations instead of the point coordinates only.

 
Posted : February 3, 2022 9:47 am

Get the 2023 SurveyorConnect Wall Calendar

(@rkinnie)
Posts: 31
Member Member
 

I think you need them to export into XML and then you would have all the data

Leica stores data as lat/lon and then applies a coordinate system for viewing ( which is what I am guessing you are seeing)

also an export to a rinex file might work too

 
Posted : February 3, 2022 11:47 am
Rover83
(@rover83)
Posts: 1775
Member Member
 

That XML file is missing the observations. Trimble JXL (JobXML) files have a FieldBook section and a Reductions section.

The FieldBook is where all the raw data are stored, so you should see station setups, observations, vector data with covariance info, cogo, etc.

The Reductions section only contains the final values of all the points in the job.

I only see points in Reductions, which means the observations are not being stored (or translated).

 
Posted : February 3, 2022 12:13 pm
Jitterboogie reacted
Alan Chyko
(@alan-chyko)
Posts: 153
Member Member
 

Rover83 is spot on.  You are missing the observation data from that JXL.  Seems like something isn't working out in the conversion from Leica format to JXL.

 

 
Posted : February 3, 2022 2:41 pm

Get the 2023 SurveyorConnect Wall Calendar

Geomágico
(@geomagico)
Posts: 22
Member Member
Topic starter
 

Thank you for looking into this. I contacted Leica and the JXL file provided didn't contain the observations. I got a new JXL file that includes the vector observations.

Appreciate everyone's input.

Cheers!

 
Posted : February 4, 2022 8:14 am
(@tbohan)
Posts: 1
Regular Member Member
 

@geomagico I'm looking to do the same thing, except primarily with TS values. would you mind sharing the JXL file?

 
Posted : January 25, 2023 2:44 pm
jim.cox
(@jimcox)
Posts: 1624
Member Supporter
 

You might like to look into using GNSS vector exchange (GVX) files - they are designed for this sort of thing

 
Posted : January 25, 2023 4:25 pm

Get the 2023 SurveyorConnect Wall Calendar