Search code examples
cassandrageoserverqgisgeomesa

GeoMesa: Cassandra WMS compatibility


I noticed at the bottom of this GeoMesa Cassandra page:

http://www.geomesa.org/documentation/1.3.0/user/cassandra/geoserver.html

that it says:

"Also remember that all queries to a Cassandra layer must include both a bbox component and a date/time between component as part of the CQL filter."

How does this effect compatibility with WMS compliant tools/apis (ie using the geoserver rest api to access layers) such as Leaflet.js and the QGIS time manager plugin? What I would like to do is implement an automatic playback (ie - like playing a movie) for a range of time, displaying the layers across a particular time period with data stored in Cassandra via GeoMesa, but obviously I want to use Leaflet.js and/or the QGIS time manager plugin to automatically supply the updated time parameters to implement this. It seems though that the statement above as it applies to GeoMesa and Cassandra would not comply with the WMS standard which Leaflet.js and the time manager plugin are following.

Am I incorrect in this assessment of GeoMesa and how it stores/exposes data to/from Cassandra? If I am incorrect, is it possible to use the open source tools that I have mentioned for autoplayback which follow the WMS standard?

Thanks.


Solution

  • Full query support was added to the GeoMesaa Cassandra implementation starting in version 1.3.1. However, even in earlier versions, the Cassandra data store is still WMS compliant when installed in GeoServer. It won't return data for queries that don't have both a bounding box and a time range, but as long as you satisfy those requirements, you can call it from leaflet or qgis.