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

Should the refine property inherit from its parent tile? #7

Closed
pjcozzi opened this issue Jul 30, 2015 · 1 comment
Closed

Should the refine property inherit from its parent tile? #7

pjcozzi opened this issue Jul 30, 2015 · 1 comment

Comments

@pjcozzi
Copy link
Contributor

pjcozzi commented Jul 30, 2015

Currently refine is optional and defaults to "add" (as opposed to "replace").

Instead, if it is omitted, should it inherit its parent's value recursively up the tree?

@pjcozzi
Copy link
Contributor Author

pjcozzi commented Nov 12, 2015

Instead, if it is omitted, should it inherit its parent's value recursively up the tree?

Yes, this is consistent with the spatial coherence inheritance, and it is hard to say that either "add" or "replace" is a sensible default given the diverse use cases 3D Tiles serve.

I also thought about putting this in the top-level 3D Tiles object, e.g., as a sibling to root, but then that would force putting a subtree tree in a separate tiles.json to change refinement strategy, which I believe would take away from a tileset's flexibility for heterogeneous data.

@lilleyse I'll make this change in the spec and probably Cesium if time allows.

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

No branches or pull requests

1 participant