Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

particle_single_constituent_name #15

Closed
stefankneifel opened this issue May 14, 2018 · 1 comment · Fixed by #33
Closed

particle_single_constituent_name #15

stefankneifel opened this issue May 14, 2018 · 1 comment · Fixed by #33
Assignees
Labels

Comments

@stefankneifel
Copy link
Collaborator

I don't really understand why we put the constituent name into a single attribute (particle_single_constituent_name) and not a variable as in the Excel table particle_constituent_name(particle_constituent_number)? Again, for just one constituent it doesn't really matter but if I have 2 or 3 I have to generate more and more new attributes instead of having one variables which contains them all.

@rhoneyager
Copy link
Owner

I haven't yet merged my improvements to the HDF5 backend; until then we can't easily write tables of strings. It's in progress.

@rhoneyager rhoneyager self-assigned this May 14, 2018
@rhoneyager rhoneyager added this to Being worked on now in Shape file import via automation May 14, 2018
@rhoneyager rhoneyager moved this from Being worked on now to Done in Shape file import Sep 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

2 participants