graphic column to show CPT data as colours based on a threshold

Question

I have CPT type data in a "double" type field and want to plot it on fence graphic column as colours based on a defined trigger value like "if the value is <1 then orange, else green"

I have put the condition:

<<Case(_
<<SCPP_BNI2014.FS>>,_
< 1,Medium Orange,_
Else,Light Green_
)>>

in the config - section color expression on the graphic column and set all override colours to none, lines to white and the main fill type symbol to solid.

whatever I change I get solid black sticks on the fence. I've also tried to use the expression in the background fill tab instead, but same issue.

both Medium Orange and Light Green are named colours on the symbol design tab.

I guess this is possible, as a similar feature would be used for contamination test or monitoring results where a threshold is set and either exceeded or not.

Kirk Johnson · Answer

Hi The colors in gINT are actually stored as a number. You can find the number in Symbol Design ...colors. it is easiest to just reference the Number in your expressions In the expression use the number Here is help file topic in gINT goto Help look up this guide and the are additional links and topics. Assigning Background Fills (how-to guide) The Background Fill tab appears in the following entity types: Polyline Graphic Column Column - Graphic Column Column - Bar Charts vs Depth Bar Charts vs Depth This tab has all the same properties as the fill specification on the Configuration or Data Representation tabs. That is, all have the following: Output Condition Fill Type[!Symbol] Fill Scale Override Fill Color Fill Rot'n (Hatches only) All the entities listed above, except for Polylines, also have: Section Color Expression The background fill is a fill pattern that is laid down before the fill specified with the Fill Type[!Symbol] property of these entities. It has two uses: Laying down a background color using a Solid fill. Specifying an overlay fill. The latter usage could be done without the background fill capability by just specifying two graphic columns to print in the same area but taking their fills from two places. The former cannot be reliably done this way since you cannot control which of the two fills will print first. If the solid fill prints first it will cover the main pattern. In both cases, the background fill is a better choice simply because it means fewer entities to deal with, thereby making construction, maintenance, and, to a minor extent, the output speed, better. The properties on the Background Fill tab allow you to set background fills and colors that can be hardcoded (specific colors or fills) or can be variable with expressions. Not only can the fill and color be variable, but you can apply an Output Condition that will govern when the fill is output. Background Color Example with Graphic Column: You wish to print your material graphics column with colored backgrounds indicating the geologic unit. We will use the UK AGS database structure for this example. It is easily changed to match whatever structure you may be using. The GEOL table (captioned "Strata Main" in the gINT database) uses the GEOL_LEG field for the main fill for graphic columns. There is also a GEOL_GEOL field which generally stores the geologic unit associated with each stratum. That field has a library table lookup called AGS_GEOLOGIC_CODE. You would add "Colour" field (since this is a UK standard we will use the UK spelling) to the AGS_GEOLOGIC_CODE library table and populate it with the colors you wish to associate with each geologic unit. The Graphic Column properties would be as follows: Main: Fill Type[!Symbol]: Matl!<> Background Fill: Fill Type[!Symbol]: <>,<>)>>,Solid)>> Section Color Expression: <>,<>)>> The background fill is Solid only if there is an associated color. Without this condition, geologic units to which you did not assign colors would have a solid fill with no override color, that is, black, and you would not see the main fill. Background Color Examples with Bar Chart or Column - Bar Chart entities: You are plotting some chemical results and want to have a black fill if the value of the chemical is below some safe limit, blue if the value is above the safe limit but below some critical value, and red if the value is above the critical value. The "Section Color Expression" property would read something like the following: <>,_ < 100,0,_ < 500,16711680,_ Else,255_ )>> See the Colors application for the color numbers that need to be used. You are plotting percent gravel, sand, silt, and clay as bar charts. The foreground Fill Type[!Symbol] property is set to one that is appropriate to the fraction being plotted, the background Fill Type[!Symbol] is set to Solid , and the Override Fill Color is set to some color that is appropriate to the fraction (for example, very light yellow for sand). See the Particle Size Data Represented as Bars topic in Help for further details on how to do this. Specifying an Overlay Fill: Instead of creating combination material symbols such as "CL-ML", "SP-SC", "GP-GM", you could just have the individual symbols ("CL", "ML", etc.) and specify the mix at input time. This would reduce your symbol list but takes away your ability to make the combination different than just the combination of the two patterns. If you choose to do this, there are two methods: A. Single symbol field: You would keep just one field for the material graphic and it would be a lookup in the material symbols but you not make it a Must use lookup , that is, the user could select from the list or type something else. So if you wanted a dual symbol, you would type "XX- YY", for example, "CL-ML" would say to overlay the CL and ML symbols. Using our usual, non-AGS table and field names, the graphic column properties would be: Main: Fill Type[!Symbol]: Matl!<>,-,1)>> Background Fill: Fill Type[!Symbol]: Matl!<>,-,2)>> That is, the main fill will be the name left of the "-", if there is one, otherwise it will be the entire name. The background fill would be the name right of "-", if there is one, otherwise nothing. The disadvantage to this technique is that you lose the control that a Must use lookup provides and the user could inadvertently type the wrong name. B. Two symbol fields: In this scenario you would have a second field, let's call it "Graphic2". It would be a Must use lookup field into the material symbol list just like the "Graphic" field usually is. The Graphic Column properties would then be: Main: Fill Type[!Symbol]: Matl!<> Background Fill: Fill Type[!Symbol]: Matl!<>