We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As for stationXML v1.x, epochs in a channel are defined as new channels.
What about modeling in the metadata that one channel has one or more epochs ? Like this 👍
<Channel> <Epoch starttime="" enddime=""> </Epoch> </Channel>
We could put everything defined in a channel v1.x inside of the Epoch element.
This would be more consistent with the classical data model and simplify metadata exploration.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As for stationXML v1.x, epochs in a channel are defined as new channels.
What about modeling in the metadata that one channel has one or more epochs ? Like this 👍
We could put everything defined in a channel v1.x inside of the Epoch element.
This would be more consistent with the classical data model and simplify metadata exploration.
The text was updated successfully, but these errors were encountered: