-
Notifications
You must be signed in to change notification settings - Fork 8
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
Distance between Sta and Cha issue #142
Comments
@stephanezuzlewski is the distance between the station and channel 1 KM apart in the X-Y plane or is it in the Z plane? Are these MagnetoTelluric data? We can consider softening this rule into a warning. This rule has helped us catch a number of typos in latitudes and longitudes so it should not be removed altogether. Thanks for providing some additional details and thanks for bringing this issue to our attention. |
@timronan They could be apart either in the X-Y plane (in the case of a dam) or in the Z plane (in the case of a borehole site). The specific example I mentioned is an EM channel at a borehole site in Parkfield. But there are also NSMP dam structure arrays where the distance between the station and the channel is over 1 KM. |
Hi, the validator is flagging our multi-sensor array sites (bridge and dam arrays) with error messages like “222,Error,NP,1035,,,1998-08-15T18:00:00,,Distance between Sta: 1035 and Chan: HN2 Loc: AA is expected to be less than 1 km but is 1.3460944237526158 km.” This is making it complicated to push new stations to production entered in SIS (which is using this validator for checks) and also streaming NP dam and bridge data to IRIS. Would it be possible to use the COSMOS codes for dams, bridges, geotechnical array sites to allow these sites to be accepted and not flagged by the validator. As a program focused on monitoring structures at the NSMP (NP array) we have many with this flag and it would be great to resolve them. Here is a current error list:
|
Thank for this example. We will soften this rule from an error to a warning in the next stationxml-validator update. We will get begin working on a release candidate, and will let everyone know know when it is ready. |
Thanks so much @timronan! |
@stephanezuzlewski and @lschleicher stationxml-validator 1.7.2 has been released and addresses this issue by turning rule 222 from an error into a warning. The stationxml-loader has also been updated to include this changed rule. Please close this issue after you verify the update. Sorry for the delay on dealing with this issue. https://github.com/iris-edu/stationxml-validator/releases/tag/stationxml-validator-1.7.2 |
We have several sites (e.g. boreholes, dams) where the distance between the station and a given channel is well over 1 KM.
222,Error,BK,PKD1,,,1992-10-21T00:00:00,2000-10-01T23:59:00,Distance between Sta: PKD1 and Chan: BQ2 Loc: is expected to be less than 1 km but is 12.111411437028966 km
Those distances are indeed correct and should not be flagged as an error.
The text was updated successfully, but these errors were encountered: