This example will be similar to using Options to vary the Units per Page on a log...
Except in this case, we will set up our templates so our logs are always generated with a nice scale that the user can choose to vary between Locations if desired. We’ll still use a Units per Page expression, but the Units Per Page will be calculated based on the scale we’d like to use...
To do so, you can create a Picklist with the Scale Factors you’d like to use. For example, a Scale Factor of 10 would result in a scale of 1:10. A Scale Factor of 20 would result in a scale of 1:20, and so on.
You can create the Picklist under Configuration>Manage Picklists. In this example, we’ll call the picklist ‘Options – ScaleFactor’ and add the values we’d like.
You can then create a Project Option group named ‘ProjectOptions’ with a ‘ScaleFactor’ Picklist header. (You can name the group and header whatever you'd like, but these are the names used in this example.)
You can also add a Location Option group named ‘LocationOptions’ with a ‘ScaleFactor’ Picklist header.
You will then need to open your Borehole Log template(s) in Template Studio and enter a ‘Units per Page’ expression under Design>Template Setup.
The general equation we will use is:
Scale Factor * Plot Area / Conversion Factor
The Plot Area is the height of Depth Area on your template, which can be found in Template Studio under Design>Template Setup.
The Conversion Factor is dependent on the depth units used for your configuration pack (meters vs. feet) and the Measurement Units used for your template (mm vs. inches). For example:
Config Pack Depth Units | Template Measurement Units | Conversion Factor |
m | mm | 1000 |
ft | mm | 304.8 |
ft | in. | 12 |
m | in. | 39.3701 |
In this example, we have a 200 mm Plot Area, a metric configuration pack, and mm Template Measurement Units, which means we will use 1000 as a Conversion Factor. We will want the Location Option to override the Project Option (similar to this example). So, we will use the Expression:
if(isblank([LocationOptions.ScaleFactor]),[ProjectOptions.ScaleFactor],[LocationOptions.ScaleFactor]) * 200 / 1000
We can then check how this works…
For our Scale Factor, we’ll enter a Project Option of 40 and a Location Option of 20 for ‘TP1’. We then output a Log Report and see that all Locations have a Scale of 1:40 (the Project Option) except for TP1, which has a scale of 1:20 (the Location Option).
If the ‘Units Per Page’ expression does not return a value, such as if a Project or Location Option is not entered, it will use the default Scale or Units per Page defined in the template or Report Profile when generating Quick Logs or Log Reports.
Alternatively, we could slightly modify the expression to return a default value for the Scale Factor, in this case 50:
if( isblank([LocationOptions.ScaleFactor]), if( isblank([ProjectOptions.ScaleFactor]), 50, [ProjectOptions.ScaleFactor] ), [LocationOptions.ScaleFactor] ) * 200 / 1000
(Formatted to 1 line:)
if(isblank([LocationOptions.ScaleFactor]),if(isblank([ProjectOptions.ScaleFactor]),50,[ProjectOptions.ScaleFactor]),[LocationOptions.ScaleFactor]) * 200 / 1000
There are many potential variations to how your Options and Units per Page expression can be set up to achieve the behavior you would like.
Additional Notes