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

What standard do ndpyramids conform to? #78

Closed
TomNicholas opened this issue Dec 5, 2023 · 2 comments · Fixed by #89
Closed

What standard do ndpyramids conform to? #78

TomNicholas opened this issue Dec 5, 2023 · 2 comments · Fixed by #89

Comments

@TomNicholas
Copy link
Contributor

My understanding after speaking to @katamartin and @andersy005 yesterday is that the visualization tools expect the pyramids to conform to some "slippy web map tile" standard (or something like that), and that the purpose of this package is to write out Zarr store which basically contain data that conforms to this standard in some way. This info about the standard doesn't seem to be documented anywhere in this package though - have I misunderstood?

@maxrjones
Copy link
Contributor

Hi @TomNicholas! You can find some documentation here - https://docs.carbonplan.org/maps/data. Note that page needs some updating after recent maps enhancements (we now support EPSG:4326 as well). We should also add a link to that page from ndpyramid.

We've been talking about formalizing this beyond just our mapping library (e.g., zarr-developers/zarr-specs#125) - let us know if you'd be interested in collaborating on that!

@TomNicholas
Copy link
Contributor Author

Thanks @maxrjones . I guess I'm still a bit confused - that page talks about "adhering to the conventions encoded in the ndpyramid utility", but is that a one-off bespoke format? Did you guys come up with the 128x128 size tiles, and a set of groups of integer multiples of those sizes (i.e. 256x256 for the next resolution up)?

We've been talking about formalizing this beyond just our mapping library

I think that would be very cool, but probably mostly involves you guys talking to the developers of other visualization libraries (e.g. holoviews) to agree upon a standard.

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 a pull request may close this issue.

2 participants