Differences

This shows you the differences between two versions of the page.

--- bds [2019/09/09 10:30] – [Concepts] add thconfig maps brucemutton
+++ bds [2024/11/17 05:49] (current) – [Concepts] clarify maps off brucemutton
@@ Line 83: / Line 83: @@
 **
 ''export map -projection plan        \''\\
-''-layout LayoutMapThisCave     \''\\
+''-layout LayoutMapThisCave     \'' **# called first, processed first** \\
-''-layout LayoutMapThisCavePlan \''\\
+''-layout LayoutMapThisCavePlan \'' **# called last, processed last** \\
 ''-output ./Output/MapBulmerSystem_Plan.pdf''
 **
@@ Line 139: / Line 139: @@
 <code>
 (thconfig-)*.thc  (thconfig)
-                    |-source (of surveys and drawings to compile)
+                    |-source     (of surveys and drawings to compile)
-                    |-maps   (enables or disables output map structure for the selected surveys and or maps)
+                    |-maps       (enables or disables output map structure for the selected surveys)
-                    |-select (particular surveys and or maps to export)
+                    |-maps-offset (enables or disables output of defined passage offsets from their true positions)
-                    |-input  (other files that contain text, lookups and layouts, so as not to clutter your thconfig)
+                    |-select     (particular surveys and or maps to export)
-                    |-text   (if you want to redefine default legend and map-header text strings)
+                    |-input      (other files that contain text, lookups and layouts, so as not to clutter your thconfig)
-                    |-lookup (if you want to redefine default colour palettes and text strings that can be used with map-fg layout options)
+                    |---text       (if you want to redefine default legend and map-header text strings)
-                    |–layout (to define options for appearance and 'layout' of 2D outputs)
+                    |---lookup     (if you want to redefine default colour palettes and text strings that can be used with map-fg layout options)
-                    |-cs     (to specify the output coordinate system)
+                    |–--layout     (to define options for appearance and 'layout' of 2D outputs)
-                    |-export (selected maps and specify layout, projection, filename, format etc)
+                    |-cs         (to specify the output coordinate system)
+                    |-log extend (to add a transcript of the extend sequence to therion.log)
+                    |-export     (selected maps and specify layout, projection, filename, format etc)
 </code>
@@ Line 154: / Line 156: @@
 **Source**  specifies the survey data and scraps or maps that are to be compiled.  You must specify at least one source.
 \\ \\
-**maps** if maps OFF is chosen, defined map structures are NOT parsed to the outputs (therefore offsets are disabled).  Only scraps from the selected maps are output.  Survey centrelines and stations are not output.
+**maps** if maps OFF is chosen, defined map structures are NOT parsed to the outputs (therefore offsets are disabled and previews of passages are not shown).  Only scraps from the selected (or source) surveys or maps are output.  Survey centrelines and stations are not output. Optional.
 \\ \\
-**Select** selects particular surveys and or maps to export.  If you do not select a survey, all surveys are selected by default.  If you do not select a map, all scraps and maps are selected by default.  Optional.
+**maps-offset** if OFF is chosen, defined offsets are ignored, and the scraps are drawn in their true positions.   Previews are exported as usual (although previews associated with any offsets are of course not required).  Maps-offset has no meaning or effect if maps off is also chosen.  Optional.
+\\ \\
+**Select** selects particular surveys and or maps to export.  If you do not select a survey, all surveys are selected by default.  If you do not select a map, all scraps are selected by default and map features such as offsets and previews are not actioned.  Optional.
 \\ \\
 **Input** enters the text of other files, as though they were typed herein.  You can use ''input'' to refer to standard ''text'', ''lookup'' or ''layout'' files, and avoid having long cumbersome thconfig files.  Optional.
 \\ \\
-**Text** commands redefine Therions default output text strings, such as those in map-headers and legends.  Mostly you will not need to use ''text''.
+**Text** commands redefine Therions default output text strings, such as those in map-headers and legends.  Mostly you will not need to use ''text''. Optional.
 \\ \\
-**[[examples#colour_scales_-_lookups|Lookups]]** define colour palettes for map and atlas outputs, and can apply to various parameters such as altitude, exploration or survey dates, or 'by map or 'by scrap'.
+**[[examples#colour_scales_-_lookups|Lookups]]** define colour palettes for map and atlas outputs, and can apply to various parameters such as altitude, exploration or survey dates, or 'by map or 'by scrap'. Optional.
 \\ \\
 **Layouts** define the look of 2D outputs.  ie scale, symbols, headings, graphics, co-ordinate system (which can differ to those used for survey data entry)%%**%%  You almost always need to use a layout to create an output that looks the way you want it to.
 \\ \\
 **cs** specifies the coordinate system to use for outputs.  If you do not specify this, Therion will use one of the coordinate systems used in the source survey files.  Optional.
+\\ \\
+**log extend** to add a transcript of the extend option and station sequence to therion.log.  See [[/extend#enumerating_extend_station_sequence]] and [[breakingextend]]. Optional.
 \\ \\
 **export** exports the maps selected above and specifies the format (type) of output to produce, the projection, if applicable, and many other options. Required.
@@ Line 189: / Line 195: @@
 With so many layout files it is inevitable that some parameters are changed and changed back and changed back again by the various layouts called.
-The key to understanding which setting will prevail is;
+The key to understanding which setting will prevail is knowing that;
-  * knowing that the order in which the layouts are called (by a copy statement for example) determines the order that the parameters are changed, the last one called determines the final value, and
+  * the order in which the layouts are called (by a copy statement for example) determines the order that the parameters are changed, the last one called determines the final value (but see https://github.com/therion/therion/issues/425),
-  * that the order or presence of an input statement has no effect on the order the parameters are changed.  The input statement just tells Therion in which file(s) to look for layouts.
+  * layouts called in an export statement are processed in order, the last one called determines the final value, and
+  * the order or presence of an input statement has no effect on the order the parameters are changed.  The input statement just tells Therion in which file(s) to look for layouts.
 Usually there is no problem with all this changing and changing back, but some parameters don't take kindly to it at all.  On rare occasions you will find anomalies or even strange errors because of this.  To debug for this type of problem, first comment out all the layouts, and then incrementally add layouts or individual statements back into the mix.
@@ Line 200: / Line 207: @@
 ...in the Layout[Map or Atlas]Cave layout;
+  copy LayoutStandard       # sets most parameters, symbol-set, then symbol-assignment, then other settings you want to standardise across the project
+  copy LayoutScale
+  # now call symbol redefinitions
   copy water-blue           # comment out for default hatching
   copy sump-blue            # comment out for default cross hatching
   copy scalebar-with-text   # comment out for default with no scale id
-  copy LayoutStandard       # sets most parameters
+  # maybe hide some symbols
-  copy LayoutScale
+  symbol-hide point remark
-  copy LayoutCave_Annotation
+  copy LayoutCave_Annotation # a specific layout describing this cave
 ...in the Layout[Map or Atlas]Cave[Plan or Elev] layout;