Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
tips [2018/05/28 11:23] – Hiding particular symbols from legend brucemutton | tips [2022/04/02 00:29] (current) – [Joining scraps together] duplicate joined points will be ignored brucemutton | ||
---|---|---|---|
Line 45: | Line 45: | ||
* Always check the " | * Always check the " | ||
* If you press the " | * If you press the " | ||
- | * If you add line object, you may start to insert new line simple by pressing of Ctrl+L keys, you don't need to escape from " | + | * To add a line object, you may start to insert new line simple by pressing of Ctrl+L keys, you don't need to escape from " |
* Always check the small yellow tick on first point of line object. It shows the FREE space side of line. It means you should draw walls in counterclockwise direction, the blocks in clockwise direction, pit or chimney in counterclockwise direction, etc. If you made a mistake there is " | * Always check the small yellow tick on first point of line object. It shows the FREE space side of line. It means you should draw walls in counterclockwise direction, the blocks in clockwise direction, pit or chimney in counterclockwise direction, etc. If you made a mistake there is " | ||
+ | |||
+ | ===Finding Objects if you have large blank extents=== | ||
+ | If you have inserted an xvi or drawing image with large extents, it may be difficult to find the drawing objects by panning or zooming around the drawing interface.\\ | ||
+ | An easier way to locate any drawing objects is to open the Objects window on the top right-hand side of the XTherion interface, and click on one of the objects listed. | ||
+ | Except for scraps, and areas, most objects will be selected and the drawing area will be panned to show the object mid-screen.\\ | ||
+ | For example, clicking on object 4 below, selects it and brigs it to the centre of the drawing area. | ||
+ | |||
+ | {{tips: | ||
+ | |||
+ | If you are repeatedly creating th2 files with large blank extents around the drawings and images, then it may be because of spurious drawing lines made accidentally when navigating during data collection with PocketTopo, TopoDroid, SexyTopo or the likes. | ||
+ | If drawings and export\imports are well posed, then your drawing area extents should not be much larger than your actual drawing.\\ | ||
+ | You can manually or automatically tweak the drawing area that is viewable for a particular file if you scroll down to the Drawing Area window near the bottom of the right-hand side of XTherion, and make adjustments there. | ||
Line 85: | Line 97: | ||
====Scrap Drawing Tips==== | ====Scrap Drawing Tips==== | ||
[[drawingchecklist# | [[drawingchecklist# | ||
+ | |||
+ | ====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 105: | Line 131: | ||
As described in the Therion Book, __How the map is put together__, the layers are ' | As described in the Therion Book, __How the map is put together__, the layers are ' | ||
- | 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. | + | 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. |
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 122: | 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' | + | Over time the pdf outputs have become resilient to many drawing misdemeanour' |
Here are the usual culprits. | Here are the usual culprits. | ||
^ Misdemeanour ^ Symptom ^ | ^ Misdemeanour ^ Symptom ^ | ||
|* //line wall// with incorrect ' | |* //line wall// with incorrect ' | ||
- | |* //line wall// | + | |* //line wall// |
+ | |* //line wall// that is completely enclosed by a single scrap (such as for an oxbow passage) but is not continuous and closed. | ||
|* 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 ' | + | |* Scrap is wider than it is long, or has long walls with '' |
|* 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' | |* 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' | ||
- | |* Therion cannot handle two consecutive | + | |* Therion cannot handle two consecutive |
- | |* 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 '' |
|* 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 158: | Line 185: | ||
One of Therion' | One of Therion' | ||
- | Most maps contain many scraps, and if they don't happen to appear perfectly joined by coincidence, | + | Most maps contain many scraps, and if they don't happen to appear perfectly joined by coincidence, |
+ | |||
+ | '' | ||
+ | |||
+ | **Do not use** the **join** command if your adjacent scraps do not have any lines that need to be joined. | ||
+ | |||
+ | **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. | ||
+ | |||
+ | 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 ' | ||
+ | |||
+ | 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** | ||
Line 168: | Line 213: | ||
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>] | ||
- | **Manual line by line** | + | The method can only join two scraps at a time. Note that it only works using passages defined by lines of " |
+ | |||
+ | **Manual line or point by point** | ||
- | From time to time the semi-automatic way does not work, or you want more refined control. | + | From time to time the semi-automatic way does not work, or you want more refined control. |
Line 195: | Line 242: | ||
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 200: | Line 249: | ||
join line1:john line2:jane line3:jack line4:jill | join line1:john line2:jane line3:jack line4:jill | ||
- | For more detail see [[tbe: | + | 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: | ||
====How to export correct extended elevation from zig-zag centerline==== | ====How to export correct extended elevation from zig-zag centerline==== | ||
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 " | + | In Survex and in Therion there could be label '' |
Example: | Example: | ||
Line 231: | Line 281: | ||
\\ | \\ | ||
- | Command | + | Command |
- | 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 | + | 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 |
\\ | \\ | ||
Final result should be as on images:\\ | Final result should be as on images:\\ | ||
{{: | {{: | ||
See also [[extend|Extended Elevations]] page for comprehensive extended elevation guidance. | See also [[extend|Extended Elevations]] page for comprehensive extended elevation guidance. | ||
+ | |||
+ | ====Showing centreline for parts of a cave, and passage walls for others==== | ||
+ | |||
+ | Sometimes you might have full survey data and drawings for some parts of a cave, while other parts might have only centreline data. It is possible to combine these in the same PDF output, using a map consisting of other maps, and other surveys: | ||
+ | |||
+ | map allcave | ||
+ | subsection_map@subsection #the part with walls drawn | ||
+ | othersubsection_survey | ||
+ | endmap | ||
+ | |||
+ | Note that you now cannot use " | ||
+ | |||
+ | ====Making a subset of the cave take its altitude colours from a larger part of the cave==== | ||
+ | |||
+ | When rendering a map (map-endmap), | ||
+ | |||
+ | When you want to render a subset of that cave, such as a map showing only the entrance series of a cave, you might want to have the colours match the colours that were used in the overall map, so that the parts of the cave are recognisable. One way is to use an [[examples# | ||
+ | |||
+ | Another approach, which allows Therion to continue using automatic altitude colours, is to [[#Showing centreline for parts of a cave, and passage walls for others|include the highest and lowest surveys/ | ||
+ | |||
+ | map foo | ||
+ | subsection_map@subsection #the part you actually want to render | ||
+ | othersubsection_survey | ||
+ | anothersubsection_survey | ||
+ | endmap | ||
+ | |||
+ | Your layout would then include this: | ||
+ | |||
+ | color map-fg altitude | ||
+ | symbol-hide group centreline | ||
+ | |||
+ | By hiding the centreline, you cause the unwanted surveys not to render at all, so the output acts like they were never included (it is cropped accordingly to show only the rendered part). | ||
+ | |||
+ | ===Including some centreline data=== | ||
+ | |||
+ | If you need to include a centreline-only section of the cave in your rendering, then you cannot use " | ||
+ | |||
+ | scrap emptySP -projection plan -scale [1 10 1 10 0.0 0.0 10 10 m] | ||
+ | point 1 1 station -name 2 -visibility off | ||
+ | endscrap | ||
+ | |||
+ | Include that scrap instead of including the survey itself. You will then also need to [[metapost# | ||
+ | |||
+ | map othersubsection_one_station_map | ||
+ | emptySP | ||
+ | endmap | ||
+ | |||
+ | Then include that map with an offset, pushing it into the normally visible area of the survey (the same position as the passages that you want to show). This seems convoluted and takes a little time to set up perfectly, but it works. | ||
+ | |||
+ | map foo | ||
+ | subsection_map@subsection #the part you actually want to render | ||
+ | centreline_only_survey #the survey that contains only centreline data without any passage drawings | ||
+ | othersubsection_one_station_map@othersubsection [123 456 m] none #the survey containing the highest part of the cave | ||
+ | anothersubsection_one_station_map@anothersubsection [-23 12 m] none #the survey containing the lowest part of the cave | ||
+ | endmap | ||
=====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. | ||
+ | |||
+ | |||
+ | 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 ' | ||
+ | |||
+ | |||
+ | * Compile a map with '' | ||
+ | |||
+ | * For portrait outputs; | ||
+ | * For landscape outputs; add / remove '' | ||
+ | |||
+ | |||
+ | # Example for a portrait output, with modified y positions | ||
+ | map-header 0 109.79986718266315 nw # | ||
+ | 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 315: | Line 441: | ||
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 " | ||
+ | |||
+ | The symbol will not be visible on the main survey, but it will be in the main survey' | ||
+ | |||
+ | 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===== | ||