How to draw a dashed line on top of the water level symbol?

Hello,

I was wondering if anyone knows if is possible to draw a dashed line automatically at the water table symbol in a boring log. Refer to file attached.

Thanks.PDF

Parents
  • Hi Pelelo,

    There are probably a few ways you could do this. 

    1 option is to use a lines vs depth entity in report design. It is a little more complicated if you are using a Smart report vs a static report.

    for a static report use just use a column width to match the width of the line for a smart report you will need an expression to have the line expand as needed and also an offset x to adjust if it need to move left or right.

    In the depth expression just use the appropriate one for what you want to show. As an example if this is a standard file set and you want at time of drilling then use the standard ATD depth expression . For a fixed line type just use the line type number (IE 1 is dash)

    one thing to keep in mind this is a separate entity and it knows nothing about the text in the description entity so there are probably many scenarios where the line will run right through the text. It is not like a boundary line that is part of the description column properties that will bend(ie boundary line usually will show lithology bottom In the Description column).

    And yes technically you could create a second text vs depth entity with all of the same properties and use the boundary line for water depth expression to get it to bend , but you may get something like this. So as you can see there are options, but not sure if this is a good way to show water level where you are running it across a column that typically has lots of text.

    I would also recommend you create a copy of the report to edit. To do that pick the report in report design ..goto file..copy page . Make a copy and edit the copy, leaving the original as is until you decide you want to make it a permanent change.

    So I've done it both ways here. In the separate lines vs depth where it goes thru text I have set the print order below the text and colored it a lighter color.

  • Thanks a lot Kirk.

    I tried Lines Vs Depth properties and in the column width expression i entered a typical column width expression from other entities (Description).

    About the depth, I used the EOD water depth.

    Still, it is only shown the Water table symbol instead of the line as you showed. Refer to the file attached.

    Thanks.PDF

  • Thanks szang,

    Something I realized is that "Lines Vs  Depth Properties" Entity is not doing anything at all in the boring log. See file attached.

    In fact, I have not even found what is the entity that controls the WL symbol which clearly is working properly.

    I did follow your directions however, the fact that entity is not working in my boring log means anything that i edit of that entity will not work.

    I deleted that entity and still the water symbol is plotting properly. Clearly, this entity is completely independent from the WL symbol. I thought somehow they were supposed to be linked.  

     PDF

  • The water level symbol is plotted by the discrete graphic vs depth entity located just to the left of your description entity in your log. It will be completely independent from the line that you are trying to create as explained by Kirk above. It appears from your pictures that your log is set up as a smart log which means that the column widths and positions change depending on the type of data you are trying to plot.  It is very hard for me to know all the details of your particular setup but for the specific log you showed, try the following.

    1. Set the x coordinate of the line vs depth entity to 3.5. This should start the line at the left edge of your description column and the right edge of the water level symbol being plotted by the discrete graphic vs depth entity. The Y coordinate of 4.5 seems to be ok and keeps the entity out of the way of the rest of the entities in the log.  The Y coordinate only impacts where the entity appears during report design and does not impact the actual plotting depth.

    2. set the column width expression to 4. This will draw the line from x=3.5 to the right edge of the log at x=7.5.

    3. start by setting the depth expression to  5.  This will draw one line at a depth of 5 regardless of what the actual water depth is.  Once you confirm that this works you can put the actual data field back in and it should pick up the depths from there.

    4. in the configuration tab of the entity, make sure the output condition is empty (this will make it so the line always outputs) and the output override x is empty (this will make it so the line always starts at x=3.5)

    5. I like to change the color of the line (say to light red) and make it thicker (say 0.02) so that when I preview the log it stands out while I am debugging the entity. Once you get it working right you can set it to the desired values.

    The above should draw a dashed line across the log at a depth of 5 from an x coordinate of 3.5 to an x coordinate of 7.5.  Once you confirm that this works you can get fancier with the column width expression, output override x and output condition to make it work with the smart features of your log..

  • Thanks szang,

    I tried to follow your steps, but by the time I create the logs, still nothing new shows up. Instead of setting the depth at 5 ft, i did it at 6 ft, to avoid confusions as there is a soil division (a new layer starts at 5 ft). See below. It looks to me that entity is not working at all.

    Also from Kirk's email, I noticed that in the table section, I have an "Approved By" whereas Kirk has "Project". I don't know if this affects the entity.

    PDF

  • I note that in the configuration tab of the line vs depth entity you have the In private block property set to "well".  Since this log has no well associated with it I suspect that the entire block is set not to print.  change this value to "none" to make the line entity part of the base log and always print for now. again this is something you may want to refine to get it to work with your smart log..

    Do not worry about the differences between your choices in the field drop down selector vs Kirk's. he is using a different data structure and will have different fields available for use.

Reply Children
No Data