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

Changing to 10000 symbols after zooming in BulkSymbolActivity.java exits activity #1063

Open
adrianababakanian opened this issue Oct 15, 2019 · 2 comments

Comments

@adrianababakanian
Copy link

Background

The BulkSymbolActivity.java is quite performant on all zoom levels for the 10, 100, 500, and 1000 symbol quantity options provided in the dropdown. The 10000 option also works performantly in some cases, but causes the activity to exit after certain zoom interactions. A couple of different scenarios to reproduce the problematic behavior are presented below.

Steps to reproduce

Switching to 10000 symbols when zoomed in

Select any symbol quantity other than 10000, and then zoom into the map. Then, select 10000 from the dropdown, and the activity will exit back to the Annotation plugin list view screen.

Zooming out when using 10000 symbols

If the 10000 option is selected from the dropdown before zooming in, the symbols render after a few seconds. The map can then be zoomed in successfully with only a small amount of lag. However, attempting to zoom back out causes the activity to exit back to the Annotation plugin list view screen.

Although 10000 symbols in a geographic area as condensed as Washington DC is likely not a very common use case, the issue is worth addressing given that the behavior is not currently well-documented or explained. I could not find any log messages that explained the behavior, so even being able to better understand the exiting behavior would be a step in the right direction.

@stale
Copy link

stale bot commented Apr 13, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the archived Archived by Stale bot. label Apr 13, 2020
@stale
Copy link

stale bot commented Apr 13, 2020

This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.

@stale stale bot closed this as completed Apr 13, 2020
@langsmith langsmith reopened this Apr 13, 2020
@stale stale bot removed the archived Archived by Stale bot. label Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants