-
Notifications
You must be signed in to change notification settings - Fork 15
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
Starttime parameter confusion for station service #140
Comments
👍 Just ran into this issue using what worked in #129 before, and does not work now. |
@nbalfour The horizontal line represents the metadata active period. And query parameters are arrows below. New implementation: |
From @calum-chamberlain 's comment I think what we're expecting becomes (from the algorithm level): Include a station if its end time is after the "startTime" query parameter.Is that right? |
That sounds right. |
@junghao yes that is right |
@nbalfour @calum-chamberlain
Then startTime is a duplicate for endBefore. |
Fix query start/end time as discussed in #140.
Check the service and it's working as excepted. Thank you. |
The FDSN specification is a bit confusing when it comes to how it deals with starttime for the station service. See this thread http://www.fdsn.org/message-center/thread/176/
The main point is the last sentence in the paragraph under Time Parameter Interpretation.
"The selection shall include any metadata epochs intersecting with the specified time range."
This implies that as long as a station's status is open at the start of the time period it should be returned.
Our current implementation of starttime for the station service only returns stations that open after or at starttime.
Can we please change the the starttime for the station service to include all stations open at starttime.
The text was updated successfully, but these errors were encountered: