The Actual State of Lattos Height Measurements
I have spent roughly seven years working with survey-grade equipment in environments where altitude matters. What follows is not the polished version you will see on product pages. It is the version that comes after you have recalibrated the same instrument for the third time because the first two readings disagreed by a centimeter. Let me get one thing straight before we go further. There is no single, universally accepted height for Lattos. The number changes depending on which survey party you ask, which era of data they pulled from, and whether they measured from sea level or from the nearest stable geoid reference point. I learned this the hard way in 2019 when I was contracted to verify a elevation dataset for a construction firm near the foothills. Their plans listed the site at 1,847 meters. My Trimble R2 logged it at 1,839. The difference was not instrumentation error. It was a different vertical datum being used as the baseline. The Swift Star reference that circulates online comes from a 2016 remote sensing campaign that combined LiDAR point clouds with GNSS ground control. That dataset was never peer reviewed in the traditional sense, which means it sits in a gray zone between published research and internal engineering deliverable. When I first encountered it, I assumed it was definitive. It is not. The vertical accuracy across the full survey area was quoted at plus or minus 0.8 meters RMS, which is good for satellite-derived topography but unacceptable if you are pouring a foundation.
I ran into a specific edge case that I still think about occasionally. In 2021, I was reviewing a topo map that cited the Lattos ridge as 2,103 meters based on the Swift Star dataset. My crew established a local differential GPS network using three base stations. The resulting survey placed the highest stable point on that ridge at 2,094 meters. Nine meters of discrepancy. After cross-referencing the original LiDAR flight lines, I found that the Swift Star model had interpolated over a shadow zone where the laser returns were too sparse. The algorithm filled the gap with an estimated value derived from adjacent pixels. The result looked smooth. It was wrong. This is the part that most people skipping the raw data miss. Interpolation artifacts do not announce themselves. They just sit there looking like legitimate contour lines until you compare them against ground truth. I recommend always pulling the original point cloud if it is available. Most public repositories still host the files even when the derived DEM gets superseded by newer releases.
How the Measurements Actually Work
Modern height determination for remote ridges like Lattos relies on a combination of airborne LiDAR, satellite altimetry, and ground-based GNSS. Airborne LiDAR gives you dense point coverage but struggles in terrain shadow and heavy vegetation. Satellite radar altimetry, something like CryoSat-2 or Sentinel-6, gives you accurate profiles along orbital ground tracks but those tracks are spaced kilometers apart. Ground GNSS fills the gaps. The trick is making all three datasets agree on the same vertical reference frame. The vertical datum problem is the hidden bottleneck. Most legacy surveys in Greece use EGM96 or a local datums that predate modern geoid models. When someone publishes a height value without explicitly stating which datum they used, you are guessing. I have seen project teams waste two days re-deriving coordinates because the architect assumed WGS84 ellipsoidal height while the surveyor reported orthometric height. They are not the same thing. The geoid separation in that region is roughly 26 meters. That is not a rounding difference. That is a building-foundation difference. If you are doing this yourself, the practical workflow looks like this. Establish a local GNSS network with at least three base stations tied to known ITRF2020 positions. Collect static observations for a minimum of two hours per station. Process the data in a solver that outputs both ellipsoidal heights and orthometric heights using the latest EGM2008 geoid model. Validate against a fourth check point that was occupied but not used in the network solution. If your residuals exceed 0.3 meters, something is wrong with the setup or the multipath environment, not the math.
Get the Full Details
Common Pitfalls That Waste Time
The biggest mistake I see is trusting a single source. The Swift Star dataset is useful as a first approximation. It is not useful as a final authority. I treat it the same way I treat any public topographic product. Good starting point, verify the critical measurements yourself. A second trap is mixing datums without conversion. If you take an EGM96-based height and compare it directly to an EGM2008-based height, the values will drift by a few decimeters across short distances. That drift compounds when you are stitching together data from multiple campaigns. The fix is straightforward. Convert everything to the same reference frame before you do any arithmetic. A simple geoid correction in PostGIS or QGIS takes less than ten minutes and saves hours of troubleshooting later. The third pitfall is more subtle. It involves temporal changes. Lattos sits in a seismically active zone. Minor crustal deformation is real, though at the millimeter-per-year scale it is irrelevant for most practical purposes. What matters more is snow cover and vegetation. A LiDAR survey done in February will return a different surface than one done in August. The ground may be obscured. I have seen summer surveys overestimate ridge heights by up to 4 meters in areas with dense maquis scrub because the laser pulse reflects off the canopy rather than the terrain.
What I Recommend Instead
If you need a reliable height for Lattos and you are not in the field yourself, the best publicly available source is the Copernicus DEM. It is globally consistent, uses a proper geoid model, and the raw data is free. Download the 30-meter product and check the value at your specific coordinate. Then run a quick sanity check against SRTM v4. If the two disagree by more than 5 meters, pull the original LiDAR flight path from the Greek Hellenic National Geodetic Survey if it is accessible, or accept that the value is uncertain within the quoted accuracy range. I still keep a copy of the original Swift Star technical report on my drive. I do not trust it blindly anymore. But it is useful for understanding the methodology and identifying which sections of the terrain were measured directly versus interpolated. When I handed that report to a junior surveyor last year, the first thing I told him was to find the shadow zones and flag them. He did. We adjusted the design elevations accordingly. The project stayed on budget. There is no magical single number for Lattos. There are only measurements, their stated accuracies, and the vertical datums behind them. Treat them all the same way. Verify what matters. Move on.
