Create Legend using gINT Logs.

If you are using the  gint std us library there is already a graphic text document created called KEY TO SYMBOLS.  Outputting this report may provide what you are looking for.  Not sure if gINT logs is allowed to output graphic text documents though.

I can think of 4 ways to create a legend using only a log report form. Since You want a variable legend I will present two options for that first and then mention 2 ways to create a fixed legend.  Note that these examples were developed in gINT professional but I have tried to use only options that are available in gINT logs,  Since I do not have gINT logs you may find some differences or some of the options may not be available. The examples are based on the "gint std us" data structure and library, Your data structure and library may vary.

Option 1 - data driven log legend

This is a quasi variable legend in that it relies on you creating a "LEGEND" Borehole that then gets printed with a special log form to create the legend.  Example output is shown below.

The report design consists of a log with minimal header and footers, and 6 body entities.  In developing the report I used individual entities rather than column entities because I had no use for column lines or headers.  You could also use column entities if you want.  The report design is shown below.

There are 3 graphics vs depth entities and three text vs depth entities.  The graphic vs depth entity is driven from the data table to create individual symbols of the soil, samlpers and well.  The configuration of the first one (soil and rock symbols} is shown in the picture below:

The data table that drives this is shown below:

This is made by creating a special boring called LEGEND in each project and then populating the Lithology Table with all the unique symbols in the project and assigning each a top depth depth bottom depth and description.  It is relatively easy to create this data by exporting the entire lithology table to excel (select view entire table in input then export to excel) once the table is in excel use excel to remove duplicate symbols and write some simple formulas to create sequential top and bottom depths at regular intervals as shown.  You then have to manually enter a description for each symbol and paste it back into gINT. There is a separate text vs depth entity to the right of each symbol column in the report that is set to print the description.  It is set up similar to the graphic vs depth entity but ids driven off the description field in the lithology table. This is repeated for the sampler symbols and well symbols. To output, simply select this report and the LEGEND boring as the boring to output.

The advantage of this method is that if there are more symbols than will fit on a page it will generate more pages.  You can also easily control the order of the symbols and add more symbols than are in the project or separate symbols by spaces or subheadings (such as rock symbols and soil symbols). You can generate a nice custom legend this way but you have to manually create the data that drives it.  As described, this can be greatly simplified by using excel to extract all relevant symbols and generate even depth intervals.

Option 2 - True variable legend

This uses gINT's variable legend on a log form.  It is a bit of a stretch because it was not designed to do this but here is an example output

The log form properties are contorted to provide a first page with no body and a second page body height of 1 inch (the minimum). The report properties are shown in the picture below.

The problem with using a log report this way is that it has to have a body and it has to have at least 1 piece of data to plot in that body.  We get around that by pushing the body to the second page and giving it an invisible piece of data to plot.  Of course this forces it to generate 2 pages but you only want the first one.  The report design is shown in the picture below:

Note I have inserted 3 variable legend entities in the header space of the first page for soil symbols, sampler symbols, and well symbols.  I have also added a body entity in the bottom center of the report design that is a simple graphic vs depth entity (see picture below). the properties are set to print a solid white block between 0 and 1 foot and the  print order is set to -1 so it will be below the rest of the data.

Typical variable legend properties are shown in the picture below

The variable legend is set to draw data from the entire project so it does the work of sorting through your borings and finding what symbols you used

To output this legend you will have to select a a boring (it does not matter which one because the report does not use any actual data).  It will generate 2 pages of the same thing but you only want the first one. If you don't want to waste paper you can generate a preview and then just print the first page. you can also choose what pages to print if you export to pdf. You could probably get rid of the 2 pages by simply specifying the first page to have a 1 inch high body.  This will place the solid white box on the first page as an object but you will never see it unless you edit the output in a pdf editor or cad. I did not try this in my example but is probably worth looking into.

This report requires less work to generate a legend for the project because you don't have to create a Legend boring.  Drawbacks are that it is limited to a single page and in order to control the order and descriptions of the symbols you have to carefully build the symbol library.  Not sure what gINT logs allows in terms of editing the symbol libraries and tables.

Option 3 - Fixed graphic symbols

This is a fixed legend so explanation will be brief.  The report structure is set up similar to the option 2 above.  Instead if variable legend entities you construct the legend using individual graphic symbols and text elements.  Quite tedious but it can generate a very nice looking legend. I use this option on many of my legends as it gives me more flexibility  with formatting of legend entries.

Option 4 - Bit map image legend

This is set up similar to option 2 above and is also a fixed legend. The only entity in the header is a bitmap image that covers the entire page.  I create the bit map image in other software (I use powerpoint) and then insert it into the log.  This gives me lots of flexibility with respect to layout and formatting and is much easier (for me at least) to edit than dealing with all the entities in a gINT log form.  If I need the make a change I simply edit the powerpoint, export a high res bitmap (300 dpi) and reinsert it in the legend report. Drawbacks of this method are that it increases your library size (it has to store the bitmap) and increases output time by a second or 2.

Hope this helps, Some of my descriptions may not be all that clear but it should give you some ideas on which way you want to go.  I can provide more details on specific issues if you want.

I can think of 4 ways to create a legend using only a log report form. Since You want a variable legend I will present two options for that first and then mention 2 ways to create a fixed legend.  Note that these examples were developed in gINT professional but I have tried to use only options that are available in gINT logs,  Since I do not have gINT logs you may find some differences or some of the options may not be available. The examples are based on the "gint std us" data structure and library, Your data structure and library may vary.

Option 1 - data driven log legend

This is a quasi variable legend in that it relies on you creating a "LEGEND" Borehole that then gets printed with a special log form to create the legend.  Example output is shown below.

The report design consists of a log with minimal header and footers, and 6 body entities.  In developing the report I used individual entities rather than column entities because I had no use for column lines or headers.  You could also use column entities if you want.  The report design is shown below.

There are 3 graphics vs depth entities and three text vs depth entities.  The graphic vs depth entity is driven from the data table to create individual symbols of the soil, samlpers and well.  The configuration of the first one (soil and rock symbols} is shown in the picture below:

The data table that drives this is shown below:

This is made by creating a special boring called LEGEND in each project and then populating the Lithology Table with all the unique symbols in the project and assigning each a top depth depth bottom depth and description.  It is relatively easy to create this data by exporting the entire lithology table to excel (select view entire table in input then export to excel) once the table is in excel use excel to remove duplicate symbols and write some simple formulas to create sequential top and bottom depths at regular intervals as shown.  You then have to manually enter a description for each symbol and paste it back into gINT. There is a separate text vs depth entity to the right of each symbol column in the report that is set to print the description.  It is set up similar to the graphic vs depth entity but ids driven off the description field in the lithology table. This is repeated for the sampler symbols and well symbols. To output, simply select this report and the LEGEND boring as the boring to output.

The advantage of this method is that if there are more symbols than will fit on a page it will generate more pages.  You can also easily control the order of the symbols and add more symbols than are in the project or separate symbols by spaces or subheadings (such as rock symbols and soil symbols). You can generate a nice custom legend this way but you have to manually create the data that drives it.  As described, this can be greatly simplified by using excel to extract all relevant symbols and generate even depth intervals.

Option 2 - True variable legend

This uses gINT's variable legend on a log form.  It is a bit of a stretch because it was not designed to do this but here is an example output

The log form properties are contorted to provide a first page with no body and a second page body height of 1 inch (the minimum). The report properties are shown in the picture below.

The problem with using a log report this way is that it has to have a body and it has to have at least 1 piece of data to plot in that body.  We get around that by pushing the body to the second page and giving it an invisible piece of data to plot.  Of course this forces it to generate 2 pages but you only want the first one.  The report design is shown in the picture below:

Note I have inserted 3 variable legend entities in the header space of the first page for soil symbols, sampler symbols, and well symbols.  I have also added a body entity in the bottom center of the report design that is a simple graphic vs depth entity (see picture below). the properties are set to print a solid white block between 0 and 1 foot and the  print order is set to -1 so it will be below the rest of the data.

Typical variable legend properties are shown in the picture below

The variable legend is set to draw data from the entire project so it does the work of sorting through your borings and finding what symbols you used

To output this legend you will have to select a a boring (it does not matter which one because the report does not use any actual data).  It will generate 2 pages of the same thing but you only want the first one. If you don't want to waste paper you can generate a preview and then just print the first page. you can also choose what pages to print if you export to pdf. You could probably get rid of the 2 pages by simply specifying the first page to have a 1 inch high body.  This will place the solid white box on the first page as an object but you will never see it unless you edit the output in a pdf editor or cad. I did not try this in my example but is probably worth looking into.

This report requires less work to generate a legend for the project because you don't have to create a Legend boring.  Drawbacks are that it is limited to a single page and in order to control the order and descriptions of the symbols you have to carefully build the symbol library.  Not sure what gINT logs allows in terms of editing the symbol libraries and tables.

Option 3 - Fixed graphic symbols

This is a fixed legend so explanation will be brief.  The report structure is set up similar to the option 2 above.  Instead if variable legend entities you construct the legend using individual graphic symbols and text elements.  Quite tedious but it can generate a very nice looking legend. I use this option on many of my legends as it gives me more flexibility  with formatting of legend entries.

Option 4 - Bit map image legend

This is set up similar to option 2 above and is also a fixed legend. The only entity in the header is a bitmap image that covers the entire page.  I create the bit map image in other software (I use powerpoint) and then insert it into the log.  This gives me lots of flexibility with respect to layout and formatting and is much easier (for me at least) to edit than dealing with all the entities in a gINT log form.  If I need the make a change I simply edit the powerpoint, export a high res bitmap (300 dpi) and reinsert it in the legend report. Drawbacks of this method are that it increases your library size (it has to store the bitmap) and increases output time by a second or 2.

Hope this helps, Some of my descriptions may not be all that clear but it should give you some ideas on which way you want to go.  I can provide more details on specific issues if you want.