windows:gradework_release_1.05
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
windows:gradework_release_1.05 [2019/08/06 23:14] mikeclapp [Dynamic Enhancements] |
windows:gradework_release_1.05 [2020/02/14 23:06] (current) mikeclapp |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| * Versioning on images and separation to an images layer that like benchmarks is not bound to a surface | * Versioning on images and separation to an images layer that like benchmarks is not bound to a surface | ||
| + | |||
| + | * Group field on Report regions dialog to allow reports to be organized by something other than the first alpha characters. The chief reason is to allow phase regions from materials to be used by Gradework using volume sorting that makes sense | ||
| * Paint Brush cleanup (Gradework) - the ability to use the paintbrush feature to remove points by painting over them. We may want to dual purpose this to create vector cleanup areas that we save as more permanent cleanup trim areas. | * Paint Brush cleanup (Gradework) - the ability to use the paintbrush feature to remove points by painting over them. We may want to dual purpose this to create vector cleanup areas that we save as more permanent cleanup trim areas. | ||
| Line 22: | Line 24: | ||
| * The ability to use the cut/fill map as a background image | * The ability to use the cut/fill map as a background image | ||
| + | Move imported data to closer question when imported data is over 20,000 feet away from bounding box of existing data. | ||
| Line 35: | Line 38: | ||
| ===== Image View Control ===== | ===== Image View Control ===== | ||
| + | Ideally the image View control is a non-modal so it can be floated on a second window. We need to be able to import and rename the images while retaining the linkage to the original file. We also need to | ||
| + | |||
| + | |||
| + | ? Start using tiling for the image views rather than reading the entire bitmap. Would add flexibility to handling of maps and possibly more than one sheet ast onece | ||
| Line 71: | Line 78: | ||
| + | ===== Report Grouping ===== | ||
| + | |||
| + | Between Materials and Gradework structures and sectional areas are analogous to one another with a control to assign usage between them. The other analog not currently supported is phase regions and report regions. Currently the sorting in Gradework volumen reports depends on the first alpha characters which leads to tortured phase naming in Materials to get subtotal quantities in Gradework. Let's not do that any longer and free the regions. My suggestion is that we add a field to report regions called Group. By default it is empty Group field on Report regions dialog so it operates just like it does now. If the user puts an alphamumeric value in it, it becomes part of a group to be subtotaled on the volume reports. If it comes from a Materials phase region we default it to the name of that phase region. | ||
| + | |||
| + | |||
| + | |||
| + | ===== Saving Transformations ===== | ||
| + | |||
| + | A very common scenario is that projects are in local coordinate systems while the ortho and point clouds are almost always in State Plane (world coordinates). We currently accommodate this by making it easy move both the point cloud and ortho together and this is sufficient for one off situations where we're doing just one flight. | ||
| + | |||
| + | It becomes more problematic and complicated if there are multiple flights. Also problematic is the workflow for processing in much of the photogrammetry software where at best you must do multiple processes to tag CP/GCPs. | ||
| + | |||
| + | |||
| + | We have all the information needed as part of benchmarks. Local Coordinate and lat-long can be used to calculate the state plane value and fill in the transformation. The Pix4D requirements look like these. | ||
windows/gradework_release_1.05.1565133295.txt.gz ยท Last modified: 2019/08/06 23:14 by mikeclapp
Page Tools
