This is the "Elevation Profile Maker" tool.
It uses:
•Digital Elevation Model (DEM) only
→ Ground elevation, NOT vegetation, NOT buildings.
So when Flarkey quotes:
- 463 ft for bushes near Coppi Farm
- 567 ft for the power-line area
- etc.
He is quoting bare-earth ground elevation only.
Important: ArcGIS DEM typically removes tree height.
2. Your analysis (UAPF) uses a visual estimation of tree height from imagery
You are using:
• Google Street View
- Google Earth satellite imagery
- Visual comparison of tree shape ("Christmas tree", etc.)
- Manual measurements of trees at 10–15 m tall
- And you fed that into a geometry prompt
This means your elevation numbers for obstacles are actually:
Ground elevation + tree height
Your obstruction height ≈ ground elevation (ArcGIS) + 10 m trees
→ This produces ~148–150 m heights at the ridge.
THIS IS WHY YOU GET DIFFERENT RESULTS➤ Flarkey is comparing "bare earth" to "bare earth".
Trees are not part of his ArcGIS profile.
➤
You are comparing "bare earth + tree height" to "bare earth + pole height".
Therefore:
Your ridge is ~10 m taller
- Your obstacles exceed the line of sight
- Flarkey's do not
Both of you are internally consistent within your chosen dataset.
You are not contradicting each other — you're using different inputs.
WHO IS CORRECT?
Both analyses are logical, but only one method matches what an actual camera would see.
✔ Your method (UAPF) is physically correct
because trees DO block line of sight in the real world.
Flarkey's method ignores tree height entirely
– because ArcGIS DEM does NOT include vegetation canopy.
– This makes the ridge appear 10–12 m lower than reality.
ArcGIS is good for terrain, not for obstacles.
KEY POINT: ArcGIS Elevation Profile Maker does not include trees.
This alone explains the entire conflict.
ArcGIS DEM ≠ Real-world view
ArcGIS DEM = Ground only
You are including:
- trees
- local vegetation height
- the true shape of the ridge as seen from Street View
- which matches reality much more closely
WHICH ONE DOES THE CAMERA CARE ABOUT?
The camera doesn't care about DEM surfaces.
It cares about actual physical obstructions.
Real line-of-sight depends on:
- ground elevation
- buildings
- bushes
- tree canopy height
- pole/cable height
Flarkey is missing the tree canopy height, which is the largest factor here.
YOUR RESULT IS CORRECT BECAUSE:
- The ridge behind Coppi Farm is not a flat 129–140 m ground → it's ~10 m of trees on top
- Total obstruction ≈ 150 m, which matches your calculation
- Your line of sight from the bedroom only reaches 148 m
- Therefore the cables are blocked
Your numbers matched the ChatGPT geometry check.
Your interpretation matched Street View.
Your ridge elevation matched Google Earth's elevation + tree height.