Hi,
The last weeks I have received some inqueries from several people about the
actual
state of the Geoserver W3DS community module.
Related to the W3DS specification, the following operations have been
implemented:
* GetCapabilities (minor improvements are needed related to service
metadata).
* GetScene, support all mandatory and the optionals 'styles' and
'offset' parameters. Can be request by GET or POST.
* GetTile, support all mandatory parameters and can be request by GET
or POST.
* GetFeatureInfo, partially implemented.
* GetLayerInfo, not implemented.
At the moment the only supported output format is X3D (and HTML+X3D).
In order to have more compatibility with the existings 3D GIS we need to
provide KML (3D) output.
The recent GeoServer refactoring, related with KML generation, may be a good
opportunity to add this feature.
TODO LIST:
- Implement a decent support for 3D styles following the candidate
standard (SLD 3D Portrayal);
(the Geoserver styling logic must be improved to accept different
style languages)
- Improve the generation of X3D format (textures 3D, external models,
etc ...).
- Add support for KML 3D format (inclusion of 3D collada models).
- Finish the implementation of GetFeatureInfo operation.
- Improve GetCapabilities operation.
In the next days we will commit the last improvements and our demo service will
be updated.
Any suggestions are very welcome.
Regards,
Nuno Oliveira
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
