Closed thomasneirynck closed 2 years ago
Pinging @elastic/kibana-gis
If dynamic querying is not required, users can work-around this by configuring the WFS service as a regionmap in the kibana.yml
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.
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.
Let's close for now. It's unlikely this will get picked up soon. Can always reopen.
@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
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
Support OGC-WFS as a source in the Maps apps
Ideally, this should leverage dynamic querying capabilities of WFS.
cc @gingerwizard