I put my map definitions for each survey at the end of the th2 file. I use the survey name followed by projection as the map name using camel notation e.g. surveyNamePlan This way I always know how to reference the map for any survey without having to look in the file. The maps are then put together in a separate file in the top level folder in a file which I name caveSystemMaps.th where caveSystem is obviously the name of the top level map. I used to use cave system_maps.th as the file name but I've found by using camel notation for all map items it differentiates them from survey names. This file contains all the maps and combinations of maps eg. map caveSystemPlan -title "Cave System Plan" surveyNamePlan surveyName2Plan break lowerLevelsPlan endmap map lowerLevelsPlan surveyName3Plan surveyName4Plan [100 50 m] above endmap A real example can be seen here http://www.cave-registry.org.uk/svn/Sarawak/Mulu/Api/Clearwater/ <http://www.cave-registry.org.uk/svn/Sarawak/Mulu/Api/Clearwater/> in the file clearwater_maps.th This is my template for thconfig files. I just do find and replace surveyName with whatever my survey name is and modify the line #select surveyNamePlan to camel notation. For folder structure I put all output files into a top level folder called output to make it easier to archive everything to a repository excluding the output files which can be reproduced by Therion. This saves a lot of space on the server. encoding utf-8 ######################################## Input ################################################ source surveyName.th input /Users/daveclucas/Documents/caving/surveys/common_layout.th input /Users/daveclucas/Documents/caving/surveys/therionLayouts/layoutscales.thc ######################################## Layouts ################################################ layout layout copy common copy LayoutScale2000 map-header 0 0 off rotate 60 endlayout layout images map-image 0 100 sw ../output/componentElevations/surveyName_elev300.pdf map-header 0 0 nw endlayout layout xviScale scale 1 1000 endlayout layout debug colour map-fg altitude symbol-show point station debug station-names endlayout ######################################## Output ################################################ export model -o ../output/componentModels/surveyName.lox export model -o ../output/componentModels/surveyName.3d #export model -o ..output/componentModels/surveyName.kml #requires a fixed station in survey #export map -o ../output/componentModels/surveyName.kml #requires a fixed station in survey export map -o ../output/componentModels/surveyName.xvi -layout xviScale export map -o ../output/componentModels/surveyName_e300.xvi -layout xviScale -proj [elevation 300] #export map -o ../output/componentElevations/surveyName_elev300.pdf -proj [elevation 300] -layout layout -layout LayoutScale1000 #select surveyNamePlan #export map -o ../output/componentPlans/surveyName.pdf -layout layout -layout LayoutScale1000 #-layout images ################################################################################################# Dave Clucas daveclucas.com <http://daveclucas.com/> sarawak-caves.com <http://sarawak-caves.com/> dave.clucas@icloud.com <mailto:daveclucas@icloud.com> Exploring the World - One cave at a time
On 27 Apr 2015, at 04:11, therion-request@speleo.sk wrote:
Send Therion mailing list submissions to therion@speleo.sk
To subscribe or unsubscribe via the World Wide Web, visit http://mailman.speleo.sk/mailman/listinfo/therion or, via email, send a message with subject or body 'help' to therion-request@speleo.sk
You can reach the person managing the list at therion-owner@speleo.sk
When replying, please edit your Subject line so it is more specific than "Re: Contents of Therion digest..."
Today's Topics:
1. Re: Therion Digest, Vol 112, Issue 5 (Rob Countess) 2. Re: Therion Digest, Vol 112, Issue 5 (Bruce)
----------------------------------------------------------------------
Message: 1 Date: Sun, 26 Apr 2015 15:30:23 -0700 From: Rob Countess <rob.countess@gmail.com> Subject: Re: [Therion] Therion Digest, Vol 112, Issue 5 To: List for Therion users <therion@speleo.sk> Message-ID: <CAJJSGway102cCAHVUMhacaEsobRgyhAJn7WBd167chzLhRzeAQ@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
Bruce,
Again thanks for all your help.
In your attachment you had some mention of where to put low-level map definitions. Could you explain the benefits of placing map definitions: 1) in the file outside of surfer/endsurvery 2) in the file inside of at and the start of survey/endsurvey 3) in separate file
It seems like you've given this a lot of thought and would choose differently if you were starting out again and since I am just starting out I'd like to understand more.
Rob
The survey network and map hierarchies are then tied together in INDEX.th files
[If I were to start my 'Therion life' again, I would place the map definitions inside of, and at the start of the survey-endsurvey block to promote ease of use and simpler map references in INDEX files. The above structure was intended to make maps independent of surveys (which is preferred), but I did not think it through ? to achieve that we would have to have map definitions in separate files. Separate files would work OK, but would increase the number or size of files. At the time, we chose not to go this way. Another time, I might choose differently. Bruce]
On Sun, Apr 26, 2015 at 2:54 PM, Bruce <bruce@tomo.co.nz> wrote:
Rob
This is not a dataset, but it is an example of a file I have recently started placing at the top level of a survey project folder, to remind me and other users what conventions are used and preferred in a particular project. It might, indirectly, help you think about some of the considerations when starting a large project.
See attached.
Bruce
------------------------------
*From:* therion-bounces@speleo.sk [mailto:therion-bounces@speleo.sk] *On Behalf Of *Rob Countess *Sent:* Friday, 24 April 2015 7:58 a.m. *To:* List for Therion users *Subject:* Re: [Therion] Therion Digest, Vol 112, Issue 5
Does anyone mind sending me one of your data sets. It would help me understand the structure and organization.
I have data for several cave areas on Vancouver Island BC Canada in Walls and On Station. I want to convert the whole mess.
My data sets are
Glory 'ole/Arch Cave area
-18 km in 4 main caves and a dozen or so smaller caves linked by overland survey and GPS
- longest caves are Arch (10.6 km km 3 entrances), Glory 'ole (2.7 km) Pellucidar (1.9 km) Resonance (1.8 km)
- Arch cave is divided into several series based on streams and distinct areas of the cave
- 3 caves (Glory 'ole, Resonance, and Arch) overlap in plan view (I want to produce a high level map with all three caves in different colours, initially just line plots but eventually real maps)
White Ridge
-7 km in 3 main caves and a half dozen smaller caves Linked by radio location and GPS
Larch Mountain
2 km in 3 main caves and a dozen smaller caves linked by GPS
I also have a friend that manages data for Weymer Creek (over 30 km in over 100 caves, longest are 12 and 9 km lots of caves overlap in plan view). I am trying to convince him to switch to Therion too.
I am looking for an example data set that has
1) multiple caves in one caving area
2) at least one cave large enough to be broken into series
3) overlapping layers in at least one of the caves
4) examples of files to produces different outputs with overlapping caves or cave series in different colours on the same map.
Thanks,
Rob Countess
PS If you don't want to spam the mailing list then send to:
rob.countess@gmail.com
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion