This is intended as a small update to Gradework/Earthwork 4D. There's quite a bit of overlap where the functionality occurs in both programs but a few items that are unique to Gradework.

• Fix Template window button bug (Already started)
• Add two new Guides for Vector PDF and (Gradework only) Drone file processing
• Add ConX upload support for Leica Export Model (pattern for KMZ too?)
• Finish State Plane question for .LAS files (Gradework only)
• Template Scale fix? (Ted?)

It appears this is fixed as of now (10/29/2018)

Note: this copied from here: AGTEK-Leica Synergy Notes

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 10-29-2018 ConX is currently limited in file upload size to 512mb. We've mentioned to them that this will be problematic to their Leica Infinity interface but it probably doesn't affect us

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.

Ted, please elaborate to see if this is something that's going to make it in.

• Add new guide for Drone file processing (menu Name?)
• Finish State Plane question for .LAS files (Gradework only)