In the IRC meeting today, we discussed: 1. Putting out a 1.5rc2 in approx 3 weeks 2. Incorporating LISAsoft's catalog example into the codebase (moved from sandbox) 3. Deprecating OWSExplorer and contenxtEditor examples, as the functionality has been moved into LISAsoft's catalog example. 4. Markus Innerbner has volunteered to help with the Catalog example.
Roald, Could you please outline what is required to move the Catalog from the sandbox into the 1_5 branch and the trunk. I'd like to add the capability to process (in order of priority) 1. WMS GetCapabilities 2. WFS GetCapabilities 3. WMC 4. Geonetwork Catalog query We need to explain to Markus what is required here. I assume we will need an EBRIM catalog and I've asked Cubewerx if they can stand one up for us. (as per the CGDIIP project we developed) --- Here is a quick summary of differences between OWSExplorer (old), contextEditor (old) and catalog (new) examples. Old: Capability queries of the numerous services (WMS, WFS, Catalog) are put into numerous XML models. There are then NUMEROUS pick widgets, one for each model, which allow you to pick a layer and put it into a target Context doc. New: Queries of services are converted directly into a Context document. Then we have ONE pick widget which selects a layer for the target Context. -- Cameron Shorter Geospatial Systems Architect Tel: +61 (0)2 8570 5050 Mob: +61 (0)419 142 254 Think Globally, Fix Locally Commercial Support for Geospatial Open Source Solutions http://www.lisasoft.com/LISAsoft/SupportedProducts.html ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
