You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2023. It is now read-only.
The FDSN webservice generates QuakeML with latitude and longitude uncertainties in km. However, the QuakeML latitude and longitude are in degrees and we can therefore think that the uncertainty should also be in degrees.
This unit conversion issue also exists in the XSLT files but it's much harder to fix. The conversion from km to degrees involves some cosine computation that isn't available in the XSLT stylesheet. I don't know how we can do this properly.
The text was updated successfully, but these errors were encountered:
Agree, it is confusing. It would be nice that either QuakeML specifies that latitude / longitude uncertainties are in km, or that SC3's fdsnws does the conversion to degrees.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The FDSN webservice generates QuakeML with latitude and longitude uncertainties in km. However, the QuakeML latitude and longitude are in degrees and we can therefore think that the uncertainty should also be in degrees.
This unit conversion issue also exists in the XSLT files but it's much harder to fix. The conversion from km to degrees involves some cosine computation that isn't available in the XSLT stylesheet. I don't know how we can do this properly.
The text was updated successfully, but these errors were encountered: