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

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.

It does if you google the make and model to find out the lens parameters (assuming it isn't a fancy camera with interchangeable lenses)