JuliaDataCubes / JuliaDataCubes/PyramidScheme.jl

Output keyword for Pyramid construction

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
18
Forks
3
PR merge metrics
No merged PRs in 30d

Description

We should be able to set the location that the pyramids are saved to. This could be internal, saying it would be saved in the same file as the input or it could be a path to a new file. Or temp for the current behavior. Should we be able to also save geotiff overviews or focus on zarr?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or construction entry point is named. Start by locating the pyramid-construction API and tracing how its current temporary output is selected. Before implementation, clarify whether the issue should support internal output, a new path, or temporary storage, and whether GeoTIFF overviews are in scope alongside Zarr.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
data-visualization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.