-
Notifications
You must be signed in to change notification settings - Fork 47
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
Overhaul of FeatureInfo (i.e. Infoclick) #1034
Labels
difficulty:complex
Functionality is considered complex to port
module:client/core
Core functionality (not a plugin)
new feature
Request for adding/changing functionality
priority:high
Milestone
Comments
jacobwod
added
difficulty:complex
Functionality is considered complex to port
module:client/core
Core functionality (not a plugin)
new feature
Request for adding/changing functionality
labels
Mar 15, 2022
I'm really looking forward to test this out! 🥳 |
Today's progress: implemented the features list view and a basic "show all attributes" table in the last step (feature details view). Skarminspelning.2022-03-18.kl.13.55.17.mov |
Substantial progress since last time:
Skarminspelning.2022-03-22.kl.14.59.54.mov |
jacobwod
added a commit
that referenced
this issue
Apr 11, 2022
jacobwod
added a commit
that referenced
this issue
Apr 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
difficulty:complex
Functionality is considered complex to port
module:client/core
Core functionality (not a plugin)
new feature
Request for adding/changing functionality
priority:high
I'm adding this issue, as I couldn't find any covering this - in spite of an old ongoing discussion, and complete mock-ups.
We need a way to group feature info responses by layer, similarly to how it's done in search results, where data sets are the first step displayed, before user sees the list of actual results.
There's a mockup that I've done one ugly edit to. The point of my edit is to visualise one more step between step 2-3. I think you get the idea.
I imagine this will be an on-off switch per map where current functionality will remain untouched.
The text was updated successfully, but these errors were encountered: