To All professional,
I have interest to know the capbility of geoserver; Can it act for a satellite image web server? Any project was something like this?
Thks
Treo
_________________________________________________________________
¶i×^»y¡A¥²¶·´x´¤¥¿½T¤èªk! §K¶O4Ó¤ë^»y½Òµ{¡AݨɬF©²¶i׸ê§U¡A¥ß§Y¦æ°Ê! http://go.msnserver.com/HK/49935.asp
tan tan wrote:
To All professional,
I have interest to know the capbility of geoserver; Can it act for a
satellite image web server? Any project was something like this?
GeoServer is focued on being a Web Feature Server (WFS), that is vector
data. It has recently added the ability to make a raster out of its
Feature data as a Web Map Server (WFS). Both WFS and WMS are
specifications provided by the Open *GIS* Consortium (*OGC*)
<http://www.opengis.org/>\.
The OGC has specifications for a Coverage Server that is more in keeping
with your idea looking at satellite images. GeoServer does seem to want
to develop into a framework for different Web * Services - check back in
a couple of months (or we always accept volunteers).
Jody
Thks
Treo_________________________________________________________________
進修英語，必須掌握正確方法! 免費4個月英語課程，兼享政府進修資助，立即
行動! http://go.msnserver.com/HK/49935.asp-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! InstallShield Windows Installer Get Your Free Trial Today | Revenera
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Jody is quite right in that the OGC Web Coverage Server is currently the approach designed to cope with high volume gridded data.
There is an important underlying principle that is not widely understood or recognised however: Feature Collections and Coverages are transformable:
a Feature Collection is a Feature
a Coverage is a Feature (think of the typical case of metadata, including geometry, plus a simple property containing or referencing a binary grid data structure)
Features can define non-gridded coverages (discrete points or surfaces created from polygons)
To illustrate this, imagine a rainfall data set. It might be a discrete coverage of sampling points or it might be a gridded model output from the same data, at some level there is semantic equivalence. Why should WFS and WCS be very different.
IMHO the current WCS should be thought of as “a convenience API for the limited case of coverages with regular grids”.
Another really good example of the fundamental equivalence is the idea of a “getCount” function in WFS. You are actually returning a coverage with the search area as the implicit geometry and the count statistics as the coverage model. It is easy therefore to extrapolate from getCount to
getCountBy( geometry function such as a grid) or getCountBy(Attribute)
In practice, we often find it necessary to extract the coverage view of data density before unleashing poorly conceived queries to a real data store. This leads into the “query abstraction” concepts we have started to hint at in the ideas for geoserver enhancements coming out ot SEEGrid (see the twiki)
Rob Atkinson
Jody Garnett wrote: