ok, sounds good. I will code for the fdsn version and assume you all work faster then I do. :)<span></span><div><br></div><div>thanks,</div><div>Philip<span></span><br><br>On Wednesday, March 13, 2013, Chad Trabant wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><div>Hi Philip,</div><div><br></div><div>This is a bug. We will fix this in our soon-to-be-released FDSN event web service. We will probably not change the current behavior of the production service as there are likely dependencies on how we are generating it now.</div>
<div><br></div><div>Thanks for reporting it. Somewhat surprising that it took this long to get noticed.</div><div><br></div><div>Chad</div><br><div><div>On Mar 13, 2013, at 11:41 AM, Philip Crotwell <<a>crotwell@seis.sc.edu</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div><div><div><div><div>Hi<br><br></div>The quakeml spec (1.2) says that this depth field in an origin is in meters.<br><br>
<div><p><span style="font-size:10pt;font-family:'CMSSBX10'">depth </span><span style="font-size:10pt;font-family:'CMSS10'">Depth of hypocenter with respect to the nominal sea level given by the WGS84 geoid (Earth Gravitational
Model, EGM96, </span><span style="font-size:10pt;font-family:'CMSS10';color:rgb(0,0,128)">Lemoine et al. 1998). </span><span style="font-size:10pt;font-family:'CMSS10'">Positive values indicate hypocenters below sea level. For shallow
hypocenters, the </span><span style="font-size:10pt;font-family:'CMSSBX10'">depth </span><span style="font-size:10pt;font-family:'CMSS10'">value can be negative. Note: Other standards use different conventions for depth
measurement. As an example, GSE2.0, defines depth with respect to the local surface. If event data is
converted from other formats to QuakeML, depth values may have to be modified accordingly.
</span></p><p><span style="font-size:10pt;font-family:'CMSSI10'">Unit: </span><span style="font-size:10pt;font-family:'CMSS10'">m
</span></p>
</div>
<br></div>But when I query the event ws, the values that come back look like they are in kilometers, ie 33 instead of 33000 like in this:<br><br><origin publicID="smi:<a href="http://www.iris.edu/ws/event/query?originId=4908125" target="_blank">www.iris.edu/ws/event/query?originId=4908125</a>" iris:contributor="NEIC PDE-M" iris:catalog="NEIC PDE"><time><value>1999-08-17T15:06:27.0700</value></time><creationInfo><author>NEIC</author></creationInfo><latitude><value>34.814</value></latitude><longitude><value>32.859</value></longitude><depth><value>33.0</value></depth></origin><br>
<br><br></div>QuakeML doesn't have a "units" field, so it can't just be labeled as "m" or "km".<br><br></div>Is this a bug, or is the iris ws just choosing to not follow the spec? <br>
<br></div>thanks<br>Philip<br></div>
_______________________________________________<br>webservices mailing list<br><a>webservices@iris.washington.edu</a><br>
<a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br></blockquote></div><br></div></blockquote></div>