jbnkwsk
September 23, 2022, 7:24am
1
Hi ObsPy team,
My name is Jarek Bienkowski, I’m currently chairing the EIDA IDG. I would like to ask you a question related to the developments of the new StationXML scheme (v1.2). The 12 data centers comprising EIDA federation are planning to switch to this new scheme in coming weeks and we are in the process of assessing its impact on our users and downstream services. We have already tested the current ObsPy version compatibility with StationXML 1.2 and it seems to be working thanks to the nature of the scheme changes (mostly minor and cosmetic), but we have been wondering if this work requires coordination with, perhaps, new ObsPy version that officially supports schema 1.2. Please let me know what is your opinion/suggestion here.
Reference: StationXML changes from version 1.1 to 1.2
Regards,
Jarek
1 Like
megies
September 27, 2022, 1:47pm
2
Thanks for the heads-up @jbnkwsk ! This actually required (minimal) changes going forward so upcoming ObsPy releases will not hickup on 1.2 files.
About to be included in soon-to-be-releases bug fix version 1.3.1 and subsequent feature release 1.4.0.
obspy:maintenance_1.3.x ← obspy:stationxml12
opened 01:40PM - 27 Sep 22 UTC
### What does this PR do?
Bump StationXML to schema version 1.2, which claims… to have no semantic changes, only additions to the inline documentation in the XSD schema.
- put 1.2 as schema version when writing stationxml
- make sure we don't refuse to read StationXML 1.2
- add 1.2 XSD schema file for validation
### Why was it initiated? Any relevant Issues?
- see [Our Forum](https://discourse.obspy.org/t/eida-moving-to-stationxml-1-2/1507)
- see [FDSN "What's New"](https://docs.fdsn.org/projects/stationxml/en/latest/overview.html#changes-from-version-1-1-to-1-2-2022-2-25)
- closes #2993
### PR Checklist
- [x] Correct base branch selected? `master` for new features, `maintenance_...` for bug fixes
- [x] This PR is not directly related to an existing issue (which has no PR yet).
- [ ] If the PR is making changes to documentation, docs pages can be built automatically.
Just add the "build_docs" tag to this PR.
Docs will be served at [docs.obspy.org/pr/{branch_name}](https://docs.obspy.org/pr/) (do not use master branch).
Please post a link to the relevant piece of documentation.
- [ ] If all tests including network modules (e.g. `clients.fdsn`) should be tested for the PR,
just add the "test_network" tag to this PR.
- [ ] All tests still pass.
- [ ] Any new features or fixed regressions are covered via new tests.
- [ ] Any new or changed features are fully documented.
- [x] Significant changes have been added to `CHANGELOG.txt` .
- [x] First time contributors have added your name to `CONTRIBUTORS.txt` .
- [ ] If the changes affect any plotting functions you have checked that the plots
from all the CI builds look correct. Add the "upload_plots" tag so that plotting
outputs are attached as artifacts.
- [ ] Add the "ready for review" tag when you are ready for the PR to be reviewed.
Perfectly clear. Thank you, @megies !