i.e. Sandy Silt and not any additions like -moist,dense,etc even though it's in the lithology description.
Hoping to have the layout like this.
You need to have separate fields in your Lithology table and and then write your Text vs Depth expression using the field you made with soil classification.
See my Lithology below:
For my setup, the Text vs Depth expression would be <<FirstData(<<Lithology.soilClass>>,<<Lithology.RockClass>>)>> to pull in LEAN CLAY at 0.3 feet, SILTY SAND at 3.0 feet, and Schist at 11 feet.
Thanks Allan.
That helps.
One question out of the initial discussion. Does the color field determine the color of your fence hatch graphics?
You could possibly tie the color to the included gINT colors but it'd require some finesse. ;)
I print in black and white and I rarely print from gINT to pdf. I usually export the graphics to DGN and bring them into Microstation to add strata lines, groundwater, existing grade, proposed grade, etc.
Hi Mark,
Here are a couple of guides about the topics you are discussing (using a component model for lithology descriptions and coloring symbols from an input field, or coloring the symbols themselves)
If you would like to email me privately I would be happy to call and help modify your customized gINT files. Just click on my name and send me a message.
Also How to guide in gINT.... goto Help ...Search Assigning Colors to Graphic Column Sections (how-to guide)
You can do this using the current description field as is; provided ALL descriptions are entered using uniform formatting. In the example you provided above, you could search the text string for the position of the first and second bolding marks, then extract the text between them for display on your column. This only works if you always bold the text you want on your column or use some other uniform way (such as all text before the first period) to determine the text to extract. Anything else can be extracted from a long description as well. For example, you could extract the color to control the color of your graphics if it is ALLWAYS the word between the second and third comma. If you are hand entering your descriptions, the probability of a description being written in a different order or using different punctuation/ formatting is high. A component description model using pick lists for each component reduces this probability. I do not have a computer with gINT available right now but if you want help writing a function to extract the desired text, let me know and I will provide more insight mid next week.