-
Notifications
You must be signed in to change notification settings - Fork 4
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
Differentiating Between LCWIPs/schemes on browse page #445
Comments
Maybe we want to revisit the idea of a 3 tier system: superschemes/LCWIPs, schemes, interventions. Thiscould be reintroduced by putting all schemes from a file into a single superscheme @dabreegster |
The boundary polygons have caused UX problems in the past; I'm not sure about encouraging more. Line 44 in a965c5b
If we had confidence the boundary polygons wouldn't overlap, we could render them as non-interactive objects and style clearly as boundaries using dashed lines. But also, manually drawing these sounds tedious and ripe for inconsistencies. We could calculate convex or concave hulls and see if that helps? Or do some kind of KNN matching. As a brute force thing to try, we could color every scheme a different color. Since there's too many, we could cycle through just some colors, but try to use different colors for adjacent schemes. Maybe in the initial tooltips, we could emphasize scheme too, not just feature name. I don't understand the superscheme idea. We have many schemes (both from LCWIPs and other sources) next to each other on the map, and visually distinguishing them is hard -- that's the root problem we've got? |
|
Just putting the specific ask here for more context |
At a glance, and even possibly with close inspection it's not possible to differentiate between which features belong to which scheme/LCWIP.
We have a 'bounding polygon' tag you can apply to polygons drawn in the sketcher. Maybe we want to encourage the use of this and make it used by the browse page?
I'm sure there are plenty of other options for this too.
The text was updated successfully, but these errors were encountered: