Doug Gallup

GMS Development Team
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About Doug Gallup

  • Rank
    GMS Developer
  • Birthday

Contact Methods

  • ICQ
  1. Try following the suggestions here, or contact technical support with your data and the steps you took to duplicate the problem.
  2. In addition, try turning on "Overwrite the outputs of geoprocessing options" in the Geoprocessing, Geoprocessing Options... menu item, if it's already off.
  3. I would suggest contacting Tech Support and sending them your files. The wizard probably isn't completing for some reason. To view your results, make a new data frame (ArcMap: Insert menu, Data Frame), then add just the XS2D_Panel_23 and XS2D_Boreline_23 feature classes.
  4. Check the "Default output workspace" on Step 1 of the wizard. This should be by default the same workspace as the SectionLine4. I would suggest moving your SectionLine and Well features into a new feature dataset, with a projected coordinate system. This way, you'll ensure that the output XS2D feature classes have the same projected coordinate system. After creating the XS2D Boreline feature class, the wizard will try and read the Well and Borehole Log data, if that option is turned on. It's the "Yes" or "No" radio button on Step 1. If it's turned on, it will try and create the XS2D Boreline features. Were any features created in XS2D_Boreline_23? Because these XS2D features are two dimensional features representing 3D data, they won't show up next to your well data. They should be displayed in their own data frame inside ArcMap, so that the X dimension in ArcMap is really the distance along the SectionLine feature, and the Y dimension in ArcMap is the vertical profile scaled by the vertical exaggeration. So, on the XS2D panel, X=0 where the SectionLine starts. It doesn't make sense to view them in ArcScene. ArcMap is used for viewing in plan view, but the XS2D data is just a way to view a cross section profile. The data has just been transformed so you can view it in ArcMap. When finished, you can convert the XS2D data to true 3D objects (see the GeoSection tutorial) if you wish. After the XS2D Boreline features are created (if you've turned this option on), it tries to create the XS2D panel dividers, and then it tries to create all the grid lines based on Step 3 of the wizard. I'd try making a new feature dataset with a projected coordinate system, and placing your SectionLine and Well features inside of that, and then try running the wizard again. When you run the wizard, just leave the default options for the output workspace, keeping it so that it's the same feature dataset as your SectionLine and Well. You could also check the "Results" window to see if there were any problems running some of the geoprocessing tools. What was the last tool run, and were there any errors reported?
  5. The wizard wants a visible polyline feature class loaded in the active map, with some of the default Arc Hydro Groundwater field names & types, and a projected coordinate system. Make sure that you're not in an XS2D data frame when you try to use this tool, and that the SectionLine layer is turned on (visible) in the table of contents. Also, check if your coordinate system is geographic or projected. Finally, from your screenshot, I can't tell what the actual field names are because it looks like the Alias names are being shown instead ("Vertical Exaggeration" is an alias). The wizard is looking for the following fields, please double check them by right clicking on your SectionLine layer in the Table of Contents, and choosing Properties, and looking on the Fields tab: HydroID (integer) SName (string) VertExag2D (double)
  6. When you originally created your data, you probably used one of the wizards for creating the cross section and geophysical data. These wizards basically run the geoprocessing tools mentioned above, without you having to worry about all of the inputs. They first create all of the necessary Data Frames, XS2D feature classes, etc. before creating the new features. You won't be able to use the wizards to add to existing data, and you might have to play with the "Plot Options" category for adding geophysical log plots to make them look like the existing data (same size, layout, position, etc.) You could use the wizards to totally generate the data again from scratch, but this will not keep any additional edits you've made in the meantime, like adding XS2D Panels, for example. However, if you're saving the geoprocessing history with your Arc Map document, you could simply use the geoprocessing tools with the same inputs and settings to your advantage. For example, the wizard to build geophysical plot features calls the "Create XS2D Geophysical Plot Features" tool. If you look in your history, you should see it there after running the wizard (if your Geoprocessing Options in Arc Map are set up to save it in your history). If it is in your history, and you want to use the same plot options (size, positioning, etc.), just select the new Well features with geophysical plot data that you want to add, the open the "Create XS2D Geophysical Plot Features" tool from your geoprocessing Results tab, and review all the information there before running your tool. Just be sure that your "Append" option for the tool is turned on.
  7. For adding geophysical log plots to existing plots, you can do basically the same thing with the "Create XS2D Geophysical Plot Features" tool. See the "Adding Borehole Log Plots to Cross Sections" tutorial for more info. Add new Well features if necessary. You don't need to do this if you are adding a geophysical log for a Well you just created (like above) or for a Well that already exists in your data. Add new data fore this borehole to your table containing your geophysical log information. In the tutorial referenced above, the table is called LogData. All you need here is to enter the WellID, Depth, LogValue, and FType. WellID should match the HydroID value of the matching Well feature. Depth is the depth of the reading. LogValue is the value of the reading. FType is a description of the type of data (ex: gamma) Finally, in your Data Frame with your Well features, select the Well feature(s) with the new geophysical log data you wish to plot. Open the "Create XS2D Geophysical Plot Features" tool. Enter all of the information necessary to run the tool. Make sure the "Append Features to Feature Classes" toggle is turned ON. Be sure to expand the "Plot Options" category at the bottom. You will have to play with these values in order to plot the data to the size, position, etc. that you want.
  8. I would take a look at the "Advanced Cross Section Editing" tutorial at Assuming you've already generated an XS2D cross section for a particular SectionLine, and you want to add to it: First off, I would add a new point to the Well feature class at the location of your new borehole. Make sure it has a unique HydroID value. This is done in your plan view data frame, not XS2D cross section. Then, add your borehole information to the BoreholeLog table. There should be one row for each hydrogeologic unit. The WellID attribute for the new BoreholeLog rows should have the same value as the HydroID for the new well you created. For the BoreholeLog table, make sure the HGUID, TopElev and BottomElev fields are filled out. So, for example, Well has a new feature point, with a HydroID of 1234567 (or some other unique value). The BoreholeLog table will then have multiple new rows for each hydrogeologic unit in the borehole, with the WellID value being 1234567 (or whatever you used for HydroID on Well), and the top and bottom elevations and HGUID fields populated. Now, make sure you're in the Arc Map Data Frame with your Well features, SectionLine features, and BoreholeLog table. You want this Data Frame to be active, not the one for your XS2D cross section. Select the SectionLine you're adding to, along with the new Well feature you just created. ***** This is vital to adding to an existing cross section ***** The tool will work off selected well features, so if you're adding one or more wells/boreholes, then you want to select just the ones you want to add. Open the "Create XS2D Boreholes" tool (in the Subsurface Analyst, XS2D Editor toolset). Choose the appropriate Section Line layer, and enter the appropriate HydroID value for the SectionLine you're adding to (the Identify tool works great for this). Choose the same XS2D_Catalog table that you used before (you're probably only using 1, and the default name will be XS2D_Catalog). Choose the appropriate Well feature class, where you added the new well and assigned a unique HydroID value. Choose the appropriate Well HydroID field (it's optional, but in this case, where you're adding to an existing cross section, you'll want to use it). Choose the appropriate BoreholeLog table, and its WellID field. Choose the XS2D Boreline layer you want to add to. By default, it will be named XS2D_Boreline_.... with the HydroID of the original SectionLine in the name. For example, XS2D_Boreline_6475. You can just go to your XS2D cross section data frame, and look for the name there. Finally, make sure the "Overwrite" toggle is not checked. We want to append to the XS2D boreline layer, not overwrite everything in it. Once you run the "Create XS2D Boreholes" tool, you should see the new XS2D Boreline features appear in your XS2D cross section (you probably have to activate its Data Frame to see it). At this point, you'll probably have to update your XS2D Panel features to reflect the new borehole. See section 8 in "Advanced Cross Section Editing" tutorial on how to do this. This is simply using the ESRI tools to create or edit polygons.
  9. I don't think there's a way to georeference a jpg image in ArcScene. You can certainly do that in ArcMap ( but that's only in X, Y. As you mentioned, you can display them in the XS2D space (using ArcMap to display a single cross section), but as far as I know, not in ArcScene. See the "Adding Images to Cross Sections" tutorial on the AHGW Learning Center (
  10. The Time Series Grapher and its Setup are not geoprocessing tools. They are custom commands and tools for the Arc Map interface.
  11. Check the Groundwater Analyst toolset in the Arc Hydro Groundwater Tools toolbox. If you can't find the toolbox in your "System Toolboxes" area in Arc Toolbox, browse to your AHGW install area and look for it there. Create Blank AHGW Geodatabase is available to anyone who has installed AHGW.
  12. GMS will directly export data to Arc Hydro Groundwater: GMS borehole data is exported to Arc Hydro Groundwater BoreLine features. GMS hydrostratigraphy (solids and borehole cross sections) data is exported to GeoVolume and GeoSection features. GMS isosurfaces are also exported. If you have a MODFLOW model saved, you can import that into Arc Hydro Groundwater using tools built into MODFLOW Analyst. These tools will rebuild the model inside of ArcGIS. For more information on importing a MODFLOW model into Arc Hydro Groundwater, see the tutorials for MODFLOW Analyst here:
  13. I would suggest going through the ArcGIS examples and tutorials for animations, as what you're asking isn't specific to Arc Hydro Groundwater. Other things to explore would be creating a time animation (if appropriate) or exporting your data for a single attribute into a new layer (for example, having one borepoint layer for horizon ID 7, another for horizon ID 6, etc.)
  14. For more information on the warning you mentioned, see this link: "This is a warning; no change is necessary." Check either the Scene Properties (ArcScene: View, Scene Properties...), or Data Frame Properties (ArcMap: View, Data Frame Properties...) depending on which application you're running. This will show the scene or data frame's spatial reference being displayed. This may differ than some of the layers being displayed in the scene/map, which is always projected on the fly. In the data associated with the GeoSection to Points tutorial, you'll find a mix of NAD83 / Massachusetts Mainland [ft] and GRS_1980_Lambert_Conformal_Conic.
  15. The message about the map and output is probably happening because the display projection and units in the map's data frame differ from the data being used.