-
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] enhance "go to" with location geocoder #31262
Comments
Pinging @elastic/kibana-gis |
++ I've heard this one a few times now and agree that it would be a great enhancement. |
@nickpeihl @thomasneirynck Could geocoding be a service that EMS provides? |
I know we've had similar discussions in the past, but it would be a great service to provide some day. |
It's been considered, but no real action on that front. Pelias -built on top of elasticsearch - could be an avenue to provide geocoding functionality https://github.com/pelias/pelias |
Consider thinking about this as just a search-box backed by a generic (possibly 3rd party) geocoder. It could include support for a customer's Pelias instance, the Google geocoder, Bing geocoder, etc... Does not need to be backed by an Elastic provided geocoder, e.g. part of EMS. @nickpeihl created proof of concept with Pelias #33811 cc @kmartastic |
Agree with @thomasneirynck. We want a search-box experience. If customers can plug their own provider in, that's great. In the end, the majority of customers (especially not Public Sector) will expect Elastic to provide this out of the box (no 3rd party required). |
I am going to close this issue and make a bold statement: The search experience we want is a standalone widget, not an extension of the Go To experience. I have logged a separate issue for this enhancement. #82523 |
The existing
Go to
button allows users to enter latitude, longitude, and zoom. Might be nice to also add a text box that allows users to enter a location name that would then be geocoded into a latitude and longitude. This request came from #28823 which asked for a geocoder in the coordinate map visualization along with some other enhancements.cc @alexfrancoeur
The text was updated successfully, but these errors were encountered: