KMZ export is a form of portable reporting utilizing AGTEK Data in a Google Earth compatible file. The contents will vary based on the exporting program and user choices.

We currently support KMZ export in Sitework 4D, Trackwork, and GradeModel. In the February release we will expand that to include Earthwork 3D/Highway but only at a basic level. The two levels are:

Basic Google Earth is for Earthwork 3D/Highway/SiteModel (not siteplan, it contains no benchmarks). The best description would be GE prior to the latest changes made in 1.06. It should not support Regions, Sections, Reporting, plan sheets, etc.

Advanced features expand the use of GE as a reporting tool. Some examples of the output are:

Sitework 4D https://agtek.s3.amazonaws.com/Agtek/SlzZ6HnKeMKm

Haul planning from 4D (adding to KMZ files)https://agtek.s3.amazonaws.com/Agtek/iojrut0mDu2R

Materials 4Dhttps://agtek.s3.amazonaws.com/Agtek/mF9iH1As0i4u

Trackwork

• Folders to organize the more interesting data. Stripping, Report Regions, Sectional Areas, Cut-Fill, and Plansheet graphics all have individual folders. This make it easier to control what is visible and also make picking of individual items work a lot better. It’s especially important to have the cut/fill and plan sheet image overlays in there because they will cause picking problems.
• PDF/Bitmaps are exported as images and aligned using the groundoverlay kmz feature.
• A key addition to making ground overlay work right is to set the draw order for Cut/Fill color to –2 and the plansheet as –3. This will put the cut-fill on top of the plansheets.
• Use the Region setting (example towards the top of the file, search for Region) that automatically suppresses placemark objects like Benchmarks from displaying until the job goes over a certain size on the screen. Because placemarks are size independent of zoom, they otherwise appear when zoomed all the way out. It’s distracting but somewhat livable with Benchmarks only but becomes very distracting when we start to get into Materials and underground data. We might as well get it right now.
• The KMZ file doesn’t have everything turned on when exported. The state that I’ve sent the file in is my best guess for the default state it comes up in. The Materials file will be different in its default views.
• Adding to KMZ files instead of just writing them as new.

• Added Cut-Fill Legend imageoverlay to a Cut-Fill folder which also contains the cut-fill groundoverlay.
• Sectional Areas and Report Region lines are written out as separate polygons with html descriptions and colors. The html descriptions are derived from the esw file and include areas and volumes. The colors ideally would match the hatching pattern that Sitework uses but if they are random, the KMZ file could be random as well. Sections or report regions of the same name should have the same colors though for consistency.

• Tracks contain description from Trackwork Analysis bar on volumes, avg load, cycles, avg length, avg move time, stops, cycle time, total travel, avg. move speed, cycle hours, minutes per hour, cost hours.
• Haul info like that from sitework but with the addition of actual numbers to the template containing the planned numbers.