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
tips [2019/12/08 22:37] – including the centreline tarquinwjtips [2024/11/17 06:08] (current) – [Choosing Colour Palettes] Add https://colorcodes.io brucemutton
Line 131: Line 131:
 As described in the Therion Book, __How the map is put together__, the layers are 'default-bottom', 'default' and 'default-top'.  'Default', as you might guess is in the middle. Areas go to the bottom, ceiling-step and chimney go to the top, everything else is somewhere in the middle. As described in the Therion Book, __How the map is put together__, the layers are 'default-bottom', 'default' and 'default-top'.  'Default', as you might guess is in the middle. Areas go to the bottom, ceiling-step and chimney go to the top, everything else is somewhere in the middle.
  
-Now if you find that you have not drawn an entity in exactly the right order to get that special effect you were after, there is an over-ride.  There are two more 'layers', 'top', and 'bottom' and these are placed by Therion above 'default-top' and below 'default-bottom' respectively.  To put an entity in either of these layers, add the option -place top or -place bottom.  If using -place for an area it is probably a good idea to use -place for its defining border as well.+Now if you find that you have not drawn an entity in exactly the right order to get that special effect you were after, there is an over-ride.  There are two more 'layers', 'top', and 'bottom' and these are placed by Therion above 'default-top' and below 'default-bottom' respectively.  To put an entity in either of these layers, add the option -place top or -place bottom.  If using -place for an area it is probably a good idea to use -place for its defining border as well. There is then an upper layer on top of 'top', which is the layer containing any items that have '-clip off', since these are rendered after all items that take part in normal clipping. If you have an entity without '-clip off' that needs to be rendered on top of an entity that has '-clip off' (eg. a ceiling step that must appear on top of a boulder when the boulder-edge has '-clip off'), then you will need to give the first entity (the ceiling step in the example) '-clip off' as well. These non-clipped entities are then layered with respect to each other respecting the usual -place and stacking orders.
  
 Fifthly, transparency and opacity settings come into it, as well as the particular viewer or printer driver you are using, as indicated in the first paragraph above. Fifthly, transparency and opacity settings come into it, as well as the particular viewer or printer driver you are using, as indicated in the first paragraph above.
Line 148: Line 148:
  
 ==== Avoiding Invisible or Misshapen Scraps in Loch and Google Earth ==== ==== Avoiding Invisible or Misshapen Scraps in Loch and Google Earth ====
-Over time the pdf outputs have become resilient to many drawing misdemeanour's, and so you can break many of the rules described in the Therion Book, and still get a pretty good (or even perfect) output. But the Loch model and Google Earth map outputs are not yet so versatile (June 2011 version 5.3.8), and often result in missing or miss-drawn pieces of cave passage. \\+Over time the pdf outputs have become resilient to many drawing misdemeanour's, and so you can break many of the rules described in the Therion Book, and still get a pretty good (or even perfect) output. But the Loch model and Google Earth map outputs are not yet so versatile (2011 - 2021), and often result in missing or miss-drawn pieces of cave passage. \\
 Here are the usual culprits. Here are the usual culprits.
 ^ Misdemeanour ^ Symptom ^ ^ Misdemeanour ^ Symptom ^
 |* //line wall// with incorrect 'reverse' status (yellow tick should point inside passage void) | Invisible passage.  Loch walls appear and vanish as you rotate the model | |* //line wall// with incorrect 'reverse' status (yellow tick should point inside passage void) | Invisible passage.  Loch walls appear and vanish as you rotate the model |
-|* //line wall// with interior passage that does not have '-outline in' option set. | Interior of loop is rendered and passage is invisible |+|* //line wall// that is completely enclosed by a single scrap (such as for an oxbow passage) that does not have ''-outline in'' option set. | Interior of loop is rendered and passage may be invisible | 
 +|* //line wall// that is completely enclosed by a single scrap (such as for an oxbow passage) but is not continuous and closed.  Hint: Close intentionally open ends that are completely enclosed by a single scrap with a ''line wall -subtype invisible'' to solve this problem. | Interior of loop is rendered and passage may be invisible |
 |* An open passage end has one or more wall ends that curls back into the interior of the passage. | Invisible passage | |* An open passage end has one or more wall ends that curls back into the interior of the passage. | Invisible passage |
 |* A scrap has open space along it's length. ie openings left for side passages directly opposite each other break the scrap in half. | Only one of the parts of the scrap are rendered | |* A scrap has open space along it's length. ie openings left for side passages directly opposite each other break the scrap in half. | Only one of the parts of the scrap are rendered |
-|* Scrap is wider than it is long, or has long walls with '-subtype invisible', or \\ very complicated scraps | These are not necessarily misdemeanours, but I think it might cause the passage to be invisible. |+|* Scrap is wider than it is long, or has long walls with ''-subtype invisible'', or \\ very complicated scraps | These are not necessarily misdemeanours, but I think it might cause the passage to be invisible. |
 |* Passage wall has a loop in it, either because the bezier curve handles have been extended too far, or because the subsequent morphing when scraps join has encouraged a loop to form|probably invisible passage (not verified) Metapost gives a 'scrap outline intersects itself' warning| |* Passage wall has a loop in it, either because the bezier curve handles have been extended too far, or because the subsequent morphing when scraps join has encouraged a loop to form|probably invisible passage (not verified) Metapost gives a 'scrap outline intersects itself' warning|
-|* Therion cannot handle two consecutive //wall:invisible// lines joining each other (5.3.9 Nov 2011) Try making the two invisible lines into one long invisible line or make one of them //-visibility off// instead|Passages have gaps and strange artefacts emanating from them | +|* Therion cannot handle two consecutive ''wall:invisible'' lines joining each other (5.3.9 Nov 2011) Try making the two invisible lines into one long invisible line or make one of them ''-visibility off'' instead|Passages have gaps and strange artefacts emanating from them | 
-|* A line with //-outline out// is connected to a line with //-outline in// |Passages have gaps and strange artefacts emanating from them|+|* A line with ''-outline out'' is connected to a line with ''-outline in'' |Passages have gaps and strange artefacts emanating from them|
 |* Instead of abutting end to end, a pair of line wall overlap each other, the first segment of one line with the last segment of another | Loch model contains large spurious artefacts | |* Instead of abutting end to end, a pair of line wall overlap each other, the first segment of one line with the last segment of another | Loch model contains large spurious artefacts |
  
Line 184: Line 185:
  
 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. \\
  
-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.+''**Important:** Only use the **join** command if it is necessary to do so. ie when there are open passage ends or drawing lines that should be joined in the final output, but are not. \\ 
 + 
 +**Do not use** the **join** command if your adjacent scraps do not have any lines that need to be joined.  An example of this would be a higher passage approaching the top of a pitch, and a lower passage that continues from the bottom of the pitch.  Both the upper scrap and the lower scrap might be drawn with closed ends around the top and bottom of the shaft respectively.  These overlapping scraps would not normally need to be joined, and using the semi-automatic approach described below will guarantee extreme distortion!''\\ 
 + 
 +**How to join scraps** 
 + 
 +There are three ways to join scraps, or components of scraps;  
 +  * fully automatically in *.th2 file,  
 +  * semi-automatically scrap by scrap, and  
 +  * manually line or point by point (if you must specify exactly which lines and points join).  
 + 
 +For any particular pair of lines or points to be joined, you should only use one of these methods.  Multiple joins of the same set of objects is likely to give unpredictable results! The last two methods are described in Thbook and all three are described below.\\ 
 + 
 +Join commands can be put directly into a survey definition, but not usually inside scrap or map definitions.
  
 **Fully automatic in *.th2 file** **Fully automatic in *.th2 file**
  
-If you draw two or more scraps adjacent to each other in your drawing *.th2 file, and make sure the adjacent line wall ends snap to each other, then Therion will automatically morph them, if necessary, to create a perfect join.  A morph might be necessary, if for example survey closure or other drawing distortions might tend to separate the scraps you have drawn as touching.+If you draw two or more scraps adjacent to each other in your drawing *.th2 file, and make sure the adjacent line wall ends snap to each other, then Therion will automatically morph them, if necessary, to create a perfect join.  A morph might be necessary, if for example survey closure or other drawing distortions might tend to separate the scraps you have drawn as touching.\\ 
 +This is really just an automatic implementation of the 'Manual line or point by point' method described below.\\ 
 + 
 +In fact, any points or line points (not just open ends of passage walls) drawn coincident (snapped together) in a th2 file will be morphed in the output to also be coincident.
  
 **Semi-automatic scrap by scrap** **Semi-automatic scrap by scrap**
  
-    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 
 +                       where <number> must be greater than or equal to 2
  
-The method can only join two scraps at a time.  Note that it only 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 opening. If there are multiple places where the two scraps join, you can normally use the "-count" option to say how many possible passage joins Therion should search for in the two scraps.+The method can only join two scraps at a time.  Note that it only 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 opening. If there are multiple places where the two scraps join, you can normally use the "-count" option to say how many possible passage joins Therion should search for and join in the two scraps.
  
-**Manual line by line**+**Manual line or point by point**
  
-From time to time the semi-automatic way does not work, or you want more refined control.  Then you should join each line to the other line (usually, but not only walls) or to a point. If you have several objects to join at one point, then unlike the scrap by scrap join above, you should use one join statement to join them all (see bottom of this topic).  Every point on a line has a mark according its sequence from beginning of line (yellow tick). The first one has mark 0, next one 1, etc., last one is mark "end". So the join command will be:\\+From time to time the semi-automatic way does not work, or you want more refined control.  Then you should join each line or point to the other line or point (usually, but not only walls). If you have several objects to join at one point, then unlike the scrap by scrap join above, you should use one join statement to join them all in one go (see bottom of this topic).  Every point on a line has a mark according its sequence from beginning of line (yellow tick). The first one has mark 0, next one 1, etc., last one is mark "end". So the join command will be:\\
  
  
Line 232: Line 250:
     join line1:john line2:jane line3:jack line4:jill     join line1:john line2:jane line3:jack line4:jill
  
-For more detail see [[tbe:wiki3#joining_scraps|Therion by Examples, chapter 3]] and [[faq#how_do_i_join_three_scraps_in_a_y-shape]]+If you refer to the same point in more than one join statement, then one of the joins will be ignored.
  
 +For more detail see [[tbe:wiki3#joining_scraps|Therion by Examples, chapter 3]] and [[faq#how_do_i_join_three_scraps_in_a_y-shape]]
 ====How to export correct extended elevation from zig-zag centerline==== ====How to export correct extended elevation from zig-zag centerline====
  
Line 304: Line 323:
 ===Including some centreline data=== ===Including some centreline data===
  
-If you need to include a centreline-only section of the cave in your rendering, then the same approach works, but it is a little more convoluted. Create a scrap in the highest and lowest parts of the cave. Those scraps should contain only a single station point. It doesn't have to be the highest or lowest station, since simply including any station causes all of them within that survey to be considered for the highest and lowest points. Give that station the "-visibility off" option:+If you need to include a centreline-only section of the cave in your rendering, then you cannot use "symbol-hide group centreline". However, the same basic approach for getting the correct vertical range works, but it is a little more convoluted. Create a scrap in the highest and lowest parts of the cave. Those scraps should contain only a single station point. It doesn't have to be the highest or lowest station, since simply including any station causes all of them within that survey to be considered for the highest and lowest points. Give that station the "-visibility off" option:
  
   scrap emptySP -projection plan -scale [1 10 1 10 0.0 0.0 10 10 m]   scrap emptySP -projection plan -scale [1 10 1 10 0.0 0.0 10 10 m]
Line 324: Line 343:
     anothersubsection_one_station_map@anothersubsection [-23 12 m] none #the survey containing the lowest part of the cave     anothersubsection_one_station_map@anothersubsection [-23 12 m] none #the survey containing the lowest part of the cave
   endmap   endmap
 +
 =====Map Layout===== =====Map Layout=====
  
Line 422: Line 442:
 With this example, none of these borders will appear in the legend, even if these lines are used in the drawing. With this example, none of these borders will appear in the legend, even if these lines are used in the drawing.
      
 +====Drawing a symbol on the legend which is not used on the map====
 +
 +Therion allows you to embed one PDF (eg. an elevation survey) in another PDF (eg. a plan survey), so that two views of the cave can be displayed together. When doing this, you normally only want one copy of the legend, so you would disable the legend on one of them. The survey being embedded may use symbols that are not used on the main survey, and those symbols would not be shown on the main legend.
 +
 +To fix this, use the same symbol somewhere on the main survey. Place it outside of the cave outline, so it is not within a passage. If it has "outline out" by default (such as a wall), set "-outline none". If it has "clip off" by default (most point symbols, some line symbols such as water-flow and label), set "-clip on".
 +
 +The symbol will not be visible on the main survey, but it will be in the main survey's legend. A nice and simple solution.
 +
 +Note that it is not possible to use this approach with symbols that display differently in plan and elevation view (eg. handrails), and there does not appear to be an easy solution to that. The only alternative would be to export a custom PDF survey that uses only that symbol, a box line around it, a text label to one side. Try to make it look like a legend item. Embed it into the main survey just below the legend. This is an ugly hack.
 +
 =====Atlas Layout Parameter Calculator===== =====Atlas Layout Parameter Calculator=====
  
Line 451: Line 481:
 //**Take care that the final colour will strictly depend on setup (calibration) of your screen, system, application and printer or data projector!!!**// //**Take care that the final colour will strictly depend on setup (calibration) of your screen, system, application and printer or data projector!!!**//
  
 +Also check out https://colorcodes.io 
 =====Reconstruction of surveying data from paper map===== =====Reconstruction of surveying data from paper map=====
  
  • tips.1575841071.txt.gz
  • Last modified: 5 years ago
  • by tarquinwj