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.
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:
* 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.
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.
The Drone processing guide shouldn't be regarded as the absolute order that things should be done in because there's several ways to do it. What it does provide is the list of steps which is something that students in classes have struggled to remember. It also provides shortcuts like the copying of contours that involve multiple steps and combines them into one.
.jpgw files are jpegs that include a separate transformation file of the same name. George has done work to read them and apply the transformation similar to GeoTiffs.
More info and samples here: