Yes, I think that is the conclusion I came to. Bruce
_____ From: therion-bounces at speleo.sk [mailto:therion-boun...@speleo.sk] On Behalf Of Martin Sluka Sent: Monday, 27 April 2015 6:47 p.m. To: List for Therion users Subject: Re: [Therion] Therion Digest, Vol 112, Issue 5 27. 4. 2015 v 5:42, Bruce <bruce at tomo.co.nz>: So, Low level map (ie first stage collection of scraps into usable maps) definitions; 1) in the survey.th <http://survey.th/> file outside of survey/endsurvey: Bruce, I apologize myself, but I think this not the best idea. Either such a definitions of maps are inside of survey-endsurvey section of upper level. But in this case there is VERY difficult to change anything in the lowest level of survey-endsurvey and not to correct other informations connected with such a change. Therion uses "name spaces" (or "branches") where you may identify any object in such name space by the "path" to it. So if you "tune" or "debug" maps in the lowest level of survey-endsurvey structure, that one where are surveying data, maps definitions should be in this survey-endsurvey section. In second level of survey-endsurvey structure you "input" only .th files, not .th2 ones which are yet "inputed" in the lowest level of survey-endsurvey section and as such by "inputing" of .th file the input includes .th2 too. It has one VERY important advantage: I have to NEVER rename the stations from 1 to 1 at survey1 if you call scraps from upper level of survey-endsurvey section. Instead you call scrap1 at survey1 or map1 at survey1 and all station names and map definitions stay unchanged. Any object of the lowest level (lines IDs, .) you may "call" in such a way. m.s. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150427/0fa743fd/attachment.html>
