addedInput schema / properties / magnitude_type
Added value: +{
+ "description": "Magnitude type, e.g. \"mb\" or \"mww\"; both sources. Blank means omitted.",
+ "type": "string"
+}
addedInput schema / properties / product_type
Added value: +{
+ "description": "Required product type, e.g. \"moment-tensor\"; USGS only. Blank means omitted.",
+ "type": "string"
+}
addedInput schema / properties / review_status
Added value: +{
+ "description": "USGS review status: automatic or reviewed. Blank means omitted; unsupported by EMSC.",
+ "type": "string"
+}
changedInput schema / properties / source / description
Previous value: -"Data source. Both catalogs are global. \"usgs\" covers global events with PAGER, DYFI, and ShakeMap metadata. \"emsc\" is an independent global catalog operated by the European-Mediterranean Seismological Centre — use it to cross-check any event, anywhere, against a separate network. It publishes no PAGER, DYFI, or ShakeMap metadata and no per-event detail endpoint; its station coverage is densest around Europe and the Mediterranean."New value: +"USGS includes PAGER, DYFI and ShakeMap; EMSC (European-Mediterranean Seismological Centre) is an independent global catalog, with densest station coverage around Europe/Mediterranean and no such impact products. Event-detail tool accepts USGS IDs only."
changedOutput schema / properties / countUnavailable / description
Previous value: -"True when the follow-up total-count query failed, so the total is unknown for this call rather than never requested. The returned events are complete and unaffected; only totalCount is missing. Retry earthquake_count_events with the same filters to recover the total. Absent whenever the count succeeded or was never needed."New value: +"True if the count lookup failed; events are unaffected, totalCount unknown. Retry earthquake_count_events with identical filters. Absent if count succeeded or was unnecessary."
changedOutput schema / properties / error / properties / data / properties / reason / description
Previous value: -"Machine-readable failure mode. Declared by this tool: `result_too_large`: One event or page metadata cannot fit the response budget. `invalid_radius`: latitude or longitude provided without radius_km, or vice versa. `invalid_bounding_box`: min_latitude exceeds max_latitude, or min_longitude exceeds max_longitude. `source_unavailable`: Selected source API returns a 5xx or is unreachable. `source_timeout`: Selected source API did not answer before the request deadline. `upstream_rejected`: The source API rejected the query parameters and explained why in its response body. `upstream_rejected_no_reason`: The source API rejected the query but its response body carried no usable explanation. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_range`: Minimum magnitude or depth exceeds its maximum, or start_time is after end_time. `result_too_large`: One event or page metadata cannot fit the response budget. `invalid_radius`: latitude or longitude provided without radius_km, or vice versa. `invalid_bounding_box`: min_latitude exceeds max_latitude, or min_longitude exceeds max_longitude. `source_unavailable`: Selected source API returns a 5xx or is unreachable. `source_timeout`: Selected source API did not answer before the request deadline. `upstream_rejected`: The source API rejected the query parameters and explained why in its response body. `upstream_rejected_no_reason`: The source API rejected the query but its response body carried no usable explanation. Other values are possible when a failure originates below the handler."
changedOutput schema / properties / error / properties / data / properties / reason / examples
Previous value: -[
- "result_too_large",
- "invalid_radius",
- "invalid_bounding_box",
- "source_unavailable",
- "source_timeout",
- "upstream_rejected",
- "upstream_rejected_no_reason"
-]New value: +[
+ "invalid_range",
+ "result_too_large",
+ "invalid_radius",
+ "invalid_bounding_box",
+ "source_unavailable",
+ "source_timeout",
+ "upstream_rejected",
+ "upstream_rejected_no_reason"
+]
changedOutput schema / properties / events / items / properties / alert / description
Previous value: -"PAGER estimated impact alert level. Null when USGS ran no PAGER assessment, and always null for EMSC, which publishes no such field."New value: +"PAGER estimated impact; null without an assessment or for EMSC."
changedOutput schema / properties / events / items / properties / auth / description
Previous value: -"Code of the agency or network the source names as authoritative for this solution, e.g. \"NEIC\", \"BMKG\", \"NDI\" from EMSC or \"us\", \"ci\", \"ak\" from USGS. Absent when the source reports none."New value: +"Authoritative agency/network code (EMSC auth or USGS net); absent if unpublished."
changedOutput schema / properties / events / items / properties / cdi / description
Previous value: -"Maximum reported intensity (Community Decimal Intensity, 0–12 scale), derived from DYFI responses. Null when USGS computed no DYFI intensity, and always null for EMSC, which publishes no such field."New value: +"Maximum DYFI Community Decimal Intensity (0–12); null if uncomputed or unsupported (EMSC)."
changedOutput schema / properties / events / items / properties / depth_km / description
Previous value: -"Hypocenter depth in kilometers. Shallow (<70 km), intermediate (70–300 km), or deep (>300 km). Null for historical events where depth was not measured."New value: +"Hypocenter depth in km; null if unmeasured."
changedOutput schema / properties / events / items / properties / event_certainty / description
Previous value: -"How certain the source is of event_type: \"known\" (asserted), \"suspected\", \"unknown\", or \"unreported\". EMSC publishes this as the first character of its event-type code — a suspected explosion is not a confirmed one, and this is the only field that says so. Absent for USGS, which publishes no certainty axis, and absent for an EMSC code outside the published nomenclature."New value: +"EMSC classification certainty: known (asserted), suspected, unknown, or unreported. Suspected is not confirmed. Absent for USGS and unrecognized EMSC codes."
changedOutput schema / properties / events / items / properties / event_type / description
Previous value: -"What kind of event this is, in one vocabulary whichever source served it — the QuakeML type names USGS publishes (\"earthquake\", \"quarry blast\", \"explosion\", \"ice quake\"). EMSC's two-character code is decoded to the same names, so the same event carries the same value from either source; how sure the source is rides on event_certainty instead. A code outside the published nomenclature is forwarded verbatim rather than guessed at. Not every record in either catalog is a tectonic earthquake. Absent when the source publishes no classification."New value: +"QuakeML classification (earthquake, quarry blast, explosion, etc.). EMSC codes decode to USGS names; unknown codes pass through verbatim. Certainty is separate. Absent if unpublished; either catalog includes non-tectonic events."
changedOutput schema / properties / events / items / properties / felt / description
Previous value: -"Number of DYFI (Did You Feel It?) responses. Null when USGS has received no reports for the event, and always null for EMSC, which publishes no DYFI field — a null is not evidence the event went unfelt."New value: +"DYFI (Did You Feel It?) response count; null if no USGS reports or source has no DYFI (EMSC). Null does not mean unfelt."
changedOutput schema / properties / events / items / properties / magnitude / description
Previous value: -"Preferred magnitude value. Null when no magnitude was computed for the event (the title renders it as \"M ?\")."New value: +"Preferred magnitude; null if not computed (title: \"M ?\")."
changedOutput schema / properties / events / items / properties / mmi / description
Previous value: -"Maximum ShakeMap instrumental intensity (Modified Mercalli, 0–12 scale). Null when USGS produced no ShakeMap for the event, and always null for EMSC, which publishes no such field."New value: +"Maximum ShakeMap Modified Mercalli intensity (0–12); null without a ShakeMap or for EMSC."
changedOutput schema / properties / events / items / properties / significance / description
Previous value: -"USGS significance score (0–2000+). Combines magnitude, felt reports, PAGER. Null when USGS computed no score, and always null for EMSC, which publishes no such field."New value: +"USGS significance (0–2000+), combining magnitude, felt reports and PAGER; null if uncomputed or for EMSC."
changedOutput schema / properties / events / items / properties / source_catalog / description
Previous value: -"Upstream catalog this solution came from, e.g. \"EMSC-RTS\" (EMSC real-time seismicity, revised as analysis continues). Absent for USGS, which publishes no catalog identifier on event records."New value: +"Solution catalog, e.g. EMSC-RTS (real-time, subject to revision). Absent for USGS."
changedOutput schema / properties / events / items / properties / status / description
Previous value: -"Human-review state: \"automatic\" (posted by automatic processing, not yet verified by a person), \"reviewed\" (examined by an analyst), or \"deleted\". Null when the source publishes no review status — EMSC does not, so treat an EMSC solution as unverified and subject to revision rather than final."New value: +"Review state: automatic (unverified), reviewed (analyst checked), or deleted. Null if unpublished (EMSC); such solutions remain unverified and subject to revision."
changedOutput schema / properties / events / items / properties / title / description
Previous value: -"Human-readable event summary, e.g. \"M 6.0 - 13 km S of Honaunau-Napoopoo, Hawaii\"."New value: +"Event summary, e.g. \"M 6.0 - Hawaii\"."
changedOutput schema / properties / events / items / properties / tsunami / description
Previous value: -"USGS tsunami flag: 1 for large events in oceanic regions, 0 otherwise. It is not a warning — USGS states the flag does not indicate whether a tsunami did or will exist; check NOAA (tsunami.gov) for actual alert status. Null when the source publishes no such flag, as EMSC does not."New value: +"USGS tsunami flag: 1 for large oceanic events, 0 otherwise; null if unpublished (EMSC). Not a warning or evidence of a tsunami; check NOAA tsunami.gov for alerts."
changedOutput schema / properties / nextOffset / description
Previous value: -"Value to pass as the offset input to retrieve the next page, with every other input unchanged. Present when more events remain or may remain with an unknown total; absent means this was the last page."New value: +"Next 1-based offset; keep other inputs unchanged. Present if more events remain or may remain with unknown total; absent on last page."
changedOutput schema / properties / queryEcho / properties / alert_level / description
Previous value: -"PAGER alert filter sent upstream. Absent for EMSC — not supported there."New value: +"Applied minimum PAGER alert; absent for EMSC."
changedOutput schema / properties / queryEcho / properties / end_time / description
Previous value: -"Effective query end time. Absent when omitted from input — the upstream defaults to the current time."New value: +"Applied end time; absent means upstream current-time default."
changedOutput schema / properties / queryEcho / properties / event_type / description
Previous value: -"Event-type filter sent upstream. Absent for EMSC — not supported there."New value: +"Applied event type; absent for EMSC."
changedOutput schema / properties / queryEcho / properties / latitude / description
Previous value: -"Radius-search latitude sent upstream."New value: +"Circle latitude, degrees."
changedOutput schema / properties / queryEcho / properties / longitude / description
Previous value: -"Radius-search longitude sent upstream."New value: +"Circle longitude, degrees."
addedOutput schema / properties / queryEcho / properties / magnitude_type
Added value: +{
+ "description": "Applied magnitude type.",
+ "type": "string"
+}
changedOutput schema / properties / queryEcho / properties / max_depth_km / description
Previous value: -"Maximum depth filter sent upstream."New value: +"Applied maximum depth, km."
changedOutput schema / properties / queryEcho / properties / max_magnitude / description
Previous value: -"Maximum magnitude filter sent upstream."New value: +"Applied maximum magnitude."
changedOutput schema / properties / queryEcho / properties / min_depth_km / description
Previous value: -"Minimum depth filter sent upstream."New value: +"Applied minimum depth, km."
changedOutput schema / properties / queryEcho / properties / min_felt / description
Previous value: -"DYFI felt-report filter sent upstream. Absent for EMSC — not supported there."New value: +"Applied minimum DYFI response count; absent for EMSC."
changedOutput schema / properties / queryEcho / properties / min_magnitude / description
Previous value: -"Minimum magnitude filter sent upstream."New value: +"Applied minimum magnitude."
changedOutput schema / properties / queryEcho / properties / min_significance / description
Previous value: -"Significance filter sent upstream. Absent for EMSC — not supported there."New value: +"Applied minimum significance; absent for EMSC."
addedOutput schema / properties / queryEcho / properties / product_type
Added value: +{
+ "description": "Applied required product; USGS only.",
+ "type": "string"
+}
addedOutput schema / properties / queryEcho / properties / review_status
Added value: +{
+ "description": "Applied review status; USGS only.",
+ "enum": [
+ "automatic",
+ "reviewed"
+ ],
+ "type": "string"
+}
changedOutput schema / properties / queryEcho / properties / start_time / description
Previous value: -"Effective query start time sent upstream — server-resolved to a 30-day window when omitted from input."New value: +"Applied start time; defaults to 30 days before end/now."
changedOutput schema / properties / totalCount / description
Previous value: -"Total events matching the query before the limit was applied. Fetched via a follow-up count query when results are truncated at the limit. Absent when results were not capped, and when that follow-up query failed — countUnavailable separates the two."New value: +"Full match total, inferred from a nonempty short upstream page (or empty first page), otherwise counted for full pages. Absent for empty later pages or failed counts; countUnavailable marks failures."
changedOutput schema / properties / truncated / description
Previous value: -"True when results were capped by the requested limit, candidate limit, or response byte budget. totalCount carries the full match count when available, and nextOffset the input for the following page. With countUnavailable set the total is unknown, so this flag means the page was filled, not that more events are confirmed to remain."New value: +"Page capped by limit, candidates or bytes. Continue with nextOffset. Without totalCount, more events may remain but are not confirmed."