Both (all?) approaches discussed have merit, and could be considered 'correct' in varying circumstances.
We already have a revise statement and a person-rename statement, so lets figure out if they can be used 'as is' for Benedikts purposes, and if not if there is an acceptable change that could be made. I like the idea of merging multiple persons in 'club groups' as was suggested earlier, as for large overview maps this makes the header a smaller more manageable size, without the need for manual edits. I have used revise to change station-names at compile time, where scraps are drawn spanning multiple surveys and -station-names have been used in the original centrelines. Ie https://therion.speleo.sk/wiki/paperless?s[]=revise <https://therion.speleo.sk/wiki/paperless?s%5b%5d=revise> Also to reuse a projected elevation scrap as an extended elevation (where the projection angle is perpendicular to the passage). I have explored it's use when creating multiple extended elevations of different configuration (left, right, hide etc) from the same centreline data (forget if I ended up using revise for this or not). It can be used to alter map definitions at compile time (according to the Therion Book). So there is already the generic precedent and capability. There must be many other possible uses. >From the Therion Book. revise Description: This command is used to set or change properties of an already existing object. Syntax: The syntax of this command for object created with "single line" command is revise id [-option1 value1 -option2 value2 ...] For objects created with "multi line" commands is syntax following revise id [-option1 value1 -option2 value2 ...] ... optionX valueX data ... endrevise Context: all Arguments: The id stands for object identifer (the id of an object you want to revise must always be specified). Bruce -----Original Message----- From: Therion [mailto:[email protected]] On Behalf Of Wookey via Therion Sent: Tuesday, 7 March 2017 1:58 AM To: Benedikt Hallinger via Therion <[email protected]> Cc: Wookey <[email protected]> Subject: Re: [Therion] Revise command: how to remove persons later on On 2017-03-05 19:30 +0200, Benedikt Hallinger via Therion wrote: > The same reason like already told in this thread: the data should > reflect otherwise recorded data. Right, but in this case they didn't actually turn up, so how is it correct to leave them as listed on the survey team? I, too, like to keep notes original, but when they are provably wrong they are changed (usually with a comment explaining the change from the original notes). This happens regularly for instrument readings, and sometimes for station conenctions. It can happen for team members too. Unless someone wants to propose a general 'revised notes' command, I don't think it makes sense to provide this for team members, but not readings, or indeed anything else. I can see that marking data as 'revised from original notes' might actually be useful (because that effectively makes it possible to show the 'thisa was revised' comments in some kind of UI). Wookey -- Principal hats: Linaro, Debian, Wookware, ARM <http://wookware.org/> http://wookware.org/
_______________________________________________ Therion mailing list [email protected] https://mailman.speleo.sk/listinfo/therion
