Skip to content
This repository has been archived by the owner on May 10, 2023. It is now read-only.

Populate unit field of amplitude measurement #243

Closed
calum-chamberlain opened this issue Sep 11, 2019 · 6 comments
Closed

Populate unit field of amplitude measurement #243

calum-chamberlain opened this issue Sep 11, 2019 · 6 comments

Comments

@calum-chamberlain
Copy link

calum-chamberlain commented Sep 11, 2019

Hi all, I'm not a Seiscomp user myself, but I do make heavy usage of the GeoNet (New Zealand) catalogue, which is built using Seiscomp. Their catalogue is missing units for amplitude measurements (see this issue): looking at the QuakeML docs it looks like the units for amplitudes should be SI, but those in the GeoNet catalogue are in either mm or mm/s and the unit field of the amplitude is not populated. It would be really handy if this was populated, and the QuakeML spec encourages it.

As an extra - can the methodID field also be populated with a link to the appropriate page in the seiscomp docs for various fields so that catalogue users can easily find how processing was undertaken?

@gempa-jabe
Copy link
Member

That is implemented for quite some time now, see https://github.com/SeisComP3/seiscomp3/blob/build/jakarta/2018.327/src/trunk/libs/seiscomp3/datamodel/exchange/quakeml.cpp#L857. I don't know how GeoNet creates their QuakeML files. If they use the built-in QuakeML converter (C++) then it should work as expected.

@calum-chamberlain
Copy link
Author

Thanks for that! I don't know either, I will chase more on their end! Thanks for your patience. Happy to close this.

@calum-chamberlain
Copy link
Author

Actually I might leave this open in case @salichon wants to comment.

@salichon
Copy link
Contributor

salichon commented Sep 11, 2019

Great thanks @calum-chamberlain @gempa-jabe - i ll follow up on this and see how indeed it s been implemented into the Geonet quakeml services (hence not the sc3 built in quakeml converter most likely).
Cf: GeoNet/help#60
Cheers
jerome

@salichon
Copy link
Contributor

salichon commented Sep 11, 2019

I verified that our process is not converting into SI units and unit labeeling
Our conversion would benefit from these kind improvements ! :) - or use the built in conversion

@salichon
Copy link
Contributor

  • I think this issue can be closed -> related to our external on-the-fly conversion process

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants