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 ;-)
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 !
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.
It’s an effective a surprisingly old technique, being used on cruise missiles as early as the 1960s. It actually precedes GPS and satellite navigation by several decades. Im continuously blown away by what engineers were able to do in that era with such limited computing power. Take a look at SAGE, for example.
Fun fact: the usage of TERCOM in the tomahawk missile actually limited its ability to be used in Operation Desert Storm. Routes had to be planned to go around actual topographical features, instead of hundreds of miles of flat desert.
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. https://www-robotics.jpl.nasa.gov/what-we-do/flight-projects...
I find it highly ironic that his is the second article on the main page right after "avoid building technologies that could be used by a police state".
> 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, zero-dependency CUDA/C++ inference engine for NVIDIA's DVLT. Reconstructs 3D scenes from a handful of images (depth + rays + camera pose => point cloud), no python, no torch, no framework." project.
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.
Claude / Gemini + OSM Turbo is a crazy you can do natural language queries like "find me a bus stop in germany that's surrounded by more than 5 three story buildings"
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 - https://github.com/deepanwadhwa/anumaan
do u mean the whole work ?
I spent at first 3 "whole" days in research, trial and error
trying different methods and scripts, like for example tried the depth estimation to build upon it, failed many times till I gave up
then came back after a week and spent another 4 days till succeeded
then the refining, cleaning and organizing of all of that, also structuring and writing the blog, took about another 3 days
thanks, and yea, it should be solved easily by passing the img to google lens, the website is the first result, but I found a fun opportunity to solve it in different way
yea, good observation, my guess is its the data more than the filter. OSM coastline polygons are generalized to different degrees depending on who traced them and from what imagery, so the fine shape detail a halo check would key on often is not in the geometry at all.
I observed that at the end, didnt push on it further though. It already passed and I was super exhausted
I meant the blog itself, the writeup, the steps and the walkthrough all by hand
, the final code u see is llm refined, of course, I wont publish my messy and spaghetti files with much tests, failures and dead ends, also vizualizations functions to produce that green maps , and faulty versions of them
ok, if u came with the whole conclusion by only this line, ok
, but to answer u, ( I hate to justify myself , but have to )
I started writing the blog after I started solving another challenge from gralhix : https://gralhix.com/list-of-osint-exercises/osint-exercise-0...
and the part of the solution came from the metadata, the camera model, you can check urself, so when I came back to write the blog, it just came by flow,
yea thank u, that's another part, but mainly it would hard although knowing that, because you need to know elevation of the drone or the camera, which is also extremely difficult (I already mentioned that in the blog)
they literally memorize and get patterns of every possible road, place, map of any area (scanned by google earth), getting exact coordinates from single image, and play competitions and world cup based on that
they do really nice videos about finding places in old photos people ask for
haha, thanks :D
I was hesitant to whether write it or not,
but I really really despise llm generated posts and blogs
and im glad someone appreciated it
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 ;-)
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 !
agree! AWESOME work!
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.
https://en.wikipedia.org/wiki/TERCOM
oh, wow, I didnt know that existed, thank u, sure gonna look into it
It’s an effective a surprisingly old technique, being used on cruise missiles as early as the 1960s. It actually precedes GPS and satellite navigation by several decades. Im continuously blown away by what engineers were able to do in that era with such limited computing power. Take a look at SAGE, for example.
Fun fact: the usage of TERCOM in the tomahawk missile actually limited its ability to be used in Operation Desert Storm. Routes had to be planned to go around actual topographical features, instead of hundreds of miles of flat desert.
Rumour has it that they achieved the first TERCOM using the then revolutionary bit slicing technology.
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. https://www-robotics.jpl.nasa.gov/what-we-do/flight-projects...
omg wow, thats super hard, although cool ,
It was cool, very fun 3 years of my life working as a part of that team :)
I find it highly ironic that his is the second article on the main page right after "avoid building technologies that could be used by a police state".
EVERY technology could be used by a police state
It is a question of how adversely empowering the technology is.
This is beyond impressive. Very good work!
glad u liked it :D
> 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, zero-dependency CUDA/C++ inference engine for NVIDIA's DVLT. Reconstructs 3D scenes from a handful of images (depth + rays + camera pose => point cloud), no python, no torch, no framework." project.
Awesome write up! This is now one of my favorite articles on HN.
thaaank u man, I really appreciate ur comment
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.
yea , heard about them before, but didnt know that whole treasure till I really used it , impressive
Claude / Gemini + OSM Turbo is a crazy you can do natural language queries like "find me a bus stop in germany that's surrounded by more than 5 three story buildings"
People liking this post will probably like this [1] and especially these [2] from the channel. All solved using algorithms and map data.
[1] https://www.youtube.com/@colsto
[2] https://www.youtube.com/watch?v=eY-W9gmwxhg https://www.youtube.com/watch?v=nzytWZPyuEw https://www.youtube.com/watch?v=rkmXs_7hELg
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 - https://github.com/deepanwadhwa/anumaan
Really great article! OP, you did an awesome job breaking down a complex problem into manageable chunks and synthesizing the solution.
thanks, appreciate it
@yassa How long did this take?
do u mean the whole work ? I spent at first 3 "whole" days in research, trial and error trying different methods and scripts, like for example tried the depth estimation to build upon it, failed many times till I gave up then came back after a week and spent another 4 days till succeeded then the refining, cleaning and organizing of all of that, also structuring and writing the blog, took about another 3 days
you can say that total is ~10 days of work
Excellent read, I loved it.
Incidentally, the image seems to be the one the resort uses on their website! https://oanresort.wixsite.com/chuuk
thanks, and yea, it should be solved easily by passing the img to google lens, the website is the first result, but I found a fun opportunity to solve it in different way
Good article! Off-topic, Is Palantir doing the same thing with its internal software to geolocate?
thanks ! no idea about Palantir, but in my opinion, this can not be automated , needs much manual work and tons of trial and error
Assuming they (and militaries broadly) do this +more, like actually using vision models trained on billions of geolocated landscape photos.
It’s interesting that most top contenders don’t pass the eyeball halo check, seems like there’s room to optimize that filter in code.
yea, good observation, my guess is its the data more than the filter. OSM coastline polygons are generalized to different degrees depending on who traced them and from what imagery, so the fine shape detail a halo check would key on often is not in the geometry at all.
I observed that at the end, didnt push on it further though. It already passed and I was super exhausted
I read all the process, literally awesome, i don't do OSINT (i know only what is this) and i think that's very cool
thaaank you !! Its my first ever challenge to do, and yea, I really found my passion
Good job, Yassa. This is how you get a job in the AI age.
haha, I wish , this is my first OSINT challenge to solve tho
What do you mean by no LLM generation if an LLM did all the coding based on reading through the .py files? Pangram isn't kind to "your" text either.
I meant the blog itself, the writeup, the steps and the walkthrough all by hand , the final code u see is llm refined, of course, I wont publish my messy and spaghetti files with much tests, failures and dead ends, also vizualizations functions to produce that green maps , and faulty versions of them
but you are right, I should add that
Just by reading your actual messages it's easy to see that you didn't write the blog post entirely by hand.
ok
"No EXIF, no GPS, no camera make or model."
Yeah, a human definitely wrote this. Nothing fishy here. (Why would the camera make or model matter???)
ok, if u came with the whole conclusion by only this line, ok , but to answer u, ( I hate to justify myself , but have to ) I started writing the blog after I started solving another challenge from gralhix : https://gralhix.com/list-of-osint-exercises/osint-exercise-0...
and the part of the solution came from the metadata, the camera model, you can check urself, so when I came back to write the blog, it just came by flow,
If you know the camera make and model, you might be able to get lens parameters and get better estimates of real world geometry from the image
yea thank u, that's another part, but mainly it would hard although knowing that, because you need to know elevation of the drone or the camera, which is also extremely difficult (I already mentioned that in the blog)
The camera make and model wouldn't tell you the lens parameters. The EXIF would, but that was already covered in the triplet.
Nice, but Rainbolt would do it in under a minute ;)
haha, I actually agree
What about tides? Would the outline of the island be different based on the time of day.
honestly, I didn't think about it, I just trusted the OSM polygons
Not glamorous but it works
this is really cool. fun little problem turned into great write-up, and i love that you included the code snippets. thanks for sharing
really glad that you liked it
great blog and great writeup
thannks, really grateful :D
Loved it.
really impressive, could that be the way to locate yourself without GPS? assuming we know more/less where we are
yea, search about geoguessing on youtube, people like Rainbolt, https://www.youtube.com/@georainbolt
they literally memorize and get patterns of every possible road, place, map of any area (scanned by google earth), getting exact coordinates from single image, and play competitions and world cup based on that
they do really nice videos about finding places in old photos people ask for
> NOTE: this is a genuine human work, didnt use LLM generation.
A million upvotes from me.
haha, thanks :D I was hesitant to whether write it or not, but I really really despise llm generated posts and blogs and im glad someone appreciated it
impressive
All of this to not use Google images
All of this to try and learn something new
This is the real takeaway