Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Frontier Labs Job-Board (frontierlabs.work)
    —discuss
  2. Show HN: A Simple GPU Job Scheduler (github.com/ceruleane)
    —discuss
  3. 'Things Will Never Be Chill Again':The Doomers Who Shaped the AI Safety Freakout (wsj.com)
    —discuss
  4. Thiel: Trump administration is staffed by not smart but loyal people (twitter.com/rpsagainsttrump)
    1comments
  5. Show HN: An interactive debugger for the Mornington Crescent esolang (codeberg.org/two9a)
    —discuss
  6. AI-native React components that signal how oversubscribed your funding round is (cncl.co)
    —discuss
  7. The LLM Job Paradox (nilesh.io)
    2comments
  8. United in debt: America has become a nation of fake rich people (thehill.com)
    —discuss
  9. OpenAI halts training of latest models (theguardian.com)
    1comments
  10. You don't need to win or lose. You don't need to choose
    1comments
  11. Beware of Chicken (audible.com)
    1comments
  12. You don't have to choose. You don't have to win or lose
    —discuss
  13. The Six Dumbest Ideas in Computer Security (ranum.com)
    —discuss
  14. Show HN: Ppgrid – Rasterising points in minutes, not hours (mrzk.io)
    —discuss
  15. An agent in a loop optimizing a renderer with the goal to minimize frame times (twitter.com/mitchellh)
    —discuss
  16. Friends embark on 20-year board game battle (bbc.co.uk)
    —discuss
  17. MapleKit – The front end review toolkit (maple-kit.org)
    —discuss
  18. For 958 old to new 9Y0.2 blackened running water tail lamp assembly (porsche-km.com)
    —discuss
  19. OpenAI and Anthropic are investigating cases of AI misbehaving, report says (madrobot.blog)
    —discuss
  20. Horizon Create and Horizon Studio (meta.com)
    —discuss
  21. Trellis: Fractal Layouts for Web Apps (trellisui.com)
    1comments
  22. The SaaSpocalypse was more like a RenaiSaaS (stripeeconomics.com)
    —discuss
  23. I Found a $113,337 Af_alg Linux Local Privilege Escalation Before Copy Fail (idnsec.com)
    —discuss
  24. I expect AI replication incidents by 2027 (lesswrong.com)
    1comments
  25. The Boring Decision That Beats 95% of Stock Pickers (comuniq.xyz)
    —discuss
  26. Show HN: Trail – new kind of logic game (franzai.com)
    —discuss
  27. My Husband Left Me 6 Weeks Postpartum and All I Got Was This Pretty Cool Baby (viverricious.substack.com)
    —discuss
  28. AI and Teams =? (mcastenfors.substack.com)
    —discuss
  29. The New Copilot with Home, Code and Autopilot (blogs.microsoft.com)
    1comments
  30. Kidnapping kids remains legal in USA, this site has you experience it first-hand (elan.school)
    —discuss

Show HN: Ppgrid – Rasterising points in minutes, not hours

2 pointsby 54m agomrzk.io
0 comments
Hi all,

I wanted to share a recent library I made for myself since I continually have to work with large-scale point data spanning millions of rows. I generally found existing IDW tools are insanely slow and unreliable with the datasets I commonly work with.

ppgrid is an open source GIS tool and it is intended to create beautiful visualisations that don't take an absurd amount of time to process. It uses a modified Inverse Distance Weighting (IDW) approach: instead of having to traverse every single point for every single grid O(N*M), it precalculates which points intersect which grids. This means that we essentially avoid the multiplicative scaling costs associated with traditional IDW.

For perspective, ppgrid is significantly faster than IDW from the likes of gdal_grid or GRASS, in the order of 17x faster. I say in the order of as I couldn't really effectively test IDW on the crappy laptop I use beyond 1M points, where as ppgrid happily chewed through 16mil points.

My goals/intention for this post is twofold:

- looking to share it as a tool for anyone who may find it relevant or useful

- looking to stress-test it with different types of point data and try to surface any quirks, bugs or random edge case failures

Important note which I discuss more in my write-up: ppgrid is not yet stress-tested or validated in terms of statistical correctness, as my current use case prioritises visualisation.

AI Disclosure & Creds: I've been pair-coding this with my local Qwen3.8 27B agent, I discuss this in my write-up further. I have ~9YoE in GIS work and ~10YoE as a fullstack.

GitHub Repo: https://github.com/marzukia/ppgrid/

Any other feedback/comments are welcome, please let me know if this has helped as I'd love to see it in action.

A quiet thread, for now.Start the conversation on HN ↗