The fdsnstationxml xschema shows that the "number" attribute on a
<ResponseStage> is a CounterType, which is an integer with <xs:minInclusive
value="0"/>. However, general usage, and the output from the web service
generally count stages starting at 1. Might be nice to have the schema
enforce this convention by having a separate counter type that starts at 1
for the cases where that makes sense. Especially since the seed usage of
stage zero meaning "overall gain" would be confusing if someone indexed
their ResponseStages starting at zero per the xschema.
thanks
Philip
<ResponseStage> is a CounterType, which is an integer with <xs:minInclusive
value="0"/>. However, general usage, and the output from the web service
generally count stages starting at 1. Might be nice to have the schema
enforce this convention by having a separate counter type that starts at 1
for the cases where that makes sense. Especially since the seed usage of
stage zero meaning "overall gain" would be confusing if someone indexed
their ResponseStages starting at zero per the xschema.
thanks
Philip
-
And just to make sure I understand, in fdsnstationxml, there should never
be a <ResponseStage> with number="0", correct? In the old seisFile, I had
code that would check for a stage zero for overall sensitivity, but I think
that should no longer be needed.
Philip
On Tue, Apr 9, 2013 at 5:39 PM, Philip Crotwell <crotwell<at>seis.sc.edu>wrote:
The fdsnstationxml xschema shows that the "number" attribute on a
<ResponseStage> is a CounterType, which is an integer with <xs:minInclusive
value="0"/>. However, general usage, and the output from the web service
generally count stages starting at 1. Might be nice to have the schema
enforce this convention by having a separate counter type that starts at 1
for the cases where that makes sense. Especially since the seed usage of
stage zero meaning "overall gain" would be confusing if someone indexed
their ResponseStages starting at zero per the xschema.
thanks
Philip
-
Hi
Following up, I found this in the comments. Sorry, I should read more
carefully, but I think this is a leftover comment from the old station xml
as the same text appears in the old stationxml schema doc? Presumably you
would not have deprecated features in a brand new schema? Can you clarify?
In this schema, stage 0 gains are allowed but are considered deprecated.
thanks
Philip
On Wed, Apr 10, 2013 at 8:01 AM, Philip Crotwell <crotwell<at>seis.sc.edu>wrote:
And just to make sure I understand, in fdsnstationxml, there should never
be a <ResponseStage> with number="0", correct? In the old seisFile, I had
code that would check for a stage zero for overall sensitivity, but I think
that should no longer be needed.
Philip
On Tue, Apr 9, 2013 at 5:39 PM, Philip Crotwell <crotwell<at>seis.sc.edu>wrote:
The fdsnstationxml xschema shows that the "number" attribute on a
<ResponseStage> is a CounterType, which is an integer with <xs:minInclusive
value="0"/>. However, general usage, and the output from the web service
generally count stages starting at 1. Might be nice to have the schema
enforce this convention by having a separate counter type that starts at 1
for the cases where that makes sense. Especially since the seed usage of
stage zero meaning "overall gain" would be confusing if someone indexed
their ResponseStages starting at zero per the xschema.
thanks
Philip
-