<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: NextGen EQMaps Beta</title></head><body>
<div>Thanks, Lisa! Sorry to bother you about a resolved issue.</div>
<div><br></div>
<div>So the floor is now M=0? I assume that will satisfy folks. I
actually have no idea whether the network locates earthquakes
M<0!</div>
<div><br></div>
<div>Mike</div>
<div><br></div>
<blockquote type="cite" cite>The omission of M<1 earthquakes was an
error on our part. We fixed that one immediately. If you
take a look at the Beta maps now, you'll see all the M<1
earthquakes on them already.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite><a
href="http://earthquake.usgs.gov/earthquakes/mapping/"
>http://earthquake.usgs.gov/earthquakes/mapping/</a><br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>- Lisa</blockquote>
<blockquote type="cite" cite>------</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite><br>
<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>On Dec 3, 2010, at 12:45 PM, Michael
Blanpied wrote:</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Lisa,</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Thanks very much for the feedback and
summary! It's great to know that you're making progress on the new
maps, and that you've found a suitable way around the Google
impediments.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>One point that I don't see on your list
is the question of M<1 earthquakes. Our colleagues with interests
in central California and in volcanic areas are very keen to see the
magnitude floor removed from the maps. This has been brought to my
attention a couple of times now, so I'd appreciate hearing the status
of that issue so that I'll know how to respond next time it comes
up.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Thanks again,</blockquote>
<blockquote type="cite" cite>Mike</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>At 10:49 AM -0700 12/3/10, Lisa A Wald
wrote:<br>
<blockquote type="cite" cite>Everyone-<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Thank you for your feedback, comments,
and suggestions about the Next Generation Earthquake Maps for the EHP
website.<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>The Web Team has compiled the various
comments, weighted them according to how many times we received the
same comment, and we are currently addressing all the comments
starting with those with the highest priority.<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Because of Google licensing issues with
our high web traffic to the EQ Maps, we are having to move to another
client-side software, OpenLayers API. I think you'll agree that
OpenLayers is every bit as good, if not better, than Google Maps (and
it doesn't preclude us from using Google Maps API in the future if the
licensing issue is resolved).<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>These are some of the tasks we're working
on to address your concerns before the Public Beta is launched in
January:<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>1. Remove clustering algorithm, or allow
user to turn it on and off; add cluster symbol to map key.<br>
</blockquote>
<blockquote type="cite" cite>2. Add links to event pages from event
table below map; turn off dbl-click on event symbol on map.<br>
</blockquote>
<blockquote type="cite" cite>3. Implement full-page-size map.<br>
</blockquote>
<blockquote type="cite" cite>4. Add magnitude to hover text.<br>
</blockquote>
<blockquote type="cite" cite>5. Change labeling from "Event"
to "Earthquake".<br>
</blockquote>
<blockquote type="cite" cite>6. Add user guide for features that are
not intuitively obvious.<br>
</blockquote>
<blockquote type="cite" cite>7. Use our own basemaps, cities, list,
etc instead of the build-in data provided by Google Maps.<br>
</blockquote>
<blockquote type="cite" cite>8. Other small changes such as scale bar,
lat/lon of mouse position.<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Additional features, such as faults with
mouse-over info, volcano locations, caldera boundaries, etc. will be
added in the future, potentially before the final public release.
We'll have a mechanism in place to receive comments on the next
beta version too.<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Thanks for helping to make this an
outstanding product!<br>
</blockquote>
<blockquote type="cite" cite><font
face="Verdana">- </font>Lisa<font face="Verdana"><br>
<font color="#008500">--------------------------<br>
Lisa Wald, Geophysicist</font></font><br>
</blockquote>
<blockquote type="cite" cite><font face="Verdana" color="#008500">Web
Team Manager/Project Manager<br>
USGS Earthquake Hazards Program<br>
Golden, CO<br>
303-273-8543<br>
</font><a href="mailto:lisa@usgs.gov"><font face="Verdana"
color="#008500">lisa@usgs.gov</font></a><br>
</blockquote>
<blockquote type="cite" cite>--------------------------</blockquote>
</blockquote>
<div><br></div>
</body>
</html>