Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Understanding elevation (Google 3D Tiles) #748

Open
RodrigoHamuy opened this issue Sep 16, 2024 · 6 comments
Open

Understanding elevation (Google 3D Tiles) #748

RodrigoHamuy opened this issue Sep 16, 2024 · 6 comments
Labels
question Further information is requested

Comments

@RodrigoHamuy
Copy link

Example: Trafalgar Square ( tiles.setLatLonToYUp(51.507500 * MathUtils.DEG2RAD, -0.128100 * MathUtils.DEG2RAD); )

  • In 3DTilesRendererJS elevation seems to be roughly at ~ 55 meters.
const axes = new AxesHelper(1000);
axes.position.y = 55;
scene.add(axes);

image

Any reason why Google 3D tiles seem so off?

Thanks!

@RodrigoHamuy RodrigoHamuy added the question Further information is requested label Sep 16, 2024
@gkjohnson
Copy link
Contributor

My only explanation is that Google's data isn't completely precise compared to what are considered canonical altitudes. I asked a similar question on the Cesium forums but never got an answer. Basically Mt Everest's height is measured to be 8,848 meters but when measuring against the served data in this library and Google Earth we get values around 8,700 meters (~8,700m and 8,729m respectively, see images in forum post). It's possible the discrepancy between this project and the Google Earth app is caused by different level of details being loaded (see #747) but I can't be sure.

@lilleyse sorry to ping again - I'm not sure if you have any more information on the precision of Googles Tiles. I see there's no information regarding error bounds listed in the Cesium Ion page. The page on Cesium's globe tiles data has more information on resolution but doesn't state anything about resolution or accuracy relating to altitude. It would nice if this were listed for the data if available - and noted if it's not known.

@lilleyse
Copy link

We've noticed elevation discrepancies with Google 3D Tiles as well. We don't have specific details aside from Google's disclaimer here (see "Can I use it for precise measurements? Can I get the elevation info or other attribution?")

@gkjohnson
Copy link
Contributor

Thanks @lilleyse - is there any more information about altitude information for Cesium's quantized mesh globe tiles? Should we expect that tile set to be more precise? The page I linked looks like it only specifies resolution in latitude and longitude.

@gkjohnson
Copy link
Contributor

I've created a forum post here to see what the right way is to measure heights in Cesium to get a sense for accuracy since it wasn't obvious how to do so. If there's any broader information on elevation accuracy in the Cesium globe data sets that would be best, though!

@lilleyse
Copy link

@gkjohnson Cesium World Terrain should be more precise. If the input data has an embedded vertical datum we use that, otherwise we default to EGM2008. (Though I think the current version of CWT defaulted to EGM96).

@gkjohnson
Copy link
Contributor

Thanks @lilleyse - I've extracted the geoid height from this site and it looks like it adds an additional 28.34m to the mt everest height - bringing the Cesium terrain height to ~8,800m and the Google Terrain sample from this project to ~8,730m.

Looking at the data from Trafalgar Square it looks like the geoid difference is around -46m. Cesium's height sample at the provided lat / lon is ~55m, as well, so with the geoid difference both samples are ~8m, matching Google Earths. It's possible that Google Earth is already including this difference in the calculations.

Other than that I can't tell you why the reported heights in the "whatismyelevation" page. It only really talks about taking data from your mobile device to derive height but not where it comes from when you manually enter a location. Without knowing the provenance of the data being sampled in any of these data sets it's not possible to say what kind of inaccuracies might be introduced and where. Also it's worth nothing that the linked elevation website reports "8,730m" when querying the coordinates for Mt Everest so I wouldn't necessarily consider it a perfect source of truth for this, either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants