yes, the fast buriers of information did a very thorough job to make the reverse engineering of the event as hard as possible…
last week, I compiled a kml file (available from https://howdoiknowthisinfo.com/butler/snapshots/snapshot_current.zip) that represents my view.
it gives distances and altitudes and heights in feet, meters and yards.
there you can find the coordinates where I put the JCB hydraulic lift based on the information we had at the moment of shipping:
-79.97112266623199,40.85668312671275,3.12 for the hydraulic lift
-79.97099884455767,40.85698684915142,2.99 for Trump’s ear
-79.97048784435141,40.8582313115371,4.3 for the man who died on the roof of building 6
-79.97015846819109,40.85901508681097,9 for the location where I believe the real shooter shot from
earlier this week, forum member @rough_country_gypsy did an excellent drone survey of the area, and I am now stitching these drone images together to get an excellent current view of the rally area and the AGR site.
as soon as that stitching is done, the coordinates mentioned above will be finetuned, but I do not expect huge changes/differences…
when you open the kml file from the zip file mentioned above, you will find a folder called “horizontal planes”.
that is a very valuable (imho ) folder.
when you select whatever altitude above sea level you prefer, it will blacken out all the objects and land below that altitude.
example: this is what you see by default in google earth pro:
after you tick 408.499999, you get this:
as you can see, there is some black creeping up, and everything that has been blackened out is below 408.499999m above sea level…
if you tick 409.749999, you get this:
this system has allowed me to determine the altitudes above sea level for all the points of interest in my kml file:
Trump’s ear on the podium
the bleachers
the roof of building 6 and the higher roof behind him (seen from Trump’s side)
the JCB hydraulic lift, etc, etc…
I am now adding ballistic trajectories to my kml generator such that we can evaluate which vent, window, door opening and roof or even tree top would make sense, as the ballistic trajectories add something very valuable to my model: the angle of impact…
the angle of impact is not guessable while using lines of sight…
given the almost horizontal flag, there was a very heavy wind, which means that if the wind had been a little less prominent, Trump would have died with certainty (the wind came from the side of the green, blowing the bullet (slightly but sufficiently) away from his face…
so, these are my two cents about coordinates
during next week, I will release an update of my current snapshot that contains these ballistic trajectories, but for now on, you can play with the straight lines of sight version…
something like this is what you get when selecting the current straight line of sights model under the assumption that the bullets were fired from the position where that man died:
these are the lines of fire when shot from the higher roof behind building 6:
and this is a combination of both to show that there is no noticeable difference between the different lines of sight:
the only (!) remark I got so far on this model is that “the position of the shooter on that higher building does not match the audio files”, and that is true.
I started analyzing the sound analysis, and what turns out?
Mike Bell states in his analyses that there are anomalies with the sound registrations of RealDjStew and the witnesses near the trees because they heard the shots TOO early…
by now, it should not be a surprise to you that both witnesses had direct line of ear (hehe) with that higher roof!
there is about 130m between the position I put the real shooter at and the witnesses who made recordings under the trees, and about 140m between that real shooter and RealDjStew…
after having added the ballistic trajectories to my kml file, I will calculate the sound patterns myself to corroborate the sound analyses, but many different concerns have been spotted with these analyses already:
- they do not all use the same (or even close) speeds of sound. Chris provided me with the speed of sound value that he uses, so that is the value that I will be using too for reference and validation
- they use average muzzle velocities, but do not consider the calibers and muzzle velocities that I would consider
- certain models need some help to validate whether a certain shooter position would make sense or not, and the analyses never considered testing that higher building…
so be it
about your question about RealDjStew’s drone sightings in his videos: I only “trust” videos that have been made available until 1-2 days after the event.
I know of 5 videos that have these drone sightings, and it turns out that RealDjStew’s phone was confiscated by the fast buriers of information for 3 days… that leaves plenty of time to add some drone shaped smudges and launch the hoax that there were military grade fast flying drones at the rally…
I do not trust any eye witness or any news media reporting on these things.
I do follow Chris Martenson and Gary Menton from Paramount Technical and Gray Hugues Investigates and a couple of other great sources, but I do not take whatever they say for face value…
I have been a forensic researcher for over 20 years and an auditor of complex systems for over 27 years…
I only trust what I have corroborated myself based on various sources.