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.

Sign up for GitHub

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

Jump to bottom

use init_bounds instead of pyramid bounds on readonly mode #257

Merged
merged 1 commit into from Mar 23, 2020
Merged

use init_bounds instead of pyramid bounds on readonly mode #257

merged 1 commit into from Mar 23, 2020

Conversation

ungarj
Copy link
Owner

@ungarj ungarj commented Mar 23, 2020

In readonly mode all init_bounds (e.g. through the --bounds parameter) are ignored and the default process pyramid bounds are used. This results in the inability to spatially subset the process area.

@ungarj ungarj added the bug label Mar 23, 2020
@ungarj ungarj self-assigned this Mar 23, 2020
@ungarj ungarj added this to In progress in 0.33 Mar 23, 2020
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.626% when pulling 4ea1242 on fix_area_at_zoom into 849bd55 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.626% when pulling 4ea1242 on fix_area_at_zoom into 849bd55 on master.

@ungarj ungarj merged commit ff03747 into master Mar 23, 2020
@ungarj ungarj moved this from In progress to Done in 0.33 Mar 23, 2020
@ungarj ungarj deleted the fix_area_at_zoom branch July 14, 2021 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@ungarj ungarj

Labels
bug
Projects
No open projects
0.33
  
Done
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@ungarj @coveralls