This is an old revision of the document!
Table of Contents
These notes are based on meeting with different Leica organizations. Finding areas of technical and sales cooperation where systems and processes can be integrated for a more cohesive story.
ConX - Access
Leica Contacts - Eric Trehn
ConX REST API docs leica_conx_one_api-1.pdf
VC++ REST Libraries https://github.com/Microsoft/cpprestsdk
Levels of Integration
One way data transfer
AGTEK Model to ConX Export Story step 1
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 (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
ConX website upload method
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.
UAV (Infinity Software)
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.
Field Software collaboration
Have SmartGrade save a Leica Localization file. Upload to ConX? probably
Possible rebranding/renaming to Icon Office mobile for Leica customers?
