Is survey -namespace off and sometimes on possible in same survey project?
Just a quick question before contemplating the migration of a large (more than 70 km and many caves) dataset to Therion. The dataset has unique station names, so in Therion speak, every survey would have -namespace off set. I have never used this setting, but do not anticipate any problem so long as every survey has -namespace off set. The trick is that there are two caves that have been processed from the very start with Therion (using the default -namespace on, of course) and one of the large caves has a currently 'not-incorporated' section of Therion namespaced data. None of this Therion data is currently incorporated in the large dataset. There will probably be more namespaced data in future. So my question is: Can we have an integrated Therion project where some surveys have -namespace on and some with -namespace off? I imagine this will work, but having never tried it I am cautious about diving into such a large undertaking, in case it is doomed to failure because of a requirement for significant manual intervention (I did that for 30 km of the system, but I have lost enthusiasm for that). Bruce
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Em domingo, 14 de novembro de 2021 às 2:10 AM, Bruce Mutton <bruce@tomo.co.nz> escreveu:
Just a quick question before contemplating the migration of a large (more than 70 km and many caves) dataset to Therion.
The dataset has unique station names, so in Therion speak, every survey would have -namespace off set.
Sorry for the slightly off topic reply but AFAIU your dataset having station unique names allows you to set -namespace off which could save some work but you don't have to and as you already know that some other parts of your dataset needs -namespace on, why bother with -namespace off? Regards, Rodrigo
Em domingo, 14 de novembro de 2021 às 2:10 AM, Bruce Mutton <bruce@tomo.co.nz> escreveu:
Just a quick question before contemplating the migration of a large (more than 70 km and many caves) dataset to Therion.
The dataset has unique station names, so in Therion speak, every survey would have -namespace off set.
Sorry for the slightly off topic reply but AFAIU your dataset having station unique names allows you to set -namespace off which could save some work but you don't have to and as you already know that some other parts of your dataset needs -namespace on, why bother with -namespace off?
Because the existing dataset that it is proposed to migrate (using a custom script): - is large with many surveys and sub-surveys - Therion implicitly defaults to -namespace on for every single survey - with that setting, survey stations, although unique across surveys, cannot be seen unless a namespace is specified - therefore it will not compile until -namespace off is set in each relevant survey and sub-survey. A decade ago, before I was particularly aware of 'survey -namespace', I migrated this same dataset, and not being aware I could turn it off, had to manually equate stations to join all the surveys, and equate loops where they involved more than one survey. I only did half of it before I got fed up. I realise now that -namespace off is the solution, and that it can be put in the custom script. But in the meantime I have some native Therion sub-projects that I want to merge into the migrated project, that, of course, use and rely on the implicit default of -namespace on because the stations are not unique (each survey has the station sequence 1 2 3 4 ...). I do not have an appetite to manually make these stations unique, even using -station-names to modify them it will be too painful. Hence I am testing the idea of projects where some surveys have -namespace on and some -namespace off. I could modify one of my existing projects to see what happens, but before doing that I am interested to find out if others have experience with this scenario. Regards Bruce
Hi Bruce, as far as I know, namespace could be specified for individual surveys. I am just afraid, this feature has not been tested a lot, so please let me know if some unexpected behavior occurs. Thanks, S. On Sun, 14 Nov 2021 at 20:09, Bruce Mutton <bruce@tomo.co.nz> wrote:
Em domingo, 14 de novembro de 2021 às 2:10 AM, Bruce Mutton < bruce@tomo.co.nz> escreveu:
Just a quick question before contemplating the migration of a large (more than 70 km and many caves) dataset to Therion.
The dataset has unique station names, so in Therion speak, every survey would have -namespace off set.
Sorry for the slightly off topic reply but AFAIU your dataset having station unique names allows you to set -namespace off which could save some work but you don't have to and as you already know that some other parts of your dataset needs -namespace on, why bother with -namespace off?
Because the existing dataset that it is proposed to migrate (using a custom script): - is large with many surveys and sub-surveys - Therion implicitly defaults to -namespace on for every single survey - with that setting, survey stations, although unique across surveys, cannot be seen unless a namespace is specified - therefore it will not compile until -namespace off is set in each relevant survey and sub-survey.
A decade ago, before I was particularly aware of 'survey -namespace', I migrated this same dataset, and not being aware I could turn it off, had to manually equate stations to join all the surveys, and equate loops where they involved more than one survey. I only did half of it before I got fed up. I realise now that -namespace off is the solution, and that it can be put in the custom script. But in the meantime I have some native Therion sub-projects that I want to merge into the migrated project, that, of course, use and rely on the implicit default of -namespace on because the stations are not unique (each survey has the station sequence 1 2 3 4 ...). I do not have an appetite to manually make these stations unique, even using -station-names to modify them it will be too painful.
Hence I am testing the idea of projects where some surveys have -namespace on and some -namespace off. I could modify one of my existing projects to see what happens, but before doing that I am interested to find out if others have experience with this scenario.
Regards Bruce
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
participants (3)
-
Bruce Mutton -
rsev＠protonmail.com -
Stacho Mudrak