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

Apply root tile scale to tileset geometric error #11047

Merged
merged 1 commit into from
Jan 25, 2023

Conversation

lilleyse
Copy link
Contributor

@lilleyse lilleyse commented Jan 24, 2023

This is related to the problem that was brought up in #5330. As of #8182 we take scale into account when computing a tile's geometric error (see updateGeometricErrorScale) but we don't take scale into account when computing the top-level tileset geometric error.

This can lead to situations where the tileset's geometric error is less than the root tile's geometric error and traversal exits early.

The fix is to scale the tileset's geometric error by the root tile's scale.

@cesium-concierge
Copy link

Thanks for the pull request @lilleyse!

  • ✔️ Signed CLA found.
  • CHANGES.md was not updated.
    • If this change updates the public API in any way, please add a bullet point to CHANGES.md.
  • ❔ Unit tests were not updated.
    • Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

  • Cesium Viewer works.
  • Works in 2D/CV.

@ggetz
Copy link
Contributor

ggetz commented Jan 25, 2023

Thanks for the fix, @lilleyse! I tested this out on a tileset where the traversal was exiting early and the issue is resolved.

@ggetz ggetz merged commit e912d6c into main Jan 25, 2023
@ggetz ggetz deleted the fix-tileset-geometric-error branch January 25, 2023 14:17
@jo-chemla
Copy link

Cross-posting from the cesium community forum:

I have the same issue, where setting a maximumScreenSpaceError of 0.1 makes it so that my tileset appears at lower zoom levels - and it disappears when this max error is set to simply 1.0. I’m using Cesium version 1.106. Has this fix been merged to the current cesium build? Thanks a lot for getting back!

Looks like the fix indeed has been merged into 1.102, but I’m still seeing this issue. If you’d like a link to the dataset, I can share it privately.

@ggetz
Copy link
Contributor

ggetz commented Jun 9, 2023

Hi @jo-chemla, you can send private data to [email protected]. Please include a link to the original post so we know what the context is. Thanks!

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

Successfully merging this pull request may close these issues.

4 participants