AGTEK R & D Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Export Revamp 2018 Sitework & Gradework ======

The file types exported has grown over the years and our approach to export is inconsistent and probably not quite right as it is. Many of the exports are done through Save As and it isn't really appropriate. My proposal is this. Remove the following from the Save As dialog and move them to a File-Export submenu. Also remove Export CAD from the File menu and add it to the Export submenu.


===== Export Reorganization Proposal =====


File - Export 

  * AGTEK Mobile *.adf
  * AGTEK Data transfer *.agt
  * AGTEK COGO *.cgo
  * AGTEK RDS *.rds
  * AGTEK ROG *.rog
  * AGTEK RCS *.rcs
  * AutoCad Transfer *.dxf
  * AutoCad Drawing *.dwg
  * Comma Separated Values *.csv
  * LandXML *.xml
  * Leica Icon *.dxf
  * Lidar/Drone data *.las *.xyz
  * KMZ *.kmz  (from Planview)
  * Revit XYZ *.csv
  * Topcon TN3 *.tn3
  * Topcon LN3 *.ln3
  * Trimble TTM *.ttm
  * VRML *.vrml (from Planview)




I've slightly modified the descriptions, placed them in Alpha order (description) and removed the word "Export" from descriptions since it's redundant.


===== New KMZ Export =====

KMZ outputs have expanded and become more important since first implemented. This window was derived off the existing KMZ exporter with two primary changes. The surfaces/layers now have an option to set the visibility of the outputs and the options for exporting images have more control along with visibility controls.

==== Default Settings ====

My inclination is to duplicate what we do now for defaults. What's visible on screen are the settings when the window is opened. With images, the current image is selected but not set to visible.



{{:windows:export:save_file_kmz_export.png?600|}}


Please ignore the the group boxes not extending out, etc. in the drawing. I'm looking for functionality here rather than exactly copying the interface shown here.




===== New ADF Export =====

The ADF export may pre-date the current KMZ window and needs to be updated to reflect the additional surfaces and layer types that have been added. Ideally much of the window would be shared with or derived from the revamped KMZ window since much of it is identical. The chief differences are in the center in choosing surface comparison options. 

This also changes the data flow of choosing to calculate the IsoPach from the Save dialog to the export selection screen as well as moving the Access saving to after the selection to match what we do with KMZ.

{{:windows:export:save_file_adf_export.png?600|}}


===== Add GCP (ground control point) Export options =====


Ground control points are used by photogrammetry software in the process of developing surfaces. AGTEK Benchmarks are a natural way to capture GCPs and the export would simply take all Benchmarks and write them out in the appropriate format for the software. The current known types are:

  * Drone Deploy (csv)
  * Pix 4D (txt or csv)
  * 3D Robotics (txt or csv)
  * PhotoModeler (LLA txt)

I'm purposely leaving off Identified and Kespry because their data flows don't use GCPs normally and Identified uses a very custom excel spreadsheet that would be more difficult to match correctly.


==== Interface Flow ====

Because I think these might expand the Export should just read Export  - Ground Control Points with a popup to choose the selected output. My inclination is to not choose units but instead use the job values but I could be talked into a control specifying feet or meters.


Here's a pass at the dialog but you have leeway on how it's done.

{{:windows:export:gcp_export.png?400|}}


==== The Gory details of File types ====

These are for the most part very similar to one another with slightly different headers or formatting. 

This [[https://agtek.s3.amazonaws.com/Agtek/GvmUwAKTHCC9]] is an example of an ESW files and the corresponding Benchmarks 

=== 3D Robotics ===

Format appears to be id, N, E, Elev, description


Example file from Finn here

[[https://agtek.s3.amazonaws.com/Agtek/QoRG7negGHfp|Finn 3DR GCPs.csv]]

It looks like this and doesn't appear to have any units or epsg code denoted.

<code>
id,y,x,z,desc
1,2060782.351,6208986.530,686.085,2nd post front pasture
2,2060876.751,6209378.817,685.938,back fence middle
3,2060784.468,6209349.729,686.458,back corner pasture
4,2060758.539,6209105.127,687.446,drive edge gcp
5,2060990.909,6209069.614,683.929,garden spigot
6,2060976.870,6208603.695,682.760,oak knoll
7,2061015.191,6208258.803,662.535,front n wood post
8,2060830.730,6208451.338,667.460,center high front s pasture
</code>


=== DroneDeploy ===

Format appears to be GCP label, N, E, Elevation with the units in the header as (ft) or (m)


Example file from Finn here

[[https://agtek.s3.amazonaws.com/Agtek/V6Ld5Q2r0urS|Finn DD GCP.csv]]


<code>
GCP Label,Northing,Easting,Elevation (ft)
1,2060782.351,6208986.530,686.085
2,2060876.751,6209378.817,685.938
3,2060784.468,6209349.729,686.458
4,2060758.539,6209105.127,687.446
5,2060990.909,6209069.614,683.929
6,2060976.870,6208603.695,682.760
7,2061015.191,6208258.803,662.535
8,2060830.730,6208451.338,667.460
</code>





=== PhotoModeler ===
Photomodeler appears like it's going to be the most difficult because LL is neither required or necessarily accurate depending on the source. They appear to use Lat, Long instead of NE specified in decimal degrees and the default delimiter is a space. We'll need to error check that we actually have LL on the benchmarks before allowing export but it does nothing to ensure they are correct. We could take it a step further and calculate LL on those BM based on what we know but I'm hesitant to do so.


[[https://agtek.s3.amazonaws.com/Agtek/FxhV7Z9V1PUY|Finn PM GCP.csv]]


<code>
37.6482 -121.71821 686.085
37.64847 -121.71686 685.938
37.64822 -121.71696 686.458
37.64814 -121.7178 687.446
37.64878 -121.71793 683.929
37.64872 -121.71954 682.760
37.64881 -121.72073 662.535
37.64831 -121.72006 667.460
</code>



=== Pix 4D ===

Pix 4D can read files as x,y,z or y,x,z but the former is the default and what I'd suggest we write. 

Format appears to be Easting, Northing, Elevation with no header or units


Example file from Finn here

[[https://agtek.s3.amazonaws.com/Agtek/LXAT8mIKeSdF|Finn pix GCP.csv]]


<code>
label1, 6208986.530,2060782.351,686.085
label2,6209378.817,2060876.751,685.938
label3,6209349.729,2060784.468,686.458
label4,6209105.127,2060758.539,687.446
label5,6209069.614,2060990.909,683.929
label6,6208603.695,2060976.870,682.760
label7,6208258.803,2061015.191,662.535
label8,6208451.338,2060830.730,667.460
</code>

In the event there is no label, start numbering as the label
AGTEK R & D Wiki

User Tools

Site Tools

Page Tools
