-
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
Support for GeoJson as alternative to WMS #10757
Comments
@thomasneirynck hopefully this is an accurate representation of our discussion. |
@gingerwizard excellent, thanks |
@thomasneirynck does 5.5 geo json cover the requirements here? |
@gingerwizard no. The geojson in 5.5 (region map viz) will only let you use geojon as an overlay layer. The coloring is based on metric-values of a term aggregation. This use-case is for adding a geojson layer for background data. We also want to be able to style this layer arbitrarily. |
We are working on a new implementation of map visualizations and are not planning to add any new features to the existing implementation. We will take this suggestion under consideration for the new app. |
This feature request has been implemented in the new Maps application. The Maps application will be available as a beta preview in the upcoming stack releases 6.7.0 and 7.0.0. You can try the new Maps application today with the 7.0.0-beta1 release |
Currently if a user wishes to render a custom image using the Kibana Maps feature they are required to utilise a WMS service. This is excessive for smaller datasets where the user wishes to still plot geo points e.g. an image of a datacentre with data points representing server temperature.
As an addition to the existing functionality, this ticket proposes adding the ability for the user to specify a geo json source i.e. url. This geo json could be enhanced with simple styles allowing basic styling of the image. The current implementation would need to be enhanced to read and interpret these styles. This approach should be sufficient for small datasets such as building plans. The user would in turn be required to encode the data appropriately within the bounds of the image.
The text was updated successfully, but these errors were encountered: