Open damb opened 4 years ago
In general, the federator can only support request parameters which are supported by all federated services, otherwise the response is unpredictible for the user (the same query parameter set would cause different service behaviour if applied to a different geographic area).
my original question: Question:
I can see all stations if I make a simple query: http://federator-testing.ethz.ch/fdsnws/station/1/query?network=Z3&level=station&format=text
if I restrict to a givenon-date, I only get RESIF stations. http://federator-testing.ethz.ch/fdsnws/station/1/query?network=Z3&level=station&format=text&startafter=2010-01-01
Is this a known limitation?
Note this query works fine directly at the host nodes that also use the SC3 version, eg ETH: http://eida.ethz.ch/fdsnws/station/1/query?network=Z3&level=station&format=text&startafter=2010-01-01
Apparently, the
fdsnws-station
specific time constraint query filter parametersstartbefore
,startafter
,endbefore
andendafter
are not consumed and processed by allfdsnws-station
implementations at EIDA DCs in the same way.The specs mention the parameters with:
When executing a HTTP POST request including one of the filter parameters mentioned above, SC3
fdsnws-station
implementations return HTTP status code 400:In contrast, the
fdsnws-station
implementation of RESIF does allow these additional time constraint filter query parameters.Though, allowing both the query filter parameters
startbefore
,startafter
,endbefore
,endafter
andstarttime
andendtime
parameters is somehow redundant and cumbersome.At the time being,
eida-federator
is simply forwarding the parameters tofdsnws-station
endpoint resources.Question: What implementation should
eida-federator
follow in order to provide the best user experience?Thanks for reporting, @jfclinton.