tips

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
tips [2018/04/30 07:42] – [How to export correct extended elevation from zig-zag centerline] brucemuttontips [2019/06/09 10:05] – match ISO paper size proportions brucemutton
Line 85: Line 85:
 ====Scrap Drawing Tips==== ====Scrap Drawing Tips====
 [[drawingchecklist#scrap_drawing|Some Scrap Drawing Tips]] [[drawingchecklist#scrap_drawing|Some Scrap Drawing Tips]]
 +
 +====Pitch Drawing Tips====
 +[[offsetpitches|Colouring pitches in simple and offset maps]]
 +
 +====Surface Drawing Tips====
 +[[surfacefeatures|Drawing surface features]]
 +
 +====Using map connections====
 +[[mapconnectors|Map Connections]]
 +
 +====Using elevations====
 +[[projectedelevations|Making projected elevations]]
 +
 +[[colouringelevations|Colouring elevations]]
  
 ====Drawing Order How to draw symbols over or under an area==== ====Drawing Order How to draw symbols over or under an area====
Line 159: Line 173:
 One of Therion's key features is that drawings are created in small pieces - scraps. A scrap is the smallest indivisible part of the drawing that can exported to create an output.\\ One of Therion's key features is that drawings are created in small pieces - scraps. A scrap is the smallest indivisible part of the drawing that can exported to create an output.\\
 Most maps contain many scraps, and if they don't happen to appear perfectly joined by coincidence, then you should "join" these individual scraps to get Therion to morph them together. There are three ways to do it; fully automatically in *.th2 file, semi-automatically scrap by scrap, and manually line by line (if you must specify exactly which lines and points join). The last two are described in Thbook; Most maps contain many scraps, and if they don't happen to appear perfectly joined by coincidence, then you should "join" these individual scraps to get Therion to morph them together. There are three ways to do it; fully automatically in *.th2 file, semi-automatically scrap by scrap, and manually line by line (if you must specify exactly which lines and points join). The last two are described in Thbook;
 +
 +Join commands are put directly into the survey section, not inside any scrap or map definitions - lines are joined independently, ignoring whatever scraps and maps they are defined or included in.
  
 **Fully automatic in *.th2 file** **Fully automatic in *.th2 file**
Line 167: Line 183:
  
     join scrap1 scrap2 [-count <number of passage (not line) joins for Therion to look for>]     join scrap1 scrap2 [-count <number of passage (not line) joins for Therion to look for>]
 +
 +Note that this works using passages defined by lines of "wall" type (even if their "-outline" is set to "none"). It does not join other types of line. It normally expects to find pairs of lines, one on each side of the passage. If there are multiple passages that need to be joined between pairs of scraps, you can normally use the "-count" option to say how many possible passage joins Therion should search for.
  
 **Manual line by line** **Manual line by line**
Line 195: Line 213:
  
 You may use join command to join line to line or line to point. So if the beginning of a particular passage is between two blocks you may join walls of passage to points of rock-borders. After the morphing the beginning of passage will be still connected to blocks. You may use join command to join line to line or line to point. So if the beginning of a particular passage is between two blocks you may join walls of passage to points of rock-borders. After the morphing the beginning of passage will be still connected to blocks.
 +
 +The lines (just like maps, scraps, points and stations) are referenced by their ID directly inside their survey - inside a subsurvey, this would be as id@subsurvey (or id@subsurvey.subsurvey for nested subsurveys) - so make sure you have assigned an ID to each line that needs to be joined using the join command.
  
 If you want to join three or more lines and or points, do all the coincident joins in a single command, eg If you want to join three or more lines and or points, do all the coincident joins in a single command, eg
Line 206: Line 226:
 Very common problem, when drawing extended elevation of steepy and large passage where centerline is from practical reasons zig-zag and automatic generation of centerline will increase real length of passage. Very common problem, when drawing extended elevation of steepy and large passage where centerline is from practical reasons zig-zag and automatic generation of centerline will increase real length of passage.
  
-In Survex and in Therion there could be label "nosurvey" in data structure definition command. +In Survex and in Therion there could be label ''no survey'' in data structure definition command. 
  
 Example: Example:
Line 231: Line 251:
  
 \\ \\
-Command //data nosurvey from to// means there will be created fake survey shot from station 18.2 to 18.5, but this survey shot will play in extended elevation generation.\\ +Command ''data nosurvey from to'' means there will be created fake survey shot from station 18.2 to 18.5, but this survey shot will play in extended elevation generation.\\ 
-To prevent interaction with survey shots from station 18.2 to 18.3, 18.3 to 18.4 and 18.4 to 18.5 there is another command //extend ignore// what mean those shots will be not included in extended elevation generation. \\+To prevent interaction with survey shots from station 18.2 to 18.3, 18.3 to 18.4 and 18.4 to 18.5 there is another command ''extend ignore'' what mean those shots will be not included in extended elevation generation. \\
 \\ \\
 Final result should be as on images:\\ Final result should be as on images:\\
 {{:tips:zig-zag_map.png?150|map}} {{:tips:zig-zag_extended.png?150|extended}}\\ {{:tips:zig-zag_map.png?150|map}} {{:tips:zig-zag_extended.png?150|extended}}\\
 See also [[extend|Extended Elevations]] page for comprehensive extended elevation guidance. See also [[extend|Extended Elevations]] page for comprehensive extended elevation guidance.
- 
 =====Map Layout===== =====Map Layout=====
 +
 +====How to make map outputs match ISO paper size proportions====
 +from Chris Hayes
 +
 +ISO paper sizes have an edge length ratio, H:W, of √2:1, or vise versa. However when exporting maps to pdf, Therion makes the pdf exactly match the bounds of the cave, plus any images or legend elements that we might include with the layout.  This does not typically match an ISO paper size, or the proportions thereof.
 +
 +
 +If we want our exported map output to scale nicely to print to a standard paper size (e.g. A4, A3, A1) then we need to cunningly include a map-header and or a map-image element to nudge the size of the pdf 'paper'.
 +
 +
 +  * Compile a map with ''map-header 0 100 nw'' and ''map-header 100 0 se'' to get the dimensions, H and W of the pdf, then modify the map-header specification and compile again.
 +
 +  * For portrait outputs;  add / remove ''delta H = 50*[√(2)*W/H -1]'' to the y positions
 +  * For landscape outputs; add / remove ''delta W = 50*[√(2)*H/W -1]'' to the x positions
 +
 +
 +  # Example for a portrait output, with modified y positions
 +  map-header 0 109.79986718266315 nw               #place map header in top left corner
 +  map-image 100 -9.79986718266315 se Club_Logo.png #place an image such as club logo in bottom right corner
 +
 +The output will probably not match an ISO paper size that you have in your printer, but it will be of the correct proportion to be scaled to fit thatISO paper size.
  
 ====Map-image and custom legendbox==== ====Map-image and custom legendbox====
Line 303: Line 343:
  
 {{:multilingual_legend.png|}} {{:multilingual_legend.png|}}
 +
 +==== Hiding particular symbols from legend ====
 +Sometimes you might want to hide just one particular symbol from the legend. \\
 +This is as simple as setting the legend text for the symbol to an empty string, "" \\
 +This is done within the thconfig file.
 +eg
 +  text en "line border:visible" ""
 +  text en "line border:temporary" ""
 +  text en "line border:presumed" ""
 +  
 +With this example, none of these borders will appear in the legend, even if these lines are used in the drawing.
 +  
 =====Atlas Layout Parameter Calculator===== =====Atlas Layout Parameter Calculator=====
  
  • tips.txt
  • Last modified: 2 years ago
  • by brucemutton