I have a new web service that will be producing various geospatial products from another data source. My web service is REST or SOAP based and as such I was looking for the right way to integrate a plugin into Geoserver.
I want to be able to take advantage of Geoserver's WMS capability but just have it forward calls to retrieve data from my service rather than its own native data sources.
I cannot write a data source because this functionality I'm creating is to be used in a larger system that will be independent of Geoserver. The Geoserver portion is only the client side.
From the tutorial, it seemed like there was no standard API that I should be implementing for this kind of functionality (in the OWS method).
Should I be implementing the GetMapProducer interface? There's no methods there that correspond to the WCS GetCoverage and WFS GetFeature methods in that interface so I was also wondering how I can inject my service into that portion of the server.
Thanks,
Ronak Patel
Ronak Patel ha scritto:
I have a new web service that will be producing various geospatial
products from another data source. My web service is REST or SOAP
based and as such I was looking for the right way to integrate a
plugin into Geoserver.
I want to be able to take advantage of Geoserver's WMS capability but
just have it forward calls to retrieve data from my service rather
than its own native data sources.
I cannot write a data source because this functionality I'm creating
is to be used in a larger system that will be independent of
Geoserver. The Geoserver portion is only the client side.
From the tutorial, it seemed like there was no standard API that I
should be implementing for this kind of functionality (in the OWS
method).
Should I be implementing the GetMapProducer interface? There's no
methods there that correspond to the WCS GetCoverage and WFS
GetFeature methods in that interface so I was also wondering how I
can inject my service into that portion of the server.
Let me try to drill down the extensions possibilities you have
today:
- you implement a map producer or a output format in case
the data sources we have already suit you (shapefile, postgis,
and so on) and you have to generate a new kind of output,
say a different image format or something similar
- you implement a new service if you want geoserver to talk
a different protocol that then ones it can do already, that
is, WMS, WCS, WFS (WPS being in the works)
- you implement a new datastore if the formats and services
are ok, but you need to grab data from a source we cannot
talk to already. This seems your case btw.
- you implement a new coverage format if you need to read
raster data in a format we don't already support
If you need to render something that cannot be represented
as Feature or as Coverage, or you need styling other than
SLD, then we don't have an extension point ready for you.
To make you an example, today we have no way to cascade
another WMS because there is no way to represent that in the
catalog (it's not feature, it's not coverage) and we have
no way to build a custom renderer for that layer.
Hope this helps
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.