Feature Request: OGC Support

[lossyrob]

There should be clear ways to expose GeoTrellis functionality through OGC compliant services such as WMS/WCS. This can happen through integration with GeoServer, or by creating services in Scala inside GeoTrellis or in an external project.

Feel free to comment on this issue for ideas about approaches and how to get this done.

[metasim]

We talked about this early on in our project, and think that it wouldn't be too hard to serve up GeoTrellis layers as a WCS. After reading this I think it's clear that WCS is what you want if you're doing data analysis on tiles. WMS (which GT could also provide) is what you want for slippy map like or front-end visualization functionality. At any rate (and either way) I think it is the Data Store API that you'd have to implement.

Here are the GeoMesa docs on how it works in their implementation.

[metasim]

cc: @mteldridge

[echeipesh]

Work on GeoTrellis WCS service started here: https://github.com/geotrellis/geotrellis-server Currently it has the limitation of only serving layers in LatLng, repcjerting source layer if needed. This restriction should be removed in the next stage of work there.

[ALPSMAC]

You might be able to introduce a more general GeoServer plugin to expose a TMS publishing GeoTiff formatted tiles as a new Data Store.
That way you could stick with the general pattern of exposing your own tileserver via e.g. Spray or Akka-Http and then just proxy the result through GeoServer to allow it to corner-turn the TMS into WMS/WCS/whatever... We've had some success with that approach internally but have struggled with understanding GeoServer's treatment of the TIME and ELEVATION dimensions.

[pomadchin]

https://github.com/geotrellis/geotrellis-server 💯