I think you could use the "new image format" hook. Your layer, of
course, is not based on a data file but is generated totally another way
- but it still does the job of saying to the rest of the geoserver
"based on some data that I have (even though it's not from a file), here
are some shapes".
If the geoserver insists that you do use a file, then you could always
stick the connection configuration in it, and that becomes your "image
data" that your plugin knows how to parse.
Alternatively, the geoserver can link to services that provide shapes.
You could write a service that implements that protocol directly, and
point the geoserver at it.
-----Original Message-----
From: Michael Chisholm [mailto:chisholm@anonymised.com]
Sent: Tuesday, 13 January 2009 6:20 AM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Creating a programmatically dynamically
generatedWMS layer
I want to create a WMS layer which does not (directly) come from any
canned shapefile or other service. I need to get at the parameters of
the GetMap query, use them to query some geospatial data, and generate
my own image which is based on that data. So I'm thinking I need a way
to create some sort of plugin. E.g. I could create the raw image data,
say as a Java BufferedImage object, and then pass that off to some other
part of the system to convert to a data stream in some image file
format, which is sent back to the client.
Reference docs on the website
(http://geoserver.org/display/GEOSDOC/0+Extension+Points) list two
extension points; neither quite matches what I need. I don't need new
image formats or WMS operations. (Also, that web page prominently says
it's no longer relevant... not sure what to make of that. Is the
concept of extension points irrelevant, or are those particular
extension points no longer relevant, or are they still there but the
extension mechanism is implemented differently...?)
I am a newbie to GeoServer and to WMS's. Apologies if I am on the wrong
list. In my mind, plugins sit somewhere in between development of
geoserver itself (the dev list) and use and configuration of the webapp
(the user list). Is GeoServer designed to be extended in the way I have
described? How hard would it be to do this? I'm not even wedded to
GeoServer, if anyone has a suggestion for another tool (preferably Java)
which would be more suitable.
Thanks
Andy
------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
------
If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments.
Please consider the environment before printing this email.
------