deegree 3 developer meeting (2008/11/04)
Protocol by: AndreasSchmitz
1. Handing over responsibilities
The recent departure of OliverTonnhofer was handled successfully, by means of handing over the responsibilities to other personnel. RutgerBezema took over the raster model, WCS etc. while MarkusSchneider took over the SOS.
2. Geometry model
The geometry model/GML parsing is 95% complete. There are still thoughts/discussions about how to handle the different backends (simple geometry models like PostGIS/JTS as opposed to a complete model like GML), especially when considering the different use cases ("intersects" for simple geometries for delivering/querying the data, geometric operations of all kinds for editing data eg. in a client). The simple models are bound to support many operations on simple geometries, while the complete model (for example the "default" implementation) can represent all kinds of geometries but lacks implementations of the operations. There was the thought that maybe Java3D can be used to support operations also on 3D geometries. JTS can be used to properly support all sorts of 2D operations.
The default implementation set up in the configuration is now "default" instead of JTS.
The lack of resources forces us to postpone the security implementation in deegree 3 for now. It was also said that the implementation of the OWSProxy like component in deegree 3 will take place/makes sense only after the services are running.