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

Picking the correct window size #8

Closed
khufkens opened this issue Jan 18, 2024 · 1 comment
Closed

Picking the correct window size #8

khufkens opened this issue Jan 18, 2024 · 1 comment

Comments

@khufkens
Copy link
Member

khufkens commented Jan 18, 2024

The correct window size for your analysis is dependent on:

  • the texture(s) of your data (crown sizes)
  • the resolution of you data (relative to the true crown sizes)
  • the coverage desired

When selecting your window size you want to make sure that the coarsest texture is captured by such a window. A window size below this coarsest texture in the analysis will lead to poorly classified textures (across the whole spectrum of your dataset). Including too much data, with a large window, will equally decrease the ability of the algorithm to capture all textures well.

In short, the choice of the window depends on the input data and texture types encountered.

To increase the coverage, spatially of the classification output you can use a moving window approach. Rather than using zones, and decreasing the resolution, by a factor scaling with the window size, every pixel and its surrounding will be considered. The resolution of the input data is therefore maintained.

This topic was brought to my attention by @vincent-haller

@khufkens khufkens pinned this issue Jan 18, 2024
@khufkens
Copy link
Member Author

A preliminary vignette is here:

https://bluegreen-labs.github.io/foto/articles/foto-background.html

This documents the basic theoretical background.

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

No branches or pull requests

1 participant