Review options #100

enzet · 2021-12-20T06:59:28Z

Suggested by @edward17829991 in #99

Boundary box can

be specified explicitly,
be extracted from the input file,
be computed from size and center coordinates,
be computed from explicitly specified tiles.

Stop processing if explicitly specified boundary box is invalid, even if we can get the right one from another source.

If boundary box is explicitly specified, coordinates will be ignored.

enzet added the bug Something that went wrong label Dec 20, 2021

enzet self-assigned this Dec 20, 2021

enzet added a commit that referenced this issue Jan 28, 2022

Issue #100: fix boundary box computing.

743cbb5

enzet added this to To do in Support Feb 16, 2022

enzet added this to the 0.2 milestone Feb 21, 2022

enzet added a commit that referenced this issue Oct 10, 2022

Issue #100: process invalid boundary box.

a6851f1

Stop processing if explicitly specified boundary box is invalid, even if we can get the right one from another source.

enzet added a commit that referenced this issue Oct 11, 2022

Issue #100: add warning for coordinates option.

fa92e68

If boundary box is explicitly specified, coordinates will be ignored.

enzet closed this as completed Oct 11, 2022

Support automation moved this from To do to Done Oct 11, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Review options #100

Review options #100

enzet commented Dec 20, 2021

Review options #100

Review options #100

Comments

enzet commented Dec 20, 2021