Remove tile transform restriction on regions #326
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
|
Closing. After some thinking I decided that this restriction is actually ok and makes the most sense. Engines can handle additional client-side transforms however they want, whether that means moving the region or not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed the restriction that states a tile transform can't be used on the
regionbounding volume type. An implementation can get around the coordinate system problem by converting the regions to boxes at runtime, like in CesiumGS/cesium#6755. I wasn't sure if that strategy should be mentioned in the spec or left open.This is targeting the 1.0 branch but can be retargeted if needed.