This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
windows:earthwork4dversions:earthwork_4d_update_fall_2018_desktop [2018/10/29 22:49] mikeclapp created |
windows:earthwork4dversions:earthwork_4d_update_fall_2018_desktop [2018/11/09 18:32] (current) mikeclapp [Drone Processing Guide] |
||
---|---|---|---|
Line 10: | Line 10: | ||
* Finish State Plane question for .LAS files (Gradework only) | * Finish State Plane question for .LAS files (Gradework only) | ||
* Template Scale fix? (Ted?) | * Template Scale fix? (Ted?) | ||
+ | * Include George's update to support use of .jpgw files (Gradework only) | ||
==== Template Window Bug ==== | ==== Template Window Bug ==== | ||
+ | It appears this is fixed as of now (10/29/2018) | ||
==== Vector PDF Guide ==== | ==== Vector PDF Guide ==== | ||
Line 20: | Line 21: | ||
- | ==== Template Scale ==== | + | Note: this copied from here: [[http://dev.agtek.com/dokuwiki/doku.php?id=agtek_-_leica_synergy_notes|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) | ||
+ | |||
+ | {{::leicamc_export.png?600|}} | ||
+ | |||
+ | * 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. | ||
+ | |||
+ | {{::conxexportsave.png?400|}} | ||
+ | |||
+ | {{::conxexportscreen.png?600|}} | ||
+ | |||
+ | 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?) | ||
+ | * {{::loginscreen.jpg?400|}} | ||
+ | * 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. | ||
+ | | ||
+ | {{::conxexportprojectselect.png?400|}} | ||
+ | |||
+ | * 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 ** | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | === 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. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | |||
+ | |||
+ | {{::screenshot_2018-06-05_12.35.58.png?600|}} | ||
+ | |||
+ | {{:screenshot_2018-06-05_12.36.14.png?600|}} | ||
+ | |||
+ | {{:Screenshot 2018-06-05 12.37.13.png?600|}} | ||
+ | ==== Template Scale ==== | ||
+ | |||
+ | Ted, please elaborate to see if this is something that's going to make it in. | ||
===== Gradework only features ===== | ===== Gradework only features ===== | ||
Line 28: | Line 80: | ||
* Add new guide for Drone file processing (menu Name?) | * Add new guide for Drone file processing (menu Name?) | ||
* Finish State Plane question for .LAS files (Gradework only) | * Finish State Plane question for .LAS files (Gradework only) | ||
+ | * Add in George's changes to use .jpgw files as orthomosaic background files | ||
==== Drone Processing Guide ==== | ==== Drone Processing Guide ==== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | |||
+ | - Import Orthomosaic Image | ||
+ | * Bring up the Import dialog | ||
+ | - Create New Surface | ||
+ | * Bring up Create New Surface dialog | ||
+ | - Enter Perimeter | ||
+ | * Put user in new surface, layer Perimeter, Entry mode | ||
+ | - Import Point Cloud | ||
+ | * Bring up Import dialog | ||
+ | - Transfer Points | ||
+ | * Transfer point cloud to new surface, layer data lines, edit mode | ||
+ | - Remove Points Outside Perimeter | ||
+ | * Put user in new surface, layer perimeters, Edit mode with all perimeters highlighted | ||
+ | - Remove Obstructions | ||
+ | * Put user in new surface, layer data lines, edit mode | ||
+ | - Review Graphics | ||
+ | * Go to 3D View, make new surface Ref: | ||
+ | - Contour Surface | ||
+ | * New surface, layer data lines, edit mode and bring up Edit Contour Interval dialog Utility>Contour Surface | ||
+ | - Copy Contours | ||
+ | * Copy contours from contour layer and paste into new surface, layer data lines, Edit mode. Delete contours from contour layer. | ||
+ | - Point Grid – Delete/Annotate | ||
+ | * New surface, layer data lines, edit mode, select point grid if possible. | ||
+ | - Stage Surface | ||
+ | * Put user in 3D View with Ref being new surface, bring up Stage Surface dialog (Utility>Stage Reference) with Ref being new surface and Diff ????? probably whatever is set as Diff or Stripped. | ||
+ | - Calculate Volumes | ||
+ | * Go to 3D View | ||
+ | |||
==== Move to State Plane Question for .LAS ==== | ==== Move to State Plane Question for .LAS ==== | ||
+ | |||
+ | |||
+ | ==== Integrate support of .jpgw files ==== | ||
+ | |||
+ | .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: |