Earthquake AnalystYour source for official seismic data.Analyzed | Visualized | ExplainedAnalyzed | Visualized | Explained
Earthquakes

Query appendix — implementation facts

Verified against release 2.1.0 source on September 30, 2026. Optional parameters are sent only when supplied or needed by the selected task; requests include explicit format/pagination defaults. Internal field names can differ from the provider parameter names below.

ProviderParameters or path selection sent
USGS / EMSC / GEOFON catalogformat, starttime, endtime, minmagnitude, limit, offset, nodata, optional latitude, longitude, maxradiuskm, minlatitude, maxlatitude, minlongitude, maxlongitude
USGS current feedChosen magnitude/feed threshold and hour, day, week or month in the public feed path
USGS event detaileventid, format=geojson
USGS event productsExact HTTPS file URL listed by the retrieved event/product manifest. Product type/content key/version select that URL; no arbitrary URL proxy is offered
EMSC identifier associationsource_id, source_catalog, out_catalog=all, format=json, include_info=true
EarthScope station / instrument responsenet, sta, optional loc, cha, start, end, plus format, level, nodata
EarthScope waveformnet, sta, loc, cha, start, end, format, nodata; station metadata is also queried to preserve network citations
NWSstatus=actual, selected tsunami event, optional area, point as latitude/longitude, cursor
NTWC / PTWCSelected center's fixed CAP or Atom bulletin path; no user-location parameter is sent to these bulletin files
NOAA NCEI historical eventsminYear, maxYear, optional country, itemsPerPage, page
NOAA NCEI runupstsunamiEventId, itemsPerPage, page
Copernicus Rapid / Risk-RecoveryService family in the endpoint; category=EARTHQUAKE for discovery, optional code, search, plus limit, offset
NASA EONETcategory, status, limit, optional start, end date strings
USGS WaterDataCollection path; station-specific item path or monitoring_location_id, parameter_code, optional cursor, time, plus f=json, limit

A point used to inspect a previously downloaded ShakeMap grid is processed in the application; the upstream request is for the manifested grid file. Waveform detrending/tapering and card/map drawing also happen in the application rather than at a third-party image service.

Outgoing scientific-data requests use GET with fixed application User-Agent and Accept headers. They do not forward the visitor's account identifier, email, name, cookies, access token, authorization header or full chat text. The network provider and hosting infrastructure still handle normal request metadata.

Share-page/PNG requests are different: they send the bounded encoded public event snapshot to this application's own host. They do not query scientific providers or accept arbitrary upstream URLs.