Klaxon a livr earthquake map with no back end

(klaxon.live)

11 points | by Accher 2 hours ago ago

10 comments

  • Retr0id an hour ago

    >open dev tools network tab

    >backend

  • Gualdrapo an hour ago

    Wanted to reach the author about the possibility to help translating this to spanish but they made it a bit difficult. The /about page remits you to the /sources page for some reason, and for some other reason the /sources page remits you to hantawatch.net, which seems to be currently down. Oh well.

    • setopt an hour ago

      Seems the author is active on HN (see the parallel thread)

    • Accher an hour ago

      Hantawatch was my first try at this design of map which I have now archived. I can definitely add in Spanish.

  • pluc an hour ago

    So you've built a JSON parser

  • vachina an hour ago

    There is a frickin backend

    • an hour ago
      [deleted]
  • an hour ago
    [deleted]
  • Accher 2 hours ago

    I built Klaxon (https://klaxon.live) as a hobby project — a single static HTML page that fetches the USGS GeoJSON feed client-side and renders it on a Leaflet map. No backend, no database, no tracking, no ads. It deploys as one file on Netlify.

    It shows M3.5+ earthquakes (1h/24h/7d), with tectonic plate boundaries overlaid so the spatial pattern is obvious. Popups surface USGS PAGER alert level, MMI, felt reports and tsunami flags when present. For events in Japan it links to JMA, since Japanese users think in shindo intensity rather than magnitude. UI is in English, Japanese and Korean.

    Deliberately limited: it does not ingest JMA/NOAA directly (CORS + the static-only constraint), it's not an alerting system, and tsunami support is just a filter on USGS's tsunami flag — not wave modelling. It's a situational-awareness map, not a warning service.

    It's a sibling to an earlier project of mine (an outbreak tracker). Happy to answer questions about the architecture or the deliberate constraints.

    • echoangle an hour ago

      > USGS GeoJSON feed

      Isn’t that your backend then?