conv.

All stories
TechQuiet 62d · day 63

Solver geolocates a resort island using triangle geometry and CUDA

A writeup for OSINT puzzle Gralhix 004 fingerprints a drone photo's island triangle and brute-forces it against global coastline data on GPU.

What to know

  • A writeup for the 'Gralhix 004' OSINT puzzle geolocates a resort island by building a triangle geometry fingerprint from three visible islands in a drone photo.
  • The author deliberately avoided reverse-image tools like Google Lens, instead brute-forcing the triangle against global OpenStreetMap coastline data using one CUDA thread per candidate triangle.
  • The post reached the Hacker News frontpage (score 226, 46 comments) and was mirrored to Lobsters and Mastodon, where one poster mocked the approach and questioned whether it was genuinely human-made work.

yassa9 Author of the geolocation writeupSofia Santos | Gralhix Creator of the Gralhix OSINT challenge seriesngate@mastodon.social Mastodon commenter

How it unfolded 4 developments, newest first · click a bar or a number to jump articlesposts

No items in the last 30 days Sep 20, 10 PM — quietSep 21, 5 AM — quietSep 21, 12 PM — quietSep 21, 7 PM — quietSep 22, 2 AM — quietSep 22, 9 AM — quietSep 22, 4 PM — quietSep 22, 11 PM — quietSep 23, 6 AM — quietSep 23, 1 PM — quietSep 23, 8 PM — quietSep 24, 3 AM — quietSep 24, 10 AM — quietSep 24, 5 PM — quietSep 25, 12 AM — quietSep 25, 7 AM — quietSep 25, 2 PM — quietSep 25, 9 PM — quietSep 26, 4 AM — quietSep 26, 11 AM — quietSep 26, 6 PM — quietSep 27, 1 AM — quietSep 27, 8 AM — quietSep 27, 3 PM — quietSep 27, 10 PM — quietSep 28, 5 AM — quietSep 28, 12 PM — quietSep 28, 7 PM — quietSep 29, 2 AM — quietSep 29, 9 AM — quietSep 29, 4 PM — quietSep 29, 11 PM — quietSep 30, 6 AM — quietSep 30, 1 PM — quietSep 30, 8 PM — quietOct 1, 3 AM — quietOct 1, 10 AM — quietOct 1, 5 PM — quietOct 2, 12 AM — quietOct 2, 7 AM — quietOct 2, 2 PM — quietOct 2, 9 PM — quietOct 3, 4 AM — quietOct 3, 11 AM — quietOct 3, 6 PM — quietOct 4, 1 AM — quietOct 4, 8 AM — quietOct 4, 3 PM — quietOct 4, 10 PM — quietOct 5, 5 AM — quietOct 5, 12 PM — quietOct 5, 7 PM — quietOct 6, 2 AM — quietOct 6, 9 AM — quietOct 6, 4 PM — quietOct 6, 11 PM — quietOct 7, 6 AM — quietOct 7, 1 PM — quietOct 7, 8 PM — quietOct 8, 3 AM — quietOct 8, 10 AM — quietOct 8, 5 PM — quietOct 9, 12 AM — quietOct 9, 7 AM — quietOct 9, 2 PM — quietOct 9, 9 PM — quietOct 10, 4 AM — quietOct 10, 11 AM — quietOct 10, 6 PM — quietOct 11, 1 AM — quietOct 11, 8 AM — quietOct 11, 3 PM — quietOct 11, 10 PM — quietOct 12, 5 AM — quietOct 12, 12 PM — quietOct 12, 7 PM — quietOct 13, 2 AM — quietOct 13, 9 AM — quietOct 13, 4 PM — quietOct 13, 11 PM — quietOct 14, 6 AM — quietOct 14, 1 PM — quietOct 14, 8 PM — quietOct 15, 3 AM — quietOct 15, 10 AM — quietOct 15, 5 PM — quietOct 16, 12 AM — quietOct 16, 7 AM — quietOct 16, 2 PM — quietOct 16, 9 PM — quietOct 17, 4 AM — quietOct 17, 11 AM — quietOct 17, 6 PM — quietOct 18, 1 AM — quietOct 18, 8 AM — quietOct 18, 3 PM — quietOct 18, 10 PM — quietYesterday, 5 AM — quietYesterday, 12 PM — quietYesterday, 7 PM — quietToday, 2 AM — quietToday, 9 AM — quietToday, 4 PM — quiet ◂ 1–4 earlier
Sep 23Sep 26Sep 29Oct 2Oct 5Oct 8Oct 11Oct 14now · 10:34 PM ET
  1. 4

    Additional Mastodon relay reposts the story

    A Mastodon relay bot re-shares the Hacker News link and discussion thread, continuing cross-platform circulation of the writeup.

    • People liking this post will probably like this [1] and especially these [2] from the channel. All solved using algorithms and map data.[1]

      sllabresHacker News62d agoview on Hacker News ↗
    2 more of the top 3 · 5 posts in this stretch
    • > NOTE: this is a genuine human work, didnt use LLM generation.I'm sorry, but I don't believe this. The article reads like LLM text post-edited by an AI prompted to "write like a non-native English speaker, replace you for u, make errors, etc".The other pages on your site are cough, "the smoking gun". For instance, your "Suckless, single binary…

      mattpkHacker News62d agoview on Hacker News ↗
    • Super fun! Interestingly, this is how JPL was able to significantly reduce the Mars 2020 landing radius on Mars. Cameras onboard take pictures of the terrain and match that to maps to figure out where the lander is.

      zer0x4dHacker News62d agoview on Hacker News ↗
    all of them →
  2. 3

    Lobsters community mirrors the writeup

    The same writeup is cross-posted to Lobsters under the title 'Geolocating Random Islet Image Using Geometry & CUDA GPU Programming', gaining a modest score with no comments yet.

    1. first by HN Best, 62d ago · also HN Frontpage

    • Excellent write up and an enjoyable read! Reminds me of the “good old times” where posts on HN were written by humans and with a specific writing style like yours. You could’ve used a little bit more of geoguessing to narrow down results, or do a brute force visual check on the last hundred or so ;-)

      NKosmatosHacker News62d agoview on Hacker News ↗
    2 more of the top 3 · 5 posts in this stretch
    • This is awesome. I worked on something similar a few months ago. It is a general purpose navigation system based on TERCOM and dead reckoning -

      dwa3592Hacker News62d agoview on Hacker News ↗
    • yea, thanks :D , I used a tiny idea from geoguessing, that I banded the search on islands only in latitude between -30 to +30 deg. based on the sky and the tropical vibes in the img , and it worked !

      yassa9Hacker News62d agoview on Hacker News ↗
    all of them →
  3. 2

    Mastodon poster mocks the method and questions authorship

    A Mastodon account reacts sarcastically to the approach, framing it as overkill compared to Google Lens and casting doubt on whether the writeup is genuinely human-authored work.

    “🤦‍♂️ So someone decided to play "Where's Waldo?" with an island using geometry and GPU programming. Because clearly, using Google Lens is just too mainstream for the cool kids with their ✨CUDA skills✨. And remember, this is absolutely, positively, 100% human work!”
    — ngate@mastodon.social
    • ngate@mastodon.social

      🤦‍♂️ So someone decided to play "Where's Waldo?" with an island using # geometry and GPU programming. Because clearly, using Google Lens is just too mainstream for the cool kids with their ✨CUDA skills✨. And remember, this is absolutely, positively, 100% human work! (As if anyone else would claim it 🤷‍♀️). https:// yassa9.github.io/osint/gralhix…

      ngate@mastodon.socialMastodon62d agoview on Mastodon ↗
    2 more of the top 3 · 3 posts in this stretch
    • For drones and missiles, this technique is known as Terrain Contour Matching. If terrain contour are measured optically, navigation is independent of RF jamming, unlike GNSS.

      bmurray7jhuHacker News62d agoview on Hacker News ↗
    • OpenStreetMap data really is a godsend for such OSINT purposes. Works much better in populated areas too, with more features like roads, shops, electric lines that can be used to search.

      lexlambdaHacker News62d agoview on Hacker News ↗
    all of them →
  4. 1

    Hacker News frontpage picks up the writeup

    The post climbs to a score of 226 with 46 comments on Hacker News after being submitted, and is separately flagged by the HN Frontpage RSS feed.

    “In my opinion, solving this challenge with google lens is wasting a fun opportunity, so decided to solve it with math and programming.”
    — yassa9, Author of the writeup · source
  5. background

    yassa9 publishes CUDA/geometry solution to island geolocation puzzle — The writeup solves Gralhix challenge 004 by clicking pixel coordinates of three islands to build a triangle geometry fingerprint, then filtering global OpenStreetMap land-polygon data (882MB) by tropical latitude, point density and cluster size before running a CUDA kernel that gives one GPU thread per candidate triangle to find a real-world match.

What people are saying 4 voices from 1 site · best of 13 · verbatim