Geoera HOVER WP3 – Task 3-5c product for thermal and natural mineral waters – queries and filters about project-support-wp8

[nmtoken]

If all the information you want to filter on are available as separate attributes in your vector data then you can use custom SLD in a WMS to provide filtered views of data (maps), similarly if you want the results as some data output you can use WFS, filters &/or stored procedures.

For example in the mintell WFS service we have a storequery for filtering by named commodity and year, and output in a number of formats:

• All bauxite production for 2013 output as GML would be:

  http://ogc2.bgs.ac.uk/cgi-bin/mintell/ows?service=WFS&version=2.0.0&request=GetFeature&STOREDQUERY_ID=CommodityByYearStoredQuery&commodity=Bauxite&year=2013&
  

• All lithium production for 2004, output as CSV would be:

  http://ogc2.bgs.ac.uk/cgi-bin/mintell/ows?service=WFS&version=2.0.0&request=GetFeature&STOREDQUERY_ID=CommodityByYearStoredQuery&commodity=Lithium&year=2004&outputFormat=CSV&
  

For WMS if you have standard views you want to show, then you can pre-configure a number of styles per layer, and allow the user to select which style they wish to use; if on the other hand you want users to restyle the map on any available attribute, the client will need to have some intelligence on creating a remote style...

[nmtoken]

Technically the onus on you is to provide consistent data, the required functionality should be configurable by the service provider/implementer.

That said, I think that the EGDI admin console does allow for the posting of MapServer config files which may allow you to provide such functionality indirectly.

So for example you may be able to write your own stored procedure, define your own output format, define your own styles for MapServer, and upload those config files.

[bgsmase]

@elsdan @mh-geus-dk If you have some example data ready for uploading perhaps you could try uploading to the EGDI platform now and see if the level of querying possible is adequate for your needs or not?

[mh-geus-dk]

The sample data is unreadable her at GitHub but if you upload data to EGDI it is possible to add filters and only show part of the data like all values larger that x. If you upload the data to our test system, we can try to add the filter the data. /Martin

[soreslaszlo]

Filtering by property values is a general functionality of the FROST service. Examples are provided and explained in the HOVER FROST training material. Queries can be tested at the prototype service.
e.g.: Find HOVER features with temperature higher than 100 degreeC:

https://geoera.brgm-dev.fr/FROST-Server/v1.1/Datastreams?$count=true&$select=observedArea&$filter=ObservedProperty/definition%20eq%20%27https://data.geoscience.earth/ncl/geoera/hover/temperatureClass%27%20and%20Observations/result%20eq%20%27%3e100%27&$expand=Thing

(for access rights please contact "jb roquencourt" [email protected] )

[mh-geus-dk]

FROST will not be part of the EGDI platform within the GeoERA project.

[bgsmase]

The project will upload their data to the EDGI platform and use the filtering capability available on that. Given that I think this issue can be closed. If there are any problems found with the operation of the filtering afterwards a new issue can be opened.