Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1 User Guide
TM
Page 1 of 158
A-Prime Software, 1600 Broadway, Suite 2400, Denver, Colorado 80202 Copyright 2008 A-Prime Software All rights reserved. Second edition 2008 (Revision 2, addressing ArcGIS Desktop 9.1, 9.2, and 9.3) The information contained in this document is subject to change without notice. A-Prime Software reserves the right to revise and improve its products as it sees fit. This publication describes the state of this product at the time of its publication, and may not reflect the product at all times in the future. The information contained in this document is the exclusive property of A-Prime Software. This work is protected under United States copyright law and the copyright laws of the given countries of origin and applicable international laws, treaties, and/or conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying or recording, or by any information storage or retrieval system, except as expressly permitted in writing by APrime Software. All requests should be sent to Attention: CrossView Product Manager, A-Prime Software, 1600 Broadway, Suite 2400, Denver, Colorado 80202, USA. A-Prime Software makes no warranty, either express or implied, including but not limited to any implied warranties of merchantability or fitness for a particular purpose regarding these materials, and makes such materials available solely on an as-is basis. In no event shall A-Prime Software be liable to anyone for special, collateral, incidental, consequential or any other kind of damages in connection with or arising out of purchase or use of these materials. The sole and exclusive liability of A-Prime Software, regardless of the form of action, shall not exceed the purchase price of the materials described herein. All use, modification, reproduction, release, performance, display or disclosure of the commercial computer software shall be in strict accordance with the End User License Agreement (EULA). Trademarks: A-Prime Software, CrossView, and www.aprimesoftware.com are trademarks, registered trademarks, or service marks of A-Prime Software in the United States, the European Community, or certain other jurisdictions. Such rights are reserved under the laws of the appropriate jurisdiction. Other companies and products mentioned herein are trademarks or registered trademarks of their respective trademark owners. In particular, ESRI, ArcGIS, ArcGIS Desktop, ArcView, ArcInfo, ArcMap, and ArcCatalog are trademarks, registered trademarks, or service marks of ESRI in the United States, the European Community, or certain other jurisdictions. U.S. GOVERNMENT RESTRICTED/LIMITED RIGHTS: Any software, documentation, and/or data delivered hereunder are subject to the terms of the End User License Agreement (EULA). In no event shall the U.S. Government acquire greater than RESTRICTED/LIMITED RIGHTS. The data and technical data is commercial in nature. At a minimum, use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 52.227-14 Alternates I, II, and III (JUN 1987); FAR 52.227-19 (JUN 1987) and/or FAR 12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS 252.227-7015 (NOV 1995) (Technical Data) and/or DFARS 227.7202 (Computer Software) and other related provisions, as applicable. Contractor/Manufacturer is A-Prime Software, 1600 Broadway, Suite 2400, Denver, Colorado 80202, USA.
TM
Page 2 of 158
Table of Contents
Documentation Notes ................................................................................................... 8 Preliminary Overview of CrossView .......................................................................... 9 Required Preliminary Steps ....................................................................................... 12 (1) (2) Select the Line Defining the Course of the Cross Section .................................. 13 The CrossView Dialog Button .......................................................................... 14
TM TM
Visual Overview of the CrossView Dialog Window Layout .................................... 15 (1) (2) (3) Four Main Tabs .................................................................................................. 17 Preview Section.................................................................................................. 20 Options Section .................................................................................................. 22
TM
Using the CrossView Dialog Window ...................................................................... 23 (1) Surfaces Tab and Data Requirements for Surface Datasets.............................. 24 (A) Surfaces to be Represented in Profile ........................................................ 25 (B) Surfaces Tab Options................................................................................. 27 1) Show as a Surface Line...................................................................... 28 2) Split Surface Line Using Polygon Overlay .......................................... 29 3) Show as a Solid.................................................................................. 31 4) Z Factor .............................................................................................. 32 5) Invert Surface ..................................................................................... 33 6) Export Full Polygons........................................................................... 34 (2) Points to Lines Tab and Data Requirements for Point Layers to be Represented as Vertical Lines............................................................................ 37 (A) Points to be Represented as Linear Features ............................................ 40 (B) Line Top ..................................................................................................... 41 1) Top Elevation Field............................................................................. 41 2) Depth to Top Field .............................................................................. 42 (C) Line Bottom ................................................................................................ 43 1) Bottom Elevation Field........................................................................ 44 2) Vertical Thickness Field...................................................................... 45 3) Depth to Bottom Field......................................................................... 45 4) Vertical Thickness Constant ............................................................... 46 (D) Z Factor ...................................................................................................... 47 (E) Search Distance ......................................................................................... 48
TM
Page 3 of 158
(3)
Points to Polygons Tab and Data Requirements for Point Layers to be Represented as Vertically Oriented Polygon Columns..................................... 50 (A) Points to be Represented as Polygonal Features ...................................... 53 (B) Polygon Top ............................................................................................... 54 1) Top Elevation Field............................................................................. 55 2) Depth to Top Field .............................................................................. 56 (C) Polygon Bottom .......................................................................................... 56 1) Bottom Elevation Field........................................................................ 57 2) Depth to Bottom Field......................................................................... 58 3) Vertical Thickness Field...................................................................... 59 4) Vertical Thickness Constant ............................................................... 60 (D) Polygon Width ............................................................................................ 61 1) Use Automated Values....................................................................... 61 2) Directly Enter a Width Value............................................................... 62 (E) Z Factor ...................................................................................................... 62 (F) Search Distance ......................................................................................... 64
(4)
Points to Points Tab and Data Requirements for Point Layers to be Represented as Points at a Specified Elevation or Depth .................................. 66 (A) Points to be Represented as Point Features .............................................. 69 (B) Choose One ............................................................................................... 69 1) Point Elevation Field........................................................................... 70 2) Depth to Point Field ............................................................................ 71 3) Depth to Point Constant ..................................................................... 72 (C) Z Factor ...................................................................................................... 73 (D) Search Distance ......................................................................................... 74
(5)
Preview Section.................................................................................................. 76 (A) Preview Graphic ......................................................................................... 76 (B) Major and Minor Reference Grids............................................................... 77 1) Display Grid on Preview ..................................................................... 77 2) Major and Minor Reference Grid Controls .......................................... 78 3) Major and Minor Grid Output .............................................................. 80
(6)
Options Section .................................................................................................. 81 (A) Vertical Exaggeration ................................................................................. 81 (B) Base Elevation............................................................................................ 84 (C) Show Preview............................................................................................. 86
(7)
Finishing the CrossView Dialog Window ............................................................ 87 (A) Double-Check Selected Inputs ................................................................... 87 (B) What to Expect: An Overview of CrossView Output .................................. 88 1) ESRI Geodatabase Feature Classes or Shapefiles............................ 88 2) The Cross Section Data Frame in the Source ArcMap MXD ........... 88
TM
Page 4 of 158
(C) Finishing ..................................................................................................... 90 1) The Finish Button ............................................................................. 90 2) Choose a Base Filename ................................................................... 90 3) After You Save ................................................................................... 91 Working with the Cross Section Data Frame ........................................................ 92 (1) (2) (3) (4) Initial Adjustment of Elements within the Data Frame ........................................ 93 Update Extents Dialog Window .......................................................................... 95 Data Frame Size and Position ............................................................................ 97 Setting a Specific Cross Section Data Frame Scale........................................... 98 (A) Identify the Horizontal Coordinate System Properties of the Source Planimetric Data Frame from which the Cross Section Data Frame was Generated ....................................................................... 98 1) Activate the Source Planimetric Data Frame...................................... 98 2) Open the Data Frame Properties Coordinate System Tab............... 98 (B) (Optional) Use the CrossView Update Extents Function........................ 100 (C) Define the Projection of the Cross Section Data Frame ........................... 100 1) Activate the Cross Section Data Frame............................................ 100 2) Open the Data Frame Properties Coordinate System Tab............. 101 3) Set the Coordinate System of the Data Frame................................. 101 (D) Set a Fixed Scale for the Cross Section Data Frame ............................... 102 1) Switch to the Data Frame Tab ....................................................... 102 2) Set the Desired Fixed Scale ............................................................. 102 (E) Resize the Cross Section Data Frame ..................................................... 104 Layers Output by CrossView .................................................................................. 105 (1) Feature Classes or Shapefiles Placed in the Cross Section Data Frame ...... 107 (A) (B) (C) (D) (E) (F) (2) <name>_solids (and <name>_solid_#) ................................................... 107 <name>_surface_#................................................................................... 107 <name>_overlaysurface_# ....................................................................... 108 <name>_pointline_# ................................................................................. 108 <name>_pointpoly_# ................................................................................ 109 <name>_pointpoint_#............................................................................... 110
TM
Grid Line Feature Classes or Shapefiles .......................................................... 111 (A) <name>_grid ............................................................................................ 111 (B) <name>_subgrid....................................................................................... 111
TM
Page 5 of 158
(3)
Buffer Polygon Feature Classes or Shapefiles ................................................. 112 (A) <name>_buff_# ........................................................................................ 112 (B) <name>_buff__pointpoly_# ...................................................................... 112 (C) <name>_buff__pointpoint_#..................................................................... 112
Symbolizing Layers in the Cross Section Data Frame ....................................... 114 (1) (2) (3) (4) (5) (6) Symbolizing <name>_solids and <name>_solid_# Polygon Layers ............ 116 Symbolizing <name>_ surface_# Line Layers................................................ 117 Symbolizing <name>_ overlaysurface_# Line Layers .................................... 118 Symbolizing <name>_ pointline_# Line Layers .............................................. 119 Symbolizing <name>_ pointpoly_# Polygon Layers....................................... 120 Symbolizing <name>_ pointpoint_# Point Layers .......................................... 121
Labeling and Annotating Features in the Cross Section Data Frame ............... 122 (1) (2) (3) (4) Activate the Cross Section Data Frame ......................................................... 123 Open the Data Frames Property Dialog General Tab ................................... 123 Set the Map Units ............................................................................................. 124 Labeling and Annotation Example .................................................................... 125
Altering Major and Minor Grids in the Cross Section Data Frame .................... 126 (1) (2) (3) Activate the Cross Section Data Frame ......................................................... 126 Open the Data Frames Property Dialog Grids Tab........................................ 126 View and Edit Grid Properties: The Reference System Properties Dialog........ 128 (A) Custom Overlay Tab................................................................................. 128 (B) Point Axes, Labels, and Lines Tabs ......................................................... 129 (C) Example of Altered Major and Minor Grids............................................... 130 Appendix A: Required and Optional Input Geospatial Datasets .......................... 131 (1) Required Input Datasets................................................................................... 132 (A) GRID and/or TIN surface dataset(s) ......................................................... 132 (B) Line defining the planimetric course of the cross section ......................... 133
TM
Page 6 of 158
(2)
Optional Input Datasets .................................................................................... 134 (A) (B) (C) (D) Point layer(s) to be depicted as vertical lines ........................................... 134 Point layer(s) to be depicted as vertically oriented polygon columns ..... 137 Point(s) to be depicted as point features at an elevation or depth ............ 140 Overlay polygon layer(s) to split and attribute ........................................ 142
TM
TM
Page 7 of 158
Documentation Notes
Throughout this CrossView 1.1 documentation, the terms profile and cross section are used synonymously and interchangeably. While there are subtle differences between these two terms, this documentation, and indeed CrossView itself, addresses them as identical in both concept and overall intent. CrossView is a proprietary trademark of A-Prime Software and the name given to the software discussed in this User Guide. Throughout this User Guide, the term CrossView is used to refer to this trademarked software application name. Questions regarding CrossView , CrossView User Documentation, or any of its contents or described procedures should be directed to: A-Prime Software Customer Support: support@aprimesoftware.com 1-877-MAP-DOWN (1-877-627-3696)
TM TM
TM
Page 8 of 158
TM
Page 9 of 158
(1) Preconditions
CrossView 1.1 creates cross section diagrams using data layers within an active, planimetric ArcMap Data Frame (data view). The source data frame, as well as all its data layers, must use Projected Coordinate Systems (PCS) CrossView cannot accept datasets or data frames that use Geographic Coordinate Systems (GCS). The source data frame must also contain at least one surface dataset. Appropriate surface datasets include: ESRI GRIDs; ESRI TINs; USGS DEMs; or other singleband raster datasets that typically would be used to contain elevation data and are recognized by ArcGIS as single-band image/raster files. Very Important: For a full accounting of preconditions required for CrossView, please review the CrossView Requirements document. For detailed information concerning requirements for surface and other datasets in the source data frame to be represented in output cross section diagrams, please review Appendix A: Required and Optional Input Geospatial Datasets in this User Guide.
TM
Page 10 of 158
What input point features you want to display as either a single vertically oriented polygon column feature or multiple, vertically stacked polygon column features (e.g., soil bore segments). What input point features you want to display as point features at depth on the output diagram (e.g., soil sample locations).
Other diagram controls allow you to specify a vertical exaggeration and base elevation for the output cross section diagram, and configure its reference grid.
Page 11 of 158
TM
Page 12 of 158
CrossView 1.1 creates cross section diagrams using data from within ArcMaps active Data Frame (data view).
TM
(1) Select the Line Defining the Course of the Cross Section
Within the source ArcMap documents data view, you must first select the line element that defines the planimetric course of the cross section you wish to create. This line can be either a graphic drawing element within the data view or a line feature in a geospatial data layer that has been added to the data view (e.g., a geodatabase feature class, a shapefile, or an ArcInfo coverage). Important Note: The planimetric line feature or graphic defining the course of the cross section need not be a simple 2-point line connecting a beginning and ending vertex. The line can be crooked, containing as many intermediate vertices as needed, and can even contain curved segments. Note: To select a graphic line drawing element, use the ArcMap Select Elements tool. To select a line feature within a geospatial data layer, use the ArcMap Select Features tool. CRITICAL: The spatial extent of the line feature or graphic line defining the course of the cross section must lie completely within the bounds of all surface datasets (e.g., GRIDs and/or TINs) to be represented in a CrossView profile diagram. In the screenshot at right, a selected line feature is highlighted in cyan.
TM
Page 13 of 158
The CrossView Dialog window appears on the screen in front of the ArcMap window (see the screenshot example below).
TM
Page 14 of 158
TM
Page 15 of 158
This section of the User Guide simply presents the new user with a visual overview of the CrossView Dialog Windows layout (and its various components). Subsequent sections of this document will provide details regarding each of the CrossView Dialog Windows components, including how to use each, what inputs and choices you have on each, and how each choice affects the resulting output cross section diagram. The screenshot below is an example of the CrossView Dialog window that appears when CrossView first begins.
TM
Page 16 of 158
(1) Four (4) main tabs occupy the large, upper left portion of the dialog window:
Surfaces Points to Lines Points to Polygons Points to Points
The majority of the information you select or enter in the CrossView Dialog window is addressed on these four tabs. Details regarding the use of these tabs are discussed in subsequent sections of this User Guide. These tabs let you tell CrossView: a) What surfaces to display on the output diagram (and how to depict them). b) What input point features you want to display as vertical line segments in the output diagram (e.g., wells, utility poles). c) What input point features you want to display as either a single vertically oriented polygon column feature or multiple, vertically stacked polygon column features (e.g., soil bores). d) What input point features you want to display as point features at depth on the output diagram (e.g., soil sample locations, utility line locations). Note that the Surfaces tab is depicted by default when CrossView begins:
TM
Page 17 of 158
Screenshots of the other three tabs are shown below and on the following pages (the relevant tab areas are outlined in magenta). The Points to Lines tab:
TM
Page 18 of 158
TM
Page 19 of 158
(2) The Preview section on the right side of the CrossView Dialog window:
As you select and enter information on the four tabs (mentioned above), as well as other sections of the Dialog window, the display area in the top-right portion of the Preview section (the large white area on the screenshot above) shows a visual graphic of what the cross section diagram you are developing will look like when output to ArcMap. Note: There are Zoom-In, Zoom-Out, Pan, and View Full Extent tool buttons above the Preview display area that allow you to manipulate your view of cross section elements depicted. While the Previews graphic is not WYSIWYG (what you see is what you get), it provides a very useful visual preview (and approximation) of what you can expect for output. This is particularly true as you become more proficient with CrossView, and come to rely on the Preview graphic as your guide when specifying and/or selecting various elements to add to (or alter on) a diagram. As you move the cursor around on the Previews graphic area, its appropriate coordinate location is shown below the graphic as the Map Location (where X is the linear distance from the beginning of the line defining the planimetric course of the cross section, and Y is elevation). The screen capture on the following page provides an example of the Preview windows display once a number of elements have been selected and configured within CrossView.
TM
Page 20 of 158
Also note that it is at the bottom of the Preview section where you specify whether or not to display a reference grid for the cross section diagram in the Preview section, as well as the distance intervals for both horizontal and vertical grid lines.
TM
Page 21 of 158
(3) The Options section along the bottom left portion of the CrossView Dialog window:
This small, but important, section of the Dialog window allows you to: a) Toggle the display of the Preview section on or off in the CrossView Dialog window via a check box. b) Set a vertical exaggeration for your output cross section diagram. CrossView provides you with several vertical exaggeration values from a pulldown list (None, 0.5, 2, 5, 10, and 20). Alternatively, you can enter your own specific vertical exaggeration value in this field (e.g., 1.5, 3, 7.5, 15, 30, etc.). c) Set a base elevation for your output cross section diagram. This field allows you to control the elevation of the bottom of your cross section diagram.
TM
Page 22 of 158
TM
Page 23 of 158
This section of the User Guide provides details regarding each of the CrossView Dialog Windows components.
TM
Page 24 of 158
TM
diagram, you will have complete control over each surfaces polygon fill symbol. To alter the initial order of surface datasets for display on your cross section diagram, highlight a surface datasets name in the Surfaces to be represented in profile list (by clicking on it in the list) and use the Move Up and Move Down buttons to the right of the list. In the screenshot below, the three surfaces in the Surfaces to be represented in profile list (also depicted in the Preview graphic) are in proper order for display in a cross section diagram (i.e., highest to lowest surface). Specifically, the Topo Elevation (GRID) surface is highest, and it is drawn first in the Preview area (orange-red in this screenshot). The Groundwater (GRID) surface is next highest, and it is depicted on top of the Top Elevation (GRID) in light green in this screenshot. The Bedrock Surface (TIN) surface is lowest in elevation, and it is depicted on top of both the other surfaces (in light orange in this screenshot).
Note that if either of the higher surfaces in the screenshot above are ordered so that they are drawn on top of either of the lower surfaces (i.e., moved down in the list), they would cover up and hide the lower surface(s). The Preview area in the screenshot on the following page illustrates this by showing what happens when the highest surface (Topo Elevation (GRID)) is improperly placed in the list of surfaces for appropriate display on a cross section diagram.
TM
Page 26 of 158
Lastly, note that the Export full polygons check-box can be selected, giving you additional surface polygon display and symbolization options in the final cross section diagram. This output configuration option is described fully in the following section of this User Guide.
Once you have selected a surface, the Options section gives you the following choices for displaying the surface on the cross section diagram to be output by CrossView: Important Note: These options are not mutually exclusive, so you can choose one option, or all options, depending on the graphic output(s) needed for your cross section diagram.
TM
Page 27 of 158
In the illustration below, the Groundwater Table surface dataset is depicted as a horizontally oriented line feature.
TM
Page 28 of 158
TM
Page 29 of 158
In the screenshot below, the user has chosen to depict the Topo Elevation (GRID) surface dataset as a contiguous sequence of horizontally oriented surface lines, created by splitting the larger, single line depicting this surface at polygon boundaries in the Soil Types (shapefile) layer. Each resulting line segment will contain the appropriate soil type attributes from the selected polygon layer.
In the illustration below, the horizontally oriented line representing the top (topographic) surface has been split into a sequence of contiguous line features, each attributed with data taken from a polygonal overlay layer of soil types.
TM
Page 30 of 158
3) Show as Solid
The Show as solid checkbox will output a polygon feature to represent the selected surface. In the screenshot below, the option to depict the Topo Elevation (GRID) surface dataset as a polygon has been chosen, and the Preview graphic gives the user an idea of what this feature will look like in the output cross section diagram.
In the illustration below, the Bedrock and Topographic surface datasets are depicted as polygon features.
TM
Page 31 of 158
4) Z Factor
If the units of measure used for elevation (Z) values in the selected surface dataset differ from the units of measure used for its horizontal (X,Y) coordinates (e.g., elevations are in feet and horizontal coordinates are in meters), then the elevation (Z) values must be converted to the horizontal coordinate systems units of measure. The Z Factor field allows you to direct CrossView to convert the selected surface datasets elevation values to a different unit of measure (e.g., feet to meters). Z-values in the selected surface dataset are multiplied by the Z Factor when calculating output cross section surface elevations. Important Notes: This field defaults to a value of one (1), indicating that a unit of elevation is the same as a horizontal unit of measure (e.g., both are in feet or both are in meters). Unless a Z Factor is specified, CrossView expects the horizontal and vertical units of measure in a surface dataset to be the same. If the horizontal X,Y units and vertical Z units of a surface dataset differ, the Z Factor must be set appropriately, or the resulting cross section will be incorrect. The Z Factor should not be used to convert elevations from one vertical datum to another. It is the users responsibility to ensure that all datasets to be represented in the cross section diagram use the same vertical datum for their elevation measurements. In the screenshot below, the selected surface datasets elevation (Z) units are in feet and its horizontal (X,Y) units are meters. In this case, a Z Factor (0.3048) must be entered to convert Z units from feet to meters (1 foot = 0.3048 meters).
TM
Page 32 of 158
5) Invert Surface
The Invert Surface checkbox option multiplies each elevation of the specified surface by negative one (-1) so that the surface appears inverted on the output cross section diagram. Important Notes: This is a data manipulation intended specifically (solely) for use with surfaces recorded as positive depth values below a set elevation (almost always Mean Sea Level) rather than true elevation values. Surface elevations resulting from this manipulation will be negative (<= 0), and will be interpreted by CrossView as lying below the zero (0) elevation horizon commonly thought of as Mean Sea Level. In the screenshot below, the Lakota-Morrison (GRID) surface dataset is depicted twice as solid-fill polygons, and a Mean Sea Level (MSL) surface is depicted as a horizontal red line. A base elevation of -2000 has been set for the cross section diagram. The Lakota-Morrison (GRID) dataset contains cell values that represent depths below Mean Sea Level rather than true elevations (e.g., depth values such as 796, 1142, 2074, 3658). The copy of the surface that appears higher in elevation (light orange in the Preview graphic) has not been inverted by CrossView, and its depth values are interpreted as elevations above MSL. While this is CrossViews default interpretation of surface values (and rightfully so), this depiction inverts the surface intended by its developer. The copy of the surface that appears lower in elevation (light yellow in this screenshot) has been inverted by CrossView, and all its cell values multiplied by negative one (-1). In this very specific situation, inverting the surface causes CrossView to correctly portray this dataset (as envisioned by its developer).
TM
Page 33 of 158
Important Note: If the Export full polygons option is not selected, CrossView outputs a single polygon layer (feature class or shapefile) containing one polygon for each surface dataset selected by the user for depiction as a solid in the output cross section diagram. Only the bottom-most solid surfaces polygon extends down to the specified Base Elevation. The top-most and middle solid surfaces polygons only exist where they are visible as
CrossView 1.1 User Guide (Revision 2)
TM
Page 34 of 158
depicted in the Preview graphic i.e., their output polygon features do not overlap other layers polygon features, and do not extend down to the specified Base Elevation. To illustrate your choices, consider the following diagrams:
(A) This diagram shows the single solid polygon layer output by CrossView when the Export full polygons option is not selected. Note that none of the polygons representing the three surfaces depicted overlap one another, and only the bottom-most surface extends down to the cross section diagrams base elevation. Note also how these multiple surfaces are represented as features within a single polygon layer in the ArcMap Table of Contents.
(B) This diagram shows the multiple, but separate, polygon layers output by CrossView when the Export full polygons option is selected. Note that the polygons representing the three surfaces depicted overlap, and that each extends down to the cross section diagrams base elevation.
CrossView 1.1 User Guide (Revision 2)
TM
Page 35 of 158
Note also how each polygon layer representing an individual surface is listed separately in the ArcMap Table of Contents. Very Important: The Export full polygons option is particularly useful when you have multiple surface datasets whose surfaces intertwine along the course of your cross section, i.e., one surface is higher than another along certain portions of the cross section, but lower along other portions. In these rare cases, CrossView can yield inconsistent results if you output these interwoven surfaces to a single output polygon layer (illustration (A) above). To avoid this problem in these unusual situations, it is recommended that you use the Export full polygons option (illustration (B) above). The separate output polygon layers can then be ordered and visually separated more easily, and according to your specific needs. Further, you can apply altogether different symbology settings (e.g., transparency) among the different layers to help visually distinguish surfaces in complex situations.
TM
Page 36 of 158
Very Important: This tab allows you to specify one or more point layers containing features to be depicted on your cross section diagram as vertical line features (e.g., wells, utility poles). The source planimetric data frame in the screenshot below depicts a selected cross section line (highlighted in cyan) and a point Wells (shapefile) layer. Well features in this layer can be depicted on a cross section diagram as vertical line features if its feature attribute table contains appropriate elevation and/or depth values. Specific point attribute requirements are outlined below.
TM
Page 37 of 158
In the illustration below, the Well datasets point features are depicted as vertical line features.
TM
Notes: o Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables. o The Line Top field is not mandatory if you choose to let these values be set by CrossView to the elevations of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. A Line Bottom field containing elevation values, depths to the bottoms of the vertical line features to be depicted in the output diagram, or vertical thickness values for the vertical line features to be depicted. (See the illustration above.) Notes: o Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables. o Vertical thickness values should be the difference between the top and bottom elevations / depths of the vertical line features to be depicted in the output diagram. o The Line Bottom field is not mandatory if you choose to enter a constant vertical thickness value interactively for all vertical line features to be depicted in the output diagram. Beyond the required fields listed above, input point feature attribute tables or XY event layer source tables may contain as many descriptive attribute fields as needed. VERY IMPORTANT: If a stacked sequence of vertical lines is desired, then the input point layer must contain multiple points at the same location (corresponding to multiple records in the feature attribute table). Similarly, XY event layer tables must also contain multiple records, one for each vertical line element in the stacked sequence of lines to be depicted in the output diagram.
TM
Page 39 of 158
TM
Page 40 of 158
To specify which of these values you want CrossView to use, the Line Top (Choose One) section gives you two pull-down fields that can be used as follows: Important Note: You may only place a selection in ONE of these two fields; the other MUST contain the default value of -None-.
TM
Page 41 of 158
If appropriate, select the field name from the highlighted point datasets table that contains explicit elevations for the vertical locations of the tops of vertical line features to be depicted in the output diagram. Alternatively, you can choose -Top-most Surface- to let top elevation values default to the appropriate elevations at each points location of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. Lastly, if you are specifying a Depth to Top Field value (see below), you MUST select the -None- option for the Top Elevation Field selection. In the screenshot below, the Top Elevation Field pull-down list is depicted, and the user is in the process of selecting the TOC_ELEV field to tell CrossView the top elevation of each vertical line feature.
Page 42 of 158
In the screenshot below, the Depth to Top Field pull-down list is depicted, and the user is in the process of selecting the SCREEN_TOP field to tell CrossView the top elevation of each vertical line feature.
TM
Page 43 of 158
A numeric constant to be used as a vertical thickness measured below an already-established top vertical elevation / location
To specify which of these values you want CrossView to use, the Line Bottom (Choose One) section gives you four fields that can be used as follows: Important Note: You may only place a selection in ONE of these four fields; the other three fields MUST contain the default value of -None- (or blank or zero (0) for the Vertical Thickness Constant field).
TM
Page 44 of 158
TM
Page 45 of 158
If appropriate, select the field name from the highlighted point datasets table that contains a depth value for the bottoms of vertical line features to be depicted in the output diagram. CrossView assumes that depths are measured from the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. If you are specifying a field name or value in ANY of the other three fields in the Line Bottom (Choose One) section, you MUST select the -None- option for the Depth to Bottom Field selection. In the screenshot below, the Depth to Bottom Field pull-down list is depicted, and the user is in the process of selecting the CASE_DEPTH field to tell CrossView the bottom elevation of each vertical line feature.
TM
Page 46 of 158
(D) Z Factor
If the units of measure used for elevation (Z) values in the highlighted point dataset differ from the units of measure used for its horizontal (X,Y) coordinates (e.g., elevations are in feet and horizontal coordinates are in meters), then the elevation (Z) values must be converted to the horizontal coordinate systems units of measure. The Z Factor field allows you to direct CrossView to convert the highlighted point datasets elevation values to a different unit of measure (e.g., feet to meters). Z-values in the highlighted point dataset are multiplied by the Z Factor when calculating output elevations for the tops and bottoms of vertical line features to be depicted in the output diagram. Important Notes: This field defaults to a value of one (1), indicating that a unit of elevation is the same as a horizontal unit of measure (e.g., both are in feet or both are in meters). Unless a Z Factor is specified, CrossView expects the horizontal and vertical units of measure in a surface dataset to be the same. If the horizontal X,Y units and vertical Z units of a surface dataset differ, the Z Factor must be set appropriately, or the resulting cross section will be incorrect. The Z Factor should not be used to convert elevations from one vertical datum to another. It is the users responsibility to ensure that all datasets to be represented in the cross section diagram use the same vertical datum for their elevation measurements.
TM
Page 47 of 158
In the screenshot below, the highlighted point datasets elevation (Z) units are in feet and its horizontal (X,Y) units are meters. In this case, a Z Factor (0.3048) must be entered to convert Z units from feet to meters (1 foot = 0.3048 meters).
TM
Page 48 of 158
Important Notes: You MUST click the Search button after entering a Search Distance value! After clicking the Search button, you can change the search distance (or any other setting for the highlighted point dataset), if desired. Once change(s) have been made to the datasets settings, you must click the Search button AGAIN to use the new settings to search for applicable point features. The Search Distance value should be in the same units of measure (e.g., feet or meters) as the horizontal coordinates of the layers in the source MXD data view.
In the screenshot below, a Search Distance of 5 (feet) has been specified. All well features (the highlighted point dataset) within 5 feet of the planimetric line that defines the course of the cross section will be found by the search, and depicted as vertical line features on the output diagram.
TM
Page 49 of 158
Very Important: This tab allows you to specify one or more point layers containing features to be depicted on your cross section diagram as either a single vertically oriented polygon column feature or multiple, vertically stacked polygon column features (e.g., soil bores, well screens) The source planimetric data frame in the screenshot below depicts a selected cross section line (highlighted in cyan) and a point soil_bores Events (dbf) layer. Soil bore features in this layer can be depicted on a cross section diagram as vertically oriented polygon features if its feature attribute table contains appropriate elevation and/or depth values. Specific point attribute requirements are outlined below.
TM
Page 50 of 158
In the illustration below, the Soil Bore datasets point features are depicted as vertically stacked polygon column features.
Data Requirements for Point Layers to be Represented as Vertically Oriented Polygon Columns
Input point layers can be geodatabase feature classes, shapefiles, or ArcInfo coverages. Alternatively, XY Event Layers containing appropriate, projected coordinates of point locations (XY events) can be used instead of geospatial point layers. Each point feature in an input point layer corresponds to a single record in either a feature attribute table or an XY event layer source table. CrossView converts each input point feature / table record to a single vertically oriented polygon column feature in the output cross section diagram. Each input point feature attribute table or XY event layer source table MUST contain the following pieces of information in unique fields: Important Note: For a more detailed discussion of these fields, please see Point layer(s) to be depicted as vertically oriented polygon columns under the Optional Input Datasets portion of Appendix A: Required and Optional Input Geospatial Datasets of this documentation. X Coordinate Values (these are implicit within geospatial point layers) Y Coordinate Values (also implicit within geospatial point layers) A Polygon Top field containing either elevation values or depths to the tops of the vertically oriented polygon column features to be depicted in the output diagram. (See the illustration on the following page for reference.)
Page 51 of 158
TM
Notes: o Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables. o The Polygon Top field is not mandatory if you choose to let these values be set by CrossView to the elevations of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. A Polygon Bottom field containing elevation values, depths to the bottoms of the vertically oriented polygon column features to be depicted in the output diagram, or vertical thickness values for the vertically oriented polygon features to be depicted. (See the illustration above.) Notes: o Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables. o Vertical thickness values should be the difference between the top and bottom elevations / depths of the vertically oriented polygon column features to be depicted in the output diagram. o The Polygon Bottom field is not mandatory if you choose to enter a constant vertical thickness value interactively for all vertically oriented polygon column features to be depicted in the output diagram. Beyond the required fields listed above, input point feature attribute tables or XY event layer source tables may contain as many descriptive attribute fields as needed. VERY IMPORTANT: If a stacked sequence of vertically oriented polygon column features is desired, then the input point layer must contain multiple points at the same location (corresponding to multiple records in the feature attribute table). Similarly, XY event layer tables must also contain multiple records, one for each vertically oriented polygon element in the stacked sequence of polygon columns to be depicted in the output diagram.
CrossView 1.1 User Guide (Revision 2)
TM
Page 52 of 158
TM
Page 53 of 158
To specify which of these values you want CrossView to use, the Polygon Top (Choose One) section gives you two pull-down fields that can be used as follows: Important Note: You may only place a selection in ONE of these two fields; the other MUST contain the default value of -None-.
TM
Page 54 of 158
TM
Page 55 of 158
Page 56 of 158
An explicit elevation (e.g., in feet or meters above mean sea level) A vertical thickness (e.g., in feet or meters) measured below an alreadyestablished top vertical elevation / location A depth (e.g., in feet or meters) at each points location below the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab A numeric constant to be used as a vertical thickness measured below an alreadyestablished top vertical elevation / location
To specify which of these values you want CrossView to use, the Polygon Bottom (Choose One) section gives you four fields that can be used as follows: Important Note: You may only place a selection in ONE of these four fields; the other three fields MUST contain the default value of -None- (or a blank or zero (0) for the Vertical Thickness Constant field).
TM
Page 57 of 158
In the screenshot below, the Bottom Elevation Field pull-down list is depicted, and the user is in the process of selecting the depth field to tell CrossView the bottom elevation of each vertically oriented polygon column feature.
TM
Page 58 of 158
TM
Page 59 of 158
TM
Page 60 of 158
These three widths are calculated automatically as set percentages of the total length of the planimetric line that defines the course of the cross section. The Narrow width is 2% of the total profile length; the Medium width is 5%; and the Wide width is 8% of the total profile length. In the screenshot below, the Medium Polygon Width has been selected. In this 875-long profile, each vertically oriented polygon column feature will be 43.75 wide (5% of the total length).
TM
Page 61 of 158
(E) Z Factor
If the units of measure used for elevation (Z) values in the highlighted point dataset differ from the units of measure used for its horizontal (X,Y) coordinates (e.g., elevations are in feet and horizontal coordinates are in meters), then the elevation (Z) values must be converted to the horizontal coordinate systems units of measure.
CrossView 1.1 User Guide (Revision 2)
TM
Page 62 of 158
The Z Factor field allows you to direct CrossView to convert the highlighted point datasets elevation values to a different unit of measure (e.g., feet to meters). Z-values in the highlighted point dataset are multiplied by the Z Factor when calculating output elevations for the tops and bottoms of vertically oriented polygon column features to be depicted in the output diagram. Important Notes: This field defaults to a value of one (1), indicating that a unit of elevation is the same as a horizontal unit of measure (e.g., both are in feet or both are in meters). Unless a Z Factor is specified, CrossView expects the horizontal and vertical units of measure in a surface dataset to be the same. If the horizontal X,Y units and vertical Z units of a surface dataset differ, the Z Factor must be set appropriately, or the resulting cross section will be incorrect. The Z Factor should not be used to convert elevations from one vertical datum to another. It is the users responsibility to ensure that all datasets to be represented in the cross section diagram use the same vertical datum for their elevation measurements. In the screenshot below, the highlighted point datasets elevation (Z) units are in feet and its horizontal (X,Y) units are meters. In this case, a Z Factor (0.3048) must be entered to convert Z units from feet to meters (1 foot = 0.3048 meters).
TM
Page 63 of 158
In the screenshot on the following page, a Search Distance of 6 (feet) has been specified. All Soil Bore features (the highlighted point dataset) within 6 feet of the planimetric line that defines the course of the cross section will be found by the search, and depicted as vertically oriented polygon column features on the output diagram.
TM
Page 64 of 158
TM
Page 65 of 158
Very Important: This tab allows you to specify one or more point layers containing features to be depicted on your cross section diagram as point features at a specified elevation or depth (e.g., soil or groundwater sample locations, soil property measurement locations, utility line locations). The source planimetric data frame in the screenshot below depicts a selected cross section line (highlighted in cyan) and a point ABCD Samples (shapefile) layer. Chemical sample concentration features in this layer can be depicted on a cross section diagram as point features at a specified elevation or depth if its feature attribute table contains appropriate elevation and/or depth values. Specific point attribute requirements are outlined below.
TM
Page 66 of 158
In the illustration below, the ABCD Sample Concentrations datasets point features are depicted as points at depth.
Data Requirements for Point Layers to be Represented as Points at a Specified Elevation or Depth
Input point layers can be geodatabase feature classes, shapefiles, or ArcInfo coverages. Alternatively, XY Event Layers containing appropriate, projected coordinates of point locations (XY events) can be used instead of geospatial point layers. Each point feature in an input point layer corresponds to a single record in either a feature attribute table or an XY event layer source table. CrossView converts each input point feature / table record to a single vertically oriented polygon column feature in the output cross section diagram. Each input point feature attribute table or XY event layer source table MUST contain the following pieces of information in unique fields: Important Note: For a more detailed discussion of these fields, please see Point layer(s) to be depicted as point features at an elevation or depth under the Optional Input Datasets portion of Appendix A: Required and Optional Input Geospatial Datasets of this documentation.
TM
Page 67 of 158
X Coordinate Values (these are implicit within geospatial point layers) Y Coordinate Values (also implicit within geospatial point layers) A Point Elevation or Depth to Point field containing either elevation values or depths to the point features to be depicted in the output diagram. (See the illustration below for reference.)
Notes: o Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables. o Neither the Point Elevation field nor the Depth to Point field are mandatory if you choose to let these values be set by CrossView to the elevations of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. o Furthermore, neither the Point Elevation field nor the Depth to Point field are mandatory if you choose to enter a constant point depth value interactively for all point features to be depicted in the output diagram. Beyond the required fields listed above, input point feature attribute tables or XY event layer source tables may contain as many descriptive attribute fields as needed. VERY IMPORTANT: If a stacked sequence of vertically oriented point features is desired (e.g., point locations at increasing depths down a well casing or soil bore), then the input point layer must contain multiple points at the same location (corresponding to multiple records in the feature attribute table). Similarly, XY event layer tables must also contain multiple records, one for each point at depth element in the stacked sequence of points to be depicted in the output diagram.
TM
Page 68 of 158
Page 69 of 158
where each point feature is (in elevation) relative to other surfaces and features to be depicted in the output diagram. The vertical location of a point feature can be expressed in four ways (see the diagram below for reference): An explicit elevation (e.g., in feet or meters above mean sea level) Default to the elevation at each points location of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab A depth (e.g., in feet or meters) at each points location below the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab A numeric depth constant measured at each points location below the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab.
To specify which of these values you want CrossView to use, the Choose One section gives you three pull-down fields that can be used as follows: Important Note: You may only place a selection in ONE of these three fields; the others MUST contain the default value of -None- (or a blank or zero (0) for the Depth to Point Constant field value).
TM
Page 70 of 158
location) of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. Lastly, if you are specifying a Depth to Point Field value or a Depth to Point Constant value (see below), you MUST select the -None- option for the Point Elevation Field selection. In the screenshot below, the Point Elevation Field pull-down list is depicted, and the user is in the process of selecting the -Top-most Surface- option to tell CrossView the elevation of each point at depth or elevation feature.
TM
Page 71 of 158
In the screenshot below, the Depth to Point Field pull-down list is depicted, and the user is in the process of selecting the depth field to tell CrossView the elevation of each point at depth feature.
TM
Page 72 of 158
(C) Z Factor
If the units of measure used for elevation (Z) values in the highlighted point dataset differ from the units of measure used for its horizontal (X,Y) coordinates (e.g., elevations are in feet and horizontal coordinates are in meters), then the elevation (Z) values must be converted to the horizontal coordinate systems units of measure. The Z Factor field allows you to direct CrossView to convert the highlighted point datasets elevation values to a different unit of measure (e.g., feet to meters). Z-values in the highlighted point dataset are multiplied by the Z Factor when calculating output elevations for the point features at depth or elevation to be depicted in the output diagram.. Important Notes: This field defaults to a value of one (1), indicating that a unit of elevation is the same as a horizontal unit of measure (e.g., both are in feet or both are in meters). Unless a Z Factor is specified, CrossView expects the horizontal and vertical units of measure in a surface dataset to be the same. If the horizontal X,Y units and vertical Z units of a surface dataset differ, the Z Factor must be set appropriately, or the resulting cross section will be incorrect. The Z Factor should not be used to convert elevations from one vertical datum to another. It is the users responsibility to ensure that all datasets to be represented in the cross section diagram use the same vertical datum for their elevation measurements.
TM
Page 73 of 158
In the screenshot below, the highlighted point datasets elevation (Z) units are in feet and its horizontal (X,Y) units are meters. In this case, a Z Factor (0.3048) must be entered to convert Z units from feet to meters (1 foot = 0.3048 meters).
TM
Page 74 of 158
Important Notes: You MUST click the Search button after entering a Search Distance value! After clicking the Search button, you can change the search distance (or any other setting for the highlighted point dataset), if desired. Once change(s) have been made to the datasets settings, you must click the Search button AGAIN to use the new settings to search for applicable point features. The Search Distance value should be in the same units of measure (e.g., feet or meters) as the horizontal coordinates of the layers in the source MXD data view.
In the screenshot below, a Search Distance of 5 (feet) has been specified. All utility line location features (the highlighted point dataset) within 5 feet of the planimetric line that defines the course of the cross section will be found by the search, and depicted as point features at depth on the output diagram.
TM
Page 75 of 158
Very Important: The Preview Section of the CrossView Dialog window provides you with a visual graphic of what the cross section diagram you are developing will look like when output to ArcMap. It also allows you to specify whether or not to display (and output) a reference grid for your cross section diagram, as well as the distance intervals for both horizontal and vertical grid lines.
Page 76 of 158
Important Note: The Preview Graphics display is not WYSIWYG (what you see is what you get). However, it provides a very useful visual preview (and close approximation) of what you can expect for output in ArcMap. This is particularly true as you become more proficient with CrossView, and come to rely on the Preview graphic as your guide when specifying and/or selecting various elements to add to (or alter on) a diagram. As you move your cursor around on the Preview Graphic display, its appropriate coordinate location is shown below the display and to the right of the Map Location: text. Displayed X-coordinate values are measured in linear distance units from the beginning of the line defining the planimetric course of the cross section to its end. The units of measure for these Xcoordinates are the same as those used for the horizontal coordinate system shared by the layers in the source MXDs data view. Displayed Y-coordinate values are in the elevation datum shared by the layers in the source MXDs data view.
TM
Page 77 of 158
TM
Page 78 of 158
Important Notes Concerning Grid Settings: Whenever you change a Major or Minor Grid parameters value, you must click in a separate (different) grid parameter field for the change to be recognized by CrossView. To add Minor Grid lines or adjust the interval (spacing) of Minor Grid lines, specify the number of Minor Grid intervals (i.e., gaps or spaces) that you want between Major Grid lines in the Number of Minor Grid Intervals fields for the X and Y axes. Important: Values entered in the Number of Minor Grid Line Intervals fields for the X and Y axes are not distances between Minor Grid lines. Instead, these values need to be the number of Minor Grid intervals between Major Grid lines. Example: You have Major Grid Intervals set at: X = 200 and Y = 20. You want Minor Grid lines every 50 along the X axis and every 5 along the Y axis (in between the Major Grid lines). There are four (4) 50 INTERVALS for every 200 Major Grid interval along the X axis. Therefore, you need to enter 4 in the Number of Minor Grid Line Intervals X field to get Minor Grid lines every 50 between Major Grid lines along the X axis. Similarly, there are four (4) 5 INTERVALS for every 20 Major Grid interval along the Y axis. Therefore, you need to enter 4 in the Number of Minor Grid Line Intervals Y field to get Minor Grid lines every 5 between Major Grid lines. (See screenshot below.)
TM
Page 79 of 158
CrossView assumes that you will want a grid containing Major Grid lines generated for your output cross section diagram. If this is not the case, simply enter X and Y Major Grid Intervals that are LARGER than the horizontal and vertical extents of your cross section diagram. Important Note: You should NOT enter zero (0) values in the Major Grid Interval fields to turn off Major Grid lines (this simply will not work). Instead, follow the instructions in the above bulleted text.
TM
Page 80 of 158
Very Important: The Options Section of the CrossView Dialog window provides you with fields that allow you to apply a vertical exaggeration to the output cross section diagram, and set a base elevation for the diagram. This Section also gives you a checkbox to toggle the display of the entire Preview Section of the Dialog window on or off.
Page 81 of 158
For example, with a vertical exaggeration of 2, Y axis units would be doubled in height on a cross section diagram, while X axis units would remain unchanged. With a vertical exaggeration of 10, Y axis units would be 10 times their original height on the diagram, while (again) X axis units would remain unchanged. The Preview Graphics in the following screen captures illustrate the effects different vertical exaggerations have on a given cross section area: Vertical Exaggeration = None ( 1 unit in X = 1 unit in Y )
TM
Page 82 of 158
TM
Page 83 of 158
TM
Page 84 of 158
In the second set of screen captures, a Base Elevation of 4,800 has been set for the cross section. Note how dramatically different the surface appears in the Preview Graphic. The diagram now depicts a surface polygon feature that is still 875 wide, but is only about 450 thick.
In the final set of screen captures, a Base Elevation of 5,150 has been set for the cross section, along with a Vertical Exaggeration of 5 (to emphasize vertical relief across this relatively flat surface). The surface polygon feature is still 875 wide, and its thickness (depth) has been reduced to approximately 100 (at its highest elevation). Due to the vertical exaggeration, note that this 100 thickness has been stretched to look approximately 500 thick.
TM
Page 85 of 158
The CrossView Dialog window with the Preview Section display toggled on:
The CrossView Dialog window with the Preview Section display toggled off:
TM
Page 86 of 158
Before finishing with the CrossView Dialog window, it is wise to make sure that you have performed the following required steps (and as many of the following optional steps, as needed) to generate your cross section diagram: Required or Optional ========= Required Required ---------------Optional Optional Optional Optional Optional Optional Optional =========
Step Description ============================================== Select and configure at least one surface dataset for display Configure Major Grid line settings for the output diagram --------------------------------------------------------------------------------Select and configure other surface dataset(s) for display Select and configure point dataset(s) for display as vertical lines Select and configure point dataset(s) for display as vertically oriented polygons Select and configure point dataset(s) for display as points at depth Configure Minor Grid settings for the output diagram Set an appropriate vertical exaggeration for the output diagram Set an appropriate base elevation for the output diagram ==============================================
TM
Page 87 of 158
A complete review of all the possible feature classes or shapefiles that CrossView generates can be found in the Layers Output by CrossView section of this User Guide. All output feature classes or shapefiles are placed in the geodatabase, geodatabase feature dataset, or folder of your choice on either your PC or network. You navigate to the target geodatabase, feature dataset, or folder on the Choose a Base Filename popup window (shown on the following page). Names of all output feature classes or geodatabases, regardless of their content, begin with a prefix of your choosing (also entered on the Choose a Base Filename popup window). The middle portions and numeric suffixes of output layer names are generated by CrossView; these are thoroughly reviewed in the Layers Output by CrossView section of this User Guide.
TM
Page 88 of 158
In addition, the new Cross Section data frame displays the appropriate grid lines, axes, tics, and tic labels that you specified in CrossViews Dialog window.
TM
Page 89 of 158
(C) Finishing
1) The Finish Button
When you are ready to generate your cross section diagram (in the form of all the output briefly described above): Click on the Finish button in the extreme lower-right corner of the CrossView Dialog window. The Choose a Base Filename popup window appears.
Page 90 of 158
Once the output layers have been created: CrossView returns you to your source ArcMap map document (MXD) and automatically places you on that documents layout view. CrossView creates a new data frame (entitled Cross Section) in the lower left-most corner of the MXDs page layout. This data frame contains all of the output feature classes or shapefiles needed to depict your cross section diagram. CrossView graphically selects the Cross Section data frame on the page layout.
TM
Page 91 of 158
TM
Page 92 of 158
While there are a number of ways to eliminate these gaps so that grid extents snap back to the left (beginning) and right (end) of the cross section, the fastest ways are to: Re-size (in a minor way) the Cross Section data frame using one of its four corner graphic handles. It is easiest to click and drag the upper-right handle just a bit further to the upper-right. Quickly toggle over to the Data View for the cross section frame, and then return to the Page Layout View.
Regardless of which method you choose to readjust the data frame, the resulting data frame will display the cross section elements across its full extent (see the screenshot on the following page).
TM
Page 93 of 158
TM
Page 94 of 158
The four fields on the Update Extents dialog allow you to adjust the following: Min X This value sets the minimum X-axis extent. CrossView initially sets this value to zero (0), marking the beginning of the planimetric line that defines the course of the cross section. Max X This value sets the maximum X-axis extent. CrossView initially sets this value to the end length of the planimetric line that defines the course of the cross section. Min Y This value sets the minimum Y-axis extent. CrossView initially sets this value to the Base Elevation value you specified in the CrossView Dialog window. Max Y This value sets the maximum Y-axis extent. CrossView initially sets this value to an elevation that is as high above the highest point on the topmost surface in the diagram as the Base Elevation is below the lowest point on that same surface.
CrossView 1.1 User Guide (Revision 2)
TM
Page 95 of 158
You can adjust any or all of these grid extents, as needed. Regardless of how you change grid extents within the data frame, the extents of the data frames profile features (i.e., the polygon, line, and point feature classes or shapefiles) do not change. It is possible, therefore, to extend the grid beyond the leftmost, right-most, and bottom-most extents of the profiles / cross sections features (see example at right). Note: A negative Minimum X-Axis grid extent is particularly helpful if you want extra space inside the grid to the left of the profiles beginning. After changing extent values in fields on the Update Extents dialog, click the Apply button to change grid extents in the Cross Section data frame. When finished with the Update Extents dialog, click the Exit button to close its window.
TM
Page 96 of 158
TM
Page 97 of 158
(A) Identify the Horizontal Coordinate System Properties of the Source Planimetric Data Frame from which the Cross Section Data Frame was Generated
Important Notes: Although the Cross Section data frame created by CrossView initially has undeclared projection, coordinate system, and units of measure properties, these are, in reality for the diagrams horizontal (X or distance) axis, derived from those of the source planimetric data frame. The units of measure of the Cross Section data frames vertical (Y or elevation) axis should also reflect those of the source planimetric data frames units of measure property. This will be the case if the horizontal and vertical units of measure of the surface dataset(s) represented in the cross section diagram are the same, or if the user specified an appropriate Z-Factor on the CrossView dialogs Surfaces tab.
TM
Page 98 of 158
In the example below, the horizontal coordinate system and units of measure of the source planimetric data frame (at the top of the page layout) are: Colorado State Plane, NAD27, U.S. Survey Feet (this coordinate system is based on a Lambert Conformal Conic projection).
Note: If you want to set the scale of the Cross Section data frame to match that of the source planimetric data frame, switch to the Data Frame Tab in the Data Frame Properties dialog window, and note the scale of the source data frame.
TM
Page 99 of 158
The Data Frame Properties dialog Data Frame Tab shown at right indicates that the example source planimetric data frame has a Fixed Scale of 1:2,500.
Cross Section data frames name in the ArcMap Table of Contents, and select Activate from the context menu that appears.
TM
Important Note: If you switch to the Data Frame Properties dialogs General Tab, you will notice that the data frames Units settings are no longer unknown instead, they reflect the units of measure of the source data frames projection and coordinate system.
(D) Set a Fixed Scale for the Cross Section Data Frame
1) Switch to the Data Frame Tab
With the Cross Section Data Frame Properties dialog open, switch to the Data Frame Tab. In the Extent section of this Tab, the Fixed Extent radio button is pre-selected, and the values in its fields are set to either: those established by CrossView when it created the Cross Section data frame, or those set with the CrossView Update Extents utility.
TM
The graphic elements within the Cross Section data frame will be adjusted to the scale you have specified. Important Note: After the Cross Section data frame has been rescaled, you will almost always notice that the cross section diagrams elements no longer extend to the left, right, and bottom edges of the Cross Section data frame. The graphic below depicts a planimetric data frame (containing a selected cross section line) with a scale of 1:2,500, and a Cross Section data frame that has been set to this same scale. In the cross section diagram, note how its graphic elements (in this case, a polygon feature representing a single surface) no longer extend to the left, right, and bottom edges of the data frame.
TM
A Cross Section data frame after setting a fixed scale, and after manual resizing:
TM
TM
TM
As output, CrossView creates a variety of ESRI feature classes or shapefiles, and places these in the output geodatabase, geodatabase feature dataset, or folder you specify in the Choose a Base Filename popup window. The numbers and categories of these layers depend on the variety of elements you have selected for output to your cross section diagram. There are three general categories of feature classes or shapefiles: Feature classes or shapefiles placed in the Cross Section data frame These are CrossViews primary output layers, and the ones with which you most commonly interact after CrossView has created your diagram in the Cross Section data frame. Grid Line feature classes or shapefiles Grid line layers are created by CrossView to support the ArcMap custom grid(s) that CrossView creates to depict Major (and if selected, Minor) grid lines on your output cross section diagram. Buffer Polygon feature classes or shapefiles These layers are created during each CrossView search distance operation for point layer features to be depicted as points at depth, vertical lines, or vertically oriented polygons on your output cross section diagram.
Following is a detailed listing of all the feature classes or shapefiles that CrossView can generate in these three categories: Notes: The Base Filename that you specify in the Choose a Base Filename popup window is always used as the prefix for ALL feature class or shapefile names. In the list below, the character string <name> is used as a place holder (variable) for your specified Base Filename. With the exceptions of the solids feature class or shapefile (see below) and Grid Line feature classes or shapefiles, the names of layers end in a suffix containing the under-bar character followed by an integer (e.g., _1, _3, etc.). These numbers indicate the position of the input dataset (surface or point layer) on the list of datasets on the CrossView Tab used to select and configure the given dataset for inclusion and display on the output diagram. In the list below, the # character is used as a place holder (variable) for this integer.
TM
(1) Feature Classes or Shapefiles Placed in the Cross Section Data Frame
For each of the input datasets (surfaces and point layers) selected for display in the output cross section diagram, CrossView generates a unique feature class or shapefile containing the polygon, line, or point features needed to appropriately depict that datasets information. Following is a complete list of the six (6) types of feature classes or shapefiles CrossView can generate and place in the output Cross Section data frame.
(A) <name>_solids
If you do not check the Export full polygons option checkbox on the Surfaces tab, this polygon feature class or shapefile contains the polygon features for ALL of the surfaces selected and configured on the Surfaces Tab for display as a solid on the output cross section diagram. The layers feature attribute table contains a descr field that lists, for each polygon feature in the layer, its surface name from the source ArcMap MXDs Table of Contents. Very Important Note: If you do check the Export full polygons option checkbox on the Surfaces tab, a SERIES of polygon feature classes or shapefiles are generated. Each layer in the series contains a single polygon feature that represents one of the surfaces selected and configured on the Surfaces Tab for display as a solid on the output cross section diagram. Each layers feature attribute table contains a descr field that lists its surface name from the source ArcMap MXDs Table of Contents. Each polygon layer in the series is given a unique name: <name>_solid_#
(B) <name>_surface_#
Each of these line feature classes or shapefiles contains the single line feature for ONE of the surfaces selected and configured on the Surfaces Tab for display as a horizontally oriented surface line on the output cross section diagram. Each layers single-record feature attribute table contains a descr field that lists the appropriate surface name from the source ArcMap MXDs Table of Contents.
TM
(C) <name>_overlaysurface_#
Each of these line feature classes or shapefiles contains a sequence of line features depicting ONE of the surfaces selected and configured on the Surfaces Tab for display as a surface line split using a polygon overlay on the output cross section diagram. Each line feature in each of these layers has been created by splitting the full surface profile line at the boundaries of the specified overlay polygon layer. Taken together, this sequence of lines depicts the selected surface in full profile. Each layers feature attribute table contains the attribute fields from the selected overlay polygon layer, and each line features attribute record lists the descriptive attributes of the appropriate overlay polygon. Important Note: When you specify that you want to display a surface as a surface line on the Surfaces Tab, and then further specify that you want to split this surface line using a polygon overlay, CrossView generates TWO output feature classes or shapefiles. First, a <name>_surface_# layer is created containing a single horizontally oriented line depicting the surface. Second, a <name>_overlaysurface_# layer is created containing the sequence of lines (created by splitting the single surface line), each attributed with the appropriate values from the selected overlay polygon layer.
(D) <name>_pointline_#
Each of these line feature classes or shapefiles contains line features derived from one of the point layers selected on the Points to Lines Tab for display as vertical line features on the output cross section diagram. Each layers feature attribute table contains the attribute fields from the selected point layer, and each line features attribute record lists the descriptive attributes of the appropriate source point feature it represents. In addition, each layers feature attribute table contains two additional fields as described below: 1) The cv_offset field lists how far away (perpendicularly) each vertical line in the layer is from the planimetric line defining the course of the cross section. When you specified a Search Distance for the selected input point layer on the Points to Lines Tab, CrossView searched out perpendicularly from the planimetric cross section line to locate point features within your specified distance. The cv_offset field provides you with the exact
CrossView 1.1 User Guide (Revision 2)
TM
distance between each located point (depicted on the cross section diagram as a vertical line) and the planimetric cross section line. Units of measure for cv_offset distance values are the same as for the planimetric cross section line. 2) The cv_dist field lists how far each vertical line in the layer is along the planimetric line defining the course of the profile from its beginning. Units of measure for cv_dist field distance values are the same as for the planimetric cross section line.
(E) <name>_pointpoly_#
Each of these polygon feature classes or shapefiles contains polygon features derived from one of the point layers selected on the Points to Polygons Tab for display as vertically oriented polygon column features on the output cross section diagram. Each layers feature attribute table contains the attribute fields from the selected point layer, and each polygon features attribute record lists the descriptive attributes of the appropriate source point feature it represents. In addition, each layers feature attribute table contains two additional fields as described below: 1) The cv_offset field lists how far away (perpendicularly) each vertically oriented polygon column feature in the layer is from the planimetric line defining the course of the cross section. When you specified a Search Distance for the selected input point layer on the Points to Polygons Tab, CrossView searched out perpendicularly from the planimetric cross section line to locate point features within your specified distance. The cv_offset field provides you with the exact distance between each located point (depicted on the cross section diagram as a vertically oriented polygon column) and the planimetric cross section line. Units of measure for cv_offset distance values are the same as for the planimetric cross section line. 2) The cv_dist field lists how far each vertically oriented polygon column feature in the layer is along the planimetric line defining the course of the profile from its beginning. Units of measure for cv_dist field distance values are the same as for the planimetric cross section line.
TM
(F) <name>_pointpoint_#
Each of these point feature classes or shapefiles contains point features derived from one of the point layers selected on the Points to Points Tab for display as point features at depth or elevation on the output cross section diagram. Each layers feature attribute table contains the attribute fields from the selected point layer, and the attribute record for each point feature at depth or elevation lists the descriptive attributes of the appropriate source point feature it represents. In addition, each layers feature attribute table contains two additional fields as described below: 1) The cv_offset field lists how far away (perpendicularly) each vertically oriented polygon column feature in the layer is from the planimetric line defining the course of the cross section. When you specified a Search Distance for the selected input point layer on the Points to Polygons Tab, CrossView searched out perpendicularly from the planimetric cross section line to locate point features within your specified distance. The cv_offset field provides you with the exact distance between each located point (depicted on the cross section diagram as a vertically oriented polygon column) and the planimetric cross section line. Units of measure for cv_offset distance values are the same as for the planimetric cross section line. 2) The cv_dist field lists how far each vertically oriented polygon column feature in the layer is along the planimetric line defining the course of the profile from its beginning. Units of measure for cv_dist field distance values are the same as for the planimetric cross section line.
TM
(A)
<name>_grid
This line feature class or shapefile contains all of the line features needed by ArcMap to display the Major Grid lines specified in the Preview Section of the CrossView Dialog window and output to the Cross Section data frame. Each grid layers feature attribute table contains a descr field containing the numeric values for each grid line. Horizontal lines are given appropriate elevation values, and vertical lines are given appropriate cross section distance (length) values (measured from the cross sections beginning point).
(B)
<name>_subgrid
This line feature class or shapefile contains all of the line features needed by ArcMap to display the Minor Grid lines specified in the Preview Section of CrossViews Dialog window and output to the Cross Section data frame. A feature class or shapefile for Minor grid lines is generated by CrossView ONLY if non-zero values have been specified in either (or both) of the Number of Minor Grid Intervals fields in the Preview Section. Each grid layers feature attribute table contains a descr field containing the numeric values for each grid line. Horizontal lines are given appropriate elevation values, and vertical lines are given appropriate cross section distance (length) values (measured from the cross sections beginning point).
TM
(A)
<name>_buff_#
Each of these polygon buffer feature classes or shapefiles contains a single polygon feature created around the planimetric line in the source ArcMap MXD that delineates the course of the cross section. Each buffer is created during CrossViews search for point features in one of the point layers selected on the Points to Lines Tab for display as vertical lines on the output cross section diagram. Each buffer layers feature attribute table contains a descr field containing the value buffer for the single buffer polygon feature in the feature class or shapefile.
(B)
<name>_buff__pointpoly_#
Each of these polygon buffer feature classes or shapefiles contains a single polygon feature created around the planimetric line in the source ArcMap MXD that delineates the course of the cross section. Each buffer is created during CrossViews search for point features in one of the point layers selected on the Points to Polygons Tab for display as vertically oriented polygon column features on the output cross section diagram. Each buffer layers feature attribute table contains a descr field containing the value buffer for the single buffer polygon feature in the feature class or shapefile.
(C)
<name>_buff__pointpoint_#
Each of these polygon buffer feature classes or shapefiles contains a single polygon feature created around the planimetric line in the source ArcMap MXD that delineates the course of the cross section. Each buffer is created during CrossViews search for point features in one of the point
TM
layers selected on the Points to Points Tab for display as point features at depth or elevation on the output cross section diagram. Each buffer layers feature attribute table contains a descr field containing the value buffer for the single buffer polygon feature in the feature class or shapefile.
TM
TM
CRITICAL: It is essential to understand that all feature classes or shapefiles placed in the Cross Section data frame by CrossView can be symbolized and manipulated just like any other set of layers in any other ArcMap data frame. The symbolization possibilities for layers and features output by CrossView are limitless within the bounds of the ArcMap application itself. Following are brief, simple examples of how features within the six (6) types of feature classes or shapefiles placed in the Cross Section data frame can be symbolized. Note: This section of the User Guide references the six (6) types of feature classes or shapefiles placed in the Cross Section data frame discussed in the Layers Output by CrossView section of this Guide above. o The Base Filename specified in the Choose a Base Filename popup window is used as the prefix for ALL layers names. In what follows, the character string <name> is used as a place holder (variable) for your specified Base Filename. o Feature classes or shapefiles that are symbolized within the Cross section data frame end in a suffix containing the under-bar character followed by an integer (e.g., _1, _3, etc.). These numbers indicate the position of the input dataset (surface or point layer) on the list of datasets on the CrossView Tab used to select and configure the given dataset for inclusion and display on the output diagram. In what follows, the # character is used as a place holder (variable) for this integer.
TM
TM
TM
TM
TM
TM
TM
TM
The point, line, and polygon feature classes or shapefiles output by CrossView and placed in the Cross Section data frame carry with them any descriptive attributes present in the input point layers or input polygon overlay layers. CRITICAL: It is essential to understand that you can use these descriptive attribute values to label and/or annotate features in the Cross Section data frame just as you would any layer in any other ArcMap data frame. The labeling and annotation possibilities for features output by CrossView are limitless within the bounds of the ArcMap application itself. Set the Cross Section Data Frames Map Units within ArcMap Important Note: CrossView does not set the output Cross Section data frames map units within ArcMap (e.g., feet, meters, etc.). Before you can convert dynamic labels to annotation in this data frame, you must first specify the appropriate map units in ArcMap. To set the Cross Section data frames map units within ArcMap, do the following:
TM
TM
And as with any data frame, a legend can be added to assist with conveying your cross section diagrams information:
TM
Altering Major and Minor Grids in the Cross Section Data Frame
TM
CrossView generates an ArcMap Custom Grid for Major Grid lines placed in the output data frame. If specified by the user, a separate Custom Grid for Minor Grid lines is also created. To view and change (if needed) the properties of each of these Custom Grids:
TM
(3) View and Edit Grid Properties: The Reference System Properties Dialog
To view (and edit) the properties of either of these ArcMap Custom Grids, highlight the grids name on the Grids Tab list, and click on the Properties button. The grids Reference System Properties dialog opens and displays the first (Custom Overlay) of its four Tabs.
The name of the grid feature class or shapefile used for the ArcMap Custom Grid selected on the Grids Tab is listed in the System: field on the Custom Overlay tab of the Reference System Properties dialog. Under normal circumstances, DO NOT CHANGE the name of the feature class or shapefile in the System: field, nor the field name listed in the Label field:. Notes: Based on your Major and Minor Grid specification in the Preview Section of the CrossView Dialog window, CrossView creates line layer(s) containing all of the appropriate grid lines for each ArcMap Custom Grid it makes in the Cross Section data frame. The <name>_grid feature class or shapefile is created for Major grid lines, and, if specified by the user, the <name>_subgrid feature class or shapefile is created for Minor grid lines. Each grid feature class or shapefile is placed in the output geodatabase, feature dataset, or folder you specified in the Choose a Base Filename popup when finishing the CrossView Dialog window (i.e., the
Page 128 of 158
TM
same geodatabase, feature dataset, or folder that holds all the other output feature classes or shapefiles generated by CrossView for your cross section diagram).
* Note: On the Lines tab of the Reference System Properties dialog, the Show as a grid of ticks option will not yield a grid of ticks it will instead result in the grid lines not being shown at all (i.e., it produces the same result as the Do not show lines or ticks option). This is due to the grid line layer that CrossView generated for this Custom Grid (it only contains full lines, so ticks are not available).
TM
TM
TM
CrossView 1.1 creates cross section diagrams using data within ArcMaps active Data Frame (data view). Before attempting to use CrossView with their own datasets, we strongly recommend that users review and understand the types of data (and formats) that CrossView requires and that can be incorporated optionally when creating a cross section diagram.
TM
In the illustration below, the Bedrock and Topographic surface datasets are depicted as polygon features. The Water Table surface dataset is depicted as a line feature.
TM
In the illustration below, the highlighted line feature (cyan) in the ArcMap Data View has been selected for input to CrossView as the planimetric course of a profile / cross section.
TM
(2) Optional Datasets that can be Incorporated into a Cross Section Diagram
(A) One or more point layers containing features to be
depicted on a cross section diagram as vertical line features (e.g., wells, utility poles)
Note: Input point layers can be geodatabase feature classes, shapefiles, or ArcInfo coverages. Alternatively, XY Event Layers containing appropriate, projected coordinates of point locations (XY events) can be used instead of geospatial point layers. In the illustration below, the Well datasets point features are depicted as vertical line features.
Attribute Format Information Each point feature in an input point layer corresponds to a single record in either a feature attribute table or an XY event layer source table. CrossView converts each input point feature / table record to a single vertical line feature in the output cross section diagram. Each input point feature attribute table or XY event layer source table MUST contain the following pieces of information in unique fields: Important Notes Regarding Field Names: o Field names can be whatever the user would like, since CrossView works with any field name commonly acceptable within other applications.
TM
o Since CrossView can generate ESRI Shapefiles as its output (and these use dBase attribute tables with a field name limit of 10 characters), all input field names should be limited to 10 characters or less if you anticipate creating cross section shapefiles with CrossView. o Since CrossView can generate ESRI File Geodatabase feature classes as its output (and such geodatabases have reserved field names that cannot be used), all input field names must comply with these restrictions if you anticipate creating cross section file geodatabase feature classes with CrossView. X Coordinate Values of the horizontal locations of input point features or XY events. These values are implicit within geospatial point layers such as geodatabase feature classes, shapefiles, and coverages. Y Coordinate Values of the vertical locations of input point features or XY events. These values are implicit within geospatial point layers such as geodatabase feature classes, shapefiles, and coverages. A Line Top field containing one of the following* (see reference diagram below): o Elevations (typically above mean sea level) of the tops of the vertical line features to be depicted in the output cross section diagram. o Depths to the tops of the vertical line features to be depicted in the output cross section diagram. Note: Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables and within CrossViews dialog window. *Note: The Line Top field is not mandatory, but only if you choose to let these values be set by CrossView to the elevations of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab.
TM
A Line Bottom field containing one of the following* (see reference diagram above): o Elevations (typically above mean sea level) of the bottoms of the vertical line features to be depicted in the output cross section diagram. o Depths to the bottoms of the vertical line features to be depicted in the output cross section diagram. Note: Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables and within CrossViews dialog window. o The thickness of vertical line features to be depicted in the output cross section diagram Note: Vertical thickness values should be the difference between the top and bottom elevations / depths of the vertical line features to be depicted in the output diagram. *Note: The Line Bottom field is not mandatory, but only if you choose to enter a constant vertical thickness value interactively for all vertical line features to be depicted in the output diagram.
Beyond the required fields listed above, input point feature attribute tables or XY event layer source tables may contain as many descriptive attribute fields as needed. However, depending on the type of output format you are using with CrossView, you must adhere to field name restrictions discussed in the important note at the beginning of this attribute field section. VERY IMPORTANT: If a stacked sequence of vertical lines is desired, then the input point layer must contain multiple points at the same location (corresponding to multiple records in the feature attribute table). Similarly, XY event layer tables must also contain multiple records, one for each vertical line element in the stacked sequence of lines to be depicted in the output diagram.
TM
depicted on a cross section as either a single vertically oriented polygon column feature or multiple, vertically stacked polygon column features (e.g., soil bores, well screens)
Note: Input point layers can be geodatabase feature classes, shapefiles, or ArcInfo coverages. Alternatively, XY Event Layers containing appropriate, projected coordinates of point locations (XY events) can be used instead of geospatial point layers. In the illustration below, the Soil Bore datasets point features are depicted as stacked, vertically oriented polygon column features.
Attribute Format Information Each point feature in an input point layer corresponds to a single record in either a feature attribute table or an XY event layer source table. CrossView converts each input point feature / table record to a single vertically oriented polygon feature in the output cross section diagram. Each input point feature attribute table or XY event layer source table MUST contain the following pieces of information in unique fields: Important Notes Regarding Field Names: o Field names can be whatever the user would like, since CrossView works with any field name commonly acceptable within other applications. o Since CrossView can generate ESRI Shapefiles as its output (and these use dBase attribute tables with a field name limit of 10 characters), all input field names should be limited to 10
CrossView 1.1 User Guide (Revision 2)
TM
characters or less if you anticipate creating cross section shapefiles with CrossView. o Since CrossView can generate ESRI File Geodatabase feature classes as its output (and such geodatabases have reserved field names that cannot be used), all input field names must comply with these restrictions if you anticipate creating cross section file geodatabase feature classes with CrossView. X Coordinate Values of the horizontal locations of the input point features or XY events. These values are implicit within geospatial point layers such as geodatabase feature classes, shapefiles, and coverages. Y Coordinate Values of the vertical locations of the input point features or XY events. These values are implicit within geospatial point layers such as geodatabase feature classes, shapefiles, and coverages. A Polygon Top field containing one of the following* (see reference diagram below): o Elevations (typically above mean sea level) of the tops of the vertically oriented polygon column features to be depicted in the output cross section diagram. o Depths to the tops of the vertically oriented polygon column features to be depicted in the output cross section diagram. Note: Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables and within CrossViews dialog window. *Note: The Polygon Top field is not mandatory, but only if you choose to let these values be set by CrossView to the elevations of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab.
TM
A Polygon Bottom field containing one of the following* (see diagram above): o Elevations (typically above mean sea level) of the bottoms of the vertically oriented polygon column features to be depicted in the output cross section diagram. o Depths to the bottoms of the vertically oriented polygon column features to be depicted in the output cross section diagram Note: Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables and within CrossViews dialog window. o The thickness of the vertical line features to be depicted in the output cross section diagram Note: Vertical thickness values should be the difference between the top and bottom elevations / depths of the vertically oriented polygon column features to be depicted in the output diagram. *Note: The Polygon Bottom field is not mandatory, but only if you choose to enter a constant vertical thickness value interactively for all vertically oriented polygon column features to be depicted in the output diagram.
Beyond the required fields listed above, input point feature attribute tables or XY event layer source tables may contain as many descriptive attribute fields as needed. However, depending on the type of output format you are using with CrossView, you must adhere to field name restrictions discussed in the important note at the beginning of this attribute field section. VERY IMPORTANT: If a stacked sequence of vertically oriented polygon column features is desired, then the input point layer must contain multiple points (multiple records in the corresponding table) at the same location. Similarly, XY event layer tables must also contain multiple records, one for each vertically oriented polygon element in the stacked sequence of polygon columns to be depicted in the output diagram.
TM
depicted on a cross section as point features at a specified elevation or depth (e.g., soil or groundwater sample locations, soil property measurement locations, utility line locations)
Note: Input point layers can be geodatabase feature classes, shapefiles, or ArcInfo coverages. Alternatively, XY Event Layers containing appropriate, projected coordinates of point locations (XY events) can be used instead of geospatial point layers. In the illustration below, the Chemical ABCD Sample Concentrations datatsets point features are depicted as points at depth.
Attribute Format Information Each point feature in an input point layer corresponds to a single record in either a feature attribute table or an XY event layer source table. CrossView converts each input point feature / table record to a single point at depth feature in the output cross section diagram. Each input point feature attribute table or XY event layer source table MUST contain the following pieces of information in unique fields:
TM
Important Notes Regarding Field Names: o Field names can be whatever the user would like, since CrossView works with any field name commonly acceptable within other applications. o Since CrossView can generate ESRI Shapefiles as its output (and these use dBase attribute tables with a field name limit of 10 characters), all input field names should be limited to 10 characters or less if you anticipate creating cross section shapefiles with CrossView. o Since CrossView can generate ESRI File Geodatabase feature classes as its output (and such geodatabases have reserved field names that cannot be used), all input field names must comply with these restrictions if you anticipate creating cross section file geodatabase feature classes with CrossView. X Coordinate Values of the horizontal locations of the input point features or XY events. These values are implicit within geospatial point layers such as geodatabase feature classes, shapefiles, and coverages. Y Coordinate Values of the vertical locations of the input point features or XY events. These values are implicit within geospatial point layers such as geodatabase feature classes, shapefiles, and coverages. A Point Elevation / Depth field containing one of the following* (see reference diagram below): o Elevations (typically above mean sea level) of the point features to be depicted in the output cross section diagram. o Depths of the point features to be depicted in the output cross section diagram. Note: Depth values should be the depths below the surface elevation of the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. CrossView uses the elevations of this surface to locate and place all depth values specified in input source tables and within CrossViews dialog window. *Note: This field is not mandatory, but only if you choose to enter a constant point depth value interactively for all point features to be depicted in the
CrossView 1.1 User Guide (Revision 2)
TM
output diagram. The elevations of these point features at depth are determined using the user-specified depth value and elevations derived from the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. Beyond the required fields listed above, input point feature attribute tables or XY event layer source tables may contain as many descriptive attribute fields as needed. However, depending on the type of output format you are using with CrossView, you must adhere to field name restrictions discussed in the important note at the beginning of this attribute field section. VERY IMPORTANT: If a stacked sequence of vertically oriented point features is desired (e.g., point locations at increasing depths down a well casing or soil bore), then the input point layer must contain multiple points (multiple records in the corresponding table) at the same location. Similarly, XY event layer tables must also contain multiple records, one for each point at depth element in the stacked sequence of points to be depicted in the output diagram.
features that will be used to split and attribute output surface profile lines (for a selected surface dataset) on the resulting cross section diagram.
In essence, an overlay polygon layer is intersected with the planimetric line defining the course of the cross section in an overlay operation, and the result is output as a sequence of surface profile lines (depicting the selected surface dataset) on the output diagram. Furthermore, each surface profile line is attributed with field values from the overlay polygon layer. Note: Input overlay polygon layers can be geodatabase feature classes, shapefiles, or ArcInfo coverages. Important Notes Regarding Field Names: o Field names can be whatever the user would like, since CrossView works with any field name commonly acceptable within other applications. o Since CrossView can generate ESRI Shapefiles as its output (and these use dBase attribute tables with a field name limit of 10 characters), all input field names should be limited to 10 characters or less if you anticipate creating cross section shapefiles with CrossView. o Since CrossView can generate ESRI File Geodatabase feature classes as its output (and such geodatabases have reserved field names that cannot be used), all input field names must comply with these restrictions if you anticipate creating cross section file geodatabase feature classes with CrossView.
CrossView 1.1 User Guide (Revision 2)
TM
In the illustration below, the line representing the top (topographic) surface has been split and attributed with a polygonal layer of soil types.
TM
CrossView Glossary
TM
TM
Constants
When representing point data in CrossView, users are required to identify attribute fields that contain elevation, depth, and thickness values. Because some point attribute data may not contain this information, CrossView allows users to enter a constant value to take the place of an attributes values for all features in a point layer (e.g., all my points are 20 feet below the surface, so the Depth to Point Constant would be 20 feet). For additional information, please reference the Using the CrossView Dialog Window section of the CrossView User Guide.
a simple 2-point line connecting a beginning and ending vertex. The line can be crooked, containing as many intermediate vertices as needed, and can even contain curve and arc segments. For additional information, please reference the Required Preliminary Steps section of the CrossView User Guide.
Cross Section
As used within the context of CrossView, the term cross section (with or without the hyphen) is synonymous with the term profile, and dictionaries typically define them in very similar ways*. Generically, a profile or cross section is a section created by a plane cutting an object or solid perpendicular to an axis. In the earth sciences, these terms more specifically refer to a drawing that depicts a vertical section of the ground showing the varying slopes and elevations of surfaces intersected by the cross section plane. In other words, these are diagrams that show, by means of a side-view (or profile), the Earths surface, as well as subsurfaces, subsurface layers (soil, groundwater, geologic structure) and related features. CrossView simplifies the creation of cross section diagrams giving the user the ability to add and depict many surfaces and related features at depth, providing for a rich visual presentation of subsurface information. Cross section layers output by CrossView carry with them any descriptive attributes of input point layers or polygon overlay layers. This allows the user to customize the symbology of each layer in the output cross section diagram. For further information, please reference the Symbolizing Layers in the Cross Section Data Frame section of the CrossView User Guide. *Note: We realize that surveyors and engineers make a distinction between the terms profile and cross section, with the former referring to a vertical section of the ground surface taken parallel to (along) a survey line, and the latter referring to a vertical section of the ground surface taken at right angles to a survey line. Nevertheless, the fundamental concept of taking a vertical section of the ground surface along some specified line is shared by each, and so from an engineering or surveying perspective, CrossView can be used to develop profiles and cross sections.
TM
CrossView Dialog
After drawing or selecting a cross section line and clicking on the CrossView Dialog button (see screen capture at right), the CrossView Dialog Window is displayed (see the screenshot on the following page). This dialog allows users to select and enter information required to generate cross section diagrams. The CrossView Dialog window organizes the entry of information into four tabs: Surfaces; Points to Lines; Points to Polygons; and Points to Points. For additional information, please reference the Visual Overview of the CrossView Dialog Window Layout section of the CrossView User Guide.
Depth to Bottom
When representing point data in CrossView as vertical lines or polygons, users can select a Depth to Bottom field from the input point layers point attribute table to indicate the depth (from the surface) to the bottom of the vertical line or polygon feature that will depict each input point (e.g., well, well screen, bore segment) on the output cross section diagram. To assist users in selecting a Depth to Bottom field, CrossView provides a pull-down list of all numeric field names in the highlighted point datasets (feature attribute) table. In addition, the pullCrossView 1.1 User Guide (Revision 2)
TM
down list includes the -None- option. If appropriate, select the field name from the highlighted point datasets table that contains a depth value for the bottoms of features to be depicted in the output diagram. CrossView assumes that depths are measured from the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. If you specify a field name or value in ANY of the other fields that can indicate a depth to bottom value, then you must select the -None- option for the Depth to Bottom Field selection. For further information, please reference the Using the CrossView Dialog Window section of the CrossView User Guide.
Depth to Point
When representing point layers as points at depth, CrossView requires users to select a Depth to Point field input point layers point attribute table to indicate each points depth from the surface. To assist users in selecting a Depth to Bottom field, CrossView provides a pulldown list of all numeric field names in the highlighted point datasets (feature attribute) table. In addition, the pull-down list includes the -None- option. If appropriate, select the field name from the highlighted point datasets table that contains a depth value for each point feature at depth to be depicted in the output diagram. CrossView assumes that depths are measured from the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. If you are specifying a Point Elevation Field value or a Depth to Point Constant value, you must select the -None- option for the Depth to Point Field selection. For additional information, please reference the Using the CrossView Dialog Window Points to Points Tab section of the CrossView User Guide.
Depth to Top
When representing point data in CrossView as vertical lines or polygons, users can select a Depth to Top field from the input point layers point attribute table to indicate the depth (from the surface) to the top of the vertical line or polygon feature that will depict each input point (e.g., well, well screen, bore segment) on the output cross section diagram. To assist users in selecting a Depth to Top field, CrossView provides a pulldown list of all numeric field names in the highlighted point datasets (feature attribute) table. In addition, the pull-down list includes the
CrossView 1.1 User Guide (Revision 2)
TM
-None- option. If appropriate, select the field name from the highlighted point datasets table that contains a depth value for the tops of features to be depicted in the output diagram. CrossView assumes that depths are measured from the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. If you specify a Top Elevation Field value, you must select the -None- option for the Depth to Top Field selection. For additional information, please reference the Using the CrossView Dialog Window section of the CrossView User Guide.
Event Layers:
Planimetric
The term planimetric refers to a horizontal, two-dimensional interpretation of geospatial features (disregarding elevation or relief). CrossView requires as input, a planimetric line feature or graphic defining the course of the cross section. This cross section line does not need to be a simple 2-point line connecting a beginning and ending vertex. The line can be crooked, containing as many intermediate vertices as needed, and can even contain arc and curve segments. For additional information, please reference the Required Preliminary Steps Select the Line Defining the Course of the Cross section portion of the CrossView User Guide.
CrossView 1.1 User Guide (Revision 2)
TM
Points to Lines
CrossView allows you to select one or more point layers containing features to be depicted on your cross section diagram as vertical line features (e.g., wells, utility poles). For further information, please reference the Using the CrossView Dialog Window Points to Lines Tab section of the CrossView User Guide.
TM
Points to Points
CrossView allows you to select one or more point layers containing features to be depicted on your cross section diagram as point features at a specified elevation or depth (e.g., soil or groundwater sample locations, soil property measurement locations, utility line locations). For further information, please reference the Using the CrossView Dialog Window Points to Points Tab section of the CrossView User Guide.
Points to Polygons
CrossView allows you to select one or more point layers containing features to be depicted on your cross section diagram as either a single vertically oriented polygon column feature or multiple, vertically stacked polygon column features (e.g., soil bores, well screens). For further information, please reference the Using the CrossView Dialog Window Points to Polygons Tab section of the CrossView User Guide.
TM
Polygon Width
CrossView allows you to specify the widths of vertically oriented polygon column features depicted in your output cross section diagram. Specified widths are in the same units of measure (e.g., feet or meters) as those used for horizontal coordinates in the source MXDs data view. For additional information, please reference the Using the CrossView Dialog Window Points to Polygons Tab section of the CrossView User Guide.
Profile:
TM
Stacked Sequence
This term refers to the appearance of multiple, vertically oriented line segments or polygon column segments at a single location (see the soil bores in the screenshot at right as an example). To achieve a stacked sequence appearance, multiple records must exist for a single point location, one for each vertical line or polygon element in the stacked sequence of features to be depicted in the output diagram. For additional information, please reference the Data Requirements for Point Layers to be Represented as Vertical Lines section of the CrossView User Guide.
Surface
Within CrossView, a surface is any raster or triangulated irregular network dataset (recognized by ArcGIS as such) that represents a surface containing X,Y,Z locations in coordinate space. Appropriate surface datasets include: ESRI GRIDs (ESRI raster datasets): A GRID is a raster data storage format native to ESRI, and contains equally sized square cells that have attribute values representing X,Y,Z coordinates. ESRI TINs (Triangulated Irregular Network datasets): A TIN is a vector data structure that partitions geographic space into contiguous, non-overlapping triangles (facets). The vertices of each facet are sample data points with X,Y,Z values.
CrossView 1.1 User Guide (Revision 2)
TM
USGS DEMs (Digital Elevation Model files from the U.S. Geological Survey): A DEM is a raster data storage format used by the USGS, and contains equally sized square cells that have attribute values representing X,Y,Z coordinates. Other single-banded raster datasets that typically would be used to contain elevation data and are recognized by ArcGIS as single-banded image/raster files, e.g., ERDAS IMAGINE files (.img), TIFFs (.tif), PNG files (.png), and JPEG 2000 files (.jp2). CrossView requires that the source ArcMap document contain one or more appropriate surface datasets. For additional information, please reference the Data Requirements for Surface Datasets section of the CrossView User Guide.
Top Elevation
When representing point data in CrossView as vertical lines or polygons, users can select a Top Elevation field from the input point layers point attribute table to indicate the elevation of the top of the vertical line or polygon feature that will depict each input point (e.g., well, well screen, bore segment) on the output cross section diagram. To assist users in selecting a Top Elevation field, CrossView provides a pull-down list of all numeric field names in the highlighted point datasets (feature
CrossView 1.1 User Guide (Revision 2)
TM
attribute) table. In addition, the pull-down list includes the -None- option. If appropriate, select the field name from the highlighted point datasets table that contains an elevation value for the tops of features to be depicted in the output diagram. If you specify a field name in the Depth to Top field, then you must select the -None- option for the Top Elevation Field selection. For additional information, please reference the Using the CrossView Dialog Window section of the CrossView User Guide.
Top-Most Surface
This term refers to the surface layer listed at the top of the Surfaces to be represented in profile list on the Surfaces Tab. Under normal circumstances, this should be the highest (in elevation) surface layer to be depicted in the output cross section diagram. When representing point data in CrossView as vertical lines or polygons, users can select the -Top-most Surface- layer instead of selecting a field containing a Top Elevation or Depth to Top value from the input point layers point attribute table. If the top-most surface is selected, elevations of the tops of vertical lines or polygons default to the appropriate elevations of the top-most surface at each points location. For additional information, please reference the Using the CrossView Dialog Window section of the CrossView User Guide.
Update Extents
Once you have created an output cross section diagram using CrossView, the Cross Section data frames grid may be too large or small for your purposes. Using the Update Extents button on the CrossView toolbar in ArcMap, you can alter the grid extents (minimum x, maximum x, minimum y, and maximum y) of the cross section diagram. In the example at right, the Minimum X extent has been set to -250, the Maximum X extent has been set to 1000, the Minimum Y extent has been set to 5,100, and the Maximum Y extent has been set to 5,300. For additional information, please reference the Options section of the CrossView User Guide, as well as the Working with the Cross Section Data Frame section of the User Guide.
Vertical Exaggeration
Vertical exaggeration enlarges (or in rarer cases, reduces) Y axis units (elevation) relative to X axis units (linear distance along the planimetric line defining the course of the cross section). In essence, vertical exaggeration stretches (or more rarely, compresses) cross section diagrams, but ONLY along the Y (elevation) axis. The screen captures on the following page briefly illustrate the effects of vertical exaggeration. For additional information and discussion, please reference the Using the CrossView Dialog Window Options section of the CrossView User Guide.
CrossView 1.1 User Guide (Revision 2)
TM
Vertical Exaggeration of 0:
Vertical Exaggeration of 5:
Vertical Thickness
Vertical thickness is the distance between an alreadyestablished top elevation (or depth) to the actual bottom elevation (or depth) of a feature to be depicted as a vertical line or polygon in an output cross section diagram (see illustration at right). Vertical thickness values, in conjunction with top elevations (or depths) provide CrossView with all the top and bottom elevations needed to properly depict point layer features as vertical lines and polygons. When representing point data in CrossView as vertical lines or polygons, users can select a Vertical Thickness field from the input point layers point attribute table to indicate, in essence, the elevation of the bottom of the vertical line or polygon feature that will depict each input point (e.g., well, well screen, bore segment) on the output cross section diagram. To assist users in selecting a Vertical Thickness field,
CrossView 1.1 User Guide (Revision 2)
TM
CrossView provides a pull-down list of all numeric field names in the highlighted point datasets (feature attribute) table. In addition, the pull-down list includes the -None- option. If appropriate, select the field name from the highlighted point datasets table that contains a vertical thickness value for the features to be depicted in the output diagram. If you specify a field name in any of the other fields that specify the elevation or depth of the bottom of these features, then you must select the -None- option for the Vertical Thickness Field selection. CrossView also allows users to enter a vertical thickness constant value to be applied to all the features of a selected dataset. The vertical thickness constant, along with the Line or Polygon Top setting, is then used to determine the bottom elevation of each vertical line or polygon feature in the output diagram. For additional information, please reference the Points to be Represented as Linear Features section of the CrossView User Guide.
For additional information, please reference the Data Requirements for Point Layers to be Represented as Vertically Oriented Polygon Columns section of the CrossView User Guide.
XY Event Layers
XY Event Layers are data sources that contain location information in tabular form (called events) used to create a spatial dataset within ArcMap. XY Event layers originate as tables or formatted text files that contains x,y coordinate data for point locations. ArcMap reads the assigned x,y coordinate data and creates an event layer
CrossView 1.1 User Guide (Revision 2)
TM
rendered in the Data Frame. For additional information, please reference the Data Requirements for Point Layers to be Represented as Vertical Lines section of the CrossView User Guide.
Z Factor
The Z-Factor is used to adjust vertical and horizontal measurements so that they are in the same units of measure. In CrossView, the Z Factor field allows you to direct CrossView to convert the selected surface or point datasets elevation (z) values to a the same unit of measure (e.g., feet to meters) used for its horizontal coordinates. Zvalues in the selected dataset are multiplied by the Z Factor when calculating output cross section surface elevations. For example, if a surface's horizontal units are meters and its elevation (z) is measured in feet, the z-factor is 0.3048 (the number of meters in a foot). For additional information, please reference the Using the CrossView Dialog Window section of the CrossView User Guide.
TM