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

[Maps] Support WFS for vector layers #33955

Closed
thomasneirynck opened this issue Mar 27, 2019 · 7 comments
Closed

[Maps] Support WFS for vector layers #33955

thomasneirynck opened this issue Mar 27, 2019 · 7 comments
Labels
[Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation enhancement New value added to drive a business result

Comments

@thomasneirynck
Copy link
Contributor

thomasneirynck commented Mar 27, 2019

Support OGC-WFS as a source in the Maps apps

Ideally, this should leverage dynamic querying capabilities of WFS.

  • based on extent
  • based on time (WFS service dependent)
  • based on additional custom query params (WFS service dependent)

cc @gingerwizard

@thomasneirynck thomasneirynck added [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation enhancement New value added to drive a business result labels Mar 27, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-gis

@thomasneirynck
Copy link
Contributor Author

If dynamic querying is not required, users can work-around this by configuring the WFS service as a regionmap in the kibana.yml

@thomasneirynck thomasneirynck changed the title [Maps] Support WFS for vector data [Maps] Support WFS for vector layers Mar 27, 2019
@gingerwizard
Copy link

gingerwizard commented Mar 27, 2019

Example i was looking at was here The Sigmets (areas not to fly) accept params and can be based on time ranges and various filters.

I'd also like us to consider indexing these objects into ES - as well as providing a dynamic querying ability to their original service. Ideally this would be a simple checkbox option (store in ES), with documents indexed periodically in the background as a scheduled task. However, it could also easily be beat. The sigmets above have useful text for querying, not supported through their dynamic interface.

@nreese
Copy link
Contributor

nreese commented Mar 27, 2019

Querying across multiple APIs like WFS is going to be complicated. How do you translate a KQL query into CQL (WMS/WFS query standard) or URL query parameters?

I think it is best to avoid any querying of WMS/WFS and instead move users towards ES ingestion if querying is required.

I like the idea of a Beat that consumes WFS and ingests into elasticsearch.

@thomasneirynck
Copy link
Contributor Author

Let's close for now. It's unlikely this will get picked up soon. Can always reopen.

@desean1625
Copy link
Contributor

desean1625 commented Feb 9, 2024

@thomasneirynck @nreese This plugin support the mapping of geofield and the time field to the wfs propertyName
And supports the conversion of KQL to CQL. It needs more work but has most of the features described here.
https://github.com/spectriclabs/kibana_acecard_external_map_services

@nreese
Copy link
Contributor

nreese commented Feb 10, 2024

This plugin support the mapping of geofield and the time field to the wfs propertyName
And supports the conversion of KQL to CQL. It needs more work but has most of the features described

Thanks for sharing the links. This is a great example of an integration between kibana and WFS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation enhancement New value added to drive a business result
Projects
None yet
Development

No branches or pull requests

5 participants