Skip to content
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

[ML] Better support for geo in datafeeds #42820

Closed
benwtrent opened this issue Jun 3, 2019 · 1 comment · Fixed by #42969
Closed

[ML] Better support for geo in datafeeds #42820

benwtrent opened this issue Jun 3, 2019 · 1 comment · Fixed by #42969
Assignees
Labels
>enhancement :ml Machine learning

Comments

@benwtrent
Copy link
Member

benwtrent commented Jun 3, 2019

We should allow reading from a geo_point piece of data when using the lat_long detector. The Datafeed needs to automatically account for either a raw geo_point or a geo_centroid (in the event of aggregated data) data point. The formatting (comma delimited string) should happen automatically in the Datafeed before it sends the data back to the ML process.

In short, for the lat_long detector, a Datafeed should support data from: geo_point field, geo_centroid agg, geo_shape field (point type only), and the legacy (current) scripted field option.

This will require a fair bit of work within the extractor logic and some within the validation logic.

@benwtrent benwtrent added >enhancement :ml Machine learning labels Jun 3, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :ml Machine learning
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants