-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Maps] Add categorical styling #54408
[Maps] Add categorical styling #54408
Conversation
721ad06
to
db8ad51
Compare
d259e1b
to
b8f0aa3
Compare
Pinging @elastic/kibana-gis (Team:Geo) |
remove cruft remove cruft more palettes move options to size as well default rename auto-select tmp stops for consistency fix legend toggle behavior add default stop subdued text color custom legend
b8f0aa3
to
8454f19
Compare
a31ee38
to
87fac2c
Compare
check vlaidyt
add unit test for legend rendering more tests
17235bd
to
599b1a4
Compare
34eec16
to
1c52a14
Compare
restore deal with incomplete config
1c52a14
to
17d51ac
Compare
x-pack/legacy/plugins/maps/public/layers/styles/vector/properties/dynamic_color_property.js
Outdated
Show resolved
Hide resolved
x-pack/legacy/plugins/maps/public/layers/styles/vector/properties/dynamic_color_property.js
Outdated
Show resolved
Hide resolved
x-pack/legacy/plugins/maps/public/layers/styles/vector/properties/dynamic_color_property.js
Outdated
Show resolved
Hide resolved
x-pack/legacy/plugins/maps/public/layers/styles/vector/vector_style_defaults.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
code review, tested in chrome
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✨ Great addition! Thanks for the lifecycle updates to color_map_select
. Offline we discussed one more hopefully quick fix for occasionally passing an undefined
color value to mapbox which causes an error but doesn't appear to affect functionality. Otherwise, works smoothly! lgtm
- tested locally in chrome
- code review
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
thx @aaronjcaldwell , 0532b65 should address the undefined branch coloring issue. |
This allows users to style fields by category. Users can either uses one of default color palettes or specify a custom ramp.
* upstream/master: (72 commits) [ML] Calculate model memory limit API integration tests (elastic#54557) Skip flakey index template component integration tests. (elastic#54878) Add label and icon to nested fields in the doc table (elastic#54199) Reverse dependency of home plugin and apm/ml/cloud (elastic#52883) [SIEM][Detection Engine] Order JSON keys, fix scripts, update pre-packaged rules update invalid snapshot add readme note about alerting / manage_api_key cluster privilege (elastic#54639) [SIEM] New Overview Page (elastic#54783) [Uptime] Feature/refactor context initialization (elastic#54494) Upgrade EUI to v18.2.0 (elastic#54786) [SIEM] [Detection engine] from signals to timeline (elastic#54769) [Index Management] Add Mappings Editor to Index Template Wizard (elastic#47562) [SIEM][Detection Engine] Removes deprecated filter from mapping [Maps] Add categorical styling (elastic#54408) Add mapbox-gl-rtl-text library (elastic#54842) [SIEM][Detection Engine] Adds actions to Rule Details (elastic#54828) Lexicographically sort location tags (elastic#54832) [Maps] expand extent filter to tile boundaries (elastic#54276) [Maps] Use v7.6 Elastic Maps Service API (elastic#54399) [DOCS] Adds monitoring setting (elastic#54819) ...
This allows users to style fields by category. Users can either uses one of default color palettes or specify a custom ramp.
Closes #32202 by adding categorical styling for color properties.
Scope
String fields can be matched to a color
Using a custom palette
Using one of the default palettes.
When using one of the default palettes, the top ten terms from the underlying data are used to style the features.
To keep this PR as small as possible, it excludes some additional features. These can be addressed in subsequent PRs: