Leica Contacts - Eric Trehn

ConX REST API docs leica_conx_one_api-1.pdf

VC++ REST Libraries https://github.com/Microsoft/cpprestsdk

We currently have an export specifically for Leica Machine control which is a DXF file with certain trimesh parameters. This story simply expands this export using the same pattern we use for AGTEK Access.

The steps are:

• Open the desired AGTEK model file in Sitework/Gradework.
• Select Export - Leica iCON (.dxf)

* A save dialog for naming appears and then the export screen shown below. It is very similar to existing AGTEK DWG/DXF/KMZ/ADF interfaces. It differs slightly in contents and options and this Leica export is one specified by Leica as optimal for their machine control.

The new option here is the Upload to ConX in the lower right corner which is similar in function to our Upload to Access.

• With Upload to ConX set to Yes the unique part of the interface appears. With ConX the user has to:
  • login/authenticate . The image matches the naming conventions of Conx ie Username. We have to display this everytime for changing but can store the remembered value if the user chooses to.(can we cache the tokens/values? Are we doing a third party integration?)
  • 
  • Select the project (GET /api/one/v1/builders/{company uuid}/projects/?recursive=1) This is derivative from our existing project selection. It looks like creation of new projects is also API supported.

• Choose the unit and/or machine type. For example you might send a machine file to all the excavators or just a single named dozer. (A tree control with checkboxes organized by type then individual units might be an appropriate method.
• Press Upload and Assign to start the uploading.

9-27-18 Apparently the New Project functionality was never implemented in the API. Leave the New project button out on the select Project Dialog for now. If they choose to implement it (I gave them use cases) we can add it back in to match the Access upload

FYI, when uploading manually from the ConX website they specify the data type and unit type (dozer, blade, field - survey). For our purposes uploading a DXF file we're likely safe specifying “Reference model” (I will confirm).

There's also a specification by machine type but that might be better represented by the tree referenced above.

After meetings with the ConX guys it's apparent they're also going to want our KMZ outputs although they need to extend their KMZ reader to handle image overlays and the CData property sheet info. Besides adding ConX as an option the only to the data flow may be to ask the user to designate what they want to use it for (Background image, etc.) While ConX attempts to identify the data type coming into the system there are cases where the user supplying the data needs to designate it. That is not clear now and before we implement any interface to support it, we will need to be supplied the logical types.

Kevin Hanson

Processing Drone data for photogrammetry

We have a version of Infinity in the office and it's fairly complex and probably more suitable for a surveyor at this point. Sort of a huge Swiss army knife that spans all of their sensors. Initial impressions it that the default values do excessive vertical filtering and we'll need to figure out which adjustment of many can be used to adjust it.

I have no doubt this software does everything correctly but it is challenging. Too much so for the average US construction customer.

API's for a roll your own construction version due beginning of 2019. 9-27-18 This turns out to be more about them creating a web interface for this functionality. I offered to look at early versions for suggestions on simplification. They're aiming this at the UAV market so it should be simpler.

Have SmartGrade save a Leica Localization file. Upload to ConX? probably

Possible rebranding/renaming to Icon Office mobile for Leica customers?

The M20 job has both AGTEK trackers and the ConX Earthmover Ipad on CAT801 for 10-12-2018. The Track under “Track - Location History” looks like a series of points representing a track. There was some question of whether we could read these as tracks. The more that I look at the data compared to the same track we captured I realize that the lines are probably just a vector between the pickup and dump points. If I try to pick any of those points on the screen it looks like it actually goes to the single points at the end of the lines. Frankly I'd represent them as an icon with matching numbers for load and dump because the vectors add to the busyness.

ConX currently has limited support for KMZ. They don't support the image overlay object which precludes them from displaying plan sheets or cut/fill colors. Their intention is to do so since they already support KMZ linework, placemarks(?) and closed polygons. It doesn't appear that they support any html view of the property sheets either.

The interface challenge for export is that the KMZ export already has an export to Access option and our