Differences

This shows you the differences between two versions of the page.

--- standards:sitework_surfaces_and_layer_definitions [2011/10/11 00:31]
mikeclapp [Current, Previous, and User named Surfaces]
+++ standards:sitework_surfaces_and_layer_definitions [2012/10/10 16:01] (current)
@@ Line 43: / Line 43: @@
-=== Layers in surfaces ===
+===== Layers in surfaces =====
@@ Line 78: / Line 78: @@
-=== Layer Definitions ===
+==== Layer Definitions ====
-	* Data lines - the lines and points that form the respective surfaces. The most important data in any file
+	* **Data lines** - the lines and points that form the respective surfaces. The most important data in any file
-	* Annotation - Annotation is lines and point that do not modify their respective surface. At the most basic level they simple serve as a 2D guide. The most common usage is as something to be assigned an elevation and then be converted to a data line.
+	* **Annotation** - Annotation is lines and point that do not modify their respective surface. At the most basic level they simple serve as a 2D guide. The most common usage is as something to be assigned an elevation and then be converted to a data line.
-	* Perimeters - Perimeters control the surface and volume calculations.
+	* **Perimeters** - Perimeters control the surface and volume calculations.
+           * **Existing Perimeters** are closed 2D polygons that limit ALL surface generation outside of its limits. In the case of an existing perimeter within another, the innermost perimeter is a hole in ALL surfaces. Two existing perimeters that are not overlapping are considered an Island situation. Both perimeters calculate surfaces within them.
+           * **Design Perimeters** denote limits of excavation and are closed 2D polygons. They limit surface generation for Design and Subgrade surfaces to the area within their limits. At their most common, the process of creating a Design perimeter prompts the user on whether to create a matching 3D drape line in the Data lines layer. This drape line has its elevations derived from the Existing Surface and effectively makes the Design surface match the Existing surface at the perimeter boundary. This is commonly called  "daylight".  A Design Perimeter within a Design Perimeter creates a hole in the Design Surface (the existing surface is visible through this hole) and is also usually daylighted. Two Design perimeters that do not overlap create an Island situation. In this case, two separate design meshes are created within the perimeters with no surface existing outside of the perimeters.
-		* Existing Perimeters are closed 2D polygons that limits ALL surface generation outside of its limits. In the case of an existing perimeter within another, the innermost perimeter is a hole in ALL surfaces. Two existing perimeters that are not overlapping are considered an Island situation. Both perimeters calculate surfaces within them.
+	* **Stripping Areas** - Stripping Areas are closed polygons with no elevation but a uniform depth and name assigned. The Existing ground data lines are depressed within the bounds of a Stripping area and the result is the Stripped surface. Stripping areas are exclusive in their depth and are not additive. A stripping area within another stripping area with a depth of 0 results in a hole in the larger stripping area.
-		* Design Perimeters denote limits of excavation and are closed 2D polygons. They limit surface generation for Design and Subgrade surfaces to the area within their limits. At their most common, the process of creating a Design perimeter prompts the user on whether to create a matching 3D drape line in the Data lines layer. This drape line has its elevations derived from the Existing Surface and effectively makes the Design surface match the Existing surface at the perimeter boundary. This is commonly called  "daylight".  A Design Perimeter within a Design Perimeter creates a hole in the Design Surface (the existing surface is visible through this hole) and is also usually daylighted. Two Design perimeters that do not overlap create an Island situation. In this case, two separate design meshes are created within the perimeters with no surface existing outside of the perimeters.
+	* **Benchmarks** -
+	* **Strata Bore Holes**
+	* **Strata Break Lines**
+	* **Profile Lines**
+	* **Contours** - The contours layer is primarily for contours generated by AGTEK software. They have no effect upon surface generation and serve mostly as an easily understood 2d representation of a 3D surface. They can be copied and pasted into a data lines layer if the user wishes to use them for surface generation.
+	* **Cut-Fill Labels** - User generated points that display on the cut-fill map and printouts.
+	* **Cut-Fill Lines** - reference lines created when
+	* **Haul Paths**
+	* **Pipelines** -
+	* **Report Regions** - Report Regions are enclosed 2D polygons used to segment site volumes for reporting.
+	* **Sectional Areas**
+	* **Balance Regions**
+	* **Stake Point Lists** - Individual, user entered points for use in surveying.
+	* **Driving Simulation** - A user drawn 2D line that serves as a playback path in the 3D view driving simulator.
+	* **Highway Data** - lines created by the Highway module such as COGO.
+	* **Stage Areas** -
+	* **Survey Data**
-	* Stripping Areas
-	* Benchmarks
+====== Application Specific Notes ======
-	* Strata Bore Holes
-	* Strata Break Lines
-	* Profile Lines
-	* Contours - The contours layer is primarily for contours generated by AGTEK software.
+===== SmartDirt =====
-	* Cut-Fill Labels
-	* Cut-Fill Lines
+SmartDirt really only cares about data lines and the perimeters that clip them. A minor exception would be the benchmarks used to calculate alignment. The remaining layers do not have any calculations applied to them and are either displayed for reference or not at all.
-	* Haul Paths
-	* Pipelines
+At this time, SmartDirt does not save any data. In the future, there may be a need to save isopach's and/or tracks with time stamps. Tracks with times stamps could probably be stored in Survey Data and displayed. Setting the elevation of such tracks to 0 would automatically cause them to be properly treated in the desktop software.
-	* Report Regions
-	* Sectional Areas
+==== Layer Usage ====
-	* Balance Regions
-	* Stake Point Lists
+M = Mesh
-	* Driving Simulation
+D = Display
-	* Highway Data
+C = Clip
-	* Stage Areas
-	* Survey Data
+^ Layers   ^    Usage ^
+^Data Lines  |  M,D  |
+^Annotation |  D  |
+^Perimeters (1) |  C,D  |
+^Stripping Areas|  D  |
+^Benchmarks (2)|  D  |
+^Strata Bore Holes |    |
+^Strata Break Lines |    |
+^Profile Lines |    |
+^Contours |    |
+^Cut-Fill Labels |    |
+^Cut-Fill Lines |  D  |
+^Haul Path |  D  |
+^Pipe Lines |  D  |
+^Report Regions |  D   |
+^Sectional Areas |  D  |
+^Balance Regions |  D  |
+^Stake Point Lists |    |
+^Driving Simulation |    |
+^Highway Data |  D  |
+^Stage Areas |  D  |
+^Survey Data |    |
+* User named surfaces include Current, Previous, Overex, Sewer, Storm, Water
+(1) Existing Perimeters clip ALL surfaces for meshing, Design Perimeters clip Design, Subgrade, Strata, etc but does not clip Existing or Stripping surfaces.
+(2) Benchmarks are used to calculate alignment.

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools