-
Notifications
You must be signed in to change notification settings - Fork 2
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
Multiple Phenologic event handling #12
Comments
Hey, so I would be very sure "Phenophases" can't overlap before we bank on it (though it maybe a pragmatic choice). I do agree they should occupy the same ring. The best definition I can find in my dilletance is "An observable stage or phase in the annual life cycle of a plant or animal that can be defined by a start and end point. Phenophases generally have a duration of a few days or weeks. Examples include the period over which newly emerging leaves are visible, or the period over which open flowers are present on a plant. (See also phenological event) (Note: The definition of the term “phenophase” has not yet been standardized and varies among scientists. The definition presented here reflects our usage of the term on the USA-NPN website.)" |
Indeed. The only real issue there would be to consider what happens on hover (since we have an overlap). Still depending on how we display the data it may not matter (mouseover could show info for all the phenophases)... just something we need to cover in designing the interface. |
I am working on the design which, on click, shows all phenophases of a particular specie. Which would alleviate the on click issue. Hover might be different, but for now it could probably just highlight the specie and top most event. A new use case which I outline in issue #17 wants to have the |
Species can have multiple events, how should these be handled?
I feel like they should appear on the same "line" (or ring). In most cases it would seem to me that phenolocigal events never overlap.
I also think, however, that there should be an option to render them separately as well.
The text was updated successfully, but these errors were encountered: