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

Unsure about manually entered polygons being cached (Windows) #28

Open
myles28 opened this issue Oct 28, 2022 · 0 comments
Open

Unsure about manually entered polygons being cached (Windows) #28

myles28 opened this issue Oct 28, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@myles28
Copy link

myles28 commented Oct 28, 2022

Still working through this one, so may update if I find more information. I think queries may be using previously cached results, or polygons.

image
Using the above image as an example here are roughly the steps I took to get that result.

  • Manually draw polygon (Roughly where the fires are in the lower left of the image)
  • Search for MTBS wildfires
  • Delete polygon layer and results polygon
  • Draw new polygon (shown in picture above)
  • Search for MTBS Wildfires

This returned wildfires contained in the new polygon and also appears to have returned wildfires from the old search.

Potential things that could be causing this?

  • When adding polygon layers, they all add to the same name for me (geo_enrichment_polygon), even if I add multiple at the same time (I may create a new issue for this)
  • The old results are somehow still saved and when the new query completes it just adds on to the old results table / file

This is running on Windows, with the most recent plugin version (v0.4)

@myles28 myles28 added the bug Something isn't working label Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant