<div dir="ltr"><div>Hi Bruce,</div><div> </div><div>Thank you very much for tracking this down for me and for the excellent explanation on what was ocurring. We have modified our end to prepare for both names.</div><div>As a related question, is there a difference between mi (macroseismic intensity) and mmi (modified mercalli intensity)? Is mmi a subset of mi?</div>
<div> </div><div>Many Thanks,</div><div>Matt</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 3:24 PM, C. Bruce Worden <span dir="ltr"><<a href="mailto:cbworden@usgs.gov" target="_blank">cbworden@usgs.gov</a>></span> 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">Hi Matt,<div><br></div><div>I've discussed this with the NC operations personnel and they're changing from 'mmi' to 'mi' in the shape.zip file, effective more or less immediately. Note that the change will only be going forward, so the mmi filenames will persist in the shape.zip archives of older events until and unless those events are reprocessed.</div>
<div><br></div><div>The reason for the difference in names was that NC needed to support another piece of software that required 'mmi' rather than 'mi'. Eventually that software was updated, but the naming convention persisted. Since other networks use that same software, you should be prepared to see either 'mmi' or 'mi' in their shape files.</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>Bruce</div><div><br></div><div><br></div></font></span><div><div><div><div>On Aug 25, 2014, at 11:49 AM, "Fee, Jeremy" <<a href="mailto:jmfee@usgs.gov" target="_blank">jmfee@usgs.gov</a>> wrote:</div>
<br></div><div><div class="h5"><blockquote type="cite"><div dir="ltr">Hi Matt,<div><br></div><div>This looks like a difference between "us" and "nc" ShakeMap providers. I've cc'ed Bruce Worden who can look into this issue and respond.</div>
<div><br>
</div><div><br></div><div>Thanks,</div><div><br></div><div>Jeremy</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 25, 2014 at 12:16 PM, Matt W. <span dir="ltr"><<a href="mailto:maw269@gmail.com" target="_blank">maw269@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div dir="ltr">We rely on the USGS Earthquake Realtime Feed (GeoJSON).<div>
<br></div><div>We have found an inconstancy in one of your latest products.</div>
<div><br></div><div>If you download the shape.zip from:</div><div>
<div>M6.9 - 43km ENE of Tambo, Peru</div><div><a href="http://earthquake.usgs.gov/earthquakes/feed/v1.0/detail/usb000s5x1.geojson" target="_blank">http://earthquake.usgs.gov/earthquakes/feed/v1.0/detail/usb000s5x1.geojson</a></div>
<div>
<br></div><div>Then</div><div><a href="http://earthquake.usgs.gov/product/shakemap/usb000s5x1/us/1408925670763/download/shape.zip" target="_blank">http://earthquake.usgs.gov/product/shakemap/usb000s5x1/us/1408925670763/download/shape.zip</a></div>
</div><div><br></div><div>The Intensity dbf file is named: mi.dbf</div><div>______________________________</div><div>If you download the shape.zip from:</div><div><div>M 6.0 - 6km NW of American Canyon, California</div><div>
<a href="http://earthquake.usgs.gov/earthquakes/feed/v1.0/detail/nc72282711.geojson" target="_blank">http://earthquake.usgs.gov/earthquakes/feed/v1.0/detail/nc72282711.geojson</a></div><div><br></div><div>Then</div><div>
<a href="http://earthquake.usgs.gov/product/shakemap/nc72282711/nc/1408983729833/download/shape.zip" target="_blank">http://earthquake.usgs.gov/product/shakemap/nc72282711/nc/1408983729833/download/shape.zip</a></div>
</div><div><br></div><div>The Intesity dbf file is named: mmi.dbf</div><div><br></div><div>This has caused issues in our use of the feed.</div><div><br></div><div>In this file:</div><div><a href="http://earthquake.usgs.gov/product/shakemap/usb000s5x1/us/1408925670763/download/metadata.txt" target="_blank">http://earthquake.usgs.gov/product/shakemap/usb000s5x1/us/1408925670763/download/metadata.txt</a><br>
</div><div><br></div><div>The description states the dbf should be named mmi.dbf :</div><div>" Detailed_Description:</div><div> Entity_Type: </div><div> Entity_Type_Label: mmi.dbf (shapefile from "shape.zip" download file)</div>
<div> Entity_Type_Definition: Polygons of estimated instrumental intensity</div><div> Entity_Type_Definition_Source: ESRI Shapefile Technical Description "</div><div><br></div><div>However, we have found the normal name of the file is mi.dbf</div>
<div>As in this post: <a href="https://geohazards.usgs.gov/pipermail/shake-dev/2011-June/000368.html" target="_blank">https://geohazards.usgs.gov/pipermail/shake-dev/2011-June/000368.html</a></div><div><br></div><div>What is the standard name of the mi.dbf (mmi.dbf) located in the shape.zip and what should we be expecting?</div>
<div>Can you please explain why the recent California earthquake had a mmi.dbf file as opposed to a mi.dbf file?</div><div><br></div><div>Thanks,</div><div><br></div><div>Matt</div><div><br></div></div>
<br>_______________________________________________<br>
Realtime-feed-users mailing list<br>
<a href="mailto:Realtime-feed-users@geohazards.usgs.gov" target="_blank">Realtime-feed-users@geohazards.usgs.gov</a><br>
<a href="https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users" target="_blank">https://geohazards.usgs.gov/mailman/listinfo/realtime-feed-users</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div></div><br></div></div></blockquote></div><br></div>