-
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] Define and document a public maps plugin API for creating custom sources and layers #60918
Comments
Pinging @elastic/kibana-gis (Team:Geo) |
@maihde We are working on providing a registry for sources and layer creation wizards. Check out PR #60870 and please provide feedback. This PR adds a source_registry so plugins can register sources and the PR adds a layer_wizard_registry so plugins can add menu options to |
Pinging @elastic/kibana-presentation (Team:Presentation) |
Closing, completed in #136761. That PR added an example of how to add a custom source |
Describe the feature:
Kibana supports a plugin-system, but the maps sub-system does not expose a mechanism for 3rd party plugins to officially extend the map with custom sources or layers. I would like to request an official supported API within the maps subsystem that allows plugins to extend the map with new sources and layers.
Describe a specific use case for the feature:
We have a custom tile-map-server that provides additional features beyond a generic TMS (https://github.com/spectriclabs/elastic_datashader). We have developed tight integration within Kibana by making a custom-map-source available, but this is accomplished by directly modifying the Kibana source code (highly undesirable). Furthermore, making such modifications to Kibana could in some situations be considered in violation of section 2 of the Elastic License (also highly undesirable).
The text was updated successfully, but these errors were encountered: