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

Support for TiledNdArray objects which are subsets of a larger Tileset #136

Open
m-burgoyne opened this issue Oct 19, 2022 · 1 comment
Open
Labels
Priority 2 Dsesirable V1.1 Non-breaking change for Version 1.1

Comments

@m-burgoyne
Copy link

To get the full caching benefits that Tilesets provide it would be useful if TiledNdArray objects could describe a subset of the tiles generated for larger areas, this would allow reuse of existing tiles by CoverageJSON responses for sub regions of larger datasets.

One way this could be acheived would be to add an optional origin member to the TiledNdArray object, this would be an integer array of the same shape as the tileShape member which would describe the origin index values for a TileSet. The values provided by the origin member could then be used by CoverageJSON clients to adjust the values provided by the tileShape member so that they described a subset of the larger tileset. If an origin member was not specified a client would treat the origin values for all dimensions to be zero.

@letmaik
Copy link
Contributor

letmaik commented Oct 19, 2022

I think that makes sense. Are you aware of other standards or APIs where this technique is used?

@chris-little chris-little added the V1.1 Non-breaking change for Version 1.1 label Nov 2, 2022
@chris-little chris-little added the Priority 1 Highly desirable label Jul 11, 2024
@chris-little chris-little added Priority 2 Dsesirable and removed Priority 1 Highly desirable labels Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 2 Dsesirable V1.1 Non-breaking change for Version 1.1
Development

No branches or pull requests

3 participants