Patrick Spurgeon wrote:
I need to show details above ground surface for the well diagram. The well that I am trying to represent has a riser that sticks up 3 feet above ground surface (ags) and the protective casing sticks up an additional 0.5 feet.
Despite my attempts to enter negative numbers in the well construction depth field, I am unable to get the preview to show the -3.5 feet (it would help if the depth column also could go negative).
I also need to show a well within a well. The first 20 feet were drilled with a 10-inch bit, then a 6-inch protective casing was inserted within the 10-inch hole, then the following 150 feet were drilled with a 6-inch bit, and finally a 2-inch riser was placed within all of this.
I have figured out how to show 2 pipes per well, but I cannot figure out how to show a pipe-within-a-pipe. Nor have I figured out how to show annular space with varying widths.
My Reply:
Patrick, the depth column can actually go negative. There is a property of a report that allows you to pick a particular piece of depth data and use it as the start-point of the log, instead of the default zero depth.
In the REPORT DESIGN application, pick your log report, and click its Properties icon to open the Properties dialog. Next, open the Report Structure tab, and enter an expression in the Top Depth Expression property. For your purpose, this would likely be the minimum well construction depth, which would then be negative if there is a riser on the well. If you are using the gint std ags3_1 or gint std ags4 dataset, this expression will not be able to reference the BACKFILL Depth value, which I believe is constrained to be 0 or greater. In that case, you might have an additional field in either BACKFILL or PIPE to account for the negative depth.
I hope you will also get a reply from one of the AGS experts. Dave Kyllonen, for example, may be able to help you work around the limit for the backfill to zero depth or greater.
Pipe-within-pipe is a symbol design issue, most likely. Please take a look at the symbol CMNT11 - notice how the pipe verticals are specified? You may be able to use this technique to create the symbol that will represent the internal riser within the 6-inch casing, and a second graphic to display the narrower pipe below that point.
Regarding showing a pipe-within-a-pipe for a well symbol there are several ways to accomplish this. The simplest is to create some new well symbols. For example, the following values will provide one method;
Create a new Well Composite Symbol (such as 6-inch Casing).
Fill Type: Tile!linedsh17
From%: 0
To%: 35
Vertical Borders: Right
From%: 65
To%: 100
Vertical Borders: Left
Fill Type: Solid
From%: 16
To%: 18
Vertical Borders: empty
From%: 82
To%: 84
You can replace the Linedsh17 tile used if you a different tile for your grout.
You can adjust the values for the From and To properties to "play" with the horizontal placement of the casing within the hole. Note that you will want a range of 2 or 3 percent to get a noticeable line representing the conductor casing (your pipe-within-a-pipe).
By using the above technique you can include a third casing if necessary. You will have to experiment with the values for the From and To properties to get it to look acceptable to you.
As Pat indicated, if you are working with the gINT AGS database structure you will not be allowed to enter negative depths in the Backfill table. The can be changed, but then you will not be in compliance with the AGS standard so that when you export data from your gINT database to an AGS file you will have data that will not get exported property. But, based on your statement that you have entered negative numbers in the "well construction depth field" it appears that you might not be using a gINT AGS database structure so you can enter negative depths in Input and have the well graphics print on your log "above ground". You will not get the depth scale to print negative numbers however, the program does not support this.
Here is a note from the gINT Help file regarding what you are trying to accomplish:
1) A special case with Logs and Fences: Negative Depths
The main purpose of this capability is to accommodate above-ground well details. To show well details on a report you use Graphic Column, Text vs Depth, and Vertical Line to Depth entities.
Be a bit careful on using this capability. You need to limit how high the graphic, text, or line will print.
For example, you might specify a well graphic that shows a protective casing to go from -3 to 0 feet since the case protruded 3 feet above the ground surface. If your vertical scale is 2 feet per inch the graphic would stick up 1.5 inches above the zero depth line. If you only have 1 inch of space allotted in the column header area, the top of the graphic would overwrite the page header. To handle this situation, write your depth expressions like the following:
<<MaxVal(<<TABLE.Depth>>,<<Calc(-1 * <<LogVS>>)>>)>>
that is, the program will calculate how many feet are represented by 1 inch (the space you've allotted) and make it negative. The MaxVal will take the maximum of the depth specified in Input (<<TABLE.Field>>) and the allotted amount. Change the <<TABLE.Field>> to whatever is appropriate in your database (<<WELL.Depth>>, <<WELL Construction.Depth>>, etc.) and the "1" to the number of inches or millimeters you have allotted in the column header.
One more thing, you indicated that you are unable to get the preview to show negative depths. It sounds like you can enter the negative values but nothing is getting printed above ground, is that correct?
How current is your copy of gINT? Select About gINT from the gINT Help menu.
Older versions of gINT did not support printing graphics above ground if that meant that the graphics were printed above the report body (into the column header space).
I don't recall when this changed, but it was a few years ago.
The way I handle this is as follows. Note that this is just one way and there are other approaches that might work better for you.
My well table includes only 4 fields, depth, bottom depth, well graphic, and well notes (not a standard ags or gINT table)
I have created a series of well graphics that include Pipe within a pipe, cap within a pipe, just a large pipe, etc. There is one for each different type of backfill so I have pipe within pipe with concrete backfill, pipe within pipe with sand backfill, etc. The symbols include a vertical line at each edge that represents the hole and a partial line at the top that serves as a divider between it and the next symbol. Thus as you go down the hole you simply select the appropriate well graphic at each depth where anything changes (pipe or backfill) on the cross section of the well installation. Since this approach results in about 120 different well symbols, I have adopted a naming convention for the well graphics that forms the name as a combination of the backfill type and pipe type to make it easy to locate the correct graphic in the list of well graphics (For example "SAND SCREEN". I also have a series of "NOHOLE" well graphics that have no backfill symbol, no vertical lines that represent the hole and no divider lines for use in cases where you are at negative depths (above ground). I also have a "VOID NOPIPE" symbol that has just lines representing the edge of the hole for cases when the top of the well is recessed below the ground surface. Note that the symbols are designed so that they match up with each other...In other words, the riser pipe of my "RISER" symbol is the same style and width as the inner pipe in my "CASING+RISER" symbol. Thus these work no matter what width you specify the well column to be in the final report because the width of the pipe in the well graphic symbol is specified as a percentage of the overall column width. They also work well on fence reports since the edge of the hole is included in the graphic.
As Pat has indicated I have set the top depth expression property in my well log report to:
<<MinVal(<<Int(<<Calc(<<Min(<<WELL.Depth>>)>>-0.999)>>)>>,0)>>
The integer function makes it always start at an even number, the min function pulls the smallest (largest negative) value from my well installation table and subtracts just less than one foot from it (this makes sure there is always some space left above the top of the well in the report), and the minval function makes sure the starting depth is never greater than zero (shouldn't really be necessary but included if for some odd reason you did not start your well installation graphics at zero depth)
This constructs the well diagram entirely within the body of the report with nothing sticking up above the body to interfere with the header. Note that this approach does not scale the pipe diameters relative to the hole. Rather, it presents them in a readable graphic sketch with the diameters indicated by notes. An example of the results is shown below. The data that drives this example would be something like:
Hope this helps.
Patrick, if the example that Szang provided is what you are looking for then the method described by both Pat & Szang is what you want.
Note that you can add a Lines vs Depth entity in the "Depth/Elev" and "Details" columns with a hard-coded depth value of 0 (zero) to help the reader see where the "ground surface" is.
On the other hand, you can get well graphics to print above the top of the report log body by using negative depths, which is what I was talking about. But, as I indicated, you will not be able to get the depth scale to print negative numbers above the top of the report log body.