docs: Better use of computational region in NumPy examples #6315
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This improves how computational region is handled in all NumPy examples. Specifically, it creates variables for number of rows and columns and only then sets the computational region to be clear what is happening.
This still has limited applicability as it works without a geographical context. Notably, NumPy arrays are generally not georeferenced, so XY project is applicable and I added creation of the project to the example. Maybe this is enough for the basic example.
While this builds on #6313 (and currently contains also the changes from there), I'm opening a separate PR to allow for a separate discussion on how to handle this.