deegree3 developer team meeting (2009-09-22)
Protocol by: AndreiIonita
1. Interest in WPVS
Interest in deegree 3 WPVS is growing. On the users mailing list (firstname.lastname@example.org) there have been some discussions on configurations which spanned valuable explanations that are worth to be included in the wiki. deegree 3 developer RutgerBezema says that sometimes there is no time to rewrite these explanations into the wiki, and encourages the WPVS users to spend some time and share this information for the future by editing the WPVS page.
2. WPS workshop
ChristianKiehle and MarkusSchneider were tutors in a deegree3/ProcessingService workshop in Bonn/Cologne. Christian presented the motivation and the theoretical foundations of the service in the first day, while Markus held an hands-on session that used the deegree 3 WPS on the second day.
Also worth mentioning as part of the streak of popularity of WPS is that the BKG (Bundesamt für Kartographie und Geodäsie) is interested in the service.
3. Status of services
3.1. WCS status
The deegree3/CoverageService is now CITE-compliant. It is now used in the CCIP project. Recent developments have added a range-set feature and will continue by enabling the writing of GeoTiff data in the future. Altogether, WCS version 1.1 is in the pipeline.
3.2. CSW backend
The prototype for the CSW backend has been defined, supporting a registry approach which should be fast as well as flexible. JensFitzke started a table of requirements that can be found at deegree3/CSWRequirements.
3.3. WFS status
The deegree3/FeatureService version of deegree 3 has the 1.1.0 protocol basically ready (exceptions make the operations LockFeature and GetFeatureWithLock which are currently being worked on).
3.4. WMS status
The deegree3/MapService has now the capability of answering SLD requests.
3.5. SOS status
The optional operation GetFeatureOfInterest has been implemented, as it was needed in the CCIP project (in which it is now used).
4. Other news
A new version is coming for the XML schemas that define the configurations for the services. Accordingly, a policy for version numbering/changing should come its way to the wiki soon.
SteffenThomas has now joined the developer team (Welcome!) and has spent some time familiarizing with the deegree3/CoverageService, as well as with the other related services (e.g. deegree3/SensorObservationService).